Z2m can not start anymore after reboot

Configuration Zigbee
1

Hi,

Currently running a HassOS instance on a ProxMox server.
I noticed that after a reboot of the ProxMox server, the Z2M usb stick is not recognized anymore,and thus the Home Assistant Z2M addon can not start.
Simply unplugging the Z2M stick an plugging it into another usb port is enough repair this issue.

So, is there a way that the usb stick is recognized by home Assistant after a reboot of the ProxMox host?

Bart

2

Did you update the core and OS? I did yesterday, running HassOS bare bones, and Z2M is doing the same thing to me. I’m wondering if it has something to do with the newest update. I didn’t see any breaking changes for that.

3

I was already on the latest version. I upgraded the underlying ProxMox server an had to reboot the whole system.

However, I had the same issue when running hassos directly on a raspberry pi, so I don’t think it has anything to do with ProxMox.

So:

  • restarting HA: no problem
  • restarting underlying OS (HAOS on a barebone, or ProxMox server in my case) —> problem
4

@bartplessers Did you find a solution? I’m having te same issue

5

no, but for some reason I do not have this issue anymore…
I’m running HA 2024.3.3 with Z2M 1.36.1-1 now

6

If your Z2mqtt config is set to use the dev/tty path instead of dev/serial/by-id, this issue can occur because there’s no guarantee your coordinator gets assigned the same USB path on restart.

It’s mentioned in the Z2mqtt docs too, so have a read there for a better explanation.

7

Even than, this issue occured on my setup. But as I said, no problems anymore now

1 Like