Take a backup in Phoscon and then delete and re-add the add-on. You shouldn’t need the backup but just in case.
Hi all, I run into the following issue. I installed deconz as a Hassio addon. When I restart the host (an Intel Nuc) via supervisor, the authentication between the Phoscon and home assistant seems to fail. I either need to remove the integration and re-add phoscon again or restart home assistant via configuration -> server controls -> restart server.
I am running home assistant 0.110.4 and deconz 5.3.4. I recently had to reconnect my devices to deconz again after upgrading the stick. not sure if that had anything to do with it. Thanks
System is fucked up again after a power cut last night.
Now I can’t access my 50+ lights.
Tried everything that I can think of.
What are my options? Which is the best way to start from scratch (hopefully without the need to reset all lights, a tragedy for me, because some lights are not easily accessible)
. I am so tired of this s***
I un installed the addon, removed the stick, reinserted it, installed the addon, load a backup.
The lights in the phoscon app are there but all unresponsive. If I go with VNC the lights are all there but zero mesh.
After one hour is still like that (no mesh). What do I do bedsde opening the trash can and throw all my IOT devices into it?
Did you try to update your conbee or raspbee? last firmware update has a fix for this kind of bug if I remember correctly
Ohh, well I just updated to 26330500 but situation is the same.
So now I try to
- reboot the host, then what? uninstall the addon and reinstall the addon?
Ohhh perhaps is this???
Last firmware seems to be 26350500 (from March 2020):
http://deconz.dresden-elektronik.de/deconz-firmware/?C=M;O=D
26330500 is from last year (22-Apr-2019).
also Conbee 1, I have Conbee 1, and I did the update automatically. How to do it manually ???
EDIT OK, now it asks by itself to upgrade to 26350500 , this guy is making all by himself
EDIT EDIT, no after update, the firmware stays to 26330500 …man this thing was working until yesterday, I have no cue which upate, but I did update regularly. Since this morning was not working I did a gateway reset, so I guess it resets itself to a very old firmware, but now I can’t update
See above, theres an issue updating to latest firmware
I’ve usually ended up sticking the conbee in my laptop and flashing with GCflasher manually.
And as for the problems noted above. Have you tried restoring a backup? Or a snapshot in hassio?
Hi, ok, I put my Conbee stick to an unused raspberry pi3 (just wanted to move out from HASSIO integration if the poroblem is there with HASSoS 4.8) , downloaded the GCFFlasher utility the 26350500 firmware, and flashed, that went well. Then I installed deconz 2.05.77 latest. Then I uploaded a backup (a bit older from december 2019 of my lights).
Now deconz-gui started, phoscon-app works, but still no mesh. Everything is up to date and I am on a pi3 (not HASSIO). but still NO MESH.
What are the options now? Is there something else I can do?
BTW does a HASSIO backup contain a raspbee_gateway_config backup configuration file?
Hi there, how would I go about adding a device that is not on the ConBee2 compatibility list? Specifically I have a Stitchy switch and a dimmer. Have not powered them up yet. Is there a Deconz debug facility or similar for reporting zigbee codes/packets so I could add a custom device?
If they report using generic data they “could” potentially work out of the box even though they’re not on the supported list
1 Like
thanks, they are labelled “Phillips Hue compatible” so maybe they will work out of the box. Thanks for the link you provided. Half way down that page they say “If the device is not listed … a new issue should be created with the information as described below” which says to get screenshots of “clusters of the node” and “node info panel”. Where is that panel located? What software do I need to run to show that?
Yeah, Philips Hue compatible definitely increases the likelihood of it working out of the box. Thats the deconz desktop frontend, you can reach it using vnc if you run deconz in docker/addon
1 Like
In general most Zigbee devices that are lights just work. That part of the Zigbee standard seems to be handled the same way and everyone wants to be compatible with Philips Hue hub
In general any remote control (switch) not on the supported list, will not work.
1 Like
I just did the update of the Deconz add-on to 5.3.5. After reading the changelog, it was actually a downgrade though?
However, now HASS is not able to connect to any of the DeconZ entities anymore, while in Phoscon they are all there and work. So something is wrong with the latest update of the add-on and it breaks it connection somehow to HASS (integration still shows up and is not removed).
On Github seems I’m not the only one experiencing this?
I’ve rebooted the HASS server in it’s entirety as well, but the entities in HASS do not connect back and show as unavailable.
Only error I see in the log so far:
Logger: homeassistant.helpers.service
Source: helpers/service.py:423
First occurred: 5:24:57 PM (2 occurrences)
Last logged: 5:32:12 PM
Unable to find referenced entities light.attic_light_5, light.attic_light_6, light.attic_light_7, light.attic_light_8
Unable to find referenced entities cover.window_covering_device_18, cover.window_covering_device_19
In the Supervisor log I do see the following (Docker IP of Deconz):
20-06-04 16:06:47 ERROR (SyncWorker_9) [asyncio] Unclosed connection
client_connection: Connection<ConnectionKey(host='172.30.33.1', port=8099, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None)>
How can I best troubleshoot to provide some more useful info?
It’s a quite urgent matter because now all my zigbee lights and devices are not working with HASS in the house 
which are almost all the lights I have…
For situations like that, I highly recommend binding switches directly to light groups so that you can control the lights with wall buttons if HA or deconz stops working.
But it is to late for you now. You have to get your system up and running before anything else.
1 Like
Gee, I’m glad I read the change log before clicking update. When I read it was a downgrade, I decided not to, as my setup was working fine (if it ain’t broke…). Sorry if this is rubbing salt into people’s wounds who did update but I’ve learnt the hard way not to blindly click update on everything.
I gave up trying to do this with Ikea stuff as it was just too brittle. Switches would randomly stop working with lights or the hub and then going through the process of re-binding them would stuff up any other switches I had not disconnected the batteries for… such a headache.