Home Assistant OS 17.2 and ZWave JS UI

Hi all,

I have updated both my HomeAssistant installations with OS 17.2 this morning. After rebooting, they both show: “Driver: failed to open the serial port. error: no such file or directory, cannot open /dev/serial/by-id/…” No hardware changes. I do not even see the USB port in System–Hardware-All Hardware. I rebooted both systems, and nothing fixes it. Any idea why this is happening?

Thanks!

I just noticed a similar issue with Zigbee. It says: “Unknown command.” in the Control Panel, and Zigbee devices do not work. The 17.2 update seems to have impacted all USB connected dongles (running on a RPi4).

I’ve got a yellow with a RPi4 module in it and just updated to OS 17.2. USB based Z-wave is fine, as is Zigbee using the internal radio.

I reverted to OS 17.1 and everything is back to normal, on both instances. Something is wrong with the 17.2 update for sure…

You have not mentioned your hardware / environment.

1 Like

RPi 4. Others have reported the same issue and logged it on the repo.

Did the update on my vm no problem

Some updates… The issue seems to be related to the firmware and bootloader versions of some RPi 4 and 5. Some reported that updating the firmware/bootloader separately, and re-applying the 17.2 update has worked. I will try this tonight.

This seems to be the issue on GitHub dealing with (and resolving) this problem on certain versions of Pi4 machines, and at that only running a certain bootloader version on the Pi

I confirm that applying this process has addressed the issue and I was able to update to 17.2.

The linked issue (now locked) seems to assume that only the RPi4B Rev 1.4 is impacted, but also tells that “old rpi4” are impacted. I have a rev 1.2 which is arguably older that 1.4.

Should I upgrade my EEPROM bootloader ? If so, where to ask for the public instructions to be updated to avoid misleading information ?

I did not yet update to 17.2 nor update the EEPROM. Do you want me to try first updating HAOS to check whether things break ? Or are rev 1.2 boards certain to have the problem anyway ?

My Homeassistant runs from an SSD instead of an SD card. I can SSH into the HA, but running the update fails:

rpi-eeprom-update -a

lspci: invalid option – ‘d’
rpi-eeprom-update is only available when booting from an SD card or if flashrom can be used.

Can I just use a ‘plain’ Raspbian SD as described, update the EEPROM and reboot from the USB HDD? Or will the update also mess around with the boot options? Any help / feedback would be highly appreciated!

use this method mentioned on the GitHub issue if you have a spare SD card…

(as an aside, in terms of the error you are seeing I’d guess you are SSH into HA and not HAOS as they are two different things to access)

I know that alternative, see my post :wink: I just want to make sure that the Pi will afterwards still boot from my ext USB SSD and not be stuck booting from a non-existent SD :wink:

2 Likes

so if you knew :wink: why did you ask me then by replying direct to my post :man_shrugging:t2:

So the solution is to update the EEPROM bootloader, using either an SD card or enable developer SSH access using a USB drive.

I’m guessing there is no solution for remote systems that are 4 hours away without visiting the site, correct?

Did you figure this out? I have the same question.

Hi Peter! I had to go on business travel before I could give it a try. I created an update SD and will run the test next Saturday/Sunday when I’m back home. Per se, the latest firmware should still support USB boot. Worst case: another boot from SD is necessary and the boot-loader-options re-written ( sudo -E rpi-eeprom-config --edit - see also: https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER) Hope this helps - If you can wait, I’ll give you a heads up in a week :wink: