#@marcelveldt I was testing HAOS 11.1 dev
next marsh
Yes, I'm working on that, the attribute does not get refreshed atm. I'm implementing the new diagnostics next week so this will be fixed (and visible in a human readable way in the UI). I will also implement a simple ping command which will issue an OS ip6 ping to the known address from the matter server.
BTW: Thanks for your help in debugging the routing issue! Really glad we're another step further towards stability 🙂
cunning nymph
Have you seen the patch 😳
next marsh
Have you seen the patch 😳
yeah, I was surprised that we only find out now haha
cunning nymph
Frustrating that it wasn’t a compile error but that’s macros for you
next marsh
I'm glad we solved it now, it explains a few mystery cases
cunning nymph
Yes - all my triage since haos 10 was on the basis that was fixed 😱 sure it will improve things massively
rotund cedar
yes I was pulling my hair out during my failover testing.....
but as you will see in post #2, HAOS 11.1 fixed it
neat oak
but as you will see in post #2, HAOS 11.1 fixed it
Which post are you guys talking about? What was the issue?
cunning nymph
One of the fixes we made a year ago had a typo
The kernel patches
It was a C macro so happened to compile down to something that was valid C but incorrect
The effect was that it took 30 minutes to recover from a BR outage instead of a few seconds
Fix is in HAOS 11.1
rotund cedar
@neat oak My blog post #2 https://www.derekseaman.com/2023/10/part-2-smart-home-matter-and-thread-deep-dive.html
@cunning nymph As I covered in post #2, 11.1 failover is almost instant and only 1 ping drops through the whole proccess. Very impressive.