Hi,
I been getting these errors since the last HA operating system. Just wondering if anyone else has been getting them as well?
Hi,
I been getting these errors since the last HA operating system. Just wondering if anyone else has been getting them as well?
No mouse or keyboard. Only thing I got plugged in there is a JetKVM and also another usb cable going to ups for NUT. I did swap usb ports and this was a refurb desktop and it would not shock me if it is showing its age.
So I am already planning for having to swap it. All these videos I am finding want me to boot into Ubuntu and use that to leverage that to install HA. Why can’t I just pull the nvme from the desktop and burn directly to it with Balena Etcher. I seem to recall doing that way, but it was a long time ago.
Thanks.
Well a KVM is an HID (Human Interface Device), so look there.
I’m seeing the same issue. I’ve got a JetKVM hooked up to a KVM switch with 4 computers connected. Only the Home Assistant OS box is showing the errors and preventing my from typing consistently. I’ve taken a look at the “All hardware” to try to find what it’s complaining of and I cannot find the device. But given it’s affecting my typing, it’s probably the one for the KVM switch/JetKVM. Any pointers for things to search for there?
I’m running HAOS v17.2 but I saw the same on v17.1. Core 2026.4.3, if that helps.
I use my JetKVM’s separately and not with a switch, but app version is 0.5.6 and system is 0.2.7. I don’t think we are having same issue. My HA is current:
I was more concerned because my HA is running on a refurbished micro mini desktop and its on my radar to replace it. I was just hoping my hand wouldn’t be forced sooner rather than later.