Aqara Temp: temperature returns same value for weeks

[KatyPurry]

Describe the bug

The temperature of the device returns same temperature for weeks. I have this behavior with 2 of 4 Aqara Temperature Humidity Sensor. Only solution is to remove device from Phoscon and add again. It happened in may first time.

The behavior happened at the same time for both devices (20th august).

Steps to reproduce the behavior

Seems random. Didn't found a schema

Expected behavior

True values

Screenshots

This is the example in Eve App :

Environment

• Host system: unRAID
• Running method: Marthoc Docker container
• Firmware version: 26700700
• deCONZ version: 2.12.6
• Device: ConBee II
• Do you use an USB extension cable: Yes
• Is there any other USB or serial devices connected to the host system? No

deCONZ Logs

Last 30 mins of logs :

00:09:55:488 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x842E14FFFE074363 (seems to be active)
00:09:55:489 binding for cluster 0x0008 of 0x842E14FFFE074363 exists (verified by reporting)
00:09:55:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x842E14FFFE074363 (seems to be active)
00:09:55:489 binding for cluster 0x0300 of 0x842E14FFFE074363 exists (verified by reporting)
00:09:55:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x842E14FFFE074363 (seems to be active)
00:09:55:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0x842E14FFFE074363 (seems to be active)
00:09:55:489 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0x842E14FFFE074363 (seems to be active)
00:09:55:489 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x842E14FFFE074363 (seems to be active)
00:09:56:026 verified group capacity: 255 and group count: 1 of LightNode 0x842e14fffe074363
00:09:56:026 0x842e14fffe074363 found group 0xFFF0
00:09:57:488 binding for cluster 0x0000 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:09:57:489 binding for cluster 0x0006 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:09:57:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:09:57:489 binding for cluster 0x0008 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:09:57:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:09:57:489 binding for cluster 0x0300 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:09:57:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE61F99C (wait reading or unsupported)
00:09:57:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:09:57:489 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:09:57:489 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:09:57:561 verified group capacity: 255 and group count: 1 of LightNode 0xccccccfffe61f99c
00:09:57:561 0xccccccfffe61f99c found group 0xFFF0
00:09:59:489 binding for cluster 0x0000 of 0x000B3CFFFEF09DCB exists (verified by reporting)
00:09:59:489 binding for cluster 0x0006 of 0x000B3CFFFEF09DCB exists (verified by reporting)
00:09:59:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x000B3CFFFEF09DCB (seems to be active)
00:09:59:822 verified group capacity: 255 and group count: 1 of LightNode 0x000b3cfffef09dcb
00:09:59:822 0x000b3cfffef09dcb found group 0xFFF0
00:10:00:537 Bind response success for 0x000b3cfffef09dcb ep: 0x01 cluster: 0x0008
00:10:00:537 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x000B3CFFFEF09DCB (seems to be active)
00:10:04:489 binding for cluster 0x0000 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:10:04:489 binding for cluster 0x0006 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:10:04:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE620174 (seems to be active)
00:10:04:489 binding for cluster 0x0008 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:10:04:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE620174 (seems to be active)
00:10:04:489 binding for cluster 0x0300 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:10:04:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE620174 (wait reading or unsupported)
00:10:04:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE620174 (seems to be active)
00:10:04:490 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE620174 (seems to be active)
00:10:04:490 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE620174 (seems to be active)
00:10:05:069 verified group capacity: 255 and group count: 1 of LightNode 0xccccccfffe620174
00:10:05:069 0xccccccfffe620174 found group 0xFFF0
00:10:07:489 binding for cluster 0x0000 of 0x086BD7FFFE426344 exists (verified by reporting)
00:10:07:489 binding for cluster 0x0006 of 0x086BD7FFFE426344 exists (verified by reporting)
00:10:07:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x086BD7FFFE426344 (seems to be active)
00:10:08:589 Bind response success for 0x086bd7fffe426344 ep: 0x01 cluster: 0x0008
00:10:08:589 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x086BD7FFFE426344 (seems to be active)
00:10:09:488 binding for cluster 0x0000 of 0x086BD7FFFE08981B exists (verified by reporting)
00:10:09:488 binding for cluster 0x0006 of 0x086BD7FFFE08981B exists (verified by reporting)
00:10:09:488 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x086BD7FFFE08981B (seems to be active)
00:10:09:534 Bind response success for 0x086bd7fffe08981b ep: 0x01 cluster: 0x0008
00:10:09:534 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x086BD7FFFE08981B (seems to be active)
00:10:11:489 binding for cluster 0x0000 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:10:11:489 binding for cluster 0x0006 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:10:11:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:10:11:489 binding for cluster 0x0008 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:10:11:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:10:11:489 binding for cluster 0x0300 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:10:11:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE9E7882 (wait reading or unsupported)
00:10:11:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:10:11:489 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:10:11:489 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:10:13:489 binding for cluster 0x0000 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:10:13:489 binding for cluster 0x0006 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:10:13:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:10:13:489 binding for cluster 0x0008 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:10:13:490 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:10:13:490 binding for cluster 0x0300 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:10:13:490 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE61FF61 (wait reading or unsupported)
00:10:13:490 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:10:13:490 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:10:13:490 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:10:14:065 verified group capacity: 255 and group count: 1 of LightNode 0xccccccfffe61ff61
00:10:14:065 0xccccccfffe61ff61 found group 0xFFF0
00:10:35:520 Device TTL 5335 s flags: 0x7
00:11:02:650 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:11:12:589 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:11:35:518 Device TTL 5275 s flags: 0x7
00:11:43:501 GW firmware version: 0x26700700
00:11:43:501 GW firmware version is up to date: 0x26700700
00:11:58:006 ZCL attribute report 0x086BD7FFFE426344 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:12:35:520 Device TTL 5214 s flags: 0x7
00:12:56:992 ZCL attribute report 0x00158D00045F9452 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:12:56:992 0x00158D00045F9452 extract Xiaomi special attribute 0xFF01
00:12:56:992 01 battery 2985 (0x0BA9)
00:12:56:992 03 Device temperature 25 °C
00:12:56:992 04 unknown 17320 (0x43A8)
00:12:56:992 05 RSSI dB (?) 53 (0x0035)
00:12:56:992 06 LQI (?) 4294967296 (0x0100000000)
00:12:56:992 0a Parent NWK 22212 (0x56C4)
00:12:56:993 64 on/off 0
00:12:56:993 0b lightlevel 7 (0x0007)
00:13:35:519 Device TTL 5154 s flags: 0x7
00:14:01:364 ZCL attribute report 0x00158D0006BEE125 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:14:01:364 0x00158D0006BEE125 extract Xiaomi special attribute 0xFF01
00:14:01:364 01 battery 2975 (0x0B9F)
00:14:01:364 03 Device temperature 25 °C
00:14:01:364 04 unknown 5032 (0x13A8)
00:14:01:364 05 RSSI dB (?) 13 (0x000D)
00:14:01:364 06 LQI (?) 4294967296 (0x0100000000)
00:14:01:364 0a Parent NWK 0 (0x0000)
00:14:01:364 64 on/off 0
00:14:34:430 ZCL attribute report 0x0017880104AF5DBA for cluster: 0x0001, ep: 0x02, frame control: 0x18, mfcode: 0x0000
00:14:35:519 Device TTL 5094 s flags: 0x7
00:14:46:634 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:15:35:520 Device TTL 5034 s flags: 0x7
00:15:43:489 GW firmware version: 0x26700700
00:15:43:489 GW firmware version is up to date: 0x26700700
00:16:01:947 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:11:813 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:16:35:522 Device TTL 4974 s flags: 0x7
00:17:35:521 Device TTL 4914 s flags: 0x7
00:18:12:490 ZCL attribute report 0xCCCCCCFFFE9E7882 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:18:28:795 ZCL attribute report 0xCCCCCCFFFE61FF61 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:18:35:521 Device TTL 4854 s flags: 0x7
00:19:35:522 Device TTL 4793 s flags: 0x7
00:19:35:536 ZCL attribute report 0x0017880104AF5DBA for cluster: 0x0001, ep: 0x02, frame control: 0x18, mfcode: 0x0000
00:19:43:489 GW firmware version: 0x26700700
00:19:43:489 GW firmware version is up to date: 0x26700700
00:19:45:893 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:19:54:695 ZCL attribute report 0x00158D0004A01411 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:19:54:695 0x00158D0004A01411 extract Xiaomi special attribute 0xFF01
00:19:54:695 01 battery 3015 (0x0BC7)
00:19:54:695 03 Device temperature 20 °C
00:19:54:695 04 unknown 17320 (0x43A8)
00:19:54:695 05 RSSI dB (?) 40 (0x0028)
00:19:54:695 06 LQI (?) 4294967296 (0x0100000000)
00:19:54:695 0a Parent NWK 0 (0x0000)
00:19:54:695 64 on/off 0
00:20:08:516 ZCL attribute report 0x00158D0006BEE219 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:20:08:516 0x00158D0006BEE219 extract Xiaomi special attribute 0xFF01
00:20:08:516 01 battery 3015 (0x0BC7)
00:20:08:516 03 Device temperature 21 °C
00:20:08:516 04 unknown 17320 (0x43A8)
00:20:08:516 05 RSSI dB (?) 21 (0x0015)
00:20:08:516 06 LQI (?) 4294967296 (0x0100000000)
00:20:08:516 0a Parent NWK 755 (0x02F3)
00:20:08:516 64 on/off 0
00:20:35:518 Device TTL 4733 s flags: 0x7
00:21:01:172 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:21:11:109 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:21:35:518 Device TTL 4673 s flags: 0x7
00:22:21:296 ZCL attribute report 0x000B3CFFFEF09DCB for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:22:35:521 Device TTL 4613 s flags: 0x7
00:23:04:933 ZCL attribute report 0x086BD7FFFE08981B for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:23:35:519 Device TTL 4553 s flags: 0x7
00:23:43:488 GW firmware version: 0x26700700
00:23:43:488 GW firmware version is up to date: 0x26700700
00:24:19:026 ZCL attribute report 0x00158D0004A03EA2 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:24:19:026 0x00158D0004A03EA2 extract Xiaomi special attribute 0xFF01
00:24:19:026 01 battery 2985 (0x0BA9)
00:24:19:026 03 Device temperature 24 °C
00:24:19:026 04 unknown 5032 (0x13A8)
00:24:19:026 05 RSSI dB (?) 65 (0x0041)
00:24:19:027 06 LQI (?) 4294967296 (0x0100000000)
00:24:19:027 0a Parent NWK 0 (0x0000)
00:24:19:027 64 on/off 0
00:24:35:519 Device TTL 4493 s flags: 0x7
00:24:36:630 ZCL attribute report 0x0017880104AF5DBA for cluster: 0x0001, ep: 0x02, frame control: 0x18, mfcode: 0x0000
00:24:45:156 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:25:35:519 Device TTL 4432 s flags: 0x7
00:26:00:437 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:26:10:349 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:26:35:519 Device TTL 4372 s flags: 0x7
00:27:35:518 Device TTL 4312 s flags: 0x7
00:27:43:489 GW firmware version: 0x26700700
00:27:43:489 GW firmware version is up to date: 0x26700700
00:28:35:522 Device TTL 4252 s flags: 0x7
00:29:33:195 ZCL attribute report 0x086BD7FFFE413B70 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:29:35:520 Device TTL 4192 s flags: 0x7
00:29:37:754 ZCL attribute report 0x0017880104AF5DBA for cluster: 0x0001, ep: 0x02, frame control: 0x18, mfcode: 0x0000
00:29:44:381 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:29:59:488 ZCL attribute report 0x086BD7FFFE08981B for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:30:31:867 ZCL attribute report 0x00158D00058896EF for cluster: 0x0000, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:30:31:867 0x00158D00058896EF extract Xiaomi special attribute 0xFF01
00:30:31:867 01 battery 2995 (0x0BB3)
00:30:31:867 04 unknown 17320 (0x43A8)
00:30:31:867 05 RSSI dB (?) 14 (0x000E)
00:30:31:867 06 LQI (?) 4294967296 (0x0100000000)
00:30:31:868 64 temperature 1466
00:30:31:868 65 humidity 8966
00:30:31:868 66 pressure 100276 (1003)
00:30:31:868 0a Parent NWK 18400 (0x47E0)
00:30:35:520 Device TTL 4132 s flags: 0x7
00:30:58:634 ZCL attribute report 0x086BD7FFFE426344 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:30:59:698 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:31:00:963 ZCL attribute report 0xCCCCCCFFFE61FF61 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:31:01:794 ZCL attribute report 0xCCCCCCFFFE9E7882 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:31:02:036 ZCL attribute report 0xCCCCCCFFFE61F99C for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:31:02:445 ZCL attribute report 0xCCCCCCFFFE620174 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:31:09:638 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:31:35:522 Device TTL 4071 s flags: 0x7
00:31:43:490 GW firmware version: 0x26700700
00:31:43:490 GW firmware version is up to date: 0x26700700
00:32:35:521 Device TTL 4011 s flags: 0x7
00:33:15:072 ZCL attribute report 0x086BD7FFFE413B70 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:33:35:518 Device TTL 3951 s flags: 0x7
00:34:04:006 ZCL attribute report 0x00158D0006C04B99 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:34:04:007 0x00158D0006C04B99 extract Xiaomi special attribute 0xFF01
00:34:04:007 01 battery 3055 (0x0BEF)
00:34:04:007 03 Device temperature 18 °C
00:34:04:007 04 unknown 5032 (0x13A8)
00:34:04:007 05 RSSI dB (?) 28 (0x001C)
00:34:04:007 06 LQI (?) 4294967296 (0x0100000000)
00:34:04:007 0a Parent NWK 43982 (0xABCE)
00:34:04:007 64 on/off 0
00:34:20:871 ZCL attribute report 0xCCCCCCFFFE61FF61 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:21:083 ZCL attribute report 0xCCCCCCFFFE61F99C for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:21:233 ZCL attribute report 0xCCCCCCFFFE9E7882 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:21:279 ZCL attribute report 0xCCCCCCFFFE620174 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:25:873 ZCL attribute report 0xCCCCCCFFFE61FF61 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:26:083 ZCL attribute report 0xCCCCCCFFFE61F99C for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:26:236 ZCL attribute report 0xCCCCCCFFFE9E7882 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:26:281 ZCL attribute report 0xCCCCCCFFFE620174 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:34:35:519 Device TTL 3891 s flags: 0x7
00:34:38:848 ZCL attribute report 0x0017880104AF5DBA for cluster: 0x0001, ep: 0x02, frame control: 0x18, mfcode: 0x0000
00:34:43:679 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:34:51:757 ZCL attribute report 0xCCCCCCFFFE620174 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:35:26:427 ZCL attribute report 0x000B3CFFFEF09DCB for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:35:35:030 ZCL attribute report 0xCCCCCCFFFE61F99C for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
00:35:35:523 Device TTL 3831 s flags: 0x7
00:35:43:530 GW firmware version: 0x26700700
00:35:43:531 GW firmware version is up to date: 0x26700700
00:35:58:997 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:36:08:870 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:36:17:525 ZCL attribute report 0x00158D0006BEC80E for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:36:17:525 0x00158D0006BEC80E extract Xiaomi special attribute 0xFF01
00:36:17:525 01 battery 3015 (0x0BC7)
00:36:17:525 03 Device temperature 21 °C
00:36:17:525 04 unknown 17320 (0x43A8)
00:36:17:525 05 RSSI dB (?) 24 (0x0018)
00:36:17:526 06 LQI (?) 4294967296 (0x0100000000)
00:36:17:526 0a Parent NWK 0 (0x0000)
00:36:17:526 64 on/off 0
00:36:35:521 Device TTL 3771 s flags: 0x7
00:36:59:247 Invalid admin password hash: $1$8282jdkm$w.o6XjJEGLzAYkVqLPAYx1
00:37:02:053 created username: F78E3AA3AB, devicetype: Phoscon#B1888x1251
00:37:03:358 New websocket 192.168.1.192:63496 (state: 3)
00:37:07:675 Websocket disconnected 192.168.1.192:63496, state: 0, close-code: 1001, reason:
00:37:08:825 New websocket 192.168.1.192:63502 (state: 3)
00:37:11:156 Websocket disconnected 192.168.1.192:63502, state: 0, close-code: 1001, reason:
00:37:12:854 New websocket 192.168.1.192:63547 (state: 3)
00:37:35:522 Device TTL 3711 s flags: 0x7
00:37:43:128 Websocket disconnected 192.168.1.192:63547, state: 0, close-code: 1001, reason:
00:38:14:076 verified group capacity: 255 and group count: 1 of LightNode 0x086bd7fffe426344
00:38:14:076 0x086bd7fffe426344 found group 0xFFF0
00:38:17:489 binding for cluster 0x0000 of 0x086BD7FFFE413B70 exists (verified by reporting)
00:38:17:489 binding for cluster 0x0006 of 0x086BD7FFFE413B70 exists (verified by reporting)
00:38:17:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x086BD7FFFE413B70 (seems to be active)
00:38:17:808 verified group capacity: 255 and group count: 1 of LightNode 0x086bd7fffe413b70
00:38:17:808 0x086bd7fffe413b70 found group 0xFFF0
00:38:18:570 Bind response success for 0x086bd7fffe413b70 ep: 0x01 cluster: 0x0008
00:38:18:570 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x086BD7FFFE413B70 (seems to be active)
00:38:35:518 Device TTL 3650 s flags: 0x7
00:38:50:810 verified group capacity: 255 and group count: 1 of LightNode 0x086bd7fffe08981b
00:38:50:810 0x086bd7fffe08981b found group 0xFFF0
00:38:56:814 verified group capacity: 255 and group count: 1 of LightNode 0xccccccfffe9e7882
00:38:56:814 0xccccccfffe9e7882 found group 0xFFF0
00:39:03:482 ZCL attribute report 0x00158D0006BEC7E4 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
00:39:03:482 0x00158D0006BEC7E4 extract Xiaomi special attribute 0xFF01
00:39:03:482 01 battery 3035 (0x0BDB)
00:39:03:482 03 Device temperature 21 °C
00:39:03:482 04 unknown 5032 (0x13A8)
00:39:03:482 05 RSSI dB (?) 24 (0x0018)
00:39:03:482 06 LQI (?) 4294967296 (0x0100000000)
00:39:03:482 0a Parent NWK 755 (0x02F3)
00:39:03:482 64 on/off 0
00:39:10:150 New websocket 192.168.1.192:63666 (state: 3)
00:39:13:305 Websocket disconnected 192.168.1.192:63666, state: 0, close-code: 1001, reason:
00:39:14:556 New websocket 192.168.1.192:63670 (state: 3)
00:39:35:518 Device TTL 3590 s flags: 0x7
00:39:39:944 ZCL attribute report 0x0017880104AF5DBA for cluster: 0x0001, ep: 0x02, frame control: 0x18, mfcode: 0x0000
00:39:42:919 ZCL attribute report 0x842E14FFFE074363 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
00:39:43:490 GW firmware version: 0x26700700
00:39:43:490 GW firmware version is up to date: 0x26700700
00:39:56:765 verified group capacity: 24 and group count: 1 of LightNode 0x00178801041897b0
00:39:56:766 0x00178801041897b0 found group 0xFFF0
00:39:59:489 binding for cluster 0x0006 of 0x842E14FFFE074363 exists (verified by reporting)
00:39:59:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x842E14FFFE074363 (seems to be active)
00:39:59:489 binding for cluster 0x0008 of 0x842E14FFFE074363 exists (verified by reporting)
00:39:59:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x842E14FFFE074363 (seems to be active)
00:39:59:489 binding for cluster 0x0300 of 0x842E14FFFE074363 exists (verified by reporting)
00:39:59:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x842E14FFFE074363 (seems to be active)
00:39:59:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0x842E14FFFE074363 (seems to be active)
00:39:59:489 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0x842E14FFFE074363 (seems to be active)
00:39:59:489 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x842E14FFFE074363 (seems to be active)
00:39:59:785 verified group capacity: 255 and group count: 1 of LightNode 0x842e14fffe074363
00:39:59:785 0x842e14fffe074363 found group 0xFFF0
00:40:04:488 binding for cluster 0x0000 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:40:04:488 binding for cluster 0x0006 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:40:04:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:40:04:489 binding for cluster 0x0008 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:40:04:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:40:04:489 binding for cluster 0x0300 of 0xCCCCCCFFFE61F99C exists (verified by reporting)
00:40:04:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE61F99C (wait reading or unsupported)
00:40:04:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:40:04:489 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:40:04:489 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE61F99C (seems to be active)
00:40:05:061 verified group capacity: 255 and group count: 1 of LightNode 0xccccccfffe61f99c
00:40:05:061 0xccccccfffe61f99c found group 0xFFF0
00:40:06:488 binding for cluster 0x0000 of 0x000B3CFFFEF09DCB exists (verified by reporting)
00:40:06:488 binding for cluster 0x0006 of 0x000B3CFFFEF09DCB exists (verified by reporting)
00:40:06:488 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x000B3CFFFEF09DCB (seems to be active)
00:40:07:308 verified group capacity: 255 and group count: 1 of LightNode 0x000b3cfffef09dcb
00:40:07:309 0x000b3cfffef09dcb found group 0xFFF0
00:40:07:570 Bind response success for 0x000b3cfffef09dcb ep: 0x01 cluster: 0x0008
00:40:07:570 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x000B3CFFFEF09DCB (seems to be active)
00:40:10:489 binding for cluster 0x0000 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:40:10:489 binding for cluster 0x0006 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:40:10:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE620174 (seems to be active)
00:40:10:489 binding for cluster 0x0008 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:40:10:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE620174 (seems to be active)
00:40:10:489 binding for cluster 0x0300 of 0xCCCCCCFFFE620174 exists (verified by reporting)
00:40:10:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE620174 (wait reading or unsupported)
00:40:10:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE620174 (seems to be active)
00:40:10:490 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE620174 (seems to be active)
00:40:10:490 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE620174 (seems to be active)
00:40:11:061 verified group capacity: 255 and group count: 1 of LightNode 0xccccccfffe620174
00:40:11:061 0xccccccfffe620174 found group 0xFFF0
00:40:13:488 binding for cluster 0x0000 of 0x086BD7FFFE426344 exists (verified by reporting)
00:40:13:488 binding for cluster 0x0006 of 0x086BD7FFFE426344 exists (verified by reporting)
00:40:13:488 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x086BD7FFFE426344 (seems to be active)
00:40:14:519 Bind response success for 0x086bd7fffe426344 ep: 0x01 cluster: 0x0008
00:40:14:519 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x086BD7FFFE426344 (seems to be active)
00:40:15:489 binding for cluster 0x0000 of 0x086BD7FFFE08981B exists (verified by reporting)
00:40:15:489 binding for cluster 0x0006 of 0x086BD7FFFE08981B exists (verified by reporting)
00:40:15:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x086BD7FFFE08981B (seems to be active)
00:40:15:522 Bind response success for 0x086bd7fffe08981b ep: 0x01 cluster: 0x0008
00:40:15:522 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x086BD7FFFE08981B (seems to be active)
00:40:17:489 binding for cluster 0x0000 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:40:17:489 binding for cluster 0x0006 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:40:17:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:40:17:489 binding for cluster 0x0008 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:40:17:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:40:17:489 binding for cluster 0x0300 of 0xCCCCCCFFFE9E7882 exists (verified by reporting)
00:40:17:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE9E7882 (wait reading or unsupported)
00:40:17:489 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:40:17:490 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:40:17:490 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE9E7882 (seems to be active)
00:40:19:489 binding for cluster 0x0000 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:40:19:489 binding for cluster 0x0006 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:40:19:489 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:40:19:489 binding for cluster 0x0008 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:40:19:489 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:40:19:489 binding for cluster 0x0300 of 0xCCCCCCFFFE61FF61 exists (verified by reporting)
00:40:19:489 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xCCCCCCFFFE61FF61 (wait reading or unsupported)
00:40:19:490 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:40:19:490 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:40:19:490 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCCCCCCFFFE61FF61 (seems to be active)
00:40:20:063 verified group capacity: 255 and group count: 1 of LightNode 0xccccccfffe61ff61
00:40:20:063 0xccccccfffe61ff61 found group 0xFFF0
00:40:35:522 Device TTL 3530 s flags: 0x7

[Mimiix]

As this is not a bug as per #5113, Im closing this issue.

Feel free to post on the forums https://forum.phoscon.de

And also: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Xiaomi:-Lost-devices-or-functional-issues