Platform 2.5.1.174
New Mater over Thread device provisioned in Apple Home. Pairing code generated by Apple Home. On Hubitat - add device/matter entering the code, but 'Start pairing' button is greyed out.
What am I missing?
It used to be a trivial thing on C8 Pro (non Thread), although several platform versions back. All my Matter devices were paired that way.
Any ideas?
Did you enter your Wi-Fi credentials in the inputs right above this?
(I know that sounds weird if you know it's a Thread device, but the hub doesn't have a way to tell before it has the code, and if you're doing it from the hub's web UI, this was the most straightforward way to have those available if needed.)
Thanks bertabcd1234
No, I did not enter Wi-Fi credentials. My hub (as well as Apple TV TBR) does not even aware of Wi-Fi existence. It is all ethernet.
On top of that, it was a simple task on my previous hub - same network structure, no Wi-Fi credentials were required.
Your Apple TV can obtain your Wi-Fi credentials and can just share them with Matter over Wi-Fi devices when commissioning if needed. The Hubitat mobile app can also get them from Apple's APIs (though I wouldn't suggest the mobile app for Thread devices at the moment since it apparently also likes to take Apple's TBRs instead of your hub). The Hubitat hub via the web interface can't, so you'll have to enter them here for pairing/commissioning to become available.
This is related to platform version, not hub hardware; platform version 2.5.1+ can commission Matter devices directly from the hub's web interface, so the new fields are necessary when doing this. (It also doesn't have a way to know if you're just pairing or actually commissioning a new device, since you wouldn't need them for the former, either, but requiring them period was apparently the most straightforward way to avoid problems.) Old versions could only pair a "shared" (in-pairing-mode, already commissioned) device.
Thanks, it worked
Obviously I don't know much about provisioning Matter over Thread/Wi-Fi protocols, but to me it sounds strange. Anyway, my problem solved - thanks!