Ikea MYGGSPRAY sensor not able to add to homey

Devices
1

Hello,

I am trying to add the Ikea MYGGSPRAY sensor to homey pro 2026 via matter over thread. Tried every possible route by adding, factory reset of the sensor but no luck. I got below screens with the error. Anyone have an idea what to do? I searched for other topics on the forum but did not find anyone with a solution…

1000041725
10000417251344×2992 86.5 KB

1000041726
10000417261344×2992 122 KB

2

Did you pay attention to that?

image
image2050×326 69.4 KB

3

Checked the knowledge base as well?
https://support.homey.app/hc/en-us/search?utf8=✓&query=thread&commit=Search

4

Use the pair with Android method or iPhone equivalent

The Homey method isn’t ideal unless you’re right next to the hub

5

Thanks for all suggestions.

Tried it all, device is 2cm away from Homey. Wifi is not on 1, through homey or Android connecting does not improve..

So what to do?

6

I have a ticket about ikea matter products. Same screen, issue. It worked for a few weeks but then all collapsed after an “up”date. Don’t let anyone tell you it’s your problem or you should put more effort in this. Homey does simply not have this under control. Do not buy ikea matter until they do (hopefully permanent then)

7

Hi,
Just taken out of the box two brand new MYGGSPRAY sensors and no way to pair with HomeyPro 2026 :frowning:

8

I have 15 IKEA devices, all Matter over Thread, all working fine and actually performing much better since Homey firmware v13.1.

User error should always be the first concern.

9

Wifi is not on?

You need WiFi on to be able to pair using Android and it must be on the SAME LAN as your Thread network and SAME LAN as your Homey Pro.

If you’re using any kind of VLANs or different subnets, that could be the issue.

Alternatively, if you have Unifi access points, then it’s likely an issue with IPv6.

10

Did you find the KB link a few posts back?
There’s not just one way to add the devices. You need to know a few things.

11

Matter only works with Wi-Fi 2.4 so if you have muliple like I have 2.4, 5 and 6 you must change in the router or firewall to use only Wi-Fi 2.4 when you try to connect Matter.

13

MYGGSPRAY is a Matter over Thread device, so first communication is over bluetooth where sensor is paired and keys of HomeyPro Thread network are shared to the sensor, once this is done all later communication is over Thread. I don’t see a point with WiFi involved in here, except possible Thread interference with 2.4 WiFi channel 11.

14

Indeed didn’t check initially KB. However Android way neither is working, anyway I see MYGGSPRAY device in bluetooth discovered devices on Android. However during the activation with Android it stuck on communication over Thread with HomeyPro. My HomeyPro is using 5G WiFi, the same as Android device and when I check Thread settings in HomeyPro app I see border router available - yes.

15

Both my MYGGSPRAY are starting to behave erratically now

False positives, dropping off the thread mesh. Taking ages to re-pair.

Firmware must be bunk.

16

Same issue here, added to Homey once while homey is connected with ethernet. Put the Ipad on 2.4 wifi and add the sensor. Then within some days not working anymore. Can’t reconnect anymore. Added to the dirigera however these sensors will not be shared through the dirigera app in homey.

17

Just sharing my experience of pairing Myggspray with Homey Pro 2026. I have an Android phone, not an iPhone.

I have two Myggspray sensors. For the first one, I was able to pair it successfully as a Matter device without using any Homey app. However, the same could not be said for the second Myggspray, I kept getting the error of not finding the device. Eventually I used Homey official IKEA Home Smart app to pair it and succeeded.

18

I am also having this issue and have been for the last 2 or 3 weeks now, I am unable to add any of my 2x MYGGSPRAY motion sensors or my 3 x BILRESA remote controls.

My setup is as follows:

  • Homey Self Hosted running the latest 13.2.0 version running through a docker container in Windows 11
  • Samsung S25 runing current OneUI with a Homey app version 9.9.0.1954
  • Eero Pro 6 acting as a thread boarder router running firmware 7.14.1 with IPv6 enabled

Diagnostics:

  • My phone can see the thread border router when checking in the android settings
  • The phone can see the device and goes through the pairing process OK, except on the handoff back to Homey
  • In this last step I get a message in Homey saying "Could not reach the (Thread) network. Please restart your (Thread) router
  • The devices CAN be added without any problems to the Alexa app, they just won’t work with Homey
  • The devices HAVE worked with Homey in the past, they stopped a couple of weeks ago now

The logs from docker look like this:

homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:energy:getLiveReport
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:energy:getLiveReport → Success 200
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
homey-shs      | Homey [log][ManagerMatterLocal] [Pairing:0x3d9cc5a8] Start
homey-shs      | Homey [log][ManagerMatterLocal] [Pairing:0x3d9cc5a8] Got status update: SEARCHING (-0x01, Unknown)
homey-shs      | Homey [log][ManagerMatterLocal] Updating PAA certs
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204
homey-shs      | Homey [log][ManagerMatterLocal] [Pairing:0x3d9cc5a8] Starting pairing with ip
homey-shs      | Homey [log][ManagerMatterLocal] [Pairing:0x3d9cc5a8] Pairing to device...
homey-shs      | Homey [err][ManagerMatterLocal] [Pairing:0x3d9cc5a8] Finished with error: Could not pair node (Matter code: UNKNOWN (0x2000065))
homey-shs      | Homey [err][ManagerMatterLocal] [Pairing:0x3d9cc5a8] Could not stop pairing: Could not stop pairing (Matter code: INVALID_DEVICE_DESCRIPTOR (0x0033))
homey-shs      | Homey [err][ManagerMatterLocal] [Pairing:0x3d9cc5a8] Failed: Could not pair node (Matter code: UNKNOWN (0x2000065)) (at stage: unknown)
homey-shs      | Homey [log][ManagerCloud] Proxy GET /pair/vdevice/virtualdrivermatter/pair.js
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204
homey-shs      | Homey [log][ManagerCloud] Proxy GET /pair/templates/img/error.svg
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
homey-shs      | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204

I can upload a video of the Android pairing process if this is helpful