Xiaomi Motion Sensor RTCGQ11LM not reporting occupancy:true the second (like#1498) #2274
Comments
|
In the log I see that only the illuminance level is reported and no occupancy, can you check again with the xiaomi hub if they work there? |
|
I've just did it, and it works. I get the message "Motion detected, Illumination is: xx Lux. Today I've observed the sensors and found messages with occupancy = true. Here a corresponding log:
Where can you see that no occupancy is reported? For me it looks quite similar.. Thx |
|
If occupancy is reported you will find |
|
I just posted #2364. I wanted to let you know that I once again was able to get the faulty sensor to work again. I re-paired it several times and suddenly it started working again. Normally it works for a few weeks or months and then it starts failing again. The procedure to get it cooperate again is not exactly reproducible and simply restarting zigbee2mqtt can make it fail again. |
|
I have the same problem |
|
Now we are three of us ;-) |
|
I have the latest version of zigbee2mqtt@1.7.1 and the latest firmware in CC2531 (20190608), but the problem persists. |
|
To further debug this issue, could you sniff the traffic while the sensor should detect occupancy when connected with zigbee2mqtt (https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html)? |
|
I suppose I need another CC2531? I will order one and come back with the results. It's gonna take some time. |
|
Yes you need another one |
|
I will wait patiently for e-t-h to do the test, because I don't have another dongle either. :) |
|
Hi Koenkk, |
|
Okay, thank you for your support, surprisingly it is now working! Please ignore the posting before ;-) |
|
Hi Koenkk, Might be you've changed something? Or: I've been running the sensors together with the XIAOMI-hub meanwhile I've been waiting for the USB stick. Is it possible that an update of the firmware of the sensor have happened in this period? Is there anything I can read to be able to understand the data packets I receive with my brand new sniffer what you can recommend? I would appreciate any advice. By the way, is it possible to initiate a transmit of the illumination value by sending a request from the stick? Last but not least: Thank you for your work! Ekkehard |
|
Hi @e-t-h, I'm afraid that you most likely experience the same symptoms in the future again. I'm having this problem for many months now and the problem normally persists only for a week or something and then the sensor stops working again. Sometimes it happened right after just restarting z2m and I think it also happened during normal operation. Then it takes me many re-pairing to get it work again and then it works stable for some time. It could be that the behaviour is more likely to happen if the sensor connects via a router but I'm not sure. Jan |
|
Hi Jan, Ekkehard |
|
Xiaomi devices can drop off the network when the linkquality is low, this can be improved: https://www.zigbee2mqtt.io/how_tos/how_to_improve_network_range.html |
|
Hi @Koenkk, The sensors don't completely drop off the network since they're still reporting luminance and battery levels every hour our so (as you already saw from analyzing the logs a few posts above). Jan |
|
@guardiande that's even more interesting. When this happens, could you sniff the zigbee traffic when you expect occupancy being detected? In this way we can determine if it's an issue of zigbee2mqtt or the sensor itself. https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html |
|
@Koenkk I just got myself a second CC2530 for that but (un-)fortunately it's working now. Will have to way for the next failure :) |
Hi Jan, |
|
I'm having the same issue. Some of Aqara PIRs working fine, others not reporting occupancy change (but reporting other parameters the same time, and when movement present in front of sensor). I sniffed traffic from that sensor (and it happened that during recording it reported once occupancy). As this was my first time with wireshark, can someone please advise how (and in what format) export data for sharing here (I would like to keep security key private)? If just share privately with @Koenkk , then I can send unfiltered recordings. |
|
Hi all, Event Listing: Very strange. |
|
Hi essera, |
|
Oh sorry - repair means i did an "repairing" with any device with the this issue. now there are working. I cannot say how long it takes til the device have the same issue again. But then i will post it here. |
|
I too am having similar issues with the RTCGQ11LM. Movement is triggering messages in the Zigbee2MQTT log but message shows occupancy=false. Also shows illuminance. zigbee2mqtt:info 2020-02-11 19:40:32: MQTT publish: topic 'zigbee2mqtt/laundry_ceiling_light', payload '{"state":"OFF","brightness":255,"color_temp":250,"linkquality":107,"color":{"x":0.383,"y":0.382}}' The first time the sensor is triggering correctly and reporting occupancy = true. |
|
I have the same issue for ~1 year. Somtimes RTCGQ11LM sensors stop to send I tried to narrow the scope by doing these experiments:
Very often the issue disappears just by itself, without repairing. So reproduce the issue isn't an easy task. Thanks |
|
I noticed the same behaviour with one of my PIR sensors (5 in total).
|
|
Hi all, i promised in my last post to give you an update if the issue happens again - it happens again :-( It happend to my test PIR on my desk and one in my cellar. Meanwhile i tried the same Things to get the PIR back to work.
One PIR stops working only one time - after ReParing , he is working since 5 weeks. i was on Holiday for a week and in that time all PIR´s worked OK, now. @Koenkk |
|
I bit the bullet and used an old CC2531 device as a second coordinator, running in a second zigbee2mqtt docker instance. I put only my Aqara motion sensors in the second zigbee network. Now indeed the device updates are not failing anymore :) |
|
Having the same issue with the Xiaomi RTCGQ11LM devices. (Re)pairing close to the coordinator fixes the issue for 2-3 days until the network gets rearranged. |
|
@milaq unfortunately not, we have no control over what parents will be used by the devices. Note that we cannot fix this issue from Zigbee2MQTT, it's an issue in the firmware of the routers. |
|
Do we know which routers are affected?
With my Innr bulbs it works fine for example.
… Am 14.09.2020 um 22:21 schrieb Koen Kanters ***@***.***>:
@milaq unfortunately not, we have no control over what parents will be used by the devices. Note that we cannot fix this issue from Zigbee2MQTT, it's an issue in the firmware of the routers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Reading this issue, lot of people experience it with OSRAM devices. |
|
Innr smartplug in my case. And osram bulbs.
Il lun 14 set 2020, 22:40 Koen Kanters <notifications@github.com> ha
scritto:
… Reading this issue, lot of people experience it with OSRAM devices.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2274 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATG2PHXY4SPHJRA3JFVED3SFZ5SJANCNFSM4JIXEDAA>
.
|
Thanks for the swift response! Maybe this could be worth a wiki update?
At least routing via my "Osram Smart +" plugs ( I ordered these Xiaomi plugs (https://www.amazon.de/dp/B083F91ZX3/) and will test them in the exact same constellation as parent for the |
|
And Philps Hue bulbs too, sorry.
Il lun 14 set 2020, 22:44 Michele <roncallim@gmail.com> ha scritto:
… Innr smartplug in my case. And osram bulbs.
Il lun 14 set 2020, 22:40 Koen Kanters ***@***.***> ha
scritto:
> Reading this issue, lot of people experience it with OSRAM devices.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#2274 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AATG2PHXY4SPHJRA3JFVED3SFZ5SJANCNFSM4JIXEDAA>
> .
>
|
|
Well yes I read that.
Interestingly enough I never had this happen although I have two Lightify plugs in my network. Maybe luck.
… Am 14.09.2020 um 22:40 schrieb Koen Kanters ***@***.***>:
Reading this issue, lot of people experience it with OSRAM devices.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Today the Xiaomi plugs arrived. They cost ~7€ more than the Osram plugs but the build quality is way better and they also pass power as well as circuit temperature measurements. The relay is also quieter when switching. To sum things up: After short testing, the 'Xiaomi Mi Smart Plugs' ( |
|
Since this issue cannot be solved from Zigbee2MQTT I will close this. I've updated the docs: https://www.zigbee2mqtt.io/devices/RTCGQ11LM.html#troubleshooting-no-occupancy-only-illuminance-is-published |
|
Thanks Koen everything is working fine since.
Outlook for Android<https://aka.ms/ghei36> downloaden
…________________________________
From: Koen Kanters <notifications@github.com>
Sent: Friday, September 25, 2020 7:57:40 PM
To: Koenkk/zigbee2mqtt <zigbee2mqtt@noreply.github.com>
Cc: dirkve <dirk_versavel@hotmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [Koenkk/zigbee2mqtt] Xiaomi Motion Sensor RTCGQ11LM not reporting occupancy:true the second (like#1498) (#2274)
Closed #2274<#2274>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#2274 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFCZTR7FVYVI5IY3XFPXAULSHTKZJANCNFSM4JIXEDAA>.
|
|
@AlexxIT found a possible fix for this issue. It seems that the illuminance is only send through the Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html) |
|
This is great news! Did anyone do some testing yet on the dev branch? |
|
Im on the dev branch since this fix has been implemented.
Need more time but atm it's seems to work just great.
Will report an update in a few weeks.
Il sab 19 dic 2020, 11:55 freakshock88 <notifications@github.com> ha
scritto:
… This is great news! Did anyone do some testing yet on the dev branch?
Would love to go back to a single zigbee network instead of separate ones
again :)
Will try to test when I have time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2274 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATG2PBH3HQXL2U3JN7VFZ3SVSBBZANCNFSM4JIXEDAA>
.
|
|
You need to know, this fix helps if only one message from sensor missed. Motion or illumination. It won't help if both messages will be missed for some reason. |
|
I have tested the new dev branch for about a week now, and this issue seems totally solved :) Super happy. Thanks to @AlexxIT ! |
Thank you! |
|
@bongiozzo today (zigbee2mqtt 1.17.0) |
|
Do I understand correctly, that this information can be safely removed from documentation for all previously affected devices?
|
|
@qqgg231 this device does still not route all messages correctly, however for the no occupancy for the Xiaomi RTCGQ11LM a workaround has been found. Updates the docs accordingly (will be updated tomorrow) |
|
If I understand this right, just by having these on a Zigbee network, you run the risk of missing some messages that may be routed through them. If so, would it be possible to work around this issue by disabling routing on these specific devices? Making them work only as end devices and not routers? This way, they could still be used as smart plugs, while other (well-behaved) routers in the network do the routing. |
Bug Report
I have the same issue like described in the closed issue #1498: sensors don't report occupancy:true.
I have two RTCGQ11LM sensors, ran for a long time at an Aqara Hub, without any issues. Since I am working with zigbee2mqtt I've noticed that they shows the same behavior @zerofruchtshake desribed in issue #1498: the occupancy value is not set properly. I am currently not able to get a message with "true".
What happened
Two sensors:
Sensor 1 (friendly name Bew_unten) is hardware modified like discribed in the documentation to shorten the time the sensor ignores any movements.
Sensor 2 (friendly name Bew_oben) is not modified.
Both have the same issue.
What did you expect to happen
sensors value "occupancy" should be set to "true"
How to reproduce it (minimal and precise)
It happens every time with every sensor; sensors were resetted,
Debug Info
zigbee2mqtt version: 1.6.0,
CC253X firmware version:20190608
I've collect some debug messages with the option DEBUG=zigbee-shepherd*-option, might be that helps? Currently I am not able to sniff with a second CC253x..
sensor 1
sensor 2
Any ideas? What can I additionaly provide? Does this debug output help to determine what the stick have received? I assume that the data item in the incoming message stores this information? Am I able to figure out how the software translate the data into the payload (if so, where I can find it)?
data 1 {"0":24,"1":47,"2":10,"3":0,"4":0,"5":33,"6":18,"7":0}
data 2 {"0":24,"1":24,"2":10,"3":0,"4":0,"5":33,"6":44,"7":0}
payload 1 {"illuminance":18,"linkquality":34,"occupancy":false,"battery":100,"voltage":3035}'
payload 2 {"illuminance":44,"linkquality":31,"battery":100,"voltage":3035,"occupancy":false}
Sincerly..
The text was updated successfully, but these errors were encountered: