livid dust
I have a 2.4Ghz 20 key keypad that I was using in conjunction with the Keyboard Remote integration. I'm hosting HAOS on a VM on a Synology NAS with the USB device passed through.
The keypad shows as 2 different devices, one that controls all the keys and a different one that controls the jog wheel.
When initially trying to pin down the device_name to use, I had added each and every related device_descriptor, event4 through event9.
I did a basic config for each device_descriptor just like this -
- device_descriptor: "/dev/input/event4"
type:
- 'key_up'
- 'key_down'
- 'key_hold'
This worked and I was able to see events triggering by listening to 'keyboard_remote_command_received'
this allowed me to switch the config to using a device name as below -
- device_name: "Compx 2.4G Wireless Receiver"
type:
- 'key_up'
- 'key_down'
- 'key_hold'
- device_name: "Compx 2.4G Wireless Receiver Consumer Control"
type:
- 'key_up'
- 'key_down'
- 'key_hold'
This config has worked until a recent reboot, suddenly the keypad side stopped working - "Compx 2.4G Wireless Receiver" - but the jog wheel continued to work. As I'm passing the USB to a VM, I've seen quirks in the past where any changes needed a VM reboot. I've done that, that didn't help so I took the more full on approach and rebooted the Synology (after a clean shutdown of HA).
Suddenly, neither part of the device works.
I have switched back to using a device_descriptor config and that is working again.
Sadly I just can't seem to get it working again with a device name.
My other Keyboard Remote devices that use device_name work fine, just not this one.
Maybe I'm over thinking by wanting to use device_name instead of device_descriptor.. but it was working and now it's suddenly not.
I have recently updated to the latest version of HA but I have rebooted since and the keyboard stayed alive.
Any help would be great!