Matter homekit incompatible devices with 2.4.0.144

I have 3 matter light bulbs that were working just fine in 2.3.9 that now are listed as incompatible devices in the HomeKit page after upgrading to 2.4. They work fine from hubitat but cant be added to HomeKit and the old devices show "not responding" on the Home app.

Matter devices have not been allowed in the HomeKit integration for about a year now, though it's possible existing devices you may have integrated that way would have continued to work. This is because you can integrate Matter devices directly into HomeKit without going through Hubitat (and it prevents problems that can ensue from doing this in a circle).

3 Likes

Wow this is news to me, Im sure I only added these matter bulbs a few months ago.

So what would be the procedure to fix this? I remember needing to use the home app to put them in pairing mode and then pairing them to hubitat. So I would need to delete the devices from hubitat and re-pair them direct to the Home app? How do I then see them in hubitat to automate them etc? I guess it will break all the rules and automations when I move them over.

Didn't your first sentence say you already commissioned them with the Home app? In that case, they are already there (pairing them also to Hubitat doesn't change that--unless maybe you removed them from Home afterwards for some reason, in which case it's not clear why since it sounds like you want them in Home). I'd check this first.

Otherwise, yes, resetting and re-pairing them will make them appear as new devices to Hubitat, so you'd need to swap them out in any apps you'd be using. But you'll get a "Replace" option when you add the new devices, or you can use the "Swap Devices" tool after the fact, so with a simple (non-parent/child, where this won't work) device, it won't be that bad.

I thought the procedure before was to detect them and put them in pairing mode with homekit, then actually pair them on Hubitat, not homekit. So they dont exist in Home, only by the hubitat homekit integration.

So when I reset and pair them in Home, how do they now appear in Hubitat? I thought the homekit integration went the other way, ie expose Hubitat devices to Homekit. How are Homekit devices exposed to Hubitat?

No, this was never possible. You have to add them to Home first, which is technically commissioning the device and pairing it to Home (same step, as most hubs don't let you separate the former from the latter if you're setting up the device the first time). Then you use Home, which you've added the device to, to turn on pairing mode and get it added to Hubitat that way.

See: How to use Matter on Hubitat Elevation | Hubitat Documentation. The procedure is documented here, and one of these would had to have been what you did.

This is correct (but not what you want in this case -- and the fact that you can't is probably saving you from the problem I mentioned in the first post).

If they support Matter, you follow the above procedure. HomeKit devices in general are not all supported this way, just Matter devices that Apple Home(Kit) also allows you to use since such devices are also directly compatible with it -- and, unlike HomeKit-only devices, also other systems.

2 Likes

OK it's sorted now, thanks. I reset the bulbs with on/off 6 times, newly added them to Homekit, then added them to Hubitat where I was able to use Replace easily. I also removed the old devices from Homekit. Now everyone is happy. Strange how I got into that pickle in the first place. Thanks for the assist there.

2 Likes

Ok this is interesting/weird, initially all 3 matter bulbs were showing not responding in the Home app, I re-paired the first one as I described, and now all 3 are back to responding without needing to re-pair the other two. When I removed the old "not responding" lamp entity from homekit, it said it was removing something called "matter test", maybe this was the issue. This newfangled matter sure is confusing :upside_down_face:

That sounds like the list of other systems you have the device added to, and it was likely Hubitat (or anything else that might be using a similar ID, which Hubitat does not currently have one of its own for yet).

You might have just been having an odd device problem that "restarting" the device could have helped with, or if it's a Thread device, possibly restarting your TBR (HomePod or AppleTV, most likely). Hubitat doesn't actually go through Home, so you may have also found that they would still work on Hubitat but not Home or vice versa -- though ideally, never not either (still a bit early in Matter :slight_smile: ).

In any case, glad you have things working!