Guides
The device web interface
Every Shelly has its own small interface running on its local IP address — full control and configuration without the app and without the cloud.
Every Shelly device has a built-in web interface that runs on the device itself, reachable at its local IP address. It needs no app, no account, and no internet connection — just your phone or computer being on the same network (or, during initial setup, connected directly to the device's own Wi-Fi). This is verified against Shelly's own web interface guides on kb.shelly.cloud, for both Gen1 and Gen2+ devices.
Finding the IP address
| Method | How |
|---|---|
| During initial setup | Right after the device connects to your Wi-Fi, a link with the new IP address appears directly on the configuration page — paste it into your browser. |
| Via the app | Open the device → Settings → Device Information. This shows the device's IP, and you can jump straight to the web interface from there. |
| Via the router | Your router's admin interface lists connected devices with their assigned IP — Shelly devices usually show up under their device name. |
| Shelly Device Finder | A standalone desktop tool from Shelly that lists every Shelly device on the network along with its IP address. |
| Universal address during pairing | As long as the device is in its own access-point mode (e.g. right after first power-up), it's always reachable at 192.168.33.1. |
When a device is listed as offline in the app (for example if cloud is turned off or the network changed), the router's device list or Device Finder is often the only way to locate it again.
What you can do in the interface
The web interface isn't a stripped-down version of the app — it's the full configuration surface, and some settings only exist here:
- Control. Turn on/off, see the current state, the same basic function as in the app.
- Inputs and outputs. Choose input mode (button, switch, analog), output type (toggle, momentary, edge, detached) and what the output should do after a power outage.
- Network. Wi-Fi (up to two networks with failover), access point, Bluetooth, static IP where supported, and on Pro devices Ethernet.
- Schedules and timers. Basic schedules (time, sunrise/sunset) and, on Gen2+, advanced cron-based schedules.
- Actions/webhooks. URLs called on events — button presses, output on/off, and similar.
- Firmware. Check, download and install updates, or upload custom firmware manually.
- Cloud connection. Turn the cloud on or off per device, right here.
- MQTT. Enable and configure a connection to an MQTT broker.
- Security. Set a password for access to the web interface itself, factory reset, reboot.
On Gen2+ devices (Plus, Pro, Gen3, Gen4) an entire extra layer is added:
- Scripts. Custom automations written in JavaScript, running locally on the device — no cloud needed.
- KVS (Key-Value Storage). Simple key-value storage on the device, up to 50 pairs, readable and writable by scripts.
- Dynamic components. Virtual Boolean, Number, Text, Enum and Button components usable in automations.
- BTHome. Pairing with Bluetooth devices, including Shelly's own BLU sensors.
- KNX. Integration with KNX building automation.
- MQTT with SSL, RPC over UDP, and outbound WebSocket, in addition to basic MQTT.
Gen1 vs Gen2+
| Gen1 | Gen2+ (Plus/Pro/Gen3/Gen4) | |
|---|---|---|
| Core approach | URL/webhook-driven ("I/O URL Actions") | RPC-based API |
| Scripts | Not available | JavaScript, runs locally |
| MQTT | Yes, but enabling MQTT disables cloud control at the same time | Yes, with SSL, works alongside cloud |
| KVS, BTHome, KNX | Not available | Available |
| Schedules | Basic (time/sun) | Basic + advanced (cron) |
| Address during pairing | 192.168.33.1 |
192.168.33.1 |
Gen1 is built on an older, simpler interface where automation happens through URLs called from outside or by the device itself. Gen2 and later replaced that with an RPC-based API and added local scripting, which is the single biggest practical difference if you want to build your own automations without the cloud or third-party tools.
Local interface isn't the same thing as local control
Being able to reach the web interface locally doesn't automatically mean the cloud is off — the two are independent. You can have the cloud turned on and still control the device locally through the interface, or turn the cloud off entirely and run purely local. See Cloud or local for what that difference means in practice, including what stops working in the app if you turn the cloud off.