I saw the github issue when someone was discussing this issue on deconz discord
1 Like
The error I described earlier (not the unexpected color mode 2 problem) continues.
The problem is occuring daily (seems to be at a simular time of the day, in the evening) where I can’t control the deconz entities. The problem is easily solved by restarting the Pi4 system or replugging the conbee stick.
I use a Conbee stick on a 2m usb cable connected to a Pi4 with deconz add-on running in HA. Also using a SSD.
Here I’ve tried to show some log snippets from the current failure I got today some hours ago:
18:40:06:468 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0xCC86ECFFFE9A702A (seems to be active)
18:40:24:454 timeout on poll APS confirm
18:40:24:738 0xB4E3F9FFFEFFE241 error APSDE-DATA.confirm: 0xA7 on task
18:52:34:654 enqueue APS request failed with error 2, drop
18:53:34:454 timeout on poll APS confirm
18:53:35:354 enqueue APS request failed with error 2, drop
18:53:41:454 GW firmware version is up to date: 0x26400500
18:54:35:454 timeout on poll APS confirm
19:29:41:454 GW firmware version is up to date: 0x26400500
19:31:15:872 Announced to internet https://phoscon.de/discover
19:31:15:874 discovery server date: Mon, 14 Nov 2022 18:31:15 GMT
19:31:15:875 local time seems to be ok
19:31:23:629 enqueue APS request failed with error 2, drop
Anyone got an idea what causes these failures?
I had problems on a rpi4. Switching to rpi3 solved them all 
I have this issue too, using and RPi 3b and an Conbee I stick, a friend of mine with a RPi 4 and a Conbee II.
It is discussed in the deconz-forum Deconz stops working (conbee II stick) - #7 by skank01 - General - deCONZ Community without a solution yet.
Hopefully the next deconz release will fix it. Until then I restart the deconz-addon daily.
I have a strange behavior with couple Xiaomi Mi Smart Home Occupancy Sensors. They are outside in my summer cabin and when detected movement security cameras send me a notification of the area. I have got false detections but I have thought that they are just because of sun or other reasons. Until now:
I realized the false detections follow a pattern – they appear in every 55 minutes when they start but they don’t detect all the time (a pic below). I do not know any reason for that. I have more of those same sensors in summer cabin and home which do not follow this pattern. Any idea what is going on here?
Best thing would to look at the debug logs to see what message are being sent every 55 minutes that will toggle it.
Thanks! I copied this to my config:
logger:
default: info
logs:
pydeconz: debug
homeassistant.components.deconz: debug
Right?
And now the logs we are talking can be found in HA logs (or Addon logs)?
Precisely!
It just happened and I found this in Deconz logs:
22:21:33:542 sensor 50 (lumi.sensor_motion): disable presence
22:21:35:041 Set sensor check interval to 1000 milliseconds
Does it help?
And this for the second sensor:
22:26:57:842 sensor 51 (lumi.sensor_motion): disable presence
22:26:59:341 Set sensor check interval to 1000 milliseconds
And these two were not false detections 
I don’t recognize those logs. Are they really from home assistant?
Aah ok so you’re looking in the add-on logs, for the integration (which you enabled debugging for) you should look in the ha logs instead.
Try it 
why don’t ya?
OK - does this help?
2022-11-15 22:21:22.371 DEBUG (MainThread) [pydeconz.websocket] {“attr”:{“id”:“50”,“lastannounced”:“2022-04-12T20:05:35Z”,“lastseen”:“2022-11-15T20:21Z”,“manufacturername”:“LUMI”,“modelid”:“lumi.sensor_motion”,“name”:
Those are the correct logs. Preferably you find an example in the logs with what events are sent in that specific time you day nothing should trigger the sensor
OK Thanks!
OK this is what I found. Logs for two identical LUMI sensors: Motion11 without false positives and Motion12 with false positives. Every 55 minutes I can see two identical logs in blue below. In addition to Motion12 (red below) a log with “presence”:true following one what I did not copy with “presence”:false
So what should I think about this: there is maybe an update in every 55 minutes which causes these false detection but how to get rid of them is the Question.
The red one you mean? You should report it to Deconz github as it’s something on deconz side. Because it looses a lot of trust if you get phantom motion
OK Thanks! I will report this to github then.
1 Like