Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[Semmy]

Hallo

Ich habe heute ein update der node.js von 16.17.0 auf 16.17.1 gemacht. Nun funktioniert ein Adapter nicht mehr. Ist es möglich, wieder auf Version 16.17.0 einen downgrade zu machen?

Viele Grüße
Semmy

[Thomas Braun]

@semmy Schau dir den Adapter an, nicht nodejs.

sudo ln -s /usr/bin/node /usr/bin/nodejs
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

sagt?

[Semmy]

@thomas-braun Das kommt als Antwort:

pi@raspberrypi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs
pi@raspberrypi:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
aarch64
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.17.1
v16.17.1
8.15.0
4.0.23
pi
pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
/home/pi
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
nodejs:
  Installed: 16.17.1-deb-1nodesource1
  Candidate: 16.17.1-deb-1nodesource1
  Version table:
 *** 16.17.1-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u1 500
        500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages
     12.22.5~dfsg-2~11u1 500
        500 http://deb.debian.org/debian bullseye/main arm64 Packages

[Thomas Braun]

@semmy

Passt.
Und um welchen Adapter mit welchen Meldungen im LogFile geht es?

[Semmy]

@thomas-braun Es geht um den Worx-Adapter, der verbindet sich nicht mehr mit den Server. Das steht im Log:

worx.0
2022-09-25 09:13:55.999	error	ERROR: StatusCodeError: 404 - {"message":"Not Found","code":"404.000"}

worx.0
2022-09-25 09:13:55.998	error	Could not Connect to Worx Server: StatusCodeError: 404 - {"message":"Not Found","code":"404.000"}

worx.0
2022-09-25 09:13:55.647	debug	Connect to worx....

worx.0
2022-09-25 09:13:55.645	info	kress is selected

worx.0
2022-09-25 09:13:55.604	info	starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.worx, node: v16.17.1, js-controller: 4.0.23

worx.0
2022-09-25 09:13:55.062	debug	Plugin sentry Initialize Plugin (enabled=true)

worx.0
2022-09-25 09:13:54.405	debug	States connected to redis: 127.0.0.1:9000

worx.0
2022-09-25 09:13:54.124	debug	States create User PubSub Client

worx.0
2022-09-25 09:13:54.119	debug	States create System PubSub Client

worx.0
2022-09-25 09:13:53.991	debug	Redis States: Use Redis connection: 127.0.0.1:9000

worx.0
2022-09-25 09:13:53.797	debug	Objects connected to redis: 127.0.0.1:9001

worx.0
2022-09-25 09:13:53.774	debug	Objects client initialize lua scripts

worx.0
2022-09-25 09:13:53.346	debug	Objects create User PubSub Client

worx.0
2022-09-25 09:13:53.342	debug	Objects create System PubSub Client

worx.0
2022-09-25 09:13:53.335	debug	Objects client ready ... initialize now

worx.0
2022-09-25 09:13:53.115	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001

worx.0
2022-09-25 09:13:47.381	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

worx.0
2022-09-25 09:13:47.379	debug	Plugin sentry destroyed

worx.0
2022-09-25 09:13:47.377	info	terminating

worx.0
2022-09-25 09:13:47.376	info	cleaned everything up...

worx.0
2022-09-25 09:13:47.373	info	Got terminate signal TERMINATE_YOURSELF

[Thomas Braun]

@semmy

Das hat nix mit nodejs zu tun.

https://github.com/iobroker-community-adapters/ioBroker.worx/issues/569