External Keyboard does not trigger event.

[froidl]

The problem

Using it on an Pi 400 with HASOS Doesent matter, if i put the integrated Keyboard into the config or not, Its triggering events. But it is not workjing with an externel USB Keyboard. Tryed multiple. Everytime i tryed the config with device_descriptor: by id and with Event. Loaded YAML after every change. nothing works. After Installing "apk add linux-headers xf86-input-evdev gcc python3-dev musl-dev libc-dev" via Terminal, the internal Keyboard doenst work also. After Deinstalling it, the Internal Keyboard works again.

What version of Home Assistant Core has the issue?

core-2024.1.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Keyboard Remote

Link to integration documentation on our website

https://www.home-assistant.io/integrations/keyboard_remote/

Diagnostics information

Example YAML snippet

keyboard_remote:
- device_descriptor: '/dev/input/by-id/usb-0c45_USB_Keyboard-event-kbd'
  type: "key_down"
  emulate_key_hold: true
  emulate_key_hold_delay: 0.25
  emulate_key_hold_repeat: 0.033
- device_descriptor: '/dev/input/by-id/usb-_Raspberry_Pi_Internal_Keyboard-event-kbd'
  type: "key_down"

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @bendavid, @lanrat, mind taking a look at this issue as it has been labeled with an integration (keyboard_remote) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `keyboard_remote` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign keyboard_remote` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

keyboard_remote documentation keyboard_remote source _{^{(message by IssueLinks)}}

[froidl]

Read very much Threads about this Problem. But no one has an answer

[lanrat]

@froidl have you tried using the evtest command with this keyboard to verify the paths and events that your device emits match your expected values?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.