Sebastiaan Dammann
Sebastiaan Dammann
More information: Also happens on some core upgrades, `dmesg -W`: ``` [547142.559507] audit: type=1300 audit(1697121742.867:1279): arch=c000003e syscall=321 success=yes exit=15 a0=5 a1=c00018d7f8 a2=78 a3=0 items=0 ppid=1428606 pid=1428617 auid=4294967295 uid=0 gid=0 euid=0...
I *think* this seems to be resolved with latest stable. I'm investigating further.
Nope, it happened again after installing the latest 2012.12 release.
Thanks, I thought I was getting crazy. Still, after reboot of the VM I need to re-attach the virtual device.
Still happens on v11.3.
Still happens on OS v11.4. Temporary workaround: *fix-conbee.sh* ``` echo "Detaching device" sudo virsh detach-device hassos conbee-serial.xml echo "... sleeping" sleep 1 echo "Attaching device" sudo virsh attach-device hassos conbee-serial.xml...
Happened again after installing that 2024.1.4 Home Assistant Core update, without rebooting the OS/VM: ``` [ 1223.340769] usb 4-1: USB disconnect, device number 2 [ 1223.340959] ftdi_sio ttyUSB0: FTDI USB...
I don't have it while HA is running, but there are firmware updates you can try. Met vriendelijke groet, Sebastiaan Dammann ________________________________ Van: mlg9000 ***@***.***> Verzonden: Wednesday, February 7, 2024...
No, sorry, this issue still happens.
> I've been plagued by the same issue with my RFLink. This is rather not a ha but kvm issue (kvm should reattach usb devices if they reappear on the...