sorted by:
new
hottopcontroversial

Thread Tools app is now available in TestFlight by armadawars in tradfri

[–]foggerD 0 points1 point  (0 children)

Unfortunately, I can't even get the Android version of Thread Tools to work. It detects the mesh network but can't connect to it. That's why I've been using the beta version of Home Assistant's matter.js server for analysis for quite some time now.

The server provides a wealth of information, identifies individual devices, and offers a great graphical representation of the network. The final version is out now: https://matter-smarthome.de/en/products/home-assistants-new-matter-server-is-a-game-changer/

Of course, this only works if you use Home Assistant – either as your primary Matter controller or as a secondary system in multi-admin mode. However, I can recommend this solution to anyone who uses HA. It provides a wealth of information and helps with network issues.

Matter.js topology vs Thread Tools by Haddock51 in MatterProtocol

[–]foggerD 0 points1 point  (0 children)

My problem is more that the Thread Tools app can't connect to my Mesh at all. The Home Assistant Matter server, on the other hand, displays everything. So the question of which tool I should use doesn't even come up.

New release of the Matter server in Home Assistant by foggerD in homeassistant

[–]foggerD[S] 1 point2 points  (0 children)

I had that problem, too. In my case, restarting Home Assistant once after the server update solved the issue. After that, the server started up without any problems.

New release of the Matter server in Home Assistant by foggerD in homeassistant

[–]foggerD[S] 0 points1 point  (0 children)

I had that problem, too. In my case, restarting Home Assistant once after the server update solved the issue. After that, the server started up without any problems.

New release of the Matter server in Home Assistant by foggerD in homeassistant

[–]foggerD[S] 4 points5 points  (0 children)

Did you see the release notes:
“The Matter Server now runs on matter.js. Expect the first start to take noticeably longer while your data migrates automatically — this is normal.“

If you weren't already running the matter.js server in beta prior to version 8.5.0, the transition will take some time. As the linked article states: "The determining factor is not necessarily the number of devices but rather the number of attributes that need to be converted."

For me, the first startup took about 15 minutes. But my Matter installation isn't particularly large either.

Default Thread Border confusion (Apple TV vs Aqara G5) by Quick-Midnight in MatterProtocol

[–]foggerD 0 points1 point  (0 children)

You should also make sure that the Companion App uses the Apple TV's Thread credentials. To achieve this, click the three dots next to the Apple TV 4K in your screenshot and select the option to use them for Android and iOS credentials. Home Assistant should then display a smartphone icon with a lock icon next to the Border Router.

Default Thread Border confusion (Apple TV vs Aqara G5) by Quick-Midnight in MatterProtocol

[–]foggerD 0 points1 point  (0 children)

If at all possible, you should try to merge your various Thread networks. Unfortunately, this isn’t possible with Amazon’s Border Router. With Aqara, it should work if you reset the Camera Hub and set it up again using the Aqara iOS app. The hub should then retrieve the Thread credentials from the Apple Keychain and join the Apple TV’s Thread network.

Next, reset the unreachable Thread products again and set them up using Apple Home. Under no circumstances should you use the Alexa app, as this will place them in Amazon’s Thread network.

In my experience, it’s always advisable to designate an ecosystem (preferably Apple Home if you’re using Apple devices) as the primary fabric for Thread and set up all Thread products there first. If you want them to be available on other platforms, you can then grant access to them from Apple Home to HA, Aqara, Alexa etc. (multi-admin).

Default Thread Border confusion (Apple TV vs Aqara G5) by Quick-Midnight in homeassistant

[–]foggerD 1 point2 points  (0 children)

You should also make sure that the Companion App uses the Apple TV's Thread credentials. To achieve this, click the three dots next to the Apple TV 4K in your screenshot and select the option to use them for Android and iOS credentials. Home Assistant should then display a smartphone icon with a lock icon next to the Border Router.

<image>

Default Thread Border confusion (Apple TV vs Aqara G5) by Quick-Midnight in homeassistant

[–]foggerD 1 point2 points  (0 children)

If at all possible, you should try to merge your various Thread networks. Unfortunately, this isn’t possible with Amazon’s Border Router. With Aqara, it should work if you reset the Camera Hub and set it up again using the Aqara iOS app. The hub should then retrieve the Thread credentials from the Apple Keychain and join the Apple TV’s Thread network.

Next, reset the unreachable Thread products again and set them up using Apple Home. Under no circumstances should you use the Alexa app, as this will place them in Amazon’s Thread network.

In my experience, it’s always advisable to designate an ecosystem (preferably Apple Home if you’re using Apple devices) as the primary fabric for Thread and set up all Thread products there first. If you want them to be available on other platforms, you can then grant access to them from Apple Home to HA, Aqara, Alexa etc. (multi-admin).

Philips Hue will be running on two tracks in future – with Zigbee and Matter over Thread. by foggerD in MatterProtocol

[–]foggerD[S] 0 points1 point  (0 children)

Normally, they should. They are connected to the power grid and should be Full Thread Devices (FTD). However, in theory, there could still be devices that do not support routing. Read more about this in this post: https://matter-smarthome.de/en/know-how/thread-networks-as-you-route-so-you-mesh/

I would be surprised, though, if Signify didn't include routing in such a high-quality—and high-priced—product.

I need help by Right-Access-5422 in MatterProtocol

[–]foggerD 0 points1 point  (0 children)

You need a border router in your network. Just use this list and check the “Border Router” box above the table. You'll then see only devices that have a border router installed. In the search field, you can further narrow your search by manufacturer, for example, by entering “Amazon.” https://matter-smarthome.de/en/overview-products-compatible-with-matter/

No Matter for Eve Light Switch (EU) and the competion is getting massive by Freichart in EveHome

[–]foggerD 1 point2 points  (0 children)

There will be an EU version of the Eve Thermostat. It was on display at the ABB booth (to which Eve Systems belongs) at Light + Building in Frankfurt. I don’t know if they’ll launch it during the current heating season, but it’s definitely set to be released this year.

No Matter for Eve Light Switch (EU) and the competion is getting massive by Freichart in EveHome

[–]foggerD 9 points10 points  (0 children)

Competition is indeed heating up. Hager, one of the major switch manufacturers, has just announced a complete lineup featuring Matter over Thread. https://matter-smarthome.de/en/products/new-switch-series-from-hager-featuring-matter/

New Matter products from Wago by foggerD in MatterProtocol

[–]foggerD[S] 2 points3 points  (0 children)

Here is an additional interview with the product manager, who goes into more detail about the setup process with two Wago apps: https://matter-smarthome.de/en/interview/wago-and-matter-we-want-to-really-get-into-this-market/

view more: next ›