-
-
Notifications
You must be signed in to change notification settings - Fork 37.2k
Xiaomi Aqara window sensors stuck in off state #14775
Copy link
Copy link
Closed
Description
Home Assistant release with the issue:
0.70.1
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Any
Component/platform:
binary_sensor.xiaomi_aqara
Description of problem:
User reported their sensor_magnet.aq2 devices created binary_sensor.xiaomi_aqara entities stuck in off state, despite push events from the Xiaomi gateway for open and close.
The log shows:
2018-06-02 17:55:50 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'sensor_magnet.aq2', 'cmd': 'report', 'sid': '158d000205b435', 'params': [{'window_status': 'close'}]}
2018-06-02 17:55:50 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Door Window Sensor_158d000205b435: off>: {'raw_data': [{'window_status': 'close'}], 'window_status': 'close'}
2018-06-02 17:55:52 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'sensor_magnet.aq2', 'cmd': 'report', 'sid': '158d000205b435', 'params': [{'window_status': 'open'}]}
2018-06-02 17:55:52 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Door Window Sensor_158d000205b435: off>: {'raw_data': [{'window_status': 'open'}], 'window_status': 'open'}
The problem is that the XiaomiDoorSensor class expects the property to be named status rather than window_status. I'm not sure if this is because of some configuration in the gateway, but the class should handle both.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
xiaomi_aqara:
gateways:
- key: ***Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels