I would like to be able to use the Philips Hue Tap Dial Switch (model: RDM002) in Gladys scenes via the Zigbee2MQTT integration.
Observation:
Z2M correctly receives the presses: zigbee2mqtt/Living Room Remote 1 publishes "action":"button_1_press", then "action":"button_1_press_release".
In Gladys, the device is correctly created with a “Button Click” feature, but it has no state in the history. The Battery and Signal Strength features, however, each have over 1,200 states.
A scene triggered on “Button Click” therefore never starts.
Request:
Add in Gladys the actions of this model (button_1 to button_4: press, press_release, hold, hold_release, and if possible the rotation of the dial), as was done for the Hue Dimmer Switch v2 in version 4.74.
Context: Gladys on TrueNAS (Docker), Zigbee2MQTT, Sonoff ZBDongle-E key.
Thanks for the diagnosis, it was spot on: Gladys didn’t recognize any of the Tap Dial actions, so the « Button Click » feature never received any status.
short press (button_N_press_release) → « Button N single click »
long press (button_N_hold_release) → « Button N long click »
In your scene, you’ll just need to choose for example « Button 1 single click » as the trigger.
Gladys only reads button releases. A short press sends press then press_release. A long press sends press, then hold (possibly several times as long as you hold the button), then hold_release. By only reading the releases, each press triggers the scene once, and a long press doesn’t also trigger the short press.
What is not covered: the wheel. It sends a message for each notch, so a scene linked to the rotation would start several times with each gesture. To vary the brightness, the genLevelCtrl binding you’ve already set up in Z2M remains the best solution, as it is much more responsive than a scene.
The fix will be available once the PR has been reviewed and merged into a future version of Gladys. I’ll keep you posted!