Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[Beowolf]

Hallo zusammen,

ich habe vier ( 0 - 3 ) Saugroboter 1S. Also die erste Generation.

Drei Instanzen sind grün. Die vierte bleibt gelb mit dieser Meldung.

mihome-vacuum.3
	2025-12-28 19:46:39.314	error	could not find model, please try again later or set manually in config
mihome-vacuum.3
	2025-12-28 19:46:39.312	error	YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
mihome-vacuum.3
	2025-12-28 19:46:31.298	info	IOT disabled, delete state
mihome-vacuum.3
	2025-12-28 19:46:31.272	info	starting. Version 5.3.0 (non-npm: iobroker-community-adapters/ioBroker.mihome-vacuum) in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v20.19.6, js-controller: 7.0.7
host.raspberrypi
	2025-12-28 19:46:30.327	info	instance system.adapter.mihome-vacuum.3 in version "5.3.0" (non-npm: iobroker-community-adapters/ioBroker.mihome-vacuum) started with pid 911225
host.raspberrypi
	2025-12-28 19:46:27.102	info	instance system.adapter.mihome-vacuum.3 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
mihome-vacuum.3
	2025-12-28 19:46:26.662	info	terminating
host.raspberrypi
	2025-12-28 19:46:26.254	info	stopInstance system.adapter.mihome-vacuum.3 send kill signal
mihome-vacuum.3
	2025-12-28 19:46:26.163	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
mihome-vacuum.3
	2025-12-28 19:46:26.163	info	terminating
mihome-vacuum.3
	2025-12-28 19:46:26.162	error	Socket Close
mihome-vacuum.3
	2025-12-28 19:46:26.161	info	Got terminate signal TERMINATE_YOURSELF

Jeder hat natülich seinen eigenen Port und IP-Adresse.

Alle anderen Einstellungen sind gleich.

Über die Xiaomi Home App kann ich alle Sauger ansteuern.

Wo liegt wohl der Fehler?

[Thomas Braun]

@Beowolf sagte in mihome xiaomi Staubsauger 1s - wird nich grün:

node: v20.19.6

nodejs@22 installieren. Und dann das Log BITTE NICHT aus dem Admin kopieren sondern aus

iob logs

Und eine Repo-gestützte Version verwenden, nix aus dem GitHub geklaubtes.

[Beowolf]

Ich würde ja gerne auf 22.21.1 updaten. Aber immer wenn ich auf der Übersichtsseite in der letzen Kachel "raspberry" auf den kleinen "kringelpfeil" klicke, kommt zwar der Hinweis Node.js-Upgrade, aber nach dem Upgrade steht dort immer noch 20.19.6.

[Beowolf]

 iob logs
2025-12-28 20:21:14.844  - info: host.raspberrypi stopInstance system.adapter.mihome-vacuum.3 (force=false, process=true)
2025-12-28 20:21:14.849  - info: mihome-vacuum.3 (915730) Got terminate signal TERMINATE_YOURSELF
2025-12-28 20:21:14.851  - error: mihome-vacuum.3 (915730) Socket Close
2025-12-28 20:21:14.851  - info: mihome-vacuum.3 (915730) terminating
2025-12-28 20:21:14.852  - info: mihome-vacuum.3 (915730) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2025-12-28 20:21:14.961  - info: host.raspberrypi stopInstance system.adapter.mihome-vacuum.3 send kill signal
2025-12-28 20:21:15.351  - info: mihome-vacuum.3 (915730) terminating
2025-12-28 20:21:15.869  - info: host.raspberrypi instance system.adapter.mihome-vacuum.3 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-12-28 20:21:19.008  - info: host.raspberrypi instance system.adapter.mihome-vacuum.3 in version "5.3.0" (non-npm: iobroker-community-adapters/ioBroker.mihome-vacuum) started with pid 916425
2025-12-28 20:21:19.939  - info: mihome-vacuum.3 (916425) starting. Version 5.3.0 (non-npm: iobroker-community-adapters/ioBroker.mihome-vacuum) in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v20.19.6, js-controller: 7.0.7
2025-12-28 20:21:19.965  - info: mihome-vacuum.3 (916425) IOT disabled, delete state
2025-12-28 20:21:27.978  - error: mihome-vacuum.3 (916425) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
2025-12-28 20:21:27.981  - error: mihome-vacuum.3 (916425) could not find model, please try again later or set manually in config

[Thomas Braun]

@Beowolf sagte in mihome xiaomi Staubsauger 1s - wird nich grün:

Aber immer wenn ich auf der Übersichtsseite in der letzen Kachel "raspberry" auf den kleinen "kringelpfeil" klicke, kommt zwar der Hinweis Node.js-Upgrade, aber nach dem Upgrade steht dort immer noch 20.19.6.

Macht man ja auch nicht so, sondern per

iob nodejs-update

[Beowolf]

OK. Geändert hat sich aber nichts an der Instanz. Immer noch gelb.

SUCCESS!
v22.21.0 has been installed! You are using the latest nodejs@22 release now!

COMPATIBILITY CHECK IN PROGRESS (Only a --dry-run! No modules are really changed or added!)
add fsevents 2.3.3

added 1 package in 2s

139 packages are looking for funding
  run `npm fund` for details


We tried our best to fix your nodejs. Please run iob diag again to verify.

*** RESTARTING ioBroker NOW! ***
 Please refresh or restart your browser in a few moments.

[Thomas Braun]

@Beowolf

Auf welchen Ports lauschen die Geräte denn?
Steht u. a. in der Ausgabe von

iob diag

drin.

[Beowolf]

ok.

SUCCESS!
v22.21.0 has been installed! You are using the latest nodejs@22 release now!

COMPATIBILITY CHECK IN PROGRESS (Only a --dry-run! No modules are really changed or added!)
add fsevents 2.3.3

added 1 package in 2s

139 packages are looking for funding
run npm fund for details

We tried our best to fix your nodejs. Please run iob diag again to verify.

*** RESTARTING ioBroker NOW! ***
Please refresh or restart your browser in a few moments.

[Beowolf]

Port vom Roboter: 54321

Eigener Port: 53421; 53422; 53423; 53424