Replies: 1 comment
|
Okay, looks like my second issue is discussed here, with a possible solution: https://community.shelly.cloud/topic/14977-input-button-binding-in-200/ EDIT: Actually, setting this value to 2 seems to have set both to toggle mode. Yay!
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Hi,
To make my Zigbee setup more resilient in case of Home Assistant or Z2M being down, I am trying to get all lights and switches connected via direct binding wherever this is possible.
I was very happy to get my Shelly 1 (PM) Gen 4 updated to Firmware version 2 for this purpose. Unfortunately, I have two issues:
Also, they are triggered via door and motion sensors, through HA. Using the switches to toggle the bound light normally does not work when it was triggered via a Home Assistant automation before. I believe the Shelly send "on" or "off" in alternating sequence, no matter the current state of the light. After the light was switched on via an automation, I have to flip the switch twice. I built an automation that checks if the lights reacted to a switch toggle, and if not, does it via the automation. It works. However, it looks like the automation always wants to fire twice - and in the Zigbee logs it looks like the Shelly actually sends the command twice:
Could the issue have something to do with the binding? Is the command sent twice because I bound the Shelly to both the Coordinator and the Light?
Only "input_1_off". I guess this second issue might be a firmware thing?
All reactions