Deconz - Aqara Zigbee sensors are not refreshed for hours and keep a static state

[MonkeyTrunky]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

I am using Home Assistant OS on a Raspberry Pi 4 with deCONZ integration, deCONZ Addon and a RaspBee II Gateway. All worked fine for some years.

Suddenly all the Aqara temperature and humidty sensor didn't refresh anymore and kept a static state. They were not shown as unavailable but the state has not changed for hours.

The zigbee temperature sensors (integrated via deCONZ and raspbee II) are not refreshed. I don't have an explanation for this.

All connected temperature sensors stay at a static value at the same time. Shutting down Home Assistant and power cycle the hardware helps for a certain time but the problem is occurring again.

I have other devices in the network that are working fine. LIDL window sensor, LIDL switches, Philips Hue Dimmers, IKEA Styrbar Dimmers, IKEA blinds. --> The only issue is with the Aqara Multisensors and motion sensors.

Steps to reproduce the behavior

1. Checked HA version --> Home Assistant OS latest stable version (2024.10.1) - Addon up to date.

2. I realized that the firmware of the RaspBee II was not up to date. I decided to migrate to a ConBee III and use the RaspBee II for another network and make the firmware update later.

3. I've flashed the latest firmware (26530900) to the ConBee III and uploaded the backup to it. I had to manually connect the sensors again. It worked for some minutes or hours and then I observed the same behavior -> static values.

4. After monitoring this for 1 day, I changed the Zigbee channel from 15 to 20 and monitored it for another day. I did not notice any improvement.

Expected behavior

Regularly refreshed values like usually at least after firmware update.

Screenshots

Environment

• Host system: (Raspberry Pi )
• Running method: Home Assistant OS, deCONZ Integration and Addon
• Firmware version: (26530900)
• deCONZ version: (2.28.1)
• Device: ConBee III / RaspBee II (both with same issue)
• Do you use an USB extension cable: yes
• Is there any other USB or serial devices connected to the host system? If so: Which? - SSD hard drive

deCONZ Logs

00:14:32:517 ZCL attribute report 0x00158D000802B149 for cluster: 0x0000, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:14:42:665 ZCL attribute report 0x0C4314FFFE53A42D for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:15:01:951 ZCL attribute report 0x00158D0007E0B655 for cluster: 0x0000, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:15:02:268 ZCL attribute report 0x001788010C2AA81D for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:15:22:503 ZCL attribute report 0x0017880108F48347 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
00:15:30:661 ZCL attribute report 0x84FD27FFFECF6AFA for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:15:43:448 ZCL attribute report 0x60A423FFFE053761 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:16:02:252 ZCL attribute report 0x00158D0008378574 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:02:332 ZCL attribute report 0x00158D0008378574 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:02:411 ZCL attribute report 0x00158D0008378574 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:05:148 ZCL attribute report 0x00158D000AF04E2E for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:05:276 ZCL attribute report 0x00158D000AF04E2E for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:05:323 ZCL attribute report 0x00158D000AF04E2E for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:31:350 ZCL attribute report 0x00158D000AF04630 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:31:396 ZCL attribute report 0x00158D000AF04630 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:31:411 ZCL attribute report 0x00158D000AF04630 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:49:908 ZCL attribute report 0x84FD27FFFED0DFCE for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:16:52:397 ZCL attribute report 0x00158D0007DF8A99 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:52:445 ZCL attribute report 0x00158D0007DF8A99 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:52:461 ZCL attribute report 0x00158D0007DF8A99 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
127.0.0.1: new handler Process
127.0.0.1 - - [11/Oct/2024 00:21:45] "GET //websockify HTTP/1.1" 101 -
127.0.0.1 - - [11/Oct/2024 00:21:45] 127.0.0.1: Plain non-SSL (ws://) WebSocket connection
127.0.0.1 - - [11/Oct/2024 00:21:45] 127.0.0.1: Path: '/websockify'
127.0.0.1 - - [11/Oct/2024 00:21:45] connecting to: 127.0.0.1:5900
127.0.0.1 - - [11/Oct/2024 00:28:07] 127.0.0.1:5900: Client closed connection
127.0.0.1 - - [11/Oct/2024 00:28:07] 127.0.0.1:5900: Closed target
00:17:16:296 ZCL attribute report 0xB4E3F9FFFE786606 for cluster: 0x0006, ep172.30.32.2 - - [11/Oct/2024:00:28:07 +0200] "GET /novnc/websockify HTTP/1.1" 101 1457179 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0"
: 0x0B, frame control: 0x18, mfcode: 0x0000
00:17:33:820 0x84FD27FFFED0DFCE found group 0xFFF0
00:17:33:820 0x84FD27FFFED0DFCE found group 0x001D
00:17:35:180 ZCL attribute report 0x00158D000AF008E3 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:17:35:245 ZCL attribute report 0x00158D000AF008E3 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:17:35:277 ZCL attribute report 0x00158D000AF008E3 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:17:36:172 0x84FD27FFFECF6AFA found group 0xFFF0
00:18:47:750 ZCL attribute report 0x60A423FFFE050416 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:18:51:350 ZCL attribute report 0x842E14FFFEE1BDD2 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:18:52:550 ZCL attribute report 0x60A423FFFE0040D1 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:19:45:599 ZCL attribute report 0x0C4314FFFE53A42D for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:19:47:279 ZCL attribute report 0x0C4314FFFE53A42D for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:20:01:255 ZCL attribute report 0x001788010C2AA81D for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:20:23:646 ZCL attribute report 0x0017880108F48347 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
00:20:34:300 ZCL attribute report 0x84FD27FFFECF6AFA for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:20:46:139 ZCL attribute report 0x60A423FFFE053761 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:21:49:754 ZCL attribute report 0x50325FFFFE243327 for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:21:53:177 ZCL attribute report 0x84FD27FFFED0DFCE for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:22:00:125 ZCL attribute report 0x00158D000AF04664 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:22:00:173 ZCL attribute report 0x00158D000AF04664 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:22:00:188 ZCL attribute report 0x00158D000AF04664 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:22:18:917 ZCL attribute report 0xB4E3F9FFFE786606 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:23:07:156 binding for cluster 0x0006 of 0x84FD27FFFED0DFCE exists (verified by reporting)
00:23:07:156 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x84FD27FFFED0DFCE (seems to be active)
00:23:50:211 ZCL attribute report 0x60A423FFFE050416 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:23:55:660 ZCL attribute report 0x60A423FFFE0040D1 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:23:56:237 ZCL attribute report 0x842E14FFFEE1BDD2 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:24:48:614 ZCL attribute report 0x0C4314FFFE53A42D for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:24:50:165 ZCL attribute report 0x0C4314FFFE53A42D for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:25:00:227 ZCL attribute report 0x001788010C2AA81D for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:25:23:900 ZCL attribute report 0x0017880108F48347 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
00:25:37:866 ZCL attribute report 0x84FD27FFFECF6AFA for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:25:48:937 ZCL attribute report 0x60A423FFFE053761 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:26:56:018 ZCL attribute report 0x84FD27FFFED0DFCE for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:27:21:557 ZCL attribute report 0xB4E3F9FFFE786606 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:28:52:708 ZCL attribute report 0x60A423FFFE050416 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:28:57:893 ZCL attribute report 0x842E14FFFEE1BDD2 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:28:58:964 ZCL attribute report 0x60A423FFFE0040D1 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:29:16:635 ZCL attribute report 0x00158D000802B149 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:29:16:666 ZCL attribute report 0x00158D000802B149 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:29:16:746 ZCL attribute report 0x00158D000802B149 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:29:26:785 ZCL attribute report 0x00158D0007DF8A99 for cluster: 0x0000, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:29:51:593 ZCL attribute report 0x0C4314FFFE53A42D for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:29:59:132 ZCL attribute report 0x001788010C2AA81D for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:30:24:405 ZCL attribute report 0x0017880108F48347 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
00:30:41:555 ZCL attribute report 0x84FD27FFFECF6AFA for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:30:51:630 ZCL attribute report 0x60A423FFFE053761 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:31:08:188 remove dead link for (4F7, 7EBF)
00:31:09:157 binding for cluster 0x0006 of 0x60A423FFFE053761 exists (verified by reporting)
00:31:09:157 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x60A423FFFE053761 (seems to be active)
00:31:11:156 binding for cluster 0x0006 of 0x842E14FFFEE1BDD2 exists (verified by reporting)
00:31:11:156 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x842E14FFFEE1BDD2 (seems to be active)
00:31:11:295 0x60A423FFFE053761 found group 0xFFF0
00:31:59:078 ZCL attribute report 0x84FD27FFFED0DFCE for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:32:24:237 ZCL attribute report 0xB4E3F9FFFE786606 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:32:38:929 ZCL attribute report 0x00158D000AF008E3 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:32:39:137 ZCL attribute report 0x00158D000AF008E3 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:32:57:895 ZCL attribute report 0x00158D000AF045FA for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:32:57:926 ZCL attribute report 0x00158D000AF045FA for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:32:57:958 ZCL attribute report 0x00158D000AF045FA for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:33:45:079 0x842E14FFFEE1BDD2 found group 0xFFF0
00:33:45:079 0x842E14FFFEE1BDD2 found group 0x0014
00:33:45:156 binding for cluster 0x0006 of 0x84FD27FFFECF6AFA exists (verified by reporting)
00:33:45:156 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x84FD27FFFECF6AFA (seems to be active)
00:33:56:864 ZCL attribute report 0x60A423FFFE050416 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:34:01:232 ZCL attribute report 0x842E14FFFEE1BDD2 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:34:03:882 ZCL attribute report 0x60A423FFFE0040D1 for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:34:36:724 ZCL attribute report 0x00158D000AF04630 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:34:36:740 ZCL attribute report 0x00158D000AF04630 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:34:54:604 ZCL attribute report 0x0C4314FFFE53A42D for cluster: 0x0006, ep: 0x0B, frame control: 0x18, mfcode: 0x0000
00:34:58:023 ZCL attribute report 0x001788010C2AA81D for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:35:01:143 ZCL attribute report 0x00158D0008378574 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:35:01:207 ZCL attribute report 0x00158D0008378574 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000

Additional context

Network size: 59 devices
Gateway: 1
Brands: Aqara, LIDL, Philips Hue, IKEA

[MonkeyTrunky]

Since I needed a running Zigbee network again quickly, I switched to zigbee2mqtt and purchased a Sonoff ZB Dongle-E (EFR32MG21) and upgraded it to EmberZNet 7.4.4.

deCONZ and z2m are running in parallel at the moment, as I still have to add some devices to the Sonoff gateway that are still connected to the Conbee III. I have placed the two gateways at some distance from each other.

So far, everything has been very stable despite the same conditions as the Conbee III in terms of installation position, number of routers and distances. The framework conditions cannot be responsible for the static values that the Conbee III delivered.

[TheNON75]

Hi, can you try downgrading Deconz to 2.22.00 or something similar but far away enough from your recent version? In my experiences older versions run aqara reporting properly.

[bluemoehre]

The screenshots and description look similar to my current network issues, which are related to #7935.

@MonkeyTrunky maybe you can check if your issues are caused by the DDF problem as well? (At least I am in the same situation as you; got the Sonoff Dongle-E today, struggled it to v7.4.4; now started moving nodes into the new network - what a pain)

[MonkeyTrunky]

Hi, can you try downgrading Deconz to 2.22.00 or something similar but far away enough from your recent version? In my experiences older versions run aqara reporting properly.

Hi,

Unfortunately I cannot do as suggested. I struggled for weeks finding a solution and asked the deCONZ support several times for help. I haven't received an answer at all.

After this experience, I switched to zigbee2mqtt with the Sonoff ZB Dongle-E. Everything works fine now. As the heating season started and I was dependent on the room temperatures, I didn't have time to wait any longer for a response from Dresden Elektronik.

And I refuse to downgrade to older firmware. In my opinion, this is not the right approach. The aim should be to keep the current firmware compatible. If Dresden Elektronik has this sensor in its own compatibility list, then it should also work. Otherwise it should no longer be listed there.

[MonkeyTrunky]

The screenshots and description look similar to my current network issues, which are related to #7935.

@MonkeyTrunky maybe you can check if your issues are caused by the DDF problem as well? (At least I am in the same situation as you; got the Sonoff Dongle-E today, struggled it to v7.4.4; now started moving nodes into the new network - what a pain)

@bluemoehre Thank you for sharing your report. I hope Dresden Elektronik is going to fix it. It should be in their interest. And I agree with you: I also think this should be top priority. In my opinion this is a bug. Maybe older firmware can fix it, but this is not the way I want to go. Apart from that, I'm pretty excited about how powerful zibee2mqtt is.

[TheNON75]

@MonkeyTrunky
Hi, I did not say to downgrade firmware. I was talking about software version, the two things are different kind of things. Firmware is on the stick, software runs on your computer. With docker it is just 1-2 minutes of total effort to downgrade.
Anyhow you have the solution you were looking for and it is great as you won't suffer.

[MonkeyTrunky]

@TheNON75
Hi,
Aha, then I misunderstood. That would of course be an option. You're right, I now have a solution that I'm happy with. Thank you for your advice and the patience.