Hello,
Here is one of the two scenes that do not work in real life, although it works when using the « start » button (sent via Telegram, which I use for scene debugging).
When you click on the « on » part of the switch, it is supposed to trigger the scene that turns on a light.
(The other scene is the opposite.)
But it doesn’t work. The value (on/off) is correctly sent to the Zigbee key (state change seen in gladys8080).
Thanks in advance,
So it’s equal to « on » not 1, right?
I would say yes except that « device state change » only accepts numerical values in the field to fill in. (impossible to save)
« An error occurred while saving your scene. Please check that all actions / triggers are filled in and correct. »
The « device state change » interface should be like the motion detector RTCGQ11LM (which has ON and OFF checkboxes to click)
If I am told where to change in gladys via command line, no problem.
The problem is right there, it’s not just a switch
Its possible values are on, off, brightness_move_down, brightness_move_up, brightness_stop
But Gladys sees it as binary.
I need to dig a bit, I don’t have an immediate solution for you.
The Zigbee2mqtt integration needs to perform a conversion and on the Gladys side, there needs to be development in the UI to support a dropdown with the different values 
No problem. Personally, I only need the on/off.
You will have the same issues with this one too, if not worse as it has more functions.
Why not split the functions in « devices » of zigbee2mqtt. We would choose if we want the brightness behavior or not (not by default)
simulated_brightness: Set totrueto simulate abrightnessvalue (default:false). If this device provides abrightness_move_uporbrightness_move_downaction it is possible to specify the update interval and delta. This can be done by instead of specifyingtrue:For the brightness part, it’s a new feature as each pulse would add +1 or -1 to the current brightness value (if managed)
