[RELEASE] Matter Advanced Bridge (limited device support)

What is the proper course to recover from an Offline Hub 2?
Got up this morning and the blinds weren't working via HE but ok from the SB app.
I rebooted the HUB 2 and did an Init/Refresh command but it's still offline.
Don't want to mash all the commands in case I screw something up.
I did update to beta .146 last night so maybe I have to roll back to .145.

image
dev:23202025-01-07 09:51:01.730infoKitchen Hub 2 ERROR during the Matter Bridge and Devices discovery : ERROR during the Matter Bridge and Devices discovery (state BRIDGE_GLOBAL_ELEMENTS_WAIT)
dev:23202025-01-07 09:51:01.216infoKitchen Hub 2 ERROR during the Matter Bridge and Devices discovery (STATE_DISCOVER_GLOBAL_ELEMENTS)
dev:23202025-01-07 09:50:47.789infoKitchen Hub 2 Discovering the Bridge...
dev:23202025-01-07 09:50:47.744infoKitchen Hub 2 Removing all current subscriptions ...
dev:23202025-01-07 09:50:47.621infoKitchen Hub 2 Initialized (fullInit = true)
dev:23202025-01-07 09:50:47.619infoKitchen Hub 2 DEVICE_TYPE = MATTER_BRIDGE
dev:23202025-01-07 09:50:47.617infoKitchen Hub 2 all states and scheduled jobs cleared!
dev:23202025-01-07 09:50:47.541infoKitchen Hub 2 Starting Matter Bridge and Devices discovery ...

At the current stage of Matter protocol implementation in HE, it is somewhat difficult to troubleshoot connectivity problems...

If you go to Setting->Matter Details, do you see a green checkmark or a red cross against the Hub2 device?

Matter device is gone. :frowning:

Not in the list?

No, list is empty now.
It was my only device.

Thats weird... Try rebooting both hubs when the moment permits, but I can't recall a case where the already paired Matter device disappears from the list.

Rebooted hub and Hub 2. Nada.
Interesting is the Hub 2 link LED goes solid after reboot which means it's linked.

In the SB app if I go to Matter is it says Linked with a >. If I click on the > it takes me to Google Home. Did the Matter link move to Google from HE?

I have no linked apps there and only Hubitat as a linked service.

1 Like

Rebooted and UNPLUGGED the HE hub and the Matter device came back. :slight_smile:
So it was linking with HE in the background but not connecting as an existing device.

Well, never let an old programmer at the code. :rofl:
I swapped these 2 numbers and threw the Reverse Position Reports switch in the Prefs:

@Field static final Integer OPEN = 0 // this is the standard! Hubitat is inverted?
@Field static final Integer CLOSED = 100 // this is the standard! Hubitat is inverted?

Seems to work and display properly now.
The only strange thing that eludes me is the open and close just don't follow the shade template in the Dashboard.
It's like the tile isn't getting the states but it does work and show position.
Oh well. My OCD is feeling better. :slight_smile:

image

2 Likes

I am glad to hear you have nailed it! :+1:

These OPEN/CLOSED definitions are left from my attempts to achieve the same outcome; however, with the Tuya motors, there were other problems; the directions were already reversed for some models, and reverting the already reverted commands became a mess...

1 Like

Should I ask the community about the Dashboard compliance?
It may not be anything to do with your driver per se.

I have not experimented changing the dashboard background colors...

The MAB child device driver declares

capability 'WindowShade'

The same capability is used in the community 'ZemiSmart Zigbee Blind' driver that I am supporting too, and I don't remember a problem with the HE legacy dashboards.

Can you create a virtual device, assigned some of the inbuilt 'virtual blind' or 'virtual shade' drivers and compare whether changing the background works?

A virtual shade works, the colours change appropriately.
There is no virtual Blind driver but calling the tile a Blind in the Dashboard works as well.

Can you post side-by-side screenshots of the Current States section of a device using virtual shade and a screenshot of this driver shade device?

This driver is probably missing an attribute present in the virtual driver.

Virtual device
image

Matter device
image

IBlind working device
image

1 Like

Added a screenshot of how to configure the Preferences for the Zemismart ZM85EL-2Z curtains robot here. Unfortunately, the Tuya Matter Bridges do not reveal any information that can help to identify which model (manufacturer) is the bridged device exactly, so it is not possible to configure the multiple options automatically.

I did try the prefs screenshot.
The open/close still works properly with my reported changes but the Dashboard tile still doesn't change colours according to the template; still just grey.
Oh well, not a big deal. I'm happy they track the same as the iBlinds now.

This screenshot was mostly for me, Tuya/Zemismart motors have probably different settings than the SwitchBot motors...

Can you manually update only the 'Matter Generic Component Window Shade' driver?

https://raw.githubusercontent.com/kkossev/Hubitat---Matter-Advanced-Bridge/main/Components/Matter_Generic_Component_Window_Shade.groovy

I have added 'Switch' and 'SwitchLevel' capabilities in the driver, I think that this is the difference with the virtual shade device.

You may need to manually edit the OPEN/CLOSE definitions in the code to match your last working settings.

1 Like

Under test, tks.

Well the colours work now but in reverse.
I tried changing 0 and 100 in the code and various Prefs settings.
The closest I could get was Closed and Open with the correct colours and icons with
Substitute Open/Close w/ setPosition set to enable and your code unmodified with respect to 0 and 100 reversal.
It's all good visually now but I expected reversing the 0 and 100 in the code so make it perfect but it didn't help this time.
Living room is iBlinds normal, Kitchen Left is test subject. and KItchen Right is your driver unmodified.
Thanks for playing with the issue though. At least I can get the "at a glance" value now with the colour change. The slider being backwards is not a big issue.

1 Like