# Issues with the new IKEA Matter range

**URL:** <https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090>\
**Category:** Configuration\
**Tags:** matter\
**Created:** [March 4, 2026, 2:32pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090 "2026-03-04T14:32:26Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [March 4, 2026, 2:32pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/1 "2026-03-04T14:32:26Z")

</div>

Hello,

My installation is starting to work, a big thank you to everyone who helped me by the way! 🙂

I’m starting a small thread here because I think it will interest people

I have some IKEA Matter devices (TIMMERFLOTTE, …) that I managed to integrate into Gladys. However I’m encountering a difficulty: they stop being updated after a while.  
Over these few weeks of testing, I’ve had the chance to redo the steps to integrate the devices into my setup, AND each time I noticed data refresh issues.

Searching online it seems to be the same problem for Home Assistant or others.  
IKEA issue? Integration issue? We don’t really know yet I think

So I’m posting this topic to make sure people who ask the question on Google end up here and not on a HA forum.

And let’s try to work together to find a solution (well, the issue is simply due to an integration problem)

---

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [March 4, 2026, 2:34pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/2 "2026-03-04T14:34:47Z")

</div>

First point: I found this:

> <https://github.com/home-assistant/core/issues/158954>
>
> \### The problem
> 
> I've connected IKEA MYGGSPRAY motion detector both through the …IKEA Dirigera hub then shared to Home Assistant, and directly to Home Assistant, and every 30 minutes of idle time, Home Assistant loses connection with the device:
> 
> \`\`\`
> 2025-12-13 14:31:49.936 (Dummy-2) CHIP\_ERROR \[chip.native.DMG\] Subscription Liveness timeout with SubscriptionID = 0xcf7b37b7, Peer = 01:0000000000000006
> \`\`\`
> it claims it reconnects successfully:
> \`\`\`
> 2025-12-13 14:31:49.937 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
> 2025-12-13 14:32:00.687 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> Re-Subscription succeeded
> \`\`\`
> However, no new signals are received from the device to Home Assistant -- no new updates on the motion detector or on the light sensor that is in the package with it. The Dirigera hub and it's related app do continue to pick up updates from the motion detector (it does not appear to expose the light sensor). I've also checked it paired to Google Home, and Google Home also continues to receive updates after Home Assistant stops receiving updates.
> 
> After 30 minutes, again, HA reports another failure and reconnect:
> \`\`\`
> 2025-12-13 15:02:44.965 (Dummy-2) CHIP\_ERROR \[chip.native.DMG\] Subscription Liveness timeout with SubscriptionID = 0xeddbfa6b, Peer = 01:0000000000000006
> 2025-12-13 15:02:44.967 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
> 2025-12-13 15:02:59.803 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> Re-Subscription succeeded
> \`\`\`
> but Home Assistant is still not receiving any signal from the motion detector. It still reports correctly to both Dirigera and Google Home.
> 
> Restarting the Home Assistant Matter Server successfully reconnects to the device and resumes receiving signals, until it becomes idle for 30 minutes.  
> 
> Worth noting, that when the device was initially commissioned, it does state that it has what appears to be a half-hour reporting time:
> 
> \`\`\`
> 2025-12-13 13:41:35.851 (MainThread) INFO \[matter\_server.server.device\_controller\] Starting Matter commissioning using Node ID 6 and IP fdaa:35c9:32bf:1:70c8:3c2b:a3cd:d49d.
> 2025-12-13 13:41:36.967 (Dummy-2) INFO \[chip.ChipDeviceCtrl\] Established secure session with Device
> 2025-12-13 13:41:44.720 (Dummy-2) INFO \[chip.ChipDeviceCtrl\] Commissioning complete
> 2025-12-13 13:41:44.720 (MainThread) INFO \[matter\_server.server.device\_controller\] Matter commissioning of Node ID 6 successful.
> 2025-12-13 13:41:44.720 (MainThread) INFO \[matter\_server.server.device\_controller\] Interviewing node: 6
> 2025-12-13 13:41:49.658 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> Setting-up node...
> 2025-12-13 13:41:49.660 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> Setting up attributes and events subscription.
> 2025-12-13 13:41:54.625 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> Subscription succeeded with report interval \[0, 1800\]
> 2025-12-13 13:41:54.626 (MainThread) INFO \[matter\_server.server.device\_controller\] Commissioning of Node ID 6 completed.
> 2025-12-13 13:42:58.070 (MainThread) INFO \[matter\_server.server.device\_controller\] \<Node:6\> No new update found.
> \`\`\`
> 
> 
> 
> \### What version of Home Assistant Core has the issue?
> 
> core-2025.12.3
> 
> \### What was the last working version of Home Assistant Core?
> 
> \_No response\_
> 
> \### What type of installation are you running?
> 
> Home Assistant OS
> 
> \### Integration causing the issue
> 
> Matter
> 
> \### Link to integration documentation on our website
> 
> https://www.home-assistant.io/integrations/matter/
> 
> \### Diagnostics information
> 
> \_No response\_
> 
> \### Example YAML snippet
> 
> \`\`\`yaml
> 
> \`\`\`
> 
> \### Anything in the logs that might be useful for us?
> 
> \`\`\`txt
> 
> \`\`\`
> 
> \### Additional information
> 
> \_No response\_

I can check the dedicated logs to see what’s happening with my temperature sensor that’s stuck (I have two temp+humidity sensors, and only one of the temperature sensors appears to not respond at all). But I’d need guidance to find those logs.

---

<div class="post-metadata">

**Author:** ![jcmoriaud](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/jcmoriaud/32/20053_2.png) [@jcmoriaud](https://community.gladysassistant.com/u/jcmoriaud)\
**Post date:** [March 4, 2026, 5:18pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/4 "2026-03-04T17:18:09Z")

</div>

Great initiative.

For info, I had started talking about my struggles with the IKEA Matter gear here:

> [@Quel hub pour Matter?](https://community.gladysassistant.com/t/quel-hub-pour-matter/9512/20?u=jcmoriaud):
>
> Le Aqara M100 est vu par Gladys : Maintenant j’essaie d’appairer des télécommandes Ikea matter Bilresa et ça plante chaque fois via l’application Aqara (traduite de façon catastrophique…) : J’ai bien vérifié IPv6 sur ma box et partout pourtant… J’essaie également de les ajouter directement via Gladys qui ne les trouve pas, mais je ne sais pas si c’est la bonne manière de faire…

We could merge the thread; I’ll let the admins decide.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [March 5, 2026, 7:43am UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/5 "2026-03-05T07:43:08Z")

</div>

> [@jcmoriaud](#):
>
> We could merge the thread, I’ll let the admins decide.

I think we could instead separate your topic into a thread dedicated to the Aqara M100 so it’s clearer for anyone searching, on the forum or on Google 🙂 I’ll do that!

---

<div class="post-metadata">

**Author:** ![jcmoriaud](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/jcmoriaud/32/20053_2.png) [@jcmoriaud](https://community.gladysassistant.com/u/jcmoriaud)\
**Post date:** [March 5, 2026, 7:55am UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/6 "2026-03-05T07:55:20Z")

</div>

That’s perfect!

---

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [March 10, 2026, 7:28pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/7 "2026-03-10T19:28:26Z")

</div>

Okay, here’s a video that analyzes and explains the problems, even offering solutions:  
 ![](https://img.youtube.com/vi/mMQubi-sa5c/maxresdefault.jpg)https://www.youtube.com/embed/mMQubi-sa5c?feature=oembed&wmode=opaque

The part about switching to automatic IP is explained

---

<div class="post-metadata">

**Author:** ![jcmoriaud](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/jcmoriaud/32/20053_2.png) [@jcmoriaud](https://community.gladysassistant.com/u/jcmoriaud)\
**Post date:** [March 10, 2026, 10:36pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/8 "2026-03-10T22:36:15Z")

</div>

For reference, the link I posted in the other discussion:

[https://majornetwork.net/2026/01/home-assistant-was-unable-to-add-ikea-matter-devices/](https://majornetwork.net/2026/01/home-assistant-was-unable-to-add-ikea-matter-devices/)

---

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [March 12, 2026, 12:58pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/9 "2026-03-12T12:58:52Z")

</div>

well, while looking at this thread I had to change a setting that’s causing a problem:  
![image|690x114](upload://pnGxr4jpcK6SWdwE4z

---

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [March 17, 2026, 11:15am UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/10 "2026-03-17T11:15:30Z")

</div>

Well, they’re working on a fix on the HA (Home Assistant) side:

> <https://github.com/matter-js/matterjs-server/issues/187>
>
> \### 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

At this stage I can’t really say whether we should wait for an IKEA fix or an HA/Gladys fix 🤔

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [March 17, 2026, 6:03pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/11 "2026-03-17T18:03:36Z")

</div>

Given the issue’s tag («&nbsp;probably-vendor-issue&nbsp;»), and the messages in the post, the problem seems to be on IKEA’s side 🙂

I asked the AI to give me a recap:

 ![Screenshot 2026-03-17 at 19.03.07](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/4/5/454abf36ebc67e9afcce9ea6d3619d5bac392914.png)

---

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [March 17, 2026, 7:21pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/12 "2026-03-17T19:21:55Z")

</div>

ok, thanks  
we could imagine a Zigbee smart plug to switch the DIRIGERA off and on periodically 😃

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [March 17, 2026, 7:36pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/13 "2026-03-17T19:36:12Z")

</div>

Not very practical 😂 I think we’ll wait for the IKEA fix, aha

---

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [March 17, 2026, 7:57pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/14 "2026-03-17T19:57:03Z")

</div>

I don’t know if this is the best place to post this but here’s a video that explains Matter a bit:  
 ![](https://img.youtube.com/vi/yG-41bbeJAs/maxresdefault.jpg)https://www.youtube.com/embed/yG-41bbeJAs?feature=oembed&wmode=opaque

Well, it’s in English, but I think it’s fairly simple to understand (you do, of course, need to understand English)  
We should do the same in French and put a small link in Gladys to guide beginners.  
Any volunteers?

---

<div class="post-metadata">

**Author:** ![4get9](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/4/dbc845/32.png) [@4get9](https://community.gladysassistant.com/u/4get9)\
**Post date:** [May 9, 2026, 11:34pm UTC](https://community.gladysassistant.com/t/soucis-avec-la-nouvelle-gamme-ikea-matter/10090/15 "2026-05-09T23:34:44Z")

</div>

Hello,

It seems that IKEA has finally fixed the issue with its DIRIGERA

You need to update to firmware 2.934.5  
I had noticed that for a few days I had temperatures displaying in Gladys, but I no longer believed in a fix. So I thought it was a ghost data.

Now to be tested.  
I can finally get back to my home automation!