NEWS

Ghostrider

Hallo zusammen,

ich bin mir nicht ganz sicher ob ich hier im richtigen Bereich bin aber ich versuche einfach mal mein Glück.
Ich versuche aktuell mein IoBroker direkt mit der Roon API zu verbinden (läuft über einen Websocket). Dafür gibt es von Roon auch einige NodeJs module, welche ich auch installieren konnte. Nun habe ich aber das Problem, dass ich bei diesem Beispielscript keine funktionierende Verbindung zum Server hinbekomme:

javascript.0
	2023-10-07 19:29:09.588	error	at Receiver.receiverOnMessage (/opt/iobroker/node_modules/ws/lib/websocket.js:789:20)
javascript.0
	2023-10-07 19:29:09.588	error	at WebSocket.emit (node:events:513:28)
javascript.0
	2023-10-07 19:29:09.588	error	at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/event-target.js:120:16)
javascript.0
	2023-10-07 19:29:09.588	error	at WebSocket.Transport.ws.onmessage (/opt/iobroker/node_modules/node-roon-api/transport-websocket.js:50:14)
javascript.0
	2023-10-07 19:29:09.588	error	at Transport.moo.transport.onmessage (/opt/iobroker/node_modules/node-roon-api/lib.js:444:22)
javascript.0
	2023-10-07 19:29:09.588	error	at Moo.handle_response (/opt/iobroker/node_modules/node-roon-api/moo.js:199:21)
javascript.0
	2023-10-07 19:29:09.588	error	at Object.cb (/opt/iobroker/node_modules/node-roon-api/lib.js:410:37)
javascript.0
	2023-10-07 19:29:09.588	error	at RoonApi.ev_registered (/opt/iobroker/node_modules/node-roon-api/lib.js:484:61)
javascript.0
	2023-10-07 19:29:09.588	error	at Object.found_core (/opt/iobroker/node_modules/node-roon-api/lib.js:291:64)
javascript.0
	2023-10-07 19:29:09.588	error	at Object.core_paired (script.js.sonstiges.Roon.RoonAdapterTest:18:19)
javascript.0
	2023-10-07 19:29:09.588	error	script.js.sonstiges.Roon.RoonAdapterTest: TypeError: Cannot read properties of undefined (reading 'subscribe_zones')

und diesen hier:

javascript.0
	2023-10-07 19:29:19.581	error	Error: WebSocket is not open: readyState 2 (CLOSING) at WebSocket.ping (/opt/iobroker/node_modules/ws/lib/websocket.js:264:19) at Timeout._onTimeout (/opt/iobroker/node_modules/node-roon-api/transport-websocket.js:26:21) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)
javascript.0
	2023-10-07 19:29:19.580	error	Error: WebSocket is not open: readyState 2 (CLOSING)
javascript.0
	2023-10-07 19:29:19.580	error	An error happened which is most likely from one of your scripts, but the originating script could not be detected.

Ich habe testweise exakt das gleiche Script mal lokal bei mir auf dem Rechner ausgeführt, da funktioniert alles genau so wie es soll und ich bekomme die korrekten Daten. Also die aktuellen Infos vom Server als Json Objekt.
Mene Vermutung ist deshalb, dass der Fehler irgendwie mit IoBroker zusammenhängt? IoBroker nutzt ja auch Websockets. Kann es sein, dass diese sich gegenseitig irgendwie behindern?

Vlt. hat ja jemand eine Idee, woran das liegen könnte oder was ich noch ausprobieren könnte.

Vielen Dank und viele Grüße

Ghostrider

ok, hat sich erledigt, das ganze war meine Schuld. Ich hatte auf der alten Instanz SSL mit einem extra Docker Volume für die Zertifikate eingerichtet. Das Volume habe ich zwar auch beim neuen Container gemappt, allerdings vergessen die Zertifikatsdateien hinzuzufügen. Danach und einem Neustart des Containers ist der Adapter auch problemlos gestartet.

Ghostrider

@glasfaser
Hier der Log des Docker Containers, seit 1. Start bis zum Ende (1 Neustart)

 
--------------------------------------------------------------------------------
-------------------------     2023-08-09 14:20:52      -------------------------
--------------------------------------------------------------------------------
-----                                                                      -----
----- ██╗  ██████╗  ██████╗  ██████╗   ██████╗  ██╗  ██╗ ███████╗ ██████╗  -----
----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ -----
----- ██║ ██║   ██║ ██████╔╝ ██████╔╝ ██║   ██║ █████╔╝  █████╗   ██████╔╝ -----
----- ██║ ██║   ██║ ██╔══██╗ ██╔══██╗ ██║   ██║ ██╔═██╗  ██╔══╝   ██╔══██╗ -----
----- ██║ ╚██████╔╝ ██████╔╝ ██║  ██║ ╚██████╔╝ ██║  ██╗ ███████╗ ██║  ██║ -----
----- ╚═╝  ╚═════╝  ╚═════╝  ╚═╝  ╚═╝  ╚═════╝  ╚═╝  ╚═╝ ╚══════╝ ╚═╝  ╚═╝ -----
-----                                                                      -----
-----              Welcome to your ioBroker Docker container!              -----
-----                    Startupscript is now running!                     -----
-----                          Please be patient!                          -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                          System Information                          -----
-----                    arch:                x86_64                       -----
-----                    hostname:            iobroker                     -----
-----                                                                      -----
-----                          Version Information                         -----
-----                    image:               v8.0.1                       -----
-----                    build:               2023-07-19T23:45:22+00:00    -----
-----                    node:                v18.17.0                     -----
-----                    npm:                 9.6.7                        -----
-----                                                                      -----
-----                        Environment Variables                         -----
-----                    SETGID:              1000                         -----
-----                    SETUID:              1000                         -----
-----                    USBDEVICES:          /dev/ttyUSB0                 -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                   Step 1 of 5: Preparing container                   -----
--------------------------------------------------------------------------------
 
Updating Linux packages on first run... Done.
 
Registering maintenance script as command... Done.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
IoBroker backup file detected in /opt/iobroker.
Since Docker Image v8, automatic initial restore is no longer supported!
IoBroker will start with a fresh installation, while your backup file will be copied into the backup directory.
You will be able to restore your backup file manually by using the backitup adapter or the containers maintenance script.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).
 
Copying backup file and restoring initial ioBroker installation... Done.
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)setting permissions (This might take a while! Please be patient!)... Done.
 
Fixing "sudo-bug" by replacing sudo with gosu... Done.
 
Initializing a fresh installation of ioBroker... Done.
 
Hostname in ioBroker does not match the hostname of this container.
Updating hostname to "iobroker"... The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "iobroker".
The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "iobroker".
The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "iobroker".
Done.
 
--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------
 
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).
 
USBDEVICES is set.
Setting permissions for "/dev/ttyUSB0"... Done.
 
 
--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------
 
Starting ioBroker... 
 
##### #### ### ## # iobroker.js-controller log output # ## ### #### #####
host.iobroker check instance "system.adapter.admin.0" for host "iobroker"
host.iobroker check instance "system.adapter.discovery.0" for host "iobroker"
host.iobroker check instance "system.adapter.backitup.0" for host "iobroker"
================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]
Send diag info: {"uuid":"XXX","language":"de","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.17.0","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.23","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"Common KVM processor","cpus":4,"mem":8323035136,"ostype":"Linux","city":""}
================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]
Terminated
 
Recived termination signal (SIGTERM).
Shutting down ioBroker... 
 
--------------------------------------------------------------------------------
-------------------------     2023-08-09 14:25:47      -------------------------
--------------------------------------------------------------------------------
-----                                                                      -----
----- ██╗  ██████╗  ██████╗  ██████╗   ██████╗  ██╗  ██╗ ███████╗ ██████╗  -----
----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ -----
----- ██║ ██║   ██║ ██████╔╝ ██████╔╝ ██║   ██║ █████╔╝  █████╗   ██████╔╝ -----
----- ██║ ██║   ██║ ██╔══██╗ ██╔══██╗ ██║   ██║ ██╔═██╗  ██╔══╝   ██╔══██╗ -----
----- ██║ ╚██████╔╝ ██████╔╝ ██║  ██║ ╚██████╔╝ ██║  ██╗ ███████╗ ██║  ██║ -----
----- ╚═╝  ╚═════╝  ╚═════╝  ╚═╝  ╚═╝  ╚═════╝  ╚═╝  ╚═╝ ╚══════╝ ╚═╝  ╚═╝ -----
-----                                                                      -----
-----              Welcome to your ioBroker Docker container!              -----
-----                    Startupscript is now running!                     -----
-----                          Please be patient!                          -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                          System Information                          -----
-----                    arch:                x86_64                       -----
-----                    hostname:            iobroker                     -----
-----                                                                      -----
-----                          Version Information                         -----
-----                    image:               v8.0.1                       -----
-----                    build:               2023-07-19T23:45:22+00:00    -----
-----                    node:                v18.17.0                     -----
-----                    npm:                 9.6.7                        -----
-----                                                                      -----
-----                        Environment Variables                         -----
-----                    SETGID:              1000                         -----
-----                    SETUID:              1000                         -----
-----                    USBDEVICES:          /dev/ttyUSB0                 -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                   Step 1 of 5: Preparing container                   -----
--------------------------------------------------------------------------------
 
This is not the first run of this container. Skipping first run preparation.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
Existing installation of ioBroker detected in "/opt/iobroker".
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)setting permissions (This might take a while! Please be patient!)... Done.
 
Fixing "sudo-bug" by replacing sudo with gosu... Done.
 
Checking Database connection... Done.
 
Hostname in ioBroker matches the hostname of this container.
No action required.
 
--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------
 
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).
 
USBDEVICES is set.
Setting permissions for "/dev/ttyUSB0"... Done.
 
 
--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------
 
Starting ioBroker... 
 
##### #### ### ## # iobroker.js-controller log output # ## ### #### #####
================================== > LOG REDIRECT system.adapter.admin.0 => true [starting]
host.iobroker check instance "system.adapter.admin.0" for host "iobroker"
host.iobroker check instance "system.adapter.influxdb.0" for host "iobroker"
host.iobroker check instance "system.adapter.javascript.0" for host "iobroker"
host.iobroker check instance "system.adapter.telegram.0" for host "iobroker"
host.iobroker check instance "system.adapter.mqtt.0" for host "iobroker"
host.iobroker check instance "system.adapter.ping.0" for host "iobroker"
host.iobroker check instance "system.adapter.samsung.0" for host "iobroker"
host.iobroker check instance "system.adapter.sonoff.0" for host "iobroker"
host.iobroker check instance "system.adapter.spotify-premium.0" for host "iobroker"
host.iobroker check instance "system.adapter.unifi.0" for host "iobroker"
host.iobroker check instance "system.adapter.zigbee.0" for host "iobroker"
host.iobroker check instance "system.adapter.discovery.0" for host "iobroker"
host.iobroker check instance "system.adapter.backitup.0" for host "iobroker"
host.iobroker check instance "system.adapter.anelhut.0" for host "iobroker"
host.iobroker check instance "system.adapter.birthdays.0" for host "iobroker"
host.iobroker check instance "system.adapter.birthdays.1" for host "iobroker"
host.iobroker check instance "system.adapter.device-reminder.0" for host "iobroker"
host.iobroker check instance "system.adapter.discord.0" for host "iobroker"
host.iobroker check instance "system.adapter.linux-control.0" for host "iobroker"
host.iobroker check instance "system.adapter.net-tools.0" for host "iobroker"
host.iobroker check instance "system.adapter.parser.0" for host "iobroker"
host.iobroker check instance "system.adapter.pi-hole.0" for host "iobroker"
host.iobroker check instance "system.adapter.proxmox.0" for host "iobroker"
host.iobroker check instance "system.adapter.simple-api.0" for host "iobroker"
host.iobroker check instance "system.adapter.vis.0" for host "iobroker"
host.iobroker check instance "system.adapter.web.0" for host "iobroker"
Send diag info: {"uuid":"XXX","language":"","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.17.0","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.23","platform":"Javascript/Node.js"},"anelhut":{"version":"1.0.13","platform":"Javascript/Node.js"},"birthdays":{"version":"2.2.0","platform":"Javascript/Node.js"},"device-reminder":{"version":"1.2.9","platform":"Javascript/Node.js"},"discord":{"version":"1.1.6","platform":"Javascript/Node.js"},"influxdb":{"version":"3.2.0","platform":"Javascript/Node.js"},"javascript":{"version":"7.0.3","platform":"Javascript/Node.js"},"linux-control":{"version":"1.1.3","platform":"Javascript/Node.js"},"mqtt":{"version":"4.1.1","platform":"Javascript/Node.js"},"net-tools":{"version":"0.2.0","platform":"Javascript/Node.js"},"parser":{"version":"1.3.2","platform":"Javascript/Node.js"},"pi-hole":{"version":"1.3.6","platform":"Javascript/Node.js"},"ping":{"version":"1.5.3","platform":"Javascript/Node.js"},"proxmox":{"version":"1.3.5","platform":"Javascript/Node.js"},"samsung":{"version":"0.5.11","platform":"Javascript/Node.js"},"simple-api":{"version":"2.7.2","platform":"Javascript/Node.js"},"socketio":{"version":"4.2.0","platform":"Javascript/Node.js"},"sonoff":{"version":"2.5.3","platform":"Javascript/Node.js"},"spotify-premium":{"version":"1.2.2","platform":"Javascript/Node.js"},"telegram":{"version":"1.16.0","platform":"Javascript/Node.js"},"unifi":{"version":"0.6.6","platform":"Javascript/Node.js"},"vis":{"version":"1.4.16","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"zigbee":{"version":"1.8.21","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":26,"compactMode":false,"noCompactInstances":0,"model":"Common KVM processor","cpus":4,"mem":8323035136,"ostype":"Linux","city":"","vis":0}
================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]

Oder meintest du diesen Log von IoBroker selbst?

2023-08-09 14:31:15.151  - info: host.iobroker iobroker npm-install: host.iobroker object system.adapter.web created/updated
2023-08-09 14:31:16.185  - info: host.iobroker iobroker npm-install: exit 0
2023-08-09 14:31:17.186  - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 2 attempt
2023-08-09 14:31:17.188  - info: host.iobroker iobroker install vis@1.4.16 using installedFrom
2023-08-09 14:31:20.716  - info: host.iobroker iobroker npm-install: NPM version: 9.6.7Installing iobroker.vis@1.4.16... (System call)
2023-08-09 14:31:28.062  - info: vis.0 (1509) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24
2023-08-09 14:31:28.379  - info: vis.0 (1509) vis license is OK.
2023-08-09 14:31:28.426  - error: vis.0 (1509) 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().
2023-08-09 14:31:28.428  - error: vis.0 (1509) unhandled promise rejection: Not exists
2023-08-09 14:31:28.435  - error: vis.0 (1509) Error: Not exists
    at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17)
    at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26)
    at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29)
    at process.processImmediate (node:internal/timers:478:21)
2023-08-09 14:31:28.437  - error: vis.0 (1509) Not exists
2023-08-09 14:31:28.945  - info: vis.0 (1509) terminating
2023-08-09 14:31:28.945  - warn: vis.0 (1509) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-08-09 14:31:29.574  - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6
2023-08-09 14:31:30.616  - info: host.iobroker iobroker npm-install: exit 25
2023-08-09 14:31:31.617  - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 3 attempt
2023-08-09 14:31:31.617  - info: host.iobroker iobroker install vis@1.4.16 using installedVersion
2023-08-09 14:31:33.772  - info: host.iobroker iobroker npm-install: NPM version: 9.6.7
2023-08-09 14:31:33.773  - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call)
2023-08-09 14:31:41.407  - info: vis.0 (1567) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24
2023-08-09 14:31:41.546  - info: vis.0 (1567) vis license is OK.
2023-08-09 14:31:41.574  - error: vis.0 (1567) 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().
2023-08-09 14:31:41.575  - error: vis.0 (1567) unhandled promise rejection: Not exists
2023-08-09 14:31:41.576  - error: vis.0 (1567) Error: Not exists
    at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17)
    at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26)
    at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29)
    at process.processImmediate (node:internal/timers:478:21)
2023-08-09 14:31:41.577  - error: vis.0 (1567) Not exists
2023-08-09 14:31:42.082  - info: vis.0 (1567) terminating
2023-08-09 14:31:42.085  - warn: vis.0 (1567) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-08-09 14:31:42.778  - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6
2023-08-09 14:31:43.818  - info: host.iobroker iobroker npm-install: exit 25
2023-08-09 14:31:44.820  - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 4 attempt
2023-08-09 14:31:44.821  - info: host.iobroker iobroker install vis@1.4.16 using installedVersion
2023-08-09 14:31:47.179  - info: host.iobroker iobroker npm-install: NPM version: 9.6.7
2023-08-09 14:31:47.182  - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call)
2023-08-09 14:31:55.581  - info: vis.0 (1627) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24
2023-08-09 14:31:55.914  - info: vis.0 (1627) vis license is OK.
2023-08-09 14:31:55.943  - error: vis.0 (1627) 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().
2023-08-09 14:31:55.944  - error: vis.0 (1627) unhandled promise rejection: Not exists
2023-08-09 14:31:55.946  - error: vis.0 (1627) Error: Not exists
    at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17)
    at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26)
    at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29)
    at process.processImmediate (node:internal/timers:478:21)
2023-08-09 14:31:55.946  - error: vis.0 (1627) Not exists
2023-08-09 14:31:56.449  - info: vis.0 (1627) terminating
2023-08-09 14:31:56.450  - warn: vis.0 (1627) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-08-09 14:31:57.040  - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6
2023-08-09 14:31:58.057  - info: host.iobroker iobroker npm-install: exit 25
2023-08-09 14:31:59.058  - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log!
2023-08-09 14:39:30.382  - error: admin.0 (2200) admin.0 invalid process id scenario 170 vs. own ID 2200. Stopping
2023-08-09 14:39:30.389  - info: admin.0 (2200) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-08-09 14:43:35.437  - info: vis.0 (2422) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24
2023-08-09 14:43:35.796  - info: vis.0 (2422) vis license is OK.
2023-08-09 14:43:35.829  - error: vis.0 (2422) 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().
2023-08-09 14:43:35.829  - error: vis.0 (2422) unhandled promise rejection: Not exists
2023-08-09 14:43:35.831  - error: vis.0 (2422) Error: Not exists
    at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17)
    at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26)
    at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29)
    at process.processImmediate (node:internal/timers:478:21)
2023-08-09 14:43:35.831  - error: vis.0 (2422) Not exists
2023-08-09 14:43:36.334  - info: vis.0 (2422) terminating
2023-08-09 14:43:36.335  - warn: vis.0 (2422) Terminated (UNCAUGHT_EXCEPTION): Without reason

Das ist ein Teil den ich noch über iob logs erhalte. Brauchst du mehr, dann könnte ich noch den kompletten Log als Datei anhängen.

Ghostrider

Hallo zusammen,
ich habe vorhin ein Backup meiner IoB Instanz über den BackItUp Adapter gemacht und jetzt versucht den bei der neuen Instanz zu restoren (ist in beiden fällen ein Docker Container - nur neuer Host). Der restore an sich wird auch erfolgreich durchgeführt, als letzte Nachricht steht da, dass neu gestartet wird. Wenn ich jetzt in den Log des COntainers schaue kommt folgende Fehlermeldung:

================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]

Über den Befehl iob logs konnte ich sehen, dass noch die npm Module installiert werden. Dies habe ich abgewartet. Hierbei tritt der Fehler auf, dass er den vis Adapter nicht installieren kann, aber das ist vermutlich noch ein anderes Problem:

2023-08-09 13:30:55.758  - error: vis.0 (1387) 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().
2023-08-09 13:30:55.759  - error: vis.0 (1387) unhandled promise rejection: Not exists
2023-08-09 13:30:55.760  - error: vis.0 (1387) Error: Not exists
    at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17)
    at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26)
    at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29)
    at process.processImmediate (node:internal/timers:478:21)
2023-08-09 13:30:55.761  - error: vis.0 (1387) Not exists
2023-08-09 13:30:56.267  - info: vis.0 (1387) terminating
2023-08-09 13:30:56.270  - warn: vis.0 (1387) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-08-09 13:30:57.140  - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6
2023-08-09 13:31:58.057  - info: host.iobroker iobroker npm-install: exit 25
2023-08-09 13:31:59.058  - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log!

Danach passiert nichts mehr (habe noch ca. ne Stunde gewartet) und hab dann den Container nochmal neu gestartet.
Der admin Adapter ist jedoch nicht gestartet und lässt sich auch nicht starten. Mit iob start admin wirft er zwar keine Fehlermeldung, aber er startet den Adapter auch nicht.
Wenn ich versuche ihn mit folgenden Command zu starten node node_modules/iobroker.admin/main.js --logs erhalte ich nur einen Fehler:

2023-08-09 14:39:30.382  - error: admin.0 (2200) admin.0 invalid process id scenario 170 vs. own ID 2200. Stopping
2023-08-09 14:39:30.389  - info: admin.0 (2200) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

Kann mir hier jemand helfen oder hat noch ne Idee was ich falsch gemacht haben könnte?

Viele Grüße
Henrik

Ghostrider

Hallo Zusammen,

gibt es bei dem Adapter die Möglichkeit bei den Alarmkreisen auf Iobroker Enums zurückzugreifen? Habe zu Testzwecken als Objekt ID einfach mal eine Enum ID eingetragen. Das hat leider nicht funktioniert. Muss man das irgendwie anders machen oder unterstützt der Adapter Enums aktuell noch nicht?

Ghostrider

Super, vielen Dank für deine schnelle Antwort.
Ja, scheint bei Z-Wave wirklich so zu sein. Zumindest steht bei meinen geschalteten Aktoren, die nicht erreichbar sind, das Flag auf False.

Gibt es denn auch ne Möglichkeit dieses Flag im Vis bei einem Switch auszuwählen, sodass sich das Icon erst ändert, wenn das ACK-Flag auf True steht? Also dass ich schon am Icon sehe, ob er auch wirklich geschaltet hat?

Ghostrider

Hallo Zusammen,

ich habe auf meinem IOBroker den ZWave Adapter installiert und konfiguriert. Ich kann auch problemlos die Geräte einbinden und die Schalter lassen sich auch schalten. Nun ist mir aber bei der Einrichtung der Vis aufgefallen, dass ich den PowerState bei z.B. einem Binary Switch ändern kann aber IOBroker (oder der Adapter) nicht überprüft, ob das Gerät überhaupt erreichbar ist und geschaltet wurde. Ich konnte Geräte schalten, die dann als On(true) angezeigt wurden, aber gar nicht in einer Steckdose steckten.

Ich habe bereits im Forum einen ähnlichen Artikel gefunden, bei dem es um das selbe Problem ging (https://www.forum.iobroker.net/topic/10028/anfängerfrage-schalten-obwohl-gerät-nicht-verfügbar-ist) Allerdings ging es da nur um das anzeigen / ausgrauen im VIS, wenn das Gerät nicht verfügbar ist.

Wenn ich nun aber den State eines ZWave Gerätes ändern kann und er steht dann im System mit dem neuen Wert, ohne das ich sicher gehen kann, dass er wirklich geschaltet hat ist doch der ganze Sinn von ZWave hinfällig. Der Vorteil gegenüber eines billigen 433MHZ Aktors ist ja unteranderem, dass es einen Rückkanal gibt und die Geräte einen Schaltvorgang bestätigen, oder verstehe ich hier etwas falsch?

Oder gibt es irgendeine Möglichkeit zu sagen, dass er den Rückkanal beachtet und er den State bei IOBroker nur ändert, wenn der Schalter auch wirklich geschaltet hat?

Ich hoffe mir kann dazu jemand genauere Infos geben.

Viele Grüße

NEWS

Ghostrider

@Ghostrider

Latest posts made by Ghostrider