search

alexryd / homebridge-shelly

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

Shelly 1 PM devices: Activation possible / deactivation not possible! #467

Open Robin-Se opened 4 months ago

Robin-Se commented 4 months ago

Describe 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 Supervisor]^[[0m UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js ^[[0;37m[27.2.2024, 12:55:30] ^[[0m^[[0;36m[Homebridge UI]^[[0m ^[[0;33mHomebridge UI v4.55.1 is listening on :: port 8581^[[0m ^[[37m[27.2.2024, 12:55:31]^[[0m ^[[36m[HB Supervisor]^[[0m Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution ^[[37m[27.2.2024, 12:55:31]^[[0m ^[[36m[HB Supervisor]^[[0m Started Homebridge v1.7.0 with PID: 5423 ^[[37m[27.2.2024, 12:55:34] ^[[39mLoaded config.json with 0 accessories and 3 platforms. ^[[37m[27.2.2024, 12:55:34] ^[[39mLoaded 20 cached accessories from cachedAccessories. ^[[37m[27.2.2024, 12:55:34] ^[[39m--- ^[[37m[27.2.2024, 12:55:34] ^[[39mLoaded plugin: homebridge-shelly@0.19.1 ^[[37m[27.2.2024, 12:55:36] ^[[39mRegistering platform 'homebridge-shelly.Shelly' ^[[37m[27.2.2024, 12:55:36] ^[[39m--- ^[[37m[27.2.2024, 12:55:36] ^[[39mLoaded plugin: homebridge-shelly-ng@1.6.0 ^[[37m[27.2.2024, 12:55:36] ^[[39mRegistering platform 'homebridge-shelly-ng.ShellyNG' ^[[37m[27.2.2024, 12:55:36] ^[[39m--- ^[[37m[27.2.2024, 12:55:36] ^[[39mLoading 3 platforms... ^[[37m[27.2.2024, 12:55:36] ^[[39m^[[36m[Shelly]^[[39m Initializing Shelly platform... ^[[37m[27.2.2024, 12:55:36] ^[[39m^[[36m[Shelly NG]^[[39m Initializing ShellyNG platform... ^[[37m[27.2.2024, 12:55:36] ^[[39m^[[36m[Shelly]^[[39m 19 accessories loaded from cache Setup Payload: X-HM://0024HH9M280I7 Enter this code with your HomeKit app on your iOS device to pair with Homebridge: ^[[30m^[[47m ^[[49m^[[39m ^[[30m^[[47m ┌────────────┐ ^[[49m^[[39m ^[[30m^[[47m │ 613-85-706 │ ^[[49m^[[39m ^[[30m^[[47m └────────────┘ ^[[49m^[[39m ^[[30m^[[47m ^[[49m^[[39m

Environment:

martijndierckx commented 4 months ago

I'm encountering the exact same thing. I thought it was going to be something very odd, so I'm very happy I'm seeing someone else with the same problem.

Some can be toggle on, but not off. And vice versa.

tbrune0362 commented 3 months ago

Also dealing with the same problem with a Shelly 1.

Robin-Se commented 3 months ago

My problem is „solved“. I had 2 defect Shellys. They responded but died after some days. After replacing them, everything is fine again.

Am 06.04.2024 um 09:42 schrieb tbrune0362 @.***>:

Also dealing with the same problem.

— Reply to this email directly, view it on GitHub https://github.com/alexryd/homebridge-shelly/issues/467#issuecomment-2041005527, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARUWHNXALXIR5E62NMPJN3LY36RNPAVCNFSM6AAAAABD37UARSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGAYDKNJSG4. You are receiving this because you authored the thread.

martijndierckx commented 3 months ago

Mine is solved as well. Turns out IGMP snooping (unifi) + IGMP proxy (pfsense) do not play well with Shellies