Q: Existing devices sometimes appear with Hex name in deconz?

iisworks · September 16, 2022, 7:38am

Not a big deal, but wanted to mention it: sometimes devices randomly pop up in deconz with a hex name instead of the actual device name. In Phoscon the name is always still normal.

Just now I restarted deconz, and the device with the hex name returned with its normal name, but at the same time another device showed up in deconz with a hex name. Also, when I rename a hex device in Phoscon, the new name is updated in deconz as well. I have seen this a couple of times now with lights and plugs, I think usually after a restart and/or pairing of other devices.

Deconz beta 2.18.1 (I think this also happened in 2.18), Docker on Synology. Sorry, no logs.
Have others seen this as well, and has anything changed recently that could explain this behavior?

Gautama · September 16, 2022, 8:19am

Typical behavior for devices who won´t come in correctly or older device data.
Persnaly I saw this a couple of times in my own setup when the connection wasn´t that stable and I´ve tried to bring in a new device. It pop´s up as Hex, then (sometimes after a few tries) the correct name was shown.
Maybe some of the other guys here have some ideas also, but so far it isn´t abnormal.

iisworks · September 16, 2022, 12:00pm

Could it be related to:

github.com/dresden-elektronik/deconz-rest-plugin

Functional devices get hex names in deconz GUI

opened 09:16PM - 13 Sep 22 UTC

SwoopX

Confirmed Bug Bug report

## Describe the bug  Under not yet clear conditions, nodes do not get properly processed during the start of deconz and some might show up with a hex name. Indications where things go wrong can be seen in the debug output of function `handleDDFInitRequest()` as below (2 devices affected at the same time in my production): ``` 20:59:11:265 DEV found DDF for 0x0000000000000000, path: /home/deconz/.local/share/dresden-elektronik/deCONZ/devices/sp_120.json [...] 20:59:12:891 DEV found DDF for 0x0000002B00000002, path: /home/deconz/.local/share/dresden-elektronik/deCONZ/devices/170-33505_170-33605_smart_socket.json ``` So it looks like `event.deviceKey()` apparently gets, good question, corrupted? Other potentially disruptive side effects are not clear yet. ## Steps to reproduce the behavior  This is not consistently reproducible. I had to restart my dev environment like 10 times for it to occur. Regardless, that condition manifests if one or more nodes do show a hex name out of a sudden after restart. ## Expected behavior  Supported devices being covered by DDF should get completely loaded and data processed via the intended code. ## Screenshots  2nd screenshot depicts how it is supposed to be ![grafik](https://user-images.githubusercontent.com/4005212/189996253-a79356d5-7cba-4d90-af11-98d06eee7427.png) ![grafik](https://user-images.githubusercontent.com/4005212/189996429-d581e4be-693d-45b2-922e-e86e1de7b18c.png) ## Environment  - Host system: irrelevant - Running method: irrelevant - Firmware version: irrelevant - deCONZ version: 2.18.01 and presumably many versions below - Device: irrelevant - Do you use an USB extension cable: irrelevant - Is there any other USB or serial devices connected to the host system? irrelevant ## deCONZ Logs  This is a more extensive debug log of mine. The part `22:28:35:827 EventEmitter - Event ID: 68, Node ext: 0x0015BC0036000C0D` in the middle of it is generated in `enqueueEvent()`. ``` 22:28:35:817 handleDDFInitRequest - Event ID: , Event devicekey: 0x0015BC0036000C0D 22:28:35:817 DEV path: /usr/share/deCONZ/devices/frient/aqszb-110_voc_sensor.json, result value: -1 22:28:35:817 DEV_InitCompatNodeFromDescription 22:28:35:818 Item count: 12 22:28:35:818 Available items: attr/name 22:28:35:818 Available items: attr/manufacturername 22:28:35:818 Available items: attr/modelid 22:28:35:818 Available items: attr/type 22:28:35:818 Available items: attr/swversion 22:28:35:818 Available items: attr/id 22:28:35:818 Available items: attr/uniqueid 22:28:35:818 Available items: attr/lastannounced 22:28:35:818 Available items: attr/lastseen 22:28:35:818 Available items: config/on 22:28:35:818 Available items: config/reachable 22:28:35:819 Available items: state/lastupdated 22:28:35:819 attr/id 22:28:35:819 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/id 22:28:35:819 attr/lastannounced 22:28:35:819 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/lastannounced 22:28:35:819 SQL exec failed: SELECT attr FROM sensors WHERE uniqueid = '00:15:bc:00:36:00:0c:0d-26-fc03' AND deletedState = 'normal', error: no such column: attr (1) 22:28:35:819 attr/lastseen 22:28:35:819 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/lastseen 22:28:35:819 attr/manufacturername 22:28:35:819 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/manufacturername 22:28:35:819 attr/modelid 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/modelid 22:28:35:820 attr/name 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/name 22:28:35:820 attr/swversion 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/swversion 22:28:35:820 attr/type 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/type 22:28:35:820 attr/uniqueid 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: attr/uniqueid 22:28:35:820 config/battery 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, create item: config/battery 22:28:35:820 config/on 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: config/on 22:28:35:820 config/reachable 22:28:35:820 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: config/reachable 22:28:35:821 state/airqualityppb 22:28:35:821 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, create item: state/airqualityppb 22:28:35:821 state/airquality 22:28:35:821 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, create item: state/airquality 22:28:35:821 state/lastupdated 22:28:35:821 sub-device: 00:15:bc:00:36:00:0c:0d-26-fc03, has item: state/lastupdated 22:28:35:822 EventEmitter - Event ID: 70, Node ext: 0x0015BC0036000C0D 22:28:35:822 DEV_InitCompatNodeFromDescription 22:28:35:823 Item count: 12 22:28:35:823 Available items: attr/name 22:28:35:823 Available items: attr/manufacturername 22:28:35:823 Available items: attr/modelid 22:28:35:823 Available items: attr/type 22:28:35:823 Available items: attr/swversion 22:28:35:823 Available items: attr/id 22:28:35:824 Available items: attr/uniqueid 22:28:35:824 Available items: attr/lastannounced 22:28:35:824 Available items: attr/lastseen 22:28:35:824 Available items: config/on 22:28:35:824 Available items: config/reachable 22:28:35:824 Available items: state/lastupdated 22:28:35:824 attr/id 22:28:35:824 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/id 22:28:35:824 attr/lastannounced 22:28:35:824 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/lastannounced 22:28:35:825 SQL exec failed: SELECT attr FROM sensors WHERE uniqueid = '00:15:bc:00:36:00:0c:0d-26-0402' AND deletedState = 'normal', error: no such column: attr (1) 22:28:35:825 attr/lastseen 22:28:35:825 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/lastseen 22:28:35:825 attr/manufacturername 22:28:35:825 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/manufacturername 22:28:35:825 attr/modelid 22:28:35:825 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/modelid 22:28:35:825 attr/name 22:28:35:825 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/name 22:28:35:825 attr/swversion 22:28:35:825 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/swversion 22:28:35:825 attr/type 22:28:35:825 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/type 22:28:35:825 attr/uniqueid 22:28:35:825 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: attr/uniqueid 22:28:35:826 config/battery 22:28:35:826 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, create item: config/battery 22:28:35:826 config/offset 22:28:35:826 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, create item: config/offset 22:28:35:826 config/on 22:28:35:826 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: config/on 22:28:35:826 config/reachable 22:28:35:826 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: config/reachable 22:28:35:826 state/lastupdated 22:28:35:826 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, has item: state/lastupdated 22:28:35:826 state/temperature 22:28:35:826 sub-device: 00:15:bc:00:36:00:0c:0d-26-0402, create item: state/temperature 22:28:35:827 EventEmitter - Event ID: 68, Node ext: 0x0015BC0036000C0D 22:28:35:827 DEV_InitCompatNodeFromDescription 22:28:35:827 Item count: 12 22:28:35:827 Available items: attr/name 22:28:35:827 Available items: attr/manufacturername 22:28:35:827 Available items: attr/modelid 22:28:35:828 Available items: attr/type 22:28:35:828 Available items: attr/swversion 22:28:35:828 Available items: attr/id 22:28:35:828 Available items: attr/uniqueid 22:28:35:828 Available items: attr/lastannounced 22:28:35:828 Available items: attr/lastseen 22:28:35:828 Available items: config/on 22:28:35:828 Available items: config/reachable 22:28:35:828 Available items: state/lastupdated 22:28:35:828 attr/id 22:28:35:828 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/id 22:28:35:828 attr/lastannounced 22:28:35:828 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/lastannounced 22:28:35:828 SQL exec failed: SELECT attr FROM sensors WHERE uniqueid = '00:15:bc:00:36:00:0c:0d-26-0405' AND deletedState = 'normal', error: no such column: attr (1) 22:28:35:829 attr/lastseen 22:28:35:829 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/lastseen 22:28:35:829 attr/manufacturername 22:28:35:829 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/manufacturername 22:28:35:829 attr/modelid 22:28:35:829 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/modelid 22:28:35:829 attr/name 22:28:35:829 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/name 22:28:35:829 attr/swversion 22:28:35:829 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/swversion 22:28:35:829 attr/type 22:28:35:829 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/type 22:28:35:829 attr/uniqueid 22:28:35:829 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: attr/uniqueid 22:28:35:829 config/battery 22:28:35:830 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, create item: config/battery 22:28:35:830 config/offset 22:28:35:830 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, create item: config/offset 22:28:35:830 config/on 22:28:35:830 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: config/on 22:28:35:830 config/reachable 22:28:35:830 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: config/reachable 22:28:35:830 state/humidity 22:28:35:830 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, create item: state/humidity 22:28:35:830 state/lastupdated 22:28:35:830 sub-device: 00:15:bc:00:36:00:0c:0d-26-0405, has item: state/lastupdated 22:28:35:830 DEV add binding cluster: 0x0001, 0x0015BC0036000C0D 22:28:35:830 DEV add binding cluster: 0x0402, 0x0015BC0036000C0D 22:28:35:831 DEV add binding cluster: 0x0405, 0x0015BC0036000C0D 22:28:35:831 DEV add binding cluster: 0xFC03, 0x0015BC0036000C0D 22:28:35:831 DEV found DDF for 0x0000000000000262, path: /usr/share/deCONZ/devices/frient/aqszb-110_voc_sensor.json ``` ## Additional context  N/A

iisworks · September 17, 2022, 1:47pm

Not sure if it is somehow related. I just ran into this specific case: seems that this node 0xA4C138FE374472AD somehow stopped responing an edwas marked as Zombie. I tried a deconz restart and it turned up with a hex name, and still inactive in Phoscon. I have many similar plugs, and sometimes one just stops responding, and it usually will become activate again automatically again later on.

13:29:31:892 0xA4C138FE374472AD error APSDE-DATA.confirm: 0xD0 on task
13:29:31:893 max transmit errors for node 0xA4C138FE374472AD, last seen by neighbors 9 s
13:29:32:312 Skip idle timer callback, too early: elapsed 541 msec
13:29:32:584 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
13:29:32:754 0xA4C138FE374472AD error APSDE-DATA.confirm: 0xE9 on task
13:29:32:755 max transmit errors for node 0xA4C138FE374472AD, last seen by neighbors 9 s

This behavior only started recently, the plugs were pretty stable before.
What could cause this? Wifi interference maybe?

Smanar · September 17, 2022, 3:38pm

You have the error description here for 0x0D and 0xE9.
The device is stil not recheable, can just try a power cycle (of the device).

For me this issue is more “agressive” than just an interference.

For the 0xXXXX name it seem its already corrected Fix event emitter invalid memory references by manup · Pull Request #6331 · dresden-elektronik/deconz-rest-plugin · GitHub

iisworks · September 17, 2022, 4:49pm

A device poweroff/poweron always helps, just waiting or a reboot of deconz also helps sometimes. I guess the hex name has nothing to do with it then.

But I am still wondering what are the most common causes devices to become unreachable (the zigbee network is stable otherwise)? Wifi interference (I would expect more intermittent issues instead of a device remaining unreachable and not reporting)? I did notice that it is worse in a specific location in the house, and I even replaced the plug in that location with a completely other one couple of times. I have been on channel 25 since the beginning.

I also noticed this device becomes gray in Phoscon, but later on it looks normal again. In deconz/vnc I can read clusters, but it looks like (bottom one, no connections?):

Smanar · September 18, 2022, 6:57am

It’s a personnal advice, but on my side I think it can be too the power line.
I already have “freezed” ikea bulb, but the device don’t work again itself, the firwmare was totaly blocked, a power cycle was needed.

I would expect more intermittent issues instead of a device remaining unreachable and not reporting

Yeah for me too, for me interferences can cause the device miss some requests, but totally disconnect for more than 5mn …

And it’s a router, so it have more than 1 way.

As the position have an impact, yes it go in interference issue, but still strange for me.

Always the same device ? or have the issue for all devices in this zone ?

iisworks · September 18, 2022, 7:41am

I have many of these Tuya plugs, and it looks like the issue usually occurs in 1 or 2 specific locations in the house. And even when I swap plugs, so most likely not an issue with a specific plug, but more related to the location.

I still don’t understand why it gets disconnected for a while and then reconnects automatically after a while (no power cycle or deconz restart). Also the plug now seems to have connections again and looked OK, but on/off did not work?

I then did a read on the basic cluster from deconz, and after that it worked fine.
BTW: It’s an empty plug for now, so nothing is connected to it.

Does this logging hold a clue (0xA4C138FE374472AD)?

07:36:11:447 ZCL attribute report 0x00158D00054D0553 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:11:470 ZCL attribute report 0x00158D00054D0553 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:12:312 Skip idle timer callback, too early: elapsed 860 msec
07:36:12:725 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:14:059 ZCL attribute report 0x04CF8CDF3C78C39E for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:14:207 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:14:568 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:15:457 ZCL attribute report 0x04CF8CDF3C7B50D0 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:15:458 Skip idle timer callback, too early: elapsed 886 msec
07:36:16:301 ZCL attribute report 0x04CF8CDF3C7D1330 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:17:147 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:19:253 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:19:357 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:19:732 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:20:642 ZCL attribute report 0x04CF8CDF3C7B50D0 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:24:310 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:24:588 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:24:650 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:25:811 SC tick --> StateCallFunction
07:36:25:812 SC_SetOnOff()
07:36:25:906 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:25:907 SC state/on: synced
07:36:25:907 SC --> StateFinished
07:36:25:908 SC state change finished: a4:c1:38:fe:37:44:72:ad-01
07:36:26:049 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:26:206 ZCL attribute report 0xEC1BBDFFFEB181D9 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
07:36:26:233 ZCL attribute report 0x04CF8CDF3C7D1330 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:26:244 ZCL attribute report 0xEC1BBDFFFEB181D9 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
07:36:29:117 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:29:544 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:31:858 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:33:345 Device TTL 5099 s flags: 0x7
07:36:33:837 ZCL attribute report 0x04CF8CDF3C78C39E for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:34:115 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:34:183 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:35:098 ZCL attribute report 0x84BA20FFFEAD21C2 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
07:36:35:144 ZCL attribute report 0x00158D000461F3E0 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:35:155 ZCL attribute report 0x00158D000461F3E0 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:35:255 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:35:551 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:36:141 ZCL attribute report 0x04CF8CDF3C7D1330 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:36:152 ZCL attribute report 0x04CF8CDF3C7D1330 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:38:600 ZCL attribute report 0xEC1BBDFFFE547491 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
07:36:38:675 ZCL attribute report 0x84BA20FFFEAD21C2 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
07:36:38:685 ZCL attribute report 0x84BA20FFFEAD21C2 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
07:36:38:898 0xec1bbdfffeb88896 found group 0x0003
07:36:40:302 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:40:320 Skip idle timer callback, too early: elapsed 16 msec
07:36:40:548 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:41:108 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:44:110 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:45:123 ZCL attribute report 0x04CF8CDF3C7B50D0 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:45:559 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:46:115 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:46:143 ZCL attribute report 0x04CF8CDF3C7D1330 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:48:548 remove link for (277, 313D)
07:36:49:065 ZCL attribute report 0x00158D0004AB3C58 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:49:251 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:50:019 ZCL attribute report 0x00158D00058A26A4 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:50:145 ZCL attribute report 0x00158D00058A26A4 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:50:250 ZCL attribute report 0x00158D00058A26A4 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:50:684 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:51:334 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:51:795 emit event/tick: 0xa4c138fe374472ad
07:36:51:837 	0xA4C138FE374472AD force poll (2)
07:36:51:863 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:51:864 SC state/on: synced
07:36:51:865 SC --> StateFinished
07:36:51:865 SC state change finished: a4:c1:38:fe:37:44:72:ad-01
07:36:52:006 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:52:268 emit event/tick: 0xa4c138fe374472ad
07:36:52:311 	0xA4C138FE374472AD force poll (2)
07:36:52:511 sensor 55 (lumi.sensor_motion.aq2): disable presence
07:36:53:016 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:53:017 SC state/on: synced
07:36:53:017 SC --> StateFinished
07:36:53:017 SC state change finished: a4:c1:38:fe:37:44:72:ad-01
07:36:53:654 ZCL attribute report 0xA4C138C783B59014 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:54:237 ZCL attribute report 0xA4C1383602BE8319 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:54:695 ZCL attribute report 0xA4C138E35F5B0868 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:54:699 emit event/tick: 0xa4c138fe374472ad
07:36:54:745 	0xA4C138FE374472AD force poll (2)
07:36:54:776 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:54:777 SC state/on: synced
07:36:54:778 SC --> StateFinished
07:36:54:778 SC state change finished: a4:c1:38:fe:37:44:72:ad-01
07:36:55:056 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:55:806 emit event/tick: 0xa4c138fe374472ad
07:36:55:847 	0xA4C138FE374472AD force poll (2)
07:36:55:872 ZCL attribute report 0xA4C138FE374472AD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
07:36:55:873 SC state/on: synced

Smanar · September 18, 2022, 7:45am

This logs mean all is fine.
It say the device make is report periodically, relay good sign.

Nothing special in this location ? it s not your armored vault ? ^^

I don’t think it s caused by a neigtboard, as you have so much connexion.

No seriously, no idea on my side.

iisworks · September 18, 2022, 7:47am

OK, thanks! Nevermind, this is a bit off topic anyway. I will just keep an eye on it, and if it happens again I’ll just open a new topic.