Open noworthwhile opened 7 months ago
What's not working currently in HomeKit?
All Action values are exposed. Combining them into a single button will not change the behavior or the events that get triggered.
Five buttons are exposed to HomeKit:
A single press is mapped to button one in HomeKit, then a second single press is mapped to button two. then it goes back to button one, and then two and so on.
Long pressing is mapped to button 4, and then another long press is mapped to button 5. Releasing the long press from either of the two long presses is mapped to button 3.
Mapping the button to turning on and off a connected light with a single short press is not working, as the switch will use either button 1 or 2, depending what was pressed before.
Example:
Is it possible to configure the switch to be only: button 1 : Toggle(ON/OFF), button 2 : Long press?
Thank you for your answer.
For such customization, I would suggest to see if you can handle this particular device with a plugin like homebridge-mqttthing.
It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!
Device Model
NIKO NV; Battery switch, 1 button
Is there an existing issue for this?
Supported by Zigbee2MQTT?
Missing features / functionality
This wireless single button from Niko reports 5 states within Zigbee2mqtt as seen in the following code from the boot up of Homebridge.
`[12/5/2023, 12:22:17 PM] [zigbee2mqtt] Mapping of property 'action' of device 'Niko Wireless button': Button 1 (off):
This shows 5 different buttons within HomeKit.
"Brightness_move_up and _down" are long presses, and button 3 always activates when the long press is ended.
This prevents correct operation within HomeKit
HomeKit Services and Characteristics
Possible to expose a simple "Toggle" and a "Long press" ?
Scenes and automations are not working correctly with the current behaviour
Exposes information from Zigbee2MQTT
Additional information / Other remarks
No response