You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The actions for each button in Z2M are (where <button> is a button no like 1_single):
<button>_single
<button>_double
<button>_hold
These all show up correctly in Z2M however in HASS the events for hold specifically do not contain the button number, only the text "hold".
So when clicking button 1 once the event in both is "1_single", when double clicking it its "1_double", but when holding it its "1_hold" in Z2M but "hold" in HASS when means I can't disambiguate which button was actually held.
What did you expect to happen?
When holding a button I expect to know which button was held in the event.
Have a look at the other attributes (besides event_type). Not all possible action values are parsed in the current experimental implementation, the fallback is to just put everything in event_type.
What happened?
Using the experimental support in #24233.
I have a four button scene switch https://www.zigbee2mqtt.io/devices/TS0044.html#tuya-ts0044.
The actions for each button in Z2M are (where
<button>
is a button no like 1_single):<button>_single
<button>_double
<button>_hold
These all show up correctly in Z2M however in HASS the events for hold specifically do not contain the button number, only the text "hold".
So when clicking button 1 once the event in both is "1_single", when double clicking it its "1_double", but when holding it its "1_hold" in Z2M but "hold" in HASS when means I can't disambiguate which button was actually held.
What did you expect to happen?
When holding a button I expect to know which button was held in the event.
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.42.0 commit: 861cba6
Adapter firmware version
7.4.2 [GA]
Adapter
TubesZB MGM21
Setup
x86-64 Docker
Debug log
No response
The text was updated successfully, but these errors were encountered: