They sent men to the moon with engineers relying on slide rules and some very smart human calculators. They also employed some Sinclair personal computers and mainframe computers. Today, our cell phones have far more computing power, but it still takes very smart humans working with computers to place humans in low earth orbit and bring them home safely.
How does the "Matter Bridge" driver get installed? For the life of me, I can't get my Home Assistant Matter Hub to finish setup on Hubitat. It will not commission the device in Hubitat at all (it's an entirely software device, so no Bluetooth necessary on a mobile device), and while it commissions perfectly fine on Google or Alexa, and the sharing code won't work with Hubitat either. It's like Hubitat just has no idea what to do when trying to add the bridge.
I didn't know about Matter bridge on Hubitat. It indeed would be a cool feature, such HomeKit integration.
Is it released to everyone?
The "Matter bridge" is currently installed from Hubitat Package Manager (HPM). It's called Matter Advanced Bridge. It allows you to add Matter devices from other hubs. Those hub's may convert their 'non Matter devices' to Matter. They often do not convert.
I don't see a "Home Assistant Matter Hub" in my Home Assistant install - I do have a HA Matter Server though and It can share matter devices with other hubs.
It is a rework of the older "Matter Bridge" add-on for Home Assistant. It is currently in "alpha" stage, although it seems to work beautifully with both Google Home and Alexa. It basically allows me to take any device or entity from HA with a matter-compatible component to it and share it as a matter device to any other ecosystem that supports Matter. Except Hubitat apparently. It's the only system so far that flat out refuses to commission it or accept it as a shared device from Google's Matter network...
1 Like
Please be aware that Hubitat now natively supports adding "Matter Bridge" devices without the need for community developed software. I am not saying that Hubitat's built-in software is better or worse than @kkossev's solution. Just stating that one may want to start with the built-in solution before assuming the need for 3rd party software. For example, Hubitat's built-in Matter Bridge supports includes adding a Philips Hue bridge as a Matter Bridge to Hubitat. This then exposes all of the lights, motion sensors, etc... as devices on Hubitat.
That being said, I have yet to be able to add the Arduino "Nano Matter" device to Hubitat. It is a Matter over Thread device, which presents itself as a Matter Bridge. I have it paired with Apple Home. However, when I try to share it from Apple Home to Hubitat, it is never successfully added to the HE hub. Sounds similar to what @a.mcdear is experiencing trying to add HA's Matter Bridge device to Hubitat.
1 Like
Yup. I have an ESP32C6 running a Swift dimmer example that works with Homekit and Home Assistant but not Hubitat. I could attach a terminal for logging and look at the Swift and C++ code to see where the problem might be but that would require effort and thought. I can't blame Hubitat until I've at least looked at the code. Maybe it's alpha quality. 
1 Like
I can't get it to run in docker -- it seems to hate the -volumes entry. I've spent way to much time trying to get it working. Nice idea if and when it works.
Yes, at the moment it is quite finicky. Before you have a chance to configure it, it attempts load EVERY entity from HA into it, and when there's something that it can't figure out how to make a matter compliant device for, it crashes hard. I had to write a config file to force it to ignore all entities at first and only try to include a select few that I knew would work, like a switch or a bulb. Once I got it running, I was able to use it's own tools to include/exclude the items I wanted.
I'm sure there will be a GUI for all that eventually, but for now you have to set it up pretty manually.
What does Matter need to commission devices that Hubitat has put off doing?
