[RELEASE] Matter Advanced Bridge (limited device support)

Having the Dirigera bridge successfuly paired to HE as a Matter means that your LAN settings are OK. You should be able to pair also other Matter devices that are initially commissioned with the Dirigera TBR..

Which code are you entering in Apple Home (also in Hubitat) ?
It should be the NEW code generated by the IKEA Home app, not the original one printed on the IKEA gadget.

I’ve been using the new codes generated by the ikea app.

I downloaded all of the drivers you have posted and for whatever reason, the pairing process worked perfectly today. I followed the exact same process (generate and copy code in ikea app, add matter device and paste number in Hubitat app) that I’ve used on several different occasions but today it worked.

Bottom line is that everything seems to work now. Thanks again for your help and the work you put into the drivers.

1 Like

I found the article I had been searching for over the past few days.


1 Like

OK, after getting regular matter devices working, MAB seems to have mysteriously stopped working with my ikea hub. I’ve tried rebooting both hubs with no luck. The logs for the devices that aren’t responding don’t show anything helpful but the log from the ikea hub device shows errors.

Any suggestions on what is wrong?

Also, my matter over thread devices have stopped working as well.

I knew alot of this, and I’ve even seen Fabric conflicts in my own home, with devices have multiple ULA (unique address), that cause routing conflicts for replies. - That all said, I did NOT know about the “healing times” and waiting 30-60 mins before rejoining a network.

My issues have been with HE unable to contact a Matter device, but AppleHome still working, so I’ve not had to do the full factory reset of an endpoint device, rather just remove it from HE, and then re-provision it, with the Apple pairing code. - Something is still different in the AppleHome code versus the HE Matter stack, in that Apple Home seems to “always work”.

Anyways, your link was a helpful article, so thanks for sharing!

1 Like

Best to not know about it IMHO - it’s folklore, just like Zigbee “mesh settling”.

3 Likes

@Pat-C - Did you solve the Dirigera Matter connectivity problem?
For some reason, it was not reachable from your HE hub. The 'Queue full' error message in the logs is due to the Ikea bridge not responding to the periodic ping() commands...

Yes, I did finally resolve it by powering down the ikea hub for about an hour and afterwards ran the discover all command again. Thanks for clarifying what the logs meant.

1 Like

I wanted to post a thank you to @kkossev for this great driver.

I recently received a Rachio Smart Lighting Controller (after waiting for almost a year) and using this driver I was able to add the controller into Hubitat and immediately integrate it into my house automations.

1 Like

@kkossev - do you think there’s a way to bring in switches’ labels when importing devices from Aqara hub (G3) with MAB ? I have several switches (all labeled in aqara app), but when bringing them in to HE they all are recognized as “Aqara wall switch EU” if using general matter bridge or just ‘Switch’ when using MAB.

Manually re-labeling doesnt help much as when adding another device and refreshing / rediscovering, they all go back to ‘switch’

1 Like

Hi @redpaw ,

This has been on my TODO list for quite a long time... Not easy to implement, as the multi-component devices (as the Aqara Wall Switches) are presented in the Matter protocol as a complex bridged devices of an 'Aggregator' type, with its own nested list of child devices ('parts'), which user set lables are presented in another way, much more complex than the simple devices.

This shouldn't happen with the MAB. Existing child devices should not be touched when doing a re-discovery... Can you test again?

1 Like

Yikes, that doesnt sound promising. But if they should keep their names, that would be good enough. I’ll try do test it again this week… it’s a bit of a mess with duplicating devices created by different bridges and will have to go through all the automations to remember what i need to recreate when all is deleted. But had to do it anyway, so just need to find some time to do that.
Will let you know as soon as i test it, thanks.

1 Like

Making the Matter Advanced Bridge package compatible with the HE stock 'Generic Matter Bridge' driver now doesn't sound impossible!


There is still a lot of work to be done, but the first tests for an automatic change of the child devices driver types were successful. :slight_smile:

1 Like

Sorry, i meant it’s a mess in my current setup… with devices being duplicated, and some authorizations also running in aqara and alexa apps (from before the aqara could have been brought in to HE)… so, it’s gonna take me a while to write it all down, remove and recreate again

@kkossev, finally managed to pair my Switch Bot Hub 2 again with latest software release :grinning_face: (had to use MQTT/HA to use it in Hubitat since last year).

Switchbot Standing Fan:
I can change the fan speed using fan speed selector :grinning_face:
But, I get an error with the "Cycle Speed" command, please review when you can.

1 Like

You are absolutely right, did the cleaning and after doing rediscovery they stay labeled… i think what was happening before was, when deleting the device to rediscover it with a different driver, then it would lose its label, but if i leave them and do rediscovery then nothing changes with them, so all good.

The only problem (kind of) i have now, is that it discovered 8 “button’ devices, that i cannot link to anything. I have two H1 wireless switches, but tracked them down via logs… those 8 extra buttons i have no idea what that might be.