i have just installed a new raspbian image on my rpi; then installed docker, portainer and docker compose. In raspi-config I enabled the serial interface (not logon) and rebooted.
My zwave device is an AeoTec z-stick Gen5+ in an USB2 port.
My zwave USB device under /dev/ttyAMA0
stty -F /dev/ttyAMA0
`speed 3000000 baud; line = 15;
min = 1; time = 0;
-brkint -icrnl -imaxbel
-opost
-isig -icanon -iexten -echo
Looking back at this, they /dev/serial/by-id/<device_id> path is probably the way to go with this. I recall a while back having similar issues. I think this originates from udev and changing device ID’s.
This is ultimately what drove me to moving my setup to a virtualenv instead of docker, but if you really want to stay with the docker setup, try finding the exact path in /dev/serial/by-id and map that to /dev/ttyACM0 or whatever your homeassistant config is looking for.
Apparently the AeoTec ZStick Gen5+ has an USB design flaw which is incompatible with RPI4.
As i just bought it new on Amazon, I’m going to return it. The workaround is to use an USB hub.
Yes…the only way to know you have the “fixed” version is to look at the graphics on the stick. Aeotec didn’t change the model number…and stores/sellers all say NEW which only indicates it hasn’t been opened, but not if it’s the latest design. As you said, the solution is to use the cheapest usb 2 hub you can find (less than $2 on EBAY). Personally, if I didn’t already own an Aeotec stick, I’d buy one from a different manufacturer…IMHO, Aeotec should have changed the model or version number instead of essentially forcing you to buy directly from them to know you are getting the “fixed” stick.