I have a set of Danfoss Ally thermostats in my home.
Some of them lose connection on a regular basis.
Did anyone else have this issue?
Hi can you share some logs?
Hi,
thanks for your quick response.
Is there any way to filter the log for specific devices? I don’t want to drop a huge log on you here with lots of useless information in it.
Using grep I was able to extract this:
14:31:31:994 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:015 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:115 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:223 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:319 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:420 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:566 aps request id: 143 prf: 0x0000 cl: 0x0001 timeout NOT confirmed to 0xB4E3F9FFFED43572 (0xB0D7)
14:31:32:620 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:720 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:819 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265519 s
14:31:32:919 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:088 aps request id: 155 prf: 0x0000 cl: 0x0001 timeout NOT confirmed to 0xB4E3F9FFFED43572 (0xB0D7)
14:31:33:133 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:230 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:315 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:419 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:575 aps request id: 168 prf: 0x0000 cl: 0x0001 timeout NOT confirmed to 0xB4E3F9FFFED43572 (0xB0D7)
14:31:33:689 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:715 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:816 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265520 s
14:31:33:930 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:094 aps request id: 178 prf: 0x0000 cl: 0x0001 timeout NOT confirmed to 0xB4E3F9FFFED43572 (0xB0D7)
14:31:34:133 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:217 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:327 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:412 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:516 aps request id: 194 prf: 0x0000 cl: 0x0001 timeout NOT confirmed to 0xB4E3F9FFFED43572 (0xB0D7)
14:31:34:692 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:712 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:822 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265521 s
14:31:34:916 aps request id: 203 prf: 0x0000 cl: 0x0001 timeout NOT confirmed to 0xB4E3F9FFFED43572 (0xB0D7)
14:31:35:021 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:138 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:221 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:316 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:446 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:515 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:660 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:719 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:815 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265522 s
14:31:35:925 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265523 s
14:31:36:024 max transmit errors for node 0xB4E3F9FFFED43572, last seen by neighbors 265523 s
Hi what version are you on? Can you try 2.19.3?
Was this fixed in the latest version? I’m on 2.19.1, because I am running the Homeasssitant Addon for which I think this is the latest version.
In 2.19.3 there’s a fix for the queue locking up and devices getting disconnected.
Can you provide the full log of this?
I’ll update now and then give you an update. Thanks 
1 Like
Hi, same problem here. Works for a couple of hours and than it gets disconnected. Battery out and in and it works again for a couple of hours. I am on 2.19.3-beta, sames issue. Firmware is on RaspBee II 26780700. Most of them connect to Busch Jaeger Swiches, but i see the issue also on other routers.
Same problem here. 
But the problem only appears on 1/3 TRVs located in one room directly beside each other. And only one at a time is not reachable. With a powercycle (remove batteries) it is coming back.
The other TRVs (6) are working fine so far.
I also saw at the zigbee2mqtt GitHub a similar problem. May it helps to resolve.
https://github.com/Koenkk/zigbee2mqtt/issues/13478