I also just updated Deconz and have found that it’s not passing any entities via the integration 
Have you tried resetting the Hue bulbs and the sensors. I had to do the same, rebuild everything. I’ve realised i had to reset everything.
Took a bit of effort pairing but it eventually picked it up. Make sure your around a meter away from the conbee, i had to grab a few extension leads.
Hmm… Mine is also acting strange, eveytime I exit the WebUI and try to access again it displays the Phoscon-gw with an external IP then switches to my local IP after a minute. During that time home assistant throws an error notification stating that “login attempt has failed”. I have to reset my password everytime, during the error home assistant disconnects from the deconz integration (not passing the eneties).
Is that the case with you?
It looks like it was a problem with home assistant supporting the addon rather than the addon itself.
After updating to 0.103.3 I can confirm that it is all working for me. I have restarted hassio a few times and it continues from where I left off in the webui.
Just make sure you clear your browser cache and make snapshots of your current config incase something does go wrong
1 Like
That sounds awesome. But unfortunately you had reset it all already. Hopefully more confirmations will come from users who used their old 3.X version, updating to deconz 4.1 and 0.103.3 can confirm a stable upgrade.
Yes, I did reset all my devices while on 0.103.2 (sorry I didn’t make that clear). But even after I reset the devices, it was very flaky with the entities disappearing everytime I restarted hassio. But 0.103.3 seems to have fixed it for me (for now) I will report back if anything becomes unusual.
But I hope they release a fix that would work for everyone.
I upgraded to 4.1 and all my devices were unavailable in HA.
A reboot didn’t fix it either.
i removed deconz from the integrations and added it again and it all worked again.
What home assistant version are you running? Latest 0.103.3?
I was running 103.2 at the time but now running 103.3.
The one thing that doesn’t work now is the Phoscon page by typing in the address. It is only accessible via HA now (since the Ingress support was added).
Can anyone tell me how to reset my Phoscon password? I can’t login anymore. Maybe it got reset to a defaut password? What could that be? The restarting thing and afterwards trying to reset the password doesn’t seem to work either.
Ok, first of all, the update in 0.103.3, has nothing to do with the add-on upgrade we currently have. Yes it solved an issue we discovered in add-on version 4.0, but that was solved already with 4.1. So while I’ve added a fix to 0.103.3 for the future, it will not change any behavior with the latest version of the deCONZ add-on.
I’m sorry to hear some of you have issue now, based on all discussions I had the past days on several media, I’ve updated the documentation to cover a set of common cases and how to solve those.
The full and latest documentation of the add-on can be found here:
Added sections:
- Using the deCONZ/Phoscon API with another add-on (e.g, Node-RED)
- My gateway shows up in Home Assistant with ID 0000000000000000
- My integration shows now devices after upgrading to 4.x
Also, the Known issues and limitations has been extended to cover all current ones.
This should cover most of the cases and questions you guys have listed above.
3 Likes
Oh no… , I Do have the case of ID000000…
It sounds like much work and risk getting this changed.
I think I stay with deConz 3.8 until the end of all days which has no issues so far.
Thanks @frenck for the clarifications and all your work! As written before, my configuration seems to work fine despite the fact that I can’t access the deconz webpage because I can’t login. Passwort reset doesn’t seem to work (or I’m doing it wrong) and the default password doesn’t work either. Any hint is appreciated!
Yes same here…Suggestions unfortunately don’t work…can’t access the phoscon app without IP ban…disabled that but stil can’t get past the password input…tried “delight” but it’s not that…!!
2 Possible things going on (well others as well, but the following is the most obvious):
- Browser cache (clear it or try incognito)
- Outdated deconz discovery data. Solving this is easy go to the page that lists devices (before login). Leave it open, grab a coffee, 10 minutes later try to login.
Am I right, that I cannot access the API from outside hassio anymore??? Before I use the chrome addon “Postman” to list all sensors/lights to easily show all entitis.
In the past this works via Postman: “hassio.local:40850/api/xxxxxxxxx/sensors/”
If I follow the instrcutions here I get this weird IP address:
[
{
"id": "xxxxxxxxxxxxxxxxxx",
"internalipaddress": "172.30.33.0",
"macaddress": "xxxxxxxxxxxxx",
"internalport": 40850,
"name": "Phoscon-GW",
"publicipaddress": "myexternalipaddress"
}
]
Sidenote, and totally unrelated to your question: Update to the application, as the Postman extension will go away. 
Correct. Please read the add-on documentation, as that was answered in there.
See: Known issues and limitations
@frenck
Sorry but I dont understand your sidenote 
Ok, I had already read it in the new “Known issues and limitiations” but I was confused because there is a section " Using the deCONZ/Phoscon API with another add-on"… unfortunately I had read over the word “with another add-on”.
Could you give me a tip how to work inside hassio to access the API (to list all sensors).
Tried the first one already to no avail.
I’m not sure I understand the second suggestion. My workflow is like this:
- Click deconz on the sidebar
- A page opens whit a picture of a phoscon gateway plus the ip adress (172…)
- I click on the picture
- Password request => stuck here
What do you mean by “go to the page that lists devices (before login). Leave it open”?