#Woohoooo: Apple Home shows ’Home Assistant (Nabu Casa)‘ instead of ’4939‘ 😃👍

1 messages · Page 1 of 1 (latest)

limpid token
#

Today I paired a new device and remembered that this should work since about two months:

https://github.com/home-assistant-libs/python-matter-server/pull/909

So, I looked at the connected services of the new device and saw that it works now.

If you want that for all your devices, you need to re-interview them all manually. I tested it with some of my devices and it worked as expected.

Well done @delicate nexus and @heady sigil

Any news about the status of the Matter certification you want to share with us? 😃

IMG_1253.png
GitHub
Update label on interview by agners · Pull Request #909 · home-assi...

When triggering an interview update the Fabric label on the device as well. This allows users to update the label by a simple re-interview.

heady sigil
#

Yeah, we silently added this a while ago but we're still waiting for our certification to pass. Its a very painful process

limpid token
#

Ok, it is how it is. Good luck!

I'm thinking about going all-in to Matter, but there's still no Matter over Thread light switch.

My Matter over Thread setup with 65 devices is rock stable since Apple OS 18, all the latest Home Assistant Matter server, Ubiquiti, Nanoleaf and EVE updates.

heady sigil
#

Pssst, I have multiple Matter over Thread light switches on my desk 😉

#

A lot cool stuff is coming soon including some super nice light switches, both powered and remote. I'm testing a bunch for our WWHA program so can't say everything but just know that some stuff is coming.

#

As for running Matter over Thread over Apple border routers, I'm actually less optimistic. We have uncovered some nasty bugs in their implementations and tbh I can no longer recommend it. I have actually switched my own home situation away from Apple BR's to pure OTBR and its a day and night difference in speed and stability.

A bit of background story: https://github.com/home-assistant/core/issues/131001#issuecomment-2514302373

limpid token
limpid token
# heady sigil As for running Matter over Thread over Apple border routers, I'm actually less o...

WOW! Thanks for the link to your personal background story and describing all your test results.

Yeah, I also have some CASE Session timeouts in my logs. But I do not have any Matter over Thread devices going offline every now and then. I did not see any devices going offline since round about 2 months. Oh wait, not true. I had an EVE Weather some days ago with an empty battery.

I have 7 Apple Thread Border Routers (2 hardwired AppleTV 4K 3rd Gen, 4 HomePod Minis and 1 HomePod v2). You already know that.

My Thread channel is 25. I have two 2 floors. On every floor is one of the hardwired AppleTVs. On the main floor I have 2 Unifi APs and on the top floor I have 1 Unifi AP. I do not use 2.4GHz WiFi channel 11 to reduce interferences between WiFi and Thread.

I really don't know what I can say to your statements except that my system is rock solid, reliable and fast.

Some month ago I had to reduce my Thread network traffic generated by Multi-Admin, because my environment got unstable:

  • My 39 EVE MoT devices are paired to Apple Home and Home Assistant.
  • My 26 Nanoleaf MoT bulbs are paired to Home Assistant only.
    Unpairing all my Nanoleaf bulbs from Apple Home was enough to get the stability back.

My HomePods are locked to the next AP by the Unifi Network Application. Since I locked my HomePods to my APs and did all the updates I do not see partitions in my Thread network anymore.

It’s really hard to say, where issues have their source. Next to interference reduction, reducing Multi-Thread network traffic, there were a lot of updates:

  • HAOS and HA Matter Server
  • Apple OS (17 to 18)
  • Unifi

I am using the Unifi beta firmware on my APs since years. I gave them some support files months ago. They found issues in my logs relevant to MoT and they told me that they are working on fixing those issues. At least I think they did that, because everything feels good.

#

But there is always a negative feeling. Very seldom one or more bulbs do not react instantly. That is the point where my heart goes down, because you never know if it will work or not. But it only takes one or two seconds instead of instantly to switch the bulbs on. It works.

My automations in Home Assistant also got much improved. All my automations are executed only, if the conditions are right. To switch a light on, the condition is that it’s off and vice versa.

I also built HA light groups with a max of 3 bulbs. If I want to switch more bulbs on/off my automations include more light groups instead of one light group with more bulbs.

heady sigil
#

Interesting fact about the hardwired BR per floor - it makes you wonder if those are always preferred and the homepods simply ignored (most of the time). It definitely has something to do with it because we did a test by hardcoding a static route to a wired apple tv and that got it to an almost stable state.

limpid token
#

Yeah, maybe. But I also know, that when I restart one or some of my HomePods, the remesh procedure starts. Some of my MoT devices loose their connection. But they will reconnect after some minutes automatically. Mostly this process finishes within 5 minutes. Very seldom this took 30 or 60 minutes for a single device. Oh where I write this, I recognize that I didn’t say the whole truth. Sometimes I lost one or two of my 14 EVE Energies, when I updated my APs or when I restarted one of my HomePods. I really hope that this gets solved with the 3.5.x firmware for the EVE Energy. This never happened to any other device. Even the 26 Nanoleaf bulbs do not show this issue. They always reconnected by themselves.

What we really miss is the possibility to see the issues in our Thread networks with something like a map or simple table that gives us some information about the stability or the connection per device. You already have my feature request on the table. 😉

#

I also think that TREL and the network infrastructure can play a role for those kind of issues. But I am too far away to know, how to analyze it any better with the tools we have.

#

Can you give us some command line commands to analyze the Thread routes or the Thread network traffic overall?

wild pendant
heady sigil
wild pendant
frozen verge
wild pendant
#

I don't think LG ThinQ App will integrate Matter Binding feature so quickly

#

As far as I know, the only switches with Matter Binding function are Eve Light Switch US and Energy Magic Cube Relay Module & Wall Switch (I have tested them)

tribal widget
#

Innovelli says their White Series switches support Matter binding out of the box

wild pendant
#

Due to confidentiality reasons, I cannot share images. I have seen LG's PIR Sensor, Air Quality Sensor, Window&Door Sensor (Matter over Thread). LG has distributed them to local enthusiasts for testing.

#

@heady sigil Hope WWHA can cooperate with LG as soon as possible.😬

sly shoal
#

oh, interesting. a proper pir co2 sensor in a matter device? I'm looking forwards to that :)

heady sigil
jolly violet
limpid token
#

I still do not have any major issues. I have 68 Matter over Thread devices/bulbs and 7 Apple TBRs. Log is mostly quiet.

#

Recently I have noticed devices that could be pinged via HA WebUi but were not accessible (state unavailable). Any idea?

sly shoal
#

if the state is unavailable, there should be something in the matter server logs indicating why

limpid token
sly shoal
#

state being unavailable in home assistant is triggered by either the home assistant integration being unable to connect to the matter server, or the matter server telling the HA integration that the device is not available (the latter will normally coincide with some matter server logs about failing to resolve MDNS, CASE errors, etc.)