I had the issues you descibed yesterday | Home Assistant | Page 1

silk mica Jan 11, 2024, 1:26 PM

#

I have an eve motion that went unavailable this morning actually - I've only had the yellow joined with the network since sometime earlier this week

#

I think for me to test this better though i need to setup a separate matter server. The one I have now has all my devices paired to it

#

is it possible to enable debug logs on the matter server in HAOS?

sinful sinew Jan 11, 2024, 1:32 PM

#

silk mica is it possible to enable debug logs on the matter server in HAOS?

Yes, it has an option to set the loglevel in the configuration of the add-on

silk mica Jan 11, 2024, 1:35 PM

#

i guess it might just be a network issue on my system - i paired it to a new matter server running in HAOS and it worked

#

didn't change anything else about the network - yellows still paired

#

oh, wait - it's running Add-on version: 5.0.2 even though I selected beta

#

oh then it has Requirement already satisfied: python-matter-server[server] in /usr/local/lib/python3.11/site-packages (5.1.4)

#

so i guess it installs it on demand

sinful sinew Jan 11, 2024, 1:49 PM

#

My issue came back just now. Theory is that it was routing through a homepod and now switched back to the yellow

sinful sinew Jan 11, 2024, 1:50 PM

#

silk mica oh, wait - it's running `Add-on version: 5.0.2` even though I selected beta

yeah 5.0.2 is the latest verison of the add-on (which version number is not the same as the matter server project) - if you enable the beta toggle it will grab the last release from github and install that

silk mica Jan 11, 2024, 2:01 PM

#

i guess if it was related to the yellow routing though I would expect it to fail to pair on both my servers

sinful sinew Jan 11, 2024, 2:01 PM

#

I assume your other server is using an Apple BR ?

silk mica Jan 11, 2024, 2:02 PM

#

well, I didn't move the device - so it's still sitting next to the yellow OTBR - but there's a homepod on the other side of the room

sinful sinew Jan 11, 2024, 2:02 PM

#

Yeah, I had that too but the device was connected to the homepod

#

so it doesnt choose it by close range or perse

silk mica Jan 11, 2024, 2:03 PM

#

how do I check which device it's routing through?

#

wireshark?

sinful sinew Jan 11, 2024, 2:03 PM

#

ip -6 route from the terminal of the matter server

traceroute6 -w <ip6ofdevice>

#

do you know how to get the ip of the device?

#

https://www.derekseaman.com/2023/10/part-2-smart-home-matter-and-thread-deep-dive.html
has some pointers

silk mica Jan 11, 2024, 2:08 PM

#

I have them in some base64 encoding

sinful sinew Jan 11, 2024, 2:11 PM

#

scroll down on the page I linked above

#

this section

Schermafbeelding_2024-01-11_om_15.11.17.png

#

soon we will have this in the HA interface but for now this is a bit exciting haha

silk mica Jan 11, 2024, 2:16 PM

#

i was able to grab it from an mdns browser

#

but that is useful

#

so i guess i can ping it from the server that successfully paired, but not the one that failed

sinful sinew Jan 11, 2024, 2:16 PM

#

well I think pinging succeeds

silk mica Jan 11, 2024, 2:16 PM

#

so i guess it's probably more about which border router the server has as its route

sinful sinew Jan 11, 2024, 2:16 PM

#

but maybe with packet loss

#

Yeah, we have the feeling that someything is wrong when you add the yellow as BR to the apple network

#

maybe incompatibility with TREL or whatever other mystery

silk mica Jan 11, 2024, 2:17 PM

#

so if that is the main issue, I should be able to pair a non thread device still

sinful sinew Jan 11, 2024, 2:34 PM

#

yes

sinful sinew Jan 11, 2024, 4:25 PM

#

@silk mica lets continue here before we pollut ethe regular channel haha

#

https://github.com/home-assistant/core/blob/dev/homeassistant/components/matter/api.py#L86

#

This is where the app calls the HA websocket

#

and as you can see the request is forwarded as-is to the matter server

#

hmmm

silk mica Jan 11, 2024, 4:26 PM

#

this line could convert to int? https://github.com/home-assistant/core/blob/dev/homeassistant/components/matter/api.py#L102C9-L102C9

#

but yeah - seems very straightforward

sinful sinew Jan 11, 2024, 4:26 PM

#

No, code is defined as str

#

https://github.com/home-assistant/core/blob/dev/homeassistant/components/matter/api.py#L87

#

You watched the server liogs right ?

#

and you saw the raw request being logged from the websocket call ?

silk mica Jan 11, 2024, 4:31 PM

#

i haven't done it with debug logs on

#

does it matter if the matter server and ha server are on different hosts?

sinful sinew Jan 11, 2024, 4:32 PM

#

no shouldnt matter

#

its just a websocket between ha and the matter server

#

this is a complete mystery to me

sinful sinew Jan 11, 2024, 4:57 PM

#

@silk mica are you adding devices to HA only or also taking the appl ehome step in between ?

#

I have just identified a stupid mistake on our end ionvolving share from apple only

#

it induces a race condition

#

I am like 99% sure that adding a fresh device by QR code directly to HA would work reliable in all cases

silk mica Jan 11, 2024, 5:13 PM

#

matter-server  | 2024-01-11 17:01:54 sdk4 chip.CTL[1] INFO Verifying attestation
matter-server  | 2024-01-11 17:01:54 sdk4 chip.CTL[1] ERROR Missing attestation information
matter-server  | 2024-01-11 17:01:54 sdk4 chip.CTL[1] INFO Error on commissioning step 'AttestationVerification': 'src/controller/CHIPDeviceController.cpp:2581: CHIP Error 0x0000002F: Invalid argument'
matter-server  | 2024-01-11 17:01:54 sdk4 chip.CTL[1] ERROR Failed to perform commissioning step 13
matter-server  | 2024-01-11 17:01:54 sdk4 chip.CTL[1] INFO Going from commissioning step 'AttestationVerification' with lastErr = 'src/controller/CHIPDeviceController.cpp:2581: CHIP Error 0x0000002F: Invalid argument' -> 'Cleanup'
matter-server  | 2024-01-11 17:01:54 sdk4 chip.CTL[1] INFO Performing next commissioning step 'Cleanup' with completion status = 'src/controller/CHIPDeviceController.cpp:2581: CHIP Error 0x0000002F: Invalid argument'
matter-server  | 2024-01-11 17:01:54 sdk4 chip.CTL[1] INFO Expiring failsafe on proxy 0x7f8c07f500```

#

it seems like the first commission try doesn't finish and then the second try starts

sinful sinew Jan 11, 2024, 5:13 PM

#

We have identified the issue

#

we need to fix it in the companion app

silk mica Jan 11, 2024, 5:14 PM

#

oh ok

sinful sinew Jan 11, 2024, 5:14 PM

#

so sharing from apple home to HA is broken

#

oh well it has the race condition

#

because we use the same flow it is commisisoning to a temporary fabric now

#

and then shares it again

#

so the code you receive is not being sent to HA but to apple

silk mica Jan 11, 2024, 5:15 PM

#

oh, so it's used up already by the time ha matter gets it?

sinful sinew Jan 11, 2024, 5:16 PM

#

well, Apple kjust uses the regular flow and commisons the device to a temp fabric and then shares it AGAIN to HA

#

so instead of just passing that share code along its doing an intermediate step

#

and that could potentially lead to a race condition, especially on thread where traffic is a tiny bit slower

#

and nanoleaf which resets all the time

#

we should just hook into the apple framework and pass the code along

silk mica Jan 11, 2024, 5:18 PM

#

interesting - that part is definitely over my head with what I know about this so far

sinful sinew Jan 11, 2024, 5:18 PM

#

Yeah, I've asked our iOS app dev

#

I only realized this just now when I was tracing every part step by step

#I had the issues you descibed yesterday