Error in Log

[skroob]

Describe the bug
Somtimes I found an error in the logs

To Reproduce
I have nothing found to reproduce.

Expected behavior
Mostly once a day I get this error message in the log. The Heos 5 is started via a blokly script with the command "play" and volume "17". This seems to be where the error occurs. But unfortunately not always. My IoBroker is shuting down at night so that a backup of the VM (Bookworm) can be created. I have recently updated to js-controller 5.12 and since then this error message. The adapter reconnected after the message then works normally until the next day.

Screenshots & Logfiles

2023-10-04 05:33:41.841 - error: heos.0 (798) 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().

2023-10-04 05:33:41.841 - error: heos.0 (798) unhandled promise rejection: undefined is not a valid state value
2023-10-04 05:33:41.842 - error: heos.0 (798) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17)
at Heos._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5439:49)
at Heos.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5400:21)
at HeosPlayer.parseResponse (/opt/iobroker/node_modules/iobroker.heos/lib/heos-player.js:1826:21)
at Heos.parseResponse (/opt/iobroker/node_modules/iobroker.heos/main.js:1814:17)
at Heos.onData (/opt/iobroker/node_modules/iobroker.heos/main.js:749:14)
at Socket. (/opt/iobroker/node_modules/iobroker.heos/main.js:2442:45)
at Socket.emit (node:events:517:28)
at addChunk (node:internal/streams/readable:335:12)
at readableAddChunk (node:internal/streams/readable:308:9)
at Readable.push (node:internal/streams/readable:245:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
2023-10-04 05:33:41.843 - error: heos.0 (798) undefined is not a valid state value
2023-10-04 05:33:41.843 - info: heos.0 (798) disconnecting from HEOS ...
2023-10-04 05:33:41.844 - info: heos.0 (798) [Buero - Heos 5] disconnect HEOS player Buero - Heos 5 (141082291)
2023-10-04 05:33:41.981 - info: heos.0 (798) [Denon AVR-X4400H] disconnect HEOS player Denon AVR-X4400H (347439546)
2023-10-04 05:33:42.121 - info: heos.0 (798) [Kueche - Heos 5] disconnect HEOS player Kueche - Heos 5 (1570209935)
2023-10-04 05:33:42.214 - info: heos.0 (798) [Garage - Heos 1] disconnect HEOS player Garage - Heos 1 (-175607758)
2023-10-04 05:33:42.305 - info: heos.0 (798) [Dachboden - Heos 1] disconnect HEOS player Dachboden - Heos 1 (-1801497287)
2023-10-04 05:33:42.343 - info: heos.0 (798) terminating
2023-10-04 05:33:42.343 - warn: heos.0 (798) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-04 05:33:42.489 - info: heos.0 (798) disconnected from HEOS
2023-10-04 05:33:42.859 - error: host.ioBroker-MA instance system.adapter.heos.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-04 05:33:42.859 - info: host.ioBroker-MA Restart adapter system.adapter.heos.0 because enabled

Versions:

• Adapter version: 2.1.0
• JS-Controller version: 5.12
• Node version: 9.8.1 / 18.18.0
• Operating system: Proxmox VM debian (bookworm)

[withstu]

The error appears in the following lines. So it seams that the HEOS player is answering with unexpected data. It says that the type of the media is "station", however the payload does not contain the station name. What kind of media source are you using? Is it just TuneIn radio? Maybe I need to add an extra check, if the station is defined, however I want to understand the root cause first and maybe track the logs on my side.
https://github.com/withstu/ioBroker.heos/blob/6550d821961ad68e4ac1da507f5447e6d90ea7b1/lib/heos-player.js#L1825C10-L1827C11

[skroob]

Yes your are right, it is a radio station named "Radio Zürisee 107.4 (Adult Hits)". In my heos app is the station saved in preset 1. I start playing with a vis button and set the state point to "play". Thank yo for your support.

[skroob]

Hi withstu,

Thank you for adding the check. It working now for 2 months without any problems.
A few days ago I updated to the latest npm / nodejs (NPM: 10.2.3 / Node.js:20.10.0). And now has the adapter a problem with my AVR. One warning spams my log (see picture).

Only the switching off the AVR does not function any others executed normally. And the warning that spams the log.

Settings:

Thank you for your support and I wish you a happy new year!

[withstu]

Happy new year. I've just released a new version, which is reducing the upnp requests to the devices. Can you give it a try?

[skroob]

Hello withstu,

Thanks for the support. I have tried, but the adapter still has the same problem.

Then I roll back to the v18.19.0 and everyting is fine.

For your info, I have also the Denon-Adapter installed. He has no problem with both versions. Give me a short feedback, when I can do somthing.

Thanks and have a nice day!

[skroob]

I forgot, only the AVR has this problem, the other HEOS devices function without problem.

[withstu]

This is a known bug in node 19+. By now it has not been fixed in all dependencies e.g. axios. I've just added a workaround to the code.

• "socket hang up" / ECONNRESET on consecutive requests with Node.js 19 and Node.js 20 node-fetch/node-fetch#1735
• Axios - follow NodeJS 20.x issue and restore keepalive  mborne/markdown-to-html#39

[skroob]

Hi withstu,
Thank's for fixing this. After few days testing, I don't have any errors and everything working fine.

have a nice day