So far, I’ve gone through all the updates smoothly from HassOS 5.0 to the current HaOS 6.0.
Rpi4 8GB boot SSD.
1 Like
I am in the same situation, I have a USB Coral accelerator and would like to use it with Frigate within HaOS. I have Frigate working but its using my CPUs and would rather use the USB Coral accelerator for object detection.
What is the kernel option or module name for that option?
1 Like
What is a proxmox host? do you have 2 servers? I was hoping to have Frigate + Coral USB for object detection within HaOS.
I deserved that
2 Likes
After update to Home Assistant OS 6.1 the status of my zwave devices changed to Unavailable 
I maked changes:
Set manually usb_path: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 in configuration.yaml
And now see that status is “Ready”
But after the system started - it’s not changed. I can’t on/off devices from UI. Or if I click light button - in UI it’s not changed. Last status was get when system booted:
It’s bug in 6.1 HA OS? How fix?
When I try light to on in UI in OZW_Log.txt I see these lines:
2021-06-24 11:33:07.620 Detail, Node004, Polling: COMMAND_CLASS_SENSOR_MULTILEVEL index = 1 instance = 1 (poll queue has 0 messages)
2021-06-24 11:33:07.620 Detail, Node004, Queuing (Poll) SensorMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x31, 0x04, 0x25, 0x1f, 0xec
2021-06-24 11:33:07.621 Detail,
2021-06-24 11:33:07.621 Info, Node004, Sending (Poll) message (Callback ID=0x1f, Expected Reply=0x04) - SensorMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x31, 0x04, 0x25, 0x1f, 0xec
2021-06-24 11:33:08.622 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2021-06-24 11:33:08.623 Detail, Node004, Removing current message
2021-06-24 11:33:08.623 Detail, Node004, Notification: Notification - TimeOut
2021-06-24 11:33:31.150 Info, Node011, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Dimming Duration - 5 - 1 - 255
2021-06-24 11:33:31.152 Detail, Node011, Refreshed Value: old value=255, new value=255, type=byte
2021-06-24 11:33:31.152 Detail, Node011, Changes to this value are not verified
2021-06-24 11:33:31.153 Detail, Node011, Notification: ValueChanged
2021-06-24 11:33:31.155 Info, Node011, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 255
2021-06-24 11:33:31.155 Info, Node011, SwitchMultilevel::Set - Setting to level 255
2021-06-24 11:33:31.155 Info, Node011, Duration: Default
2021-06-24 11:33:31.156 Detail, Node011, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Set (Node=11): 0x01, 0x0f, 0x00, 0x13, 0x0b, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x01, 0xff, 0xff, 0x25, 0x20, 0xaf
2021-06-24 11:33:31.156 Detail, Node011, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=11): 0x01, 0x0d, 0x00, 0x13, 0x0b, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x21, 0xa1
2021-06-24 11:33:31.170 Detail,
2021-06-24 11:33:31.170 Info, Node011, Sending (Send) message (Callback ID=0x20, Expected Reply=0x13) - MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Set (Node=11): 0x01, 0x0f, 0x00, 0x13, 0x0b, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x01, 0xff, 0xff, 0x25, 0x20, 0xaf
2021-06-24 11:33:32.171 Error, Node011, ERROR: Dropping command, expected response not received after 1 attempt(s)
2021-06-24 11:33:32.171 Detail, Node011, Removing current message
2021-06-24 11:33:32.171 Detail, Node011, Notification: Notification - TimeOut
2021-06-24 11:33:32.175 Detail,
2021-06-24 11:33:32.175 Info, Node011, Sending (Send) message (Callback ID=0x21, Expected Reply=0x04) - MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=11): 0x01, 0x0d, 0x00, 0x13, 0x0b, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x21, 0xa1
2021-06-24 11:33:33.175 Error, Node011, ERROR: Dropping command, expected response not received after 1 attempt(s)
2021-06-24 11:33:33.176 Detail, Node011, Removing current message
2021-06-24 11:33:33.176 Detail, Node011, Notification: Notification - TimeOut
Please, help me fix it!
I’ve been running unraid in a VM on Unraid (hassos_ovm-2.12). Is there ever a reason to update the qcow2 file as newer ones become available or is effectively updated internally?
Hi!
I got the same error, and don´n know why… think it has to be some install/uninstall script that caused it, as i never touched that path manually.
Did you solved it and run the upgrade?
Hi!
Got the same problem, did you figured out why and upgrade your HA instance?
solved it, just created the missing directory like this:
mkdir -p /usr/local/lib/python3.8/site-packages/httpcore-0.13.6.dist-info/METADATA
Hi all,
just to share my experience as I had to rollback to 5.13.
[Raspberry pi 4]
After the update to the 6 all the add-ons pages where extremely slow to load (+40s). The supervisor page included. i could not find any specific errors in the logs. Inspecting the page i’ve realized the the entrypoint.<code>.js was taking ~36s to load. As well all the web assesst. For example the favicon.ico was loading in 5s. Basically every web assest was taking much longer loading time than required.
All the other pages ( history, map, logbook ) were loading fine.
I did try both the core rollback and the os rollback from the cli, but both were failing because the download was hitting a timeout and could not finish.
Error: Can't fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/5.13/hassos_rpi4-5.13.raucb: Response payload is not completed. Even additional dns in coreDns did not solve the issue.
The only solution was to download the previous release version of the os in a usb storage key and bootstrap it physically form the device.
The bootstrap failed and i had to use the command systemctl restart hassos-config which finally rolled back the OS and fixed all the problems.
Hopefully someone else will be able to find specific logs for this issue so it can be fixed in the next releases.
David.
Thanks for the info!
Sorry for the late reply as I was on vacation. In my instance I believe it sorted itself after a few days. I think the Check Home Assistant configuration add-on auto updated and I believe that resolved the issue with the check. No manual actions required on my part.
Cheers 
Hi!
No problem at all, i found that it was the configuration checker itself that is (or was) buggy.
It was confirmed by the developers them selves 
After some cleanup of a couple of deprecated things, upgrade to 2021.6.6 went fine.
1 Like