As quick fix I created an input_boolean.blocksensor which will turn on every 55 minutes for few seconds after the LUMI-sensor turns on. I use that as a condition to prevent these “false alarms”.
So battery saga continues for IKEA switches…
Recently another one of my switches stopped to work, turned out to be battery dead. The first watchout; I’m monitoring all of my battery powered devices battery levels and there was no sign of warning for this device, but perhaps this is the issue of frequency of data reporting. After replacing battery, device did not picked up instantly, so I decided to remove it from config and again (perhaps my bad, I should wait or just restart the system). After adding the switch to deconz and restarting the HA (issue with name of device not being properly reflected in HA after reanaming in phoscon) device started to work as expected… Almost. It properly generates event, but now I have already 2 IKEA switches that do not report battery level at (unavailable, same issue as I described few post earlier). It was reporting battery level as long as device was configured in deconz prior to switching to DDF. After re-adding the device now it seems to drop battery level reporting support. For comparison here are the screenshots of 2 identical devices and how HA sees them:
Am I doing something fundamentally wrong or is it real issue?
Hello all!
Another month and another release of Home Assistant so here comes another release log on Phoscon forum for the HA deCONZ integration
Here are the changes coming with Home Assistant 2022.12.0
Still not much time spent on deCONZ as I’m still focusing on reworking the UniFi integration. But at least I got time to add events for the Hue Tap Dial Switch. There are suggestions here on how to make it easier to use so that is something I’ll look on down the line, try it out and add to the discussion!
Cheers!
/Robban
- Use partition rather than split akx
- Fix device class and unit of measurement for Air Quality PPB sensor
- Add event for Hue Tap Dial switch relative rotary
For feature requests of the integration post an issue at pydeconz github
1 Like
It is normal that the IKEA switches are reported not available after a deconz restart or battery change. They normally become available when you press the button. First button press may be ignorred but then it works. They also seem to wake up and report themselves online with 24 hours.
I have seen examples where a battery change made it unavailable and pressing the button did not help.
The the trick is to put deconz in pairing mode and press the pairing switch 4 times on the IKEA switch. Do not remove the switch from Deconz first. Just let it pair again and because the unique ID of the device is known it gets active again with same name and everything. I now always check when I change battery.
When I restart deconz (or upgrade) then I sometimes just walk around the house and click the most used switches once. The rest will join by themselves after some hours.
2 Likes
I have to do that with my Xiaomi switches as well. Click at least two times and everything’s ok
This is same behaviour I observed, not only for IKEA, but also for Aqara motion sensors, it need to be activated to reappear in deconz after restart.
Back to my switch issue - indeed it took almost 48 hours to restart battery level reporting… but only for the last one I reported in mal above. The other one does not show battery level for few weeks already. I tried few times to re-add it to deconz, but it did not changed situation. Perhaps it ifaulty then…
Thanks for the tip! This will make live way easier… until now I always deleted device that stopped to respond and readded it using process for new device.
Can anyone help me with this task, or is there someone at HA DEV that can make the update in the HA addon.
You can create an issue on home assistant add-on repo telling the maintainers if there is a new stable version of deconz available.
So one of my eurotronics, weirdly enough, went through a pair of batteries in no time and when I replaced them it won’t rejoin the network anymore! It just sits there at “Jin” and never appears in deconz/vnc (i did delete the old node there). And, yes, I did reset it quite a few times (holding all three buttons on the trv)…
Is it dead or am I missing something here?
Thanks!
Hi, I have a strange issue. I had a power off 15 Minutes ago. Now everything is online again but I cannot switch my lights off. All lights are on and doesn’t react on anything i.e. cannot be switched. A restart of the addon did not help
The lights cannot be controlled via Phoscon as well.
That is an extract of the deconz protokoll which doesn’t show anything interesting to me:
10:05:33:016 ZCL attribute report 0x00158D0003883DE3 for cluster: 0x0702, ep: 0x01, frame control: 0x18, mfcode: 0x0000
172.30.32.2 - - [14/Dec/2022:10:05:33 +0100] "GET /api/A2F2CBAB84/sensors/41 HTTP/1.1" 200 375 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
172.30.32.2 - - [14/Dec/2022:10:05:33 +0100] "GET /api/A2F2CBAB84/groups/10?_=1671008559767 HTTP/1.1" 200 701 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
172.30.32.2 - - [14/Dec/2022:10:05:33 +0100] "GET /api/A2F2CBAB84/sensors/23 HTTP/1.1" 200 485 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
10:05:33:941 No presence sensor found for 0x0017880106F45367, endpoint: 0x02
10:05:33:941 ZCL attribute report 0x0017880106F45367 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
172.30.32.2 - - [14/Dec/2022:10:05:34 +0100] "GET /api/A2F2CBAB84/sensors/42 HTTP/1.1" 200 380 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
10:05:34:026 ZCL attribute report 0x00158D0003883DE3 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
10:05:35:013 ZCL attribute report 0x00158D0003883DE3 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
10:05:36:016 ZCL attribute report 0x00158D0003883DE3 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
172.30.32.2 - - [14/Dec/2022:10:05:37 +0100] "GET /api/A2F2CBAB84/lights/1?_=1671008559768 HTTP/1.1" 200 345 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
172.30.32.2 - - [14/Dec/2022:10:05:37 +0100] "GET /api/A2F2CBAB84/lights/14?_=1671008559769 HTTP/1.1" 200 505 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
172.30.32.2 - - [14/Dec/2022:10:05:37 +0100] "GET /api/A2F2CBAB84/lights/14?_=1671008559770 HTTP/1.1" 200 505 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
172.30.32.2 - - [14/Dec/2022:10:05:37 +0100] "GET /api/A2F2CBAB84/lights/37?_=1671008559771 HTTP/1.1" 200 517 "https://nauen.duckdns.org:8123/api/hassio_ingress/iyHCklmQjA2_8AAZoA1dUzDeL3rVTDwifIOCYsiHIiI/pwa/index.html?_v=5d136aed7d2e79df663ab3f907954b6f3e6662bf,11,3,10&gwid=00212EFFFF04E125" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
172.30.32.2 - - [14/Dec/2022:10:05:38 +0100] "GET /websocket HTTP/1.1" 101 66372 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Edg/108.0.1462.46"
10:05:38:454 Websocket disconnected 127.0.0.1:57332, state: 0, close-code: 1000, reason:
10:05:38:962 GW firmware version is up to date: 0x26780700
10:05:42:484 ZCL attribute report 0x90FD9FFFFE67DD5F for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:05:42:543 ZCL attribute report 0x90FD9FFFFE67DD5F for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:05:42:802 ZCL attribute report 0x90FD9FFFFE67DD5F for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:05:43:973 No presence sensor found for 0x0017880106F45367, endpoint: 0x02
10:05:43:974 ZCL attribute report 0x0017880106F45367 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
PS: Ok, lucky me I created a phoscon backup yesterday. Restoring this repaired the situation.
So the question stays relevant: Why could this happen? I had a lot of power downs in the past and never had such an issue. The HA is protected by an usv. The conbeestick is plugged in a powered usb hub 3 meters away from the HA blue. Is this issue maybe related to the new architecture of deconz?
My major issue: I have to travel a lot. What happens, when my wife is alone at home. She never will be able to restore a backup in order to get the lights control up and running
Currently I’m trying to upload a DDF for my deconz stick.
However over Samba, I do not see all the folders and cannot navigate to my Deconz location.
Does someone know how I can open a file explorer to the root folder of HA, or either the Deconz addon so I can upload the DDF file?
Good evening,
I have the same issue here like @Pirol62 and @jonda since 2 weeks. I waited for a new deconz release but it only helped 3 days. Later on nearly every evening my zigbee network is not available and is reacting to nothing. Only a restart of the add-on is helping.
The problem is, there is no sign that the add-on is not working at all - it happens suddenly…the motion sensor for activating the cat-fountain is zigbee, so for me (and my cats) it’s pretty relevant to have a working add-on.
This is what I found in the protokoll - timeout on poll APS and a APSDE-Data issue:
18th Dec
19:30:29:169 Bind response success for 0x804b50fffe59b4a8 ep: 0x01 cluster: 0x0000
19:30:50:958 discovery for zombie 0xcc86ecfffe2e7902 dropped, last try was 571 seconds ago
19:30:52:598 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
19:30:57:258 0x50325ffffeaf0483 found group 0xFFF0
19:30:57:260 0x50325ffffeaf0483 found group 0x001B
19:31:02:138 binding for cluster 0x0000 of 0x0C4314FFFE2C55B4 exists (verified by reporting)
19:31:02:143 binding for cluster 0x0006 of 0x0C4314FFFE2C55B4 exists (verified by reporting)
19:31:02:147 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x0C4314FFFE2C55B4 (seems to be active)
19:31:02:150 binding for cluster 0x0008 of 0x0C4314FFFE2C55B4 exists (verified by reporting)
19:31:02:152 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x0C4314FFFE2C55B4 (seems to be active)
19:31:02:154 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
19:31:02:178 GW firmware version is up to date: 0x26400500
19:31:07:058 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
19:31:12:299 0x50325ffffebf5898 found group 0xFFF0
19:31:12:301 0x50325ffffebf5898 found group 0x001B
19:31:14:618 ZCL attribute report 0x04CD15FFFE7F7309 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
19:31:19:539 ZCL attribute report 0x04CD15FFFE7F7309 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
19:31:22:950 ZCL attribute report 0x0017880109A7C043 for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
19:31:26:269 ZCL attribute report 0x0C4314FFFE2C55B4 for cluster: 0x0008, ep: 0x01, frame control: 0x38, mfcode: 0x0000
19:31:37:139 binding for cluster 0x0000 of 0x50325FFFFEBF5898 exists (verified by reporting)
19:31:37:141 binding for cluster 0x0006 of 0x50325FFFFEBF5898 exists (verified by reporting)
19:31:37:144 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x50325FFFFEBF5898 (seems to be active)
19:31:37:147 binding for cluster 0x0008 of 0x50325FFFFEBF5898 exists (verified by reporting)
19:31:37:149 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x50325FFFFEBF5898 (seems to be active)
19:31:37:151 binding for cluster 0x0300 of 0x50325FFFFEBF5898 exists (verified by reporting)
19:31:37:153 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x50325FFFFEBF5898 (seems to be active)
19:31:37:155 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0x50325FFFFEBF5898 (seems to be active)
19:31:37:156 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0x50325FFFFEBF5898 (seems to be active)
19:31:37:158 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x50325FFFFEBF5898 (seems to be active)
19:31:47:139 binding for cluster 0x0000 of 0xB4E3F9FFFE73CAF9 exists (verified by reporting)
19:31:47:141 binding for cluster 0x0006 of 0xB4E3F9FFFE73CAF9 exists (verified by reporting)
19:31:47:144 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xB4E3F9FFFE73CAF9 (seems to be active)
19:31:47:146 binding for cluster 0x0008 of 0xB4E3F9FFFE73CAF9 exists (verified by reporting)
19:31:47:148 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xB4E3F9FFFE73CAF9 (seems to be active)
19:32:12:749 ZCL attribute report 0xB4E3F9FFFE73CAF9 for cluster: 0x0008, ep: 0x01, frame control: 0x38, mfcode: 0x0000
19:32:19:979 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0xC32E, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0058020000, zclSeq: 123
19:32:20:638 Set sensor check interval to 100 milliseconds
19:32:20:969 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
19:32:21:068 Bind response success for 0xd0cf5efffebe4c56 ep: 0x01 cluster: 0x0000
19:32:41:022 discovery for zombie 0xcc86ecfffe2e7902 dropped, last try was 681 seconds ago
PROTO: CRC error
19:32:44:329 Device protocol version: 0x010C
19:32:44:384 start reconnect to network
19:32:45:298 Skip idle timer callback, too early: elapsed 915 msec
19:32:45:330 CTRL ANT_CTRL 0x03
19:32:45:608 Device protocol version: 0x010C
19:32:49:138 reconnect network done
19:33:08:139 binding for cluster 0x0000 of 0x50325FFFFEAF0483 exists (verified by reporting)
19:33:08:141 binding for cluster 0x0006 of 0x50325FFFFEAF0483 exists (verified by reporting)
19:33:08:144 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x50325FFFFEAF0483 (seems to be active)
19:33:08:146 binding for cluster 0x0008 of 0x50325FFFFEAF0483 exists (verified by reporting)
19:33:08:148 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x50325FFFFEAF0483 (seems to be active)
19:33:08:150 binding for cluster 0x0300 of 0x50325FFFFEAF0483 exists (verified by reporting)
19:33:08:152 skip configure report for cluster: 0x0300 attr: 0x0007 of node 0x50325FFFFEAF0483 (seems to be active)
19:33:08:153 skip configure report for cluster: 0x0300 attr: 0x0003 of node 0x50325FFFFEAF0483 (seems to be active)
19:33:08:155 skip configure report for cluster: 0x0300 attr: 0x0004 of node 0x50325FFFFEAF0483 (seems to be active)
19:33:08:156 skip configure report for cluster: 0x0300 attr: 0x0008 of node 0x50325FFFFEAF0483 (seems to be active)
19:33:20:239 sensor 19 (TRADFRI motion sensor): disable presence
19:33:20:738 Set sensor check interval to 1000 milliseconds
19:33:46:103 0x04CD15FFFE657EEE error APSDE-DATA.confirm: 0xA7 on task
19:34:50:138 timeout on poll APS confirm
19:34:50:423 0x04CD15FFFE7F7309 error APSDE-DATA.confirm: 0xA7 on task
19:35:02:139 GW firmware version is up to date: 0x26400500
19:35:52:138 timeout on poll APS confirm
19:35:52:342 0xCC86ECFFFE952250 error APSDE-DATA.confirm: 0xA7 on task
19:36:23:542 0x0C4314FFFE2C55B4 error APSDE-DATA.confirm: 0xA7 on task
19:36:44:139 Skip idle timer callback, too early: elapsed 916 msec
19:36:56:023 0x04CD15FFFE657EEE error APSDE-DATA.confirm: 0xA7 on task
19:37:08:502 0xB4E3F9FFFE73CAF9 error APSDE-DATA.confirm: 0xA7 on task
19:38:01:139 timeout on poll APS confirm
19:39:02:138 timeout on poll APS confirm
19:39:02:141 GW firmware version is up to date: 0x26400500
19:40:03:138 timeout on poll APS confirm
19:41:05:138 timeout on poll APS confirm
19:42:05:138 timeout on poll APS confirm
19:42:06:138 drop request 183 send time 82894, cluster 0x0300, after 305 seconds
19:43:02:138 GW firmware version is up to date: 0x26400500
19:43:06:138 timeout on poll APS confirm
19:43:08:438 drop request 5 send time 82954, cluster 0x0000, after 307 seconds
19:44:08:138 timeout on poll APS confirm
19:44:09:138 drop request 6 send time 83015, cluster 0x0006, after 307 seconds
19:45:09:138 timeout on poll APS confirm
19:45:10:141 drop request 7 send time 83078, cluster 0x0006, after 305 seconds
19:46:10:138 timeout on poll APS confirm
19:46:10:938 drop request 8 send time 83138, cluster 0x0008, after 305 seconds
19:47:02:139 GW firmware version is up to date: 0x26400500
19:47:11:138 timeout on poll APS confirm
19:47:11:339 drop request 9 send time 83199, cluster 0x0000, after 305 seconds
19:48:11:138 timeout on poll APS confirm
19:48:12:139 drop request 10 send time 83261, cluster 0x0000, after 304 seconds
19:49:12:138 timeout on poll APS confirm
19:49:13:038 drop request 11 send time 83322, cluster 0x0000, after 303 seconds
19:49:44:366 Announced to internet https:// phoscon . de / discover
19:49:44:369 discovery server date: Sun, 18 Dec 2022 18:49:44 GMT
19:49:44:370 local time seems to be ok
19:50:13:138 timeout on poll APS confirm
19:50:15:338 drop request 12 send time 83383, cluster 0x0000, after 305 seconds
19:51:02:140 GW firmware version is up to date: 0x26400500
19:51:15:139 timeout on poll APS confirm
19:51:15:338 drop request 13 send time 83443, cluster 0x0006, after 305 seconds
Next issue: Beacon src updated and then the same timeout on poll APS:
17th Dec
19:43:34:676 Beacon src: 0xE110 ch: 11 updateId: 1
19:43:34:686 Beacon src: 0x40F2 ch: 11 updateId: 1
19:43:34:696 Beacon src: 0xA5AA ch: 11 updateId: 1
19:43:34:699 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:43:34:702 Beacon src: 0xE412 ch: 11 updateId: 1
19:43:34:707 Beacon src: 0x990C ch: 11 updateId: 1
19:43:34:712 Beacon src: 0x5057 ch: 11 updateId: 1
19:43:34:726 Beacon src: 0x0A37 ch: 11 updateId: 1
19:43:34:737 Beacon src: 0xD5CD ch: 11 updateId: 1
19:43:34:765 Beacon src: 0x257E ch: 11 updateId: 1
19:43:34:780 Beacon src: 0x2BFF ch: 11 updateId: 1
19:44:07:138 timeout on poll APS confirm
19:44:08:239 drop request 222 send time 336074, cluster 0x0006, after 305 seconds
19:45:03:140 GW firmware version is up to date: 0x26400500
19:45:08:139 timeout on poll APS confirm
19:45:08:239 drop request 223 send time 336135, cluster 0x0000, after 304 seconds
19:46:08:138 timeout on poll APS confirm
19:46:08:939 drop request 224 send time 336196, cluster 0x0000, after 303 seconds
19:46:10:579 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:13:062 Beacon src: 0x7320 ch: 11 updateId: 1
19:46:13:090 Beacon src: 0xE110 ch: 11 updateId: 1
19:46:13:096 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:13:101 Beacon src: 0x990C ch: 11 updateId: 1
19:46:13:137 Beacon src: 0x257E ch: 11 updateId: 1
19:46:13:147 Beacon src: 0x7D5C ch: 11 updateId: 1
19:46:13:149 Beacon src: 0x2BFF ch: 11 updateId: 1
19:46:13:161 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:46:16:146 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:46:16:151 Beacon src: 0x7320 ch: 11 updateId: 1
19:46:16:161 Beacon src: 0xE110 ch: 11 updateId: 1
19:46:16:171 Beacon src: 0x2BFF ch: 11 updateId: 1
19:46:16:217 Beacon src: 0x990C ch: 11 updateId: 1
19:46:16:222 Beacon src: 0x257E ch: 11 updateId: 1
19:46:16:236 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:16:241 Beacon src: 0x7D5C ch: 11 updateId: 1
19:46:18:700 Beacon src: 0x7320 ch: 11 updateId: 1
19:46:18:707 Beacon src: 0x1A90 ch: 11 updateId: 1
19:46:18:712 Beacon src: 0x257E ch: 11 updateId: 1
19:46:18:727 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:18:737 Beacon src: 0x990C ch: 11 updateId: 1
19:46:18:747 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:46:18:757 Beacon src: 0xE110 ch: 11 updateId: 1
19:46:18:803 Beacon src: 0x7D5C ch: 11 updateId: 1
19:46:18:808 Beacon src: 0x2BFF ch: 11 updateId: 1
19:46:21:836 Beacon src: 0x1A90 ch: 11 updateId: 1
19:46:21:841 Beacon src: 0x7320 ch: 11 updateId: 1
19:46:21:846 Beacon src: 0x990C ch: 11 updateId: 1
19:46:21:851 Beacon src: 0x2BFF ch: 11 updateId: 1
19:46:21:857 Beacon src: 0x7D5C ch: 11 updateId: 1
19:46:21:881 Beacon src: 0xE110 ch: 11 updateId: 1
19:46:21:904 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:46:21:941 Beacon src: 0x257E ch: 11 updateId: 1
19:46:21:952 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:24:298 Beacon src: 0x1A90 ch: 11 updateId: 1
19:46:24:303 Beacon src: 0xE110 ch: 11 updateId: 1
19:46:24:308 Beacon src: 0x7320 ch: 11 updateId: 1
19:46:24:313 Beacon src: 0x257E ch: 11 updateId: 1
19:46:24:340 Beacon src: 0x990C ch: 11 updateId: 1
19:46:24:346 Beacon src: 0x2BFF ch: 11 updateId: 1
19:46:24:378 Beacon src: 0x7D5C ch: 11 updateId: 1
19:46:24:392 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:46:24:397 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:27:410 Beacon src: 0x2BFF ch: 11 updateId: 1
19:46:27:415 Beacon src: 0x7D5C ch: 11 updateId: 1
19:46:27:420 Beacon src: 0x1A90 ch: 11 updateId: 1
19:46:27:425 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:46:27:458 Beacon src: 0xD705 ch: 11 updateId: 1
19:46:27:463 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:27:494 Beacon src: 0x257E ch: 11 updateId: 1
19:46:27:508 Beacon src: 0xE110 ch: 11 updateId: 1
19:46:27:519 Beacon src: 0x990C ch: 11 updateId: 1
19:46:29:859 Beacon src: 0x257E ch: 11 updateId: 1
19:46:29:864 Beacon src: 0x1A90 ch: 11 updateId: 1
19:46:29:869 Beacon src: 0x7320 ch: 11 updateId: 1
19:46:29:914 Beacon src: 0xE110 ch: 11 updateId: 1
19:46:29:931 Beacon src: 0x0A37 ch: 11 updateId: 1
19:46:29:936 Beacon src: 0x990C ch: 11 updateId: 1
19:46:29:964 Beacon src: 0x7D5C ch: 11 updateId: 1
19:46:29:970 Beacon src: 0x2BFF ch: 11 updateId: 1
19:46:29:975 Beacon src: 0xCAF2 ch: 11 updateId: 1
19:47:09:138 timeout on poll APS confirm
19:47:10:238 drop request 225 send time 336256, cluster 0x0300, after 305 seconds
19:48:10:138 timeout on poll APS confirm
19:48:10:239 drop request 226 send time 336317, cluster 0x0006, after 304 seconds
19:48:10:339 enqueue APS request failed with error 2, drop
19:49:03:139 GW firmware version is up to date: 0x26400500
19:49:10:138 timeout on poll APS confirm
19:49:11:139 enqueue APS request failed with error 2, drop
19:50:11:138 timeout on poll APS confirm
19:50:11:838 enqueue APS request failed with error 2, drop
19:50:48:139 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
19:50:53:139 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
19:50:58:139 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
19:51:03:140 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
19:51:08:140 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
19:51:12:138 timeout on poll APS confirm
19:51:12:239 enqueue APS request failed with error 2, drop
19:51:13:139 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
19:51:18:140 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
19:51:23:139 skip binding for attribute reporting of ep: 0x00 cluster 0x0000 (end-device might sleep)
Edit: Protokoll from todays freeze right now.
21st Dec
11:36:11:356 Beacon src: 0x7D5C ch: 11 updateId: 1
11:36:11:361 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:388 Beacon src: 0x257E ch: 11 updateId: 1
11:36:11:393 Beacon src: 0x0A37 ch: 11 updateId: 1
11:36:11:414 Beacon src: 0x257E ch: 11 updateId: 1
11:36:11:424 Beacon src: 0x7D5C ch: 11 updateId: 1
11:36:11:461 Beacon src: 0xCAF2 ch: 11 updateId: 1
11:36:11:467 Beacon src: 0x990C ch: 11 updateId: 1
11:36:11:472 Beacon src: 0xD705 ch: 11 updateId: 1
11:36:11:477 Beacon src: 0x2BFF ch: 11 updateId: 1
11:36:11:495 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:556 Beacon src: 0x7D5C ch: 11 updateId: 1
11:36:11:570 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:589 Beacon src: 0xD705 ch: 11 updateId: 1
11:36:11:594 Beacon src: 0xCAF2 ch: 11 updateId: 1
11:36:11:600 Beacon src: 0x0A37 ch: 11 updateId: 1
11:36:11:610 Beacon src: 0x2BFF ch: 11 updateId: 1
11:36:11:615 Beacon src: 0x990C ch: 11 updateId: 1
11:36:11:634 Beacon src: 0x257E ch: 11 updateId: 1
11:36:11:640 Beacon src: 0x2BFF ch: 11 updateId: 1
11:36:11:642 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:660 Beacon src: 0x0A37 ch: 11 updateId: 1
11:36:11:670 Beacon src: 0x990C ch: 11 updateId: 1
11:36:11:675 Beacon src: 0xCAF2 ch: 11 updateId: 1
11:36:11:686 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:742 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:753 Beacon src: 0x990C ch: 11 updateId: 1
11:36:11:768 Beacon src: 0x7D5C ch: 11 updateId: 1
11:36:11:773 Beacon src: 0x2BFF ch: 11 updateId: 1
11:36:11:778 Beacon src: 0xD705 ch: 11 updateId: 1
11:36:11:793 Beacon src: 0x0A37 ch: 11 updateId: 1
11:36:11:798 Beacon src: 0xCAF2 ch: 11 updateId: 1
11:36:11:829 Beacon src: 0x2BFF ch: 11 updateId: 1
11:36:11:834 Beacon src: 0x257E ch: 11 updateId: 1
11:36:11:846 Beacon src: 0x7D5C ch: 11 updateId: 1
11:36:11:861 Beacon src: 0xD705 ch: 11 updateId: 1
11:36:11:873 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:893 Beacon src: 0xCAF2 ch: 11 updateId: 1
11:36:11:903 Beacon src: 0xD705 ch: 11 updateId: 1
11:36:11:909 Beacon src: 0x257E ch: 11 updateId: 1
11:36:11:914 Beacon src: 0x990C ch: 11 updateId: 1
11:36:11:943 Beacon src: 0x0A37 ch: 11 updateId: 1
11:36:11:948 Beacon src: 0x2BFF ch: 11 updateId: 1
11:36:11:962 Beacon src: 0xCAF2 ch: 11 updateId: 1
11:36:11:968 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:11:991 Beacon src: 0x7D5C ch: 11 updateId: 1
11:36:12:015 Beacon src: 0xE110 ch: 11 updateId: 1
11:36:12:044 Beacon src: 0x257E ch: 11 updateId: 1
11:36:12:049 Beacon src: 0x990C ch: 11 updateId: 1
11:36:12:054 Beacon src: 0x2BFF ch: 11 updateId: 1
11:36:12:073 Beacon src: 0x7D5C ch: 11 updateId: 1
11:36:12:078 Beacon src: 0x257E ch: 11 updateId: 1
11:36:12:088 Beacon src: 0xCAF2 ch: 11 updateId: 1
11:36:12:117 Beacon src: 0xD705 ch: 11 updateId: 1
11:36:12:132 Beacon src: 0x0A37 ch: 11 updateId: 1
11:36:26:639 Skip idle timer callback, too early: elapsed 660 msec
11:37:02:138 timeout on poll APS confirm
11:37:10:338 drop request 44 send time 8527, cluster 0x0006, after 320 seconds
11:38:10:139 timeout on poll APS confirm
11:38:13:438 drop request 45 send time 8589, cluster 0x0000, after 321 seconds
11:39:13:138 timeout on poll APS confirm
11:39:14:438 drop request 46 send time 8656, cluster 0x0006, after 315 seconds
11:39:48:140 GW firmware version is up to date: 0x26400500
11:40:14:138 timeout on poll APS confirm
11:40:22:338 drop request 47 send time 8719, cluster 0x0006, after 320 seconds
11:41:22:138 timeout on poll APS confirm
11:41:24:438 drop request 48 send time 8780, cluster 0x0000, after 321 seconds
11:42:24:138 timeout on poll APS confirm
11:42:24:339 drop request 49 send time 8847, cluster 0x0006, after 314 seconds
11:43:24:139 timeout on poll APS confirm
11:43:24:839 drop request 50 send time 8910, cluster 0x0006, after 312 seconds
11:43:48:139 GW firmware version is up to date: 0x26400500
11:44:25:138 timeout on poll APS confirm
11:44:26:638 Skip idle timer callback, too early: elapsed 900 msec
11:44:26:939 drop request 51 send time 8971, cluster 0x0000, after 312 seconds
11:45:27:138 timeout on poll APS confirm
11:45:27:140 drop request 52 send time 9039, cluster 0x0006, after 304 seconds
11:45:27:239 enqueue APS request failed with error 2, drop
11:46:27:138 timeout on poll APS confirm
11:46:27:838 enqueue APS request failed with error 2, drop
11:47:28:138 timeout on poll APS confirm
11:47:34:438 enqueue APS request failed with error 2, drop
11:47:48:140 GW firmware version is up to date: 0x26400500
11:48:26:638 Skip idle timer callback, too early: elapsed 537 msec
11:48:34:139 timeout on poll APS confirm
11:48:35:438 enqueue APS request failed with error 2, drop
11:49:35:138 timeout on poll APS confirm
11:49:38:138 enqueue APS request failed with error 2, drop
11:50:38:138 timeout on poll APS confirm
11:50:39:238 enqueue APS request failed with error 2, drop
11:51:39:138 timeout on poll APS confirm
11:51:39:238 enqueue APS request failed with error 2, drop
11:51:48:140 GW firmware version is up to date: 0x26400500
11:52:26:638 Skip idle timer callback, too early: elapsed 537 msec
11:52:39:138 timeout on poll APS confirm
11:52:39:139 enqueue APS request failed with error 2, drop
11:53:39:138 timeout on poll APS confirm
11:53:39:838 enqueue APS request failed with error 2, drop
11:54:40:138 timeout on poll APS confirm
11:54:43:238 enqueue APS request failed with error 2, drop
I’ve also been waiting for the new release with hopes for a fix to this showstopping issue. I didn’t have a problem for a few days after the latest release as you mentioned but now it’s back to multiple failures a day again…
While waiting for the release I made an automation that restarts the add-on if anyone is at home but no deconz entities have been changes for a certain time period plus some other criteria’s which eased the problem for my significant other and myself a bit.
Good tho to hear that this issue seems to be present for many in here, if anyone finds a solution or if the issue is discussed on GitHub please share here.
However, having had this issue for so long now I see no other way soon but to bite the bullet and move all devices to some other zigbee solution in HA.
1 Like
Thanks for reporting, I have forwarded your experiences to deCONZ devs @Wayne23 and @jonda
I have myself refrained from upgrading due to similar reports.
Hi everyone, I’m not sure if this is the right place to ask for help, so please guide me if not.
I’m trying to add a new DDF file to deconz for a Tuya M100 presence detection sensor that I bought.
I cannot find a place to put the DDF file for deconz to see it.
Do someone know where can I the config folder of the deconz docker add on on host so I can place the file and then deconz see it?
I’m using Home Assistant OS on a raspberry pi 4 with deconz installed as add on.
One user suggested to go to the following path /mnt/data/supervisor/addons/data/core_deconz/. local/share/dresden-elektronik/deCONZ/devices but I get an error “No such file or directory”.
Any help would be greatly appreciated!
Why am I not seeing any deconz_event in HA despite the fact the the API Information page in Phoscon shows high activities in the event tab? I was under the impression that these events would also be found in HA (?)
I’m on HA Core 2022.12.8 and deConz 12.19.3
There should be two main causes for deconz_event not showing up. Either websocket is down or signaling on deconz side doesn’t work.
Why you still can see activities regardless on deconz side is because the ui also polls the api for data which the integration does not do.
And how do I check/verify if websocket is healthy or not, and if signaling works on the deConz side?
I can control my IKEA STARKVIND Airpurifier through the REST-API i.e.:
{
"config":{
"mode": "speed_3"
}
}
Controlling is one thing and reporting another. I forgot a third option which would be if the device pairing isn’t complete.
Do you get state updates in home assistant for other devices from Deconz? Enabling debug logs in home assistant for deconz integration should tell you if the websocket gets started our not