Caught by controller[0]: TypeError: Cannot convert undefined or null to object
vaaarg opened this issue · 8 comments
Every Night or with restart of the iot adapter i get this error. cant remember to have changed anything special and cant identify the source of this error.
iot Adapter : 3.2.2
Plattform: linux pi5
RAM: 7.8 GB
Node.js: v18.20.2
NPM: 10.5.0
JS Controller:
5.0.19
Architektur:
arm64
CPUs:
4
Geschwindigkeit:
2400 MHz
Modell:
Cortex-A76
`
Same issue here...
2024-05-04 03:29:22.566 - debug: iot.0 (24008) offline
2024-05-04 03:29:22.568 - info: iot.0 (24008) Connection changed: disconnect
2024-05-04 03:29:22.569 - debug: iot.0 (24008) [REMOTE] Cloud disconnected
2024-05-04 03:29:22.574 - error: iot.0 (24008) uncaught exception: Cannot convert undefined or null to object
2024-05-04 03:29:22.575 - error: iot.0 (24008) TypeError: Cannot convert undefined or null to object
at Function.keys ()
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:517:28)
at DeviceClient.emit (node:domain:489:12)
at MqttClient. (/opt/iobroker/node_modules/aws-iot-device-sdk/device/index.js:797:12)
at MqttClient.emit (node:events:529:35)
at MqttClient.emit (node:domain:489:12)
at TLSSocket. (/opt/iobroker/node_modules/aws-iot-device-sdk/node_modules/mqtt/lib/client.js:360:10)
at TLSSocket.emit (node:events:529:35)
2024-05-04 03:29:22.575 - error: iot.0 (24008) Cannot convert undefined or null to object
2024-05-04 03:29:22.592 - info: iot.0 (24008) terminating
2024-05-04 03:29:22.593 - debug: iot.0 (24008) Plugin sentry destroyed
2024-05-04 03:29:22.593 - warn: iot.0 (24008) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-05-04 03:29:23.095 - info: iot.0 (24008) terminating
2024-05-04 03:29:33.953 - error: host.iobroker Caught by controller[0]: TypeError: Cannot convert undefined or null to object
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at Function.keys ()
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at RemoteAccess.onCloudDisconnect (/opt/iobroker/node_modules/iobroker.iot/lib/remote.js:720:29)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at DeviceClient.onDisconnect (/opt/iobroker/node_modules/iobroker.iot/main.js:564:22)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at DeviceClient.emit (node:events:517:28)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at DeviceClient.emit (node:domain:489:12)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at MqttClient. (/opt/iobroker/node_modules/aws-iot-device-sdk/device/index.js:797:12)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at MqttClient.emit (node:events:529:35)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at MqttClient.emit (node:domain:489:12)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at TLSSocket. (/opt/iobroker/node_modules/aws-iot-device-sdk/node_modules/mqtt/lib/client.js:360:10)
2024-05-04 03:29:33.954 - error: host.iobroker Caught by controller[0]: at TLSSocket.emit (node:events:529:35)
2024-05-04 03:29:33.954 - error: host.iobroker instance system.adapter.iot.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-05-04 03:29:33.954 - info: host.iobroker Restart adapter system.adapter.iot.0 because enabled
2024-05-04 03:30:04.163 - info: host.iobroker instance system.adapter.iot.0 started with pid 24105
Plattform docker
Betriebssystem linux
Architektur x64
CPUs 4
Geschwindigkeit 2399 MHz
Modell Intel Core Processor (Skylake, IBRS)
RAM 13.54 GB
Node.js v18.20.2
NPM 10.5.0
Kann ich auch bestätigen.
Node.js 18.20.2
Npm 10.7.0
hier auch
Bei mir auch seit ein paar Tagen. Immer nur nach einem Neustart
Plattform: docker (official image - v9.1.1)
Betriebssystem: linux
Architektur: x64
CPUs: 4
Geschwindigkeit: 1501 MHz
Modell: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
RAM: 11.5 GB
System-Betriebszeit: 43 T. 17:39:52
Node.js: v18.19.0
time: 1715153126234
timeOffset: -120
NPM: 10.2.3
Adapter-Anzahl: 539
Datenträgergröße: 3572.6 GB
Freier Festplattenspeicher: 2111.0 GB
Aktive Instanzen: 29
Pfad: /opt/iobroker/
Betriebszeit: 43 T. 17:29:22
aktiv:
Please try 3.3.0
Please try 3.3.0
Heute auf Version 3.3.0 geupdated und bekomme weiterhin die Meldung:
Wenn ich die Instanz neustarte, kommt die Meldung nicht nochmal.
Vielleicht war das noch von der alten Version, als die Instanz für das Update gestoppt wurde.
Node js: 18.17.1
NPM: 9.6.7
js-controller: 5.0.19
Ich habe keine Probleme damit.
An deiner Stelle würde ich mal das System auf den aktuellen Stand bringen.
Aktuell ist:
Node.js 18.20.2
Npm 10.7.0
Ich habe keine Probleme damit. An deiner Stelle würde ich mal das System auf den aktuellen Stand bringen.
Aktuell ist:
Node.js 18.20.2 Npm 10.7.0
Habe mein System entsprechend geupdated, jetzt funktioniert es ohne Fehlermeldung.
Danke für den Hinweis!