Nature Remo

The Nature Remo integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] connects the smart remote controllers made by Nature to Home Assistant through the Nature Remo Cloud API. The Remo series are infrared remote hubs with built-in environment sensors, popular for controlling air conditioners, TVs, and lights. The Remo E series is a separate product line: it has no infrared hardware and is instead an ECHONET Lite controller that reads and controls ECHONET Lite devices, most commonly a residential smart meter.

You can use this integration to track the temperature and humidity of every room that has a Remo without extra hardware, to feed the energy imported from and exported to the grid into the energy dashboard through a Remo E, and to notice that a room has been empty for a while from the timestamp of the last detected motion.

Supported devices

The integration talks to the Nature cloud, so every Remo registered in the Nature Home app is picked up automatically, including devices in multiple homes on the same account. It has been verified with:

• Nature Remo 3
• Nature Remo mini
• Nature Remo (1st generation)
• Nature Remo Lapis
• Nature Remo E lite (ECHONET Lite controller)

Other models, such as the infrared hubs Nature Remo 2 and Remo nano and the Nature Remo E controller, use the same cloud API and are expected to work. Note that the Remo nano has no built-in sensors, so it provides no sensor entities.

Prerequisites

1. Set up your Remo devices in the Nature Home app first; the integration only sees what the Nature cloud knows about.
2. Sign in to home.nature.global with your Nature account and generate an access token. Store it somewhere safe; the token is shown only once.

Configuration

To add the Nature Remo hub to your Home Assistant instance, use this My button:

Sensors

Remo hubs expose their built-in sensors (availability varies by model):

• Temperature
• Humidity
• Illuminance: the raw brightness level the device reports; Nature does not document a physical unit for it.
• Last motion: the timestamp of the most recent motion detection.

Remo E and Remo E lite expose their smart-meter readings, ready for the energy dashboard:

• Power: the instantaneous power measured by the meter.
• Imported energy: the cumulative energy taken from the grid.
• Exported energy: the cumulative energy fed back into the grid, for example from solar panels. Only created when the meter reports it.

Example automations

Automation: warn when a room gets hot

This automation sends a notification when the living room stays above 28 °C for 10 minutes.

• Trigger: Numeric state
  • Entity: Living Remo Temperature (sensor.living_remo_temperature)
  • Above: 28
  • For: 10 minutes
• Action: Send a notification message
  • Target: My Device (notify.my_device)
  • Message: Living room is at {{ states('sensor.living_remo_temperature') }} °C.

alias: "Warn when the living room gets hot"
triggers:
  - trigger: numeric_state
    entity_id: sensor.living_remo_temperature
    above: 28
    for: "00:10:00"
actions:
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      message: >-
        Living room is at
        {{ states('sensor.living_remo_temperature') }} °C.

Data updates

The integration pollsData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more] the Nature cloud every 60 seconds (two API requests per cycle). The Nature API allows 30 requests per 5 minutes per account, shared by every API client using the same account, so configure the integration only once per account. If the account still runs into the rate limit, the integration pauses polling and retries once the reset time reported by the API has passed.

Known limitations

Polling delay

The Nature cloud has no push channel, so all data arrives by polling; state changes can take up to a minute to appear.

Motion detection

Motion is reported only as the timestamp of the last detection. A real-time motion binary sensor is not possible with this API.

Offline detection

Hubs running older firmware do not report an online/offline flag; an unplugged hub is only noticeable through readings that stop updating.

Troubleshooting

Removing the integration

This integration follows standard integration removal.

To remove an integration instance from Home Assistant

1. Go to Settings > Devices & services and select the integration card.
2. Next to the entry you want to remove, select the three dots menu. Then, select Delete.
   • Depending on the integration, the entries are listed under one of the following headings:
     • Devices
     • Hubs
     • Services
     • Integration entries
3. To confirm, select Delete.
   • Home Assistant also deletes the devices and entities of the entry.
4. If Home Assistant asks you to restart, restart Home Assistant.
5. If Home Assistant asks whether to also delete the application credentials, select Remove or Keep.
   • If you keep them, Home Assistant uses them automatically when you add the integration again.
   • To delete them later, refer to Deleting application credentials.

After removing the integration, you can revoke the access token at home.nature.global if it is no longer used.