-
-
Notifications
You must be signed in to change notification settings - Fork 29k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing repeated hue_event for Philips Hue Tap Dial switch #78621
Comments
hue documentation |
Hey there @balloob, @marcelveldt, mind taking a look at this issue as it has been labeled with an integration ( |
Don't close this little bot, we are still there looking for a fix! |
@marcelveldt Can you reopen this issue please? I missed the |
There is a duplicate event filter in the code between aiohue and the hue integration and I think that is the one causing this. I will try to find some time this week to fix it. |
Is there possibly any news on this issue? I've just got the Hue Tap Dial Switch and so far it works quite well in HA. However it indeed does filter out dublicate events, so I have to fire a different event first te retrigger the previous event. The Tap Dial is so much faster than the Ikea Symfonisk for volume control (near instant). |
For anyone interested, the rotation support will be supported in Deconz in Home Assistant 2012.12. |
I'm currently using zigbee2mqtt which supports the tap dimmer really well! |
The problem
Hi,
Repeated
start
events in the same direction seem to be ignored by the integration and they do not generate events in HA.I am monitoring this by following
hue_event
.This happens when I gently rotate the button, about every second. If I wait even more (10 seconds), and do a single rotation (without leading to the generation of
repeat
event, it won't generate astart
altogether.If the event type is the same
start
but thesubtype
is differentclock_wise
vscounter_clock_wise
, it will create a new event.If I rotate the button a little faster, it will generate a
repeat
event. However, it is harder to simulate, if I manage to keep the same rotation rythm (exact samesteps
), it looks it the repeatedrepeat
event is also ignored.That's why I am thinking this is some kind of ignored repeated events with the same
data
.I checked in the diagnostic logs of the integration and the
start
events are all here, every second. Logs below.It looks like there are filtered by the integration because it's the same event type. I had a quick look at the code, but I am not sure what could give this result, maybe the
event_filter
here and/or this long press button workaround inaiohue
because the code is not checked againstdevice.product_data.model_id not in BTN_WORKAROUND_NEEDED
like the next condition?I tried to update the code for both ideas but no difference. 😞
I don't think this is related to the "1 second polling" limitation mentioned in #75082, since the
aiohue
lib is able to catch them all.What version of Home Assistant Core has the issue?
2022.9.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Philips Hue
Link to integration documentation on our website
https://www.home-assistant.io/integrations/hue/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
The text was updated successfully, but these errors were encountered: