Xiaomi RTCGQ11LM devices not updating after some time #185
Comments
|
In case it helps, I went ahead and just tried to repair one of the problem devices and this is what it shows in the log when I repair it:
After doing this it starts to report again. I hope I can just avoid having to do this over and over. |
|
Are you running the latest firmware from: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/CC2531/bin? |
|
@Koenkk I don't know Im afraid. I bought it pre-flashed from someone on reddit. Is there a way I can check the version from the ubuntu host I have it plugged into? |
|
At the moment not, when did you order the stick? |
|
I ordered it on June 15th, so it would have been flashed sometime between June 1st and June 15th. I went ahead and ordered hardware to flash it again. should be here in a couple weeks from china. ill keep you posted if that helps. Thanks for all your time and efforts making thus great solution. |
|
I have same problem with newest Version of your firmware and the RTCGQ11LM. After Restart zigbee2mqtt both of my 2 RTCGQ11LM Motion Sensor didn't update the state. I have to push the button one time or pair again. Is there any workaround for this bug? |
|
@Sonsi79 can you check the battery of your 2 motion sensors. I tried reproducing by (on zigbee2mqtt 0.1.2 and last CC2531 firmware).
|
|
@Koenkk it seems you're right. It seems to work now. |
|
Same issue here. I have 5 RTCGQ11LM. 2 pices worked very well. But the other 3 ones lost the connection time for time. I use the problemematic 3 ones for 2 weeks now. The othes runs about for 10 weeks without problems. Is it possible, that there are different revisions on the market? But all looks equal. I use the 0.1.1 version, and the latest firmware on the CC2531 stick. |
|
@123trs have you also tried replacing the batteries? |
|
For those of us having problems, is range an issue at all? How many devices do you have joined to your stick? All the devices in my home that are having the problems are fairly far away from my CC2531 stick, Its strange that they work for a while then stop working . I hope to have my programming hardware in the next few days so I can flash another CC2531 stick to act as a router upstairs to extend the range. Currently i have 20 devices joined to my single CC2531 stick, I wonder if its getting swamped? I'm currently having problems with the following devices: WSDCGQ11LM If I rejoin them they will work for a couple days then just stop publishing their status. I was hoping just flashing to the latest firmware would be the fix but it sounds like it's more then that. |
|
@Koenkk : Yes, batteries brand new, good Varta |
|
@cmille34 : I dont think, the range is the problem. For test, I place one in 50cm range. It works for about 24h. After that, same problem. I paired 5 sensors of that. |
|
For those with this problem do you have permit_join set to true or false? With permit_join set to false I was also having heaps of problems with devices not responding after some time and needing to reboot daily and reflash the firmware weekly. I even started from scratch with a new image on my Pi and installing zigbee2mqtt again but still had same problem. I changed permit_join back to true and am finding the whole system is much more stable. |
|
"permit_join" ist set to "true" from the beginning. I never changed it. |
|
Again no responding from device 0x00158d000204aab1. New paired jesterday 16:30. Last response: state | no_motion | 2018-08-02 07:19:27 |
|
My Setting was set to „false“ i have changed it and will try now. Thank for your hint. |
|
My setting was set to false. I was using the toggle switch in Home Assistant to allow things to join when I needed. Ill change it to allow join = true all the time and see if that makes a difference. |
|
I finally received my flashing hardware and additional 2531 boards. I flashed the router firmware onto a 2531 and joined it to my zigbee2mqtt docker instance and have it plugged in upstairs to eliminate any chance of range being an issue. I then went ahead and re-flashed my coordinator 2531 stick to the firmware here: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/CC2531/bin to make sure I am on the latest. I then went through the trouble of removing and re-pairing all 20 devices. I noticed one of the devices wasn't reporting afterwards so I tried to remove it again and re-pair it and it wouldn't go through the joining process at all. I looked at the logs and found: I checked on Github here and saw the fix of reflashing the firmware again, so I went ahead and did that and now I can pair that one pesky Xiaomi temp sensor. An hour after flashing, most of the devices I paired prior to reflashing the stick aren't reporting though, only 3 of the 20 devices are. They all show up in the log at boot up of being pared but no updates are being received it seems. When I flash firmware to the stick do I have to repair the devices everytime? I really don't want to have to keep re-pairing these devices. |
|
When you flash the firmware you clear the memory of the stick so you need to repair all devices. Could you first start with a smaller set of devices (e.g. 10) and check if you can get it working stable? |
|
@Koenkk OK, I will repair only 10 devices in different areas of the house and see how it works. How exactly should I do this to make it a clean set up? 1.) Should I delete all devices in my configuration.yaml manually? |
|
|
@Koenkk OK - thanks for the guidance. I've gone ahead and reflashed the stick 1 more time, deleted the database and cleared out the devices and repaired the 11 most important devices for me. If I run into any trouble of devices no longer reporting in the zigbee2mqtt log I will post back here. Is the C2531 not a good stick? Is there a stick with more memory that handles many devices better? |
|
@cmille34 CC2531 has limited memory, but there are no other options :( |
|
@cmille34 cc2531 has old chip with limited memory (8K). On TI forum recomended CC26x2 or CC2538 chip https://e2e.ti.com/support/wireless_connectivity/proprietary_2-4_ghz/f/964/t/633997 I try to find usb-dongle with this chip and found only this https://www.alibaba.com/product-detail/CC2538-CC2592-USB-Dongle-ZigBee-adapter_60426940995.html but I can not buy it for test :( |
|
@kirovilya how about this one The U2ZB-3219 option Sent with GitHawk |
|
@ryanbeaton I bought and wait this board https://www.aliexpress.com/item/CC2538-CC2592-zigbee-6-lowpan/32879578178.html |
|
I am using OpenHab as well; however, AFAIK, the Zigbee addon for OpenHab
has a lot of issues with Xiaomi devices. Chris, the addon developer,
believes that Xiaomi devices aren't fully Zigbee compliant. I jumped
directly to Zigbee2mqtt after doing the research. And for the most part,
it's quite stable. Several of my sensors do kind of stop communicating over
time, but I think it is a range issue. I am ordering another CC2531 to use
as a router.
…On Thu, 11 Oct 2018 at 15:03, SuperTux101 ***@***.***> wrote:
I don't think Xioami delivers poor quality. If the original bridge is
used, reporting does not stop. I've seen that Openhab has an addon for
Zigbee, able to use the CC2531 (using the same firmware). It works and
devices are recognized. It's maybe a good idea to test if reporting
continues on OH.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#185 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABKsTk06orOuWUxZtF4rvHyz86PLRN66ks5uj5XygaJpZM4VGYpJ>
.
|
|
I see couple of interesting log entries today. One of the Xiaomi motion
sensors on my 2nd floor stopped triggering today. This is the one farthest
away from the Rasp Pi containing the sniffer. I took it off and re-paired
right besides the Pi. But still no mqtt message is sent. But the sensor
does work. Every time I waved my hand in front of it, I get 3 log entries:
Oct 17 22:39:41 raspberrypi npm[5241]: 2018-10-17 22:39:41 DEBUG Recieved
zigbee message with data
{"cid":"msIlluminanceMeasurement","data":{"measuredValue":9}}
Oct 17 22:39:41 raspberrypi npm[5241]: 2018-10-17 22:39:41 DEBUG Recieved
zigbee message with data
{"cid":"msIlluminanceMeasurement","data":{"measuredValue":9}}
Oct 17 22:39:41 raspberrypi npm[5241]: 2018-10-17 22:39:41 DEBUG Recieved
zigbee message with data {"cid":"msOccupancySensing","data":{"occupancy":1}}
Notice that no device id displayed in the log. So the sensor is working,
and zigbee2mqtt does receive the message, but it somehow doesn't know the
device or lost track of the device.
…On Sat, 13 Oct 2018 at 22:14, Hai Pham ***@***.***> wrote:
I am using OpenHab as well; however, AFAIK, the Zigbee addon for OpenHab
has a lot of issues with Xiaomi devices. Chris, the addon developer,
believes that Xiaomi devices aren't fully Zigbee compliant. I jumped
directly to Zigbee2mqtt after doing the research. And for the most part,
it's quite stable. Several of my sensors do kind of stop communicating over
time, but I think it is a range issue. I am ordering another CC2531 to use
as a router.
On Thu, 11 Oct 2018 at 15:03, SuperTux101 ***@***.***>
wrote:
> I don't think Xioami delivers poor quality. If the original bridge is
> used, reporting does not stop. I've seen that Openhab has an addon for
> Zigbee, able to use the CC2531 (using the same firmware). It works and
> devices are recognized. It's maybe a good idea to test if reporting
> continues on OH.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#185 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABKsTk06orOuWUxZtF4rvHyz86PLRN66ks5uj5XygaJpZM4VGYpJ>
> .
>
|
|
I restarted the device, and noticed in the log that that particular sensor
is in Unknown state. This is strange because it has been working in the
last couple of days. I had to remove it from zigbee2mqtt database using the
command "mosquitto_pub -d -t zigbee2mqtt/bridge/config/remove -m 0x..." and
re-pair again. It works afterward.
Does anyone know under what condition would zigbee2mqtt changes a known and
work device to "Unknown"?
…On Wed, 17 Oct 2018 at 22:41, Hai Pham ***@***.***> wrote:
I see couple of interesting log entries today. One of the Xiaomi motion
sensors on my 2nd floor stopped triggering today. This is the one farthest
away from the Rasp Pi containing the sniffer. I took it off and re-paired
right besides the Pi. But still no mqtt message is sent. But the sensor
does work. Every time I waved my hand in front of it, I get 3 log entries:
Oct 17 22:39:41 raspberrypi npm[5241]: 2018-10-17 22:39:41 DEBUG Recieved
zigbee message with data
{"cid":"msIlluminanceMeasurement","data":{"measuredValue":9}}
Oct 17 22:39:41 raspberrypi npm[5241]: 2018-10-17 22:39:41 DEBUG Recieved
zigbee message with data
{"cid":"msIlluminanceMeasurement","data":{"measuredValue":9}}
Oct 17 22:39:41 raspberrypi npm[5241]: 2018-10-17 22:39:41 DEBUG Recieved
zigbee message with data {"cid":"msOccupancySensing","data":{"occupancy":1}}
Notice that no device id displayed in the log. So the sensor is working,
and zigbee2mqtt does receive the message, but it somehow doesn't know the
device or lost track of the device.
On Sat, 13 Oct 2018 at 22:14, Hai Pham ***@***.***> wrote:
> I am using OpenHab as well; however, AFAIK, the Zigbee addon for OpenHab
> has a lot of issues with Xiaomi devices. Chris, the addon developer,
> believes that Xiaomi devices aren't fully Zigbee compliant. I jumped
> directly to Zigbee2mqtt after doing the research. And for the most part,
> it's quite stable. Several of my sensors do kind of stop communicating over
> time, but I think it is a range issue. I am ordering another CC2531 to use
> as a router.
>
> On Thu, 11 Oct 2018 at 15:03, SuperTux101 ***@***.***>
> wrote:
>
>> I don't think Xioami delivers poor quality. If the original bridge is
>> used, reporting does not stop. I've seen that Openhab has an addon for
>> Zigbee, able to use the CC2531 (using the same firmware). It works and
>> devices are recognized. It's maybe a good idea to test if reporting
>> continues on OH.
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#185 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/ABKsTk06orOuWUxZtF4rvHyz86PLRN66ks5uj5XygaJpZM4VGYpJ>
>> .
>>
>
|
|
@yfaway could you post your zigbee2mqtt startup log? |
|
Koen,
I am attaching the log containing the last timestamp the sensor was
working fine. The log then contains various attemps to re-pair, a restart,
a device removal, and then the final re-pair that get it back to working
state. The sensor id is: 0x00158d000200eb10.
At some point, I see this message in the log:
Oct 17 22:18:20 raspberrypi npm[5241]: 2018-10-17 22:18:20 DEBUG Recieved
zigbee message with data "0x00158d000200eb10"
Oct 17 22:18:21 raspberrypi npm[5241]: 2018-10-17 22:18:20 WARN Message
without device!
Oct 17 22:18:24 raspberrypi npm[5241]: spinlock: true []
After the restart:
Oct 17 22:42:22 raspberrypi npm[27439]: 2018-10-17 22:42:22 INFO Starting
zigbee2mqtt version 0.0.0 (commit #2ba2864)
Oct 17 22:42:22 raspberrypi npm[27439]: 2018-10-17 22:42:22 INFO Starting
zigbee-shepherd
Oct 17 22:42:25 raspberrypi npm[27439]: 2018-10-17 22:42:25 INFO
zigbee-shepherd started
Oct 17 22:42:25 raspberrypi npm[27439]: 2018-10-17 22:42:25 INFO Currently
8 devices are joined:
Oct 17 22:42:25 raspberrypi npm[27439]: 2018-10-17 22:42:25 INFO
0x00158d0001fa45fd (0x00158d0001fa45fd): RTCGQ11LM - Xiaomi Aqara human
body movement and illuminance sensor (EndDevice)
Oct 17 22:42:25 raspberrypi npm[27439]: 2018-10-17 22:42:25 INFO
0x00158d000200ed5e (0x00158d000200ed5e): RTCGQ11LM - Xiaomi Aqara human
body movement and illuminance sensor (EndDevice)
Oct 17 22:42:25 raspberrypi npm[27439]: 2018-10-17 22:42:25 INFO
0x00158d000236b6c0 (0x00158d000236b6c0): RTCGQ11LM - Xiaomi Aqara human
body movement and illuminance sensor (EndDevice)
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:25 INFO
0x00158d000236b4cd (0x00158d000236b4cd): RTCGQ11LM - Xiaomi Aqara human
body movement and illuminance sensor (EndDevice)
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:26 INFO
0x00158d000204c7ef (0x00158d000204c7ef): RTCGQ11LM - Xiaomi Aqara human
body movement and illuminance sensor (EndDevice)
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:26 INFO
0x00158d000245f049 (0x00158d000245f049): WSDCGQ11LM - Xiaomi Aqara
temperature, humidity and pressure sensor (EndDevice)
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:26 INFO
0x00158d000239725a (0x00158d000239725a): RTCGQ11LM - Xiaomi Aqara human
body movement and illuminance sensor (EndDevice)
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:26 INFO
0x00158d000200eb10 (0x00158d000200eb10): unkown - undefined unknown
(EndDevice)
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:26 WARN
`permit_join` set to `true` in configuration.yaml.
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:26 WARN Allowing
new devices to join.
Oct 17 22:42:26 raspberrypi npm[27439]: 2018-10-17 22:42:26 WARN Set
`permit_join` to `false` once you joined all devices.
Note the very last device: undefined unknown (EndDevice)
Thank you for looking at this,
…On Thu, 18 Oct 2018 at 02:09, Koen Kanters ***@***.***> wrote:
@yfaway <https://github.com/yfaway> could you post your zigbee2mqtt
startup log?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#185 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABKsTsV5sLS49G9IVpDVthr5D7mgf1agks5umBsLgaJpZM4VGYpJ>
.
|
|
Can you stop zigbee2mqtt, remove all entires of |
|
Koen,
But I did remove it and re-pair before, and it's working now.
Best,
…On Fri, 19 Oct 2018 at 16:10, Koen Kanters ***@***.***> wrote:
Can you stop zigbee2mqtt, remove all entires of 0x00158d000200eb10 from
the database.db start zigbee2mqtt and pair the sensor?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#185 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABKsTruUccNf0rv3leDn_O666bKlDVxKks5umjG7gaJpZM4VGYpJ>
.
|
|
Funny I do have some of the same issue with the 0.1.8 version and the motion sensor. It works a few times, then it stops updating the state from the sensor. reverting to 0.1.6 solves it, then everything is working again. |
|
I have the same error; when trying to rejoin I get: nov 11 22:12:37 servidor7 npm[3930]: zigbee2mqtt:error 2018-11-11 22:12:37 Cannot get the Node Descriptor of the Device: 0x00158d000201358f (Error: Timed out after 10000 ms) I cannot get it rejoined. |
|
@enboig make sure you correctly follow the pairing procedure from: https://github.com/Koenkk/zigbee2mqtt/wiki/Pairing-devices#xiaomi |
|
After upgrading to 0.1.8 (maybe not necessary) and deleting database.db I could join it. Does deleting database.db remove all the devices? is there a "less drastic" way to remove one device by id? |
|
@enboig you can also remove a single entry from it. |
|
The database is looks quite simple, to remove an entry I could use a cat & grep, is there a preferred way? I have a motion sensor and two temperature sensors, yesterday:
|
Hi, @kirovilya what are you using to program the cc2538 ? does it come with SBL ? |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I would like to add a comment to this topic.
Then I saw a line somewhere that the Xiaomi devices do not lose their connection with a paired coordinator / router. This was the solution which I was looking for. I guess you can put this solution in your documentation also? |
|
@djpollum did you reflash without the |
Yes @Koenkk , I did exactly the same as shown in the picture on https://koenkk.github.io/zigbee2mqtt/getting_started/flashing_the_cc2531.html. |
|
@djpollum at the time trying to pair the motion sensor to zigbee2mqtt, was the hub still running? |
|
@djpollum I see, can you add a PR to add this here: https://github.com/Koenkk/zigbee2mqtt/blob/master/docs/getting_started/pairing_devices.md#xiaomi? |
|
I still have this issue after updating to latest I found that I can short click pairing button on sensor without actually repairing and it starts to work again. All 4 sensors disappear at random interval between few days or weeks. |
|
It happened to me to only one device. I changed the zigbee channel (repairing all de devices...) and since then (2 weeks ago) I haven't had a single problem. Zigbee appears to use the same band (but not the same channel scheme) than wifi. Now my wifi is at channel 1 and zigbee at 25. |
|
How do you change the channel? I seem to have the same issue, if I shake the sensor it starts reporting back for a few minutes, then goes back silent... LE: I actually found out, it's in the configuration.yaml |
|
https://www.zigbee2mqtt.io/information/configuration.html |
|
I still have this issue with a RTCGQ11LM - any news on this how to resolve it? |
|
Hello! |
I've been tinkering with this for a few weeks in an effort to get rid of using the Xiaomi gateway. I have everything working for the most part but after some restarts, I am noticing that Xiaomi RTCGQ11LM and MCCGQ11LM devices will intermittently stop updating sometimes. I thought it might be a range issue but one of the motion sensors that is only 25 feet away in the other room is not longer updating now and it had been working the most reliably for the past couple weeks.
If I bring the sensor close to the flashed CC2531 stick running in a docker container in my office here and re-pair it, it will likely work for a while but within a week after some reboots I expect it to stop reporting again. I have (3) different RTCQ11LM devices that are doing this now. I don't want to have to re-pair them every week if possible. Is there something I can do to help troubleshoot this? Below is a beginning of my latest log file to help provide a better picture of my setup. Currently I am using the builtin MQTT broker in Home Assistant.
Any help you can provide to help get to the bottom of this would be appreciated. I apologize if I left out any crucial information to help troubleshoot.
The text was updated successfully, but these errors were encountered: