This driver ge4d / hubitat-code Bundles — Bitbucket has many features supported. Including add-on module.
(switches, dimmers, unbound inputs and button app compatibility, scripts, temperature and humidity sensors, voltmeters, other energy meters)
In short, you can trial it by installing as a bundle trough Hubitat bundles tab.
Hi Dmitry,
I have a Shelly 1 Gen 3 new out of the box. Updated it to latest firmware 20250508-110748/1.6.1-g8dbd358 I have updated your bundle so that I have the latest drivers.
Using your driver I can turn the switch on and off as expected, but the switch status attribute does not change unless I press refresh.
Any ideas?
Thanks, Simon
Looks like this is a Shelly firmware issue......... driver ran fine on a Shelly Plus1, I upgraded the device to latest firmware offered from this device (1.5.1) and now I have the issue. Tried the beta firmware 1.6.0 and it has the same issue.
Hello,
Could you share logs of this device? It looks like websocket connection is not open.
Root device sends 'Refresh' command trough http request. Child devices send 'Refresh' requests trough websocket connection. So you can check if the behavior is the same for root and child devices.
All status updates initiated by device are sent trough websocket connection.
For now it looks like connection is not open (its state should also be reflected by the 'link' attribute and 'healthStatus' [trough helsStatus when going offline waits for continuous failure for the configured time to filter out short disconnections])
Set up a test Plus 1 on firmware 1.5.1 this morning and it's working fine...... now I can't replicate what was happening to me yesterday !!!!! Weird
If it is not reprodicible, I may suspect it weren't reloaded. Or maybe it were 'disconnected'. In disconnected mode driver will not issue reconnection. Yet all http requests will still work (including the 'refresh' from the root device)
Thanks for the log. Looking into the issue.
It looks the same. And it seems like an expected attribute is missing in the device response.
P.S.:
Confirming: the issue is probably comes from the latest firmware. According to documentation status report must contain 'id' attribute. While HTTP response has it, WS events are missing it. Working on a solution..
The bundle is updated.
The missing 'id' attribute issue is mitigated by extracting it from component name instead.
Many many many thanks, I am glad you are still around here. I can confirm the problem is solved by the update, thanks
Many thanks Dmitry
I am running a Shellyplus 1 to remotely control a switch outside of zwave range. It is working, but the state update time is frustrating. The shortest update period I can set is 2 min, which means the controller in the house doesn't send the proper on/off command for 2 min after I turn the lights on or off. Is there a way to decrease the state update? I am using the Shellyplus Generic driver
Did you try the driver from dmitry.rozovik?
You are mentioning zwave range. It is somewhat confusing as shellies are WiFi devices and Gen4 are also zigbee cabable.
For Shelly Plus 1 (WiFi) to get instant status updates you need either my driver (based on websocket connection) or one by Daniel Winks (based on web hooks)
The Shelly wave 1 LR is now available on Amazon and I can tell you the long range works really well on this device. I included a couple at approximately 200’ from the hub.
Download the Hubitat app
