Hello!
I recently migrated from marthoc/deconz to the community deconz image and I’m experiencing an odd behaviour from all my xiaomi devices. (I already posted this issue in the docker community but it seems this is not related to the docker image).
My network is made with 17 xiaomi devices (multisensors, motion sensors and contact sensors) and a bunch of Ikea Tradfri devices (remotes, motion sensors, lights).
I use to reboot deconz every night on a cronjob and after every reboot - in the UI - ikea tradfri devices are immediately available and with their correct state, while xiaomi devices are all unavailable until their state changes (exmotion detected, temperature changes, etc). After the first xiaomi device is available again in the UI, slowly all other devices become available, but with a wrong state: all binary_sensors (ex. contact, motion) appear as “on” even if they’re really off (door closed appear as open in Deconz UI).
In practice:
3am: deconz restarts on cronjob
4am: homeassistant restarts on cronjob
7am: I wake up and all the motion sensors are “on” and my front door appears as open, with a heart attack included
I tried everything:
unpair-repair devices
changed batteries
reset devices through VNC
repull docker image
Result: none of this changed the behavior
This is my setup:
Host system: NUC (NUC6CAYH) with Proxmox VE 7.3-3
Running method: Community Docker container running in VM
Firmware version: 264A0700
deCONZ version: 2.19.03
Device: ConBee II
USB extension cable: yes
other USB or serial devices connected to the host system: a couple of ESP32 boards, an UPS (Tecnoware UPS ERA PLUS 1100) and 2 HD storage (WD and Seagate)
Hello
Why restart deconz ?
Sensors are lazy device, so they can stay 1 hour without sending state, and deconz can’t guess it.
but with a wrong state: all binary_sensors (ex. contact, motion) appear as “on” even if they’re really off (door closed appear as open in Deconz UI)
Will be usefull to log events, to see if door sensor are sending state, good or bad, because Xiaomi/Aqara devices send at least 1 report by hour, and you have longer period.
Can be done with phoscon/help/API Information/event but idk the maximum logging session possible.
I used to restart deconz at night since years already, just because I feel like clearing cache would benefit with the VM. By the way, I never had such a behavior from the sensors
here’s my log through docker container (I see no logs at all at phoscon/help/Api Information/events):
[deconzcommunity/deconz] Starting deCONZ...
[deconzcommunity/deconz] Current deCONZ version: 2.19.03
[deconzcommunity/deconz] Web UI port: 80
[deconzcommunity/deconz] Websockets port: 443
[deconzcommunity/deconz] Using options --auto-connect=1 --appdata=/opt/deCONZ --dbg-info=1 --dbg-aps=0 --dbg-zcl=0 --dbg-ddf=0 --dbg-dev=0 --dbg-zdp=0 --dbg-ota=0 --dbg-error=0 --dbg-http=0 --http-port=80 --ws-port=443
[deconzcommunity/deconz] Modifying user and group ID
[deconzcommunity/deconz] Checking device group ID
[deconzcommunity/deconz] VNC port: 5900
tigervncserver: No VNC server running for this user!
Cleaning stale pidfile '/home/deconz/.vnc/deconz.deconz:5900.pid'!
TigerVNC server sessions:
X DISPLAY # RFB PORT # PROCESS ID SERVER
/usr/bin/xauth: file /home/deconz/.Xauthority does not exist
New Xtigervnc server 'deconz.deconz:0 (deconz)' on port 5900 for display :0.
Use xtigervncviewer -SecurityTypes VncAuth,TLSVnc -passwd /home/deconz/.vnc/passwd deconz.deconz:0 to connect to the VNC server.
WebSocket server settings:
- Listen on :6080
- Web server. Web root: /usr/share/novnc
- SSL/TLS support
- Backgrounding (daemon)
[deconzcommunity/deconz] NOVNC port: 6080
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-deconz'
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
20:10:44:642 HTTP Server listen on address 0.0.0.0, port: 80, root: /usr/share/deCONZ/webapp/
20:10:44:658 /opt/deCONZ/config.ini exists and is writeable
20:10:44:658 /opt/deCONZ/zll.db exists and is writeable
20:10:44:780 COM: /dev/ttyACM0 / serialno: , ConBee II
20:10:44:780 ZCLDB init file /opt/deCONZ/zcldb.txt
20:10:44:926 DDF enabled for Gold status
20:10:45:363 gw run mode: normal
20:10:45:363 GW sd-card image version file does not exist: /opt/deCONZ/gw-version
20:10:45:364 DB sqlite version 3.34.1
20:10:45:367 DB PRAGMA page_count: 114
20:10:45:367 DB PRAGMA page_size: 4096
20:10:45:367 DB PRAGMA freelist_count: 5
20:10:45:367 DB file size 466944 bytes, free pages 5
20:10:45:367 DB PRAGMA user_version: 9
20:10:45:367 DB cleanup
20:10:45:368 DB create temporary views
20:10:45:410 DB skip loading sensor Ambiente Cucina 14, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:411 DB skip loading sensor Ambiente Cucina 15, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:411 DB skip loading sensor Porta Ingresso 46, handled by DDF Mijia open/close sensor MCCGQ01LM
20:10:45:411 DB skip loading sensor Contact Clima Cameretta 48, handled by DDF Mijia open/close sensor MCCGQ01LM
20:10:45:412 DB skip loading sensor Porta Bagno 50, handled by DDF Mijia open/close sensor MCCGQ01LM
20:10:45:412 DB skip loading sensor Ambiente Soggiorno 94, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:412 DB skip loading sensor Ambiente Soggiorno 95, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:412 DB skip loading sensor Motion Cucina Xiaomi 80, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:413 DB skip loading sensor Ambiente Balcone 16, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:413 DB skip loading sensor Ambiente Balcone 17, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:413 DB skip loading sensor Ambiente Cameretta 38, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:414 DB skip loading sensor Ambiente Cameretta 39, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:414 DB skip loading sensor Contact Clima Camera 49, handled by DDF Mijia open/close sensor MCCGQ01LM
20:10:45:414 DB skip loading sensor Motion Camera 44, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:414 DB skip loading sensor Motion Camera 43, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:415 DB skip loading sensor Motion Bagno Xiaomi 73, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:415 DB skip loading sensor Motion Ingresso Xiaomi 88, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:415 DB skip loading sensor Motion Soggiorno 62, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:415 DB skip loading sensor Ambiente Bagno 27, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:416 DB skip loading sensor Ambiente Bagno 28, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:416 DB skip loading sensor Contact Clima Soggiorno 53, handled by DDF Mijia open/close sensor MCCGQ01LM
20:10:45:416 DB skip loading sensor Motion Cameretta 36, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:417 DB skip loading sensor Motion Cameretta 35, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:417 DB skip loading sensor Ambiente Camera 41, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:417 DB skip loading sensor Ambiente Camera 42, handled by DDF Aqara temp./hum. sensor WSDCGQ01LM
20:10:45:418 DB skip loading sensor Motion Cucina Xiaomi 81, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:422 DB skip loading sensor Motion Soggiorno 52, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:424 DB skip loading sensor Motion Bagno Xiaomi 74, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:424 DB skip loading sensor Motion Ingresso Xiaomi 87, handled by DDF Aqara motion sensor RTCGQ11LM
20:10:45:426 Started websocket server on 0.0.0.0, port: 443
20:10:45:429 [INFO] - Found file containing button maps. Parsing data...
20:10:45:441 [INFO] - Button maps loaded.
20:10:45:442 found node plugin: libde_rest_plugin.so - REST API Plugin
20:10:45:443 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
20:10:45:454 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
20:10:45:689 LightNode 9: Conbee II added
20:10:45:715 LightNode 13: Luminarie added
20:10:45:719 SensorNode 55 set node 0xec1bbdfffe40aa57
20:10:45:726 LightNode 4: Lampadina Soggiorno added
20:10:45:731 LightNode 8: Ventilatore Bagno added
20:10:45:731 SensorNode 68 set node 0x00158d00032d56e0
20:10:45:731 SensorNode 67 set node 0x00158d00032d56e0
20:10:45:734 LightNode 7: Lampadina Balcone added
20:10:45:737 LightNode 18: CC2531 Router added
20:10:45:738 SensorNode 92 set node 0x00158d0002c7f59c
20:10:45:741 SensorNode 84 set node 0x90fd9ffffede5f0f
20:10:45:747 SensorNode 85 set node 0x000b57fffe329203
20:10:45:749 SensorNode 93 set node 0x90fd9ffffee1084b
20:10:45:752 LightNode 11: Lampadina Cameretta added
20:10:45:755 LightNode 6: Scald. Matr. Caricabatt. Marco added
20:10:45:755 SensorNode 57 set node 0x00158d00036cc111
20:10:45:755 SensorNode 56 set node 0x00158d00036cc111
20:10:45:757 SensorNode 72 set node 0xccccccfffe94039b
20:10:45:766 LightNode 17: Alimentazione TV Soggiorno added
20:10:45:766 SensorNode 40 set node 0x00158d000254c041
20:10:45:766 SensorNode 31 set node 0x00158d000254c041
20:10:45:770 SensorNode 54 set node 0xccccccfffe92eee6
20:10:45:774 LightNode 5: Albero di Natale added
20:10:45:776 SensorNode 82 set node 0x000b57fffe2e2365
20:10:45:779 LightNode 12: Lampadina Camera added
20:10:45:786 LightNode 14: Lampadina Ingresso added
20:10:45:787 SensorNode 32 set node 0x000b57fffe381da2
20:10:45:789 SensorNode 91 set node 0xd0cf5efffe1f2ce2
20:10:45:792 LightNode 16: Alimentazione TV Camera added
20:10:45:797 SensorNode 89 set node 0x00158d00027a7874
20:10:45:798 SensorNode 26 set node 0x000b57fffe362138
20:10:45:802 LightNode 22: Lampadina Bagno added
20:10:45:804 LightNode 19: Lampadina Cucina added
20:10:46:120 DEV no DDF for 0x000B57FFFE362138, modelId: TRADFRI remote control
20:10:46:121 DEV create on-the-fly DDF for 0x000B57FFFE362138
20:10:46:122 DEV no DDF for 0xCCCCCCFFFE94039B, modelId: TRADFRI on/off switch
20:10:46:122 DEV create on-the-fly DDF for 0xCCCCCCFFFE94039B
20:10:46:123 DEV no DDF for 0x000B57FFFE381DA2, modelId: TRADFRI motion sensor
20:10:46:123 DEV create on-the-fly DDF for 0x000B57FFFE381DA2
20:10:46:124 DEV found DDF for 0x90FD9FFFFEDE5F0F, path:
20:10:46:124 DEV found DDF for 0xD0CF5EFFFE1F2CE2, path:
20:10:46:124 DEV found DDF for 0x000B57FFFE329203, path:
20:10:46:125 DEV found DDF for 0xCCCCCCFFFE92EEE6, path:
20:10:46:125 DEV no DDF for 0x00158D00032D56E0, modelId: lumi.plug
20:10:46:125 DEV create on-the-fly DDF for 0x00158D00032D56E0
20:10:46:139 dlg action: Read binding table
20:10:46:227 DEV found DDF for 0x00158D000254C041, path:
20:10:46:228 DEV found DDF for 0x00158D00036CC111, path:
20:10:46:228 DEV found DDF for 0x90FD9FFFFEE1084B, path:
20:10:46:229 DEV found DDF for 0xEC1BBDFFFE40AA57, path:
20:10:46:229 DEV found DDF for 0x000B57FFFE2E2365, path:
20:10:46:234 DEV found DDF for 0x00158D0002C76C57, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq01lm_temp_hum_sensor.json
20:10:46:234 DEV no DDF for 0x000D6FFFFED1A5D9, modelId: TRADFRI control outlet
20:10:46:235 DEV create on-the-fly DDF for 0x000D6FFFFED1A5D9
20:10:46:237 DEV found DDF for 0x00158D00024DD593, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq01lm_openclose_sensor.json
20:10:46:240 DEV found DDF for 0x00158D0002E29B30, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq01lm_openclose_sensor.json
20:10:46:241 DEV no DDF for 0x90FD9FFFFED463D5, modelId: TRADFRI bulb E27 WS opal 980lm
20:10:46:241 DEV create on-the-fly DDF for 0x90FD9FFFFED463D5
20:10:46:244 DEV found DDF for 0x00158D0002913325, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq01lm_openclose_sensor.json
20:10:46:245 DEV no DDF for 0xCCCCCCFFFEB8D62B, modelId: TRADFRI bulb E27 WW 806lm
20:10:46:245 DEV create on-the-fly DDF for 0xCCCCCCFFFEB8D62B
20:10:46:246 DEV no DDF for 0x00124B001936ABF4, modelId: lumi.router
20:10:46:246 DEV create on-the-fly DDF for 0x00124B001936ABF4
20:10:46:251 DEV found DDF for 0x00158D0002C7C1C0, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq01lm_temp_hum_sensor.json
20:10:46:255 DEV found DDF for 0x00158D0002E2E02C, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_rtcgqq11lm_presence_sensor.json
20:10:46:256 DEV found DDF for 0x90FD9FFFFEE94E28, path: /usr/share/deCONZ/devices/ikea/e27_cws_opal_600lm_light.json
20:10:46:260 DEV found DDF for 0x00158D0002C7C22A, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq01lm_temp_hum_sensor.json
20:10:46:264 DEV found DDF for 0x00158D0002BFF8EF, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq01lm_temp_hum_sensor.json
20:10:46:267 DEV found DDF for 0x00158D0002F25205, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq01lm_openclose_sensor.json
20:10:46:272 DEV found DDF for 0x00158D0003494C8F, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_rtcgqq11lm_presence_sensor.json
20:10:46:276 DEV found DDF for 0x00158D0002E99CD7, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_rtcgqq11lm_presence_sensor.json
20:10:46:281 DEV found DDF for 0x00158D000257A026, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_rtcgqq11lm_presence_sensor.json
20:10:46:282 DEV found DDF for 0x086BD7FFFE42BC64, path:
20:10:46:282 DEV no DDF for 0x804B50FFFE132ADF, modelId: TRADFRI bulb E27 WS opal 1000lm
20:10:46:282 DEV create on-the-fly DDF for 0x804B50FFFE132ADF
20:10:46:287 DEV found DDF for 0x00158D0003494C9B, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_rtcgqq11lm_presence_sensor.json
20:10:46:292 DEV found DDF for 0x00158D0002BF631D, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq01lm_temp_hum_sensor.json
20:10:46:295 DEV found DDF for 0x00158D0002A139CC, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq01lm_openclose_sensor.json
20:10:46:295 DEV found DDF for 0xD0CF5EFFFE155FB1, path:
20:10:46:296 DEV found DDF for 0x086BD7FFFE412967, path:
20:10:46:300 DEV found DDF for 0x00158D00034977E9, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_rtcgqq11lm_presence_sensor.json
20:10:46:305 DEV found DDF for 0x00158D0002C8EB5D, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq01lm_temp_hum_sensor.json
20:10:46:306 DEV found DDF for 0x000D6FFFFE1506F5, path:
20:10:46:306 DEV found DDF for 0x84FD27FFFE35EAB4, path:
20:10:46:887 COM: /dev/ttyACM0 / serialno: , ConBee II
20:10:47:413 New websocket 192.168.1.86:35468 (state: 3)
20:10:48:545 Device firmware version 0x264A0700 ConBee II
20:10:48:550 unlocked max nodes: 512
20:10:48:559 Device protocol version: 0x010B
20:10:48:654 Current channel 15
20:10:48:660 CTRL got nwk update id 10
20:10:48:662 CTRL ANT_CTRL 0x03
20:10:48:681 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0028, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 74
20:10:48:686 ZCL attribute report 0x00158D00036CC111 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
20:10:48:687 0x00158D00036CC111 extract Xiaomi special attribute 0xFF01
20:10:48:688 64 on/off 0
20:10:48:688 03 Device temperature 26 °C
20:10:48:688 98 power 0.000000 (0)
20:10:48:689 95 consumption 44.338245 (44338)
20:10:48:689 05 RSSI dB (?) 2915 (0x0B63)
20:10:48:689 9a unknown 0 (0x00)
20:10:48:690 08 unknown 4954 (0x135A)
20:10:48:690 09 unknown 3074 (0x0C02)
20:10:48:766 delayed group sending
20:10:48:777 delayed group sending
20:10:48:778 delayed group sending
20:10:48:803 ZCL attribute report 0x84FD27FFFE35EAB4 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:10:48:949 ZCL attribute report 0x84FD27FFFE35EAB4 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:10:49:477 Set sensor check interval to 100 milliseconds
20:10:50:180 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
20:10:50:180 GW firmware version shall be updated to: 0x26720700
20:10:50:404 Announced to internet https://phoscon.de/discover
20:10:53:029 DEV Tick.Init: booted after 8000 seconds
20:10:53:871 ZCL attribute report 0x84FD27FFFE35EAB4 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:10:56:257 ZCL attribute report 0x90FD9FFFFED463D5 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:10:56:263 ZCL attribute report 0x90FD9FFFFED463D5 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:10:57:410 New websocket 192.168.1.92:50738 (state: 3)
20:11:00:231 ZCL attribute report 0x90FD9FFFFED463D5 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:11:00:236 ZCL attribute report 0x90FD9FFFFED463D5 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:11:05:783 drop request to zombie (rx = 0)
20:11:05:879 drop request to zombie (rx = 0)
20:11:07:971 ZCL attribute report 0x00158D00032D56E0 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
20:11:07:971 0x00158D00032D56E0 extract Xiaomi special attribute 0xFF01
20:11:07:971 64 on/off 0
20:11:07:972 03 Device temperature 28 °C
20:11:07:972 98 power 0.000000 (0)
20:11:07:972 95 consumption 33.124004 (33124)
20:11:07:973 05 RSSI dB (?) 3022 (0x0BCE)
20:11:07:973 9a unknown 0 (0x00)
20:11:07:973 08 unknown 4954 (0x135A)
20:11:07:973 09 unknown 3332 (0x0D04)
20:11:16:196 ZCL attribute report 0x00158D0002E99CD7 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:11:16:208 ZCL attribute report 0x00158D0002E99CD7 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:11:26:049 ZCL attribute report 0x90FD9FFFFEDE5F0F for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:11:28:727 DeviceAnnce of SensorNode: 0xD0CF5EFFFE1F2CE2 [1]
20:11:29:480 binding for cluster 0x0006 of 0x90FD9FFFFED463D5 exists (verified by reporting)
20:11:29:481 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x90FD9FFFFED463D5 (seems to be active)
20:11:29:481 binding for cluster 0x0008 of 0x90FD9FFFFED463D5 exists (verified by reporting)
20:11:29:482 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x90FD9FFFFED463D5 (seems to be active)
20:11:29:483 binding for cluster 0x0300 of 0x90FD9FFFFED463D5 exists (verified by reporting)
20:11:29:484 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x90FD9FFFFED463D5 (seems to be active)
20:11:29:484 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0x90FD9FFFFED463D5 (wait reading or unsupported)
20:11:29:484 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0x90FD9FFFFED463D5 (wait reading or unsupported)
20:11:29:486 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x90FD9FFFFED463D5 (seems to be active)
20:11:30:651 Bind response success for 0x90fd9ffffed463d5 ep: 0x01 cluster: 0x0000
20:11:30:762 ZCL configure reporting rsp seq: 75 0x90FD9FFFFED463D5 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:11:33:114 0x00158D000254C041 error APSDE-DATA.confirm: 0xE1 on task
20:11:36:085 Bind response success for 0xccccccfffeb8d62b ep: 0x01 cluster: 0x0000
20:11:36:191 ZCL configure reporting rsp seq: 86 0xCCCCCCFFFEB8D62B for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:11:36:408 Bind response success for 0xccccccfffeb8d62b ep: 0x01 cluster: 0x0006
20:11:36:482 ZCL configure reporting rsp seq: 88 0xCCCCCCFFFEB8D62B for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:11:40:630 0x90FD9FFFFED463D5 error APSDE-DATA.confirm: 0xE9 on task
20:11:41:478 binding for cluster 0x0006 of 0x00158D00036CC111 exists (verified by reporting)
20:11:41:479 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x00158D00036CC111 (seems to be active)
20:11:46:921 ZCL attribute report 0x000D6FFFFE1506F5 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:11:46:942 ZCL attribute report 0x000D6FFFFE1506F5 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:11:49:178 sensor 54 (TRADFRI motion sensor): disable presence
20:11:49:673 Bind response success for 0xccccccfffeb8d62b ep: 0x01 cluster: 0x0008
20:11:49:674 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFEB8D62B (wait reading or unsupported)
20:11:49:767 Bind response success for 0x90fd9ffffed463d5 ep: 0x01 cluster: 0x0000
20:11:51:907 Bind response success for 0x804b50fffe132adf ep: 0x01 cluster: 0x0000
20:11:51:001 ZCL configure reporting rsp seq: 102 0x804B50FFFE132ADF for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:11:53:643 0x086BD7FFFE412967 error APSDE-DATA.confirm: 0xE9 on task
20:11:54:812 Bind response success for 0x804b50fffe132adf ep: 0x01 cluster: 0x0006
20:11:54:907 ZCL configure reporting rsp seq: 107 0x804B50FFFE132ADF for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:11:55:121 Bind response success for 0xccccccfffeb8d62b ep: 0x01 cluster: 0x0000
20:11:56:301 Bind response success for 0x804b50fffe132adf ep: 0x01 cluster: 0x0008
20:11:56:302 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x804B50FFFE132ADF (wait reading or unsupported)
20:11:56:385 Bind response success for 0xccccccfffeb8d62b ep: 0x01 cluster: 0x0006
20:11:56:385 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFEB8D62B (seems to be active)
20:11:56:479 binding for cluster 0x0006 of 0x84FD27FFFE35EAB4 exists (verified by reporting)
20:11:56:480 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x84FD27FFFE35EAB4 (seems to be active)
20:11:56:480 binding for cluster 0x0008 of 0x84FD27FFFE35EAB4 exists (verified by reporting)
20:11:56:481 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x84FD27FFFE35EAB4 (seems to be active)
20:11:58:061 0x90FD9FFFFED463D5 error APSDE-DATA.confirm: 0xE1 on task
20:11:58:536 Bind response success for 0x804b50fffe132adf ep: 0x01 cluster: 0x0300
20:11:58:688 ZCL configure reporting rsp seq: 114 0x804B50FFFE132ADF for ep: 0x01 cluster: 0x0300 attr: 0x0003 status: 0x00
20:11:58:688 ZCL configure reporting rsp seq: 114 0x804B50FFFE132ADF for ep: 0x01 cluster: 0x0300 attr: 0x0004 status: 0x00
20:11:58:688 ZCL configure reporting rsp seq: 114 0x804B50FFFE132ADF for ep: 0x01 cluster: 0x0300 attr: 0x0007 status: 0x00
20:11:58:689 ZCL configure reporting rsp seq: 114 0x804B50FFFE132ADF for ep: 0x01 cluster: 0x0300 attr: 0x0008 status: 0x00
20:12:06:085 0xD0CF5EFFFE155FB1 error APSDE-DATA.confirm: 0xE1 on task
20:12:07:478 binding for cluster 0x0006 of 0x00158D00032D56E0 exists (verified by reporting)
20:12:07:479 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x00158D00032D56E0 (seems to be active)
20:12:11:650 Bind response success for 0x086bd7fffe412967 ep: 0x01 cluster: 0x0000
20:12:11:758 ZCL configure reporting rsp seq: 125 0x086BD7FFFE412967 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:12:11:916 Bind response success for 0x804b50fffe132adf ep: 0x01 cluster: 0x0000
20:12:16:090 Bind response success for 0x086bd7fffe412967 ep: 0x01 cluster: 0x0006
20:12:16:268 ZCL configure reporting rsp seq: 127 0x086BD7FFFE412967 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:12:16:478 sensor 74 (lumi.sensor_motion.aq2): disable presence
20:12:17:147 Bind response success for 0x086bd7fffe412967 ep: 0x01 cluster: 0x0006
20:12:17:148 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x086BD7FFFE412967 (seems to be active)
20:12:17:178 Set sensor check interval to 1000 milliseconds
20:12:18:021 Bind response success for 0x804b50fffe132adf ep: 0x01 cluster: 0x0006
20:12:18:023 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x804B50FFFE132ADF (seems to be active)
20:12:18:730 ZCL attribute report 0x90FD9FFFFEE94E28 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:12:19:228 Bind response success for 0x086bd7fffe412967 ep: 0x01 cluster: 0x0008
20:12:19:229 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x086BD7FFFE412967 (wait reading or unsupported)
20:12:19:883 Bind response success for 0x804b50fffe132adf ep: 0x01 cluster: 0x0300
20:12:19:884 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x804B50FFFE132ADF (seems to be active)
20:12:19:884 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0x804B50FFFE132ADF (seems to be active)
20:12:19:884 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0x804B50FFFE132ADF (seems to be active)
20:12:19:885 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x804B50FFFE132ADF (seems to be active)
20:12:21:326 Bind response success for 0x84fd27fffe35eab4 ep: 0x01 cluster: 0x0000
20:12:21:378 ZCL configure reporting rsp seq: 134 0x84FD27FFFE35EAB4 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:12:21:440 Bind response success for 0x000d6ffffed1a5d9 ep: 0x01 cluster: 0x0000
20:12:21:507 ZCL configure reporting rsp seq: 135 0x000D6FFFFED1A5D9 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:12:22:835 ZCL attribute report 0x00158D0002E99CD7 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:12:25:479 binding for cluster 0x0300 of 0x000D6FFFFE1506F5 exists (verified by reporting)
20:12:25:480 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x000D6FFFFE1506F5 (seems to be active)
20:12:25:481 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x000D6FFFFE1506F5 (seems to be active)
20:12:25:682 ZCL configure reporting rsp seq: 141 0x000D6FFFFE1506F5 for ep: 0x01 cluster: 0x0300 attr: 0x0003 status: 0x00
20:12:25:685 ZCL configure reporting rsp seq: 141 0x000D6FFFFE1506F5 for ep: 0x01 cluster: 0x0300 attr: 0x0004 status: 0x00
20:12:29:919 0x000D6FFFFE1506F5 error APSDE-DATA.confirm: 0xE9 on task
20:12:31:334 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0029, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 63
20:12:31:536 Bind response success for 0x000d6ffffed1a5d9 ep: 0x01 cluster: 0x0006
20:12:31:702 ZCL configure reporting rsp seq: 146 0x000D6FFFFED1A5D9 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:12:31:968 Bind response success for 0x086bd7fffe412967 ep: 0x01 cluster: 0x0000
20:12:31:978 Set sensor check interval to 100 milliseconds
20:12:32:695 Bind response success for 0x000d6ffffed1a5d9 ep: 0x01 cluster: 0x0006
20:12:32:696 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x000D6FFFFED1A5D9 (seems to be active)
20:12:33:817 Bind response success for 0x000d6ffffed1a5d9 ep: 0x01 cluster: 0x0008
20:12:33:818 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x000D6FFFFED1A5D9 (wait reading or unsupported)
20:12:34:932 Bind response success for 0x90fd9ffffee94e28 ep: 0x01 cluster: 0x0000
20:12:35:006 ZCL configure reporting rsp seq: 150 0x90FD9FFFFEE94E28 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:12:37:046 ZCL attribute report 0x00158D000254C041 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
20:12:37:047 0x00158D000254C041 extract Xiaomi special attribute 0xFF01
20:12:37:047 64 on/off 1
20:12:37:047 03 Device temperature 37 °C
20:12:37:048 98 power 92.000000 (92)
20:12:37:048 95 consumption 1083.943848 (1083944)
20:12:37:048 05 RSSI dB (?) 2693 (0x0A85)
20:12:37:048 9a unknown 0 (0x00)
20:12:37:048 08 unknown 4954 (0x135A)
20:12:37:049 09 unknown 3845 (0x0F05)
20:12:37:090 Bind response success for 0x90fd9ffffee94e28 ep: 0x01 cluster: 0x0006
20:12:37:148 ZCL configure reporting rsp seq: 151 0x90FD9FFFFEE94E28 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:12:37:221 Bind response success for 0x84fd27fffe35eab4 ep: 0x01 cluster: 0x0000
20:12:38:363 Bind response success for 0x90fd9ffffee94e28 ep: 0x01 cluster: 0x0008
20:12:38:364 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x90FD9FFFFEE94E28 (wait reading or unsupported)
20:12:38:426 Bind response success for 0x000d6ffffed1a5d9 ep: 0x01 cluster: 0x0000
20:12:40:175 Bind response success for 0x90fd9ffffee94e28 ep: 0x01 cluster: 0x0300
20:12:40:176 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x90FD9FFFFEE94E28 (wait reading or unsupported)
20:12:40:176 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x90FD9FFFFEE94E28 (seems to be active)
20:12:40:240 ZCL configure reporting rsp seq: 153 0x90FD9FFFFEE94E28 for ep: 0x01 cluster: 0x0300 attr: 0x0003 status: 0x00
20:12:40:241 ZCL configure reporting rsp seq: 153 0x90FD9FFFFEE94E28 for ep: 0x01 cluster: 0x0300 attr: 0x0004 status: 0x00
20:12:42:182 ZCL attribute report 0x00158D0002E2E02C for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:12:42:202 ZCL attribute report 0x00158D0002E2E02C for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:12:42:262 delayed group sending
20:12:42:278 delayed group sending
20:12:42:279 delayed group sending
20:12:43:614 0x84FD27FFFE35EAB4 force poll (2)
20:12:43:649 0x84FD27FFFE35EAB4 force poll (2)
20:12:44:716 0x000D6FFFFE1506F5 error APSDE-DATA.confirm: 0xE1 on task
20:12:50:073 ZCL attribute report 0x804B50FFFE132ADF for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:12:50:106 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x90FD9FFFFEE94E28 (seems to be active)
20:12:51:028 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x90FD9FFFFEE94E28 (wait reading or unsupported)
20:12:51:029 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0x90FD9FFFFEE94E28 (seems to be active)
20:12:51:029 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0x90FD9FFFFEE94E28 (seems to be active)
20:12:51:029 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x90FD9FFFFEE94E28 (seems to be active)
20:12:52:101 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x086BD7FFFE42BC64 (wait reading or unsupported)
20:12:52:196 ZCL configure reporting rsp seq: 164 0x086BD7FFFE42BC64 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:12:52:200 ZCL configure reporting rsp seq: 163 0x086BD7FFFE42BC64 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:12:52:313 Bind response success for 0x00158d000254c041 ep: 0x01 cluster: 0x0006
20:12:52:313 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x00158D000254C041 (seems to be active)
20:12:52:437 Bind response success for 0xd0cf5efffe155fb1 ep: 0x01 cluster: 0x0000
20:12:52:526 ZCL configure reporting rsp seq: 167 0xD0CF5EFFFE155FB1 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:12:52:666 Bind response success for 0xd0cf5efffe155fb1 ep: 0x01 cluster: 0x0006
20:12:52:772 ZCL configure reporting rsp seq: 168 0xD0CF5EFFFE155FB1 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:12:52:986 Bind response success for 0xd0cf5efffe155fb1 ep: 0x01 cluster: 0x0008
20:12:53:117 ZCL configure reporting rsp seq: 169 0xD0CF5EFFFE155FB1 for ep: 0x01 cluster: 0x0008 attr: 0x0000 status: 0x00
20:12:53:790 ZCL attribute report 0x804B50FFFE132ADF for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:12:56:260 0x000d6ffffed1a5d9 found group 0xFFF0
20:12:57:217 0x90fd9ffffed463d5 found group 0xFFF0
20:12:57:217 0x90fd9ffffed463d5 found group 0x001B
20:12:57:827 0x00158d00032d56e0 found group 0x0000
20:12:57:827 0x00158d00032d56e0 found group 0xFFF0
20:12:58:540 0xccccccfffeb8d62b found group 0x001E
20:12:58:541 0xccccccfffeb8d62b found group 0xFFF0
20:12:59:283 0x90fd9ffffee94e28 found group 0x0012
20:12:59:283 0x90fd9ffffee94e28 found group 0xFFF0
20:12:59:981 GW firmware version shall be updated to: 0x26720700
20:13:00:051 0x00158d00036cc111 found group 0x0000
20:13:00:051 0x00158d00036cc111 found group 0xFFF0
20:13:00:111 0x00158D00036CC111 error APSDE-DATA.confirm: 0xE1 on task
20:13:00:753 0x00158d000254c041 found group 0x0000
20:13:00:754 0x00158d000254c041 found group 0xFFF0
20:13:01:534 0x086bd7fffe42bc64 found group 0xFFF0
20:13:02:380 0x804b50fffe132adf found group 0xFFF0
20:13:02:380 0x804b50fffe132adf found group 0x0011
20:13:03:199 0xd0cf5efffe155fb1 found group 0xFFF0
20:13:03:200 0xd0cf5efffe155fb1 found group 0x000D
20:13:03:805 0x086bd7fffe412967 found group 0xFFF0
20:13:04:524 0x000D6FFFFE1506F5 error APSDE-DATA.confirm: 0xE9 on task
20:13:05:271 ZCL configure reporting rsp seq: 186 0x000D6FFFFE1506F5 for ep: 0x01 cluster: 0x0008 attr: 0x0000 status: 0x00
20:13:05:429 0x84fd27fffe35eab4 found group 0xFFF0
20:13:05:429 0x84fd27fffe35eab4 found group 0x000E
20:13:09:214 ZCL attribute report 0x804B50FFFE132ADF for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
20:13:10:570 Bind response success for 0xd0cf5efffe155fb1 ep: 0x01 cluster: 0x0300
20:13:10:571 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xD0CF5EFFFE155FB1 (wait reading or unsupported)
20:13:10:571 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xD0CF5EFFFE155FB1 (wait reading or unsupported)
20:13:10:838 ZCL configure reporting rsp seq: 191 0xD0CF5EFFFE155FB1 for ep: 0x01 cluster: 0x0300 attr: 0x0007 status: 0x00
20:13:10:838 ZCL configure reporting rsp seq: 191 0xD0CF5EFFFE155FB1 for ep: 0x01 cluster: 0x0300 attr: 0x0008 status: 0x00
20:13:10:950 Bind response success for 0xd0cf5efffe155fb1 ep: 0x01 cluster: 0x0000
20:13:11:963 0x90FD9FFFFED463D5 error APSDE-DATA.confirm: 0xE1 on task
20:13:12:037 Bind response success for 0x000d6ffffe1506f5 ep: 0x01 cluster: 0x0000
20:13:12:109 ZCL configure reporting rsp seq: 193 0x000D6FFFFE1506F5 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
20:13:12:236 Bind response success for 0xd0cf5efffe155fb1 ep: 0x01 cluster: 0x0006
20:13:12:237 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xD0CF5EFFFE155FB1 (seems to be active)
20:13:13:357 Bind response success for 0x000d6ffffe1506f5 ep: 0x01 cluster: 0x0006
20:13:13:490 ZCL configure reporting rsp seq: 195 0x000D6FFFFE1506F5 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
20:13:13:802 Bind response success for 0xd0cf5efffe155fb1 ep: 0x01 cluster: 0x0008
20:13:13:803 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xD0CF5EFFFE155FB1 (seems to be active)
20:13:14:303 Bind response success for 0x000d6ffffe1506f5 ep: 0x01 cluster: 0x0006
20:13:14:304 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x000D6FFFFE1506F5 (seems to be active)
20:13:18:055 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0xD0CF5EFFFE155FB1 (seems to be active)
20:13:18:055 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0xD0CF5EFFFE155FB1 (wait reading or unsupported)
20:13:18:055 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0xD0CF5EFFFE155FB1 (wait reading or unsupported)
20:13:18:056 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xD0CF5EFFFE155FB1 (seems to be active)
20:13:31:578 sensor 55 (TRADFRI motion sensor): disable presence
20:13:33:016 ZCL attribute report 0x00158D0002E99CD7 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:13:33:047 ZCL attribute report 0x00158D0002E99CD7 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:13:35:571 Bind response success for 0x000d6ffffe1506f5 ep: 0x01 cluster: 0x0000
20:13:39:678 delay sending request 216 dt 0 ms to 0x000D6FFFFE1506F5, ep: 0x01 cluster: 0x0008 onAir: 1
20:13:39:680 0x000D6FFFFE1506F5 force poll (2)
Websocket log are visible with info+info_L2, but if you don’t see it in phoscon you will not see them in deconz.
Just go on phoscon/help/Api Information/events and heat a sensor, you will see a websocket report.
I have the same issue. I am currently abroad and was bold enough to update deCONZ to 2.20.1 (HA add-on). The figure shows only a fraction of the motion sensors which are now stuck in “on” since 10 hours. I remember that this behaviour was introduced with DDF, and normally it only happens for a few sensors, but this time, ALL of them went on. Let’s fix this, it is annoying because for some of them, just walking by is not enough and repairment is needed. I also remember that you @Smanar mentioned some time ago that some regular poll of Xiaomi special attributes hasn’t been included in the DDF, which is also the reason why light level values are “stuck” as well. Could this be related?
