I don’t have any experience with the addons since I run hass and deconz in standalone dockers. There are some issues with deconz addon on hassio github. Maybe see if they experience the same issue. Else it might be worth creating a new issue regarding your problem
I have the same problem. Ever since upgrading to 2.0 all my zigbee entities has gone unavailable and can not log in to phoscon. The logo starts spinning and searches for gateways then nothing. Back to logo and no way to go further into phoscon. Worked perfectly before upgrading.
Running hass.io on a rpi3
Config entry for deconz not ready yet. Retrying in 80 seconds.
18:02 config_entries.py (WARNING) - message first occured at 16:21 and shows up 76 times
Error connecting to deCONZ gateway at 172.30.33.0
18:02 components/deconz/gateway.py (ERROR) - message first occured at 16:20 and shows up 80 times
The issue mentioned is in Phoscon, you are mentioning config entry. Can you give a bit more details here?
Ok, done a bit more investigation here, have tried resetting the gateway numerous times (there is a lesson here I’m sure about doing a backup of the network, but I didn’t learn it! Not sure it would have helped here though). Long story short, I have reset the gateway and can access it (once the add-on has been re-installed and started). Not through the UI entry point on the add-on , but via
<ip-address-of-host>:40850
So far so good. I have then gone through various cycles of changing the channel and don’t seem to be able to add any sensors etc. I can see from the logs that they are being recognised from the scan process,
08:48:19:008 0x7E70 nwk changed to 0x6687
08:48:19:009 device announce 0x00158D0002B4CED6 (0x6687) mac capabilities 0x80
08:48:19:009 set fast probe address to 0x00158D0002B4CED6 (0x6687)
08:48:19:009 FP indication 0x0000 / 0x0013 (0x00158D0002B4CED6 / 0x7E70)
08:48:19:009 ... (0x00158D0002B4CED6 / 0x6687)
08:48:19:009 device announce 0x00158D0002B4CED6 (0x6687) mac capabilities 0x80
08:48:19:121 FP indication 0x0104 / 0x0000 (0x00158D0002B4CED6 / 0x6687)
08:48:19:121 ... (0x00158D0002B4CED6 / 0x6687)
08:48:19:121 ZCL attribute report 0x00158D0002B4CED6 for cluster 0x0000, ep 0x01
08:48:19:121 0x00158D0002B4CED6 skip Xiaomi attribute 0x0000
08:48:19:201 FP indication 0x0104 / 0x0000 (0x00158D0002B4CED6 / 0x6687)
08:48:19:201 ... (0x00158D0002B4CED6 / 0x6687)
08:48:19:201 ZCL attribute report 0x00158D0002B4CED6 for cluster 0x0000, ep 0x01
08:48:19:297 FP indication 0x0104 / 0x0000 (0x00158D0002B4CED6 / 0x6687)
08:48:19:297 ... (0x00158D0002B4CED6 / 0x6687)
08:48:19:297 Remember Xiaomi special for 0x00158D0002B4CED6
08:48:19:297 ZCL attribute report 0x00158D0002B4CED6 for cluster 0x0000, ep 0x01
08:48:19:297 0x00158D0002B4CED6 extract Xiaomi special attribute 0xFF02
08:48:19:297 64 on/off 0
08:48:19:297 01 battery 2995 (0x0BB3)
08:48:19:297 03 unsupported index (data type 0x21)
08:48:19:297 04 unsupported index (data type 0x24)
08:48:19:297 05 unsupported index (data type 0x21)
08:48:19:297 06 unsupported index (data type 0x20)
08:48:19:906 [1] get node descriptor for 0x00158d0002b4ced6
08:48:31:118 New websocket 192.168.86.207:33824 (state: 3)
08:48:40:211 verified group capacity: 25 and group count: 0 of LightNode 0x0017880103883fb5
08:48:52:996 APS-DATA.indication from unknown node 0x00158D00023A6B60
08:48:52:997 ZCL attribute report 0x00158D00023A6B60 for cluster 0x0000, ep 0x01
08:48:52:997 0x00158D00023A6B60 extract Xiaomi special attribute 0xFF01
08:48:52:997 01 battery 2985 (0x0BA9)
08:48:52:997 03 temperature 20 °C
08:48:52:997 04 unknown 5032 (0x13A8)
08:48:52:997 05 RSSI dB (?) 10 (0x000A)
08:48:52:997 06 LQI (?) 12884901888 (0x0300000000)
08:48:52:997 08 unknown 516 (0x0204)
08:48:52:997 0a unknown 0 (0x0000)
08:48:52:997 64 on/off 0
08:49:06:448 Search sensors done
08:49:08:107 send permit join, duration: 59
08:49:15:671 Current channel 25
but at least in Phoscon they are not being recognised or added.
I did have a go at downgrading back to 1.4, but I’m using hassio in docker on a ubuntu box and whilst I can pull the older image, I’m not able to create the new container outside of hassio itself, so I’m stuck.
So left it a bit and came back to it later. Reset the gateway (which incidentally changed to channel 11.
I’m now able to add back in the individual door sensors and will gradually restore the others as I get time. Moral of the story is to make sure there is a backup of the config before mucking about with anything. 
Not quite sure why they wouldn’t add earlier, but I’ll just count my blessings that it’s working now. On a side note I now think my zwave network seems so much simpler and reliable than zigbee…
1 Like
Another member shared some pictures of his newly arrived Conbee2
Questions:
I am using add-on from marthdoc… want to go to official add-on now…
So what is best practice to convert? Don’t want loose to much… Is all stuff saved on stick? Is it as easy to remove integration, start new add-on, make new integration? Or are all entity names lost?
Also, with marthdoc edition firmware upgrade was possible in putty, is that also possible with official?
I can’t find any docs
Thnx
Ok, phoscon names are restored, but what about entities names for lux sensors and stuff, those things not visible in phoscon?
And firmware? How does that work?
Hi, would be the same if I want to migrate from a deCONZ/Conbee attached and configured on a different raspberry pi3, and want to bring the stick to a NUC, on which I have a HASSIO installation?
Shouldn’t be any difference, the computer is definitely changeable
Hi not sure if this has been asked already.
Is it possible to send POST URL messages from a browser to trigger deCONZ devices?
What do you want to do?
You have the configure service
When HASS is down beeing able to use zigbee devices without having to open the phoscon app.
I do have deconz/conbee on a separate pi3 that is rock solid. My HASS is not rock solid, too often there are problems.
Now I use HTTP Shortcut for all my ESPhome flashed WiFi ESP devices and I can control them even if HASS is down.
Wish to do the same with the zigbee devices
You can set up remotes to work even though phoscon is down, maybe that would be the better solution for this?
If you still want to do browser commands you can use https://dresden-elektronik.github.io/deconz-rest-doc/ if you don’t want to use phoscon frontend
Basically this for a light
PUT /api/<apikey>/lights/<id>/state
1 Like
Any idea what it means when nodes don’t have a link to them like above? I can most of the time still control them from home assistant, but occasionally they don’t respond. I’m guessing the link quality is low since they are far from the computer with the conbee usb stick.
As you can see I have 2 routers, the one named ‘Kitchen Cabinet Lights’ is an Ikea Tradfri outlet switch that is known to act as a router/repeater. The Mud Room Motion Sensor is an Xioami Aquara motion sensor. I thought just putting the router close to the motion sensor would cause the motion sensor to use it as it’s parent instead of the coordinator, but that doesn’t seem to be the case. Does anyone know how to make the motion sensor use the ikea tradfri outlet as it’s parent?
I’ve read that if you take the hub offline for 20 minutes then bring it back online it may be enough time where the motion sensor will look for a new parent, but it’s not clear. Do I need to put the motion sensor in pairing mode during this time or will it just seek out a new parent automatically?
Any assistance is appreciated!
I think you guessed correctly. Solution is to put a router in the middle (a Zigbee light bulb or power socket )
In my case many time was a matter of waiting a day or so, and the mesh would fix itself
where can I find the apikey and the ID of the devices?