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.
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
@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
