gaab11
February 9, 2026, 3:59pm
1
Hello everyone,
I have the device connected to an IKEA hub, which I use to turn the new IKEA Matter over Thread lamps on and off. The IKEA hub is connected via Thread integration in my Home Assistant.
My problem is that it simply turns off or goes into hibernation and no longer works, the leds in the device dont turn on when I press any button, or works with a huge delay. Any tips?
Molodax
(Alex)
February 9, 2026, 6:33pm
2
Experiencing the same problem. Interestingly enough, the remote works properly with IKEA app, so it seems like the delay happens somewhere between the IKEA hub and homeassistant.
Molodax
(Alex)
February 9, 2026, 8:19pm
3
gaab11:
Any tips?
Seems like known issue with HA:
opened 08:36PM - 13 Dec 25 UTC
integration: matter
### 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 have this same issue. However, if I have the Home Assistant mobile app open and on the remote’s device page, it works perfectly.
Molodax
(Alex)
March 14, 2026, 9:43pm
5
Imdeed, it works for me too as long as I’m on the remote’s device page in the app or webpage… strange. Perhaps, this needs to be added to the issue description, so hopefully someone will find the cause and fix it.
Pattillio
(Pattillio)
April 16, 2026, 10:43pm
6
Same problem here with both myggspray and bilresa scroll wheel. They seam tp go on a sleep mode. some times they work some other times they don’t.
Interestingly, the bilresa dual button works fine on HA.
I have 2 Myggspray and both work if the device page is open as someone stated.
The Bilresa scroll wheel most times does not work on HA but it does work nice via Ikea integration.
Is anyone working on this?
Molodax
(Alex)
April 25, 2026, 6:21am
7
This is fixed in the latest IKEA update 2.934.5
finkm
(Michael Fink)
May 4, 2026, 3:42pm
8
Is it? After updating my Dirigera to 2.934.5 it seemed to work briefly but over night I’m facing the same issue again.
Does it work reliably for you?
Molodax
(Alex)
May 4, 2026, 6:08pm
9
Strange. It does work for me, no issues at all now, so using several Bilresa after the fix. The issue has been closed too after many users confirmed the fix.
finkm
(Michael Fink)
May 9, 2026, 10:02am
10
You are right. False alarm. It seems to work now. The place where I kept the Bilresa had some reception issues. After changing the location it now works as it should