Deconz for Hass.io


#42

Guess again :wink:

I’m running on an big ass VM server. Resources are not the issue.

Before I switched to the Hass io plugin, I had a separated VM running Ubuntu and Deconz, and one running Hass io. I saw similar behaviour when I booted the vm’s at the same time.

When I restart Hass io, all devices are present.

I think the issue is in the Deconz plugin, with adding devices after hass io startup.


#43

If you could check to see if you get messages over websocket with something akin to ‘added’


#44

Ok. Would you mind enabling debug for deconz component to see if you get any messages from Deconz about added devices?

I assume you mean the debug ouput for the home assistant component ?

Can’t find how to do this from the documentation page:


#45

If resources aren’t the issue then it’s Hass.io and the startup sequence. I’m guessing that deCONZ just needs some time to read it’s database, etc before it’s ready to serve devices over the API.


#46

I’ve added a PR on how to debug deconz.

logger:
  default: debug
  logs:
    pydeconz: debug
    homeassistant.components.deconz: debug

#47

Hi
I successfully installed conbee and deconz addon in hassio on my intel nuc. I use xiaomi aqara push buttons, fire detectors, temperature sensors, water leak and motion sensors.
I can see my devices and connect them to conbee network when the conbee is plugged into my windows machine with deconz gui. But in hassio web interface or home assistant, all my sensors and switches are invisible. I cannot see any devices/sensors to use. I have done several restarts ets… Also successfully accessed the web interface, got the api code , changed password etc.

Anyone has any good tips on how to proceed?
Best
/PH


#48

Enable the debug logging per instructions from the component documentation :+1:


#49

Ill do that :slight_smile: in the meantime, here is the logging from the add-on log.

08:02:57:470 Device protocol version: 0x0105
08:02:57:483 CTRL restore cached node 0x00212effff022d51
08:02:57:484 new node - ext: 0x00212effff022d51, nwk: 0x0000
08:02:57:611 Current channel 15
08:02:57:655 CTRL ANT_CTRL 0x02
08:02:57:760 Device protocol version: 0x0105
08:02:57:901 Current channel 15
08:02:57:945 CTRL ANT_CTRL 0x02
08:02:58:109 ZCL attribute report 0x00158D0001A669FE for cluster 0x0000, ep 0x01
08:02:58:109 0x00158D0001A669FE skip Xiaomi attribute 0x0005
08:02:58:109 0x00158D0001A669FE extract Xiaomi special
08:02:58:109 01 battery 3115 (0x0C2B)
08:02:58:109 03 temperature 24 °C
08:02:58:110 APS-DATA.indication from unknown node 0x00158D0001A669FE
08:02:58:143 ZCL attribute report 0x00158D00016C5451 for cluster 0x0000, ep 0x01
08:02:58:143 0x00158D00016C5451 skip Xiaomi attribute 0x0005
08:02:58:143 0x00158D00016C5451 extract Xiaomi special
08:02:58:143 01 battery 3025 (0x0BD1)
08:02:58:143 03 temperature 26 °C
08:02:58:143 APS-DATA.indication from unknown node 0x00158D00016C5451
08:02:58:177 ZCL attribute report 0x00158D0001A669FE for cluster 0x0000, ep 0x01
08:02:58:177 0x00158D0001A669FE skip Xiaomi attribute 0x0005
08:02:58:177 0x00158D0001A669FE extract Xiaomi special
08:02:58:177 01 battery 3115 (0x0C2B)
08:02:58:177 03 temperature 24 °C
08:02:58:177 APS-DATA.indication from unknown node 0x00158D0001A669FE
08:03:01:766 New websocket 192.168.86.109:63336 (state: 3)

and

08:03:26:810 Daylight now: goldenHour1, status: 160
08:03:31:187 ZCL attribute report 0x00158D0001B91F8B for cluster 0x0402, ep 0x01
08:03:31:187 APS-DATA.indication from unknown node 0x00158D0001B91F8B
08:03:31:207 ZCL attribute report 0x00158D0001B91F8B for cluster 0x0405, ep 0x01
08:03:31:207 APS-DATA.indication from unknown node 0x00158D0001B91F8B
08:03:31:230 ZCL attribute report 0x00158D0001B91F8B for cluster 0x0403, ep 0x01
08:03:31:230 APS-DATA.indication from unknown node 0x00158D0001B91F8B
08:03:33:914 scan finished
08:03:36:810 Daylight now: goldenHour1, status: 160
08:03:41:465 ZCL attribute report 0x00158D0001B91F8B for cluster 0x0402, ep 0x01
08:03:41:465 APS-DATA.indication from unknown node 0x00158D0001B91F8B
08:03:41:485 ZCL attribute report 0x00158D0001B91F8B for cluster 0x0405, ep 0x01
08:03:41:485 APS-DATA.indication from unknown node 0x00158D0001B91F8B
08:03:41:507 ZCL attribute report 0x00158D0001B91F8B for cluster 0x0403, ep 0x01
08:03:41:507 APS-DATA.indication from unknown node 0x00158D0001B91F8B


#50

This is only logs about the mesh network. Nothing relevant when debugging deconz <-> hass communication.


#51

Thank you. Now, logs are enabled. What info would you like (log is almost 10 000 rows)


#52

If you don’t get deconz devices in to HASS it would be good to see the initialization part of deconz component


#53

This part isn’t quite clear to me - can you see any devices in the deCONZ web ui (either Wireless Light Control or Phoscon)? In Wireless Light Control, on the settings menu at the bottom, does it list your device’s channel and network id (it should, given the logs you’ve posted from the deCONZ add-on). If your devices aren’t showing up in the deCONZ UIs, then they won’t show up in Home Assistant either.


#54

Thank you for your interest in this :slight_smile:
No, no devices shows in wireless light control or phoscon.

Settings page says: “Your gateway is on channel 15 and has the network Id 0xf037”

If I instead put the conbee in my windows machine and run the deconz program and GUI, all devices show including status changes (blue flashing lights in gui) when buttons are pressed etc.


#55

This is very strange - I would raise an issue at the deconz rest API GitHub page since this sounds like a deconz issue rather than a Home Assistant issue.


#56

Have you registered your devices to your conbee while on your windows machine? If so, you will need to make sure that all database files are copied over to your new machine because conbee doesn’t store any information directly on the stick


#57

That’s true about the device details but he should still see devices populated in the Web UIs since the devices are paired to the Conbee itself - they just wouldn’t have any custom names (also I think scenes and groups might not be present).


#58

@gjong what’s the update procedure for your add-on?
Now I’m running the 2.05.10 version and every time I reboot my Raspberry Pi, the deconz configuration panel is shown in home assistant and I have to unlock the gateway. May be that the new version solves this problem?


#59

Updating should be easy, just download the latest version and overwite the addon folder of the plugin. Then in the interface hit upgrade, do not uninstall the previous version first.

With Regards to hassio lossing it’s Connection, that should not happen. The addon persists all configuration and group information to a persistent directory. After reboot are the group still present in deconz? If so the reboot did not erase the configuratie.

Perhaps the hassio configuration files get remove in the /config directory. The deconz plugin created several files with generated configuration.


#60

I did as you said, the update button from de deconz web interface doesn’t work and from hassio there isn’t upgrade buttons


#61

It should have an update or upgrade button in the hassio interface. Go onto the addon in the hassio and it is next to the Start, stop and uninstall buttons. The update will taken some Time as it has to compile the image on the pi itself.

If you are not comfortabel doing this manually every time, downloaden copying over the files and manually updating I suggest looping into the addon from marthoc. It is easier to use and works fine. If you want to change to that addon then first create an backup from with in the deconz software. You can then install the other addon and restore the backup from within deconz.