despite reading Matter Explained
I am struggling to understand how Matter device integration can work with a C8 hub.
Documentations says I need to commission advice with a Google Hub (which I don't have) and it can then be registered with my HE network, but what if any part does the Google Hub play after commissioning? I don't understand how the Google network (or Alexa or Apple for that "matter") links to the HE network - can anyone give me some clarity on this please?
The purpose of attempting to use Matter devices is pretty much all about the Eve (outdoor) Motion sensor - if there were a Z Wave outdoor motion sensor then I wouldn't even consider Google hubs.
After the initial commisioning you generate a fabric code for hubitat (or any other matter hub). Once that done google can drop off and you'll be fine. Though most people keep their google/alexa/apple device around for tts and voice control.
Now the above is for use with Matter over Wifi. Matter over thread is a bit different. For devices that are matter over thread you need a thread border router (like an apple homepod or tv or even a nanoleaf panel) to be in the mix. If you have only one TBR and that goes down, the device will fall off the fabric. If you have multiple TBR's it will be fine.
So, after commissioning, all comms with the sensor are to the HE? (a C7 in this case). It's remote to where any Google stuff (might) remain on a different wifi network so I was concerned that the Matter device would need to continue to see the Google Hub.
If that is all correct then I just now need to purchase a Google Hub of some kind ( - possibly just a Nest Mini maybe the display. Thought my Google Tablet would do the job via their app but no - needs to be a dedicated hardware hub for some reason. Not sure whether I want any Google stuff forming a 2nd HA tier but it's an option. Seems a nuisance to have to buy a hub to then abandon it but doubtless that works for Google!
It's to all matter controllers. They become a fabric of devices. (similar to a mesh).
Again, Google, Alexa, or Apple...(Personally I prefer Homekit as you get both a TBR for matter but TTS is easier as well with Hubitat)
That's because the app needs access to bluetooth for the initial onboarding and the tablet also doesn't have the ability to be a hub. Once Hubitat gives their app access to bluetooth you will be able to onboard matter devices directly to hubitat. (You will still need a TBR for matter over thread devices. Alexa and Google are not TBR's) Also people still want assistants with HE for Voice control and TTS.
Note: Your data and whatnot still goes back to the mothership with google and alexa. With Homekit (apple) it stays local, no cloud except for voice processing,.
Not sure that is exactly accurate. Govee devices for instance can pair directly to the Hubitat hub without Google/Alexa/Apple Home. Doing so presents a different challenge, but it is possible and it is without bluetooth.
It appears that the google Mini 2nd gen does also now include TBR after a software update?
(Based on AI response / a few Reddit users but Google don't seem to say so themselves!)
Yes, I had seen that and looked at the info from Google which has possibly not been updated.
It is not at all clear whether it is a TBR or not. Not confidence inspiring....
If I go the google route I will probably get the 2nd gen display but lacking in confidence about product continuity from google and the so called customer support is appalling.
I am going with your version - I don't trust the ambiguity on this product range.
In order to feature Thread, a software update is not enough. It would also require the proper hardware to be present on the device, which I don't think the mini has.
I'm with you about Google bad habits, but I have discountinued and no longer supported devices from google and partners. They still work fine.
If you don't need Thread, the mini can commission Matter devices over wifi. As for TBR, there are other company then the ones mention earlier: Smartthings, Tuya, maybe more.
Wow, a (slightly chaotic) voyage of discovery here....
So I have a 2nd Gen Google hub and after a few issues managed to pair the Eve Motion sensor with the my HE C7 and motion was being correctly sensed. Hooray. But to achieve the pairing I had to move the Google hub to my external wifi network as it's out of range from my house and that's where the HE C7 is installed. However when I shutdown the Google hub the Matter motion sensor device stops responding in the HE interface!
Does the Matter device need continued access to the TBR in the Google Hub AFTER pairing? I thought not based on previous posts but it would make sense...
And if yes then can they sit on 2 different wireless networks (that share the same private class c LAN)????
It's a lot to take in but not keen on this if there is a dependency on the Google Hub.
I hope somebody can follow this as I need to sit in a darkened room for a while !!!
Thread and Matter are two different things. They are related in the sense that Matter can use Thread to control devices.
Look at it like wifi. If you turn off your wifi router, you would not expect your wifi devices to stay accessible. So turning off the TBR (in this case the Nest hub) sever the connection to your Thread device. (unless there is another TBR on the mesh to take over)
Yep, that's what I was figuring.....
I hadn't taken that in at first, thought the HE C7 could communicate directly after commissioning but if it can't route thread then it's not going to communicate without the Google Hub and that makes perfect sense -now!
Options are to extend my home wifi (abandon the secondary wifi network which is a plus anyway) or again give up a reliable outdoor motion sensor!
Sending Google Hub & Eve Motion sensor back to retailers. I just decided there is too much additional hassle and equipment to justify use of an outdoor motion sensor even though after I got it working correctly (which was largely down to the issue with multiple SSID wifi networks). I can continue to live without voice activation and the inherent privacy concerns.
Just too much pain and I remain uncomfortable with the way my data is being pushed around by the likes of Google so the HE solution still works for me.
There just has to be a better way to get an outdoor visitor detection - camera with reliable detection feature???
For thread based matter anyway
