Issue with Matter on self hosted Homey

Hi everyone, I’m having an issue with an new IKEA Matter device.

I have a self-hosted Docker setup running on a Synology NAS, with a Thread border router via an Apple TV connected to the same network.

When I try to add a device, the setup goes smoothly until the naming step. Then, the screen stays stuck for about 10 minutes before timing out.

I’ve tried 4 or 5 times, resetting the device each time, but nothing works.

Does anyone have any ideas?

From within the Homey mobile app which option did you pick? I expect it might have something to do with that, although I haven’t played with HSG myself yet. Connect via Homey Pro or Connect via Android or iOS, the latter option will connect it to your phone’s preferred thread network, in this case your Apple TV.

The first option wouldn’t work since your HSH hardware won’t have any hardware to support thread. So if you’ve been trying to add it via the homey option every time, try the other one.

I have also issues. When using the share code from any other matter device, It works till the screen that it tries to communicate with the device and then error 0x00ce (I believe) and then no device.
Tried it many time, connected thru Apple (IOS) and not Homey!

Matter requires a proper IPv6 setup of your server and your Docker environment.

The NAS runs ipv6 , and the docker is running in network mode HOST so there is ipv6 then.

1 Like

You can not share devices from Apple (or anything) TO Homey (afaikat).. there is no option to select if the device is new or already in use.. connect first to Homey and share it from there to other places

Easiest is to add the Matter Bridge app instead of sharing it with pairing codes.. this way you can also easily share Zigbee and other devices.

My idiotic setup.. Homey SHS and Homey Bridge, add matter devices to Homey, then use the Matter Bridge app to share it with Home Assistant, from there share the Matter Bridge with Apple Homekit.. works freaking well

1 Like

@Waldo Thank you for your reply. Actually, I can’t select that option when adding the device in question. Perhaps this is a limitation of self-hosting?

This is the error I get when trying to connect to the matter device.

(works on Homey Pro, and Homekit, but not on SHS with ipv6 enabled)

homey-shs | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
homey-shs | Homey [log][ManagerMatterLocal] [Pairing:0x1908be3b] Start

homey-shs | Homey [log][ManagerMatterLocal] [Pairing:0x1908be3b] Got status update: SEARCHING (-0x01, Unknown)
homey-shs | Homey [log][ManagerMatterLocal] Updating PAA certs
homey-shs | Homey [log][ManagerMatterLocal] DCLs: https://on.dcl.csa-iot.org. Git: false

homey-shs | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204

homey-shs | Homey [err][ManagerMatterLocal] [Pairing:0x1908be3b] Finished with error: Unknown error (Matter code: INTERNAL (0x00ac))
homey-shs | Homey [err][ManagerMatterLocal] [Pairing:0x1908be3b] Could not cleanup pairing: Unknown error (Matter code: INTERNAL (0x00ac))
homey-shs | Homey [err][ManagerMatterLocal] [Pairing:0x1908be3b] Could not stop pairing: Could not stop pairing (Matter code: INCORRECT_STATE (0x0003))
homey-shs | Homey [err][ManagerMatterLocal] [Pairing:0x1908be3b] Failed: Unknown error (Matter code: INTERNAL (0x00ac)) (at stage: unknown)
homey-shs | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
homey-shs | Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204

Did you find a fix?

No , it just does not work, I will wait for an update of the SHS, must be some first-start issues. We are not the only ones, so it is not something we did wrong.

I have this issue as well on my SHS, cannot add my Govee AI Sync Box 2 to Homey :frowning:

I’ve used HASS for a looong time, but now with SHS, I finally started using Homey. Most of the stuff looks nice and clean, so off to a good start :slight_smile: But, SHS should work with Matter, but i cannot install Matter devices/bridges.

Getting this error in the log after connecting:

Homey [err][ManagerMatterLocal] [Pairing:0x10f2d765] Finished with error: Unknown error (Matter code: INTERNAL (0x00ac))
Homey [err][ManagerMatterLocal] [Pairing:0x10f2d765] Could not cleanup pairing: Unknown error (Matter code: INTERNAL (0x00ac))
Homey [err][ManagerMatterLocal] [Pairing:0x10f2d765] Could not stop pairing: Could not stop pairing (Matter code: INCORRECT_STATE (0x0003))

The unknown part not really helping here. Any ideas how to look further or what this could be?

Search around on the forum, you’re not alone.

My IPv6 setup was not correct. I corrected it. Let’s asume I am right, and the setup is correct in my network and in the dockers. Adding matter devices is not working.

Can anyone confirm that at this moment:

Homey‑SHS currently binds only to IPv4. Even in host mode, Docker cannot “force” an app to use IPv6. Homey‑SHS itself is not opening any IPv6 listeners. This is an application‑level limitation, not a Docker or host issue, thus we

Wait for Athom to add IPv6 listeners to Homey‑SHS.

Matter doesn’t require Homey-SHS to open ports on an IPv6 interface, discovery is done using mDNS and it’s Homey that connects to the devices. It’s irrelevant if Homey-SHS binds its webserver to IPv4 only.

Thank you :+1:t3:

Still driving me nuts. I cannot get any Matter device connected to Homey. It always ends in 0x00ac. unable to connect internal (0x00ac).

I’ve bought different devices, the most recent is the shelly 1 gen 4. The idea was that it does not required a hub to update the firmware. I started with the matter devices from Ikea, but I do not have an ikea hub, so maybe these ikea devices miss a required firmware update or something :man_shrugging: . Then I tried Switchbot smartplugs. I was able to connect the Switchbot devices to Homey, but I wasn’t really certain it was via Matter… Adding them was a weird process and it took a zillion years for them to get detected.

The Shelly wanted to update the firmware on its own, since I connect it via Wifi to the internet. That worked. The Gen4 versions can connected via Wifi , Zigbee and Matter. I tried Matter, and the first time I tried, all worked like I would have expected. Fast responsive “next-next-next”… great, until the final step. After it says, devices added to Homey :partying_face: I get the next screent that says: unable to connect internal (0x00ac)
(sad trombone) :face_with_bags_under_eyes:

I tried to add it to Homekit (AppleTV or Homepod)… works as expected. :partying_face:
Enabled “Paring Mode” in Homekit and tried to add it to homey.

Same result… unable to connect internal (0x00ac). :distorted_face:

Where should investigate?

Homey Self-Hosted Matter-over-Thread - Matter pairing 404 error: "PairSession with ID ... Not Found" - #3 by Quaasteniet same problem

I can check the logs on the Shelly easily when I scan the Matter QR code… Everything works fine on the shelly side. Shelly finishes, and then I see the Unable to connect on my iphone.

Today I paused all policies I have. Any that could block any is now off.
Reboot… same error.

The only thing that I did notice is that Shelly does not display the QR code anymore after this; it states: The device is commissioned to 1 fabrics. Reset the Matter to remove the device from all fabrics.

Even though there is no mention of the Shelly device in Homey anywhere…

Shelly Log

Connected.

13:37:44

shos_init.c:103         New min heap free: 126744

13:37:32

shos_init.c:103         New min heap free: 124736

13:37:32

shelly_debug.cpp:236    Streaming logs to 192.168.x.x

13:37:32

shos_http_client.cp:656 0x4085fd8c: Finished; bytes 926, code 200, redir 0/3, auth 0, status OK

13:37:33

shelly_notification:164 Status change of sys: {"available_updates":{"beta":{"version":"1.7.4-beta2"}}}

13:37:33

shos_rpc_inst.c:223     No handler for shelly.listalternatives

13:37:33

shos_matter_server.:297 Commissioning started

13:38:05

shos_matter_server.:333 Commissioning window closed

13:38:05

shos_matter_server.:352 Fabric updated

13:38:06

Matter-DL:1             Long dispatch time: 279 ms, for event type 3

13:38:06

shos_dns_sd_respond:236 ws(0x4084211c): Announced A085E3B56E24 any@any (Shelly IP4 192.168.x.x)

13:38:08

shos_dns_sd_respond:236 ws(0x4084211c): Announced A085E3B56E24 any@any (Shelly IPV6)

13:38:08

Matter-DL:1             Long dispatch time: 115 ms, for event type 2

13:38:09

shos_matter_server.:348 Fabric committed

13:38:10

Matter-DL:1             Long dispatch time: 402 ms, for event type 3

13:38:10

shos_matter_server.:333 Commissioning window closed

13:38:10

shos_matter_server.:257 === Commissioning complete

13:38:10

Matter-DL:1             Long dispatch time: 189 ms, for event type 32783

13:38:10

Matter-ZCL:1            Commissioning window is currently not open

13:38:10

shos_matter_server.:329 Commissioning window opened

13:38:10

shos_dns_sd_respond:236 ws(0x4084211c): Announced A085E3B56E24 any@any (Shelly IP4 192.168.x.x)

13:38:13

shos_dns_sd_respond:236 ws(0x4084211c): Announced A085E3B56E24 any@any (Shelly IP6)

13:38:13

shos_init.c:103         New min heap free: 124360

13:38:33

shos_init.c:103         New min heap free: 124232

13:38:36

Matter-SWU:1            No suitable OTA Provider candidate found

When I reset fabric and add it via Homekit all is well:

Shelly Logs

Connected.

13:51:46

shelly_debug.cpp:236    Streaming logs to IPv4:59712

13:51:34

shos_rpc_inst.c:243     matter.getsetupcode [29@acff3ded-e76b-4f6e-a17a-bf913c55c0b9] via WS_in IP v4:58404

13:51:35

shos_dns_sd_respond:236 ws(0x408421fc): Announced Shelly1G4-A085E3B56E24 any@any (Shelly IPV6)

13:51:36

shos_dns_sd_respond:236 ws(0x408421fc): Announced A085E3B56E24 any@any (Shelly IPV6)

13:51:36

shelly_update.cpp:355   Checking for updates (1.7.1 20250924-062804/1.7.1-gd336f31 {"bl":16777983,"t":1767358300.977,"ut":18194419,"hf":137720,"hmf":122072,"fs":917504,"fsf":446464,"pkw":0})

13:51:41

shos_http_client.cp:316 0x40861d80: HTTPS GET https://updates.shelly.cloud/update/S1G4?src=auto1 (CA shelly_cloud.pem,ca.pem)

13:51:41

shos_http_client.cp:656 0x40861d80: Finished; bytes 926, code 200, redir 0/3, auth 0, status OK

13:51:41

shelly_notification:164 Status change of sys: {"available_updates":{"beta":{"version":"1.7.4-beta2"}}}

13:51:41

shos_rpc_inst.c:223     No handler for shelly.listalternatives

13:51:41

shos_bt_nimble_gatt:365 CONNECT 47:35:2d:93:3c:fd,4 ch 0 st 0 AM 500 M 23

13:51:47

shos_matter_server.:297 Commissioning started

13:51:48

shos_matter_server.:333 Commissioning window closed

13:51:48

shos_bt_nimble_gatt:391 DISCONNECT 47:35:2d:93:3c:fd,4 ch 0 reason 531

13:51:48

shos_matter_server.:352 Fabric updated

13:51:49

Matter-DL:1             Long dispatch time: 270 ms, for event type 3

13:51:49

Matter-DL:1             Long dispatch time: 282 ms, for event type 2

13:51:50

shos_dns_sd_respond:236 ws(0x408421fc): Announced A085E3B56E24 any@any (Shelly IPV6)

13:51:51

shos_matter_server.:348 Fabric committed

13:51:51

shos_dns_sd_respond:236 ws(0x408421fc): Announced A085E3B56E24 any@any (IPv4)

13:51:51

Matter-DL:1             Long dispatch time: 416 ms, for event type 3

13:51:51

shos_matter_server.:333 Commissioning window closed

13:51:51

shos_matter_server.:257 === Commissioning complete

13:51:51

Matter-DL:1             Long dispatch time: 323 ms, for event type 32783

13:51:51

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_0028, err = b

13:51:51

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_0031, err = b

13:51:51

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_003C, err = b

13:51:51

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_003F, err = b

13:51:51

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_001D, err = b

13:51:51

shos_matter_server.:352 Fabric updated

13:51:52

Matter-DL:1             Long dispatch time: 210 ms, for event type 3

13:51:52

shos_dns_sd_respond:236 ws(0x408421fc): Announced A085E3B56E24 any@any (Shelly IPv4)

13:51:53

shos_dns_sd_respond:236 ws(0x408421fc): Announced A085E3B56E24 any@any (Shelly IPv6)

13:51:53

Matter-DL:1             Long dispatch time: 217 ms, for event type 2

13:51:54

shos_matter_server.:348 Fabric committed

13:51:54

Matter-DL:1             Long dispatch time: 310 ms, for event type 3

13:51:54

shos_matter_server.:257 === Commissioning complete

13:51:54

Matter-DL:1             Long dispatch time: 245 ms, for event type 32783

13:51:54

Matter-DL:1             Long dispatch time: 127 ms, for event type 2

13:51:56

shos_init.c:103         New min heap free: 121944

13:51:56

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_0028, err = b

13:51:57

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_0031, err = b

13:51:57

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_003C, err = b

13:51:57

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_003E, err = b

13:51:57

Matter-DMG:1            Error retrieving data from clusterId: 0x0000_0004, err = b

13:51:57

shos_init.c:103         New min heap free: 119544

13:51:57

shelly_notification:164 Status change of switch:0: {"output":true,"source":"matter"}

13:52:28

shelly_notification:164 Status change of switch:0: {"output":false,"source":"matter"}