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

[wendy2702]

Wie Thomas sagt.

Alles zu alt und "root"

Mach dir erstmal einen eigenen User und nutze den....

[yagharek]

@thomas-braun
Root nutze ich zur orientierung, iobroker selber läuft unter einem eigenem Nutzer:

root@iobroker:/opt/iobroker/backups# ps aux | grep iobroker
avahi      303  0.0  0.3   6912  3044 ?        Ss   Jan29   0:11 avahi-daemon: running [iobroker.local]
iobroker 15238  3.0 10.0 210888 95036 ?        Ssl  16:36   3:17 iobroker.js-controller
iobroker 16479  1.2  6.5 171356 61440 ?        Sl   18:00   0:19 io.yeelight-2.0

@thomas-braun
Meinst du mit System das Backup?

[wendy2702]

@yagharek was hat "root" mit Orientierung zu tun ?

Wenn du einen User "Heinz" einrichtest kannst du dich an dem Orientieren

[Thomas Braun]

@yagharek

Dann orientier dich um!
Mit root wird gar nix direkt gemacht. Auch nicht 'orientiert'.

Mit System ist dein Betriebssystem gemeint.
Als USER:

sudo apt update

[yagharek]

@thomas-braun
Ok, danke. Mein System ist aktuell und wurde gestern komplett neu aufgesetzt. Auch iobroker habe ich mit dem Befehl

curl -sLf https://iobroker.net/install.sh | bash -

neu installiert. Bevor ich das Backup einspiele, kann ich iiobroker im Webbrowser aufrufen. Nach der Installation des Backups nicht mehr.

[wendy2702]

dann immer noch zuerst einen USER anlegen und mit diesem weiter arbeiten.

Danach schauen welcher JS Controller installiert ist

iob -v

Wenn 4.0.24 dann unten weiter.

iob stop
iob update
iob upgrade
iob start

[yagharek]

@wendy2702
Es ist 4.0.24:

pi@iobroker:~ $ iob -v
4.0.24
pi@iobroker:~ $ 

[wendy2702]

@yagharek und ein pi User....

[Thomas Braun]

@yagharek

Zeigen:

sudo apt update

iob update
iob upgrade all

[yagharek]

@thomas-braun said in iobroker läuft, aber keine Ports in netstat:

iob upgrade all

Läuft:

pi@iobroker:~ $ sudo apt update
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease                                                                        
Err:3 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                            
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 2a00:6020:200:800::b916:8d0b 443]
Reading package lists... Done                                      
Building dependency tree... Done
Reading state information... Done
8 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 2a00:6020:200:800::b916:8d0b 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
pi@iobroker:~ $ iob update
Used repository: stable
Adapter    "admin"        : 6.3.5    , installed 3.6.0  [Updatable]
Adapter    "discovery"    : 3.1.0    , installed 1.2.4  [Updatable]
Adapter    "email"        : 1.1.4    , installed 1.0.4  [Updatable]
Adapter    "javascript"   : 6.1.4    , installed 4.1.13 [Updatable]
Controller "js-controller": 4.0.24   , installed 4.0.24
Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
Adapter    "socketio"     : 4.2.0    , installed 6.3.3
Adapter    "sonoff"       : 2.5.1    , installed 2.2.2  [Updatable]
Adapter    "vis"          : 1.4.15   , installed 1.2.0  [Updatable]
Adapter    "web"          : 4.3.0    , installed 2.4.1  [Updatable]
Adapter    "yeelight-2"   : 1.1.2    , installed 1.0.1  [Updatable]
pi@iobroker:~ $ iob upgrade all

This upgrade of "yeelight-2" will at least introduce the following changes:
==========================================================================
-> 1.1.2:
Fix Joi Error

-> 1.1.1:
js-controller 3.3 fixes
fixed unhandled promise rejection causing the adapter to stop
adapter won't set power of offline devices to off anymore

-> 1.1.0:
add release-script update testing and dependencies
fixed data types

-> 1.0.4:
fixed data types

-> 1.0.3:
add Pedant
==========================================================================

Would you like to upgrade yeelight-2 from @1.0.1 to @1.1.2 now? [(y)es, (n)o]: y
Update yeelight-2 from @1.0.1 to @1.1.2
NPM version: 8.19.3
Installing iobroker.yeelight-2@1.1.2... (System call)

added 4 packages, and changed 6 packages in 48s

28 packages are looking for funding
  run `npm fund` for details
Update "system.adapter.yeelight-2.0"
upload [20] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/1.png icons/1.png image/png
upload [19] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/2.png icons/2.png image/png
upload [18] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/3.png icons/3.png image/png
upload [17] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/4.png icons/4.png image/png
upload [16] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/5.png icons/5.png image/png
upload [15] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/6.png icons/6.png image/png
upload [14] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/7.png icons/7.png image/png
upload [13] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/bslamp1.png icons/bslamp1.png image/png
upload [12] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/ceiling1.png icons/ceiling1.png image/png
upload [11] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/ceiling10.png icons/ceiling10.png image/png
upload [10] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/ceiling3.png icons/ceiling3.png image/png
upload [9] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/ceiling4.png icons/ceiling4.png image/png
upload [8] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/color.png icons/color.png image/png
upload [7] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/desklamp.png icons/desklamp.png image/png
upload [6] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/mono.png icons/mono.png image/png
upload [5] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/icons/stripe.png icons/stripe.png image/png
upload [4] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/index.html index.html text/html
upload [3] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/index_m.html index_m.html text/html
upload [2] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/lan.jpg lan.jpg image/jpeg
upload [1] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/words.js words.js application/javascript
upload [0] yeelight-2.admin /opt/iobroker/node_modules/iobroker.yeelight-2/admin/yeelight.png yeelight.png image/png

This upgrade of "sonoff" will at least introduce the following changes:
==========================================================================
-> 2.5.1:
Fix crash case reported by Sentry

-> 2.5.0:
Implement writing of NSPanel Widget changes
Fix crash case reported by Sentry

-> 2.4.7:
Fix crash case (Sentry IOBROKER-SONOFF-1S)

-> 2.4.6:
Fix some crash cases reported by Sentry (IOBROKER-SONOFF-B, IOBROKER-SONOFF-R, IOBROKER-SONOFF-4, IOBROKER-SONOFF-1, IOBROKER-SONOFF-13, IOBROKER-SONOFF-1J, IOBROKER-SONOFF-16, IOBROKER-SONOFF-3, IOBROKER-SONOFF-H)
Adjust Uptime to mixed because it seems that it can be number or string

-> 2.4.5:
Fix some crash cases reported by Sentry

-> 2.4.4:
Added UvaIntensity and UvbIntensity

-> 2.4.3:
Better type detection for non-described states
==========================================================================

Would you like to upgrade sonoff from @2.2.2 to @2.5.1 now? [(y)es, (n)o]: y
Update sonoff from @2.2.2 to @2.5.1
NPM version: 8.19.3
Installing iobroker.sonoff@2.5.1... (System call)

changed 1 package in 43s

28 packages are looking for funding
  run `npm fund` for details
Update "system.adapter.sonoff.0"
Update "system.adapter.sonoff.1"
Update "system.adapter.sonoff.2"
Update "system.adapter.sonoff.3"
upload [3] sonoff.admin /opt/iobroker/node_modules/iobroker.sonoff/admin/index.html index.html text/html
upload [2] sonoff.admin /opt/iobroker/node_modules/iobroker.sonoff/admin/index_m.html index_m.html text/html
upload [1] sonoff.admin /opt/iobroker/node_modules/iobroker.sonoff/admin/sonoff.png sonoff.png image/png
upload [0] sonoff.admin /opt/iobroker/node_modules/iobroker.sonoff/admin/words.js words.js application/javascript

This upgrade of "email" will at least introduce the following changes:
==========================================================================
-> 1.1.4:
Prepare compatibility with future js-controller versions

-> 1.1.3:
Make sure the STARTTLS configuration field is displayed

-> 1.1.2:
Fix mail.ee settings

-> 1.1.1:
Allow to use connections to port 25 unencrypted

-> 1.1.0:
Adjust default settings for web.de and 1und1 and add ionos
Add "Always use STARTTLS" option for custom SMTP settings

-> 1.0.10:
Optimize for js-controller 3.3

-> 1.0.9:
Call message callback always with error or without
==========================================================================

Would you like to upgrade email from @1.0.4 to @1.1.4 now? [(y)es, (n)o]: y
Update email from @1.0.4 to @1.1.4
NPM version: 8.19.3
Installing iobroker.email@1.1.4... (System call)

[fastfoot]

@yagharek sagte in iobroker läuft, aber keine Ports in netstat:

Nach der Installation des Backups nicht mehr.

Es gibt den restore Befehl mit der Option --force, welche angewendet werden sollte wenn sich die js-controller von jetzigem System(4.0.24) zu der im Backup gespeicherten(3.xx oder gar 2.xx) unterscheiden.
Also entweder

• iobroker restore --force und hoffen dass es dann klappt(wenn ja alles updaten)

oder

• zuvor den js-controller downgraden(npm i iobroker.js-controller@3) und dann iobroker restore

evtl braucht der npm Befehl ein sudo, da Du das alles als user pi im Ordner /opt/iobroker machst

[Thomas Braun]

@yagharek

Und welche Datenbankpaar hast du im alten iobroker benutzt?

[yagharek]

Vielen dank an alle für die Hilfe.

Ich habe komplett übersehen, dass man nach einem "iobroker restore --force" ein iob update und iob upgrade durchführen muss.

[wendy2702]

@yagharek Das muss man nur wenn das Backup und die alte Installation hoffnungslos veraltet war.