Matter (Adapter) Problem

darkblu

@bluefox , Github Issue hatte ich zuerst aktualisiert. Ist also schon erledigt.

Was am 19.10 um 15:20 passiert ist weiss ich nicht mehr, ist ja schon ein Tag her. Ich gucke gleich mal ob ich da noch was liefern kann.

darkblu

@bluefox ,
gestern um 15:20:00 bis 15:20:59 sind im Log über 1500 Sachen passiert.
Ich blicke da aber nicht durch.

Die Dateien aus dem ota Ordner habe ich auch bei Github hochgeladen, bzw nur die .json, die .pid und .lock gehen nicht.
Allerdings ist die .lock leer,
in der .pid steht: 3751 228c20699dd9506e

die sind aber auch von heute, siehe screenshot:

Bluefox

@darkblu Dass die beiden Dateien heute wieder da sind, ist normal. Die laufende Instanz legt sie beim Start an und hält die Sperre, solange sie läuft. Zum Problem wird es erst, wenn der Prozess weg ist und die Dateien liegen bleiben. Prüf mal, ob 3751 gerade deine matter.0 ist:

ps -fp 3751

Wenn dort matter.0 steht, ist alles in Ordnung.

Die 1500 Zeilen musst du nicht alle lesen. Uns interessiert nur, was matter.0 und der Host um die Zeit gemacht haben:

zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0|host\." | head -200

Poste die Ausgabe bitte hier oder im Issue. Wichtig ist vor allem, ob die Instanz da gestoppt oder neu gestartet wurde und ob dabei "send kill signal" oder ein Exit-Code auftaucht.

Damit wir das nächste Mal direkt sehen, was passiert: Wenn es wieder auftritt, lösch die Dateien erst nach diesem Befehl:

ls -la --time-style=full-iso /opt/iobroker/iobroker-data/matter.0/ota/
cat /opt/iobroker/iobroker-data/matter.0/ota/matter.pid

Dann suchen wir im Log nach genau dieser Uhrzeit und PID.

darkblu

hier die Ausgabe von:

ps -fp 3751

dirk@smart:~ $ ps -fp 3751
UID          PID    PPID  C STIME TTY          TIME CMD

hätte ich wohl gestern abend direkt machen sollen ?

und hier die Ausgabe von:

zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0|host\." | head -200

dirk@smart:~ $ zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0|host\." | head -200
2026-10-19 15:10:10.035  - info: host.smart instance system.adapter.dwd.0 in version "2.8.5" started with pid 6194
2026-10-19 15:10:12.668  - info: host.smart instance system.adapter.dwd.0 having pid 6194 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-10-19 15:13:21.477  - info: host.smart stopInstance system.adapter.admin.0 (force=false, process=true)
2026-10-19 15:13:21.520  - info: host.smart stopInstance system.adapter.admin.0 send kill signal
2026-10-19 15:13:22.074  - info: host.smart instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-10-19 15:13:25.078  - info: host.smart instance system.adapter.admin.0 in version "8.0.14" started with pid 6215
2026-10-19 15:13:55.665  - info: host.smart stopInstance system.adapter.admin.0 (force=false, process=true)
2026-10-19 15:13:55.716  - info: host.smart stopInstance system.adapter.admin.0 send kill signal
2026-10-19 15:13:56.276  - info: host.smart instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-10-19 15:13:59.221  - info: host.smart instance system.adapter.admin.0 in version "8.0.14" started with pid 6263
2026-10-19 15:14:42.595  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/voltage changed to 237000
2026-10-19 15:14:42.597  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/apparentCurrent changed to 2
2026-10-19 15:14:42.599  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/activePower changed to 100
2026-10-19 15:14:42.600  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/apparentPower changed to 500
2026-10-19 15:14:42.602  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/rmsVoltage changed to 237000
2026-10-19 15:14:42.604  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/rmsCurrent changed to 2
2026-10-19 15:14:42.605  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/rmsPower changed to 474
2026-10-19 15:14:42.607  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/powerFactor changed to 2100
2026-10-19 15:14:42.607  - debug: matter.0 (2075) Set matter.0.controller.14388134951535934862.ElectricalSensor-2.VOLTAGE to 237 (ack = true)
2026-10-19 15:14:42.607  - debug: matter.0 (2075) Set matter.0.controller.14388134951535934862.ElectricalSensor-2.ELECTRIC_POWER to 0.1 (ack = true)
2026-10-19 15:14:44.603  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/activePower changed to 0
2026-10-19 15:14:44.605  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/rmsCurrent changed to 0
2026-10-19 15:14:44.607  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/rmsPower changed to 0
2026-10-19 15:14:44.607  - debug: matter.0 (2075) Set matter.0.controller.14388134951535934862.ElectricalSensor-2.ELECTRIC_POWER to 0 (ack = true)
2026-10-19 15:14:45.623  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/apparentCurrent changed to 0
2026-10-19 15:14:45.625  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/apparentPower changed to 0
2026-10-19 15:14:45.627  - debug: matter.0 (2075) handleChangedAttribute "14388134951535934862": Attribute undefined/2/0x0090/powerFactor changed to 0
2026-10-19 15:15:10.055  - info: host.smart instance system.adapter.dwd.0 in version "2.8.5" started with pid 6310
2026-10-19 15:15:12.694  - info: host.smart instance system.adapter.dwd.0 having pid 6310 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-10-19 15:15:32.152  - info: host.smart received SIGTERM
2026-10-19 15:15:32.159  - debug: matter.0 (2075) Send to GUI: {"command":"stopped"}
2026-10-19 15:15:32.152  - info: host.smart stopInstance system.adapter.admin.0 (force=false, process=true)
2026-10-19 15:15:32.152  - info: host.smart stopInstance system.adapter.influxdb.0 (force=false, process=true)
2026-10-19 15:15:32.153  - info: host.smart stopInstance system.adapter.javascript.0 (force=false, process=true)
2026-10-19 15:15:32.153  - info: host.smart stopInstance system.adapter.whatsapp-cmb.0 (force=false, process=true)
2026-10-19 15:15:32.153  - info: host.smart stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-10-19 15:15:32.154  - info: host.smart stopInstance system.adapter.alexa2.0 (force=false, process=true)
2026-10-19 15:15:32.154  - info: host.smart stopInstance system.adapter.cloud.0 (force=false, process=true)
2026-10-19 15:15:32.180  - info: host.smart stopInstance system.adapter.device-watcher.0 (force=false, process=true)
2026-10-19 15:15:32.181  - info: host.smart stopInstance system.adapter.feiertage.0 (force=false, process=false)
2026-10-19 15:15:32.181  - info: host.smart stopInstance canceled schedule system.adapter.feiertage.0
2026-10-19 15:15:32.181  - info: host.smart stopInstance system.adapter.fullybrowser.0 (force=false, process=true)
2026-10-19 15:15:32.181  - info: host.smart stopInstance system.adapter.hmip.0 (force=false, process=true)
2026-10-19 15:15:32.181  - info: host.smart stopInstance system.adapter.homeconnect.0 (force=false, process=true)
2026-10-19 15:15:32.182  - info: host.smart stopInstance system.adapter.hue.0 (force=false, process=true)
2026-10-19 15:15:32.182  - info: host.smart stopInstance system.adapter.ical.0 (force=false, process=false)
2026-10-19 15:15:32.182  - info: host.smart stopInstance canceled schedule system.adapter.ical.0
2026-10-19 15:15:32.182  - info: host.smart stopInstance system.adapter.modbus.0 (force=false, process=true)
2026-10-19 15:15:32.182  - info: host.smart stopInstance system.adapter.mqtt.0 (force=false, process=true)
2026-10-19 15:15:32.182  - info: host.smart stopInstance system.adapter.nuki.0 (force=false, process=true)
2026-10-19 15:15:32.183  - info: host.smart stopInstance system.adapter.shelly.0 (force=false, process=true)
2026-10-19 15:15:32.183  - info: host.smart stopInstance system.adapter.shelly.1 (force=false, process=true)
2026-10-19 15:15:32.183  - info: host.smart stopInstance system.adapter.sonoff.0 (force=false, process=true)
2026-10-19 15:15:32.183  - info: host.smart stopInstance system.adapter.sonos.0 (force=false, process=true)
2026-10-19 15:15:32.183  - info: host.smart stopInstance system.adapter.tr-064.0 (force=false, process=true)
2026-10-19 15:15:32.183  - info: host.smart stopInstance system.adapter.tuya.0 (force=false, process=true)
2026-10-19 15:15:32.183  - info: host.smart stopInstance system.adapter.uv-protect.0 (force=false, process=false)
2026-10-19 15:15:32.184  - info: host.smart stopInstance system.adapter.zigbee.0 (force=false, process=true)
2026-10-19 15:15:32.184  - info: host.smart stopInstance system.adapter.synology.0 (force=false, process=true)
2026-10-19 15:15:32.212  - info: host.smart stopInstance system.adapter.zendure-solarflow.0 (force=false, process=true)
2026-10-19 15:15:32.213  - info: host.smart stopInstance system.adapter.discovery.0 (force=false, process=true)
2026-10-19 15:15:32.213  - info: host.smart stopInstance system.adapter.sourceanalytix.0 (force=false, process=true)
2026-10-19 15:15:32.213  - info: host.smart stopInstance system.adapter.smart-eq.0 (force=false, process=true)
2026-10-19 15:15:32.213  - info: host.smart stopInstance system.adapter.web.0 (force=false, process=true)
2026-10-19 15:15:32.213  - info: host.smart stopInstance system.adapter.vis.0 (force=false, process=false)
2026-10-19 15:15:32.213  - info: host.smart stopInstance system.adapter.dwd.0 (force=false, process=false)
2026-10-19 15:15:32.213  - info: host.smart stopInstance canceled schedule system.adapter.dwd.0
2026-10-19 15:15:32.213  - info: host.smart stopInstance system.adapter.echarts.0 (force=false, process=true)
2026-10-19 15:15:32.214  - info: host.smart stopInstance system.adapter.energiefluss.0 (force=false, process=false)
2026-10-19 15:15:32.214  - info: host.smart stopInstance system.adapter.iot.0 (force=false, process=true)
2026-10-19 15:15:32.214  - info: host.smart stopInstance system.adapter.linux-control.0 (force=false, process=true)
2026-10-19 15:15:32.214  - info: host.smart stopInstance system.adapter.reolink.0 (force=false, process=false)
2026-10-19 15:15:32.214  - info: host.smart stopInstance system.adapter.statistics.0 (force=false, process=true)
2026-10-19 15:15:32.214  - info: host.smart stopInstance system.adapter.trashschedule.0 (force=false, process=true)
2026-10-19 15:15:32.214  - info: host.smart stopInstance system.adapter.upnp.0 (force=false, process=true)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.vis-canvas-gauges.0 (force=false, process=false)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.vis-players.0 (force=false, process=false)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.vis-plumb.0 (force=false, process=false)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.wled.0 (force=false, process=true)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.mytime.0 (force=false, process=true)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.vis-colorpicker.0 (force=false, process=false)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.mitsubishi-local-control.0 (force=false, process=true)
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-19 15:15:32.216  - info: host.smart stopInstance system.adapter.awtrix-ng.0 (force=false, process=true)
2026-10-19 15:15:32.216  - info: host.smart stopInstance system.adapter.awtrix-ng.1 (force=false, process=true)
2026-10-19 15:15:32.225  - info: host.smart stopInstance system.adapter.awtrix-ng.2 (force=false, process=true)
2026-10-19 15:15:32.159  - info: matter.0 (2075) 2026-10-19 15:15:32.159 NOTICE Runtime Shutting down
2026-10-19 15:15:32.166  - info: matter.0 (2075) Node "3138025706799876746" disconnected
2026-10-19 15:15:32.170  - info: matter.0 (2075) Node "2" disconnected
2026-10-19 15:15:32.172  - info: matter.0 (2075) Node "4" disconnected
2026-10-19 15:15:32.176  - info: matter.0 (2075) Node "5" disconnected
2026-10-19 15:15:32.181  - info: matter.0 (2075) Node "3" disconnected
2026-10-19 15:15:32.186  - info: matter.0 (2075) Node "14388134951535934862" disconnected
2026-10-19 15:15:32.189  - info: matter.0 (2075) Node "905838670972218924" disconnected
2026-10-19 15:15:32.192  - info: matter.0 (2075) Node "1" disconnected
2026-10-19 15:15:32.196  - info: matter.0 (2075) Stopping Controller...
2026-10-19 15:15:32.198  - info: matter.0 (2075) 2026-10-19 15:15:32.198 NOTICE Node controller going offline
2026-10-19 15:15:32.203  - debug: matter.0 (2075) 2026-10-19 15:15:32.203 INFO ClientNode controller.@1:2b8c81c11dd9ca8a going offline
2026-10-19 15:15:32.206  - debug: matter.0 (2075) 2026-10-19 15:15:32.206 INFO ClientNode controller.@1:2 going offline
2026-10-19 15:15:32.206  - debug: matter.0 (2075) 2026-10-19 15:15:32.206 INFO ClientNode controller.@1:4 going offline
2026-10-19 15:15:32.207  - debug: matter.0 (2075) 2026-10-19 15:15:32.207 INFO ClientNode controller.@1:5 going offline
2026-10-19 15:15:32.207  - debug: matter.0 (2075) 2026-10-19 15:15:32.207 INFO ClientNode controller.@1:3 going offline
2026-10-19 15:15:32.209  - debug: matter.0 (2075) 2026-10-19 15:15:32.209 INFO ClientNode controller.@1:c7acec81beae7d8e going offline
2026-10-19 15:15:32.210  - debug: matter.0 (2075) 2026-10-19 15:15:32.210 INFO ClientNode controller.@1:c922f78cf1c6e2c going offline
2026-10-19 15:15:32.210  - debug: matter.0 (2075) 2026-10-19 15:15:32.210 INFO ClientNode controller.@1:1 going offline
2026-10-19 15:15:32.212  - debug: matter.0 (2075) 2026-10-19 15:15:32.212 INFO ClientNode controller.@1:2b8c81c11dd9ca8a is offline
2026-10-19 15:15:32.213  - debug: matter.0 (2075) 2026-10-19 15:15:32.213 INFO ClientNode controller.@1:2 is offline
2026-10-19 15:15:32.213  - debug: matter.0 (2075) 2026-10-19 15:15:32.213 INFO ClientNode controller.@1:4 is offline
2026-10-19 15:15:32.214  - debug: matter.0 (2075) 2026-10-19 15:15:32.214 INFO ClientNode controller.@1:5 is offline
2026-10-19 15:15:32.215  - debug: matter.0 (2075) 2026-10-19 15:15:32.215 INFO ClientNode controller.@1:3 is offline
2026-10-19 15:15:32.215  - debug: matter.0 (2075) 2026-10-19 15:15:32.215 INFO ClientNode controller.@1:c7acec81beae7d8e is offline
2026-10-19 15:15:32.216  - debug: matter.0 (2075) 2026-10-19 15:15:32.216 INFO ClientNode controller.@1:c922f78cf1c6e2c is offline
2026-10-19 15:15:32.216  - debug: matter.0 (2075) 2026-10-19 15:15:32.216 INFO ClientNode controller.@1:1 is offline
2026-10-19 15:15:32.387  - info: host.smart stopInstance system.adapter.admin.0 send kill signal
2026-10-19 15:15:32.405  - debug: matter.0 (2075) 2026-10-19 15:15:32.405 INFO Transaction ◦offline#2eb locked controller.generalDiagnostics.state
2026-10-19 15:15:32.419  - info: matter.0 (2075) Got terminate signal TERMINATE_YOURSELF
2026-10-19 15:15:32.427  - info: host.smart stopInstance system.adapter.javascript.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.whatsapp-cmb.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.backitup.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.alexa2.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.cloud.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.device-watcher.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.fullybrowser.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.hmip.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.homeconnect.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.hue.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.modbus.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.mqtt.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.nuki.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.shelly.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.shelly.1 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.sonoff.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.sonos.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.tr-064.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.tuya.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.zigbee.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.synology.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.zendure-solarflow.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.discovery.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.sourceanalytix.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.smart-eq.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.web.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.echarts.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.iot.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.linux-control.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.statistics.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.trashschedule.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.upnp.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.wled.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.mytime.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.mitsubishi-local-control.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.awtrix-ng.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.awtrix-ng.1 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.awtrix-ng.2 send kill signal
2026-10-19 15:15:32.563  - warn: host.smart instance system.adapter.javascript.0 terminated due to SIGTERM
2026-10-19 15:15:32.563  - info: host.smart instance system.adapter.javascript.0 terminated with code null ()
2026-10-19 15:15:32.604  - debug: matter.0 (2075) 2026-10-19 15:15:32.604 INFO Transaction ◦offline#2eb committed and unlocked 1 resource
2026-10-19 15:15:32.606  - debug: matter.0 (2075) 2026-10-19 15:15:32.606 INFO MdnsAdvertisement Unpublishing kind: operational service: mdns:C1124F59EBABAC14-E3CF4773CA77CE57._matter._tcp.local time: 12h 30m 7s
2026-10-19 15:15:32.610  - debug: matter.0 (2075) 2026-10-19 15:15:32.610 INFO Session @1:2b8c81c11dd9ca8a•65bd Session ended
2026-10-19 15:15:32.610  - debug: matter.0 (2075) 2026-10-19 15:15:32.610 INFO Session @1:2•65be Session ended
2026-10-19 15:15:32.610  - debug: matter.0 (2075) 2026-10-19 15:15:32.610 INFO Session @1:4•65bf Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:3•65c1 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:c922f78cf1c6e2c•65c3 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:c7acec81beae7d8e•65c2 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:1•65c4 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:5•65c0 Session ended
2026-10-19 15:15:32.618  - info: matter.0 (2075) 2026-10-19 15:15:32.618 NOTICE Node controller is offline
2026-10-19 15:15:32.656  - debug: matter.0 (2075) 2026-10-19 15:15:32.656 INFO ServerNodeStore Closed controller storage location: /opt/iobroker/iobroker-data/matter.0/controller driver: iobroker locks: 0
2026-10-19 15:15:32.740  - info: matter.0 (2075) terminating
2026-10-19 15:15:32.741  - debug: matter.0 (2075) Plugin sentry destroyed
2026-10-19 15:15:32.741  - info: matter.0 (2075) Terminated (NO_ERROR): Without reason
2026-10-19 15:15:32.931  - info: host.smart instance system.adapter.synology.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:32.979  - info: host.smart instance system.adapter.mitsubishi-local-control.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.014  - info: host.smart instance system.adapter.sourceanalytix.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.137  - info: host.smart instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.298  - info: host.smart instance system.adapter.alexa2.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.317  - info: host.smart instance system.adapter.cloud.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.389  - info: host.smart stopInstance timeout system.adapter.admin.0 killing pid 6263
2026-10-19 15:15:33.421  - info: host.smart instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.422  - info: host.smart instance system.adapter.upnp.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.445  - info: host.smart instance system.adapter.mytime.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.446  - info: host.smart instance system.adapter.hmip.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:15:33.773  - info: host.smart stopInstance timeout system.adapter.whatsapp-cmb.0 killing pid 1320
2026-10-19 15:15:33.779  - info: host.smart stopInstance timeout system.adapter.fullybrowser.0 killing pid 1438
2026-10-19 15:15:33.780  - info: host.smart stopInstance timeout system.adapter.homeconnect.0 killing pid 1471
2026-10-19 15:15:33.780  - info: host.smart stopInstance timeout system.adapter.hue.0 killing pid 1488
2026-10-19 15:15:33.783  - info: host.smart stopInstance timeout system.adapter.modbus.0 killing pid 1522
2026-10-19 15:15:33.783  - info: host.smart stopInstance timeout system.adapter.mqtt.0 killing pid 1539
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.shelly.0 killing pid 1572
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.shelly.1 killing pid 1589
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.sonoff.0 killing pid 1606
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.web.0 killing pid 1774
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.echarts.0 killing pid 1824
2026-10-19 15:15:33.785  - info: host.smart stopInstance timeout system.adapter.awtrix-ng.0 killing pid 2083
2026-10-19 15:15:33.785  - info: host.smart stopInstance timeout system.adapter.awtrix-ng.1 killing pid 2108
2026-10-19 15:15:33.785  - info: host.smart stopInstance timeout system.adapter.awtrix-ng.2 killing pid 2125

Dann warte ich aufs "nächste Mal" und mache dann das hier:
check

ls -la --time-style=full-iso /opt/iobroker/iobroker-data/matter.0/ota/
cat /opt/iobroker/iobroker-data/matter.0/ota/matter.pid

Bluefox

@darkblu Nicht schlimm, das sagt auch so schon etwas. Wenn 3751 nicht mehr existiert, gehört die aktuelle Sperre in ota/ vermutlich schon wieder zu einem Prozess, den es nicht mehr gibt. Bitte schau, ob und mit welcher PID matter.0 gerade läuft, und vergleich das mit der Datei:

ps -ef | grep "[m]atter.0"
ls -la --time-style=full-iso /opt/iobroker/iobroker-data/matter.0/ota/
cat /opt/iobroker/iobroker-data/matter.0/ota/matter.pid

Steht in der Datei eine andere PID als bei der laufenden Instanz, ist die Sperre wieder verwaist. Dann sollte im Log beim letzten Start auch wieder storage-lock auftauchen.

Im Log vom 19.10. sieht man um 15:15:32 host.smart received SIGTERM. Da wurde also der ganze ioBroker gestoppt, kurz bevor die alten Sperrdateien um 15:20 entstanden sind. War das ein Reboot vom Pi? Das zeigt:

last -x reboot shutdown | head -20

Leider hat head -200 die Ausgabe genau an der spannenden Stelle abgeschnitten. Bitte noch einmal ohne die vielen Debug-Zeilen:

zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0|SIGTERM|kill|exit" | grep -vE "handleChangedAttribute|Set matter\.0" | head -100

Mich interessiert, ob matter.0 (2075) beim Herunterfahren sauber mit "Terminated" beendet wurde und mit welcher PID sie danach wieder gestartet ist. Ich vermute, dass die Sperre beim Stoppen bzw. Reboot liegen bleibt.

darkblu

@Bluefox said:

und vergleich das mit der Datei:

ps -ef | grep "[m]atter.0"
ls -la --time-style=full-iso /opt/iobroker/iobroker-data/matter.0/ota/
cat /opt/iobroker/iobroker-data/matter.0/ota/matter.pid

die Ausgabe sagt: 2071 und in der .pid steht auch 2071

bevor die alten Sperrdateien um 15:20 entstanden sind. War das ein Reboot vom Pi? Das zeigt:
last -x reboot shutdown | head -20

das zeigt leider nur das hier:

-bash: last: command not found

...Bitte noch einmal ohne die vielen Debug-Zeilen:

zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0|SIGTERM|kill|exit" | grep -vE "handleChangedAttribute|Set matter\.0" | head -100

hier die erneute Ausgabe:

dirk@smart:~ $ zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0|SIGTERM|kill|exit" | grep -vE "handleChangedAttribute|Set matter\.0" | head -100
2026-10-19 15:13:21.520  - info: host.smart stopInstance system.adapter.admin.0 send kill signal
2026-10-19 15:13:55.716  - info: host.smart stopInstance system.adapter.admin.0 send kill signal
2026-10-19 15:15:32.152  - info: host.smart received SIGTERM
2026-10-19 15:15:32.159  - debug: matter.0 (2075) Send to GUI: {"command":"stopped"}
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-19 15:15:32.159  - info: matter.0 (2075) 2026-10-19 15:15:32.159 NOTICE Runtime Shutting down
2026-10-19 15:15:32.166  - info: matter.0 (2075) Node "3138025706799876746" disconnected
2026-10-19 15:15:32.170  - info: matter.0 (2075) Node "2" disconnected
2026-10-19 15:15:32.172  - info: matter.0 (2075) Node "4" disconnected
2026-10-19 15:15:32.176  - info: matter.0 (2075) Node "5" disconnected
2026-10-19 15:15:32.181  - info: matter.0 (2075) Node "3" disconnected
2026-10-19 15:15:32.186  - info: matter.0 (2075) Node "14388134951535934862" disconnected
2026-10-19 15:15:32.189  - info: matter.0 (2075) Node "905838670972218924" disconnected
2026-10-19 15:15:32.192  - info: matter.0 (2075) Node "1" disconnected
2026-10-19 15:15:32.196  - info: matter.0 (2075) Stopping Controller...
2026-10-19 15:15:32.198  - info: matter.0 (2075) 2026-10-19 15:15:32.198 NOTICE Node controller going offline
2026-10-19 15:15:32.203  - debug: matter.0 (2075) 2026-10-19 15:15:32.203 INFO ClientNode controller.@1:2b8c81c11dd9ca8a going offline
2026-10-19 15:15:32.206  - debug: matter.0 (2075) 2026-10-19 15:15:32.206 INFO ClientNode controller.@1:2 going offline
2026-10-19 15:15:32.206  - debug: matter.0 (2075) 2026-10-19 15:15:32.206 INFO ClientNode controller.@1:4 going offline
2026-10-19 15:15:32.207  - debug: matter.0 (2075) 2026-10-19 15:15:32.207 INFO ClientNode controller.@1:5 going offline
2026-10-19 15:15:32.207  - debug: matter.0 (2075) 2026-10-19 15:15:32.207 INFO ClientNode controller.@1:3 going offline
2026-10-19 15:15:32.209  - debug: matter.0 (2075) 2026-10-19 15:15:32.209 INFO ClientNode controller.@1:c7acec81beae7d8e going offline
2026-10-19 15:15:32.210  - debug: matter.0 (2075) 2026-10-19 15:15:32.210 INFO ClientNode controller.@1:c922f78cf1c6e2c going offline
2026-10-19 15:15:32.210  - debug: matter.0 (2075) 2026-10-19 15:15:32.210 INFO ClientNode controller.@1:1 going offline
2026-10-19 15:15:32.212  - debug: matter.0 (2075) 2026-10-19 15:15:32.212 INFO ClientNode controller.@1:2b8c81c11dd9ca8a is offline
2026-10-19 15:15:32.213  - debug: matter.0 (2075) 2026-10-19 15:15:32.213 INFO ClientNode controller.@1:2 is offline
2026-10-19 15:15:32.213  - debug: matter.0 (2075) 2026-10-19 15:15:32.213 INFO ClientNode controller.@1:4 is offline
2026-10-19 15:15:32.214  - debug: matter.0 (2075) 2026-10-19 15:15:32.214 INFO ClientNode controller.@1:5 is offline
2026-10-19 15:15:32.215  - debug: matter.0 (2075) 2026-10-19 15:15:32.215 INFO ClientNode controller.@1:3 is offline
2026-10-19 15:15:32.215  - debug: matter.0 (2075) 2026-10-19 15:15:32.215 INFO ClientNode controller.@1:c7acec81beae7d8e is offline
2026-10-19 15:15:32.216  - debug: matter.0 (2075) 2026-10-19 15:15:32.216 INFO ClientNode controller.@1:c922f78cf1c6e2c is offline
2026-10-19 15:15:32.216  - debug: matter.0 (2075) 2026-10-19 15:15:32.216 INFO ClientNode controller.@1:1 is offline
2026-10-19 15:15:32.387  - info: host.smart stopInstance system.adapter.admin.0 send kill signal
2026-10-19 15:15:32.405  - debug: matter.0 (2075) 2026-10-19 15:15:32.405 INFO Transaction ◦offline#2eb locked controller.generalDiagnostics.state
2026-10-19 15:15:32.419  - info: matter.0 (2075) Got terminate signal TERMINATE_YOURSELF
2026-10-19 15:15:32.427  - info: host.smart stopInstance system.adapter.javascript.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.whatsapp-cmb.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.backitup.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.alexa2.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.cloud.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.device-watcher.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.fullybrowser.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.hmip.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.homeconnect.0 send kill signal
2026-10-19 15:15:32.431  - info: host.smart stopInstance system.adapter.hue.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.modbus.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.mqtt.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.nuki.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.shelly.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.shelly.1 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.sonoff.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.sonos.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.tr-064.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.tuya.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.zigbee.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.synology.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.zendure-solarflow.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.discovery.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.sourceanalytix.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.smart-eq.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.web.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.echarts.0 send kill signal
2026-10-19 15:15:32.432  - info: host.smart stopInstance system.adapter.iot.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.linux-control.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.statistics.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.trashschedule.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.upnp.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.wled.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.mytime.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.mitsubishi-local-control.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.awtrix-ng.0 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.awtrix-ng.1 send kill signal
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.awtrix-ng.2 send kill signal
2026-10-19 15:15:32.563  - warn: host.smart instance system.adapter.javascript.0 terminated due to SIGTERM
2026-10-19 15:15:32.604  - debug: matter.0 (2075) 2026-10-19 15:15:32.604 INFO Transaction ◦offline#2eb committed and unlocked 1 resource
2026-10-19 15:15:32.606  - debug: matter.0 (2075) 2026-10-19 15:15:32.606 INFO MdnsAdvertisement Unpublishing kind: operational service: mdns:C1124F59EBABAC14-E3CF4773CA77CE57._matter._tcp.local time: 12h 30m 7s
2026-10-19 15:15:32.610  - debug: matter.0 (2075) 2026-10-19 15:15:32.610 INFO Session @1:2b8c81c11dd9ca8a•65bd Session ended
2026-10-19 15:15:32.610  - debug: matter.0 (2075) 2026-10-19 15:15:32.610 INFO Session @1:2•65be Session ended
2026-10-19 15:15:32.610  - debug: matter.0 (2075) 2026-10-19 15:15:32.610 INFO Session @1:4•65bf Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:3•65c1 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:c922f78cf1c6e2c•65c3 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:c7acec81beae7d8e•65c2 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:1•65c4 Session ended
2026-10-19 15:15:32.611  - debug: matter.0 (2075) 2026-10-19 15:15:32.611 INFO Session @1:5•65c0 Session ended
2026-10-19 15:15:32.618  - info: matter.0 (2075) 2026-10-19 15:15:32.618 NOTICE Node controller is offline
2026-10-19 15:15:32.656  - debug: matter.0 (2075) 2026-10-19 15:15:32.656 INFO ServerNodeStore Closed controller storage location: /opt/iobroker/iobroker-data/matter.0/controller driver: iobroker locks: 0
2026-10-19 15:15:32.740  - info: matter.0 (2075) terminating
2026-10-19 15:15:32.741  - debug: matter.0 (2075) Plugin sentry destroyed
2026-10-19 15:15:32.741  - info: matter.0 (2075) Terminated (NO_ERROR): Without reason
2026-10-19 15:15:33.389  - info: host.smart stopInstance timeout system.adapter.admin.0 killing pid 6263
2026-10-19 15:15:33.773  - info: host.smart stopInstance timeout system.adapter.whatsapp-cmb.0 killing pid 1320
2026-10-19 15:15:33.779  - info: host.smart stopInstance timeout system.adapter.fullybrowser.0 killing pid 1438
2026-10-19 15:15:33.780  - info: host.smart stopInstance timeout system.adapter.homeconnect.0 killing pid 1471
2026-10-19 15:15:33.780  - info: host.smart stopInstance timeout system.adapter.hue.0 killing pid 1488
2026-10-19 15:15:33.783  - info: host.smart stopInstance timeout system.adapter.modbus.0 killing pid 1522
2026-10-19 15:15:33.783  - info: host.smart stopInstance timeout system.adapter.mqtt.0 killing pid 1539
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.shelly.0 killing pid 1572
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.shelly.1 killing pid 1589
2026-10-19 15:15:33.784  - info: host.smart stopInstance timeout system.adapter.sonoff.0 killing pid 1606

Ich hoffe das hilft und vielen Dank.

Kann das sein, das dass mit klick dieses Buttons in Zusammenhang steht ?
Ich werde den morgen mal (wieder) klicken und beobachten ob dann irgendwann wieder steht "keine Geräte gefunden"

Bluefox

@darkblu Danke. Im Moment ist also alles in Ordnung: 2071 läuft, und die Sperre gehört zu genau diesem Prozess.

Im Log sieht man gut, was beim Herunterfahren am 19.10. passiert ist. Um 15:15:32.419 bekommt matter.0 (2075) das TERMINATE_YOURSELF, und nur ein paar Millisekunden später schickt der Host an alle Adapter send kill signal. matter.0 war da noch beim Herunterfahren vom Controller (Transaction ... locked). Ich vermute, dass der Prozess hart beendet wurde, bevor er die Sperre in ota/ aufräumen konnte.

Dazu kommt wahrscheinlich noch etwas: Nach einem Reboot vom Pi bekommen die Prozesse wieder ähnlich niedrige PIDs (2075, 2071 ...). Bleibt eine alte matter.pid liegen und gehört die PID darin zufällig gerade zu einem anderen Prozess, hält matter.js die Sperre vermutlich für noch gültig. Das würde erklären, warum es nur manchmal passiert.

last ist bei dir nicht installiert. Die Reboots siehst du auch so:

journalctl --list-boots

Und bitte noch die Zeilen, wie matter.0 nach dem Stoppen wieder gestartet ist:

zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0 \(2075\) Terminated|system\.adapter\.matter\.0|storage-lock|locked by" | head -50

Mich interessiert, ob für 2075 noch ein "Terminated" kommt und mit welcher PID matter.0 danach gestartet ist. Das kommt dann auch ins Issue https://github.com/ioBroker/ioBroker.matter/issues/898, damit @apollon77 es sich in matter.js anschauen kann.

darkblu

@Bluefox said:

Und bitte noch die Zeilen, wie matter.0 nach dem Stoppen wieder gestartet ist:
zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0 \(2075\) Terminated|system\.adapter\.matter\.0|storage-lock|locked by" | head -50
Mich interessiert, ob für 2075 noch ein "Terminated" kommt und mit welcher PID matter.0 danach gestartet ist. Das kommt dann auch ins Issue https://github.com/ioBroker/ioBroker.matter/issues/898, damit @apollon77 es sich in matter.js anschauen kann.

hier das Ergebnis:

2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-19 15:15:32.741  - info: matter.0 (2075) Terminated (NO_ERROR): Without reason
2026-10-19 15:15:35.020  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:20:16.716  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2087

Bluefox

@darkblu Danke, das ist eindeutig: 2075 hat sich um 15:15:32.741 sauber mit "Terminated (NO_ERROR)" beendet und der Host meldet code 0. Meine Vermutung mit dem harten Kill beim Herunterfahren stimmt für diesen Stopp also nicht.

Die Sperrdateien von 15:20 gehören dann zum neuen Prozess 2087, der um 15:20:16 gestartet ist. Spannend ist also, wie 2087 bzw. die Prozesse danach beendet wurden. Bitte schau einmal über alle Logs, wann matter.0 gestartet und gestoppt wurde:

zgrep -h -E "system\.adapter\.matter\.0|matter\.0 \([0-9]+\) Terminated|received SIGTERM|storage-lock|locked by" /opt/iobroker/log/iobroker.2026-10-*.log* | sort | head -150

Und noch die Reboots:

journalctl --list-boots

Ich suche einen Start ohne ein passendes "Terminated" davor, also einen Prozess, der ohne Aufräumen weg war, zum Beispiel durch Stromausfall, harten Reboot oder einen Absturz.

Wenn wieder "Keine Geräte gefunden" kommt, bitte vor dem Neustart gleich die drei Befehle von vorhin ausführen (ps, ls, cat matter.pid) und die Ausgabe posten. Dann sehen wir direkt, welche PID in der Sperre steht.

darkblu

sodele, hier Nummer eins:

dirk@smart:~ $ zgrep -h -E "system\.adapter\.matter\.0|matter\.0 \([0-9]+\) Terminated|received SIGTERM|storage-lock|locked by" /opt/iobroker/log/iobroker.2026-10-*.log* | sort | head -150
2026-10-16 02:44:25.593  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2290
2026-10-16 02:44:32.311  - warn: matter.0 (2290) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-10-16 02:44:32.884  - error: host.smart instance system.adapter.matter.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-10-16 02:44:32.884  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-16 02:45:03.397  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2585
2026-10-16 12:17:20.556  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2213
2026-10-16 12:18:52.077  - warn: matter.0 (2213) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-10-16 12:18:54.024  - error: host.smart instance system.adapter.matter.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-10-16 12:18:54.024  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-16 12:19:56.639  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2598
2026-10-16 12:37:02.986  - info: host.smart received SIGTERM
2026-10-16 12:37:03.044  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-16 12:37:03.293  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-16 12:37:05.612  - info: matter.0 (2598) Terminated (NO_ERROR): Without reason
2026-10-16 12:37:06.172  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-16 12:41:53.192  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2059
2026-10-17 12:20:45.625  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2257
2026-10-17 12:26:04.699  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2389
2026-10-17 12:26:13.075  - warn: matter.0 (2389) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-10-17 12:26:13.658  - error: host.smart instance system.adapter.matter.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-10-17 12:26:13.658  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-17 12:26:44.167  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2465
2026-10-17 14:17:09.408  - info: host.smart received SIGTERM
2026-10-17 14:17:09.423  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-17 14:17:09.649  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-17 14:17:12.195  - info: matter.0 (2465) Terminated (NO_ERROR): Without reason
2026-10-17 14:17:12.847  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-17 14:20:31.959  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 4145
2026-10-18 12:23:32.750  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2266
2026-10-18 12:24:58.955  - warn: matter.0 (2266) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-10-18 12:24:59.671  - error: host.smart instance system.adapter.matter.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-10-18 12:24:59.671  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-18 12:25:30.732  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2632
2026-10-18 14:58:51.206  - info: matter.0 (2632) Terminated (NO_ERROR): Without reason
2026-10-18 14:58:51.836  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-18 14:58:51.837  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-18 14:59:22.329  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 3637
2026-10-18 15:29:47.786  - info: matter.0 (3637) Terminated (NO_ERROR): Without reason
2026-10-18 15:29:48.347  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-18 15:29:48.348  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-18 15:30:18.849  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 3849
2026-10-19 02:45:15.023  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2075
2026-10-19 15:15:32.152  - info: host.smart received SIGTERM
2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-19 15:15:32.741  - info: matter.0 (2075) Terminated (NO_ERROR): Without reason
2026-10-19 15:15:35.020  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:20:16.716  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2087
2026-10-20 13:08:30.346  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2279
2026-10-20 13:08:36.751  - warn: matter.0 (2279) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-10-20 13:08:37.968  - error: host.smart instance system.adapter.matter.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-10-20 13:08:37.968  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-20 13:09:15.647  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2557
2026-10-20 15:36:46.915  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-20 15:36:46.920  - info: matter.0 (2557) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-10-20 15:36:46.960  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-20 15:36:47.481  - info: host.smart instance system.adapter.matter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-10-20 15:36:50.579  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 3405
2026-10-20 15:44:25.187  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-20 15:44:25.194  - info: matter.0 (3405) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-10-20 15:44:25.248  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-20 15:44:25.758  - info: host.smart instance system.adapter.matter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-10-20 15:44:28.770  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 3445
2026-10-20 16:17:19.467  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-20 16:17:19.467  - info: host.smart "system.adapter.matter.0" disabled
2026-10-20 16:17:19.473  - info: matter.0 (3445) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-10-20 16:17:19.514  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-20 16:17:20.035  - info: host.smart instance system.adapter.matter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-10-20 16:18:08.098  - info: host.smart "system.adapter.matter.0" enabled
2026-10-20 16:18:08.591  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 3751
2026-10-21 13:14:04.137  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2290
2026-10-21 13:14:10.889  - warn: matter.0 (2290) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-10-21 13:14:11.489  - error: host.smart instance system.adapter.matter.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-10-21 13:14:11.490  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-21 13:14:42.015  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2589
2026-10-21 15:31:00.385  - info: host.smart received SIGTERM
2026-10-21 15:31:00.400  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-21 15:31:00.688  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-21 15:31:03.129  - info: matter.0 (2589) Terminated (NO_ERROR): Without reason
2026-10-21 15:31:03.689  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-21 15:35:50.783  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2071
2026-10-22 13:15:57.219  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2346
2026-10-22 13:16:02.645  - warn: matter.0 (2346) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-10-22 13:16:03.210  - error: host.smart instance system.adapter.matter.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-10-22 13:16:03.210  - info: host.smart Restart adapter system.adapter.matter.0 because enabled
2026-10-22 13:16:33.843  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2500
                      Caused by: [storage-lock] Storage is locked by another process (pid 2087)
                      Caused by: [storage-lock] Storage is locked by another process (pid 2087)
                      Caused by: [storage-lock] Storage is locked by another process (pid 2087)
                      Caused by: [storage-lock] Storage is locked by another process (pid 2087)
                      Caused by: [storage-lock] Storage is locked by another process (pid 2087)
                      Caused by: [storage-lock] Storage is locked by another process (pid 2087)
                      Caused by: [storage-lock] Storage is locked by another process (pid 2612)
                      Caused by: [storage-lock] Storage is locked by another process (pid 2612)

und Nummer 2:

 0 1334c797c3a145c3925ab89d133a55b6 Thu 2026-10-22 13:00:03 CEST Thu 2026-10-22 14:17:01 CEST

mehr gibt es nicht aus 2026

Allerdings meint Gemini rausgefunden zu haben, das ich ein Neustart Problem habe, wahrscheinlich das Netzteil.

Das würde es ja dann erklären ? Harter Abbruch und dann ist halt keine Zeit die PID zu beenden oder zu löschen.
Das werde ich jetzt ein paar Tage beobachten und es dann mal mit einem neuen Netzteil versuchen.

Thomas Braun

@darkblu sagte:

wahrscheinlich das Netzteil.

Ich kann da wirklich nur das originale Raspberry-Netzteil empfehlen. Alles andere ist nicht so gut geeignet, von zweck entfremdeten Ladegeräten ganz zu schweigen.

darkblu

und genau das habe ich, ist jetzt ca. 2 Jahre alt.
Ich werde es beobachten ob es überhaupt zu Neustarts kommt.

darkblu

@Bluefox said:

Damit wir das nächste Mal direkt sehen, was passiert: Wenn es wieder auftritt, lösch die Dateien erst nach diesem Befehl:
ls -la --time-style=full-iso /opt/iobroker/iobroker-data/matter.0/ota/
cat /opt/iobroker/iobroker-data/matter.0/ota/matter.pid
Dann suchen wir im Log nach genau dieser Uhrzeit und PID.

Es ist wieder passiert:

dirk@smart:~ $ ls -la --time-style=full-iso /opt/iobroker/iobroker-data/matter.0/ota/
cat /opt/iobroker/iobroker-data/matter.0/ota/matter.pid
total 200
drwxrwxr-x+ 2 iobroker iobroker   4096 2026-10-23 13:15:49.957617898 +0200 .
drwxrwxr-x+ 4 iobroker iobroker 188416 2026-10-23 16:55:48.634515466 +0200 ..
-rw-rwxr--+ 1 iobroker iobroker     38 2026-10-23 13:15:49.961617915 +0200 driver.json
-rw-rw-r--+ 1 iobroker iobroker      0 2026-10-23 13:15:49.957617898 +0200 matter.lock
-rw-rw-r--+ 1 iobroker iobroker     21 2026-10-23 13:15:49.961617915 +0200 matter.pid
2090 5149aee385fbd2dc

Ich weiss jetzt auch zuverlässig wann und wie es passiert, das Netzteil ist hinüber und es kommt zum harten Neustart wegen Spannungsabfall. Neues Netzteil ist bestellt.
Dann werden die Dateien eben nicht ordnungsgemäß entfernt und beim Neustart liegen die dann da noch und somit steigt der Matter Adapter dann aus, bzw nimmt seinen Dienst eben nicht auf.

bei dem hier:

zgrep "2026-10-19 15:[12]" /opt/iobroker/log/iobroker.2026-10-19.log* | grep -E "matter\.0 \(2075\) Terminated|system\.adapter\.matter\.0|storage-lock|locked by" | head -50

kommt das:

2026-10-19 15:15:32.215  - info: host.smart stopInstance system.adapter.matter.0 (force=false, process=true)
2026-10-19 15:15:32.433  - info: host.smart stopInstance system.adapter.matter.0 send kill signal
2026-10-19 15:15:32.741  - info: matter.0 (2075) Terminated (NO_ERROR): Without reason
2026-10-19 15:15:35.020  - info: host.smart instance system.adapter.matter.0 terminated with code 0 (NO_ERROR)
2026-10-19 15:20:16.716  - info: host.smart instance system.adapter.matter.0 in version "1.3.1" started with pid 2087

und in der .pid Datei steht 2090.

und danach sind die Geräte wieder da:

iob stop matter.0
rm /opt/iobroker/iobroker-data/matter.0/ota/matter.lock /opt/iobroker/iobroker-data/matter.0/ota/matter.pid
iob start matter.0

Community Forum

NEWS

Matter (Adapter) Problem

Support us

468

33.1k

84.2k

1.4m