alexryd / homebridge-shelly

Homebridge plugin for Shelly devices
MIT License
297 stars 44 forks source link

Shelly 1L loses connection #227

Open DerDirsch opened 3 years ago

DerDirsch commented 3 years ago

The Shelly does not switch approx once a day. The device is not reacting on HomeKit nor in Homebridge. I need to restart my Homebridge manually and than it works again for a while

DerDirsch commented 3 years ago

I have the feeling that happens when Shelly is switched on for a longer time approx 1h. (E.g. during morning routine)

produdegr commented 3 years ago

With all due respect, this issue is an Altereco Robotics issue and not Shelly Homebridge plugin issue. I read on the Shelly site that you must have at least 20 watt load on the switch for it to function, or must install a parallel load (they call it "bypass"). Also a beta firmware is solving some issues people have. Hope this helps

DerDirsch commented 3 years ago

Hi, Actually I have more than 20W load behind the Shelly and the device seem to work fine. I just checked the log from Homebridge. I receive error messages like to many asynchronous activities. Could thus be a reason?

alexryd commented 3 years ago

Can you post the error message?

DerDirsch commented 3 years ago

I can't find a clear error which fits to the Shelly plugin, as far as I can see. However Shelly is the only device which is not reacting in my morning HomeKit routine. at this point the button does not work in HomeKit nor in Homebridge but I can switch the Shelly from its Webinferface, thus it is fine. Unfortunately the unofficial HomeKit firmware does not load either.

This is my log after the morning 3.00 hr Cron job and 6:07 manual reboot. Afterwards the Shelly works in Homeriden and HomeKit fine.

[12/14/2020, 03:00:59] Homebridge v1.2.4 is running on port 51826. [12/14/2020, 03:30:28] [My Tahoma] Login TaHoma server... [12/14/2020, 04:00:28] [My Tahoma] Login TaHoma server... [12/14/2020, 04:30:28] [My Tahoma] Login TaHoma server... [12/14/2020, 05:00:28] [My Tahoma] Login TaHoma server... [12/14/2020, 05:30:28] [My Tahoma] Login TaHoma server... [12/14/2020, 06:00:28] [My Tahoma] Login TaHoma server... [12/14/2020, 06:04:38] [My Tahoma] [Schlafzimmer] setClosure[0] [12/14/2020, 06:04:38] [My Tahoma] [Esszimmer] setClosure[0] [12/14/2020, 06:04:38] [My Tahoma] [Wohnzimmer] setClosure[0] [12/14/2020, 06:04:38] [My Tahoma] undefined [12/14/2020, 06:04:38] [My Tahoma] Listener registered 5fa2e180-ac10-3401-3e13-8d523bd30413 [12/14/2020, 06:04:39] [Shelly] Failed to set relay0 [12/14/2020, 06:04:39] [Shelly] Error: connect EHOSTUNREACH 192.168.1.117:80 (device SHSW-L 84CCA8AD2326, at 192.168.1.117) [12/14/2020, 06:05:05] [My Tahoma] [Schlafzimmer] setClosure COMPLETED [12/14/2020, 06:05:05] [My Tahoma] [Esszimmer] setClosure COMPLETED [12/14/2020, 06:05:05] [My Tahoma] [Wohnzimmer] setClosure COMPLETED [12/14/2020, 06:07:15] [Homebridge UI] Homebridge restart request received [12/14/2020, 06:07:16] [Homebridge UI] Executing restart command: sudo -n systemctl restart homebridge homebridge : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart homebridge pam_unix(sudo:session): session opened for user root by (uid=0) Stopping Node.js HomeKit Server... [12/14/2020, 06:07:16] Got SIGTERM, shutting down Homebridge... homebridge.service: Main process exited, code=exited, status=143/n/a homebridge.service: Failed with result 'exit-code'. Stopped Node.js HomeKit Server. homebridge.service: Found left-over process 478 (homebridge-conf) in control group while starting unit. Ignoring. This usually indicates unclean termination of a previous run, or service implementation deficiencies. homebridge.service: Found left-over process 3177 (sh) in control group while starting unit. Ignoring. This usually indicates unclean termination of a previous run, or service implementation deficiencies. homebridge.service: Found left-over process 3178 (sudo) in control group while starting unit. Ignoring. This usually indicates unclean termination of a previous run, or service implementation deficiencies. homebridge.service: Found left-over process 3185 (systemctl) in control group while starting unit. Ignoring. This usually indicates unclean termination of a previous run, or service implementation deficiencies. Started Node.js HomeKit Server. pam_unix(sudo:session): session closed for user root [12/14/2020, 06:07:22] Loaded config.json with 4 accessories and 3 platforms. [12/14/2020, 06:07:22] --- [12/14/2020, 06:07:22] Loaded plugin: homebridge-config-ui-x@4.36.0 [12/14/2020, 06:07:22] Registering platform 'homebridge-config-ui-x.config' [12/14/2020, 06:07:22] --- [12/14/2020, 06:07:23] Loaded plugin: homebridge-http-switch@0.5.31 [12/14/2020, 06:07:23] Registering accessory 'homebridge-http-switch.HTTP-SWITCH' [12/14/2020, 06:07:23] --- [12/14/2020, 06:07:23] Loaded plugin: homebridge-shelly@0.16.0 [12/14/2020, 06:07:23] Registering platform 'homebridge-shelly.Shelly' [12/14/2020, 06:07:23] --- [12/14/2020, 06:07:23] Loaded plugin: homebridge-tahoma@0.3.51 homebridge-tahoma API version: 2.6 [12/14/2020, 06:07:23] Registering platform 'homebridge-tahoma.Tahoma' [12/14/2020, 06:07:23] --- [12/14/2020, 06:07:23] Loading 3 platforms... [12/14/2020, 06:07:23] [Config] Initializing config platform... [12/14/2020, 06:07:23] [Config] Spawning homebridge-config-ui-x with PID 3209 [12/14/2020, 06:07:23] [Shelly] Initializing Shelly platform... [12/14/2020, 06:07:23] [My Tahoma] Initializing Tahoma platform... [12/14/2020, 06:07:23] [My Tahoma] Fetch accessories... [12/14/2020, 06:07:23] [My Tahoma] Login TaHoma server... [12/14/2020, 06:07:23] Loading 4 accessories... [12/14/2020, 06:07:23] [ZAPPING] Initializing HTTP-SWITCH accessory... [12/14/2020, 06:07:23] [ZAPPING] Switch successfully configured... [12/14/2020, 06:07:23] [Kanal ARD] Initializing HTTP-SWITCH accessory... [12/14/2020, 06:07:23] [Kanal ARD] Switch successfully configured... [12/14/2020, 06:07:23] [Kanal ZDF] Initializing HTTP-SWITCH accessory... [12/14/2020, 06:07:23] [Kanal ZDF] Switch successfully configured... [12/14/2020, 06:07:23] [Kanal WDR] Initializing HTTP-SWITCH accessory... [12/14/2020, 06:07:23] [Kanal WDR] Switch successfully configured... [12/14/2020, 06:07:23] [Shelly] 1 accessory loaded from cache [12/14/2020, 06:07:24] [Shelly] Admin server is running on port 8181 [12/14/2020, 06:07:24] [My Tahoma] Unable to refresh states (not logged in) [12/14/2020, 06:07:24] [My Tahoma] [HOMEKIT (stack)] type: ProtocolGateway > HomekitStack, protocol: homekit [12/14/2020, 06:07:24] [My Tahoma] No definition found for ProtocolGateway > HomekitStack in mapping.json file [12/14/2020, 06:07:24] [My Tahoma] [Alarm] type: Alarm > TSKAlarmController, protocol: internal [12/14/2020, 06:07:24] [My Tahoma] Device Alarm ignored [12/14/2020, 06:07:24] [My Tahoma] [Aanraakgevoelige knop] type: Pod > Pod, protocol: internal [12/14/2020, 06:07:24] [My Tahoma] No definition found for Pod > Pod in mapping.json file [12/14/2020, 06:07:24] [My Tahoma] [IO (13524151)] type: ProtocolGateway > IOStack, protocol: io [12/14/2020, 06:07:24] [My Tahoma] No definition found for ProtocolGateway > IOStack in mapping.json file [12/14/2020, 06:07:24] [My Tahoma] [Wohnzimmer] type: RollerShutter > PositionableRollerShutterUno, protocol: io [12/14/2020, 06:07:24] [My Tahoma] Instanciate Wohnzimmer as WindowCovering [12/14/2020, 06:07:24] [My Tahoma] [Esszimmer] type: RollerShutter > PositionableRollerShutterUno, protocol: io [12/14/2020, 06:07:24] [My Tahoma] Instanciate Esszimmer as WindowCovering [12/14/2020, 06:07:24] [My Tahoma] [Kinderzimmer] type: RollerShutter > PositionableRollerShutterUno, protocol: io [12/14/2020, 06:07:24] [My Tahoma] Instanciate Kinderzimmer as WindowCovering [12/14/2020, 06:07:24] [My Tahoma] [Schlafzimmer] type: RollerShutter > PositionableRollerShutterUno, protocol: io [12/14/2020, 06:07:24] [My Tahoma] Instanciate Schlafzimmer as WindowCovering [12/14/2020, 06:07:24] [My Tahoma] [OGP KNX Bridge] type: ProtocolGateway > DynamicBridge, protocol: ogp [12/14/2020, 06:07:24] [My Tahoma] No definition found for ProtocolGateway > DynamicBridge in mapping.json file [12/14/2020, 06:07:24] [My Tahoma] [OGP Siegenia Bridge] type: ProtocolGateway > DynamicBridge, protocol: ogp [12/14/2020, 06:07:24] [My Tahoma] No definition found for ProtocolGateway > DynamicBridge in mapping.json file [12/14/2020, 06:07:24] [My Tahoma] [OGP Yeelight Bridge] type: ProtocolGateway > DynamicBridge, protocol: ogp [12/14/2020, 06:07:24] [My Tahoma] No definition found for ProtocolGateway > DynamicBridge in mapping.json file [12/14/2020, 06:07:24] [My Tahoma] [OGP Intesis Bridge] type: ProtocolGateway > DynamicBridge, protocol: ogp [12/14/2020, 06:07:24] [My Tahoma] No definition found for ProtocolGateway > DynamicBridge in mapping.json file [12/14/2020, 06:07:24] [My Tahoma] [Sonos PLAY:1] type: MusicPlayer > MediaRenderer, protocol: upnpcontrol [12/14/2020, 06:07:24] [My Tahoma] Device Sonos PLAY:1 ignored [12/14/2020, 06:07:24] [My Tahoma] [Sonos PLAY:1] type: MusicPlayer > MediaRenderer, protocol: upnpcontrol [12/14/2020, 06:07:24] [My Tahoma] Device Sonos PLAY:1 ignored [12/14/2020, 06:07:24] Initializing platform accessory 'Schlafzimmer'... [12/14/2020, 06:07:24] Initializing platform accessory 'Kinderzimmer'... [12/14/2020, 06:07:24] Initializing platform accessory 'Esszimmer'... [12/14/2020, 06:07:24] Initializing platform accessory 'Wohnzimmer'... Setup Payload: X-HM://0023ISYWY6NCI

alexryd commented 3 years ago

Error: connect EHOSTUNREACH 192.168.1.117:80 (device SHSW-L 84CCA8AD2326, at 192.168.1.117)

So homebridge can't connect to your Shelly device over HTTP. Perhaps it's offline? Something blocking the connection?

DerDirsch commented 3 years ago

Actually I have no possibilities to check this anymore. The HomeKit Firmware is working now for my device and I have integrated the Shelly directly into HomeKit. thanks for your efforts

geokvant commented 2 years ago

I have same problem on one of my shellys

[5/20/2022, 5:16:10 PM] [Shelly] Failed to set relay1
[5/20/2022, 5:16:10 PM] [Shelly] Error: connect EHOSTUNREACH 192.168.1.160:80 (device SHSW-25 E61882, at 192.168.1.160)

one day or two later shelly loses connect to WiFi network, and few hours later it hangs totally, so stops working even with hard buttons - so I have to power off / power on and for one or two days it works again.

I was thinking that my shelly just starting to glitch, but I've made few tests: 1) I've disconnected it from my WiFi network for a week and relay works as it should in terms of work and availability (was managed directly from iPad connected to it's wifi AP - was available all the time for 7 days) 2) I've connected Shelly to my WiFi network but set it as password protected - so the plugin can't manage it (but can see it online)- again 7 days without any problem.

Have no idea why it goes mad b/c other 10 shellys work just fine 99% of time