Describe the bug
Mein Internet-Anbieter fordert eine Zwangstrennung, die täglich um 03:00 Uhr stattfindet. Dabei stürzt der Adapter ab und startet neu. Ähnliche Fehlermeldungen (siehe unten) erhalte ich, wenn ich den Adapter neu starte.
Expected behavior
Da die Zwangstrennung ein "normaler" Zustand ist, sollte der Fehler entsprechend abgefangen werden, oder zumindest nicht zum Abstürzen des Adapters führen.
Screenshots & Logfiles Reconnect
host.srv-iobroker1 2024-05-14 03:00:31.981 error instance system.adapter.iot.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at TLSSocket.emit (node:events:526:35)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at TLSSocket.<anonymous> (/opt/iobroker/node_modules/mqtt/lib/client.js:360:10)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at MqttClient.emit (node:domain:489:12)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at MqttClient.emit (node:events:526:35)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at MqttClient.<anonymous> (/opt/iobroker/node_modules/aws-iot-device-sdk/device/index.js:797:12)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at DeviceClient.emit (node:domain:489:12)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at DeviceClient.emit (node:events:514:28)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at DeviceClient.onDisconnect (/opt/iobroker/node_modules/iobroker.iot/main.js:564:22)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at RemoteAccess.onCloudDisconnect (/opt/iobroker/node_modules/iobroker.iot/lib/remote.js:720:29)
host.srv-iobroker1 2024-05-14 03:00:31.981 error Caught by controller[0]: at Function.keys (<anonymous>)
host.srv-iobroker1 2024-05-14 03:00:31.980 error Caught by controller[0]: TypeError: Cannot convert undefined or null to object
iot.0 2024-05-14 03:00:31.420 error Cannot convert undefined or null to object
iot.0 2024-05-14 03:00:31.419 error TypeError: Cannot convert undefined or null to object at Function.keys (<anonymous>) at RemoteAccess.onCloudDisconnect (/opt/iobroker/node_modules/iobroker.iot/lib/remote.js:720:29) at DeviceClient.onDisconnect (/opt/iobroker/node_modules/iobroker.iot/main.js:564:22) at DeviceClient.emit (node:events:514:28) at DeviceClient.emit (node:domain:489:12) at MqttClient.<anonymous> (/opt/iobroker/node_modules/aws-iot-device-sdk/device/index.js:797:12) at MqttClient.emit (node:events:526:35) at MqttClient.emit (node:domain:489:12) at TLSSocket.<anonymous> (/opt/iobroker/node_modules/mqtt/lib/client.js:360:10) at TLSSocket.emit (node:events:526:35)
iot.0 2024-05-14 03:00:31.419 error uncaught exception: Cannot convert undefined or null to object
iot.0 2024-05-14 03:00:31.409 error Error by device connection: "read ECONNRESET"
Screenshots & Logfiles Neustart des Adapters
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at TLSSocket.emit (node:events:526:35)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at TLSSocket.<anonymous> (/opt/iobroker/node_modules/mqtt/lib/client.js:360:10)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at MqttClient.emit (node:domain:489:12)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at MqttClient.emit (node:events:526:35)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at MqttClient.<anonymous> (/opt/iobroker/node_modules/aws-iot-device-sdk/device/index.js:797:12)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at DeviceClient.emit (node:domain:489:12)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at DeviceClient.emit (node:events:514:28)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at DeviceClient.onDisconnect (/opt/iobroker/node_modules/iobroker.iot/main.js:564:22)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at RemoteAccess.onCloudDisconnect (/opt/iobroker/node_modules/iobroker.iot/lib/remote.js:720:29)
host.srv-iobroker1 2024-05-14 08:15:56.573 error Caught by controller[0]: at Function.keys (<anonymous>)
host.srv-iobroker1 2024-05-14 08:15:56.572 error Caught by controller[0]: TypeError: Cannot convert undefined or null to object
iot.0 2024-05-14 08:15:56.157 error Cannot convert undefined or null to object
iot.0 2024-05-14 08:15:56.157 error TypeError: Cannot convert undefined or null to object at Function.keys (<anonymous>) at RemoteAccess.onCloudDisconnect (/opt/iobroker/node_modules/iobroker.iot/lib/remote.js:720:29) at DeviceClient.onDisconnect (/opt/iobroker/node_modules/iobroker.iot/main.js:564:22) at DeviceClient.emit (node:events:514:28) at DeviceClient.emit (node:domain:489:12) at MqttClient.<anonymous> (/opt/iobroker/node_modules/aws-iot-device-sdk/device/index.js:797:12) at MqttClient.emit (node:events:526:35) at MqttClient.emit (node:domain:489:12) at TLSSocket.<anonymous> (/opt/iobroker/node_modules/mqtt/lib/client.js:360:10) at TLSSocket.emit (node:events:526:35)
iot.0 2024-05-14 08:15:56.155 error uncaught exception: Cannot convert undefined or null to object
Versions:
Adapter version: 3.2.2
JS-Controller version: 5.0.19
Node version: 18.17.1
Operating system: Ubuntu 22.04
Additional context
Ich nutze den Adapter ausschließlich für die Geofence-Funktion der ioBroker Visu-App. Entsprechend habe ich nur meine Zugangsdaten hinterlegt, alle Assistenten deaktiviert und weder bei "Erweiterte Einstellungen", noch bei "Services und IFTTT" Eintragungen vorgenommen, die nicht von alleine entstanden wären.
Describe the bug
Mein Internet-Anbieter fordert eine Zwangstrennung, die täglich um 03:00 Uhr stattfindet. Dabei stürzt der Adapter ab und startet neu. Ähnliche Fehlermeldungen (siehe unten) erhalte ich, wenn ich den Adapter neu starte.
Expected behavior
Da die Zwangstrennung ein "normaler" Zustand ist, sollte der Fehler entsprechend abgefangen werden, oder zumindest nicht zum Abstürzen des Adapters führen.
Screenshots & Logfiles Reconnect
Screenshots & Logfiles Neustart des Adapters
Versions:
Additional context
Ich nutze den Adapter ausschließlich für die Geofence-Funktion der ioBroker Visu-App. Entsprechend habe ich nur meine Zugangsdaten hinterlegt, alle Assistenten deaktiviert und weder bei "Erweiterte Einstellungen", noch bei "Services und IFTTT" Eintragungen vorgenommen, die nicht von alleine entstanden wären.