Matter broken?


Hub model C8 & C7, both on platform version: 2.3.9.166

Did something break with the last update in regards to Matter?

i have two matter hubs (Moes & Aqara) and one third reality motion light.
All were not responding anymore, and cheking the Matter status page, it stated that all devices were offline.

I removed the Aqara hub from HE, as this was my test hub, and removed the pairing from the Aqara app. Tried to join it again with a new code, but it will not find the hub.

Next i tried to do the same with the Aqara hub to Homekit, as this would be a good test to see if the Aqara hub was broken. it joined without any problem.

Tried to do the same to my C7 hub, and also there the Aqara hub would not join.

As a last resort, I shut down the HE C8, removed power for a few minutes, booted again to see if I could join it again. No go, as it will not find the hub.

After the shutdown, my other devices now also seem to be offline to HE.

Did I do something wrong, or is the Matter integration broken in release 2.3.9.166 ?

Speaking for myself, I've not seen any issues with Matter and 2.3.9.xxx.

1 Like

I have not noticed problems in the latest HE platform updates.

Summary

1 Like

Strange..

I removed all Matter devices from HE, disabled Matter, rebooted, enabled Matter and tried to join the aqara hub again. This time it joined as "device". Set it to the correct driver and tried to discover it.
After about one minute, it gave a timeout, and now shows ■■■ offline:

The hub is online itself, and a test device joined to that hub is also online.
It's just that HE thinks it is offline

Do you have any pending updates for the Aqara M3 hub?
The problem that you are experiencing now seems to be related to the Aqara M3 hub / the custom Matter Bridge package, not HE in general.

... I have updated the package just 22 days ago, and already forgot that Aqara M3 was the reason ... :frowning:

The aqara hub is on the tast version (4.1.6_0018)
I do not think it is the aqara hub, ans i see the same with my Moes bridge, and my third reality light.

When in doubt and troubleshooting the reason for Matter issues, I usually change the driver to the HE inbuilt 'Device' driver and hit the Configure button, This effectively unsubscribes from all events and attributes subscriptions and makes the device inactive. There is no need to delete the Matter (bridge) device and all its child devices.

Temporarily leave only the TR light using the inbuilt HE driver. If all works, switch back to the Matter Bridge drivers for the bridges one by one.

Tried this, bot not working.
I can add the aqara or the moes hub to HE, it pairs then after about two minutes, they go offline (red cross on matter status page).
The only way I seem to be able to pair them again, is to delete the devices, disable matter on HE, wait, enable it again and pair. But after two minutes, the go offline again...

Is there anything useful in the Aqara or Moes bridge devices logs?

Is the ThirdReality native Matter device working OK, when both Aqara and Moes hubs are disabled?

Nothing pairs again to he, both the c8 and the c7 refuse to add any device.
So anoying this.
All matter devices pair like a charm to homekit.

I’m letting it rest for now, bedore I kauch the hubs to the wall…

Will try again this weekend

1 Like

Some ThirdReality Night Light with motion sensor tend to drop off. Check the phone app for an update.

Time to tinker some more.

Facts:

  • All matter devices will not pair directly to HE
  • I can pair devices via Homekit to HE
  • Devices connected via HomeKit lose there link to HE after 24 hours
  • Disconnected Matter devices in HE are stil connected to Homekit and remain working there
  • HomeKit is still connected to HE when Matter devices go offline
  • Rebooting HE or Matter devices solves nothing
  • Disconnected Matter devices have no IP adres in HE Matter status page

I'm kind of at a loss here. With the introduction of Matter to HE, this has worked flawlessly for two months. I did not make any changes to my infra.

To exclude the possibility of the custom Matter Bridge package to be somehow the reason for the problems, did you change the Tuya and Aqara Matter gateways driver to the HE inbuilt 'Device' type?

The key difference is that the 'Device' driver is passive, it will not subscribe for any matter events or attributes. The custom Matter Bridge driver actively checks the connection status every 15 minutes.

For the tests, leave the Matter bridges on Device driver and use the HE inbuilt Matter driver for the TR light.

Would love to test this, but the TR light will not pair to HE.
What I did:

  • Remove the TR light from Homekit and HE
  • Factory reset the TH light
  • Put it in pairing mode on light itself > HE will not see it or pair with it
  • Put it in pairing mode on light itself > Homekit see it, and pairs within seconds
  • Put it in pairing mode within Homekit > HE will not see it or pair with it
  • Put it in pairing mode within Homekit > Alexa sees it within seconds and pairs with it normaly

I'm att a loss here. Why wil HE not pair with anything. When I get something to pair, it loses connection within 24 hours, while other Matter hubs stay working stable and pair like a charm.

If it was just my C8 doing this, I would suspect my C8 be at fault, but i see the same issue on my C7.

That's weird; TR light is not seen in HE when using the pairing QR code generated from Homekit...

At the same time, you can pair the Matter Bridges to HE - again using the new pairing codes generated within Homekit?

Do you have Hubitat security login options enabled?

Indeed this is weird, and so far, i'm not seeing the big picture apparently..

After the Tuya bridges (moes & aquara) lost matter connection to HE, I deleted them from HE, and tried to pair them again. They would not pair. Then tried to pair them to Homekit, and they paired within seconds.

Tried to pair them from Homekit to HE > no pairing. It says "Looks like you’re having trouble pairing your device. Please check that the device is in pairing mode and is on the same LAN as the hub."

And yes, they are on the same network, and same subnet.

Hubitat secure login is enabled, as it has been sinds I started my HE adventure about three years ago.

Mentioning the secure login was a shot in the dark, actually I don’t think this should have any impact on the Matter communication.

In one of the latest HE platform updates the self-signed SSL certificate was updated, but again I am not sure if this is related.

Had issue's before the current build, so the ssl cert should not be the thing that is frustrating the matter connection. (is Matter using SSL?)

The strange this is that the matter hubs and the TR light pair without any issue to Homekit, but not to HE. Never in a direct connection, and 1 of 10 atempts when sharing by Homekit.

Just tested: disable hub security, and tried to pair again:
1:1 pairing > device not found
Homekit to HE pairing> device not found.

So the security is not the issue here.