[Bug]: SoloCam S40 - Livestream funktioniert nur fallweise

[ofri2607]

Adapter version

1.1.2

JS-Controller version

4.0.24

Node version

18.17.1

Operating System type

Linux

Operating system version

Debian Bullseye

Describe the bug

Livestream mit start_stream gestartet liefert folgenden error im Log:

2023-09-10 13:24:29.804 - warn: eusec.0 (1296498) Tried all hosts, no connection could be established to station T8124Pxxxxxxxxxx.
2023-09-10 13:24:29.805 - info: eusec.0 (1296498) Timeout connecting to station T8124Pxxxxxxxxxx
2023-09-10 13:24:44.182 - info: eusec.0 (1296498) Connected to station T8124Pxxxxxxxxxx on host 192.xxx.xxx.xx and port 21287
2023-09-10 13:24:45.148 - error: eusec.0 (1296498) Station: T8124Pxxxxxxxxxx command CMD_DATABASE failed with error: ERROR_INVALID_COMMAND (-103)
2023-09-10 13:24:45.249 - warn: eusec.0 (1296498) Error: AES key could not be decrypted! The entire stream is discarded. [{"error":{"message":"Error: Error during decryption (probably incorrect key). Original error: Error: error:0200009F:rsa routines::pkcs decoding error","stacktrace":"Error: Error during decryption (probably incorrect key). Original error: Error: error:0200009F:rsa routines::pkcs decoding error\n at module.exports.NodeRSA.$$decryptKey (/opt/iobroker/node_modules/node-rsa/src/NodeRSA.js:301:19)\n at module.exports.NodeRSA.decrypt (/opt/iobroker/node_modules/node-rsa/src/NodeRSA.js:249:21)\n at P2PClientProtocol.handleDataBinaryAndVideo (/opt/iobroker/node_modules/eufy-security-client/build/p2p/session.js:1305:63)\n at P2PClientProtocol.handleData (/opt/iobroker/node_modules/eufy-security-client/build/p2p/session.js:1245:18)\n at P2PClientProtocol.parseDataMessage (/opt/iobroker/node_modules/eufy-security-client/build/p2p/session.js:1121:26)\n at P2PClientProtocol.handleMsg (/opt/iobroker/node_modules/eufy-security-client/build/p2p/session.js:957:26)\n at Socket. (/opt/iobroker/node_modules/eufy-security-client/build/p2p/session.js:2067:56)\n at Socket.emit (node:events:514:28)\n at Socket.emit (node:domain:489:12)\n at UDP.onMessage [as onmessage] (node:dgram:933:8)"},"stationSN":"T8124P3123192207","key":"5bdf20c0529cd367ca46ce1caf203385baac4f9c13671ca27aa26a44b51bf70aa9ecc6d7eb4c6127df4df74292007c3700f03296ddda305cbbcf0edee4c820772799e636b993bc4fe59700b26f2bd9e6a71d459e71152825148cc9adf8dcc9888cf2ef5199f6335022dcfef1a9e65e49744a6c68616ef588ee89e34ae306e6f6"}]
2023-09-10 13:25:15.316 - info: eusec.0 (1296498) Initiated closing of connection to station T8124Pxxxxxxxxxx for saving battery.
2023-09-10 13:25:15.317 - info: eusec.0 (1296498) Disconnected from station T8124Pxxxxxxxxxx

Gleich darauf nochmal mit start_stream gestartet und es hat funktioniert - Datenpunkte livestream und livestream_rtsp wurden befüllt und können im Browser angesehen werden.

2023-09-10 13:25:41.291 - info: eusec.0 (1296498) Connected to station T8124Pxxxxxxxxxx on host 188.xx.xxx.xx and port 17386
2023-09-10 13:25:42.338 - error: eusec.0 (1296498) Station: T8124P3123192207 command CMD_DATABASE failed with error: ERROR_INVALID_COMMAND (-103)
2023-09-10 13:25:42.465 - warn: eusec.0 (1296498) ffmpegStreamToGo2rtc(): Started
2023-09-10 13:26:31.066 - info: eusec.0 (1296498) Initiated closing of connection to station T8124Pxxxxxxxxxx for saving battery.
2023-09-10 13:26:31.068 - info: eusec.0 (1296498) Disconnected from station T8124Pxxxxxxxxxx

Einige Male ausprobiert, mal kommt der "Error: AES key could not be decrypted!" mal funktioniert der stream; wobei in Summe es öfter funktioniert hat, als nicht. Der error mit "command CMD_DATABASE failed with error: ERROR_INVALID_COMMAND (-103)" kommt jedes Mal und hin und wieder auch der Fehler "command CMD_DATABASE_IMAGE failed with error: ERROR_INVALID_COMMAND (-103)"

Nach einigen Abfrageintervallen kommt ERROR_CONNECT_TIMEOUT (-134) - ab da konnte kein Livestream mehr erfolgreich ausgeführt werden.

2023-09-10 14:52:19.031 - warn: eusec.0 (1296498) Tried all hosts, no connection could be established to station T8124P3123192207.
2023-09-10 14:52:19.032 - info: eusec.0 (1296498) Timeout connecting to station T8124Pxxxxxxxxxx
2023-09-10 14:52:33.334 - info: eusec.0 (1296498) Connected to station T8124Pxxxxxxxxxxon host 192.xxx.xxx.xx and port 29877
2023-09-10 14:52:33.492 - warn: eusec.0 (1296498) Command aged out from send queue for station T8124P3123192207 [{"commandType":1350,"nestedCommandType":1308,"channel":255,"ageing":635583,"maxAgeing":120000}]
2023-09-10 14:52:33.493 - error: eusec.0 (1296498) Station: T8124Pxxxxxxxxxx command CMD_DATABASE_IMAGE failed with error: ERROR_CONNECT_TIMEOUT (-134)
2023-09-10 14:52:38.335 - warn: eusec.0 (1296498) Command aged out from send queue for station T8124Pxxxxxxxxxx [{"commandType":1350,"nestedCommandType":1306,"channel":0,"ageing":634137,"maxAgeing":120000}]
2023-09-10 14:52:38.336 - error: eusec.0 (1296498) Station: T8124Pxxxxxxxxxx command CMD_DATABASE failed with error: ERROR_CONNECT_TIMEOUT (-134)
2023-09-10 14:52:43.054 - info: eusec.0 (1296498) Disconnected from station T8124Pxxxxxxxxxx

Ab da kommt dann auch nicht mehr im Log die info mit "Initiated closing of connection to station T8124Pxxxxxxxxxx for saving battery."

Nach Neustart des Adapter kommt wieder ERROR_INVALID_COMMAND (-103) bei jeder Abfrage und es ist auch der Livestream mit dem oben beschriebenen Verhalten wieder teilweise möglich.

To reproduce

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

Screenshots & Logfiles

No response

Additional context

No response