Open macpo opened 2 years ago
I also notice a few Unsupported state change
errors while the Miniserver is rebooting. Here's the full log of Miniserver restarting here:
2022-02-02 16:19:04.281 - info: loxone.0 (32747) Socket closed 2008
2022-02-02 16:19:09.283 - info: loxone.0 (32747) Trying to connect
2022-02-02 16:19:11.221 - error: loxone.0 (32747) Couldn't open socket
2022-02-02 16:19:16.223 - info: loxone.0 (32747) Trying to connect
2022-02-02 16:19:16.789 - error: loxone.0 (32747) 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().
2022-02-02 16:19:16.790 - error: loxone.0 (32747) unhandled promise rejection: undefined
2022-02-02 16:19:16.791 - error: loxone.0 (32747) undefined
2022-02-02 16:19:16.956 - info: loxone.0 (32747) terminating
2022-02-02 16:19:16.959 - warn: loxone.0 (32747) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-02-02 16:19:17.293 - error: loxone.0 (32747) Couldn't open socket
2022-02-02 16:19:17.461 - warn: loxone.0 (32747) Found uncleared timeouts (report to developer): 21
2022-02-02 16:19:17.583 - error: host.pl.mh Caught by controller[0]: Miniserver out of service!
2022-02-02 16:19:17.584 - error: host.pl.mh Caught by controller[1]: 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(). The promise rejected with the reason:
2022-02-02 16:19:17.584 - error: host.pl.mh Caught by controller[2]: 2000
2022-02-02 16:19:17.584 - error: host.pl.mh instance system.adapter.loxone.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-02-02 16:19:17.585 - info: host.pl.mh Restart adapter system.adapter.loxone.0 because enabled
2022-02-02 16:19:47.640 - info: host.pl.mh instance system.adapter.loxone.0 started with pid 483
2022-02-02 16:19:50.139 - info: loxone.0 (483) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.5, js-controller: 3.3.22
2022-02-02 16:19:50.386 - info: loxone.0 (483) Trying to connect
2022-02-02 16:19:50.476 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:19:55.478 - info: loxone.0 (483) Trying to connect
2022-02-02 16:19:55.547 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:00.548 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:00.624 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:05.627 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:05.659 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:10.661 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:11.760 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:16.762 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:16.821 - error: loxone.0 (483) Unsupported state change: loxone.0.18820107-0028-5206-fffff62eeb38b63d.value
2022-02-02 16:20:16.886 - error: loxone.0 (483) Unsupported state change: loxone.0.18820129-0029-5917-fffff62eeb38b63d.value
2022-02-02 16:20:16.897 - error: loxone.0 (483) Unsupported state change: loxone.0.1882015c-0162-a203-fffff62eeb38b63d.value
2022-02-02 16:20:18.447 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:23.448 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:24.057 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:29.059 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:29.719 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:34.721 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:34.788 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:39.789 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:39.849 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:44.850 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:44.895 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:46.856 - error: loxone.0 (483) Unsupported state change: loxone.0.18820107-0028-5206-fffff62eeb38b63d.value
2022-02-02 16:20:46.859 - error: loxone.0 (483) Unsupported state change: loxone.0.18820129-0029-5917-fffff62eeb38b63d.value
2022-02-02 16:20:46.865 - error: loxone.0 (483) Unsupported state change: loxone.0.1882015c-0162-a203-fffff62eeb38b63d.value
2022-02-02 16:20:49.896 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:49.911 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:54.912 - info: loxone.0 (483) Trying to connect
2022-02-02 16:20:54.919 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:20:59.920 - info: loxone.0 (483) Trying to connect
2022-02-02 16:21:00.175 - error: loxone.0 (483) Couldn't open socket
2022-02-02 16:21:05.178 - info: loxone.0 (483) Trying to connect
2022-02-02 16:21:06.460 - info: loxone.0 (483) got structure file; last modified on 2022-02-02 16:18:57
Beschreibung
Bei der Konfigurationsaktualisierung vom Miniserver kommt es zu einer UNCAUGHT_EXCEPTION, worauf der ioBroker die loxone-Instanz neustartet.
Schritte zum Reproduzieren
Durch die Aktualisierung wird der Miniserver neu gestartet und bei den nachfolgenden Verbindungsversuchen kommt es zu einer
UNCAUGHT_EXCEPTION
.Erwartetes Verhalten
Beim Neustart vom Miniserver soll in der loxone-Instanz kein
UNCAUGHT_EXCEPTION
auftreten.Versionen