Matter.js server doesn't properly handle SIGTERM when started with env var BLUETOOTH_ADAPTER=0

[schildbach]

Version

0.5.10

Node.js Version

v22.22.2

Operating System

Docker

Issue Description

When shutting down the Docker container, Docker first sends a SIGTERM to the node process, initiating a graceful shutdown. However, Matter.js server when started with "BLUETOOTH_ADAPTER=0" seems to pick that signal but doesn't shut down. Hence, after 10 seconds the process is killed forcibly (SIGKILL). This yields an exit code of 137 for the container.

I tried extending the grace period to 30 seconds but it didn't change anything.

Steps to Reproduce

1. docker run -e BLUETOOTH_ADAPTER=0 matterjs-server:0.5.10
2. wait a bit to let it start
3. press CTRL-C once
4. it says "shutting down" in the log but it doesn't
5. after 10s the container is forcibly stopped by docker and the exit code is 137

Without "-e BLUETOOTH_ADAPTER=0", it works as expected (immediate shutdown and exit code 0).

Server Logs

2026-03-28 14:34:14.673 INFO   MatterServer         Command line: (no arguments)
2026-03-28 14:34:14.676 INFO   MatterServer         Bluetooth enabled (hci-id=0)
2026-03-28 14:34:14.678 INFO   ConfigStorage        Storage location: /data (Directory)
2026-03-28 14:34:14.683 INFO   ConfigStorage        Set config key fabricLabel to HomeAssistant
2026-03-28 14:34:14.689 INFO   ConfigStorage        Set config key nextNodeId to 1
2026-03-28 14:34:14.696 INFO   ConfigStorage        Set config key wifiSsid to undefined
2026-03-28 14:34:14.700 INFO   ConfigStorage        Set config key wifiCredentials to <redacted>
2026-03-28 14:34:14.703 INFO   ConfigStorage        Set config key threadDataset to <redacted>
2026-03-28 14:34:14.706 INFO   ServerIdResolver     Using new server ID format: server-1-fff1
2026-03-28 14:34:14.711 INFO   Controller~ndHandler BLE is enabled
2026-03-28 14:34:14.712 WARN   MatterServer         WebSocket server is listening on all network interfaces. Use --listen-address to restrict access. Ensure your environment (firewall, network) prevents unauthorized access.
2026-03-28 14:34:14.712 INFO   WebSocketC~erHandler Starting server: matter-server/0.5.10 (matter.js/0.17.0-alpha.0-20260326-42b6f59b7)
2026-03-28 14:34:14.728 INFO   ServerNodeStore      Opened server-1-fff1 storage location: /data/server-1-fff1 driver: file
2026-03-28 14:34:14.763 INFO   BaseEventStore       Initialized new volatile event store
2026-03-28 14:34:14.783 INFO   Endpoint             server-1-fff1 ready endpoint#: (unassigned) type: RootNode (0x16, rev 3) behaviors: 💤parts ✓index ✓basicInformation ✓accessControl ✓groupKeyManagement ✓generalCommissioning ✓administratorCommissioning ✓operationalCredentials ✓generalDiagnostics ✓commissioning ✓network 💤productDescription 💤subscriptions 💤sessions ✓events 💤controller ✓descriptor
2026-03-28 14:34:14.792 INFO   DclOtaUpdateService  Initialize OTAUpdateService prod: https://on.dcl.csa-iot.org test: https://on.test-net.dcl.csa-iot.org
2026-03-28 14:34:14.796 INFO   Endpoint             server-1-fff1.ota-provider ready endpoint#: 1 type: OtaProvider (0x14, rev 1) behaviors: ✓otaSoftwareUpdateProvider ✓descriptor ✓softwareupdates
2026-03-28 14:34:14.805 INFO   CertificateAuthority Created new credentials with ID 0
2026-03-28 14:34:14.824 NOTICE Node                 server-1-fff1 going online
noble warning: adapter does not support Bluetooth Low Energy (BLE, Bluetooth Smart).
               Try to run with environment variable:
               [sudo] NOBLE_HCI_DEVICE_ID=x node ...
2026-03-28 14:34:14.841 NOTICE Node                 server-1-fff1 is online
2026-03-28 14:34:14.842 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1
2026-03-28 14:34:14.849 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1
2026-03-28 14:34:14.850 INFO   Transaction          Tx ◦reactor<server-1-fff1.operationalCredentials.#handleUpdatedFabric>#23 waiting on ◦offline#20
2026-03-28 14:34:14.855 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1
2026-03-28 14:34:14.862 INFO   MdnsAdvertisement    Publishing kind: operational service: mdns:2047FEC6DD3B68FA-000000000001B669._matter._tcp.local
2026-03-28 14:34:14.863 INFO   SoftwareUp~teManager Scheduling first OTA update check in 5m 44s
2026-03-28 14:34:14.878 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1 privilege: 3 authMode: 2 subjects:  targets: { cluster: 41, endpoint: 1, deviceType: null } fabricIndex: 1
2026-03-28 14:34:14.879 INFO   OtaSoftwar~derServer Added ACL entry to allow access to OTA Software Update Provider for anyone in the fabric
2026-03-28 14:34:14.879 INFO   MdnsClient           MDNS Scan targets updated : commissionable: true
2026-03-28 14:34:14.880 INFO   Controller~ndHandler Controller started
2026-03-28 14:34:14.880 INFO   Controller~ndHandler OTA event handlers registered
2026-03-28 14:34:14.881 INFO   DclVendorInfoService Initialize VendorInfoService source: https://on.dcl.csa-iot.org interval: 24h
2026-03-28 14:34:14.881 INFO   DclCertifi~teService Initialize CertificateService prod: https://on.dcl.csa-iot.org
2026-03-28 14:34:14.884 INFO   DclVendorInfoService Fetching vendor information from DCL
2026-03-28 14:34:14.891 INFO   DclCertifi~teService Loaded 0 certificates from storage
2026-03-28 14:34:15.321 INFO   DclVendorInfoService Fetched 408 vendors from DCL
2026-03-28 14:34:15.325 INFO   DclVendorInfoService Stored 412 vendors
noble warning: adapter does not support Bluetooth Low Energy (BLE, Bluetooth Smart).
               Try to run with environment variable:
               [sudo] NOBLE_HCI_DEVICE_ID=x node ...
2026-03-28 14:34:18.576 INFO   DclCertifi~teService Downloaded and stored 74 new certificates (total: 74)
2026-03-28 14:34:18.576 INFO   Controller~ndHandler Found 0 nodes:
2026-03-28 14:34:18.576 INFO   Controller~ndHandler All 0 nodes initialized, starting connections
2026-03-28 14:34:18.579 INFO   WebServer            Webserver listening on http://0.0.0.0:5580
Stopping webserver...
2026-03-28 14:35:01.547 NOTICE Runtime              Shutting down
2026-03-28 14:35:01.548 ERROR  Runtime              Unhandled error closing worker: Could not start scanning, state is unsupported (not poweredOn)
  at Noble.scan (/app/node_modules/@stoprocent/noble/lib/noble.js:193:23)
  at Noble.startScanning (/app/node_modules/@stoprocent/noble/lib/noble.js:217:12)
  at NobleBleClient.close (/app/node_modules/@matter/nodejs-ble/src/NobleBleClient.ts:155:19)
  at cancel (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:246:51)
  at RuntimeService.#cancelWorker (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:275:16)
  at RuntimeService.cancel (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:166:35)
  at RuntimeService.interrupt (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:179:14)
  at process.interruptHandler (/app/node_modules/@matter/nodejs/src/environment/ProcessManager.ts:110:22)
  at process.emit (node:events:531:35)
2026-03-28 14:35:01.556 NOTICE Node                 server-1-fff1 going offline
Handlers unregistered
Servers closed
2026-03-28 14:35:01.558 INFO   CustomClusterPoller  Custom attribute poller stopped
2026-03-28 14:35:01.565 INFO   MdnsAdvertisement    Unpublishing kind: operational service: mdns:2047FEC6DD3B68FA-000000000001B669._matter._tcp.local time: 46.7s
2026-03-28 14:35:01.566 NOTICE Node                 server-1-fff1 is offline
2026-03-28 14:35:01.571 INFO   ServerNodeStore      Closed server-1-fff1 storage location: /data/server-1-fff1 driver: file

Device Information

No response

Additional Context

No response

Pre-submission Checklist

• I am running an Alpha/Beta version of the Matter.js server
• I have included the complete server logs (not truncated)
• I have checked existing issues to avoid duplicates

[schildbach]

The issue may be limited to the case where bluetooth cannot be initialized, but even in this case I think the process should exit gracefully.

[Apollon77]

The problem is that this is very hard to debug andcan als be an issue in certain cases in the underlaying Bluetooth library. But so or so ... yes the log shows an error ... where exactly these 10s kick in? After the end of the log? or in between? I need mroe context and ideally a debug log

[Apollon77]

Ok WHile checking code we found something that could lead to this effect in exactly this error case ... so lets give next version a try

[schildbach]

v0.5.11 exhibits this problem as well, if sending the SIGTERM quick enough. Here is a debug log:

$ docker run -u 0:0 -e LOG_LEVEL=debug -e BLUETOOTH_ADAPTER=0 -v /run/dbus:/run/dbus:ro matterjs-server:0.5.11
2026-04-01 15:18:44.361 INFO   MatterServer         Command line: (no arguments)
2026-04-01 15:18:44.364 INFO   MatterServer         Bluetooth enabled (hci-id=0)
2026-04-01 15:18:44.366 DEBUG  LegacyDataLoader     No chip.json found at /data/chip.json
2026-04-01 15:18:44.366 INFO   ConfigStorage        Storage location: /data (Directory)
2026-04-01 15:18:44.369 DEBUG  NodeJsDirectoryLock  Acquired storage lock for config pid 1
2026-04-01 15:18:44.370 INFO   ConfigStorage        Set config key fabricLabel to HomeAssistant
2026-04-01 15:18:44.375 INFO   ConfigStorage        Set config key nextNodeId to 1
2026-04-01 15:18:44.381 INFO   ConfigStorage        Set config key wifiSsid to undefined
2026-04-01 15:18:44.383 INFO   ConfigStorage        Set config key wifiCredentials to <redacted>
2026-04-01 15:18:44.386 INFO   ConfigStorage        Set config key threadDataset to <redacted>
2026-04-01 15:18:44.389 INFO   ServerIdResolver     Using new server ID format: server-1-fff1
2026-04-01 15:18:44.390 DEBUG  NodeJsDirectoryLock  Acquired storage lock for server-1-fff1 pid 1
2026-04-01 15:18:44.393 DEBUG  NodeJsDirectoryLock  Released storage lock for server-1-fff1
2026-04-01 15:18:44.393 DEBUG  Crypto               Using Node.js crypto implementation
2026-04-01 15:18:44.393 INFO   Controller~ndHandler BLE is enabled
2026-04-01 15:18:44.394 WARN   MatterServer         WebSocket server is listening on all network interfaces. Use --listen-address to restrict access. Ensure your environment (firewall, network) prevents unauthorized access.
2026-04-01 15:18:44.395 INFO   WebSocketC~erHandler Starting server: matter-server/0.5.11 (matter.js/0.17.0-alpha.0-20260401-1edc54c9a)
2026-04-01 15:18:44.397 DEBUG  NodeJsDirectoryLock  Acquired storage lock for server-1-fff1 pid 1
2026-04-01 15:18:44.398 DEBUG  NodeJsDirectoryLock  Released storage lock for server-1-fff1
2026-04-01 15:18:44.405 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2026-04-01 15:18:44.408 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2026-04-01 15:18:44.410 DEBUG  NodeJsDirectoryLock  Acquired storage lock for server-1-fff1 pid 1
2026-04-01 15:18:44.412 INFO   ServerNodeStore      Opened server-1-fff1 storage location: /data/server-1-fff1 driver: file
2026-04-01 15:18:44.415 DEBUG  Crypto               Using Node.js crypto implementation for server-1-fff1
2026-04-01 15:18:44.459 INFO   BaseEventStore       Initialized new volatile event store
2026-04-01 15:18:44.476 INFO   Endpoint             server-1-fff1 ready endpoint#: (unassigned) type: RootNode (0x16, rev 3) behaviors: 💤parts ✓index ✓basicInformation ✓accessControl ✓groupKeyManagement ✓generalCommissioning ✓administratorCommissioning ✓operationalCredentials ✓generalDiagnostics ✓commissioning ✓network 💤productDescription 💤subscriptions 💤sessions ✓events 💤controller ✓descriptor
2026-04-01 15:18:44.483 INFO   DclOtaUpdateService  Initialize OTAUpdateService prod: https://on.dcl.csa-iot.org test: https://on.test-net.dcl.csa-iot.org
2026-04-01 15:18:44.485 DEBUG  NodeJsDirectoryLock  Acquired storage lock for ota pid 1
2026-04-01 15:18:44.488 INFO   Endpoint             server-1-fff1.ota-provider ready endpoint#: 1 type: OtaProvider (0x14, rev 1) behaviors: ✓otaSoftwareUpdateProvider ✓descriptor ✓softwareupdates
2026-04-01 15:18:44.498 INFO   CertificateAuthority Created new credentials with ID 0
2026-04-01 15:18:44.508 DEBUG  Fabric               Installing operational certificate nodeId: 000000000001b669 fabricId: 1
2026-04-01 15:18:44.511 DEBUG  FabricAuthority      Created new controller fabric 1
2026-04-01 15:18:44.512 DEBUG  MatterController     No former commissioned nodes to migrate.
2026-04-01 15:18:44.514 NOTICE Node                 server-1-fff1 going online
2026-04-01 15:18:44.528 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:undefined localAddress: :::52447
noble warning: adapter does not support Bluetooth Low Energy (BLE, Bluetooth Smart).
               Try to run with environment variable:
               [sudo] NOBLE_HCI_DEVICE_ID=x node ...
2026-04-01 15:18:44.529 DEBUG  NobleBleClient       Noble state changed to unsupported
2026-04-01 15:18:44.529 DEBUG  NobleBleClient       Noble state changed to poweredOff
2026-04-01 15:18:44.529 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:52447 localAddress: 0.0.0.0:52447
2026-04-01 15:18:44.534 NOTICE Node                 server-1-fff1 is online
2026-04-01 15:18:44.534 DEBUG  OccurrenceManager    Recorded event #1 eventId: 0 clusterId: 40 endpointId: 0 priority: 2 epochTimestamp: 1775056724534 payload: { softwareVersion: 511 }
2026-04-01 15:18:44.535 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1
2026-04-01 15:18:44.543 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1
2026-04-01 15:18:44.544 INFO   Transaction          Tx ◦reactor<server-1-fff1.operationalCredentials.#handleUpdatedFabric>#23 waiting on ◦offline#20
2026-04-01 15:18:44.549 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1
2026-04-01 15:18:44.550 DEBUG  OccurrenceManager    Recorded event #2 eventId: 3 clusterId: 51 endpointId: 0 priority: 2 epochTimestamp: 1775056724550 payload: { bootReason: 0 }
2026-04-01 15:18:44.555 INFO   MdnsAdvertisement    Publishing kind: operational service: mdns:06961F578695C99D-000000000001B669._matter._tcp.local
2026-04-01 15:18:44.556 INFO   SoftwareUp~teManager Scheduling first OTA update check in 8m 45s
2026-04-01 15:18:44.557 DEBUG  Advertisement        Begin auto broadcast kind: operational service: mdns:06961F578695C99D-000000000001B669._matter._tcp.local
2026-04-01 15:18:44.557 DEBUG  MdnsAdvertisement    Broadcast kind: operational service: mdns:06961F578695C99D-000000000001B669._matter._tcp.local number: 1 next: 1.21s
2026-04-01 15:18:44.560 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2026-04-01 15:18:44.561 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2026-04-01 15:18:44.561 DEBUG  NodejsChannel        Initialize multicast address: 172.17.0.3:5353 interface: eth0 type: udp4
2026-04-01 15:18:44.561 DEBUG  NodejsChannel        Initialize multicast address: ::%eth0:5353 interface: eth0 type: udp6
2026-04-01 15:18:44.571 INFO   FabricAccessControl  ACL List updated privilege: 5 authMode: 2 subjects: 112233 targets: null fabricIndex: 1 privilege: 3 authMode: 2 subjects:  targets: { cluster: 41, endpoint: 1, deviceType: null } fabricIndex: 1
2026-04-01 15:18:44.571 INFO   OtaSoftwar~derServer Added ACL entry to allow access to OTA Software Update Provider for anyone in the fabric
2026-04-01 15:18:44.573 INFO   Controller~ndHandler Controller started
2026-04-01 15:18:44.573 INFO   Controller~ndHandler OTA event handlers registered
2026-04-01 15:18:44.573 INFO   DclVendorInfoService Initialize VendorInfoService source: https://on.dcl.csa-iot.org interval: 24h
2026-04-01 15:18:44.574 INFO   DclCertifi~teService Initialize CertificateService prod: https://on.dcl.csa-iot.org
2026-04-01 15:18:44.576 DEBUG  NodeJsDirectoryLock  Acquired storage lock for vendors pid 1
2026-04-01 15:18:44.576 DEBUG  NodeJsDirectoryLock  Acquired storage lock for certificates pid 1
2026-04-01 15:18:44.576 INFO   DclVendorInfoService Fetching vendor information from DCL
2026-04-01 15:18:44.576 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/vendorinfo/vendors
2026-04-01 15:18:44.583 INFO   DclCertifi~teService Loaded 0 certificates from storage
2026-04-01 15:18:44.583 DEBUG  DclCertifi~teService Update certificates
2026-04-01 15:18:44.584 DEBUG  DclCertifi~teService Fetching PAA certificates from DCL (production)
2026-04-01 15:18:44.584 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/root-certificates
2026-04-01 15:18:44.779 DEBUG  DclCertifi~teService Found 74 production root certificates in DCL
2026-04-01 15:18:44.779 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MFIxDDAKBgNVBAoMA0NTQTEsMCoGA1UEAwwjTWF0dGVyIENlcnRpZmljYXRpb24gYW5kIFRlc3RpbmcgQ0ExFDASBgorBgEEAYKifAIBDARDNUEw/97%3AE4%3A69%3AD0%3AC5%3A04%3A14%3AC2%3A6F%3AC7%3A01%3AF7%3A7E%3A94%3A77%3A39%3A09%3A8D%3AF6%3AA5
2026-04-01 15:18:44.817 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/vendorinfo/vendors?pagination.key=AAATaQAAAAAv
2026-04-01 15:18:44.864 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/vendorinfo/vendors?pagination.key=AAAUfwAAAAAv
2026-04-01 15:18:44.911 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/vendorinfo/vendors?pagination.key=AAAVbAAAAAAv
2026-04-01 15:18:44.918 DEBUG  DclCertifi~teService Stored certificate skid: 97E469D0C50414C26FC701F77E947739098DF6A5 vid: 0
2026-04-01 15:18:44.918 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MFMxCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5EaWdpQ2VydCwgSW5jLjErMCkGA1UEAxMiRGlnaUNlcnQgUm9vdCBDQSBmb3IgTUFUVEVSIFBLSSBHMQ%3D%3D/32%3A50%3A45%3A19%3A33%3A44%3A59%3A9B%3A46%3A65%3AD4%3A59%3AFD%3A3A%3A15%3AF1%3AC1%3A16%3ACC%3ABD
2026-04-01 15:18:44.957 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/vendorinfo/vendors?pagination.key=AAAWOQAAAAAv
2026-04-01 15:18:44.964 DEBUG  DclCertifi~teService Stored certificate skid: 325045193344599B4665D459FD3A15F1C116CCBD vid: 5542
2026-04-01 15:18:44.964 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MDYxIDAeBgNVBAMMF1N0cm9uZ0tleSBNYXR0ZXIgRzEgUEFBMRIwEAYDVQQKDAlTdHJvbmdLZXk%3D/37%3A4E%3A29%3A5A%3AC5%3A51%3A73%3A0B%3AAF%3A65%3AD5%3A29%3A83%3A9B%3A4E%3AE0%3A9D%3A39%3A58%3A8A
2026-04-01 15:18:44.997 INFO   DclVendorInfoService Fetched 408 vendors from DCL
2026-04-01 15:18:45.003 INFO   DclVendorInfoService Stored 412 vendors
2026-04-01 15:18:45.010 DEBUG  DclCertifi~teService Stored certificate skid: 374E295AC551730BAF65D529839B4EE09D39588A vid: 5475
2026-04-01 15:18:45.010 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MDMxGzAZBgNVBAMMElRQLUxpbmsgTWF0dGVyIFBBQTEUMBIGCisGAQQBgqJ8AgEMBDExODg%3D/C5%3A85%3A31%3A41%3A9E%3AE0%3A3E%3AE4%3AA1%3ADC%3AF5%3A51%3AE0%3A34%3A40%3ADC%3A2B%3ABE%3AC2%3A0A
2026-04-01 15:18:45.058 DEBUG  DclCertifi~teService Stored certificate skid: C58531419EE03EE4A1DCF551E03440DC2BBEC20A vid: 0
2026-04-01 15:18:45.059 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MDUxHTAbBgNVBAMMFExFRURBUlNPTi1NQVRURVItUEFBMRQwEgYKKwYBBAGConwCAQwEMTE2OA%3D%3D/72%3AA6%3A3A%3A31%3A6E%3A9A%3A3C%3AAE%3A15%3A29%3A9C%3AFF%3A8E%3A8C%3AC7%3AFA%3AB3%3A87%3AD1%3A85
2026-04-01 15:18:45.107 DEBUG  DclCertifi~teService Stored certificate skid: 72A63A316E9A3CAE15299CFF8E8CC7FAB387D185 vid: 0
2026-04-01 15:18:45.107 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MFExITAfBgNVBAoMGHViaXN5cyB0ZWNobm9sb2dpZXMgR21iSDEWMBQGA1UEAwwNTWF0dGVyIFBBQSAjMTEUMBIGCisGAQQBgqJ8AgEMBDEwRjI%3D/A5%3AD1%3AB0%3ABF%3A94%3A89%3A48%3A67%3A99%3A86%3AD7%3A06%3A11%3A4D%3A94%3A8A%3AFA%3A87%3AF9%3A02
2026-04-01 15:18:45.152 DEBUG  DclCertifi~teService Stored certificate skid: A5D1B0BF948948679986D706114D948AFA87F902 vid: 0
2026-04-01 15:18:45.153 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MDAxGDAWBgNVBAMMD1R1eWEgTWF0dGVyIFBBQTEUMBIGCisGAQQBgqJ8AgEMBDEyNUQ%3D/35%3A57%3A52%3AA3%3AA7%3A20%3A58%3A33%3A77%3A1E%3AFA%3ABE%3AA5%3A32%3A67%3A0C%3AB0%3AB3%3A1D%3A09
2026-04-01 15:18:45.202 DEBUG  DclCertifi~teService Stored certificate skid: 355752A3A7205833771EFABEA532670CB0B31D09 vid: 0
2026-04-01 15:18:45.202 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MFExHTAbBgNVBAMMFEVzcHJlc3NpZiBNYXR0ZXIgUEFBMRowGAYDVQQKDBFFc3ByZXNzaWYgU3lzdGVtczEUMBIGCisGAQQBgqJ8AgEMBDEzMUI%3D/4D%3A12%3AF5%3A80%3A1B%3A75%3AD3%3A23%3A85%3AC5%3A55%3A90%3AEF%3A45%3A27%3ABC%3AB3%3ABA%3A71%3AE0
2026-04-01 15:18:45.253 DEBUG  DclCertifi~teService Stored certificate skid: 4D12F5801B75D32385C55590EF4527BCB3BA71E0 vid: 0
2026-04-01 15:18:45.254 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MDIxGjAYBgNVBAMMEU1lcm9zcyBNYXR0ZXIgUEFBMRQwEgYKKwYBBAGConwCAQwEMTM0NQ%3D%3D/40%3A97%3A46%3AA4%3A3D%3A7E%3AF1%3A51%3AB6%3ACD%3AD8%3AA0%3A9E%3AA4%3A76%3AFA%3A9B%3ADF%3A75%3A63
2026-04-01 15:18:45.302 DEBUG  DclCertifi~teService Stored certificate skid: 409746A43D7EF151B6CDD8A09EA476FA9BDF7563 vid: 0
2026-04-01 15:18:45.303 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MDAxGDAWBgNVBAMMD0thc2EgTWF0dGVyIFBBQTEUMBIGCisGAQQBgqJ8AgEMBDEzOTE%3D/35%3A67%3ACF%3A59%3A79%3AF6%3A5A%3AA2%3A60%3A80%3AF4%3AF1%3AC9%3A5A%3AAD%3A6E%3A89%3A51%3A9D%3A2F
2026-04-01 15:18:45.352 DEBUG  DclCertifi~teService Stored certificate skid: 3567CF5979F65AA26080F4F1C95AAD6E89519D2F vid: 0
2026-04-01 15:18:45.353 DEBUG  DclClient            Fetching from DCL: https://on.dcl.csa-iot.org/dcl/pki/certificates/MDAxGDAWBgNVBAMMD1RhcG8gTWF0dGVyIFBBQTEUMBIGCisGAQQBgqJ8AgEMBDEzOTI%3D/9F%3A63%3AB3%3A5B%3A95%3A24%3A80%3A40%3A52%3A22%3A79%3A67%3A71%3AF6%3A5A%3AD8%3A4D%3AB1%3A80%3A49
^CStopping webserver...
2026-04-01 15:18:45.376 NOTICE Runtime              Shutting down
2026-04-01 15:18:45.377 DEBUG  NobleBleClient       Stopping Noble
2026-04-01 15:18:45.377 INFO   NobleBleClient       Error starting scan during close, proceeding to stop: Could not start scanning, state is poweredOff (not poweredOn)
  at Noble.scan (/app/node_modules/@stoprocent/noble/lib/noble.js:193:23)
  at Noble.startScanning (/app/node_modules/@stoprocent/noble/lib/noble.js:217:12)
  at NobleBleClient.close (/app/node_modules/@matter/nodejs-ble/src/NobleBleClient.ts:156:23)
  at cancel (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:246:51)
  at RuntimeService.#cancelWorker (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:275:16)
  at RuntimeService.cancel (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:166:35)
  at RuntimeService.interrupt (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:179:14)
  at process.interruptHandler (/app/node_modules/@matter/nodejs/src/environment/ProcessManager.ts:110:22)
  at process.emit (node:events:531:35)
noble warning: adapter does not support Bluetooth Low Energy (BLE, Bluetooth Smart).
               Try to run with environment variable:
               [sudo] NOBLE_HCI_DEVICE_ID=x node ...
2026-04-01 15:18:45.380 DEBUG  NobleBleClient       Noble state changed to unsupported
2026-04-01 15:18:45.380 ERROR  Runtime              Unhandled error closing worker: Could not start scanning, state is unsupported (not poweredOn)
  at Hci.setScanEnabled (/app/node_modules/@stoprocent/noble/lib/hci-socket/hci.js:517:16)
  at Gap.stopScanning (/app/node_modules/@stoprocent/noble/lib/hci-socket/gap.js:63:13)
  at NobleBindings.stopScanning (/app/node_modules/@stoprocent/noble/lib/hci-socket/bindings.js:107:13)
  at NobleBindings.stop (/app/node_modules/@stoprocent/noble/lib/hci-socket/bindings.js:75:8)
  at Noble.stop (/app/node_modules/@stoprocent/noble/lib/noble.js:330:20)
  at NobleBleClient.close (/app/node_modules/@matter/nodejs-ble/src/NobleBleClient.ts:162:15)
  at cancel (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:246:51)
  at RuntimeService.#cancelWorker (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:275:16)
  at RuntimeService.cancel (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:166:35)
  at RuntimeService.interrupt (/app/node_modules/@matter/general/src/environment/RuntimeService.ts:179:14)
2026-04-01 15:18:45.382 NOTICE Node                 server-1-fff1 going offline
2026-04-01 15:18:45.382 DEBUG  OccurrenceManager    Recorded event #3 eventId: 1 clusterId: 40 endpointId: 0 priority: 2 epochTimestamp: 1775056725382
Handlers unregistered
Servers closed
2026-04-01 15:18:45.385 INFO   CustomClusterPoller  Custom attribute poller stopped
2026-04-01 15:18:45.386 DEBUG  NodeJsDirectoryLock  Released storage lock for config
2026-04-01 15:18:45.391 DEBUG  Advertisement        End auto broadcast kind: operational service: mdns:06961F578695C99D-000000000001B669._matter._tcp.local
2026-04-01 15:18:45.391 INFO   MdnsAdvertisement    Unpublishing kind: operational service: mdns:06961F578695C99D-000000000001B669._matter._tcp.local time: 836ms
2026-04-01 15:18:45.392 NOTICE Node                 server-1-fff1 is offline
2026-04-01 15:18:45.394 DEBUG  NodeJsDirectoryLock  Released storage lock for ota
2026-04-01 15:18:45.395 DEBUG  NodeJsDirectoryLock  Released storage lock for vendors
2026-04-01 15:18:45.399 DEBUG  DclCertifi~teService Stored certificate skid: 9F63B35B952480405222796771F65AD84DB18049 vid: 0
[implementation] Controller instance not yet started. Please call start() first.
      at CommissioningController.#assertControllerIsStarted (/app/node_modules/@project-chip/matter.js/src/CommissioningController.ts:348:19)
      at CommissioningController.getCommissionedNodes (/app/node_modules/@project-chip/matter.js/src/CommissioningController.ts:737:33)
      at ControllerCommandHandler.initializeNodes (/app/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:396:40)
      at async WebSocketControllerHandler.register (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:354:9)
      at async WebServer.start (/app/node_modules/matter-server/src/server/WebServer.ts:37:17)
      at async start (/app/node_modules/matter-server/src/MatterServer.ts:189:5)
2026-04-01 15:18:45.403 DEBUG  NodeJsDirectoryLock  Released storage lock for certificates
2026-04-01 15:18:45.404 DEBUG  NodeJsDirectoryLock  Released storage lock for server-1-fff1
2026-04-01 15:18:45.405 INFO   ServerNodeStore      Closed server-1-fff1 storage location: /data/server-1-fff1 driver: file
^CStopping webserver...
Handlers unregistered
Servers closed
2026-04-01 15:19:13.248 INFO   CustomClusterPoller  Custom attribute poller stopped
2026-04-01 15:19:13.249 NOTICE Runtime              Shutting down
^C
got 3 SIGTERM/SIGINTs, forcefully exiting

I pressed CTRL-C very quickly after startup, then waited for a good while, then pressed CTRL-C twice in a row.