Thread comes to Hubitat

[donkrell]

@ogiewon

Thus, this leads me to the hypothesis that using the Hubitat Mobile App on an iPhone/iPad, assuming Apple Home is set up and already has a Thread network, that all MoT devices will use the Apple Thread network instead of the Hubitat Thread network

ogiewon:

Has anybody tested using the Hubitat IOS lately to determine if the app still pairs devices to the Apple thread network rather than the Hubitat network?

[ogiewon]

@donkrell

Has anybody tested using the Hubitat IOS lately to determine if the app still pairs devices to the Apple thread network rather than the Hubitat network?

I have not tested it recently. However, @mike.maxwell has mentioned in a few posts above that the this is not a high priority right now for Hubitat Mobile App development process (IIRC .)

Found it...

Thread comes to Hubitat

Yes, we understand, this requires a not insignificant change to both of our mobile apps, They are currently on a separate unrelated development cycle, when that is finished, we will likely review an implementation. For now we are concentrating on matter's 1.6 version which supports TBR discovery and key sharing without going through the current 1.5 mobile device keychain workarounds...

and

Thread comes to Hubitat

We can stop complaining about the spazplatz commissioning and Hubitat, the root cause has likely been identified and for reasons already explained resolving this devices issues with Hubitat isn't in the current workflow.

[donkrell]

Ok thanks. I will continue to use the web interface.

[ogiewon]

Not sure if you’re aware… If you use the Hubitat web interface via a web browser on a smartphone, when pairing Matter devices, you’re given the option to use the phone’s camera to scan the Matter QR code during the pairing/commissioning process. Very handy!

[donkrell]

Ogiewon:

I'm old fashioned. I think I can still manage to type 11 numbers. If I make a mistake the check digit will tell me.

[HAL9000]

@donkrell

I'm old fashioned. I think I can still manage to type 11 numbers. If I make a mistake the check digit will tell me.

True that, but not all Matter devices have the setup code on the device itself.

[mike.maxwell]

There is an advantage to using the QR code since it includes information that determines how to specifically commission the device, ie WiFi/lan/bluetooth. The numeric code does not include this data, so matter ends up trying each one until it succeeds. You can see these gyrations in the matter log when using the numeric code vs the qr

[GuyMan]

@mike.maxwell

the QR code since it includes information that determines how to specifically commission the device

Thx! - I didn't know that - Did a bit of digging, and: Matter QR codes explained: What happens when you scan one? | Matter Alpha

[donkrell]

@mike.maxwell

There is an advantage to using the QR code since it includes information that determines how to specifically commission the device, ie WiFi/lan/bluetooth.

Mike:

Does entering the QR text in the Matter add device web page accomplish the same thing as scanning the QR code? I'm referring to the long QR text,,, not the 11 digit setup code. I have carefully avoided using my iPhone app AT ALL because of the problem of adding the device to the Apple Homekit thread network rather than the Hubitat network.

[donkrell]

Mike:

I decided to test entering the QR text instead of scanning the QR code or entering the 11 digit setup code. I chose a Matter/wifi device I had laying around as the test device.

I have a hunch this option is seldom (if ever) used. I pasted this code: MT:MVAA0EDB00ILO44CF10 into the Add Matter device dialog. I DID NOT paste where the setup is entered but into the Hubitat QR Scanner page. I got an invalid code message that is the same message one receives if the 11 digit setup code is fat fingered. The Verhoeff check digit shuts down the transaction quickly.

But the code I entered is legitimate. I asked ChatGPT to decipher it. AI did decipher it and spit out data that includes the correct 11 digit setup code. I think the Hubitat QR Scanner dialog may be interpreting the QR text as a setup code.

[ogiewon]

@donkrell

I have carefully avoided using my iPhone app AT ALL because of the problem of adding the device to the Apple Homekit thread network rather than the Hubitat network.

Agreed. This is a good idea to prevent MoT devices from being added to the wrong TBR.

@donkrell

Does entering the QR text in the Matter add device web page accomplish the same thing as scanning the QR code? I'm referring to the long QR text,,, not the 11 digit setup code.

Was this just a technical curiosity you're trying to solve? If so, please ignore the rest.

If not, did you try my suggestion of simply using a web browser on your mobile phone to open the Hubitat Hub's "add a Matter device" page? Doing so lets the user use the phone's camera to scan the QR code on the MoT device. This method avoids using the Hubitat Mobile App altogether, and thus ensures the MoT device you're pairing/commissioning uses the Hubitat C8ProT hub's TBR.

[donkrell]

@ogiewon

Was this just a technical curiosity you're trying to solve?

Yes it was technical curiosity. I don't plan on adding enough thread devices to require a streamlined procedure for adding them.

I did a test of using the QR text string (not the setup code) to add a device. See my post this morning to Mike Maxwell. I couldn't get it to work.