wichtiges UPDATE für controller 7.2.2 im stable

[icebear]

Nach einem Stromausfall funktionierte meine Markise nicht mehr die über Matter und Alexa (Echo Show 11) eingebunden war nicht mehr.

Im Matter adapter unter Controller waren die Geräte auch nicht mehr vorhanden.

Ich hab dann in Alexa einen neuen Pairing-Code erzeugt und wollte die wieder hinzufügen, dabei bekomme ich immer wieder die folgenden Fehler:

Error while handling command "controllerDiscovery" for controller: [implementation] Controller instance not yet started. Please call start() first. at CommissioningController.#assertControllerIsStarted (/opt/iobroker/node_modules/@project-chip/matter.js/src/CommissioningController.ts:361:19) at CommissioningController.get node [as node] (/opt/iobroker/node_modules/@project-chip/matter.js/src/CommissioningController.ts:328:21) at CommissioningController.discoverCommissionableDevices (/opt/iobroker/node_modules/@project-chip/matter.js/src/CommissioningController.ts:873:18) at Controller.#discovery (/opt/iobroker/node_modules/iobroker.matter/src/matter/ControllerNode.ts:650:14) at processTicksAndRejections (node:internal/process/task_queues:103:5) at Controller.handleCommand (/opt/iobroker/node_modules/iobroker.matter/src/matter/ControllerNode.ts:165:21) at MatterAdapter.handleControllerCommand (/opt/iobroker/node_modules/iobroker.matter/src/main.ts:258:36) at MatterAdapter.#onMessage (/opt/iobroker/node_modules/iobroker.matter/src/main.ts:353:13)

Was kann ich tun, ausser das Gerät auf Werkseinstellungen zurückzusetzten und alles wieder neu einzurichten?

[Thomas Braun]

@icebear

Vielleicht hat dir der Stromausfall die Konfig-Datei zerschossen. Installier den Adapter nochmal neu drüber.

[icebear]

@Thomas-Braun sagte:

Installier den Adapter nochmal neu drüber.

Hab ich getan.

Nach der Installation ist der Adapter auch grün, ohne Fehlemeldung. Die Konfig, sieht glaub ich auch gut aus. (Ist ja wie vorher und da hat der einwandfrei funktioniert)

Aber sobald ich den Controller von 'Off' auf 'On' stelle geht der Adapter in einen restart-loop und ich bekomme die Fehlermeldungen:

host.iobroker
2026-07-17 06:55:51.342	info	Restart adapter system.adapter.matter.0 because enabled

host.iobroker
2026-07-17 06:55:51.342	error	instance system.adapter.matter.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.iobroker
2026-07-17 06:55:51.342	error	Caught by controller[0]: at Construction2.#invokeInitializer (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:575:40)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at initializeDeferred (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:294:99)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at ClientNode.[construct] (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1096:21)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/node/ClientNode.ts:107:31)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1061:38)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at Behaviors.initialize (/opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:271:41)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at LocalActorContext.act (/opt/iobroker/node_modules/@matter/node/src/behavior/context/server/LocalActorContext.ts:62:22)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at initializeBehaviors (/opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:246:40)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at Function.all (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:752:25)

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: at /opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:253:27

host.iobroker
2026-07-17 06:55:51.341	error	Caught by controller[0]: AggregateError: Behaviors have errors

host.iobroker
2026-07-17 06:55:51.340	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

matter.0
2026-07-17 06:55:50.508	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

matter.0
2026-07-17 06:55:50.503	info	terminating

matter.0
2026-07-17 06:55:50.498	info	Stopping Controller...

matter.0
2026-07-17 06:55:50.481	error	Failed to start the controller: [crashed-dependency] MatterController unavailable due to initialization error at Construction2.#crashedError (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:597:42) at handleRejection (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:330:74) Caused by: [endpoint-behaviors] Behaviors have errors at /opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:253:27 at all (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:752:25) at /opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:742:17 Cause #0: [behavior-initialization] Error initializing controller.ota-provider.otaSoftwareUpdateProvider at crash (/opt/iobroker/node_modules/@matter/node/src/behavior/internal/BehaviorBacking.ts:94:30) at /opt/iobroker/node_modules/@matter/general/src/util/Promises.ts:199:38 Caused by: [crashed-dependency] controller.ota-provider.softwareupdates initialization failed at Object.assertActive (/opt/iobroker/node_modules/@matter/general/src/util/Lifecycle.ts:48:23) at Construction2.assert (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:303:23) at /opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:382:42 at OtaSoftwareUpdateProviderServer.initialize (/opt/iobroker/node_modules/@matter/node/src/behaviors/ota-software-update-provider/OtaSoftwareUpdateProviderServer.ts:90:9) Cause #1: [behavior-initialization] Error initializing controller.ota-provider.softwareupdates at crash (/opt/iobroker/node_modules/@matter/node/src/behavior/internal/BehaviorBacking.ts:94:30) at /opt/iobroker/node_modules/@matter/general/src/util/Promises.ts:199:38 Caused by: [crashed-dependency] DclOtaUpdateService unavailable due to initialization error at Construction2.#crashedError (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:597:42) at handleRejection (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:330:74) Caused by: [storage-lock] Storage is locked by another process (pid 1531) at acquireLock (/opt/iobroker/node_modules/@matter/nodejs/src/fs/lock-utils.ts:139:19) at acquireDirectoryLock (/opt/iobroker/node_modules/@matter/nodejs/src/fs/lock-utils.ts:90:5) at DatafileRoot.#acquireRef (/opt/iobroker/node_modules/@matter/general/src/storage/DatafileRoot.ts:74:29) at DatafileRoot.lock (/opt/iobroker/node_modules/@matter/general/src/storage/DatafileRoot.ts:64:20) at FlatFileBlobStorageDriver.initialize (/opt/iobroker/node_modules/@matter/general/src/storage/BlobStorageDriver.ts:55:26) at FlatFileBlobStorageDriver.initialize (/opt/iobroker/node_modules/@matter/nodejs/src/storage/fs/FlatFileBlobStorageDriver.ts:46:9) at StorageService.#openBlobFilesystem (/opt/iobroker/node_modules/@matter/general/src/storage/StorageService.ts:395:13) at /opt/iobroker/node_modules/@matter/protocol/src/dcl/DclOtaUpdateService.ts:91:32 Caused by: [storage-lock] Storage is locked by another process (pid 1531) at acquireLock (/opt/iobroker/node_modules/@matter/nodejs/src/fs/lock-utils.ts:139:19) at acquireDirectoryLock (/opt/iobroker/node_modules/@matter/nodejs/src/fs/lock-utils.ts:90:5) at DatafileRoot.#acquireRef (/opt/iobroker/node_modules/@matter/general/src/storage/DatafileRoot.ts:74:29) at DatafileRoot.lock (/opt/iobroker/node_modules/@matter/general/src/storage/DatafileRoot.ts:64:20) at FlatFileBlobStorageDriver.initialize (/opt/iobroker/node_modules/@matter/general/src/storage/BlobStorageDriver.ts:55:26) at FlatFileBlobStorageDriver.initialize (/opt/iobroker/node_modules/@matter/nodejs/src/storage/fs/FlatFileBlobStorageDriver.ts:46:9) at StorageService.#openBlobFilesystem (/opt/iobroker/node_modules/@matter/general/src/storage/StorageService.ts:395:13) at /opt/iobroker/node_modules/@matter/protocol/src/dcl/DclOtaUpdateService.ts:91:32

matter.0
2026-07-17 06:55:49.468	error	Behaviors have errors

matter.0
2026-07-17 06:55:49.468	error	AggregateError: Behaviors have errors at /opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:253:27 at Function.all (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:752:25) at initializeBehaviors (/opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:246:40) at LocalActorContext.act (/opt/iobroker/node_modules/@matter/node/src/behavior/context/server/LocalActorContext.ts:62:22) at Behaviors.initialize (/opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:271:41) at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1061:38) at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/node/ClientNode.ts:107:31) at ClientNode.[construct] (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1096:21) at initializeDeferred (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:294:99) at Construction2.#invokeInitializer (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:575:40)

matter.0
2026-07-17 06:55:49.342	error	unhandled promise rejection: Behaviors have errors

matter.0
2026-07-17 06:55:49.341	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

matter.0
2026-07-17 06:55:49.016	warn	2026-07-17 06:55:48.636 ERROR ClientNode [internal] Unsupported async initialization detected when loading known peer at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/node/ClientNode.ts:113:19) at ClientNode.[construct] (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1096:21) at initializeDeferred (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:294:99) at Construction2.#invokeInitializer (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:575:40) at Construction2.start (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:295:22) at Factory.create (/opt/iobroker/node_modules/@matter/node/src/node/client/Peers.ts:623:27) at Peers.initialize (/opt/iobroker/node_modules/@matter/node/src/node/client/Peers.ts:111:25) at ServerNode.get peers [as peers] (/opt/iobroker/node_modules/@matter/node/src/node/ServerNode.ts:182:29) at ChangeNotificationService.#beginPeerObservation (/opt/iobroker/node_modules/@matter/node/src/node/integration/ChangeNotificationService.ts:112:27) at /opt/iobroker/node_modules/@matter/node/src/node/integration/ChangeNotificationService.ts:35:50

matter.0
2026-07-17 06:55:45.693	info	2026-07-17 06:55:45.692 WARN BasicInformationServer Using development values for some BasicInformation attributes: vendorId: 65521 vendorName: Matter.js Test Vendor productId: 32768 productName: Matter.js Test Product hardwareVersion: 0 softwareVersion: 0

Ich kann den Controller dann auch nicht mehr deaktivieren. Es bleibt nur noch den Adapter zu deinstallieren und neu zu installieren.

Irgendeine Idee? (Weil vorher hat ja alles wunderbar funktioniert)

Iobroker läuft im Docker-Container v11.11.0

Node.js = v22.22.2
npm = v10.9.7
js-controller = 7.2.1
Admin = 7.9.12

[icebear]

Ich antworte mir mal selber, das Problem ist gelöst.
Durch den Stromausfall, wurde anscheinend die interne Matter DB gelockt (Fehler Meldung PID1531)

• 1. Schritt, die matter.lock Datei umbenannt in matter.lock.bak und Adapter neu gestartet
     Leider kein Erfolg, der Adapter startet aber der Controller läßt sich immer noch nicht starten und produziert die folgende Fehlermeldung:

matter.0

2026-07-17 10:46:41.133errorTypeError: Cannot read properties of undefined (reading 'getCommissionedNodesDetails') at Controller.start (/opt/iobroker/node_modules/iobroker.matter/src/matter/ControllerNode.ts:402:60) at MatterAdapter.applyControllerConfiguration (/opt/iobroker/node_modules/iobroker.matter/src/main.ts:1546:21) at MatterAdapter.#onMessage (/opt/iobroker/node_modules/iobroker.matter/src/main.ts:382:32)matter.0

2026-07-17 10:46:41.098errorunhandled promise rejection: Cannot read properties of undefined (reading 'getCommissionedNodesDetails')matter.0

2026-07-17 10:46:41.098errorUnhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().matter.0

2026-07-17 10:46:41.073error[STORAGE] Cannot save state storage.controller.root$$operationalCredentials$$trustedRootCertificates: Connection is closed.matter.0

2026-07-17 10:46:40.852info2026-07-17 10:46:40.852 NOTICE Node controller is onlinematter.0

2026-07-17 10:46:40.807info2026-07-17 10:46:40.807 NOTICE Node controller going onlinematter.0

2026-07-17 10:46:40.806info2026-07-17 10:46:40.806 WARN CommissioningController BLE is not enabled on this platformmatter.0

2026-07-17 10:46:40.741info2026-07-17 10:46:40.741 WARN FabricAuthority Using test vendor ID 0xfff1 for controller fabricmatter.0

2026-07-17 10:46:40.557warnTerminated (UNCAUGHT_EXCEPTION): Without reasonmatter.0

2026-07-17 10:46:40.556infoterminatingmatter.0

2026-07-17 10:46:40.554infoStopping Controller...matter.0

2026-07-17 10:46:40.096errorBehaviors have errorsmatter.0

2026-07-17 10:46:40.096errorAggregateError: Behaviors have errors at /opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:253:27 at Function.all (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:752:25) at initializeBehaviors (/opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:246:40) at LocalActorContext.act (/opt/iobroker/node_modules/@matter/node/src/behavior/context/server/LocalActorContext.ts:62:22) at Behaviors.initialize (/opt/iobroker/node_modules/@matter/node/src/endpoint/properties/Behaviors.ts:271:41) at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1061:38) at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/node/ClientNode.ts:107:31) at ClientNode.[construct] (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1096:21) at initializeDeferred (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:294:99) at Construction2.#invokeInitializer (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:575:40)matter.0

2026-07-17 10:46:40.088errorunhandled promise rejection: Behaviors have errorsmatter.0

2026-07-17 10:46:40.088errorUnhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().matter.0

2026-07-17 10:46:40.025warn2026-07-17 10:46:39.937 ERROR ClientNode [internal] Unsupported async initialization detected when loading known peer at ClientNode.initialize (/opt/iobroker/node_modules/@matter/node/src/node/ClientNode.ts:113:19) at ClientNode.[construct] (/opt/iobroker/node_modules/@matter/node/src/endpoint/Endpoint.ts:1096:21) at initializeDeferred (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:294:99) at Construction2.#invokeInitializer (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:575:40) at Construction2.start (/opt/iobroker/node_modules/@matter/general/src/util/Construction.ts:295:22) at Factory.create (/opt/iobroker/node_modules/@matter/node/src/node/client/Peers.ts:623:27) at Peers.initialize (/opt/iobroker/node_modules/@matter/node/src/node/client/Peers.ts:111:25) at ServerNode.get peers [as peers] (/opt/iobroker/node_modules/@matter/node/src/node/ServerNode.ts:182:29) at ChangeNotificationService.#beginPeerObservation (/opt/iobroker/node_modules/@matter/node/src/node/integration/ChangeNotificationService.ts:112:27) at /opt/iobroker/node_modules/@matter/node/src/node/integration/ChangeNotificationService.ts:35:50 

• 2. Schritt
     Offensichtlich hat der Stromausfall dazugeführt, das die Daten vom Matter-Adapter nicht vollständig oder fehlerhaft geschrieben worden sind.
     Maßnahme: Den kompletten Ordner matter.0 im /opt/iobroker-data Verzeichnis gelöscht.
     Adapter neu gestartet, Controller ließ sich jetzt auch wieder ohne Probleme starten.
     Neuen Pairing Code in Alexa erzeugt und damit ließ sich auch die Bridge und die Markise wieder hinzufügen.

[Homoran]

@icebear sagte:

Offensichtlich hat der Stromausfall dazugeführt, das die Daten vom Matter-Adapter nicht vollständig oder fehlerhaft geschrieben worden sind.

Und nicht offensichtlich musst du leider damit rechnen dass auch weitere Date(ie)n korrupt sind

Da wäre eine Neuinstallation und Rückspielen eines Backups von vor dem Stromausfall angesagt