I have an Intel BOXNUC7I3BNH
And it wont start after the update. I am stuck on the boot menu all i get when i pick one of the options it says:
Booting a comand list
Error: incorrect compressed chunk
Normal Home assistant installation no custom, all latest updates.
Open the images in new tab to see text… amature way to screshot but it is only one i have…
Might be unrelated to previous replies, but I’m also unable to boot after upgrade using VitrualBox VM. I’m able to reach BIOS but can’t proceed past that.
was just about to do this…think ill give it a miss for now as also running on an Intel NUC
@Sangoku @mrbasque this issue has been reported here as well: HA 8.0 fails to boot (incorrect compressed chunk) · Issue #1912 · home-assistant/operating-system · GitHub. It seems that GRUB2 has problems on some x86-64 systems reading from the compressed, squashfs bsaed kernel partition. Please share the details of your system in that issue report, it would help narrow down affected systems.
@Boklak we had similar reports during the RC, but it got resolved in 8.0 for most people, see Error updating versions higher than Home Assistant OS 8.0.dev20220321 · Issue #1830 · home-assistant/operating-system · GitHub. Did you upgrade to the final 8.0 release?
@LeoSko haven’t seen that issue so far, can you open an issue in the Home Assistant OS repository? Sign in to GitHub · GitHub
Homeassistant OS 8, in VMWare updated successfully, VMware, reports "Version Other Linux 5.x kernel 64-bit.
Ha reports Kernel version 5.15.38
Upgraded from latest OS, Supervisor, Core Versions
Windows 10 P(latest update), i7-4700MQ(MSI GE60), VMware VMCI Host Device - Driver Version 9.8.16.0 (Vmware Workstation 16)
PS: VMware installed on separate exFat Disk
Edit: All disks are GPT
NOTE: After reading below posts, i checked my HOST-File , and did found it “peculiar” thou i’ve never paid any special attention to the HOST-Log , But in regards to i’e network interfaces ect. Only USB shows a “strange behavior” ( New Device Found )
[ 1.367219] ACPI: bus type USB registered
[ 1.367534] usbcore: registered new interface driver usbfs
[ 1.368505] usbcore: registered new interface driver hub
[ 1.369544] usbcore: registered new device driver usb
[ 3.230689] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.236283] ehci-pci 0000:02:03.0: new USB bus registered, assigned bus number 1
[ 3.247889] ehci-pci 0000:02:03.0: USB 2.0 started, EHCI 1.00
[ 3.249986] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 3.252399] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.254494] usb usb1: Product: EHCI Host Controller
[ 3.255930] usb usb1: Manufacturer: Linux 5.15.38 ehci_hcd
[ 3.257543] usb usb1: SerialNumber: 0000:02:03.0
[ 3.259058] hub 1-0:1.0: USB hub found
[ 3.261589] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.264722] uhci_hcd: USB Universal Host Controller Interface driver
[ 3.268634] uhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 3.272893] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.15
[ 3.275313] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.277422] usb usb2: Product: UHCI Host Controller
[ 3.278850] usb usb2: Manufacturer: Linux 5.15.38 uhci_hcd
[ 3.280441] usb usb2: SerialNumber: 0000:02:00.0
[ 3.282287] hub 2-0:1.0: USB hub found
[ 3.287042] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
[ 3.293476] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 3.295925] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.298027] usb usb3: Product: xHCI Host Controller
[ 3.299455] usb usb3: Manufacturer: Linux 5.15.38 xhci-hcd
[ 3.301075] usb usb3: SerialNumber: 0000:03:00.0
[ 3.302654] hub 3-0:1.0: USB hub found
[ 3.307411] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4
[ 3.309596] xhci_hcd 0000:03:00.0: Host supports USB 3.1 Enhanced SuperSpeed
[ 3.311800] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 3.314125] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[ 3.316581] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.318687] usb usb4: Product: xHCI Host Controller
[ 3.320106] usb usb4: Manufacturer: Linux 5.15.38 xhci-hcd
[ 3.321768] usb usb4: SerialNumber: 0000:03:00.0
[ 3.323313] hub 4-0:1.0: USB hub found
[ 3.326657] usbcore: registered new interface driver usblp
[ 3.328465] usbcore: registered new interface driver usb-storage
[ 3.330281] usbcore: registered new interface driver usbserial_generic
[ 3.332171] usbserial: USB Serial support registered for generic
[ 3.388043] usbcore: registered new interface driver usbhid
[ 3.389908] usbhid: USB HID core driver
[ 3.505863] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[ 3.551880] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 3.781697] usb 2-1: New USB device found, idVendor=0e0f, idProduct=0008, bcdDevice= 1.00
[ 3.794160] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.805080] usb 2-1: Product: Virtual Bluetooth Adapter
[ 3.813894] usb 2-1: Manufacturer: VMware
[ 3.820846] usb 2-1: SerialNumber: 000650268328
[ 3.840706] usb 3-1: New USB device found, idVendor=0e0f, idProduct=0003, bcdDevice= 1.03
[ 3.845331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.849485] usb 3-1: Product: VMware Virtual USB Mouse
[ 3.852648] usb 3-1: Manufacturer: VMware
[ 3.860961] input: VMware VMware Virtual USB Mouse as /devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb3/3-1/3-1:1.0/0003:0E0F:0003.0001/input/input4
[ 3.869305] hid-generic 0003:0E0F:0003.0001: input,hidraw0: USB HID v1.10 Mouse [VMware VMware Virtual USB Mouse] on usb-0000:03:00.0-1/input0
[ 3.947009] usb 2-2: new full-speed USB device number 3 using uhci_hcd
[ 4.089167] usb 2-2: New USB device found, idVendor=0e0f, idProduct=0002, bcdDevice= 1.00
[ 4.092521] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.095298] usb 2-2: Product: VMware Virtual USB Hub
[ 4.097401] usb 2-2: Manufacturer: VMware, Inc.
[ 4.107190] hub 2-2:1.0: USB hub found
[ 5.061323] usbcore: registered new interface driver btusb
Could be the cause of “lost” USB-Devices, turning up as “New”, For some Users
EDIT: Maybe because i only have a wired mouse attached , everything was “seamless”
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
It’s a total mess 
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
For intel NUC the uefy boot menu was the solution.
I enabled legacy boot. Rebooted. enabled Uefy boot manager and it worked like a charm.
Fixed via totally shutting down (power off) the host then restarting. Thanks for the suggestion pergola.fabio!
Same here, cant turn off my lights in the middle of the night wanting to go to bed 
any fix yet on your side?
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…
BEFORE
AFTER
I’m afraid of restoring the previous Phoscon backup and having to pair my switches again…
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 
(*) mine is currently 2.15.3 / 21/04/2022
[Edit] I will try upgrade the FW manually following the instructions within that issue.
2 replies
I have a Raspbee II, version 2.15.03 / 21-4-2022. It’s also shown correctly, Can’t recall if it showed incorrect when it didn’t work.
For the Conbee II you should see a serial/by-id device like so (this is from my Rasberry Pi 4 test device running HAOS 8.0)
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.
What is your setup using exactly (what Raspberry Pi model/SD-card or SSD)?
When you connect a monitor after startup it often is not showing anything. If you try again, connect the monitor before updating. Your issue seems similar to what is described in this report: Restart issues on 8.0.rc1-4 - System seems to hang · Issue #1888 · home-assistant/operating-system · GitHub
Unfortunately, I was unable to reproduce this so far.
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
2 replies
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?
Im having some issues with the update.
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.
Someone having similar issues?
1 reply
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.
Is there a ver 8.1 or alike coming any time soon?
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.
1 reply
uncheck the other boot type to. then it shold read diferent partitions then before. That did the trick for me.
Having all kinds of issues after this install. Don’t even know where to begin. Can’t access supervisor or even its Logs or addons. Pulling the plug on RPi4 temporarily resolves it, but all issues come back after a while. Everything was working fine until OS 8.0 install. Is reverting back to 7.6 the same process as rolling back HA core?
Same issue for me.
Replying to myself.
Did a restore from a full backup/snapshot of yesterday (thank you Home Assistant Google Drive Backup add-on)
Like I was afraid, it did not fix the fact my ConBee II was still shown as a RaspBee in a “Not connected” state in the Phoscon interface
So I unplugged the Conbee stick and upgraded manually its firmware on Windows 10 following this tutorial.
Plugged back the stick on my extension cable on my RPi and got most things back like :
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2254892-if00 in Deconz add-onAll Zigbee devices seem to be up and running even those switches that are greyed out 
Thanks for your comment !
I had the exact same problem, after the update, no more connection to my Raspbee II.
I turns out the update also changed the device configuration to /dev/ttyS0 for me
I switched back to /dev/ttyAMA0 and now everything is back to normal
@JeromeO: Note that I had to trigger some state changes manually to get all my devices back online
Yes I am on a Pi 4 4GB. I’m also booting off a flash drive and not an SD card.
After updating to HA OS 8 on my RPi 4B my dashboard does not load in browser or android app, I cannot SMB or SSH via terminal from my Mac. Hooking the RPi up to my monitor, I see it boot successfully and get to the CLI ‘ha >’ prompt, but don’t really know where to go from here. Am I toast?
1 reply
Thanks, yeah, I have to find my USB keyboard. All I have right now is Bluetooth. I managed to get the dashboard to load on my phone app a few minutes ago, but by the time I got back to my laptop, it was no longer loading. I then rebooted my router and it seems to be loading everywhere now. I had unplugged my (EDIT: wrong controller) Nortek HUSBZB stick so all my ZigBee devices were unavailable. Plugged it back in and had to hit the “update configuration” button in the integration and everything seems to be back up and running. Very odd behavior.
I’m echoing similar problems in here. I have a Conbee II that I use with deCONZ. I can access the devices through the Phoscon interface in deCONZ to check sensors and turn switches on/off, but it isn’t communicating with HA. Everything from that on my dashboards just say “unavailable.”
Error connecting to deCONZ gateway at 172.30.33.4
10:42:41 PM – (ERROR) deCONZ - message first occurred at 3:48:05 PM and shows up 315 times
Config entry ‘00212E08411A’ for deconz integration not ready yet; Retrying in background
3:48:05 PM – (WARNING) config_entries.py
Apart from this, it seems like the options to restart HASSIO without restarting the host are missing? I only have the option to restart the host inside Settings > System > Hardware. I couldn’t find the ‘restart supervisor, restart hassio…’ that existed before, arey the hidden somewhere?
1 reply
Read the 2022.5 release announcement.
I can’t find a gateway IP in config_entries.
There is only a device path. But it’s the same path like in the hardware settings. So, I don’t know what to change.
What does your Phoscon interface look like ?
Is it messed up mike mine was ? => Home Assistant OS Release 8 - #17 by JeromeO (Raspbee instead of ConBee II and all)
What does your Deconz add-on config look like at https://[yourhost].duckdns.org:8123/hassio/addon/core_deconz/config ?
so OS8 completely borked my PI install. I did a fresh install, booted fine, then restored a full backup from google drive, and it rebooted, everything is fine, and then rebooted again, it has never rebooted successfully since. i don’t even know where to start trouble shooting.
Is there a way to do a fresh install with os7?
Here on the Rpi4 8Gb boot SSD everything works as expected without a problem on OS8
Thank you! This made it easy to do
figured this one out. The Insteon hub ip address is dynamic, so at upgrade the IP address changed. Once I reconfigured, it worked itself out. Strangely, I don’t have to keep updating the IP address after first config.
After initially having the same issue with my Conbee II USB zigbee dongle on the day OS8 was released a simple full power off and restart resolved the issue, however I had to restart the host again today and now I cannot get ZHA to connect to the dongle no matter how many times I do a full power cycle.
Device is showing under All Hardware, and the names match.
Keep getting the following error:
Logger: homeassistant.components.zha.core.gateway
Source: components/zha/core/gateway.py:182
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 8:24:58 pm (19 occurrences)
Last logged: 8:45:54 pm
Couldn't start deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II coordinator
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/serial/serialposix.py", line 322, in open
self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
OSError: [Errno 5] I/O error: '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2469004-if00'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 182, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.9/site-packages/zigpy/application.py", line 69, in new
await app.startup(auto_form)
File "/usr/local/lib/python3.9/site-packages/zigpy_deconz/zigbee/application.py", line 83, in startup
await self._api.connect()
File "/usr/local/lib/python3.9/site-packages/zigpy_deconz/api.py", line 254, in connect
self._uart = await zigpy_deconz.uart.connect(self._config, self)
File "/usr/local/lib/python3.9/site-packages/zigpy_deconz/uart.py", line 142, in connect
_, protocol = await serial_asyncio.create_serial_connection(
File "/usr/local/lib/python3.9/site-packages/serial_asyncio/__init__.py", line 448, in create_serial_connection
serial_instance = serial.serial_for_url(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/serial/__init__.py", line 90, in serial_for_url
instance.open()
File "/usr/local/lib/python3.9/site-packages/serial/serialposix.py", line 325, in open
raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))
serial.serialutil.SerialException: [Errno 5] could not open port /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2469004-if00: [Errno 5] I/O error: '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2469004-if00'
Hard to say as it is going to depend on your other hardware like ZigBee / Z-Wave stick etc.
Based on the data here, there are currently over 23,320 people running HA OS version 8.
Make a backup, save it external to your RPi and give it a try…
For anyone following this thread and worried about upgrading to 8.0 (I’m still on 7.6) - it looks like a fix will be included in 8.1 for the boot problems: HA 8.0 fails to boot (incorrect compressed chunk) · Issue #1912 · home-assistant/operating-system · GitHub
If you are using RaspBee II with a Raspberry Pi 3, make sure that you edit config.txt and remove any pi3- prefix from the overlay, e.g.
dtoverlay=miniuart-bt-overlay
enable_uart=1
Or if you don’t use Bluetooth, disable it entirly
dtoverlay=disable-bt-overlay
enable_uart=1
It seems that the Raspberry Pi team deprecated these overlays a while ago. See also Zigbee Home Automation - RaspBee II doesn't work after HA OS 8.0 upgrade · Issue #71950 · home-assistant/core · GitHub.
UPDATE 2:
Everything is working again after installing 8.1!
–
UPDATE: after connecting a monitor to my T620 it started to boot normally. HomeAssistant OS V8 is correctly installed and running fine. But when the monitor is disconnected it immediately fails to boot. `tried several times. Fiddled with some BIOS settings, but no luck. I’ll stick with the attached monitor for now and hope for the best when v8.1 is released.
I can confirm that upgrading 7.6 to 8.0 on proxmox went quite smoothly. Even de conbee2 stick git reattached without any manual intervention, but I’m using zigbee2mqtt since i had numerous issues with deconz on a vm - I don’t want to mention that z2m recognizes more devices tho but that’s a nice “side-effect”
On the other hand, upgrading to core 2022.5 (from 2022.3), which I did right after, took forever - was almost thinking something went wrong. But it just took forever.
OS 8.1 , Just installed ( think it was a “Beta” ), no apparent issues , thou for me neither before
Not sure now that it was (beta)
Q: is there a specific “Beta” Chanel/Topic in the Forum, or how does it work ?, if any issues/concerns/thoughts, and in specific if help needed to interpret/understand the OS log ?
1 reply
Yes i noticed that also, that’s why i noted that in Edit: ), thou i saw something, when i clicked the update (in regards to “beta”) , maybe because i’ve just signed up for “beta” 
… and have no idea how it works… yet…
Anyway as i don’t have the integrations, Devices(USB attached) that seems to have issues, i still don’t have any issues, with this update
ok, thanks , i was a turn into Github, so see whether i could get wiser in regards to the OS -releases etc.
… and this update didn’t address anything i have encountered , thou im still not “familiar” with certain repeated entries in the OS log, but not sure for how long they have been there, or whether it’s common for my VMware-image ( on my particular Board ) ( MSI GE 60 )
I.E
[ 1.574749] pci 0000:00:16.4: BAR 7: no space for [io size 0x1000]
[ 1.576574] pci 0000:00:16.4: BAR 7: failed to assign [io size 0x1000]
Not sure which port/device is “involved” here, i don’t have any obvious issues, but maybe related to a VMware installation.
And this ( just a little annoying ) , as the repeatedly adds to the log, after boot-up finnished (every minute or so)
[ 7507.471620] systemd-journald[114]: Time jumped backwards, rotating.
[ 7567.475824] systemd-journald[114]: Time jumped backwards, rotating.
[ 7627.477520] systemd-journald[114]: Time jumped backwards, rotating.
i Would feel more “comfortable” if it was Less, as it seems like alot redundant info to fill the log with
Upgrade to 8.1 for QEMU/KVM…haven’t found any particular problem
It is motioned in the Release Notes.
ℹ️ This release is currently on the beta channel! ℹ️
Yes , i did saw it, but as i “clicked” update i was unsure what i actually saw ( you could call it "total lack of short memory ) … but i actually did join Beta, the other day, but the guy in above post, did not
ok, but most likely they “pushed” this one out, for the people who have issues with boot and total loss of certain “hardware/ports/devices”, if you haven’t had any issues with 8.0, it should be safe to “include” 8.1, or wait for 8.2
Ok, maybe the “Update Channel” just indicates that i Joined “Beta Channel” , i guess i’ll find out eventually, maybe waiting with 8.2, until that is a “stable” version, and see whether “Update Channel” change
Looks like 8.1 has been bumped (rushed?) to stable without adjusting all release notes…
1 reply
Zigbee not working after 8.1 upgrade
Logger: zigpy_znp.zigbee.application
Source: /usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py:1080
First occurred: 17:17:05 (2 occurrences)
Last logged: 17:21:53Failed to reconnect
Traceback (most recent call last):
File “/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py”, line 847, in request
response = await response_future
asyncio.exceptions.CancelledErrorDuring handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py”, line 1075, in _reconnect
await self._startup()
File “/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py”, line 318, in _startup
await self.permit(time_s=0)
File “/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py”, line 517, in permit
response = await self._znp.request_callback_rsp(
File “/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py”, line 886, in request_callback_rsp
await self.request(request, **response_params)
File “/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py”, line 847, in request
response = await response_future
File “/usr/local/lib/python3.9/site-packages/async_timeout/init.py”, line 129, in aexit
self._do_exit(exc_type)
File “/usr/local/lib/python3.9/site-packages/async_timeout/init.py”, line 212, in _do_exit
raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:96
First occurred: 17:21:53 (2 occurrences)
Last logged: 17:21:53
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 886, in request_callback_rsp
await self.request(request, **response_params)
File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 842, in request
self._uart.send(frame)
AttributeError: 'NoneType' object has no attribute 'send'
Logger: homeassistant
Source: components/zha/core/channels/base.py:448
First occurred: 17:17:05 (2 occurrences)
Last logged: 17:21:53
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zha/light.py", line 522, in _refresh
await self.async_get_state()
File "/usr/src/homeassistant/homeassistant/components/zha/light.py", line 490, in async_get_state
results = await self._color_channel.get_attributes(
File "/usr/src/homeassistant/homeassistant/components/zha/core/channels/base.py", line 448, in _get_attributes
read, _ = await self.cluster.read_attributes(
File "/usr/local/lib/python3.9/site-packages/zigpy/zcl/__init__.py", line 441, in read_attributes
result = await self.read_attributes_raw(to_read, manufacturer=manufacturer)
File "/usr/local/lib/python3.9/site-packages/zigpy/device.py", line 293, in request
radio_result, msg = await self._application.request(
File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 439, in request
return await self._send_request(
File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 1401, in _send_request
response = await self._send_request_raw(
File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 1287, in _send_request_raw
self._znp.request_callback_rsp(
AttributeError: 'NoneType' object has no attribute 'request_callback_rsp'
I‘ve just updated without any issues from 7.6 to 8.1 on a HP ProDesk 600
Hi all. I previously updated to HAOS 8.0 without any issues. Just went to 8.1 and now it doesn’t boot at all. I’m not on the beta channel. RaspberryPi 4 4gb with everything on an external SSD. Tried unplugging the power several times but doesn’t seem to boot at all.
I’ll try to troubleshoot further tomorrow.
1 reply
I believe after so many restarts without a successful boot HA will try and restore the last successful boot.
Also having issues here, I’m getting an upgrade prompt to 8.1, however when I try to install it the system won’t boot, manually picking “slot A” instead of “slot B” at boot gets me back up and running, but on 8.0
I’m thinking 8.1 has some issues…
I had noted this on a separate thread, but my Raspbery Pi 3 Version B would not boot version 8.1. No green status light flashes, no video output. I reflashed version 8.0 and it booted. A reflashed 8.1, no boot. Reflashed 8.0 and it booted.
-Eric
Now on 8.1 and the front usb-s on my NUC wont work anymore. I can only use the backside ones… WHICH SUX! i now have 2 less usbs. And usb hubs wont work either
BOXNUC7I3BNH
x86 installation on a Dell Micro Optiplex.
After installing 8.1 initiating a reboot from HA the system won’t boot, it just hangs.
Power down and eventually it’ll boot after what seems an eternity.
Hopefully the next update sorts this otherwise I’ll have to go back a version or two as I seem to have lost the QNAP resource module now.
@JeromeO @zagnuts @smarthomelawyer @Insearchofth1ngs @vynsane @bobloadmire @Tuomas did you get your issues resolved?
2 replies
Yes, I stayed on Home Assistant OS 8.0 eventually and was able to flash my Conbee II stick on Windows to have it back up and running on HA.
I’m still not sure what caused the mess with my stick, the upgrade from HA OS 7.x to 8.0 and/or the update of the Deconz add-on that I triggered on the same day 
I’m staying away from HA OS 8.1 for now, too scared to break something else 
Home Assistant OS 8.1 64 bit fails to boot on CM4 with PCIE connected NVME drive.
Just a black screen and M.2 LED flashes.
32bit version boots ok.
i upgraded from I think 7.6 to 8.1 this morning. And now nothing works any more. I have x86 vim hosted with virt manager. For the initial installation I used the official container for Virt manager so I guess there is a real problem below this.
After a host restart HAOS came back. Now I’m super confused. Maybe the VM used an updated kernel module and I hadn’t restarted the host after updating that module.
7.6 → 8.1 upgraded fine for me on a RPI 8gb. Did two full hardware reboots to be safe
1 reply
Upgrading to core-2022.6.4 fixed the issue. Interesting, because the release notes do not seem to mention anything related…
Coming back to this, I did have a day of teething problems but also updated 2022.5 → 2022.6 the same day.
After several hard reboots and changing the default wifi reconnect tries it seems stable again 
Not that it helps you, but my son off ZigBee has worked on all 8.0 releases. Other issues but no issues with ZigBee. I can check firmware version when I get home if you want to compare.
Hi,
Since update (last night) the integration London Underground no longer works
Regards,
M
1 reply
Nevermind. Deactivated the zha-integration and activeted afterwards. And some host reboots later…
It seems to work now
I had no problem whatsoever with version 8 until I updated to 8.2, after that my intel NUC (BKNUC8CCHKR2) would no longer boot. It couldn’t find anything to boot.
Long story short, used an old SSD with an USB adapter to live boot linux mint, copied my last backup elsewhere and then re-installed 8.2 from scratch (wrote the latest home assistant image to the on-board emmc) and restored the backup again. Although the whole thing was annoying and cost me a few hours, I was surprised to see how well the update restore works.
And the more I think about it, the issue must have been with the update/upgrade because otherwise the fresh 8.2 install wouldn’t have run either…
Just to give an update. Just upgraded to 8.2 and everything went smoothly!
this might be a more generic question, but running HAOS in dev nightly’s in a Virtual box, I have a perfect instance, which cant update however, because the partition (10GB) is fully used.
Don’t understand with what exactly, but it seems I need the resize that partition.
How can I proceed doing that? Didnt find any related option in the Instance itself, so take it is is an OS option?
thanks for having a look!
1 reply
In VMware you just rezise The partition/disk, HA image is configured to automaticly take advantage off the added disk/Partition space