Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Robin-Se opened this issue Feb 27, 2024 · 4 comments
Open

Comments

@Robin-Se
Copy link

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:

  • Shelly device(s): Shelly 1 PM
  • Plugin version: v0.19.1 (together with Homebridge Shelly Ng v1.6.0)
  • Device running homebridge: Raspberry Pi (Raspbian GNU/Linux Bullseye (11), Node.js v20.11.1)
@martijndierckx
Copy link

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
Copy link

tbrune0362 commented Apr 6, 2024

Also dealing with the same problem with a Shelly 1.

@Robin-Se
Copy link
Author

Robin-Se commented Apr 6, 2024 via email

@martijndierckx
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants