Matter Support Released

Aqara has now released the Global version of their M3 hub - it is a Matter Controller, Matter Bridge and Thread Border Router. Available on Amazon.

5 Likes

Interesting. I just had a Nanoleaf essentials bulb do this. I didn't even realize it was showing nonresponsive. I rarely control that one. It is almost completely automated. It has been responding to its rules and automations fine. Since I picked up the March update, they have all been very stable until this bulb today. But I think the bulb in general went bad. In trying to restore it, I ended up taking it out of HomeKit and hubitat, factory resetting it, and now it won't add back,

1 Like

My current details

1 Like

I'll admit, I'm not totally sold on matter yet. I won't be going out of my way to replace working devices with matter. At this point it's interesting to play with. The only exception is that one bulb, I'll replace with another, primarily because I really like the richness of the Nano leaf essentials. Until this bulb, ever since the March update these bulbs have been very stable for me. I really do believe this particular bulb just went bad given that even after a factory reset it won't pair again, to either the Nanoleaf app or HomeKit.

1 Like

How would the Aqara M3 hub work with Hubitat, would you pair the hub with the hubitat, then anything that "pairs" with the Aqara hub would show as controllable devices in Hubitat or am I getting this all wrong?

Trying to see what uses this would add to an existing Hubitat system thanks.

I have an M3 hub although I haven't played with it extensively. It paired to Hubitat as a 'bridge'.

The way Aqara have implemented this is that any device within M3 e.g. ZigBee seems to be accessible via HE however any devices paired to the M3 bridge via Matter do not get onwardly exposed from M3 to HE which is what I had hoped and yourself I think. I suspect Aqara reason this can already be achieved directly in Matter already although they don't provide a 'share' function themselves to assist within M3. My Hue system gets into M3 via Matter but does not propagate onto HE this way for example although there are other better ways for this anyway

There are currently very few devices that will pair over Matter to the M3 but after poor feedback from users Aqara have just announced they are expanding this significantly so it should get better. Aqara are responding quickly on Reddit with OTA updates as users are raising issues.

1 Like

I added an Aqara M3 a couple of days ago to my setup,

I was trying to improve my control of the E1 curtain motors.

After a couple of attempts the curtain motors appeared as child devices under the M3 hub and I can control them directly from Hubitat.

There is a slight issue in that the controls are reversed i.e. if I click open the curtain closes and vice versa.

I need to investigate this a bit further to see if I can get the curtains and buttons to match up.

Interesting. I am about to do this with my E1 roller shade motors. Hipefully k will have time this weekend!

Mostly the same here. It is still a bit of a novelty at this point. I am somewhat surprised that there aren't more Matter devices available. It seems to be limited to mostly bulbs and a few other items at this point, not a full range of stuff that I thought we would see.

But then again, I was making fun of the people various places online who predicted that Matter would be a instant hit, and would take over the world in no time. Zigbee and Z-wave were toast! They were switching all their devices to Matter!!!

That was probably 2 years ago now. I said then that it would be years upon years before Matter took hold, and I guess I was right. Meanwhile, Zigbee and Z-wave seem to be the same as ever, I don't see any evidence their market share has dropped significantly.

1 Like

I am still and will, for the foreseeable future, be a fan of Z-wave. If matter becomes more stable, and there are more devices available AND those devices can fulfil my needs better than Z-wave, I will consider them. I may still consider Matter to get rid of my last three ZigBee bulbs and will replace my hue sensors with z-wave when the 800LR Zooz outdoor motion sensors are rereleased. Generally, I want to move away from Zigbee.

Same, I see matter being good for colour bulbs and smart appliances, but for most other things I’ll stick to zwave too.

What's the general recommendation when trouble-shooting flaky devices. I have a Tapo Matter Wi-Fi plug that started not responding consistently to commands (control via Pico/button rules and from the Device page).

I ended up removing it from HE and also from Googel Home commissioning device, and re-adding it. Should I have saved time (and frustration, joining using GH app is still an unreliable PITA) and just removed/re-added to HE? Likely same results either way, or ?

It is difficult to say what could be the reason for this instability, without having any statistical or debugging data.

You can experiment with the Matter Bridge driver, it counts the number of the re-initialisations when the Matter device does not respond when pinged. By default, the Ping period is 15 minutes.

1 Like

Many bulbs and switches, also among currently on-sale devices there are also a few locks and thermostats, RGB strip light controllers, roller shades, an air purifier, motion and light sensors, door/window contact sensors. Lots more that has passed certification, but still not readily available. More complete list of what has passed certification is here: CSA Matter Certified Devices

2 Likes

Recently I got Zemismart Matter Wifi 6-gang Wall Switch and tried to pair HE.
Generic Matter Multi-Endpoint Switch driver has been assigned automatically.
Pairing was OK but nothing working. Is there any other driver for the switch?

Product URL is: https://www.aliexpress.com/item/1005007203967676.html?spm=a2g0o.order_list.order_list_main.5.6ba11802TYjJpi

The device information in HE:

Controller Type: MAT

Data:

  • endpointId: 01
  • hardwareVersion: 1.0
  • inClusters: 0003,0004,0005,0006,001D,001E
  • isMultiEP: true
  • manufacturer: Zemismart Technology Limited
  • model: Zemismart WiFi Smart Switch
  • outClusters: 0003,0006
  • serialNumber: ce72d13f5dd742f19f5d769891b67f4b
  • softwareVersion: 1.6
  • uniqueId: 70a8366bcd7672df

When I added the switch to Homekit, all six buttons were shown and worked fine.

Switch temporarily to the HE inbuilt 'Device' driver, click on 'Get Info' and post the fingerprints for all endpoints that should appear in the live logs.

Have you refreshed the device web page to see whether the Generic Matter Multi-Endpoint Switch driver has not created 6 child devices?

I got following:

dev:1452024-07-08 08:25:57.681 PMinfofingerprint endpointId:"06", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:57.680 PMinfofingerprint endpointId:"05", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:57.678 PMinfofingerprint endpointId:"04", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:57.677 PMinfofingerprint endpointId:"03", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:57.676 PMinfofingerprint endpointId:"02", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:57.673 PMinfofingerprint endpointId:"01", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:40.128 PMinfofingerprint endpointId:"06", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:40.127 PMinfofingerprint endpointId:"05", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:40.125 PMinfofingerprint endpointId:"04", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:40.120 PMinfofingerprint endpointId:"03", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:40.119 PMinfofingerprint endpointId:"02", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

dev:1452024-07-08 08:25:40.117 PMinfofingerprint endpointId:"01", inClusters:"0003,0004,0005,0006,001D,001E", outClusters:"0003,0006", model:"Zemismart WiFi Smart Switch", manufacturer:"Zemismart Technology Limited", controllerType:"MAT"

After refreshed no child devices created. Current States section of the device page showed nothing.

1 Like

Try the Matter Advanced Bridge package, I expect to be working with this device too.

1 Like

Wow, it's working!
I thought Matter Advanced Bridge was driver only for gateway or hub(like Zemismart M1 matter hub).
So, does it work for any matter-over-wifi devices?

BTW, thanks so much for your help.

1 Like

Does anyone 'in the know' or on the devlopment team know when Locks will be supported in the Hubitat Matter implementation? I must admit, i dont know if this is a Matter constraint or an HE implementation one - im pretty sure it is the latter?

Is it on the roadmap at all, or is this 'won't implement' ever?

Thanks.

3 Likes