### Version
0.3.4
### Node.js Version
22.21.1
### Operating System
Home Ass…istant OS
### Issue Description
If I restart Matter Server in Home Assistant most my 20+ IKEA matter devices work for a very short time. After a few minutes the states stops changing. Ie: I open a window, and Home Assistant does not report the change. No entries in the matter-js log. I would expect HA to report that the window opened the same way the IKEA app reports it.
The status is imediatly updated in the IKEA app.
I have only One IKEA diregera gateway, and the matter devices are joined that and then shared with HA.
The test node is called "Node 3" in the logs
### Steps to Reproduce
1. Restart matter-js
2. Open the windows - State updated in HA
3. Close the windows - State updated in HA
4. Wait a few minutes
5. Open the windows - State is NOT updated in HA
6. Ping matter device - OK
7. Reinterview matter device - State is updated in HA
8. Close the window - State is NOT updated in HA
10. Ping matter device - OK
11. Reinterview matter device - State is updated in HA
### Server Logs
```shell
2026-02-02 16:01:38.862 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, endTimestamp: 2716729295 }
2026-02-02 16:01:38.863 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, startTimestamp: 2716382676, endTimestamp: 2716729295 }
2026-02-02 16:01:41.597 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, endTimestamp: 2716729297 }
2026-02-02 16:01:47.355 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, startTimestamp: 2716378551, endTimestamp: 2716729297 }
2026-02-02 16:01:47.356 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22934000, endTimestamp: 2716729298 }
2026-02-02 16:01:47.367 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22934000, startTimestamp: 2715674225, endTimestamp: 2716729298 }
2026-02-02 16:01:47.368 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83305999, endTimestamp: 2716729306 }
2026-02-02 16:01:47.370 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83305999, startTimestamp: 2703566710, endTimestamp: 2716729306 }
2026-02-02 16:01:54.873 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:01:54.873 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:01:54.879 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:01:54.879 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:01:54.881 INFO ClientInteraction Read » @1:3•b4b8⇵ba8d attributes: 0x0/OperationalCredentials(0x3e)/fabrics(0x1) fabricFiltered: false
2026-02-02 16:01:54.980 INFO ClientInteraction Read » @1:3•b4b8⇵ba8e attributes: 0x0/OperationalCredentials(0x3e)/fabrics(0x1) fabricFiltered: false
2026-02-02 16:02:00.125 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:02:00.125 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:02:00.126 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:02:00.126 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:02:00.129 INFO ClientInteraction Read » @1:3•b4b8⇵ba8f attributes: 0x0/OperationalCredentials(0x3e)/fabrics(0x1) fabricFiltered: false
2026-02-02 16:02:00.229 INFO ClientInteraction Read » @1:3•b4b8⇵ba90 attributes: 0x0/OperationalCredentials(0x3e)/fabrics(0x1) fabricFiltered: false
2026-02-02 16:02:01.875 INFO ClientInteraction Read « @1:3•b4b8⇵ba8d undefined attributes: 1 events: 0
2026-02-02 16:02:01.924 INFO ClientInteraction Read « @1:3•b4b8⇵ba8e undefined attributes: 1 events: 0
2026-02-02 16:02:01.983 INFO ClientInteraction Read « @1:3•b4b8⇵ba8f undefined attributes: 1 events: 0
2026-02-02 16:02:02.039 INFO ClientInteraction Read « @1:3•b4b8⇵ba90 undefined attributes: 1 events: 0
2026-02-02 16:02:02.182 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:02:02.182 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:02:02.182 INFO Controller~ndHandler Pinging node 3 on 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:02:09.604 INFO Controller~ndHandler Interview requested for node 3 - do a complete read
2026-02-02 16:02:09.606 INFO ClientInteraction Read » @1:3•b4b8⇵ba91 attributes:
2026-02-02 16:02:19.197 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30215000, endTimestamp: 2716729338 }
2026-02-02 16:02:19.200 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30215000, startTimestamp: 2715674361, endTimestamp: 2716729338 }
2026-02-02 16:02:21.171 INFO ClientInteraction Read « @1:3•b4b8⇵ba91 8↔8 attributes: 232 events: 0
2026-02-02 16:02:34.255 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, endTimestamp: 2716729348 }
2026-02-02 16:02:34.257 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, startTimestamp: 2715606884, endTimestamp: 2716729348 }
2026-02-02 16:02:38.505 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, endTimestamp: 2716729355 }
2026-02-02 16:02:45.164 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, startTimestamp: 2716382676, endTimestamp: 2716729355 }
2026-02-02 16:02:45.166 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, endTimestamp: 2716729357 }
2026-02-02 16:02:45.167 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, startTimestamp: 2716378551, endTimestamp: 2716729357 }
2026-02-02 16:02:47.904 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22937999, endTimestamp: 2716729357 }
2026-02-02 16:02:53.179 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22937999, startTimestamp: 2715674225, endTimestamp: 2716729357 }
2026-02-02 16:02:53.181 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83308998, endTimestamp: 2716729366 }
2026-02-02 16:02:54.354 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83308998, startTimestamp: 2703566710, endTimestamp: 2716729366 }
2026-02-02 16:03:19.706 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30218999, endTimestamp: 2716729398 }
2026-02-02 16:03:26.284 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30218999, startTimestamp: 2715674361, endTimestamp: 2716729398 }
2026-02-02 16:03:32.882 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, endTimestamp: 2716729408 }
2026-02-02 16:03:39.971 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, startTimestamp: 2715606884, endTimestamp: 2716729408 }
2026-02-02 16:03:39.973 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, endTimestamp: 2716729415 }
2026-02-02 16:03:39.974 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, startTimestamp: 2716382676, endTimestamp: 2716729415 }
2026-02-02 16:03:42.657 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, endTimestamp: 2716729416 }
2026-02-02 16:03:47.662 INFO ClientSubscription Subscription ca268a5a timed out after 7m 10s
2026-02-02 16:03:47.663 INFO PairedNode @1:16 Subscription timed out ... trying to re-establish ...
2026-02-02 16:03:47.663 INFO PairedNode @1:16 Reconnecting now ...
2026-02-02 16:03:47.665 INFO PhysicalDe~roperties server-2-134b.@1:16: Overwriting minIntervalFloorSeconds for intermittently connected device to 0
2026-02-02 16:03:47.665 INFO ClientInteraction Subscribe » @1:16•b4b6⇵ba92 min: 0 max: 10m attributes: events: eventFilters: undefined=65571
2026-02-02 16:03:48.035 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, startTimestamp: 2716378551, endTimestamp: 2716729416 }
2026-02-02 16:03:48.037 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22941999, endTimestamp: 2716729417 }
2026-02-02 16:03:48.048 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22941999, startTimestamp: 2715674225, endTimestamp: 2716729417 }
2026-02-02 16:03:48.051 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83309997, endTimestamp: 2716729425 }
2026-02-02 16:03:48.052 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83309997, startTimestamp: 2703566710, endTimestamp: 2716729425 }
2026-02-02 16:03:50.656 INFO ClientInteraction Subscription successful « @1:16•b4b6⇵ba92 2↔2 id: 73bfa4fa interval: 5m timeout: 7m 10s
2026-02-02 16:03:52.317 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:03:52.317 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:03:52.317 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:03:52.317 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:03:52.319 INFO ClientInteraction Read » @1:3•b4b8⇵ba93 attributes: 0x0/OperationalCredentials(0x3e)/fabrics(0x1) fabricFiltered: false
2026-02-02 16:03:52.419 INFO ClientInteraction Read » @1:3•b4b8⇵ba94 attributes: 0x0/OperationalCredentials(0x3e)/fabrics(0x1) fabricFiltered: false
2026-02-02 16:03:54.014 INFO ClientSubscription Subscription aa441620 timed out after 7m 10s
2026-02-02 16:03:54.014 INFO PairedNode @1:13 Subscription timed out ... trying to re-establish ...
2026-02-02 16:03:54.014 INFO PairedNode @1:13 Reconnecting now ...
2026-02-02 16:03:54.017 INFO PhysicalDe~roperties server-2-134b.@1:13: Overwriting minIntervalFloorSeconds for intermittently connected device to 0
2026-02-02 16:03:54.018 INFO ClientInteraction Subscribe » @1:13•b4b4⇵ba95 min: 0 max: 10m attributes: events: eventFilters: undefined=262201
2026-02-02 16:03:55.361 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:03:55.362 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:03:55.362 INFO Controller~ndHandler Pinging node 3 on 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:03:55.537 INFO ClientInteraction Read « @1:3•b4b8⇵ba93 undefined attributes: 1 events: 0
2026-02-02 16:03:55.583 INFO ClientInteraction Read « @1:3•b4b8⇵ba94 undefined attributes: 1 events: 0
2026-02-02 16:03:56.922 INFO ClientInteraction Subscription successful « @1:13•b4b4⇵ba95 2↔2 id: 9da1a698 interval: 5m timeout: 7m 10s
2026-02-02 16:03:59.902 INFO Controller~ndHandler Interview requested for node 3 - do a complete read
2026-02-02 16:03:59.903 INFO ClientInteraction Read » @1:3•b4b8⇵ba96 attributes:
2026-02-02 16:04:00.821 INFO ClientSubscription Subscription 0a433a62 timed out after 7m 10s
2026-02-02 16:04:00.822 INFO PairedNode @1:17 Subscription timed out ... trying to re-establish ...
2026-02-02 16:04:00.823 INFO PairedNode @1:17 Reconnecting now ...
2026-02-02 16:04:00.825 INFO PhysicalDe~roperties server-2-134b.@1:17: Overwriting minIntervalFloorSeconds for intermittently connected device to 0
2026-02-02 16:04:00.825 INFO ClientInteraction Subscribe » @1:17•b4b7⇵ba97 min: 0 max: 10m attributes: events: eventFilters: undefined=65554
2026-02-02 16:04:03.876 INFO ClientInteraction Subscription successful « @1:17•b4b7⇵ba97 2↔2 id: f6dae227 interval: 5m timeout: 7m 10s
2026-02-02 16:04:14.717 INFO ClientInteraction Read « @1:3•b4b8⇵ba96 8↔8 attributes: 232 events: 0
2026-02-02 16:04:19.742 INFO ClientSubscription Subscription 3e40943e timed out after 7m 10s
2026-02-02 16:04:19.742 INFO PairedNode @1:5 Subscription timed out ... trying to re-establish ...
2026-02-02 16:04:19.743 INFO PairedNode @1:5 Reconnecting now ...
2026-02-02 16:04:19.744 INFO PhysicalDe~roperties server-2-134b.@1:5: Overwriting minIntervalFloorSeconds for intermittently connected device to 0
2026-02-02 16:04:19.745 INFO ClientInteraction Subscribe » @1:5•b4be⇵ba98 min: 0 max: 10m attributes: events: eventFilters: undefined=262256
2026-02-02 16:04:22.384 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30224000, endTimestamp: 2716729458 }
2026-02-02 16:04:22.385 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30224000, startTimestamp: 2715674361, endTimestamp: 2716729458 }
2026-02-02 16:04:32.304 INFO ClientInteraction Subscription successful « @1:5•b4be⇵ba98 2↔2 id: 29cdec88 interval: 5m timeout: 7m 10s
2026-02-02 16:04:36.533 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, endTimestamp: 2716729468 }
2026-02-02 16:04:36.535 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, startTimestamp: 2715606884, endTimestamp: 2716729468 }
2026-02-02 16:04:37.729 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, endTimestamp: 2716729475 }
2026-02-02 16:04:37.735 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, startTimestamp: 2716382676, endTimestamp: 2716729475 }
2026-02-02 16:04:37.739 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, endTimestamp: 2716729476 }
2026-02-02 16:04:40.578 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, startTimestamp: 2716378551, endTimestamp: 2716729476 }
2026-02-02 16:04:45.875 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22944999, endTimestamp: 2716729477 }
2026-02-02 16:04:45.877 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22944999, startTimestamp: 2715674225, endTimestamp: 2716729477 }
2026-02-02 16:04:45.887 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83313003, endTimestamp: 2716729485 }
2026-02-02 16:04:45.889 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83313003, startTimestamp: 2703566710, endTimestamp: 2716729485 }
2026-02-02 16:04:48.478 INFO ClientSubscription Subscription 3f395bbc timed out after 7m 10s
2026-02-02 16:04:48.478 INFO PairedNode @1:15 Subscription timed out ... trying to re-establish ...
2026-02-02 16:04:48.478 INFO PairedNode @1:15 Reconnecting now ...
2026-02-02 16:04:48.479 INFO PhysicalDe~roperties server-2-134b.@1:15: Overwriting minIntervalFloorSeconds for intermittently connected device to 0
2026-02-02 16:04:48.479 INFO ClientInteraction Subscribe » @1:15•b4b5⇵ba99 min: 0 max: 10m attributes: events: eventFilters: undefined=196664
2026-02-02 16:04:48.857 INFO ClientSubscription Subscription b057302b timed out after 7m 10s
2026-02-02 16:04:48.857 INFO PairedNode @1:11 Subscription timed out ... trying to re-establish ...
2026-02-02 16:04:48.857 INFO PairedNode @1:11 Reconnecting now ...
2026-02-02 16:04:48.859 INFO PhysicalDe~roperties server-2-134b.@1:11: Overwriting minIntervalFloorSeconds for intermittently connected device to 0
2026-02-02 16:04:48.859 INFO ClientInteraction Subscribe » @1:11•b4b3⇵ba9a min: 0 max: 10m attributes: events: eventFilters: undefined=65562
2026-02-02 16:04:51.380 INFO ClientInteraction Subscription successful « @1:15•b4b5⇵ba99 2↔2 id: 64c4a371 interval: 5m timeout: 7m 10s
2026-02-02 16:04:51.753 INFO ClientInteraction Subscription successful « @1:11•b4b3⇵ba9a 2↔2 id: 330fbeb7 interval: 5m timeout: 7m 10s
2026-02-02 16:05:05.541 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:05:05.545 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:05:05.545 INFO Controller~ndHandler Pinging node 3 on 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:05:07.662 INFO ClientSubscription Subscription 9e3a99ac timed out after 16m 42s
2026-02-02 16:05:07.663 INFO PairedNode @1:19 Subscription timed out ... trying to re-establish ...
2026-02-02 16:05:07.663 INFO PairedNode @1:19 Reconnecting now ...
2026-02-02 16:05:07.666 INFO PhysicalDe~roperties server-2-134b.@1:19: Overwriting minIntervalFloorSeconds for intermittently connected device to 0
2026-02-02 16:05:07.668 INFO ClientInteraction Subscribe » @1:19•b4ba⇵ba9b min: 0 max: 10m attributes: events: eventFilters: undefined=131160
2026-02-02 16:05:11.231 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep129 reachableNewValue: true
2026-02-02 16:05:12.589 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep126 reachableNewValue: true
2026-02-02 16:05:12.590 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep128 reachableNewValue: true
2026-02-02 16:05:12.591 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep132 reachableNewValue: true
2026-02-02 16:05:12.592 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep127 reachableNewValue: true
2026-02-02 16:05:13.351 INFO ClientInteraction Subscription successful « @1:19•b4ba⇵ba9b 2↔2 id: c4018ea2 interval: 15m timeout: 16m 42s
2026-02-02 16:05:15.549 INFO Controller~ndHandler Node 3 is connected but no pings succeeded
2026-02-02 16:05:15.710 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep125 reachableNewValue: true
2026-02-02 16:05:15.712 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep124 reachableNewValue: true
2026-02-02 16:05:21.632 INFO ClientEventEmitter Received event switch.initialPress on server-2-134b.@1:1.ep1.ep84.ep85 newPosition: 1
2026-02-02 16:05:21.635 INFO ClientEventEmitter Received event switch.initialPress on server-2-134b.@1:1.ep1.ep84.ep85 newPosition: 1
2026-02-02 16:05:21.638 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30229999, endTimestamp: 2716729518 }
2026-02-02 16:05:21.639 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep138 energyImported: { energy: 30229999, startTimestamp: 2715674361, endTimestamp: 2716729518 }
2026-02-02 16:05:21.639 INFO ClientEventEmitter Received event switch.initialPress on server-2-134b.@1:1.ep1.ep84.ep86 newPosition: 1
2026-02-02 16:05:21.650 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep129 reachableNewValue: false
2026-02-02 16:05:21.650 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep128 reachableNewValue: false
2026-02-02 16:05:21.650 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep123 reachableNewValue: true
2026-02-02 16:05:21.651 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep131 reachableNewValue: true
2026-02-02 16:05:21.651 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep130 reachableNewValue: true
2026-02-02 16:05:21.651 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep128 reachableNewValue: true
2026-02-02 16:05:21.651 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep129 reachableNewValue: true
2026-02-02 16:05:21.651 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep129 reachableNewValue: false
2026-02-02 16:05:21.651 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep129 reachableNewValue: true
2026-02-02 16:05:21.652 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep125 reachableNewValue: false
2026-02-02 16:05:21.652 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep125 reachableNewValue: true
2026-02-02 16:05:21.652 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep130 reachableNewValue: false
2026-02-02 16:05:21.652 INFO ClientEventEmitter Received event bridgedDeviceBasicInformation.reachableChanged on server-2-134b.@1:1.ep1.ep130 reachableNewValue: true
2026-02-02 16:05:33.843 INFO Controller~ndHandler Node 3: Discovering addresses via mDNS (3s timeout)
2026-02-02 16:05:33.843 INFO Controller~ndHandler Node 3: mDNS discovered 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:05:33.844 INFO Controller~ndHandler Pinging node 3 on 1 addresses: fdd0:537d:3131:1:9ffe:cd6c:3d4:3e47
2026-02-02 16:05:37.376 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, endTimestamp: 2716729527 }
2026-02-02 16:05:37.378 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep136 energyImported: { energy: 10303000, startTimestamp: 2715606884, endTimestamp: 2716729527 }
2026-02-02 16:05:38.556 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, endTimestamp: 2716729535 }
2026-02-02 16:05:38.559 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep140 energyImported: { energy: 587999, startTimestamp: 2716382676, endTimestamp: 2716729535 }
2026-02-02 16:05:38.560 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, endTimestamp: 2716729536 }
2026-02-02 16:05:41.739 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep139 energyImported: { energy: 1442999, startTimestamp: 2716378551, endTimestamp: 2716729536 }
2026-02-02 16:05:43.855 INFO Controller~ndHandler Node 3 is connected but no pings succeeded
2026-02-02 16:05:47.862 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22948999, endTimestamp: 2716729537 }
2026-02-02 16:05:47.869 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep137 energyImported: { energy: 22948999, startTimestamp: 2715674225, endTimestamp: 2716729537 }
2026-02-02 16:05:47.886 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83315002, endTimestamp: 2716729545 }
2026-02-02 16:05:47.892 INFO ClientEventEmitter Received event electricalEnergyMeasurement.periodicEnergyMeasured on server-2-134b.@1:1.ep1.ep111 energyImported: { energy: 83315002, startTimestamp: 2703566710, endTimestamp: 2716729545 }
```
### Device Information
_No response_
### Additional Context
_No response_
### Pre-submission Checklist
- [x] I am running an Alpha/Beta version of the Matter.js server
- [x] I have included the complete server logs (not truncated)
- [x] I have checked existing issues to avoid duplicates