Cannot remove old Matter bridges – “Endpoint storage inaccessible” crash and automatic restart of addon

[k2c69]

Hi,
I can successfully add new Matter bridges using the Home-Assistant-Matter-Hub addon, but cannot remove existing ones.
Whenever I try to delete an old bridge from the UI or via API, the addon crashes and restarts automatically.

It looks like the storage backend cannot handle deletion of a bridge whose endpoint is no longer linked to a node.
After crash, the bridge reappears in the list, so it is never actually removed.

Expected behavior:
Deleting a bridge should correctly remove its endpoint data and not crash the addon.

Actual behavior:
The addon throws an InternalError from ServerEndpointStores.storeForEndpoint and then restarts (s6-rc restarts the service).

⸻

Log excerpt (on bridge delete):
2025-10-05 17:54:40.612 ERROR OccupancyS~ingServer OccupancySensingServer: Since revision 5 of the cluster features need to be set based on the detector type. Currently no features are enabled.
...
2025-10-05 17:54:46.143 FATAL Logger Unhandled error detected: [internal] Endpoint storage inaccessible because endpoint is not a node and is not owned by another endpoint
at ServerEndpointStores.storeForEndpoint (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120:13)
at numberPersister (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:168:28)
file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120
throw new InternalError(
^
InternalError: Endpoint storage inaccessible because endpoint is not a node and is not owned by another endpoint
at ServerEndpointStores.storeForEndpoint (...)
at numberPersister (...)
Node.js v22.19.0
s6-rc: info: service legacy-services: stopping
...
s6-rc: info: service base-addon-banner: starting

[supersavio]

same problem

2025-10-19 19:52:45.183 FATAL Logger Unhandled error detected: 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 "3".
at throwUnhandledRejectionsMode (node:internal/process/promises:392:7)
at processPromiseRejections (node:internal/process/promises:475:17)
at process.processTicksAndRejections (node:internal/process/task_queues:106:32)
node:internal/process/promises:392
new UnhandledPromiseRejection(reason);
^
UnhandledPromiseRejection: 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 "3".
at throwUnhandledRejectionsMode (node:internal/process/promises:392:7)
at processPromiseRejections (node:internal/process/promises:475:17)
at process.processTicksAndRejections (node:internal/process/task_queues:106:32) {
code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v22.20.0
...
2025-10-19 20:02:23.783 ERROR OccupancyS~ingServer OccupancySensingServer: Since revision 5 of the cluster features need to be set based on the detector type. Currently no features are enabled.

[HansSGitHub]

Same problem over here.
Home-Assistant-Matter-Hub
Version: 3.0.0-alpha.95

2025-10-23 12:16:25.826 NOTICE Node f0ca84a99f1d4abbae959e5c7cfdb96e going online
2025-10-23 12:16:25.869 INFO Transaction behavior-late-activation#eba committed and unlocked 2 resources
2025-10-23 12:16:25.885 NOTICE Node f0ca84a99f1d4abbae959e5c7cfdb96e is online
2025-10-23 12:16:25.916 INFO MdnsScanner MDNS Scan targets updated : commissionable = true Targets:
2025-10-23 12:17:20.789 INFO CertificateAuthority Loaded stored credentials with ID 0
2025-10-23 12:17:20.797 INFO MdnsScanner MDNS Scan targets updated : commissionable = true Targets:
2025-10-23 12:18:01.714 NOTICE Node 1e95197cba5a415391147306237d373b going offline
2025-10-23 12:18:01.908 INFO DeviceCommissioner All commissioning announcements stopped
2025-10-23 12:18:01.928 NOTICE Node 1e95197cba5a415391147306237d373b is offline
2025-10-23 12:18:01.930 NOTICE Node 1e95197cba5a415391147306237d373b resetting to factory defaults
2025-10-23 12:18:01.962 INFO ServerNodeStore Opened 1e95197cba5a415391147306237d373b storage at /config/data/1e95197cba5a415391147306237d373b
2025-10-23 12:18:02.080 INFO BaseEventStore Initialized new volatile event store
2025-10-23 12:18:02.140 INFO Endpoint 1e95197cba5a415391147306237d373b ready endpoint#: 0 type: RootNode (0x16) behaviors: 💤parts ✓index ✓basicInformation ✓accessControl ✓groupKeyManagement ✓generalCommissioning ✓administratorCommissioning ✓operationalCredentials ✓generalDiagnostics ✓commissioning ✓network 💤productDescription 💤subscription 💤sessions ✓events 💤controller ✓descriptor
2025-10-23 12:18:02.156 INFO Endpoint 1e95197cba5a415391147306237d373b.aggregator ready endpoint#: 1 type: Aggregator (0xe) behaviors: 💤parts ✓index ✓descriptor
2025-10-23 12:18:02.190 INFO ServerNodeStore Closed 1e95197cba5a415391147306237d373b storage at /config/data/1e95197cba5a415391147306237d373b
2025-10-23 12:18:02.192 INFO BridgeEnvi6237d373b Disposing BridgeEndpointManager
2025-10-23 12:18:02.194 INFO BridgeEnvi6237d373b Disposing BridgeDataProvider
2025-10-23 12:18:25.650 INFO DeviceCommissioner All commissioning announcements stopped

[TufftyMirror3585]

same problem
2025-11-07 17:51:01.537 FATAL Logger Unhandled error detected: [internal] Endpoint storage inaccessible because endpoint is not a node and is not owned by another endpoint
at ServerEndpointStores.storeForEndpoint (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120:13)
at numberPersister (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:168:28)
file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120
throw new InternalError(
^
InternalError: Endpoint storage inaccessible because endpoint is not a node and is not owned by another endpoint
at ServerEndpointStores.storeForEndpoint (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120:13)
at numberPersister (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:168:28)
Node.js v22.21.1

edit
however found a work around where if you set it to be limited so it is sending nothing and then try and delete it it works and does not crash.

[Blackhawk50000]

same:

2025-11-08 17:17:57.367 FATAL Logger Unhandled error detected: [internal] Endpoint storage inaccessible because endpoint is not a node and is not owned by another endpoint
at ServerEndpointStores.storeForEndpoint (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120:13)
at numberPersister (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:168:28)
file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120
throw new InternalError(
^
InternalError: Endpoint storage inaccessible because endpoint is not a node and is not owned by another endpoint
at ServerEndpointStores.storeForEndpoint (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:120:13)
at numberPersister (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/storage/server/ServerEndpointStores.js:168:28)
Node.js v22.21.1

[swever826]

I have the same issue at the moment. Is there a workaround in the meantime we wait for a fix?

[TufftyMirror3585]

If you set a filter that can not be met so there are no entities that are being sent you should be able to delete the bridge.

[dsduarte]

I also have this issue!

[mozolin]

If you set a filter that can not be met so there are no entities that are being sent you should be able to delete the bridge.

yeah, it works! thanks a million!

[Massimo-Productions]

If you set a filter that can not be met so there are no entities that are being sent you should be able to delete the bridge.

It works, thank you!