Matter with Open Thread Border Router (CC2652P, Ti firmware)

[open pike]

This is the log from the border router: https://pastebin.com/duk6EDDg

Matter with Open Thread Border Router (CC2652P, Ti firmware)

So it seems the border router starts just fine. I am not entirely sure if theres anything I need to configure in the matter server addon, but from what I see it seems like this should be it?

Ah interesting, I just reset the eve plug by pressing the button for 10 seconds and tried pairing again. Now it fails and says a border router is required. And the border router has this log entry:

otbr-agent[176]: 00:14:29.508 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:90, chksum:4ee7, ecn:no, to:aeacdce42534926b, sec:no, error:NoAck, prio:net
otbr-agent[176]: 00:14:29.508 [N] MeshForwarder-:     src:[fe80:0:0:0:3c44:9441:c3d7:fd09]:19788
otbr-agent[176]: 00:14:29.508 [N] MeshForwarder-:     dst:[fe80:0:0:0:acac:dce4:2534:926b]:19788

[strong bison]

If it says border router required it fails on your phone.

[open pike]

any hints I could use for troubleshooting?

[strong bison]

Are you on the same wifi, Lan and so on as your otbr?

[open pike]

yes ofc

[open pike]

@fading solstice you got an idea what I could do to trouble shoot this by any chance?

[strong bison]

Can ypu say more about your setup?

Android or IOS?

And so on

The problem is not the TI chip

Its somewhere Else in your setup

So you just have one subnet?

[open pike]

I am running HA OS on an i5 Laptop. Only one subnet. Tried an iPhone and an iPad with the same result.

Also, I can reproduce the open border router to drop the Failed to send IPv6 UDP msg error. I have tried the eve ios app to see if it finds a border router, and it also doesn't.

Might it be that I'm running a rather mint openwrt router for my subnet?

[fading solstice]

Nope.. traveling today and have only tested that the addon starts and seems happy with the rcp device.

[strong bison]

Are you blocking ipv6 route advertisement?

Does your phone get an ipv6 address?

And also are you blocking mdns some mdns things?

Or just haven’t enabled it

And im not talking about a link local address

[open pike]

1: no, default on by openwrt docs (if thats what you mean: https://openwrt.org/docs/guide-user/network/ipv6/configuration#router_advertisement_dhcpv6)
2: yes it does
3: not actively blocking anything
4: earm, .local addresses work fwiw

[strong bison]

Have you looked in your Settings? I have an gl.inet router running that just works. They have made som propiatary modifikations to openwrt though and run an acient kernel.

But try to check the assigned IP-adresses of your pc/phone. Is there an ipv6 that doesnt start with fe80?

Next thing ypu could try is using an mdns browser. Can you see some matter entries?

Cant remember the exact local service

[open pike]

yes I have checked the settings, default router is automatic and slaac is enabled.

https://imgur.com/a/11lkVLK

[open pike]

two ip addresses and one starts with fdcc and one with fdb0

[strong bison]

Great, thank this one is working

Then it probably has something to do with your mdns entries

[open pike]

can you recommend an mdns browser?

[open pike]

google search isn't very helpful with finding an "mdns browser".

ah, might this terminal command help?
dns-sd -B _services._dns-sd._udp

lots of results, all of them start with an underscore, none of them scream matter.

[strong bison]

https://apps.apple.com/dk/app/discovery-dns-sd-browser/id305441017

[open pike]

ah yeah that yields about the same results as the command

https://pastebin.com/mvuH56A9

[open pike]

So apparently I should see a service called _matter._tcp, which I don't, but the question is why.

oh, just checked my matter logs: 2023-07-15 13:19:54 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on enp0s26u1u5i6 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found

[strong bison]

I use this one

[open pike]

you mean the mdns scanner you posted? yeah I ran it and it contains about the same information (but less) than the command of which i posted the results in the pastebin above (because >2000 limit)

[strong bison]

My internet was just shit, so the message came delayed

[strong bison]

But is that your main interface? Its normal

Since it basically tries for every interface

[open pike]

as far as i can gather, that's the border router

the main interface is enp0s24

[strong bison]

Yeah, then it should be okay.

Are you sure you Can pair to the eve plug?

[open pike]

oh i jsut checked in ha's system->network, ipv4 and v6 are both disabled

[strong bison]

Is it already commissuoned

[strong bison]

Both?

[open pike]

no! it is brand new, the whole matter setup is mint!

nothing is paired

[open pike]

yes both for the interface witht the long id

[strong bison]

So ypu havent tried to pair it to an Apple otbr?

[open pike]

i don't have an apple otbr

[strong bison]

Or Google

[open pike]

i only have that ti chip

[strong bison]

Okay

[open pike]

i have some silabs chips that I can flash and hook up to a cp2104 fwitw, but you said it wont be the issue

[strong bison]

Did you reset the plug?

[open pike]

yes

[strong bison]

So you let it blink exactly 5 times?

[open pike]

lol, ok, I reread the manual and indeed, i did not. I did now though, and the behavior is the same. Complains about no thread border router and the border router log says:

otbr-agent[176]: 01:12:28.656 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:90, chksum:d548, ecn:no, to:b69340245f816696, sec:no, error:NoAck, prio:net
otbr-agent[176]: 01:12:28.656 [N] MeshForwarder-:     src:[fe80:0:0:0:3c44:9441:c3d7:fd09]:19788
otbr-agent[176]: 01:12:28.657 [N] MeshForwarder-:     dst:[fe80:0:0:0:b493:4024:5f81:6696]:19788

[strong bison]

I dont Think this message has anything to do with it. Is the otbr registered in HA as the default one?

[open pike]

it is the only one. how can I check if it is registered with HA? there's no such options I could find ...

[strong bison]

I cant remember it right now. Hopefully someone Else answers

Also you are trying on Android, right?

[open pike]

no, I don't run the companion app on any android devices

[strong bison]

Ahh

So on iOS you need to use an apple otbr

For now

Do you have an android device?

[open pike]

yes a slow fire tablet i use as a dashboard

[strong bison]

I would try with that one then

Or is that even running android?

[open pike]

fire os, which is basically some android

it has the compannion app, i'm installing

[strong bison]

I’m not sure that it has support for commissioning of matter devices though

If you don’t have any other device you could use the matter cli tool

https://github.com/project-chip/connectedhomeip/tree/master/examples/chip-tool

That’s a bit more work though

[open pike]

where does that conclusion come from?

[strong bison]

It because the iOS app can’t give the thread credentials to devices in the iOS commissioning process yet

Took some time to get the permissions from apple for it. Now it’s a waiting game for someone to implement

[open pike]

ohhhhhhhhhhh

[strong bison]

Sorry I didn’t think of it before

[open pike]

This would be an information i'd expect in the docs though ...

[strong bison]

Yes, they aren’t the best right now

I think someone was working on cleaning that up but forgot it again

[open pike]

no worries, I understand what I'm getting myself into 😅

so if I bought an echo dot it would also not work with ios?

[strong bison]

But if you don’t run windows and you are comfortable with playing around with a cli tool you can use the one I showed

[strong bison]

That depends on if Amazon has added it to their app yet

[open pike]

I have a windows device I can try

[strong bison]

It’s a big haste to get it working on windows

Since you need access to blue

Bluetooth

[open pike]

oh, cli it is

[strong bison]

Probably easiest to spin up a Linux vm and forward you Bluetooth adapter to it

[open pike]

the fire-os companion app says I need to use the companion app to add matter, jfi 😄

[strong bison]

Yeah, I don’t think you can use anything else to commission right now

Last I heard they disabled ble commissioning in the matter addin

Because there where problems with Bluetooth

[strong bison]

Are you able to download the Google home app on it?

The simplest solution is getting a real android device

(The Google home app might add the matter api if you are lucky)

At least that’s how to force a normal android device to download it in the background

Or maybe you can run android on an rpi with mouse and keyboard

Haven’t tried that though

[open pike]

hang on I do have an old android phone running lineage somewhere

so if I managed commision the device in the google home app, the device would be discoverable by ha as well? would that use the ha matter server?

[strong bison]

Google home would not use the Ha server

But Google home forces the api’s that are needed for the companion app to be installed on android

[open pike]

ahh

[strong bison]

(If it’s even supported on linage)

[open pike]

nah only getting a spinning circle when adding matter device

[strong bison]

Do you get some different logs?

[open pike]

no i get nothing but a blank page with a spinning circle (loading indicator) but nothing happens. no camera pops up, so there is also no commissioning happening unfortunately.