and I am encountering the following problem, the device is correctly recognized in the Zigbee application (IPgladys:8080) with all its functions, but it appears in Gladys with different functions:
No, it’s more twisted than that. First of all, what do you call the interlock? So, there are three buttons controlling the same channel. Two are push buttons, meaning you click on them, they go to state 1 and return to 0 by themselves, and the third one slides by itself when you press the push button (maybe the interlock), like the operation of the button at the top of the dashboard windows.
The big problem is that these buttons control the same channel L1, whereas from the Zigbee interface (IPGladys:8080), and as we can see in the image, there is a state L1 and a state L2. When we activate them, channels L1 and L2 work correctly.
Oops, I missed that, sorry
Indeed, it’s the interlock between the two buttons (useful for roller shutters).
But the problem is L1 and L2
Thanks for your help
The operation of the first button resembles the general button of a window (which has lights inside) declared on the dashboard.
When you click on the second one, it goes to ON and returns to OFF, and it turns the first button to ON, which remains ON.
Same behavior for the third button as for the second button.
Whether you activate the second button or the third button, it’s always L1 that lights up. (bug)
I think that if you activate the first button, it should turn on L1 and L2 at the same time.
I hope that’s clearer
Hello
I looked back at my Xiaomi double relay and found the Interlock button function. This button locks the operation of input L1 relative to input L2, in plain terms when L1 is On, L2 is Off and vice versa (two-state roller shutter operating mode up and down). When the interlock switch is not actuated, L1 and L2 can be controlled independently of each other. In Zigbee2MQTT. It is not visible in the dashboard (shown above), but it is visible in the expose tab
A small clarification:
When I manipulate the Switches on the [Zigbee2MQTT] interface, all functions work, and all status returns on the Gladys dashboard are correct.
So the problem:
When you manipulate the L1 switch on Gladys, the L1 lamp turns on and the status return on [Zigbee2MQTT] is OK.
When you manipulate the L2 switch on Gladys, the switch returns to the Off position and sends the L1 button to ON, the L1 lamp turns on, and the status return [Zigbee2MQTT] acts on L1.
When you act on the Interlock switch on Gladys, it returns to Off and sends the L1 button to ON, L1 turns on, and the status return [Zigbee2MQTT] acts on L1.
Here if it can help
I’m following up on this topic because it is not fully supported by Gladys. Indeed, using it in a scene doesn’t work because the selected device’s turn on/off action uses the first feature of type binary switch. Moreover, even if it is possible to rename the three switches, it’s hard to know which one is the common output, output 1, or output 2.
Hello, @Romuald_Pochet
I don’t have a scene on this device, so I didn’t realize, but that explains why in Google Home you only see the first feature; I thought it was Google that wasn’t taking all the features into account. So I confirm the problem.
Indeed, I had to run tests to locate the features, however all the features work well.
For me it’s a switch like the others (in terms of usage), on one side it prevents setting L1 and L2 to 1 at the same time, in the other position it allows turning on L1 and L2 at the same time.
on my dashboard it looks like this :
![image|396x226](upload://lIf9h9BDUolwbgf1z
Interlock ne « commute » rien au sens Gladys ‹ binary switch ›, c’est juste un paramètre de configuration du device comme on peut voir sur l’interface Zigbee2mqtt.