Open g-mocken opened 1 year ago
Same here! I'm using six Shelly in the "Shelly-NG" Plugin connected to HomeKit. Curious thing: Three of them are unresponsive after about 24h (2x Shelly Plus 2 PM + 1x Shelly Plus i4). The other three (Shelly Plus 2 PM) are working flawless without any issues. I have recognized, that the "Shelly-NG" Plugin adds no log entries to Hombridge log, after the "malfunction" occurs. But the other three Shelly are still working without any issue. awkward :-) All 5 Plus 2 PM have the exact same configuration in Shelly-App and router configuration... Any suggestions or ideas? Homebridge restart solves the "issue" for approx. 24h until Shellys are unresponsive again.
no issues for the last 6 days, but since 60 minutes 3 Shellys are unresponsive again.....
Just want to add, I also keep seeing this: all Gen 2 devices that are talking to Shelly NG seem to be unresponsive after a random amount of time. The buttons in Home app can be toggled, but nothing happens on the actual Shellys, until I restart the homebridge service.
Regular Shelly plugin is perfect, no issues. Only ShellyNG affected.
Same issue after reinstalling home bridge
Seems from the releases page that this plugin as well as the original homebridge-Shelly by the same author are abandoned. 🙁 If anyone knows a good alternative that is still actively maintained, feel free to post it?
i tried to use home assistant but there is no auto device discovery and IPs need to be static, so i moved back to home bridge. However all my devices stop working after a while. Im really waiting for matter to come out. btw what other plugin do you use for your plus 1 pm? this https://github.com/alexryd/homebridge-shelly#readme ?
The other plugin you linked is for Shellly 1st gen devices, like the Shelly 1PM (w/o Plus).
I had the same with a Shelly Plus 1 PM with Shelly Plus Addon and temperature sensor DS18B20 becoming unresponsive after some undefined time (hours, a day). Additionally I noticed a 'connection lost' and a "reconnection after 5 s' in the homebridge log before each unresponsive behavier. I raised the websocket 'request timout' to 120 s and 'Ping interval' to 180 s in the Shelly ng plugin No more 'connection lost' in the homebridge log seen since that. No unresponsive behavier any more. Seems that solved it. Bye, DS from Ger
Editing: Sorry, no solution. After 2 weeks it happened again, same behavier.
I have several Shelly 1 via another plugin, but just a single Shelly Plus1 using this "shelly-ng" plugin, and it is only this last one which becomes unresponsive after a day or two. There is no entry in the homebridge (1.6.0) log. I can temporarily cure the issue by either toggling the state on the Shelly's own local web page or by restarting homebridge. But then after a while it is back.