Hitting the enter boolean in the iobroker objects => adapter crashes

[Koalabaer]

Check if the Bug maybe is with Amazon
Didn't get it to run with the alex app...

Describe the bug
Sasmung Tizen 2020 Model.

The shown buttons in the iobroker objects e.g. left and right are working...
But: Enter ist not working... if I hit enter the log looks like this:

samsung.0	2023-02-17 15:47:05.334	error	Key code not available
samsung.0	2023-02-17 15:47:05.333	error	Error: Key code not available at SamsungSmartTV._callee2$ (/opt/iobroker/node_modules/iobroker.samsung/lib/samsungtv/build/device.js:237:39) at tryCatch (/opt/iobroker/node_modules/regenerator-runtime/runtime.js:62:40) at Generator.invoke [as _invoke] (/opt/iobroker/node_modules/regenerator-runtime/runtime.js:296:22) at Generator.prototype. [as next] (/opt/iobroker/node_modules/regenerator-runtime/runtime.js:114:21) at step (/opt/iobroker/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30) at /opt/iobroker/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14 at new Promise () at new F (/opt/iobroker/node_modules/babel-runtime/node_modules/core-js/library/modules/_export.js:36:28) at SamsungSmartTV. (/opt/iobroker/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12) at SamsungSmartTV.sendKey (/opt/iobroker/node_modules/iobroker.samsung/lib/samsungtv/build/device.js:275:30) at Object.send (/opt/iobroker/node_modules/iobroker.samsung/main.js:319:68) at send (/opt/iobroker/node_modules/iobroker.samsung/main.js:188:16) at Immediate. (/opt/iobroker/node_modules/iobroker.samsung/main.js:161:29) at processImmediate (internal/timers.js:466:21)
samsung.0	2023-02-17 15:47:05.325	error	unhandled promise rejection: Key code not available
samsung.0	2023-02-17 15:47:05.324	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

To Reproduce
Steps to reproduce the behavior:

1. Go to 'the objects in iobroker'
2. Click on 'button for enter'
3. See log...

Expected behavior
I've testet it in the youtube app on the tv. If i hit the button left in iobroker, the current video-selection in youtube jumps to left - all fine. Then I hit enter and I expect that the video will start. Same in the main menu of the TV... left and right, up and down are working but if I hit enter, the adapter crashes...

Screenshots & Logfiles
see above in describe the bug section

Versions:

• Adapter version: v0.5.11
• JS-Controller version: 4.0.24
• Node version: 14.21.2
• Operating system: Linux raspberrypi 5.10.103-v71

Additional context
The Status on and off are stay the same and never change... standby button is also not working...
Token is saved into the adapter and iobroker has access to the TV because left/right and so on is working...
The TV is connected to the network via WiFi - no LAN-cable connection!
The Adapter somehow starts up the TV sometimes - i gues on reboot of iobroker...

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.
Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.