Ich hoffe, es ist nicht schlimm, wenn ich hier auf den Thread antworte und keinen neuen Thread aufmache.
Hat jemand Erfahrung mit dem "Bosch Smart Home Heizkörperthermostat II"?
Über die Suche konnte ich nichts finden. Ich habe aktuell das "Eurotronic Spirit" seit ca. 3 Jahren im Einsatz, leider immer mal mit Problemen, daher möchte ich mir jetzt einen neuen Hersteller zulegen.
Ich schwankte zwischen dem Heizkörperthermostat "Aqara E1" und dem "Danfoss Ally", bin aber jetzt auch auf Bosch gestoßen und bin mir nun unsicher, welche von den 3 das zuverlässigere Heizkörperthermostat ist, in Hinsicht auf Probleme mit dem ioBroker, aber auch wie zuverlässig die Hardware ist.

Danke schon mal!

@djmarc75 sagte in Zigbee-Adapter Error herdsman Start (Texas CC26X2R1):

@lister Na dann zeig mal Deinen Einstellungen im Zigbee-Adapter

Hier die Einstellungen

ls -la /dev/serial/by-id

total 0
drwxr-xr-x 2 root root 80 Aug  5 18:32 .
drwxr-xr-x 4 root root 80 Aug  5 18:32 ..
lrwxrwxrwx 1 root root 13 Aug  5 18:32 usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Aug  5 18:32 usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if03 -> ../../ttyACM1

@thomas-braun sagte in Zigbee-Adapter Error herdsman Start (Texas CC26X2R1):

timedatectl

timedatectl

               Local time: Fri 2022-08-05 20:23:12 CEST
           Universal time: Fri 2022-08-05 18:23:12 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

sudo ln -s /usr/bin/node /usr/bin/nodejs
-> gab es noch nicht

uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

aarch64
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.16.0
v16.16.0
8.11.0
lister
/home/lister
Hit:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease     
Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease      
Hit:5 https://deb.nodesource.com/node_16.x jammy InRelease
Reading package lists... Done                      
Building dependency tree... Done
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
nodejs:
  Installed: 16.16.0-deb-1nodesource1
  Candidate: 16.16.0-deb-1nodesource1
  Version table:
 *** 16.16.0-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x jammy/main arm64 Packages
        100 /var/lib/dpkg/status
     12.22.9~dfsg-1ubuntu3 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages

@djmarc75 sagte in Zigbee-Adapter Error herdsman Start (Texas CC26X2R1):

RPI3B+

Es geht um den RPI3B+

Suche habe ich schon benutzt und einiges gelesen aber keine wirkliche Lösung gefunden, der Thread oben war mir am nächsten dran.

@djmarc75 sagte in Zigbee-Adapter Error herdsman Start (Texas CC26X2R1):

Und der RPI hat wahrscheinlich fantastische 1GB RAM?

1GB ist richtig aber ich habe dasselbe Problem mit dem PI 4 mit 4GB RAM auch.

@djmarc75 sagte in Zigbee-Adapter Error herdsman Start (Texas CC26X2R1):

Was ist denn da so alles am laufen ?

Installiert ist jetzt nur ioBroker und octoPrint, allerdings war der Fehler schon vor octoPrint da.

Re: (gelöst)Zigbee-Adapter bleibt Gelb Error herdsman Start

Hallo,
ich habe aktuell ähnliche Problem wie im Thread oben beschrieben. Nur gibt es das Problem nur, wenn der ioBroker mal abschmiert und neu gestartet werden muss aber nicht immer vll. bei jedem 5 Neustart bzw. er kommt einfach.

Fehlermeldung:

2022-08-05 18:33:40.443  - error: zigbee.0 (4353) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if00'"

2022-08-05 18:33:40.447  - error: zigbee.0 (4353) Failed to start Zigbee

2022-08-05 18:33:40.449  - error: zigbee.0 (4353) Error herdsman start

2022-08-05 18:33:40.443  - error: zigbee.0 (4353) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if00'"

2022-08-05 18:33:40.447  - error: zigbee.0 (4353) Failed to start Zigbee

2022-08-05 18:33:40.449  - error: zigbee.0 (4353) Error herdsman start

Kompletter Log:

2022-08-05 18:32:58.921  - info: host.ubuntu-pi iobroker.js-controller version 4.0.23 js-controller starting
2022-08-05 18:32:58.954  - info: host.ubuntu-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-08-05 18:32:58.956  - info: host.ubuntu-pi hostname: ubuntu-pi, node: v16.16.0
2022-08-05 18:32:58.958  - info: host.ubuntu-pi ip addresses: 192.168.2.25 fe80::ba27:ebff:fef5:6f8e
2022-08-05 18:32:58.921  - info: host.ubuntu-pi iobroker.js-controller version 4.0.23 js-controller starting
2022-08-05 18:32:58.954  - info: host.ubuntu-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-08-05 18:32:58.956  - info: host.ubuntu-pi hostname: ubuntu-pi, node: v16.16.0
2022-08-05 18:32:58.958  - info: host.ubuntu-pi ip addresses: 192.168.2.25 fe80::ba27:ebff:fef5:6f8e
2022-08-05 18:33:02.087  - info: host.ubuntu-pi connected to Objects and States
2022-08-05 18:33:02.152  - info: host.ubuntu-pi added notifications configuration of host
2022-08-05 18:33:02.087  - info: host.ubuntu-pi connected to Objects and States
2022-08-05 18:33:02.152  - info: host.ubuntu-pi added notifications configuration of host
2022-08-05 18:33:02.793  - info: host.ubuntu-pi 6 instances found
2022-08-05 18:33:02.825  - info: host.ubuntu-pi starting 6 instances
2022-08-05 18:33:02.953  - info: host.ubuntu-pi instance system.adapter.admin.0 started with pid 4308
2022-08-05 18:33:02.793  - info: host.ubuntu-pi 6 instances found
2022-08-05 18:33:02.825  - info: host.ubuntu-pi starting 6 instances
2022-08-05 18:33:02.953  - info: host.ubuntu-pi instance system.adapter.admin.0 started with pid 4308
2022-08-05 18:33:06.899  - info: host.ubuntu-pi instance system.adapter.javascript.0 started with pid 4319
2022-08-05 18:33:07.158  - info: admin.0 (4308) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:07.440  - info: admin.0 (4308) requesting all states
2022-08-05 18:33:07.443  - info: admin.0 (4308) requesting all objects
2022-08-05 18:33:06.899  - info: host.ubuntu-pi instance system.adapter.javascript.0 started with pid 4319
2022-08-05 18:33:07.158  - info: admin.0 (4308) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:07.440  - info: admin.0 (4308) requesting all states
2022-08-05 18:33:07.443  - info: admin.0 (4308) requesting all objects
2022-08-05 18:33:08.587  - info: admin.0 (4308) received all objects
2022-08-05 18:33:08.959  - info: admin.0 (4308) https server listening on port 8081
2022-08-05 18:33:08.961  - info: admin.0 (4308) Use link "https://localhost:8081" to configure.
2022-08-05 18:33:08.587  - info: admin.0 (4308) received all objects
2022-08-05 18:33:08.959  - info: admin.0 (4308) https server listening on port 8081
2022-08-05 18:33:08.961  - info: admin.0 (4308) Use link "https://localhost:8081" to configure.
2022-08-05 18:33:10.903  - info: host.ubuntu-pi instance system.adapter.history.0 started with pid 4330
2022-08-05 18:33:14.630  - info: history.0 (4330) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.history, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:14.713  - info: javascript.0 (4319) starting. Version 5.7.0 in /opt/iobroker/node_modules/iobroker.javascript, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:14.912  - info: host.ubuntu-pi instance system.adapter.zigbee.0 started with pid 4353
2022-08-05 18:33:15.245  - info: javascript.0 (4319) requesting all states
2022-08-05 18:33:15.248  - info: javascript.0 (4319) requesting all objects
2022-08-05 18:33:14.630  - info: history.0 (4330) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.history, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:14.713  - info: javascript.0 (4319) starting. Version 5.7.0 in /opt/iobroker/node_modules/iobroker.javascript, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:14.912  - info: host.ubuntu-pi instance system.adapter.zigbee.0 started with pid 4353
2022-08-05 18:33:15.245  - info: javascript.0 (4319) requesting all states
2022-08-05 18:33:15.248  - info: javascript.0 (4319) requesting all objects
2022-08-05 18:33:15.870  - info: javascript.0 (4319) received all objects
2022-08-05 18:33:15.905  - info: javascript.0 (4319) received all states
2022-08-05 18:33:15.980  - info: javascript.0 (4319) Start javascript script.js.Bettbeleuchtung_AN_AUS
2022-08-05 18:33:16.130  - info: javascript.0 (4319) script.js.Bettbeleuchtung_AN_AUS: registered 2 subscriptions and 0 schedules
2022-08-05 18:33:15.870  - info: javascript.0 (4319) received all objects
2022-08-05 18:33:15.905  - info: javascript.0 (4319) received all states
2022-08-05 18:33:15.980  - info: javascript.0 (4319) Start javascript script.js.Bettbeleuchtung_AN_AUS
2022-08-05 18:33:16.130  - info: javascript.0 (4319) script.js.Bettbeleuchtung_AN_AUS: registered 2 subscriptions and 0 schedules
2022-08-05 18:33:18.899  - info: host.ubuntu-pi instance system.adapter.discovery.0 started with pid 4360
2022-08-05 18:33:22.933  - info: host.ubuntu-pi instance system.adapter.backitup.0 started with pid 4375
2022-08-05 18:33:23.318  - info: discovery.0 (4360) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:22.933  - info: host.ubuntu-pi instance system.adapter.backitup.0 started with pid 4375
2022-08-05 18:33:23.318  - info: discovery.0 (4360) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:24.271  - info: zigbee.0 (4353) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:24.590  - info: zigbee.0 (4353) delete old Backup files. keep only last 10
2022-08-05 18:33:24.598  - info: zigbee.0 (4353) Starting Zigbee  npm ...
2022-08-05 18:33:24.590  - info: zigbee.0 (4353) delete old Backup files. keep only last 10
2022-08-05 18:33:24.598  - info: zigbee.0 (4353) Starting Zigbee  npm ...
2022-08-05 18:33:27.852  - info: zigbee.0 (4353) Installed Version: iobroker.zigbee@1.7.5
2022-08-05 18:33:29.400  - error: zigbee.0 (4353) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if00'"
2022-08-05 18:33:29.402  - error: zigbee.0 (4353) Failed to start Zigbee
2022-08-05 18:33:29.405  - error: zigbee.0 (4353) Error herdsman start
2022-08-05 18:33:29.400  - error: zigbee.0 (4353) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if00'"
2022-08-05 18:33:29.402  - error: zigbee.0 (4353) Failed to start Zigbee
2022-08-05 18:33:29.405  - error: zigbee.0 (4353) Error herdsman start
2022-08-05 18:33:31.243  - info: backitup.0 (4375) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:31.433  - info: backitup.0 (4375) [iobroker] backup was activated at 02:40 every 1 day(s)
2022-08-05 18:33:31.243  - info: backitup.0 (4375) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.16.0, js-controller: 4.0.23
2022-08-05 18:33:31.433  - info: backitup.0 (4375) [iobroker] backup was activated at 02:40 every 1 day(s)
2022-08-05 18:33:39.416  - info: zigbee.0 (4353) Try to reconnect. 1 attempts left
2022-08-05 18:33:39.420  - info: zigbee.0 (4353) Starting Zigbee  npm ...
2022-08-05 18:33:39.487  - info: zigbee.0 (4353) Installed Version: iobroker.zigbee@1.7.5
2022-08-05 18:33:39.416  - info: zigbee.0 (4353) Try to reconnect. 1 attempts left
2022-08-05 18:33:39.420  - info: zigbee.0 (4353) Starting Zigbee  npm ...
2022-08-05 18:33:39.487  - info: zigbee.0 (4353) Installed Version: iobroker.zigbee@1.7.5
2022-08-05 18:33:40.443  - error: zigbee.0 (4353) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if00'"
2022-08-05 18:33:40.447  - error: zigbee.0 (4353) Failed to start Zigbee
2022-08-05 18:33:40.449  - error: zigbee.0 (4353) Error herdsman start
2022-08-05 18:33:40.443  - error: zigbee.0 (4353) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100GQC-if00'"
2022-08-05 18:33:40.447  - error: zigbee.0 (4353) Failed to start Zigbee
2022-08-05 18:33:40.449  - error: zigbee.0 (4353) Error herdsman start
2022-08-05 18:39:49.506  - info: admin.0 (4308) failed connection to socket.io from ::ffff:192.168.2.41:
2022-08-05 18:39:49.518  - error: admin.0 (4308) Error: "error"
2022-08-05 18:39:49.598  - info: admin.0 (4308) failed connection to socket.io from ::ffff:192.168.2.41:
2022-08-05 18:39:49.602  - error: admin.0 (4308) Error: "error"
2022-08-05 18:39:49.506  - info: admin.0 (4308) failed connection to socket.io from ::ffff:192.168.2.41:
2022-08-05 18:39:49.518  - error: admin.0 (4308) Error: "error"
2022-08-05 18:39:49.598  - info: admin.0 (4308) failed connection to socket.io from ::ffff:192.168.2.41:
2022-08-05 18:39:49.602  - error: admin.0 (4308) Error: "error"
2022-08-05 18:40:16.054  - error: zigbee.0 (4353) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
2022-08-05 18:40:37.936  - error: zigbee.0 (4353) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')

Das Problem habe ich seit einiger Zeit, daher habe ich den Raspberry PI 3B komplett neu aufgesetzt und bin von ubuntu 20.04 server auf 22.04 server umgestiegen. Allerdings bleibt das Problem bestehen.
Dann merkte ich, dass meine Firmware von 2019 ist als ich das ganze in Betrieb genommen habe und dachte es liegt daran. Also jetzt die aktuelle Firmware vom 19.02.22 drauf gespielt. Leider bleibt der Fehler, da er schleichend kam, weiß ich nicht genau ab welcher ioBroker Version bzw. Zigbee-Adapter Version der Fehler sich eingeschlichen hat, anfangs dachte ich mir nichts bei.

Ich habe die Einstellung im Zigbee-Adapter überprüft und die Angaben beim COM-Anschlussname stimmen überein. Ich kann den Fehler nur beheben, wenn ich den CC26X2R1 neu flashen und dabei muss ich unbedingt Pkt. 4 + 5 aus der Anleitung durchführen, sonst bringt der Flash auch nichts. Oder ich nutze den Resetknopf am CC26X2R1, dann kann ioBroker wieder auf den CC26X2R1 zugreifen, das habe ich leider erst vor kurzem rausgefunden. Vorher musste ich den CC26X2R1 immer erst ausbauen, damit ich ihn am Window Rechner neue flashen konnte.

Jetzt meine Frage, woran kann es liegen, dass ioBroker nicht mehr auf CC26X2R1 zugreifen kann?
Ist der CC26X2R1 defekt oder gibt es ein Problem mit dem Zigbee-Adapter?

Danke schon mal!

Mein System

Raspberry PI 3 B+
PlatformBetriebssystem:linux
Architektur:arm64
CPUs:4
Geschwindigkeit:1400 MHz
Modell:Cortex-A53
RAM:905.1 MB
System-Betriebszeit:01:23:47
Node.js:v16.16.0
time:1659717604719
timeOffset:-120
Adapter-Anzahl:423
NPM:v8.11.0
Datenträgergröße:29.0 GB
freier Festplattenspeicher:15.7 GB
Betriebszeit:00:07:10
Aktive Instanzen:6
Pfad:/opt/iobroker/

@apollon77 Danke!

@apollon77 Danke für deine Antwort.
Bei admin hab ich die Version 5.3.8 installiert, war vorinstalliert und ist auch aktuell die neuste. Ein Update hab ich nur bei discovery gemacht, die Fehlermeldung war aber vorher schon da.

Das klingt als wäre die Fehlermeldung nicht weiter schlimm?

Hallo,
ich habe ein Raspberry PI 4B mit 4GB RAM, mit dem offiziell USB-C Netzteil und einem Joy-IT Gehäuse mit 2 Lüftern und montierten Kühlkörpern.
Auf dem Raspberry habe ich ubuntu 22.04 server frisch aufgesetzt auf einer 32GB SanDisk Extreme micro SDHC A1 UHS-I U3
Dann habe ich das ubuntu per "sudo apt-get update" und anschließend "sudo apt-get upgrade" auf den neusten Stand gebracht. Anschließen ioBroker per "curl -sLf https://iobroker.net/install.sh | bash -" installiert.

Und dann ioBroker aufgerufen und die Installation abgeschlossen. Bei allen diesen Schritten hatte ich keinen Fehler angezeigt bekommen und trotzdem bekomme ich in den Logs direkt "Error: "error"" angezeigt.
Ich wollte jetzt mal fragen, ist es normal das diese Fehler kommen?

Mein System aus dem ioBroker kopiert

Ich bedanke mich schon mal für die Hilfe und Erklärungen!

Hier mein Log + ein Neustart des raspberry

2022-07-26 20:49:02.552 - info: host.ubuntu-pi iobroker.js-controller version 4.0.23 js-controller starting
2022-07-26 20:49:02.559 - info: host.ubuntu-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-26 20:49:02.561 - info: host.ubuntu-pi hostname: ubuntu-pi, node: v16.16.0
2022-07-26 20:49:02.562 - info: host.ubuntu-pi ip addresses: 192.168.2.36 fe80::dea6:32ff:fe58:2e8b
2022-07-26 20:49:02.936 - info: host.ubuntu-pi connected to Objects and States
2022-07-26 20:49:02.966 - info: host.ubuntu-pi Node.js version has changed from unknown to 16.16.0
2022-07-26 20:49:03.035 - info: host.ubuntu-pi Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
2022-07-26 20:49:03.057 - info: host.ubuntu-pi added notifications configuration of host
2022-07-26 20:49:03.428 - info: host.ubuntu-pi 3 instances found
2022-07-26 20:49:03.440 - info: host.ubuntu-pi starting 3 instances
2022-07-26 20:49:03.521 - info: host.ubuntu-pi instance system.adapter.admin.0 started with pid 8260
2022-07-26 20:49:05.824 - info: admin.0 (8260) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
2022-07-26 20:49:05.896 - info: admin.0 (8260) requesting all states
2022-07-26 20:49:05.897 - info: admin.0 (8260) requesting all objects
2022-07-26 20:49:06.008 - info: admin.0 (8260) received all objects
2022-07-26 20:49:06.130 - info: admin.0 (8260) http server listening on port 8081
2022-07-26 20:49:06.131 - info: admin.0 (8260) Use link "http://localhost:8081" to configure.
2022-07-26 20:49:06.254 - warn: admin.0 (8260) Repository cannot be read: Active repo - stable
2022-07-26 20:49:06.255 - warn: admin.0 (8260) Active repository "stable cannot be read
2022-07-26 20:49:07.483 - info: host.ubuntu-pi instance system.adapter.discovery.0 started with pid 8318
2022-07-26 20:49:09.537 - info: discovery.0 (8318) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.16.0, js-controller: 4.0.23
2022-07-26 20:49:11.481 - info: host.ubuntu-pi instance system.adapter.backitup.0 started with pid 8333
2022-07-26 20:49:13.487 - info: backitup.0 (8333) starting. Version 2.4.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.16.0, js-controller: 4.0.23
2022-07-26 20:49:14.563 - info: backitup.0 (8333) [iobroker] backup was activated at 02:40 every 1 day(s)
2022-07-26 20:50:07.675 - info: host.ubuntu-pi received SIGTERM
2022-07-26 20:50:07.695 - info: backitup.0 (8333) cleaned everything up...
2022-07-26 20:50:07.723 - info: admin.0 (8260) terminating http server on port 8081
2022-07-26 20:50:07.688 - info: host.ubuntu-pi stopInstance system.adapter.admin.0 (force=false, process=true)
2022-07-26 20:50:07.727 - info: host.ubuntu-pi stopInstance system.adapter.discovery.0 (force=false, process=true)
2022-07-26 20:50:07.728 - info: host.ubuntu-pi stopInstance system.adapter.backitup.0 (force=false, process=true)
2022-07-26 20:50:07.793 - info: backitup.0 (8333) Got terminate signal TERMINATE_YOURSELF
2022-07-26 20:50:07.801 - info: discovery.0 (8318) Got terminate signal TERMINATE_YOURSELF
2022-07-26 20:50:07.820 - info: admin.0 (8260) Got terminate signal TERMINATE_YOURSELF
2022-07-26 20:50:07.797 - info: host.ubuntu-pi stopInstance system.adapter.admin.0 send kill signal
2022-07-26 20:50:07.822 - info: backitup.0 (8333) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-26 20:50:07.848 - info: discovery.0 (8318) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-26 20:50:07.851 - info: host.ubuntu-pi stopInstance system.adapter.discovery.0 send kill signal
2022-07-26 20:50:07.853 - info: host.ubuntu-pi stopInstance system.adapter.backitup.0 send kill signal
2022-07-26 20:50:07.858 - info: admin.0 (8260) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-26 20:50:08.467 - info: host.ubuntu-pi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-26 20:50:08.468 - info: host.ubuntu-pi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-26 20:50:08.503 - info: host.ubuntu-pi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-26 20:50:08.504 - info: host.ubuntu-pi All instances are stopped.
2022-07-26 20:50:08.582 - info: host.ubuntu-pi terminated
2022-07-26 20:50:19.476 - info: host.ubuntu-pi iobroker.js-controller version 4.0.23 js-controller starting
2022-07-26 20:50:19.485 - info: host.ubuntu-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-26 20:50:19.486 - info: host.ubuntu-pi hostname: ubuntu-pi, node: v16.16.0
2022-07-26 20:50:19.487 - info: host.ubuntu-pi ip addresses: 192.168.2.36 fe80::dea6:32ff:fe58:2e8b
2022-07-26 20:50:19.962 - info: host.ubuntu-pi connected to Objects and States
2022-07-26 20:50:19.998 - info: host.ubuntu-pi added notifications configuration of host
2022-07-26 20:50:20.587 - info: host.ubuntu-pi 3 instances found
2022-07-26 20:50:20.598 - info: host.ubuntu-pi starting 3 instances
2022-07-26 20:50:20.677 - info: host.ubuntu-pi instance system.adapter.admin.0 started with pid 869
2022-07-26 20:50:23.359 - info: admin.0 (869) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
2022-07-26 20:50:23.432 - info: admin.0 (869) requesting all states
2022-07-26 20:50:23.433 - info: admin.0 (869) requesting all objects
2022-07-26 20:50:23.571 - info: admin.0 (869) received all objects
2022-07-26 20:50:23.593 - warn: admin.0 (869) Repository cannot be read: Active repo - stable
2022-07-26 20:50:23.594 - warn: admin.0 (869) Active repository "stable cannot be read
2022-07-26 20:50:23.867 - info: admin.0 (869) http server listening on port 8081
2022-07-26 20:50:23.867 - info: admin.0 (869) Use link "http://localhost:8081" to configure.
2022-07-26 20:50:24.640 - info: host.ubuntu-pi instance system.adapter.discovery.0 started with pid 918
2022-07-26 20:50:26.635 - info: discovery.0 (918) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.16.0, js-controller: 4.0.23
2022-07-26 20:50:28.637 - info: host.ubuntu-pi instance system.adapter.backitup.0 started with pid 934
2022-07-26 20:50:30.747 - info: backitup.0 (934) starting. Version 2.4.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.16.0, js-controller: 4.0.23
2022-07-26 20:50:30.839 - info: backitup.0 (934) [iobroker] backup was activated at 02:40 every 1 day(s)
2022-07-26 20:52:10.851 - info: host.ubuntu-pi Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
2022-07-26 20:55:20.331 - info: host.ubuntu-pi stopInstance system.adapter.admin.0 (force=false, process=true)
2022-07-26 20:55:20.343 - info: host.ubuntu-pi stopInstance system.adapter.admin.0 send kill signal
2022-07-26 20:55:20.342 - info: admin.0 (869) Got terminate signal TERMINATE_YOURSELF
2022-07-26 20:55:20.348 - info: admin.0 (869) terminating http server on port 8081
2022-07-26 20:55:20.350 - info: admin.0 (869) terminating
2022-07-26 20:55:20.351 - info: admin.0 (869) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-07-26 20:55:20.939 - info: host.ubuntu-pi instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-07-26 20:55:23.395 - info: host.ubuntu-pi instance system.adapter.admin.0 started with pid 1193
2022-07-26 20:55:25.504 - info: admin.0 (1193) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
2022-07-26 20:55:25.653 - info: admin.0 (1193) requesting all states
2022-07-26 20:55:25.655 - info: admin.0 (1193) requesting all objects
2022-07-26 20:55:26.176 - info: admin.0 (1193) received all objects
2022-07-26 20:55:26.348 - info: admin.0 (1193) https server listening on port 8081
2022-07-26 20:55:26.349 - info: admin.0 (1193) Use link "https://localhost:8081" to configure.
2022-07-26 20:55:51.408 - info: admin.0 (1193) failed connection to socket.io from ::ffff:192.168.2.41:
2022-07-26 20:55:51.414 - error: admin.0 (1193) Error: "error"
2022-07-26 20:55:51.476 - info: admin.0 (1193) failed connection to socket.io from ::ffff:192.168.2.41:
2022-07-26 20:55:51.478 - error: admin.0 (1193) Error: "error"
2022-07-26 20:57:02.108 - info: host.ubuntu-pi iobroker upgrade discovery@3.0.5
2022-07-26 20:57:04.581 - info: host.ubuntu-pi iobroker Update discovery from @3.0.3 to @3.0.5
2022-07-26 20:57:05.738 - info: host.ubuntu-pi iobroker NPM version: 8.11.0
2022-07-26 20:57:05.742 - info: host.ubuntu-pi iobroker Installing iobroker.discovery@3.0.5... (System call)
2022-07-26 20:57:11.382 - info: host.ubuntu-pi iobroker
2022-07-26 20:57:11.385 - info: host.ubuntu-pi iobroker changed 1 package in 5s38 packages are looking for funding run `npm fund` for details
2022-07-26 20:57:11.471 - info: host.ubuntu-pi iobroker Update "system.adapter.discovery.0"
2022-07-26 20:57:11.485 - info: host.ubuntu-pi stopInstance system.adapter.discovery.0 (force=false, process=true)
2022-07-26 20:57:11.494 - info: discovery.0 (918) Got terminate signal TERMINATE_YOURSELF
2022-07-26 20:57:11.495 - info: host.ubuntu-pi stopInstance system.adapter.discovery.0 send kill signal
2022-07-26 20:57:11.497 - info: discovery.0 (918) terminating
2022-07-26 20:57:11.499 - info: discovery.0 (918) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-07-26 20:57:11.529 - info: host.ubuntu-pi iobroker upload [6] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/discovery.png discovery.png image/png
2022-07-26 20:57:11.572 - info: host.ubuntu-pi iobroker upload [5] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index.html index.html text/html
2022-07-26 20:57:11.608 - info: host.ubuntu-pi iobroker upload [4] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index_m.html index_m.html text/html
2022-07-26 20:57:11.663 - info: host.ubuntu-pi iobroker upload [3] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings.html settings.html text/html
2022-07-26 20:57:11.694 - info: host.ubuntu-pi iobroker upload [2] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings_m.html settings_m.html text/html
2022-07-26 20:57:11.712 - info: host.ubuntu-pi iobroker upload [1] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/translateTools.js translateTools.js application/javascript
2022-07-26 20:57:11.725 - info: host.ubuntu-pi iobroker upload [0] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/words.js words.js application/javascript
2022-07-26 20:57:12.061 - info: host.ubuntu-pi instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-07-26 20:57:12.784 - info: host.ubuntu-pi iobroker exit 0
2022-07-26 20:57:14.555 - info: host.ubuntu-pi instance system.adapter.discovery.0 started with pid 1253
2022-07-26 20:57:16.444 - info: discovery.0 (1253) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.16.0, js-controller: 4.0.23
2022-07-26 21:06:31.596 - error: admin.0 (1193) Error: "error"
2022-07-26 21:06:31.673 - error: admin.0 (1193) Error: "error"
2022-07-26 21:06:31.756 - error: admin.0 (1193) Error: "error"
2022-07-26 21:06:46.832 - info: host.ubuntu-pi received SIGTERM
2022-07-26 21:06:46.838 - info: backitup.0 (934) cleaned everything up...
2022-07-26 21:06:46.843 - info: host.ubuntu-pi stopInstance system.adapter.admin.0 (force=false, process=true)
2022-07-26 21:06:46.845 - info: host.ubuntu-pi stopInstance system.adapter.discovery.0 (force=false, process=true)
2022-07-26 21:06:46.846 - info: host.ubuntu-pi stopInstance system.adapter.backitup.0 (force=false, process=true)
2022-07-26 21:06:46.834 - info: admin.0 (1193) terminating https server on port 8081
2022-07-26 21:06:46.894 - info: backitup.0 (934) Got terminate signal TERMINATE_YOURSELF
2022-07-26 21:06:46.910 - info: discovery.0 (1253) Got terminate signal TERMINATE_YOURSELF
2022-07-26 21:06:46.894 - info: admin.0 (1193) Got terminate signal TERMINATE_YOURSELF
2022-07-26 21:06:46.906 - info: backitup.0 (934) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-26 21:06:46.915 - info: discovery.0 (1253) terminating
2022-07-26 21:06:46.919 - info: discovery.0 (1253) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-07-26 21:06:46.927 - info: host.ubuntu-pi stopInstance system.adapter.admin.0 send kill signal
2022-07-26 21:06:46.931 - info: host.ubuntu-pi stopInstance system.adapter.discovery.0 send kill signal
2022-07-26 21:06:46.935 - info: admin.0 (1193) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-26 21:06:46.936 - info: host.ubuntu-pi stopInstance system.adapter.backitup.0 send kill signal
2022-07-26 21:06:47.504 - info: host.ubuntu-pi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-26 21:06:47.518 - info: host.ubuntu-pi instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-07-26 21:06:47.570 - info: host.ubuntu-pi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-26 21:06:47.571 - info: host.ubuntu-pi All instances are stopped.
2022-07-26 21:06:50.101 - info: host.ubuntu-pi terminated
2022-07-26 21:07:00.932 - info: host.ubuntu-pi iobroker.js-controller version 4.0.23 js-controller starting
2022-07-26 21:07:00.941 - info: host.ubuntu-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-26 21:07:00.942 - info: host.ubuntu-pi hostname: ubuntu-pi, node: v16.16.0
2022-07-26 21:07:00.944 - info: host.ubuntu-pi ip addresses: 192.168.2.36 fe80::dea6:32ff:fe58:2e8b
2022-07-26 21:07:01.678 - info: host.ubuntu-pi connected to Objects and States
2022-07-26 21:07:01.713 - info: host.ubuntu-pi added notifications configuration of host
2022-07-26 21:07:02.256 - info: host.ubuntu-pi 3 instances found
2022-07-26 21:07:02.268 - info: host.ubuntu-pi starting 3 instances
2022-07-26 21:07:02.345 - info: host.ubuntu-pi instance system.adapter.admin.0 started with pid 867
2022-07-26 21:07:05.039 - info: admin.0 (867) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
2022-07-26 21:07:05.207 - info: admin.0 (867) requesting all states
2022-07-26 21:07:05.209 - info: admin.0 (867) requesting all objects
2022-07-26 21:07:05.935 - info: admin.0 (867) received all objects
2022-07-26 21:07:06.200 - info: admin.0 (867) https server listening on port 8081
2022-07-26 21:07:06.201 - info: admin.0 (867) Use link "https://localhost:8081" to configure.
2022-07-26 21:07:06.316 - info: host.ubuntu-pi instance system.adapter.discovery.0 started with pid 920
2022-07-26 21:07:08.298 - info: discovery.0 (920) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.16.0, js-controller: 4.0.23
2022-07-26 21:07:10.310 - info: host.ubuntu-pi instance system.adapter.backitup.0 started with pid 936
2022-07-26 21:07:12.415 - info: backitup.0 (936) starting. Version 2.4.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.16.0, js-controller: 4.0.23
2022-07-26 21:07:12.513 - info: backitup.0 (936) [iobroker] backup was activated at 02:40 every 1 day(s)
2022-07-26 21:08:07.731 - info: admin.0 (867) failed connection to socket.io from ::ffff:192.168.2.41:
2022-07-26 21:08:07.738 - error: admin.0 (867) Error: "error"
2022-07-26 21:08:07.840 - info: admin.0 (867) failed connection to socket.io from ::ffff:192.168.2.41:
2022-07-26 21:08:07.841 - error: admin.0 (867) Error: "error"

iobroker.current.log

@Thomas-Braun sagte in Heizkörperthermostat Essentials 120112 & CC26X2R1:

@Lister Wobei das eigentlich auch natürlich ohne sudo vorweg starten sollte.
Ich hab hier kein X laufen, daher kann ich mir das nicht mal anschauen.

ohne sudo also per "deCONZ" in das Eingabefenster per Remote starte es, ich glaub es nicht.

Danke dir!