deCONZ - Official thread

yan · July 3, 2019, 6:45am

I use the osram Smart plug for this.
It works Perfect, and costs around 12-15€.
All direct powered devices are working as repeaters.

cdrom1028 · July 3, 2019, 1:31pm

I am running deCONZ on hass.io with ConBee II (Firmware 26490700) and I don’t see my devices being populated in HA. My understanding was it just showed up no Yaml. Is this the case?

pergola.fabio · July 3, 2019, 1:48pm

Did you configure/add the deconz integration?

Robban · July 3, 2019, 1:48pm

Using the addon? Then it should work. Else yiu can configure it manually from the integrations pane

cdrom1028 · July 3, 2019, 2:00pm

My integrations pane is showing all unavailable and stale data. I removed the integration and am rebooting…

Update: integration re-added but no Sensors… is there a lag to the device poling where it could take time to see devices show?

Robban · July 3, 2019, 2:17pm

If deconz is working everything should be populated instantaneous

cdrom1028 · July 3, 2019, 2:26pm

Thats so weird… I get nothing indicating any issues other than there are no devices showing up…

[10:24:37] INFO: Starting VNC server...
[10:24:40] INFO: Starting the deCONZ gateway...
[10:24:40] INFO: Running the deCONZ OTA updater...
[10:24:40] INFO: Running the IKEA OTA updater...
[10:24:40] INFO: Running Hass.io discovery task...
{"uuid":"45073bc1238149ef84a95b092076e66a"}
[10:24:40] INFO: Success send discovery information to Home Assistant
[10:24:40] INFO: deCONZ is set up and running!
libpng warning: iCCP: known incorrect sRGB profile
10:24:40:909 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
10:24:40:920 CTRL. 3.22.010:24:40:937 COM: /dev/ttyACM1 / serialno: 
10:24:40:937 COM: --dev: /dev/ttyACM1 (ConBee II)
10:24:40:937 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
10:24:40:957 parent process bash
10:24:40:957 gw run mode: docker/hassio
10:24:40:957 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
10:24:40:958 DB sqlite version 3.22.0
10:24:40:958 DB PRAGMA page_count: 30
10:24:40:958 DB PRAGMA page_size: 4096
10:24:40:958 DB PRAGMA freelist_count: 0
10:24:40:958 DB file size 122880 bytes, free pages 0
10:24:40:958 DB PRAGMA user_version: 6
10:24:40:958 DB cleanup
10:24:40:958 DB create temporary views
10:24:40:959 don't close database yet, keep open for 900 seconds
10:24:40:959 started websocket server at port 40860
10:24:40:960 discovery updated announce interval to 10 minutes
10:24:40:960 found node plugin: libde_rest_plugin.so - REST API Plugin
10:24:40:960 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
10:24:41:145 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
10:24:41:158 COM: /dev/ttyACM1 / serialno: 
10:24:41:158 COM: --dev: /dev/ttyACM1 (ConBee II)
10:24:41:206 Device firmware version 0x26490700
10:24:41:211 unlocked max nodes: 200
10:24:41:305 Device protocol version: 0x010B
10:24:41:312 new node - ext: 0x00212effff04258c, nwk: 0x0000
10:24:41:321 SensorNode 2 set node 0x00158d0003499f43
10:24:41:321 SensorNode 3 set node 0x00158d0003499f43
10:24:41:321 SensorNode 4 set node 0x00158d0003499f43
10:24:41:345 ZDP node descriptor request to 0x00212EFFFF04258C
10:24:41:345 APS-DATA.request id: 4, addrmode: 0x02, addr: 0x0000, profile: 0x0000, cluster: 0x0002, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x04
10:24:41:345 ZDP send request id: 0x03 to 0x00212effff04258c
10:24:41:386 Current channel 11
10:24:41:410 CTRL ANT_CTRL 0x03
10:24:41:442 Device protocol version: 0x010B
10:24:41:509 Current channel 11
10:24:41:531 CTRL ANT_CTRL 0x03
10:24:41:587 APS-DATA.confirm id: 4, status: 0x00 SUCCESS
10:24:41:588 APS-DATA.confirm request id: 4 -> confirmed, timeout 1562163881
10:24:41:593 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8002, lqi: 241, rssi: 19
10:24:41:593 APS-DATA.indication request id: 4 -> finished
10:24:41:593 APS-DATA.request id: 4 erase from queue
10:24:41:593 ZDP status = 0x00 -> SUCCESS
10:24:41:593 ZDP Node_Descriptor_rsp 0x00212EFFFF04258C - 0x0000
10:24:41:745 ZDP active ep request to 0x00212effff04258c
10:24:41:745 APS-DATA.request id: 6, addrmode: 0x02, addr: 0x0000, profile: 0x0000, cluster: 0x0005, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
10:24:41:745 ZDP send request id: 0x07 to 0x00212effff04258c
10:24:41:762 APS-DATA.confirm id: 6, status: 0x00 SUCCESS
10:24:41:762 APS-DATA.confirm request id: 6 -> confirmed, timeout 1562163881
10:24:41:768 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8005, lqi: 241, rssi: 19
10:24:41:768 APS-DATA.indication request id: 6 -> finished
10:24:41:768 APS-DATA.request id: 6 erase from queue
10:24:41:768 ZDP status = 0x00 -> SUCCESS
10:24:41:768 ZDP active ep response for 0x00212effff04258c
10:24:41:768 	ep: 0x01
10:24:41:768 	ep: 0xF2

cdrom1028 · July 3, 2019, 2:47pm

I just noticed this…

2019-07-03 10:38:07 WARNING (MainThread) [homeassistant.components.http.auth] legacy_api_password support has been enabled.
2019-07-03 10:38:37 WARNING (MainThread) [.] Invalid key for deCONZ at 172.30.32.1
2019-07-03 10:38:37 ERROR (MainThread) [.] Error connecting with deCONZ gateway

Also I don’t have the deconz.device_refresh service …

cdrom1028 · July 3, 2019, 2:55pm

Should I just remove the Integration reboot and re-add it?

Robban · July 3, 2019, 3:01pm

Have you changed the add-on but not changed the api key? it is unique per deconz instance

cdrom1028 · July 3, 2019, 3:48pm

I had no Idea… can you point me to the documentation so I can update what i need to…

Robban · July 3, 2019, 3:52pm

You need to remove your deconz integration and pair again

cdrom1028 · July 3, 2019, 3:56pm

By remove remove your deconz integration, do you mean

remove from hassio
verify deconz is removed from integration panel and reboot
add deconz back to hassio and configure it then reboot again
check to see if things are working?

am I missing any other cleanup steps?

cdrom1028 · July 3, 2019, 4:50pm

Update:
I did this:

remove from hassio
verify deconz is removed from integration panel and reboot
add deconz back to hassio and configure it and add back to integration panel then reboot again
paired two Xiaomi sensors
check to see if things are working…

No Joy …

2019-07-03 12:44:02 WARNING (MainThread) [.] Invalid key for deCONZ at 172.30.32.1
2019-07-03 12:44:02 ERROR (MainThread) [.] Error connecting with deCONZ gateway

Robban · July 3, 2019, 4:59pm

Deconz is running fine and the sensors are working?

No need to restart after configuring the integration

cdrom1028 · July 3, 2019, 7:06pm

deCONZ is fine, the sensors are working but nothing gets populated into HA. no services, no devices…

Robban · July 3, 2019, 7:11pm

Time to share logs, enable debug per instructions in component documentation

cdrom1028 · July 3, 2019, 7:12pm

Here are logs from the component

15:11:46:658 Mgmt_Lqi_req zdpSeq: 66 to 0x00212EFFFF04258C start index 2
15:11:46:658 APS-DATA.request id: 150, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:11:46:667 APS-DATA.confirm id: 150, status: 0x00 SUCCESS
15:11:46:667 APS-DATA.confirm request id: 150 -> confirmed, timeout 1562181106
15:11:46:669 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19
15:11:46:669 APS-DATA.indication request id: 150 -> finished
15:11:46:669 APS-DATA.request id: 150 erase from queue
15:11:46:669 ZDP status = 0x00 -> SUCCESS
15:11:46:669 ZDP Mgmt_Lqi_rsp zdpSeq: 66 from 0x00212EFFFF04258C total: 3, startIndex: 2, listCount: 1
15:11:46:669     * neighbor: 0x00158D0003499F43 (0xF4D0), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:11:50:019 Mgmt_Lqi_req zdpSeq: 67 to 0x00212EFFFF04258C start index 0
15:11:50:019 APS-DATA.request id: 152, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:11:50:033 APS-DATA.confirm id: 152, status: 0x00 SUCCESS
15:11:50:033 APS-DATA.confirm request id: 152 -> confirmed, timeout 1562181110
15:11:50:040 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19
15:11:50:040 APS-DATA.indication request id: 152 -> finished
15:11:50:040 APS-DATA.request id: 152 erase from queue
15:11:50:040 ZDP status = 0x00 -> SUCCESS
15:11:50:040 ZDP Mgmt_Lqi_rsp zdpSeq: 67 from 0x00212EFFFF04258C total: 3, startIndex: 0, listCount: 2
15:11:50:040     * neighbor: 0x00158D00036B1DBE (0xB7E8), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:11:50:040     * different nwk address 0xB7E7 / 0xB7E8
15:11:50:498 Mgmt_Lqi_req zdpSeq: 68 to 0x00212EFFFF04258C start index 2
15:11:50:498 APS-DATA.request id: 154, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:11:50:514 APS-DATA.confirm id: 154, status: 0x00 SUCCESS
15:11:50:515 APS-DATA.confirm request id: 154 -> confirmed, timeout 1562181110
15:11:50:518 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19
15:11:50:518 APS-DATA.indication request id: 154 -> finished
15:11:50:518 APS-DATA.request id: 154 erase from queue
15:11:50:518 ZDP status = 0x00 -> SUCCESS
15:11:50:518 ZDP Mgmt_Lqi_rsp zdpSeq: 68 from 0x00212EFFFF04258C total: 3, startIndex: 2, listCount: 1
15:11:50:518     * neighbor: 0x00158D0003499F43 (0xF4D0), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:11:53:432 APS-DATA.indication srcAddr: 0xb7e7, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0402, lqi: 151, rssi: -75
15:11:53:432 no button map for: lumi.weather ep: 0x01 cl: 0x0402 cmd: 0x0A pl[0]: 000
15:11:53:432 ZCL attribute report 0x00158D00036B1DBE for cluster 0x0402, ep 0x01
15:11:53:443 APS-DATA.indication srcAddr: 0xb7e7, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0405, lqi: 151, rssi: -75
15:11:53:443 no button map for: lumi.weather ep: 0x01 cl: 0x0405 cmd: 0x0A pl[0]: 000
15:11:53:443 ZCL attribute report 0x00158D00036B1DBE for cluster 0x0405, ep 0x01
15:11:53:448 APS-DATA.indication srcAddr: 0xb7e7, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0403, lqi: 143, rssi: -76
15:11:53:448 no button map for: lumi.weather ep: 0x01 cl: 0x0403 cmd: 0x0A pl[0]: 000
15:11:53:448 ZCL attribute report 0x00158D00036B1DBE for cluster 0x0403, ep 0x01
15:11:53:859 Mgmt_Lqi_req zdpSeq: 69 to 0x00212EFFFF04258C start index 0
15:11:53:859 APS-DATA.request id: 162, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:11:53:875 APS-DATA.confirm id: 162, status: 0x00 SUCCESS
15:11:53:875 APS-DATA.confirm request id: 162 -> confirmed, timeout 1562181113
15:11:53:877 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 143, rssi: -76
15:11:53:877 APS-DATA.indication request id: 162 -> finished
15:11:53:877 APS-DATA.request id: 162 erase from queue
15:11:53:877 ZDP status = 0x00 -> SUCCESS
15:11:53:877 ZDP Mgmt_Lqi_rsp zdpSeq: 69 from 0x00212EFFFF04258C total: 4, startIndex: 0, listCount: 2
15:11:53:877     * neighbor: 0x00158D00036B1DBE (0xB7E7), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:11:54:339 Mgmt_Lqi_req zdpSeq: 70 to 0x00212EFFFF04258C start index 2
15:11:54:339 APS-DATA.request id: 164, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:11:54:355 APS-DATA.confirm id: 164, status: 0x00 SUCCESS
15:11:54:355 APS-DATA.confirm request id: 164 -> confirmed, timeout 1562181114
15:11:54:361 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 143, rssi: -76
15:11:54:361 APS-DATA.indication request id: 164 -> finished
15:11:54:361 APS-DATA.request id: 164 erase from queue
15:11:54:361 ZDP status = 0x00 -> SUCCESS
15:11:54:361 ZDP Mgmt_Lqi_rsp zdpSeq: 70 from 0x00212EFFFF04258C total: 4, startIndex: 2, listCount: 2
15:11:54:361     * neighbor: 0x00158D0003499F43 (0xF4D0), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:11:57:699 Mgmt_Lqi_req zdpSeq: 71 to 0x00212EFFFF04258C start index 0
15:11:57:699 APS-DATA.request id: 166, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:11:57:709 APS-DATA.confirm id: 166, status: 0x00 SUCCESS
15:11:57:709 APS-DATA.confirm request id: 166 -> confirmed, timeout 1562181117
15:11:57:711 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 143, rssi: -76
15:11:57:711 APS-DATA.indication request id: 166 -> finished
15:11:57:711 APS-DATA.request id: 166 erase from queue
15:11:57:711 ZDP status = 0x00 -> SUCCESS
15:11:57:711 ZDP Mgmt_Lqi_rsp zdpSeq: 71 from 0x00212EFFFF04258C total: 4, startIndex: 0, listCount: 2
15:11:57:711     * neighbor: 0x00158D00036B1DBE (0xB7E7), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:11:58:179 Mgmt_Lqi_req zdpSeq: 72 to 0x00212EFFFF04258C start index 2
15:11:58:179 APS-DATA.request id: 168, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:11:58:196 APS-DATA.confirm id: 168, status: 0x00 SUCCESS
15:11:58:196 APS-DATA.confirm request id: 168 -> confirmed, timeout 1562181118
15:11:58:200 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 143, rssi: -76
15:11:58:200 APS-DATA.indication request id: 168 -> finished
15:11:58:200 APS-DATA.request id: 168 erase from queue
15:11:58:200 ZDP status = 0x00 -> SUCCESS
15:11:58:200 ZDP Mgmt_Lqi_rsp zdpSeq: 72 from 0x00212EFFFF04258C total: 4, startIndex: 2, listCount: 2
15:11:58:200     * neighbor: 0x00158D0003499F43 (0xF4D0), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:12:01:538 Mgmt_Lqi_req zdpSeq: 73 to 0x00212EFFFF04258C start index 0
15:12:01:538 APS-DATA.request id: 170, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:12:01:548 APS-DATA.confirm id: 170, status: 0x00 SUCCESS
15:12:01:548 APS-DATA.confirm request id: 170 -> confirmed, timeout 1562181121
15:12:01:550 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 143, rssi: -76
15:12:01:550 APS-DATA.indication request id: 170 -> finished
15:12:01:550 APS-DATA.request id: 170 erase from queue
15:12:01:550 ZDP status = 0x00 -> SUCCESS
15:12:01:550 ZDP Mgmt_Lqi_rsp zdpSeq: 73 from 0x00212EFFFF04258C total: 4, startIndex: 0, listCount: 2
15:12:01:550     * neighbor: 0x00158D00036B1DBE (0xB7E7), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
15:12:02:019 Mgmt_Lqi_req zdpSeq: 74 to 0x00212EFFFF04258C start index 2
15:12:02:019 APS-DATA.request id: 172, addrmode: 0x03, addr: 0x00212effff04258c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:12:02:032 APS-DATA.confirm id: 172, status: 0x00 SUCCESS
15:12:02:032 APS-DATA.confirm request id: 172 -> confirmed, timeout 1562181122
15:12:02:035 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 143, rssi: -76
15:12:02:035 APS-DATA.indication request id: 172 -> finished
15:12:02:035 APS-DATA.request id: 172 erase from queue
15:12:02:035 ZDP status = 0x00 -> SUCCESS
15:12:02:035 ZDP Mgmt_Lqi_rsp zdpSeq: 74 from 0x00212EFFFF04258C total: 4, startIndex: 2, listCount: 2
15:12:02:035     * neighbor: 0x00158D0003499F43 (0xF4D0), LQI: 255, relation: 0x01 rxOnWHenIdle: 0

And here are the only entries from the Home Assistant logs that show any deCONZ related anything…

019-07-03 15:08:56 WARNING (MainThread) [.] Invalid key for deCONZ at 172.30.32.1
2019-07-03 15:08:56 ERROR (MainThread) [.] Error connecting with deCONZ gateway

cdrom1028 · July 3, 2019, 7:24pm

to me its clear that my issue is between deCONZ and Hassio. i get the weird “Invalid key for deCONZ” error, and nothing populates into the integrations.

Robban · July 3, 2019, 7:30pm

Those logs are for deconz, not the integration