btw, fix for “loosing all entities after reboot”-issue, mentioned above
Didn’t check it my self (obviously, as deCONZ doesn’t start right now)
Didn’t check it my self (obviously, as deCONZ doesn’t start right now)
Hi Frederic,
Try to start the addon and then check what the supervisor log says (Supervisor -> System)
Thanks M1ke,
A, there we have some logs!
[supervisor.docker] Can’t start addon_core_deconz: 403 Client Error: Forbidden (“endpoint with name addon_core_deconz already exists in network hassio”)"
Googled around and found ppl with similar issues with other addons. Installed Portainer but when uninstalling the deCONZ addon also seems to successfully remove the docker image, at least, as a newbie, it looks like it is executing the uninstall correctly.
Re-install, bam, same error.
I might, of course, be looking at the wrong place in Portainer as I never used this tool before.
Hmm, very strange… After you uninstall the addon and then in Portainer go to Network -> hassio, are you still seeing deconz?
Nope, it’s never seen under network. Even when re-installed as it never manage to start. (and yes, I removed all hidden containers in the Portainer settings). Yes, very strange.
Right, at least that’s how it should be then 
Sounds too easy, but have you tried to restart the host machine? As the dev of the google drive backup addon said here, this seems to be a bug in docker and might be resolved with a supervisor/host restart. Also suggested here.
1 Like
Restarted HA MANY times but never did a full re-boot of the pi. It solved it! Thanks for your help M1ke!
1 Like
Fantastic! Hopefully the other issue you mentioned does not happen anymore 
Hi,
I’m also thinking about moving deconz to “bare metal”.
Since you’ve already done this: is it possible to set up deconz on a new pi and then use a backup done within the HA add-on to have all the devices available again on the new pi? Or do I have to connect and set them up all again?
Yes that should be possible
Hi. Yes. You create a backup from the Phoscon App.
And on the new Deconz you upload the saved backup (same screen in Phoscon)
Thanks for the quick answer, will give it a shot the next days.
Hi, I have deleted integration, restarted HASSIO, now when I try to add deconz in integration it asks for HOST IP address, ,in the past it gave it automatically (173 … something) , now nothing. How to know which address to put?
@KennethLavrsen how do you run your Deconz in Ubuntu? Is it bare metal (i think so) or some VM? Frankly speaking I’m getting tired with Deconz addon to HA not being too stable and not reporting properly states to HA, so I’m considering swithing to solution that would not require restart of Zigbee network every time I restart HA. However I’m limited in possibilities, so I can install Ubuntu in ESXi, install Deconz in, passthrough the Conbee 2 stick to VM and give it a try, but once again it is virtualized env, with Zigbee gateway not connected directly to Deconz…
Currently I’m running HA as ESXi VM, which includes also all addons… I’m wondering if moving to separate VM for Zigbee will improve stability. It will remove Docker from the picture and will make Zigbee independent of HA restarts, but will it really help? Also what is your experience with Deconz releases? I think Dresden Electronics is releasing new versions more frequently that these arrive to HA. How it works in practice?
Just to make it clear, when you restart ha, deconz won‘t restart. All docker container should run, unless you restart your hassOs! This shouldn‘t be this often.
My setting here is working like a charm.
I have more then 80 zigbee devices (osram, Ikea, Xiaomi and hue), no problems with the smart plugs and all are reporting fine!
To find a solution for your problem, I have several questions:
- what is your Setting?
- how many devices do you have?
- how many routing devices (wired devices) do you have?
- on what machine is hassOs installed?
For example, my initial setting was a rasbpi 2 with some devices. As my setting was growing, my rasbpi needed over 40 minutes for an update. Also my new ikea blinds didn‘t work properly.
That was why I replaced my rasbpi to a nuc. No Linux, just hassOs directly on it!
Well updates just takes about 5 minutes, restarts are done in a couple of seconds and my zigbee setup, with deconz as an addon, runs like a charm!
Hi jan, i am currently running hass.io on vm on a nuc and facing many stability problems with the conbee stick. What are the disadvantages from your point of view when someone runs hassos directly on nuc? Is it difficult to maintain the containers?
Personally I’m running HA VMware image on ESXi server. For ZigBee I’m using Conbee II stick passthrough to HA VM. I’m running Deconz as addon within the same VM. Majority of my devices are permanently powered (38 Ikea bulbs, 2 Ikea LED drivers, 4 power outlets), only remotes (4 Ikea on/off switches) and motion sensors (4 Ikea and 8 Aqara) are battery powered. As powered devices are spread across entire house in quite uniform manner, I do not see need for repeaters.
I made some WiFi reconfiguration recently, to avoid signal interference and this improved stability of Zigbee network substantially. Issues that I’m facing are rather on HA-Deconz connection… not all devices are always visible to HA (even if these are visible in Deconz) or their state is properly reported (e.g. HA thinks it switched off all of bulbs, but some stay switched on). I think it might be partially also related to Deconz itself - for example when I switch off deconz group of light and one buld stays on it has nothing to do with HA (it switches off single entity and get state update from Deconz, that all devices are switched off). This should be Zigbee network issue, since devices in such case are located 0.5~1m away from each other.
After restart usually I quite fast see all devices being available to HA, but evry few restarts it happens that one or few devices are unavailable in HA, while Deconz see these. In such scenario running deconz.device_refresh sometimes help… but not always.
Also what I do not like in this setup is that from time to time Conbee stick stops to be visible to HA (i do not see it HW config), so also Deconz could not find it. In such case restart of entire ESXi host is required to make it available again. Those are not frequent cases, but make life less comfortable, especially that it happens usually after HA restart, that I’m doing quite regularly for updates of software or configuration changes requireing restart.
1 Like
I run deconz on bare metal on Ubuntu Mate LTS. Installed with apt after adding the Phoscon repo. And I run the beta branch as I am always after latest device support
In /etc/apt/sources.list.d/deconz.list
deb [arch=amd64] http://phoscon.de/apt/deconz focal-beta main
Then apt update and apt install deconz
See the official docu. It is so easy
1 Like
Do you have the stick in the nuc USB port? Because conbee sticks don’t like usb3 ports. Extend with a usb2 cable and the problem is solved.
Well, I run hassOS directly on a nuc. No container, no vm.
There is a whole thread about this
you will find some pro and cons in there too.
For me the only con is, the waste of ressources (what some would say).
The pro is, I don’t have to maintain another system. No Linux or windows, which needs updates, where I have to assign ressources, etc.