Does it work with just the FP sensor?
No, the Matter connection to FP2 requires Aqara M3 hub.
Reporting in to say that this driver worked great with my Neo Smart Blinds C-BR300 (with the Matter firmware upgrade) to control my MaestroShield patio shades. The open/close worked as is, but for Alexa to understand the difference between open/closed, I had to toggle the "reverse position reports" preference. I'm a happy camper. Thank you!
I had the same sort of issues.
I solved it like you but with a code change as well.
Will the Matter Advanced Bridge work with the new SwitchBot hub mini?
It will work with the new Matter enabled SwitchBot Hub Mini and Switchbot Hub 2.
Just go through the Matter setup in the SwitchBot app then setup the bridge/driver as per OP instructions.
Thank you!
1 Like
Shelly Gen 4 devices :
Update 04/06/2025 : 'Matter Advanced Bridge' version 1.5.0 '2025/04/06 5:42 PM' is pushed for update via HPM. The 'MatterAdvancedBridge.zip' bundle size is now 84KB and it takes several minutes to be updated via HPM, be patient ...
Tested with Shelly Gen4 1PM. The Power, Voltage, Amperage, Frequency, and PowerFactor seem to be working OK. Unfortunately, the Matter 'Electrical Energy Measurement Cluster' 0x0091 attributes are not decoded correctly in HE, so the energy monitoring code is commented out and not available at this time.
7 Likes
@kkossev have you released update 1.5.1? I saw this on HPM but did not see it referenced in this thread.
Hi,
Yes, I released an update 1.5.1 shortly after the 1.5.0, because I noticed I had made a mistake of not including the latest version of the new 'Matter Custom Component Power Energy' driver.
This fix relates to the new Shelly Gen4 power-metering switches only.
Due to my commitment to an important private project, I will not be able to actively participate in this forum from the beginning of April until the end of September this year. Once I return, I will review the available requests for adding new devices to the existing custom Tuya drivers. Thank you for your understanding and patience!
6 Likes
Thank you very much for your work on this.
{Problem with one out of 3 MS600 sensors}
Hub is C7 running 2.4.1.157 platform.
I have 3 Meross MS600 sensors. All are using Matter Advanced Bridge driver and up to yesterday all 3 was working just fine. According to the Meross app. all 3 sensors are on the latest firmware. All 3 are working just fine with Meross app. but one stopped reporting status to the HE.
Log for the parent device does not have anything useful (to my eyes):
Log for the Motion Sensor child is simply empty.
In order to bring this toy back in a reporting state I have to reboot everything multiple times (Sensor, HE and Router).
Since this Sensor works perfectly fine with the Meross app. it is hard to believe something is wrong with the Sensor itself. From the other side the other two sensors are still working just fine on the same hub with the same driver. The only change is - hub was updated to the latest platform 2.4.1.157. But problem started to couple days after the update.
Any ideas what may went wrong and how to fix this?
UPDATE
It looks like the sensor in question became (partially) bad. I replaced this failing sensor with a spare MS600 and now everything looks good. What is interesting, it still works with no problems in the Meross app. But when it fails in HE the Device Count reported 0. But when it works the Device Count reports 2 (below working condition states are shown):
Good Afternoon, everybody.
I'm using Hubitat C8-pro and updated to Platform 2.4.2.119. This broke the Matter Advanced Bridge driver, the error was
ERROR during the Matter Bridge and Devices discovery (BRIDGE_GLOBAL_ELEMENTS_WAIT).
Going back to 2.4.1.177 fixed the problem.
What now?
The problem is related to some changes in the HE platform that were made recently.
Until we have a solution, please stay (or revert) to the old 2.4.1.* platform.
@nghtly_strngr what is your matter Bridge that you are using this driver with?
1 Like
Will SwitchBot door locks be supported on platform 2.4.2?
Good Morning!
The hardware behind the driver is a Zemismart M1 Matter over Thread Bridge.
1 Like
@nghtly_strngr
I have patched the issue in this custom package version 1.5.3.
It is not pushed for automatic update via HPM, to update the driver use HPM 'Repair' function:
The door locks should be supported in the latest HE platform BETA version, using the inbuilt 'Generic Matter Bridge' driver.
4 Likes
Is there an easy way to convert from this custom driver to the built in driver?
Thank you, @kkossev , that solved the problem.
And thank you for your time and for providing us with your awesome expertise.
2 Likes
There is one more (hopefully the last one) change in the code to align with the latest HE beta platform changes. Please perform an 'HPM Repair' for this driver again.
Unfortunately, there is no easy way to switch from the custom driver to the inbuilt 'Generic Matter Bridge' driver. These were written at different times and use different methods for the creation of the child devices. The result is that when you switch between the drivers the child devices will be doubled.
Of course, it is much better to rely on the HE native drivers. So you can switch the device type to the HE inbuilt 'Generic Matter Bridge' driver and then click on the 'Configure' command
The list of the bridged devices will double... If everything works as expected, you can replace the newly created devices in your automation rules and dashboards, one by one,...
Before trying this, please wait for the latest Matter improvements and fixes to be released, as they are currently in BETA.
3 Likes
