Help me understand Matter

I'm still trying to wrap what little brain I have around Matter and Hubitat.

From what I understand, there was to be a Matter Hub, such as a Nest Hub Max. If I have a Matter/Thread enabled lock, I would pair it with the Nest Hub Max. Would I then be able to pull it into Hubitat?

1 Like

In general, yes, that is currently the process. This document will explain more:

However, there are currently no Matter lock drivers for Hubitat. So until that changes, the answer to your specific question is no. Here is a list of all know compatible devices, though many more work with community drivers if you are comfortable with those:

2 Likes

Thank you! I will wait on the lock...for now.

Yes. Right now Hubitat is incapable of commissioning a matter device directly until the mobile app gets access to the blue tooth radio in your phone. Until then a matter device first must be commissioned by something like an apple homepod, google speaker, alexa. Once it's commissioned a code then can be generated and that device connected to hubitat. (It can be removed from the original matter controller at any time). Now matter over thread devices require a thread border router (TBR) such as a Homepod. That has to remain in place for those devices (unless you have another hub that can be a TBR)

Hopefully that will arrive somewhat soon. Should make using Matter devices w/HE much simpler.

1 Like

I checked out the Nest Hub Max out of curiosity, and I was surprised to find that it is a TBR, since curtman3 didn't specifically mention Thread.

Does that mean Thread devices on the Nest Hub Max can be exposed to Hubitat via Matter, since the Nest Hub Max is Matter controller as well?

1 Like

yes. If you can commission a device to the matter fabric it can be installed on hubitat. However if that is the only TBR in the fabric for matter of thread devices, you can't remove it from the TBR like you can remove regular matter over wifi devices from another hub,

Good to know, I just can't see any reason to add Matter or Thread into the mix for now, but good for future possibilities.

Careful...talk like that will get you banned from this forum. A certain level of irrational "Must try everthing..." behavior is required to hang out here. :wink:

1 Like

Perhaps the Beta group would be more appropriate for this behavior.

Honestly most of us have a smattering of everything. I have 60 odd clear connect, about 60 zigbee and 50 z-wave devices. 8 or 9 wifi, umpteen virtual and and 5 or 6 matter devices (2 are blue tooth). All run pretty harmoniously. (Well till a device decides to crap itself lol)

1 Like

That's why I was curious about the Matter integration. I have a mix bag of Zigbee and Zwave, however, there's a lock I'm interested that's integrated with Google via Matter. I was wanting to run some rules on the lock, hence the integration to Hubitat with Matter.

Short story long, it's nice having the OPTIONS of being able to use other technologies, especially when there are no other options available.

With respect to Thread devices... I just want to point out that Thread devices existed before Matter was even a specification. Thread is a RF communications layer, similar to Zigbee and Z-Wave. There were "Apple HomeKit over Thread" devices, for example, that are not "Matter over Thread" devices.

The older non-Matter Thread devices cannot be 'shared' with Hubitat. Only "Matter" (WiFi/Ethernet) and "Matter over Thread" (with a requisite Thread Border Router (TBR)) can be shared from another Matter Controller to a Hubitat Hub.

4 Likes

That is how I look at it. I'm not opposed to Thread and Matter, I just have not NEEDED them yet to connect a device. It is nice to know there is the option though.

Right now for me it is mostly Zigbee, then Zwave, then a few wifi devices and some cloud integrations for Roborock, etc. Also a few devices from Home Assistant Device Bridge, and quite a few virtual devices, probably more than I have Zwave devices. Hubitat currently reports 338 devices total.

Yeah, I read up on Matter once, and Apple was one of the main companies that wanted a unifying protocol, to allow non-apple devices into their Thread based ecosystem.

Currently Hubitat does not support matter locks. (It will in the future). In the mean time you could control them on google from hubitat via virtual switches.

1 Like

Uh, if you know anything about Apple, its NEVER about allowing ANY non-Apple devices into their ecosystem.

1 Like

Actually, IMHO you are really misrepresenting Apple in this particular case. Apple has been leading the way with Matter and Matter over Thread. Apple helped to design and develop the Matter standard, which is Open and is used by a large number of manufacturers, large and small. My Matter devices have been easily shared from Apple Home to Hubitat and Home Assistant. Apple does not even make/sell any Matter end-devices (sensors, switches, locks, appliances, etc...), yet they allow any Matter device to be connected to their platform, and shared with other platforms (e.g. Google, Amazon, SmartThings, Home Assistant, Hubitat, etc...)

3 Likes

I'll agree to disagree, or perhaps restate. Its not an altruistic advance of non-apple devices into their network, its a way to push Apple devices through and into non-apple ecosystems.

I'm not making any case here, just noting the intent. The rise and fall of the Lightning connector tells you everything you need to know.

No, I don't think it was altruistic. It was purely a business decision. They tried to apply their concept of a closed ecosystem to their home automation early on, but then realized where home automation was going, it was not with totally closed systems.

That is why they were a founder of CHIP and really wanted Matter to make their systems able to compete in the market.

1 Like