Skip to content
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

Xiaomi Wireless Switch WXKG11LM and Vibration Sensor DJT11LM are not updating states on Lovelace Front End #1583

Closed
jerrychong25 opened this issue May 29, 2019 · 4 comments

Comments

@jerrychong25
Copy link

jerrychong25 commented May 29, 2019

Bug Report

What happened

Xiaomi Wireless Switch WXKG11LM and Vibration Sensor DJT11LM are not updating states on Lovelace Front End. Previously is working well, but now no longer working for unknown reason.

Weird part is that battery and linkquality are working without any issues.

Screenshot:
Screenshot 2019-05-29 at 12 55 27 PM

What did you expect to happen

Both sensors displays states correctly on Lovelace Front End.

How to reproduce it (minimal and precise)

  1. Install firmware on GBAN GB2530 Coordinator.
  2. Install Hass.io zigbee2mqtt plugin.
  3. Connect GBAN GB2530 Coordinator to Raspberry Pi.
  4. Turn on all devices.
  5. Connect these sensors by pairing them.
  6. State of sensors are not updated in Lovelace Front End.

Debug Info

zigbee2mqtt version: 1.4.0 (Hass.io add on)
CC253X firmware version: CC2530_CC2591_20190515 as per https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_Home_1.2/bin

Debug Log

Wireless Switch WXKG11LM

  zigbee2mqtt:info 5/29/2019, 12:56:28 PM MQTT publish: topic 'zigbee2mqtt/0x00158d00023dc1fb', payload '{"battery":100,"voltage":3045,"linkquality":96,"click":"single","device":{"ieeeAddr":"0x00158d00023dc1fb","friendlyName":"0x00158d00023dc1fb","type":"EndDevice","nwkAddr":3760,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_switch.aq2","hwVersion":"unknown","swBuildId":"unknown","dateCode":"unknown","status":"online"}}'
  zigbee2mqtt:info 5/29/2019, 12:56:28 PM MQTT publish: topic 'zigbee2mqtt/0x00158d00023dc1fb', payload '{"battery":100,"voltage":3045,"linkquality":96,"click":"","device":{"ieeeAddr":"0x00158d00023dc1fb","friendlyName":"0x00158d00023dc1fb","type":"EndDevice","nwkAddr":3760,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_switch.aq2","hwVersion":"unknown","swBuildId":"unknown","dateCode":"unknown","status":"online"}}'

Vibration Sensor DJT11LM

  zigbee2mqtt:info 5/29/2019, 12:57:30 PM MQTT publish: topic 'zigbee2mqtt/0x00158d0002a23402', payload '{"battery":100,"voltage":3025,"linkquality":83,"angle":177,"angle_x":1,"angle_y":1,"angle_z":89,"angle_x_absolute":89,"angle_y_absolute":89,"action":"drop","device":{"ieeeAddr":"0x00158d0002a23402","friendlyName":"0x00158d0002a23402","type":"EndDevice","nwkAddr":36657,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.vibration.aq1","hwVersion":"unknown","swBuildId":"unknown","dateCode":"unknown","status":"online"}}'
  zigbee2mqtt:info 5/29/2019, 12:57:30 PM MQTT publish: topic 'zigbee2mqtt/0x00158d0002a23402', payload '{"battery":100,"voltage":3025,"linkquality":83,"angle":177,"angle_x":1,"angle_y":1,"angle_z":89,"angle_x_absolute":89,"angle_y_absolute":89,"action":"","device":{"ieeeAddr":"0x00158d0002a23402","friendlyName":"0x00158d0002a23402","type":"EndDevice","nwkAddr":36657,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.vibration.aq1","hwVersion":"unknown","swBuildId":"unknown","dateCode":"unknown","status":"online"}}'

Thanks.

@Koenkk
Copy link
Owner

Koenkk commented May 29, 2019

With zigbee2mqtt 1.4, after a click, immediately an empty message is report. This is to make Home Assistant automation via entity possible. http://www.zigbee2mqtt.io/integration/home_assistant.html#via-home-assistant-entity

@jerrychong25
Copy link
Author

With zigbee2mqtt 1.4, after a click, immediately an empty message is report. This is to make Home Assistant automation via entity possible. http://www.zigbee2mqtt.io/integration/home_assistant.html#via-home-assistant-entity

Noted and thanks.

Is there any other ways to let empty message is report delay one second by default?

Because would like to confirm states of sensor is function properly in hardware itself before settings any automation.

Currently it is hard to visualize on this state.

@Koenkk
Copy link
Owner

Koenkk commented May 29, 2019

Can't this already be done by showing the history of the sensor?

@jerrychong25
Copy link
Author

Can't this already be done by showing the history of the sensor?

Of yes, can achieve the same via history.

I am thinking of viewing in real time =D

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants