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 RTCGQ11LM Motion and Illuminance senors does not send occupancy: true messages #2364

Closed
guardiande opened this issue Nov 18, 2019 · 1 comment

Comments

@guardiande
Copy link

Bug Report

What happened

I have three motion sensors (two RTCGQ11LM and one RTCGQ01LM). Two of the three sensors work flawlessly, but one of the RTRTCGQ11LM (with luminance) only works by chance: Right after powering it up or re-pairing it, it sends a few correct occupancy: true messages. But after a very short time it will only very seldomly sent occupancy: true messages. It actually reacts to motion but sends occupancy: false messages.

The following log entries where generated while waving my hand in front of the device:

info  2019-11-18T17:14:23: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":6,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:14:28: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:14:34: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:14:40: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:14:46: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:14:52: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":18,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:14:58: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:15:03: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":18,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:15:09: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":18,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:15:17: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":8,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:15:22: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":3,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
info  2019-11-18T17:15:22: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":3,"linkquality":15,"occupancy":true,"battery":100,"voltage":3005}'
info  2019-11-18T17:15:27: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":18,"occupancy":true,"battery":100,"voltage":3005}'
info  2019-11-18T17:15:36: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":15,"occupancy":true,"battery":100,"voltage":3005}'

And here's some corresponding debug logging:

debug 2019-11-18T17:23:21: Received Zigbee message from 'Motion2', type 'attributeReport', cluster 'msIlluminanceMeasurement', data '{"measuredValue":7}' from endpoint 1 with groupID 0
info  2019-11-18T17:23:21: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":7,"linkquality":15,"occupancy":false,"battery":100,"voltage":3005}'
debug 2019-11-18T17:23:34: Received Zigbee message from 'Motion2', type 'attributeReport', cluster 'msIlluminanceMeasurement', data '{"measuredValue":4}' from endpoint 1 with groupID 0
info  2019-11-18T17:23:34: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":4,"linkquality":18,"occupancy":false,"battery":100,"voltage":3005}'
debug 2019-11-18T17:23:39: Received Zigbee message from 'Motion2', type 'attributeReport', cluster 'msIlluminanceMeasurement', data '{"measuredValue":0}' from endpoint 1 with groupID 0
info  2019-11-18T17:23:39: MQTT publish: topic 'zigbee2mqtt/Motion2', payload '{"illuminance":0,"linkquality":18,"occupancy":false,"battery":100,"voltage":3005}'

And here's a graph showing the phenomenon (the negative y axis show the luminance and the positive y axis should show the occupancy):

image

The graph shows that the illuminance gets updated regularly but without a coincident motion.

What did you expect to happen

Correct occupancy: true events.

How to reproduce it (minimal and precise)

  • Remove battery
  • Insert battery
  • Notice how the device correctly reports occupancy and absence
  • Wait a few minutes
  • Notice how the device reacts on motion but does not indicate it in the occupancy event attribute

Debug Info

zigbee2mqtt version: 1.7.1 (commit #b459c35)
CC253X firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190619}}

@guardiande
Copy link
Author

Sorry, don't know why I didn't find those issues: #2274, #1498

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

1 participant