Philips Hue Tap Dial Switch fires multiple events

Hello,

I have 3 Philips Hue Tap Dial Switches to manage some lights. Since a while I notice that all switches have the same problem. A short press on one of the buttons fires the same event multiple times. I noticed it by using the development tool and listen to the events.

In this moment I can’t manage my lights anymore. They go very fast on and off (because of the multiple events). Has somebody the same problem or has a solution?

I don’t see this issue on mine.

Which zigbee integration are you using, and can you paste what events are being sent when you do a single press?

I use Deconz. Now version 7.0.0. But with the previous version was the same problem.

In the development tools this happens with short press button 1:

Event 0:

event_type: deconz_event
data:
  id: switch_6
  unique_id: 00:17:88:01:0d:d0:9d:aa
  event: 1000
  device_id: d507b40af72bf396e1335bb15ba42d92
origin: LOCAL
time_fired: "2024-10-18T19:02:12.778657+00:00"
context:
  id: 01JAGG4GHAPSHPJ3XERN1KG843
  parent_id: null
  user_id: null

Event 1:

event_type: deconz_event
data:
  id: switch_6
  unique_id: 00:17:88:01:0d:d0:9d:aa
  event: 1000
  device_id: d507b40af72bf396e1335bb15ba42d92
origin: LOCAL
time_fired: "2024-10-18T19:02:12.787643+00:00"
context:
  id: 01JAGG4GHKJ390ZNX4WKVV8YGH
  parent_id: null
  user_id: null

Event 2:

event_type: deconz_event
data:
  id: switch_6
  unique_id: 00:17:88:01:0d:d0:9d:aa
  event: 1002
  device_id: d507b40af72bf396e1335bb15ba42d92
origin: LOCAL
time_fired: "2024-10-18T19:02:12.876575+00:00"
context:
  id: 01JAGG4GMCPX83TDBZ27BZFZQE
  parent_id: null
  user_id: null

Event 3:

event_type: deconz_event
data:
  id: switch_6
  unique_id: 00:17:88:01:0d:d0:9d:aa
  event: 1002
  device_id: d507b40af72bf396e1335bb15ba42d92
origin: LOCAL
time_fired: "2024-10-18T19:02:12.878924+00:00"
context:
  id: 01JAGG4GMEADWDZ77K35TW5CDT
  parent_id: null
  user_id: null

Sorry, I’m familiar with Z2M & ZHA but not Deconz.

Maybe there is some kind of debounce setting you can change? Otherwise, it might be a good idea to post in issue in the deconz github page and report this.