I use a symlink to access my rfxcom device on raspberry pi, to sidestep the problem of the device moving between ttyUSB0 and ttyUSB1 after reboots. However the latest HA version (running under docker) chokes and dies if fed the synlink, it absolutely requires the specific device Id.
I use
SUBSYSTEM==“tty”, ATTRS{idVendor}==“0403”, ATTRS{idProduct}==“6015”, ATTRS{serial}==“DO2ZXZA1”, SYMLINK+=“ttyUSB-RFX433XL”
and this device is fed into docker (maybe no longer required) but the rfxcom integration refuses to see it (used to work with my old, april-ish 2021, HA version)
Did someone break it, or is it a Raspberry pi issue, or what? If I ask the pi about the device it finds it just fine:
udevadm info -a -n /dev/ttyUSB-RFX433XL
tells me more that I could possibly want to know, including which port the damn thing is on this week.