NEWS
Innogy Adapter startet nicht
-
Seit dem update auf einer neueren js-controller funktioniert der Adapter nicht mehr. Die Verbindung mit Host und Lebenszeichen sind kurzzeitig vorhanden, aber dann gehen sie wieder weg. In meiner Produktiven Instanz funktioniert es noch. Wer kann helfen, die Ursache zu finden. Habe schon einige Sachen versucht, wie z.B. wieder die 0.3.6 zu installieren. -
Und das Log File sagt uns zu der ganzen Geschichte?
-
@thomas-braun
Vielen Dank für die Hinweise. Ich habe die Schritte bezgl. der Installation geprüft und aus meiner Sicht ist alles OK.
Hier ist der Auszug aus dem Protokoll. Ich hoffe Sie können etwas erkennen und mir Hinweise geben.
Vielen Dank
Benno2021-10-14 21:30:17.184 - info: host.raspberrypi "system.adapter.innogy-smarthome.0" enabled 2021-10-14 21:30:17.435 - info: host.raspberrypi instance system.adapter.innogy-smarthome.0 started with pid 18332 2021-10-14 21:30:19.547 - info: innogy-smarthome.0 (18332) starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.innogy-smarthome, node: v12.22.1, js-controller: 3.3.15 2021-10-14 21:30:22.777 - info: innogy-smarthome.0 (18332) Initialization sequence completed: found 82 devices 2021-10-14 21:30:22.800 - warn: innogy-smarthome.0 (18332) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:22.811 - warn: innogy-smarthome.0 (18332) Unknown state (please report to dev):isCapturing {"name":"isCapturing","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:22.813 - warn: innogy-smarthome.0 (18332) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:22.814 - warn: innogy-smarthome.0 (18332) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:22.815 - warn: innogy-smarthome.0 (18332) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:22.822 - warn: innogy-smarthome.0 (18332) Unknown state (please report to dev):motionDetected {"name":"motionDetected","lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:22.841 - warn: innogy-smarthome.0 (18332) Unknown state (please report to dev):motionDetected {"name":"motionDetected","value":false,"lastchanged":"2021-10-14T18:39:10.718Z"} 2021-10-14 21:30:23.061 - error: innogy-smarthome.0 (18332) 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(). 2021-10-14 21:30:23.062 - error: innogy-smarthome.0 (18332) unhandled promise rejection: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? 2021-10-14 21:30:23.065 - error: innogy-smarthome.0 (18332) Error: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2259:17) at setObjectWithDefaultValue (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1875:30) at runNextTicks (internal/process/task_queues.js:62:5) at processImmediate (internal/timers.js:434:9) 2021-10-14 21:30:23.066 - error: innogy-smarthome.0 (18332) Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? 2021-10-14 21:30:23.068 - error: innogy-smarthome.0 (18332) 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(). 2021-10-14 21:30:23.069 - error: innogy-smarthome.0 (18332) unhandled promise rejection: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value 2021-10-14 21:30:23.070 - error: innogy-smarthome.0 (18332) Error: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2259:17) at setObjectWithDefaultValue (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1875:30) at runNextTicks (internal/process/task_queues.js:62:5) at processImmediate (internal/timers.js:434:9) 2021-10-14 21:30:23.071 - error: innogy-smarthome.0 (18332) Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value 2021-10-14 21:30:23.073 - warn: innogy-smarthome.0 (18332) State "innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value" has no existing object, this might lead to an error in future versions 2021-10-14 21:30:23.081 - info: innogy-smarthome.0 (18332) State value to set for "innogy-smarthome.0.Flur-oben.Flur-oben-Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:23.104 - info: innogy-smarthome.0 (18332) State value to set for "innogy-smarthome.0.Flur-Unten.Flur-unten-SmartCam.IsCapturing" has to be type "string" but received type "boolean" 2021-10-14 21:30:23.106 - info: innogy-smarthome.0 (18332) State value to set for "innogy-smarthome.0.Schlafzimmer.Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:23.108 - info: innogy-smarthome.0 (18332) State value to set for "innogy-smarthome.0.Flur-Unten.Flur-unten-Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:23.229 - info: innogy-smarthome.0 (18332) State value to set for "innogy-smarthome.0.Wohnzimmer.Bewegungsmelder-Medion.MotionDetected" has to be type "string" but received type "boolean" 2021-10-14 21:30:23.543 - info: innogy-smarthome.0 (18332) terminating 2021-10-14 21:30:23.545 - warn: innogy-smarthome.0 (18332) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-10-14 21:30:24.320 - warn: innogy-smarthome.0 (18332) get state error: Connection is closed. 2021-10-14 21:30:24.493 - error: host.raspberrypi instance system.adapter.innogy-smarthome.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-10-14 21:30:24.494 - info: host.raspberrypi Restart adapter system.adapter.innogy-smarthome.0 because enabled 2021-10-14 21:30:25.573 - info: host.raspberrypi instance system.adapter.innogy-smarthome.0 started with pid 18383 2021-10-14 21:30:27.493 - info: innogy-smarthome.0 (18383) starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.innogy-smarthome, node: v12.22.1, js-controller: 3.3.15 2021-10-14 21:30:30.871 - info: innogy-smarthome.0 (18383) Initialization sequence completed: found 82 devices 2021-10-14 21:30:30.891 - warn: innogy-smarthome.0 (18383) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:30.905 - warn: innogy-smarthome.0 (18383) Unknown state (please report to dev):isCapturing {"name":"isCapturing","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:30.908 - warn: innogy-smarthome.0 (18383) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:30.910 - warn: innogy-smarthome.0 (18383) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:30.911 - warn: innogy-smarthome.0 (18383) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:30.921 - warn: innogy-smarthome.0 (18383) Unknown state (please report to dev):motionDetected {"name":"motionDetected","lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:30.942 - warn: innogy-smarthome.0 (18383) Unknown state (please report to dev):motionDetected {"name":"motionDetected","value":false,"lastchanged":"2021-10-14T18:39:10.718Z"} 2021-10-14 21:30:31.157 - error: innogy-smarthome.0 (18383) 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(). 2021-10-14 21:30:31.158 - error: innogy-smarthome.0 (18383) unhandled promise rejection: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? 2021-10-14 21:30:31.161 - error: innogy-smarthome.0 (18383) Error: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2259:17) at setObjectWithDefaultValue (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1875:30) at runNextTicks (internal/process/task_queues.js:62:5) at processImmediate (internal/timers.js:434:9) 2021-10-14 21:30:31.162 - error: innogy-smarthome.0 (18383) Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? 2021-10-14 21:30:31.164 - error: innogy-smarthome.0 (18383) 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(). 2021-10-14 21:30:31.165 - error: innogy-smarthome.0 (18383) unhandled promise rejection: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value 2021-10-14 21:30:31.166 - error: innogy-smarthome.0 (18383) Error: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2259:17) at setObjectWithDefaultValue (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1875:30) at runNextTicks (internal/process/task_queues.js:62:5) at processImmediate (internal/timers.js:434:9) 2021-10-14 21:30:31.167 - error: innogy-smarthome.0 (18383) Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value 2021-10-14 21:30:31.177 - warn: innogy-smarthome.0 (18383) State "innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value" has no existing object, this might lead to an error in future versions 2021-10-14 21:30:31.185 - info: innogy-smarthome.0 (18383) State value to set for "innogy-smarthome.0.Flur-oben.Flur-oben-Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:31.301 - info: innogy-smarthome.0 (18383) State value to set for "innogy-smarthome.0.Flur-Unten.Flur-unten-SmartCam.IsCapturing" has to be type "string" but received type "boolean" 2021-10-14 21:30:31.303 - info: innogy-smarthome.0 (18383) State value to set for "innogy-smarthome.0.Schlafzimmer.Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:31.305 - info: innogy-smarthome.0 (18383) State value to set for "innogy-smarthome.0.Flur-Unten.Flur-unten-Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:31.332 - info: innogy-smarthome.0 (18383) State value to set for "innogy-smarthome.0.Wohnzimmer.Bewegungsmelder-Medion.MotionDetected" has to be type "string" but received type "boolean" 2021-10-14 21:30:31.340 - info: innogy-smarthome.0 (18383) terminating 2021-10-14 21:30:31.343 - warn: innogy-smarthome.0 (18383) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-10-14 21:30:32.371 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.373 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.374 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.374 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.375 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.376 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.377 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.377 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.378 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.379 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.380 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.380 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.381 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.382 - warn: innogy-smarthome.0 (18383) get state error: Connection is closed. 2021-10-14 21:30:32.532 - error: host.raspberrypi instance system.adapter.innogy-smarthome.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-10-14 21:30:32.533 - info: host.raspberrypi Restart adapter system.adapter.innogy-smarthome.0 because enabled 2021-10-14 21:30:33.620 - info: host.raspberrypi instance system.adapter.innogy-smarthome.0 started with pid 18398 2021-10-14 21:30:35.628 - info: innogy-smarthome.0 (18398) starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.innogy-smarthome, node: v12.22.1, js-controller: 3.3.15 2021-10-14 21:30:38.909 - info: innogy-smarthome.0 (18398) Initialization sequence completed: found 82 devices 2021-10-14 21:30:38.928 - warn: innogy-smarthome.0 (18398) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:38.940 - warn: innogy-smarthome.0 (18398) Unknown state (please report to dev):isCapturing {"name":"isCapturing","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:38.943 - warn: innogy-smarthome.0 (18398) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:38.944 - warn: innogy-smarthome.0 (18398) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:38.945 - warn: innogy-smarthome.0 (18398) Unknown state (please report to dev):isSmokeAlarm {"name":"isSmokeAlarm","value":false,"lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:38.956 - warn: innogy-smarthome.0 (18398) Unknown state (please report to dev):motionDetected {"name":"motionDetected","lastchanged":"1970-01-01T00:00:00.000Z"} 2021-10-14 21:30:38.979 - warn: innogy-smarthome.0 (18398) Unknown state (please report to dev):motionDetected {"name":"motionDetected","value":false,"lastchanged":"2021-10-14T18:39:10.718Z"} 2021-10-14 21:30:39.243 - error: innogy-smarthome.0 (18398) 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(). 2021-10-14 21:30:39.244 - error: innogy-smarthome.0 (18398) unhandled promise rejection: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? 2021-10-14 21:30:39.248 - error: innogy-smarthome.0 (18398) Error: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2259:17) at setObjectWithDefaultValue (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1875:30) at runNextTicks (internal/process/task_queues.js:62:5) at processImmediate (internal/timers.js:434:9) 2021-10-14 21:30:39.249 - error: innogy-smarthome.0 (18398) Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv? 2021-10-14 21:30:39.251 - error: innogy-smarthome.0 (18398) 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(). 2021-10-14 21:30:39.252 - error: innogy-smarthome.0 (18398) unhandled promise rejection: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value 2021-10-14 21:30:39.253 - error: innogy-smarthome.0 (18398) Error: Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2259:17) at setObjectWithDefaultValue (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1875:30) at runNextTicks (internal/process/task_queues.js:62:5) at processImmediate (internal/timers.js:434:9) 2021-10-14 21:30:39.254 - error: innogy-smarthome.0 (18398) Invalid ID: innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value 2021-10-14 21:30:39.265 - warn: innogy-smarthome.0 (18398) State "innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?.Value" has no existing object, this might lead to an error in future versions 2021-10-14 21:30:39.273 - info: innogy-smarthome.0 (18398) State value to set for "innogy-smarthome.0.Flur-oben.Flur-oben-Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:39.284 - info: innogy-smarthome.0 (18398) State value to set for "innogy-smarthome.0.Flur-Unten.Flur-unten-SmartCam.IsCapturing" has to be type "string" but received type "boolean" 2021-10-14 21:30:39.287 - info: innogy-smarthome.0 (18398) State value to set for "innogy-smarthome.0.Schlafzimmer.Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:39.288 - info: innogy-smarthome.0 (18398) State value to set for "innogy-smarthome.0.Flur-Unten.Flur-unten-Rauchmelder.IsSmokeAlarm" has to be type "string" but received type "boolean" 2021-10-14 21:30:39.421 - info: innogy-smarthome.0 (18398) State value to set for "innogy-smarthome.0.Wohnzimmer.Bewegungsmelder-Medion.MotionDetected" has to be type "string" but received type "boolean" 2021-10-14 21:30:39.465 - info: innogy-smarthome.0 (18398) terminating 2021-10-14 21:30:39.468 - warn: innogy-smarthome.0 (18398) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-10-14 21:30:40.254 - warn: innogy-smarthome.0 (18398) get state error: Connection is closed. 2021-10-14 21:30:40.399 - error: host.raspberrypi instance system.adapter.innogy-smarthome.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-10-14 21:30:40.400 - info: host.raspberrypi Restart adapter system.adapter.innogy-smarthome.0 because enabled 2021-10-14 21:30:40.401 - warn: host.raspberrypi Do not restart adapter system.adapter.innogy-smarthome.0 because restart loop detected
-
innogy-smarthome.0.Virtual.Alarmanlage-Aktiv?
Ein Datenpunkt darf keine Sonderzeichen wie ? beinhalten. Nenn den gescheit.
Und halte deine nodeJS-Installation auf Stand. -
@thomas-braun
Vielen Dank für den Hinweis. Der Datenpunkt war standardmäßig im System so benannt. Umbenennung hat geholfen. Problem gelöst.BennoO
-
@bennoo sagte in Innogy Adapter startet nicht:
Der Datenpunkt war standardmäßig im System so benannt.
Dann mach ein Issue dazu auf, damit das im Adapter auch geändert werden kann, wenn das schon von daher falsch kommt.
-
@thomas-braun Mein innogy adapter startet auch nicht mehr. Es soll der Port 3000 in use sein. Stimmt auch, da dort Grafana den Port nutzt. Nur es hat ja schon mal funktioniert. Kann man den Port vom innogy Adapter umstellen oder sollte man den Grafana Port umstellen?
-
Keine Ahnung. Hab weder den einen noch den anderen Adapter im Einsatz.
-
-
@glasfaser Danke., hat geklappt. Nach Stoppen von Grafana konnte der innogy Adapter wieder initialisiert werden.