Shelly Cloud DIY

Shelly Cloud DIY

• Authorization cloud keyThe long string the Shelly Smart Control app shows under Access and permissions.
• Server URIThe hostname shown below the key, e.g. shelly-42-eu.shelly.cloud.
• Poll interval (seconds)How often Home Assistant polls Shelly Cloud for state. Default 5 s; range 3–60 s. Shelly enforces a 1 req/s rate limit.
• Local gateway URL (optional, for EM historical data)Only needed if you use a local Shelly gateway to back-fill historical energy data.

Choose devices to expose

• Bulk action"Tick all" or "Untick all" overrides the manual list below on save. Pick "Manual selection" to keep the list as-is.
• Devices (tick/untick individually)Only ticked devices produce Home Assistant entities.

Also asked when at the selection updated — not saved yet step.

Re-authenticate Shelly Cloud DIY

• Authorization cloud keyThe long string the Shelly Smart Control app shows under Access and permissions.
• Server URIOnly change this if Shelly moved your account; the stored value is prefilled.

Sign in to Shelly again for cloud control

• Shelly account emailThe email address you use in the Shelly app.
• Shelly account passwordUsed once to sign in and then discarded. Only the resulting token is stored.

After setup

• Poll interval (seconds)3–60 s. Lower values feel snappier but consume more of Shelly's 1 req/s rate-limit budget.
• Report a device as offline after (minutes)2–1440 min, default 30. Each device's "Reporting" sensor turns off once the device has been silent this long. It is only a base value: a device that is naturally quieter earns a wider window on its own, and battery or BLE devices are handled separately. Lowering it therefore mainly speeds up detection on devices that report continuously, such as power-metering plugs.
• Warn about a relay that no longer opensOn by default. Watches every switching channel that meters its own output and warns when the relay reports itself as open while a real load is still flowing through it — a contact that has welded shut. Turn this off if a Shelly of yours sits in a two-way circuit, where the other switch can push current through the meter while the relay is genuinely open.
• Local gateway URL (optional, for EM historical data)Only needed if you use a local Shelly gateway to back-fill historical energy data.
• Warn about devices in poor healthOn by default. Interprets data every poll already returns: Wi-Fi signal (warning at -70 dBm, error at -85 dBm), component temperature (70 °C / 85 °C), free memory and free storage (under 20 % / 10 %), a restart the device is still waiting for, and any component reporting its own error. It costs no extra requests. Bluetooth (BLU) devices are judged only on the signal their gateway reports for them, and Gen1 devices are not judged at all. Only a component's own temperature counts, never an external Add-on probe.
• Count a pending firmware update as a findingOff by default. Adds "a firmware update is available" as a finding. On a typical account most devices have one pending, so switching this on tends to keep the card permanently lit — which is exactly what stops you noticing the findings that matter.
• Control virtual components over the cloud (unsupported)Off by default, and worth reading before switching on. Virtual components (an irrigation controller's zones, a script's switch) can be read over the documented Shelly Cloud API but not written — every documented route answers "no such route". Switching them is possible only over an undocumented channel, which Shelly support declared unsupported on 2026-07-27 and can change or withdraw without notice. What it costs: your Shelly account sign-in (asked for on the next step; the password is used once and never stored) and a second connection to Shelly Cloud. What it gives you: a switch for each virtual boolean, but only on devices your account owns. A shared device is refused by Shelly itself, and no switch appears for it. The switch is created in addition to the existing read-only sensor of the same component, never instead of it, so nothing you have already built on that sensor breaks. Switching this off again deletes the stored sign-in.
• Bulk action"Tick all" or "Untick all" overrides the manual list below on save.
• Devices (tick/untick individually)Only ticked devices produce Home Assistant entities.
• Bulk action"Tick all" or "Untick all" overrides the manual list below on save.
• Devices (tick/untick individually)Only ticked devices produce Home Assistant entities.
• Shelly account emailThe email address you use in the Shelly app.
• Shelly account passwordUsed once to sign in and then discarded. Only the resulting token is stored.