-
Notifications
You must be signed in to change notification settings - Fork 5
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
Aqara button #20
Comments
Multi click is normally handled by the button itself and should send a cluster : 0006/ attribute : 8000 event (not 0006/0000) as in your example (so one event only, and you should have the number of clicks in the attribute data'). Can you confirm that you have no event 0006 / 8000 in your log ? |
Multi click is recognised, the problem is that the single click is not recognize when configured as a sensor. The pressed and released signal arriving too fast after another. |
I'll add the multi click log entry tomorrow:-) |
@RiRomain is this still an issue and does it also affect the round v1 xiaomi buttons? I've got single click working as a toggle, but would like to be able to use both single and multi click. |
Yes, it's still an issue. Mine is the square aqara button. |
As of now, it's not possible to use all the function of the aqara push button.
Either it's configured as a sensor and the single click doesn't work.
Or as a toggle switch and the multi click doesn't work
As a sensor, the single click doesn't work because the state is set from Closed/Taken off/Press back to Open/Release button too fast for home-assistant to see the state change.
I added a log entry in function update_attributes and in function state to make this behavior easy to recognize.
In update_attributes, we make a call to self.schedule_update_ha_state but the state updates all happened after the attributes have already been reset to Open/Release button
I've tried to modify update_attributes to call schedule_update_ha_state(True) instead of schedule_update_ha_state() and therefore force the update. But without success.
Is there another way to force Home-Assistant to register this very short state change? Or what is the best way to handle those push button?
The text was updated successfully, but these errors were encountered: