Periodic temporary and permanent loss of devices. #4999
Comments
|
I'm facing very similar issue since a week. Zigbee2MQTT version: 1.16.1 |
|
I am also having issues with devices (seems to be end points) just losing network connectivity. This problem has started in the last few weeks since at least 1.16.0, however it may have started since1.15.0 Currently using 1.16.1 |
|
Confirm - i have the same issue since 2-3 weeks (from 1.15.0). Zigbee2MQTT version: 1.16.1 In 99% of cases - aqara devices going offline. All other devices (except connected to offline aqara router) works fine. |
|
@sinegovsky-ivan Some Aqara / Xiaomi wall switches and outlets is not routers an acting as no sleeping end devices and cat routing traffic in the network. Only checking that is working as router and if its not doing that you need more routers for building the mesh and your CC-2531 is very near its limit (12+20=32 devices) and getting / having problems :-( |
|
@MattWestb i'm sorry. my mistake. i checked and i have 2538+ 2592. as i see on the map almost all of my switches have the childs: |
|
Great then you should not having performance problem with the coordinator !!! |
|
All: Xiaomi battery powered devices leaving is a known issue which unfortunately cannot be solved from Zigbee2MQTT. Read more about what you can do here: https://www.zigbee2mqtt.io/devices/WXKG12LM.html#troubleshooting-device-stops-sending-messagesdisconnects-from-network @sysardex do you have the debug log from starting Z2M till the error?
To enable debug logging set in advanced:
log_level: debug |
|
@Koenkk I use the same setup since a year and above issues appeared from probably 1.15 😀. Restarting zigbee2mqtt in HA always solves the problem |
Just recently, out of 14 bulbs, 2 ignored the off command
|
|
Can changing channel help me? Can channel 11 be occupied by other devices? |
|
I have this issue with ikea tradfri dimmer. |
V3 20200211 |
|
@Koenkk Here the latest complete log. There is no error message, it simply stops responding. Why it receives messages ? --> "Received MQTT message on 'homeassistant/ " |
|
I had the same problem with my CC2531 and afterwards with a CC2591 (and better antenna). Solution for me: Using slaesh’s CC2652RB stick. Since then, nothing got lost anymore. |
|
Now the random device timeout again. This is a tradfri light bulb. Debug did not provide any further information. The device has been unresponsive for over an hour. But if I restart z2m now then the device will be online again.
|
|
@Koenkk I've seen the suggestion to disable the availability feature before, but where exactly can I do that? Either I'm missing something obvious in the config, or I'm not seeing it... Thanks! |
|
@brhahlen just remove or set to '0' parameter |
|
@Koenkk my issue was fixed after i enabled 2 features at config: |
|
I got 4 Ikea routers and they are all affected, types below. I replaced my CC2531 adapter on Z2M v1.14.2, with a zzh adapter (fw: 20200925) on Z2M v1.16.1. Before it was rock solid, now it´s very unreliable :-( @sinegovsky-ivan your suggestion didn't work for me. My affected Ikea routers: From the logs: |
|
@defcon84 You have no connection to the device because of very bad signal or interference. |
|
@MattWestb I believe you meant to tag @depen84.. Almost the same :) |
|
More than right @defcon84 !! Sorry for the wrong addressing it was not intended for the Netherlands (I think) ;-( |
|
@MattWestb no worries and you are correct, sir. :) |
|
Hello Koenkk
Indeed, there weren't any devices connected at that time. However it was
consequence of 3 times a day restarts of zigbee2mqtt after a week. I was
restarting zigbee2mqtt due to reported/observed lack of stability
I've paired again two sensors and they were successfuly discovered and
connected. I will observe those for a day or two and let you know
czw., 19 lis 2020, 18:46 użytkownik Koen Kanters <notifications@github.com>
napisał:
… @sysardex <https://github.com/sysardex> I suggest to disable the
availability feature first and see if the problems are fixed after that.
@igosoft <https://github.com/igosoft> your logs says: Currently 0 devices
are joined: , so it's not strange that you don't receive messages from
devices.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4999 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATYE3LWALWGTRZE44IXHX3SQVKWHANCNFSM4TXSQ3YQ>
.
|
|
@MattWestb It might actually be a bad antenna. I paired up everything a couple of days ago and all worked just fine for almost a day. Then it just went sideways. All My routers were just gone and then I found this thread. When I read your comment I recall that I made the antenna point up instead of down just to make it blend in better. Today I made it point down again and now my zigbee just works. I'll have to leave it like this to know for sure and I'll report back in a couple of days. |
|
@depen84 It can also being bad souldrings on the PCB that is moving with temperature, humidity and angle of the PCB and the antenna. Some have reporting that TI modules (with PCB and external antennas) it having better radio performance with the internal PCB antennas then the external one but then its something wrong with the module. You is doing it right that leaving it in that position for some days. After that you can trying other poisons but normally its the best 90° from the earth plane but its very depending of the antenna and the surrounding. If like looking on cracy antennas search for "coke antenna", its looks not real but is working well if making it right :-))) PS: All IKEA devices except the control outlet (have one large condensator very near the side of the antenna inside the case) have very good radio performance compared with the old TI devices (CC-253X chips) and is normally working good as routers in zigbee 3 network. |
|
I have one Tradfri bulb that disconnected and will not reconnect again, for some reason. All other devices, even in the same room, still work without problem. |
|
In my experiance, After a channel change you have to re-join all devices |
|
@baldfox Im not WiFi expert but if you compare frequencies of WiFi Chanel and ZigBee channel than you still might have overlapping frequencies. Please notice that I change also WiFi signal power. I will play with it more to figure it out where is the root cause. I'm sorry that you lost the devices. I confirm that you have to pair them again - no other changes are required to my knowledge. My current setup: Maybe you can also check other WiFi router around you by running WiFiAnalyzer application and compare frequencies of your ZigBee with other WiFi networks frequencies https://www.metageek.com/training/resources/zigbee-wifi-coexistence.html |
|
Thanks for coming back to me guys @fwelvering @igosoft - it's my fault i should have done more homework before switching the channel. I would never have bothered otherwise. I was only trying it just on the off chance. There's no other wifi signals around me, to run interference and nothings changed in 18mths except the actual software. I restored. |
|
@baldfox When I lost all of zigbee devices too and performed pairing again than I did not have change anything in HA, node-red or Z2M to make it work again |
I tried to re-add a device, but it kept telling me the name was in use. I just restored instead. Less hassle. Will see what happens with the latest release of z2m... 1.16.2 is just out |
|
Nothing has changed for me. I need to reboot z2m and devices multiple times daily. Once every 2-3 days I need to do a pair of lost devices again. Very often, due to timeouts, not all lamps in the chandelier turn off. It is very uncomfortable. I tried changing the frequency several times. |
|
I am having the same issue across multiple devices/brands with a cc1352p-2: |
|
Just so everyone is aware, there is a low level stack bug in the SiLabs EFR32 used by IKEA devices that causes them to crash. When they do crash, they still respond to multicast/group commands but no longer to direct NWK/APS queries and they also seem to stop routing for any connected end device children. This bug is fixed in Emberznet 6.7 and higher from SiLabs -- but a majority of IKEA devices are running earlier 6.0 to 6.5 releases that are all affected by this bug. The bug occurs when a bulb is processed a ZDO parent announcement and other traffic arrives. Seems to be triggering more often on large networks.
|
|
The bug validated by triggering it (with ZHA custom component) in the deCONZ github furum of the ZHA deves for around 2 months ago :-) |
So I upgraded everything to the latest version of HA (2020.12.7) and OS (5.10) and the problem still remains. I cannot for the life of me figure this out. If I restart the z2m add-on the aqara temp sensors (x2) come on immediately. I replaced the battery in one despite it showing 37% left, but it made no difference. Anyone have any success yet? I'm really loathed to change the channel and rejoin everything again, when nothing has changed from a z2m channel/wifi power/wifi channel or positioning perspective. |
Are you 100% certain of this? I thought the same thing for a while, but HA was simply getting the last MQTT message from the sensors, stored in the MQTT queue. In HA it looked like the sensors went "unavailable", I rebooted z2m, and they became "available" again, but they weren't actually available - I could tell because they always just showed the last temps they reported before vanishing. |
I have them set up in node-red (HA add-on) and as soon as I restart z2m and ask alexa or google home what the temperature is on either of them, they come back with the correct response, When they're unavailable, The command in NR falls over as they can't access HA for the reading. Now could the temperatures be frozen and report old temps, there's a slim chance it could be I suppose, but it's difficult for me to tell as I have no warning when or for how long they go unavailable for. |
|
Zigbee2mqtt For some reason the Phillips lamps doesn't work after the restart from my home server. Also 4 wall switches 230V are disconnected the end nodes work correctly
|
|
Before the Restart |
|
Is there a solution to quickly reconnect everything ? |
|
Today, after rebooting HA and Z2M, one more paired device was lost. It is still present in devices.yaml, but it is not in the list of paired devices. The latest information about this device in the logs: I still don't understand why this is happening. If he loses contact with him, shouldn't he remain in the list of devices but with a lost link? Why does it completely disappear from the device list? |
|
I also did some tests last weekend. I shutdown my rp3 for few hours (>4).
However when the system started, none of paired devices were found. I had
to pair everything again 🥺
śr., 27 sty 2021, 18:06 użytkownik sysardex <notifications@github.com>
napisał:
… Today, after rebooting HA and Z2M, one more paired device was lost. It is
still present in devices.yaml, but it is not in the list of paired devices.
The latest information about this device in the logs:
debug 2021-01-27 10:47:13: Received MQTT message on
'zigbee2mqtt/0x086bd7fffe03dbd9/availability' with data 'online'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4999 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATYE3IOESXBE7V4ZWFZO4DS4BBXXANCNFSM4TXSQ3YQ>
.
|
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
I don't believe this is stale. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
I have three aqara wired wall switches and they started to throw this error. Any solution here? |
|
Zigbee2MQTT:error 2021-04-02 15:30:33: Publish 'set' 'state' to 'switch_living_room' failed: 'Error: Command 0x00158d0003457245/2 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 34639 - 2 - 54 - 6 - 11 after 10000ms)' |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
Now after a backup and restore, on a fresh install on a new ssd plugged on RPI, I have lost again one zigbee switch. TuYa WHD02. All the other 4 switches of same model works fine. Any advice? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened
I have 56 zigbee devices.
Tradfri bulbs. More than 40 pcs
Xiaomi flood sensors
Xiaomi temperature sensors
Xiaomi buttons
Zigbee routers in every room
Issue 1
Periodically during use, one or more devices become unavailable for commands and status. The device is available on the network again if you restart the zigbee2mqtt server or restart the device itself. Logs error 2020-11-16 02:14:19: Failed to ping '0x000b ...
Issue 2
Periodically after restarting zigbee2mqtt it loses 1-2 devices. Most often these are tradfri bulbs. Logs error 2020-11-16 03:27:01: Entity '0x086b ....' is unknown. The device appears only if you join it to zigbee2mqtt again. Restoring the old version of the zigbee2mqtt database does not help. The coordinator loses the device permanently.
What did you expect to happen
How to reproduce it (minimal and precise)
Nothing, Common use.
Debug info
Zigbee2MQTT version: 1.16.1
Adapter hardware: CC2538 as coordinator, CC2531 as routers.
Adapter firmware version: "maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20200211,"transportrev":2},"type":"zStack30x"
The text was updated successfully, but these errors were encountered: