I truly hope it will fix everybody’s issues and wishes.
If it does not appear in your Hass.io panel yet, please go to Hass.io add-on store and hit the refresh icon in the top right. Next refresh your browser and the upgrade appears.
Please note: It is advised to use Home Assistant 0.103.4 or newer!
The add-on has now auto-healing capabilities. So in case of any issues, restart the add-on, wait at least 1 minute, restart Home Assistant and after that, everything should be normal again (In terms of the connection between Home Assistant and the add-on).
Sorry about the inconvenience and thanks for the patience.
Merry Christmas
Changelog:
Fix additional gateway visible on Phoscon login on Ingress
Fix Phoscon device scanning/probing triggering IP bans
Fix redirect to login page when Phoscon session expires
Fix incorrect manifest request from Phoscon frontend
Fix and improve API key handling with Hass.io discovery
Change Hass.io discovery to use add-on IP instead of hostname
Improve Phoscon discovery to work different and faster with Ingress
Add Websocket support to Ingress for instant and snappy UI updates
Re-instate direct access capabilities to the Phoscon/deCONZ API
Hi, thanks a lot.
Obviously you worked like a dog in order to get all the things fixed before Christmas.
Respect and appreciation.
Merry Christmas for you and your family.
I know there is still an issue with this when using Safari or when browser cache gets in the way. Flushing your browser data, use incognito or use chrome (or a combination of the previous). Might help there.
That said, with 5.0 you should not need to remove the add-on. Remove the integration from Home Assistant. Restart Home Assistant (not reboot). Restart the add-on, wait 1 or 2 minutes. Restart Home Assistant once more. Go to the Integrations panel. Home Assistant should have discovered the gateway. Add it. Done. (That is basically the flow to get you out of a real shitty issue).
I am still on 3.9 and 103.3…
What’s the correct procedure the update? Do I also need to remove integration? Or just update ha and deconz add-on , just like normal
@pergola.fabio If your integration shows ID 0000000: yes. If not, you should be able to just upgrade to add-on v5. However, I highly recommend to update Home Assistant to 0.103.4 first.
Another case that might cause issues, is when you have added the integration manually in the past. (instead of using the discovered version).
I have Home Assistant 0.100.2 on Raspberry Pi 4 + deCONZ 3.6 + ConBee II dongle.
I use several Zigbee devices.
Raspberry Pi is connected to the local network and the Internet via an Ethernet cable.
I wanted to check if the system would work without an Ethernet connection.
I unplugged the cable and used the switch to turn off the bulb.
It turns out that the system is not working.
When I connected the Ethernet cable again, after a few seconds the bulb went out.
Why is it like that?
I thought that since I only use Zigbee devices, the system will work even after disconnecting the Ethernet cable.
I came from 103.0 / 3.9. Upgraded to 103.4. Restarted. Everything was as normal.
Upgraded to 5.0. The integration seemed to work, all the entities were there when I went Configuration > Integration > deCONZ, but HA could find them. Restarted HA, same thing.
Deleted the integration, restarted HA, HA found deCONZ and suggested an integration, everything works.
…but since all devices got their default names, I had to change all of them back. Not that meny lights, but all thermometers that randomly got entity_name/entity_name_2 for humidity/temperature.
All in all, now it seems to work fine again.
Hat’s off for @frenck, great work. Unbelievable effort today, fighting off all impatient users and solving the problems at the same time. Hope you get some time off now, really well earned.
@ 0.103.4 and 5.0: Everything seams to work now, also after a restart of HA, but now I can’t login on the internal Phoscon site with it’s set password. Default “delight” also does not work.
The login sometimes does not work; after a few retries it will but this is somewhat strange behavior…
This can be caused by browser cache & cookies. The Phoscon app has actually some data stored in the cookies, clearing them will help. Or, it will just improve over time as thing start to expire.
From version 4 and 5 I cannot reach anymore the GUI using that address, instead it opens inside the Hassio GUI. Is there a way to restore the old behaviour?
Upgraded to 5.0…Just to confirm do you have to enter the password everytime in phoscon or is there a way to retain this information when you restart homeassistant. Thanks for the hardwork @frenck.
Add-on v5.0 is available right now.
