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
Single/double click of Xiaomi wireless button no longer works since 0.83.x #19413
Comments
breaking change in 0.83.
Check the docs and that pr for the fix. |
@marchingphoenix Thnx for your reply.
I tried to use the This does not work: - alias: Dimm light
trigger:
platform: event
event_type: click
event_data:
entity_id: xiaomi_aqara.binary_sensor.wall_switch_left_158d00027c19e9
click_type: single
action:
service: light.turn_on
entity_id: light.hue_ambiance_slaapkamer
data_template:
brightness: 80 And the title: My Home
views:
- icon: mdi:home-assistant
title: home-assistant
cards:
- type: entities
title: Woonkamer
entities:
- xiaomi_aqara.binary_sensor.wall_switch_left_158d000xxxxxx It returns the error below when I reload the Lovelace UI:
Also the |
Please prefix the value of |
@syssi Thanks for your suggestion. My mistake, silly me, although I tried it correctly before. Now I did put the # Dimm hue light with xiaomi switch
- alias: Dimm slaapkamer licht
trigger:
platform: event
event_type: xiaomi_aqara.click
event_data:
entity_id: binary_sensor.wall_switch_left_158d00027c19e9
click_type: single
action:
service: light.turn_on
entity_id: light.hue_ambiance_slaapkamer
data_template:
brightness: 80 Unfortunately it doesn't work. Do you have more suggestions? I turned on debug logging: logger:
default: debug and I captured these related log lines when I pressed the buttons:
I could not find any |
As first step could you update to HA 0.84.3 and try again? |
I upgrade already to HA 0.84.3 before I opened this issue. |
Could you check out automation called "Dimm slaapkamer licht" at the dev-state page f.e.? Is the automation enabled? It looks like the ZigBee device is working fine. Just your automation doesn't work. Could you try this automation:
|
Thnx for your instructions.
What do you mean by that? I am still a bit puzzled about some things:
Now you have proved the Xiaomi sensor is working, I will look into my actions. Thx for your help! |
You could add
Or you could add |
The first generation of the wall switch doesn't support a long press events AFAIK. |
@syssi. Very useful, I didn't know that automation's could be disabled. Thanks! |
Home Assistant release with the issue: 0.83.x, 0.84.0, 0.84.1, 0.84.2 and 0.84.3
Last working Home Assistant release (if known): 0.82.1
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: components/binary_sensor.xiaomi_aqara
Description of problem: Single/double clicks on Xiaomi wireless buttons (WXKG02LM) are no longer captured on the
dev-state
page nor do they trigger any automation since updating from 0.82.1 to 0.84.x. The state on thedev-state
page and in theLovelace UI
is presented asoff
.Remarkable: The last action of the Xiaomi buttons on the
dev-state
page and theLovelace UI
changes todouble
when I double click! Asingle
click will change it intosingle
. Along
click does make any change. No history is available.The Xiaomi wireless switch (WXKG02LM) entities are displayed on the
dev-state
as below:Triggers in my
automations.yaml
do not act on the click_typesingle
orboth_click
.Here automation snippet that works in 82.1, but not works in 0.83.x and 0.84.x:
Other Xiaomi components including motion sensors, temp/humidity sensors and power plug are still working fine in 0.82.x, 0.83.x and 0.84.x
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Below the
xiaomi_aqara
component logging. It starts with some sensors that work okay.note: I did add comments to indicate which button I pushed.
Additional information:
Community thread that other users report similar issues:
https://community.home-assistant.io/t/xiaomi-button-no-longer-registers-single-or-double-press/83129
The text was updated successfully, but these errors were encountered: