Hardware setup procedures for field installers — keep this page open or print it out
Before you start: Register the property on the platform and create rooms for each occupied space. The app will generate a unique webhook URL for each Shelly EM — you need this during setup. Get the MQTT broker credentials from the admin panel before going on site.
shellyem3g-AABBCC). Tap Register — the app will generate a webhook URL for you. Copy it.192.168.33.1.The script runs entirely on the Shelly. It does not require port-forwarding, local servers, or a Shelly Cloud account. The only requirement is outbound HTTPS access from the property's internet connection.
Gen 3 only: Only Shelly EM Gen 3 devices are supported. Gen 1 / Gen 2 devices use a different API and are not compatible with the current platform.
192.168.4.1.192.168.4.1. You'll see the SLZB-06 dashboard. Default credentials (if prompted): admin / admin.| SLZB-06M Field | Value source | Notes |
|---|---|---|
| Server/Host | From app → MQTT Settings | Broker hostname or IP |
| Port | 1883 (or 8883 for TLS) | Use TLS if broker requires it |
| Username | From app → MQTT Settings | Property-specific credential |
| Password | From app → MQTT Settings | Property-specific credential |
| Base topic | From app → MQTT Settings | e.g. myhome/gw/abc123 |
Tap the copy icon next to each value in the app to avoid typos. After saving MQTT settings, the gateway status in the app should turn Online within 30 seconds.
Gateway must be online first. Do not attempt to pair sensors until the SLZB-06M gateway is registered and showing as Online in the app. Sensors pair within ~10–15 m of the gateway (line of sight).
Do not just tap the button — it must be a sustained hold until the 3× blink pattern appears. If the LED blinks once and stops, the battery may need replacing or the sensor is already joined to a network (factory reset it first).
| Symptom | Likely cause | Fix |
|---|---|---|
| Shelly: "No readings received" | Script not saved / not toggled On | In Shelly web UI → Scripts, confirm the script exists and its toggle is On. Wait a full 60 seconds and check again. |
| Shelly: "No readings received" (continued) | Shelly not on property WiFi | Confirm the Shelly has a valid IP on the property network. AP mode (192.168.33.1) means it hasn't joined WiFi yet. |
| Gateway: status stays Offline | Wrong MQTT credentials or broker unreachable | Double-check all 5 MQTT fields (host, port, username, password, base topic) — copy from the app one at a time. Confirm the broker is running (ask admin). Check port 1883/8883 is not blocked by the property router. |
| Gateway: can't open 192.168.4.1 | Not connected to the SLZB-06M AP | Reconnect your phone to the "SLZB-06M" WiFi network. Disable mobile data if your phone switches automatically. |
| Sensor: not detected in 60 s | Button not held long enough | Hold the button for at least 3–5 seconds until you see 3× rapid blinks. A single blink means it wasn't long enough. |
| Sensor: not detected in 60 s (continued) | Sensor too far from gateway | Move the sensor within 5 m of the gateway to pair, then reposition it. Zigbee mesh extends range through other paired devices. |
| Sensor: not detected in 60 s (continued) | Sensor already joined to another network | Factory reset the sensor: hold the button for 10+ seconds until rapid multi-blink. Then retry pairing. |
| App: "Gateway not found" | Gateway changed IP after WiFi reconnect | Check the new IP in your router's DHCP table or the gateway web UI. The app uses the gateway's ID, not its IP — this should resolve automatically once the gateway reconnects to MQTT. |
If you can't resolve an issue on site, contact your platform administrator with the device's ID, property name, and a screenshot of the error in the app. Do not attempt to factory reset the gateway unless instructed.