RPi4 over here. Upgraded to HA OS 8.0 and the Deconz firmware which strangely shows “Not connected” in Phoscon…
I am using Deconz add-on 6.13.0
After restarting, Deconz is no longer booting up.
On https://xxx.duckdns.org:8123/hassio/addon/core_deconz/config , line /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2254892-if00
seems to be playing hide and seek.
After selecting it eventually and clicking Save, error ?! Failed to save add-on configuration
I had a canable USB stick too , not connected anymore… In my case I had to turn off, not restart… After boot it was up again, maybe that helps with deconz too… running on esxi here
I switched off my RPi, unplugged the Conbee 2 stick, restarted HA and the host, all this no to avail.
I’ve just noticed that, in the Phoscon interface, my Conbee II name and logo had been replaced by Raspbee with a new icon
So I’m wondering if the firmware update I made within the Phoscon interface has not broken something…
So FWIW updated to 8.0 and after restarting nothing. Pulled the power a couple of times, still nothing. My 'pi is normally running headless so I hooked up a monitor and could see nothing - so another cold boot - and this time it started up ok albeit running 7.6 so it had reverted to the fallback. I might hold off trying the update for a few days…
Had some issues after upgrading to 8.0. Very long shutdown and boot-up times. It failed boot once; got hung up on the docker container initialization, and went into emergency shell. Another forced reboot and i saw it flash up quickly and select “slot 2”, and it booted ok, but still took forever.
Noticed it was using almost all the allocated 8GB of ram before reboot, but only 3 GB after reboot.
running HASS OS under Proxmox 7.1 in OVMF, 4 cores, 128GB partition, 8 GB RAM, 2x USB 2.0 devices passed through by ID (Conbee II and zWave stick),
AddOns: Deconz, zWave JS, SSH, Studio Code Server, HACS, ESPHome
I noticed in the deconz config the device address had changed to the wrong one suddenly, changing this back fixed it for me. In my case it was set to /dev/ttyS0 while it had to be the /dev/ttyAMA0
Hmm, interesting.
Even when I choose /dev/ttyAMA0 , Save and restart the add-on, the stick is still not picked up.
Yesterday I upgraded HA OS to 8.0 AND upgraded the Deconz firmware (within the Phoscon interface)
Not sure which one broke something, if not both…
I could restore a previous version of Hassio (downgrading to OS 7.x) but I’m not sure it’ll be sufficient since I also updated the firmware in Phoscon (which I don’t know how to downgrade)
Anyway, in the Phoscon web interface, what version of firmware do you have (*) and does it say RaspBee or ConBee II like it should ?
I’m afraid if I “Reset gateway” (in Phoscon) I will have to pair all my devices again
I guess deCONZ changed the graphics because you are using a ttyAMA0 device, which is what you would use if you had a Raspbee II.
If the serial/by-id device not appearing anymore, there is some lower level problem (driver not loading correctly/hardware problem). Are the host (kernel dmesg) logs saying something? Also try to unplug/replug the device at runtime.
Yep, I do get that entry /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2254892-if00
if I play around with the tabs and radio buttons going back and forth
But like mentioned earlier, whenever this entry shows up and I select it, saving fails…
I’ll try to upgrade the Conbee II stick manually on Windows thanks to these links
Hm, that is weird, can you try restart the add-on and then save again? Maybe the front-end somehow has stale config entries, is the device still listed when reloading using Ctrl+F5? If its still present, is there maybe something in the Supervisor logs?
My hassio is working (OS version running in a laptop) but only in the SLOT A. When I try to reboot using the WebUI I dont know why but It tries to boot from SLOT B and it get stuck in a weird screen. It is weird because its like half loaded hal not loaded so can’t see very well the error or the last component loaded.
Hmmm… There are quite a number of various boot problem reported in the net.
I’.m quite sure there are lots of people following the discussions and not updating before there is an indication that the problems are corrected. I’m one of them I always read release notes and issue reports before updating.
I had the same issue as most people where my Home-Assistant wouldn’t start back up after the install of OS 8. I ended up having to pull the power and let the unit cool down before powering it back up. That resolved the issue for me.
any fix yet on your side?
I always read release notes and issue reports before updating.