#marcelveldt should I open a github

1 messages · Page 1 of 1 (latest)

tight elm
#

Yes please, that way I can keep track and follow it up. Can you also post a screenshot of your Thread config panel and include a diagnostics dump of the matter integration ?

fast pawn
#

Will do

tight elm
#

đź‘Ť

tight elm
#

Did you create the issue yet ? I think I did not yet get a ping

fast pawn
#

nope not yet

fast pawn
#

Commissioning to HA via the test flight iOS companion app right now is broken for me....zero HA Matter log entries and on my iPhone I get "unable to add accessory".

#

Up until a few weeks ago Matter was pretty stable and commissioning to HA was solid. But I don't have the cycles to try and debug all these new issues. Frustration level is too high.

#

Don't know if it's iOS 17, tvOS 17, or something else but I'm past my limit of automation problems.

tight elm
#

That is the iOS level. No logging in the matter server means it doesn’t even reach that point.

fast pawn
#

ya until Apple fixes all these issues I'm done with adding new Matter devices

tight elm
#

I'm not aware of any issues with apple commissioning atm, works fine on my end still

tight elm
#

So, I'm going to reply to you on the Github issue as well but this morning I tried to reproduce your issue on my end.

  1. I upgraded my production setup to HAOS 11
  2. I have 8 Homepod minis and 3 ATV's acting as Thread border router in my "production setup" (aka my house)
  3. I have several Thread devices spread throughout the house under 24/7 monitoring for availability, I already had that in place to just monitor the general stability.
  4. With the exception of Nanoleaf devices (which actually hurt the entire stability of my Thread mesh), my production setup based on Apple is reliable. Some devices drop off once or twice a day for a second but I think that is unavoidable and could simply be a hop to another border router, IP renewal etc.
  5. Just to be fully clear/transparant, I swapped the Unifi network gear in my home to TP-Link Omada after having too many issues with mdns discovery.

My production setup does not have any of the issues you are describing and works stable (finally)
After upgrading to HAOS 11 I could not notice any difference.

To test the Border router route switch I've just now done several tests where I unplugged several Border routers out and back, especially the border routers surround an Eve plug in my office. Each time the connection was restored within seconds or minutes. So this means that -at least on my end- the route election process works smoothly and exactly how you expect it to work.

Current theory of me and @radiant needle is that it could be related to Proxmox somehow doesn't forward some of the IPv6 ND messages but that is just a wild guess at this point. To confirm we'll have to re-do the test with proxmox involved.

fast pawn
#

@tight elm I think I'll have time tonight to put that USB adapter back on the Proxmox host and test again bypassing Proxmox networking.