Shelly Gen1
@tritter/homebridge-shelly · v0.22.0
Adds first-generation Shelly relays, dimmers, bulbs, sensors and energy meters to HomeKit.
What it says it supports
Brands
- Shelly
Devices it names
- Shelly 1
- Shelly 1L
- Shelly 1PM
- Shelly 1AddOn
- Shelly 2
- Shelly 2.5
- Shelly 3EM
- Shelly 4Pro
- Shelly Air
- Shelly Bulb
- Shelly Button 1
- Shelly Dimmer
- Shelly Dimmer 2
- Shelly Door/Window
- Shelly Duo
Shows up in Apple Home as from its README
- Lights
- Outlets
- Switches
- Buttons and Remotes
- Thermostats
- Windows and Coverings
- Garage Door Openers
- Sensors
- Valves
Sensor readings in its code
What people report
Most Gen1 Shelly relays, dimmers and sensors work, with CoAP multicast network issues the usual problem. Gen2 (Pro) devices and newer models are unrecognized in the legacy plugin and Homebridge 2.0 support is pending.
- Works4
- Partly works4
- Requested2
- Won’t be supported2
| Device | Status | What they said | Source |
|---|---|---|---|
| Shelly Button 1 | Works | Short, long and double press supportedSaved copyType: SHBTN-1 CoAP description: "{\"blk\":[{\"I\":1, \"D\":\"sensors\"}],\"sen\":[{\"I\":77, \"D\":\"battery\", \"T\":\"B\", \"R\":\"0/100\", \"L\":1}{\"I\":118,\"T\":\"S\",\"D\":\"Input\",\"R\":\"0\",\"L\":1},{\"I\":119,\"T\":\"S\",\"D\":\"Input event\",\"R\":\"S/SS/SSS/L\",\"L\":1},{\"I\":120,\"T\":\"S\",\"D\":\"Input event counter\",\"R\":\"U16\",\"L\":1}]}" CoAP status: "{\"G\":[[0,77,100][0,118,0],[0,119,\"S\"],[0,120,1]]}" HTTP Settings:: … Excerpt saved from GitHub on 2026-10-22. | Issue #131 · 2020-06 |
| Shelly Dimmer | Works | Works perfectly with the plugin.Saved copyShelly Plus 2PM not showing up in Homebridge (Docker) – what am I doing wrong? Hello everyone, I have an issue with my Homebridge installation in Docker, where I want to integrate two Shelly devices: Shelly Dimmer (works perfectly using the plugin @tritter/homebridge-shelly) Shelly Plus 2PM, which does not appear in the Homebridge UI. My setup: I use Homebridge in a Docker container via Synology NAS. For the Shelly Plus 2PM, I use the plugin homebridge-shelly-ng. My current config.json (excerpt for Shelly Plus 2PM) looks like this: json Kopieren Bearbeiten { "platform": "ShellyNG", "name": … Excerpt saved from Arctic Shift Reddit archive on 2026-10-22. | Reddit thread · 2025-03 |
| Shelly Dimmer 2 | Works | Support added via merged PRSaved copyadded support for Shelly Dimmer 2 Excerpt saved from GitHub on 2026-10-22. | PR #135 · 2020-06 |
| Shelly Motion | Works | Support added via merged PRSaved copy> > homebridge no longer detects shelly motion on fw v1.1.0 > > > Have you entered something in Internet & Security, CoIoT, Remote address in Shelly Motion web UI? I don‘t think the Shelly can be detected by the plugin anymore as multicast has been disabled in 1.1.0 tried with and without homebridge IP. Makes no differance. You are right, same for me... so Shelly Motion 1.1.0 no longer work for this plugin. Excerpt saved from GitHub on 2026-10-22. | PR #268 · 2021-02 |
| Shelly 1, 2.5 and Dimmer 2 (Hoobs) | Partly works | EHOSTUNREACH loading settings; fixes were dual WAN off or auth changeSaved copyDescribe the bug Plugin finds the Shellys, but states cant be set Log output 22/06/2021, 21:45:32HOOBSShellyERRORFailed to load device settings 22/06/2021, 21:45:32HOOBSShellyERRORError: connect EHOSTUNREACH 192.168.0.27:80 (device SHSW-1 25A2CB, at 192.168.0.27) 22/06/2021, 21:45:36HOOBSShellyERRORFailed to load device settings 22/06/2021, 21:45:36HOOBSShellyERRORError: connect EHOSTUNREACH 192.168.0.70:80 (device SHSW-25 40F5202A70DE, at 192.168.0.70) 22/06/2021, 21:45:36HOOBSShellyERRORFailed to load device settings 22/06/2021, 21:45:36HOOBSShellyERRORError: connect EHOSTUNREACH … Excerpt saved from GitHub on 2026-10-22. | Issue #319 · 2021-06 |
| Shelly 1PM | Partly works | Can turn on but not off for some users; cause was dead units or IGMPSaved copyDescribe the bug All my Shelly 1 PM devices have been behaving strangely for a few days now: I can activate them, but it's not possible to deactivate them. With the shelly app, everything works fine. Log output Nothing in the log: ^[[37m[27.2.2024, 12:55:22]^[[0m ^[[36m[HB Supervisor]^[[0m OS: Linux 6.1.74-v7+ arm ^[[37m[27.2.2024, 12:55:22]^[[0m ^[[36m[HB Supervisor]^[[0m Node.js v20.11.1 /opt/homebridge/bin/node ^[[37m[27.2.2024, 12:55:22]^[[0m ^[[36m[HB Supervisor]^[[0m Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge ^[[37m[27.2.2024, 12:55:22]^[[0m ^[[36m[HB … Excerpt saved from GitHub on 2026-10-22. | Issue #467 · 2024-02 |
| Shelly 2 / 2.5 roller shutter | Partly works | HomeKit position can desync from device; workaround with delayed pollingSaved copyThis plugin actually uses the REST API to get the current roller shutter position. I think the Shellies will start reporting their positions over CoAP in the next firmware update, but so far what is transmitted is just the states of the relays. I’ve used this to determine if the roller shutter is stopped (no relay is active) or if it is moving (one of the relays is active). Whenever the states of the relays change the API is queried to get the current position, which means that the API is queried once when the shutter starts moving and once when it stops moving. So if the position in the Home … Excerpt saved from GitHub on 2026-10-22. | Issue #12 · 2019-02 |
| Shelly Dimmer | Partly works | Fails to switch off after firmware beta; others traced to power supplySaved copyHomeKit with home bridge being its hub docent switch off the shelly dimmer after it is updated to Shelly's Beta RC5. switching on and dimming works fine Excerpt saved from GitHub on 2026-10-22. | Issue #287 · 2021-03 |
| Shelly 0-10V dimmer | Requested | New device request, still openSaved copyWe have ordered a new device from Shelly 0-10, but we cannot yet read it within the Homey system. This can be uploaded in the Shelly app. However, this does not extend to the Homey environment. Is this known to you? Excerpt saved from GitHub on 2026-10-22. | Issue #452 · 2023-11 |
| Shelly 1AddOn | Requested | Thermostat support PR still openSaved copyAs many and myself would like to have a thermostat I created one based on the shelly actions therefore the MR of https://github.com/alexryd/node-shellies/pull/30 required. To install and test, (you may need to re-add your shelly): `sudo npm i -g @tritter/homebridge-shelly` Shelly 1AddOn configurations *Applies to Shelly 1, 1PM* `"sensors"` - 1-3, number of sensors connected to the addon. (default:1 , max: 3) `"type"` - when the relais should act like a thermostat set the type to `"thermostat"` `"humidity"` - false, shows humitidy (only applicable to one sensor) `"heating"` - true|false, … Excerpt saved from GitHub on 2026-10-22. | PR #336 · 2021-09 |
| Samsung TV (mis-detected as Shelly) | Won’t be supported | TVs speak CoAP and show as unsupported Shelly; maintainer to excludeSaved copyfor me it is a samsung tv Excerpt saved from GitHub on 2026-10-22. | Issue #139 · 2020-06 |
| Shelly Pro 4PM | Won’t be supported | Unknown device model; plugin fails to add itSaved copyhi, i install the plug in in my hoobs but I see the error in object. Can you help me? 23/08/2024, 20:53:25Shelly Ng BridgeShellyNGERRORFailed to add discovered device (id: shellypro4pm-08f9e0ea14d8): shutting down in 1897 ms 23/08/2024, 20:54:15Shelly Ng BridgeShellyNG[shellypro4pm-08f9e0ea14d8] Unknown device of model "SPSW-104PE16EU" discovered. 23/08/2024, 21:03:16Shelly Ng BridgeConfiguration change 23/08/2024, 21:03:16shellyngbridge stopping 23/08/2024, 21:03:21Shelly Ng Bridge starting 23/08/2024, 21:03:24Shelly Ng BridgeLoaded plugin 'homebridge-shelly-ng' 23/08/2024, 21:03:24Shelly Ng … Excerpt saved from GitHub on 2026-10-22. | Issue #481 · 2024-08 |
Gathered from the plugin’s GitHub issues, pull requests, discussions, wiki and docs, and from r/homebridge. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local
Shelly HTTP/CoIoT over LAN
You’ll need
- Shelly Gen1 device
Compatibility
| Verified by Homebridge | No |
|---|---|
| Homebridge versions | ^1.11.0 || ^2.0.0 |
| Homebridge 2.0 | Yes |
| Node.js | >=18.20.0 |
| Settings in Homebridge UI | Yes |
| Matter | No |
| Platform name | Shelly |
| License | MIT |
Community signals
| Downloads a week | 26 |
|---|---|
| Downloads a month | 172 |
| GitHub stars | 303 |
| Open issues | 245 |
| Closed issues | 221 |
| Last code push | 2023-03-04 |
| Latest version | 0.22.0 (2026-08-26) |
| First published | 2022-07-03 |
| Releases | 8 |
In ReReHome
Whatever this plugin publishes reaches Apple Home as a normal HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Bridges get their own settings page listing the accessories behind them.
Caveats from the README
- Gen2+ devices need homebridge-shelly-ng
- Shelly Motion needs CoIoT remote address set
- Firmware minimums per model
HomeKit services in its code
Found by scanning the published npm package. A plugin can register a service only for some devices.
- Battery
- ContactSensor
- Door
- GarageDoorOpener
- HumiditySensor
- LeakSensor
- LightSensor
- Lightbulb
- MotionSensor
- OccupancySensor
- Outlet
- ServiceLabel
- SmokeSensor
- StatelessProgrammableSwitch
- Switch
- TemperatureSensor
- Thermostat
- Valve
- Window
- WindowCovering



