#thread-archived

1 messages · Page 9 of 1

spare sphinx
#

should be enough to open up the firewall between the VLANs no?

vapid shell
#

No it is not

spare sphinx
#

I have multicast relay between the networks

vapid shell
#

Doesn’t matter

#

HomePods send icmp6 packets from their non routable link local address

#

These icmp6 packets contain the routes

#

Without that nothing will work

spare sphinx
#

well shit

#

why did they do that?

twin vine
#

assume that the homepods and phone are on the home/trusted vlan, and HA on the IOT one? not that it matters

vapid shell
#

That’s how icmp6 route adverts work

#

I put my HomePods on a vlan and gave my homeassistant container a macvlan link into that vlan

#

I don’t use matter just homekit so didn’t need to put my phone on that vlan yet

spare sphinx
#

no, there's an IoT VLAN for all the chinese shit I don't trust, then there's the client VLAN for normal devices, and there's a VLAN i've called DMZ which HA is on which was supposed to be allowed to communicate with everything

#

but that was assuming everything used normal TCP/IP conventions

vapid shell
#

It is, just ipv6 ones

spare sphinx
#

hmm, I wonder if I've forgotten to make the same rules for IPv6 that I did for IPv4

vapid shell
#

RFC4191

#

Vlans explicitly not allowed

spare sphinx
#

it certainly looks so

vapid shell
#

It’s not about firewall rules

#

Icmp6 broadcasts from link local addresses don’t traverse routers

spare sphinx
#

correct

vapid shell
#

So it won’t work with vlans

spare sphinx
#

yes, I understand

#

basically I'll have to choose a VLAN where anything touching Thread must live

#

that's really dumb

#

but explains many things

vapid shell
#

Thread is designed to work in spite of your home network gear, not cooperate with it. But when you start leaning into enterprise setups, that breaks its assumptions.

spare sphinx
#

yeah, the assumption that everything is just one big network haha

vapid shell
#

The thread mesh is essentially its own vlan

spare sphinx
#

yeah that part I already knew

vapid shell
#

The brs need a no config way to inject routes to it

#

IPv6 gives you.. RFC 4191

#

And that’s where we are

spare sphinx
#

this is really annoying, because now I can't put my phone or laptop on the client VLAN if I have all the HomeKit shit on the blessed Thread VLAN

vapid shell
#

What do you mean?

spare sphinx
#

HomeKit will stop working if I put the HomeKit devices on a different VLAN no?

#

I have tried that and had issues, but now I'm wondering if maybe that's because my IPv6 rules were whack

vapid shell
#

Sorry that could mean too many different things which is why im confused

spare sphinx
#

haha

vapid shell
#

Do you mean one of the homekit integrations?

spare sphinx
#

no, just HomeKit

vapid shell
#

Homekit bridge or homekit device/controller

spare sphinx
#

not HA related

vapid shell
#

Ok

#

Yes

#

If you want to use homekit directly

#

And not re-export from home assistant

#

I re-export so it’s a non issue for me

spare sphinx
#

I'm leaning more and more towards that, especially with the 2023.11s HomeKit fixes

#

I have a really weird behaviour with my FYRTUR blackout-blinds which appears when controlling them from HomeKit, they suddenly only know 100% or 0%

#

which I think 2023.11 fixed

#

I used to have to reload the HomeKit integration to get that working normally after an HA reboot

vapid shell
spare sphinx
#

haven't been able to determine if its fully fixed because I have one FYRTUR which behaves even weirder, it just forgets to stop when it's been fully closed and keeps rotating forever

#

I can tell you I had the issue as recently as this past weekend

vapid shell
#

Ah ok. There used to be a race where if an entity hadn’t come online homekit bridge couldn’t see it or configure it correctly

#

That was fixed for entities using the entity registry, but can’t be fixed for integrations that don’t

spare sphinx
#

yeah, they'd always be there, they just wouldn't do anything except fully close or fully open

vapid shell
#

Diff bug then

spare sphinx
#

yeah, maybe I should type up a bug report haha

#

I wanna figure out what the rogue FYRTUR is up to that just keeps turning even when it's at the top, it's not supposed to do that and I can sometimes coax it into stopping, but it's hit or miss whether that will last whenever I reboot HA, I think that's also only when controlling via HomeKit actually, I do most control using Siri on the HomePods so most commands come that way

turbid helm
#

yeah now that I'm using the skyconnect for both zigbee and thread it is crashing frequently

#

not quite stable enough

turbid helm
#

do you think it is the multi-protocol support? would it make a difference to have 2 skyconnects, one for each protocol on separate channels ?

inner torrent
spring bramble
still quiver
ionic wasp
#

Any tips at getting a thread device added? I'm runing HAOS on bare metal (Intel NUC) with the Skyconnect dongle. I've got an android phone with the companion app. I'm trying to add a device but it fails with "Can't connect to thread network home-assistant". My device is within a foot of the dongle.

tall lynx
#

Hello! I've got a quick question about using Thread devices.

Do you absolutely need a HomePod or Apple TV to make them work, or are there any USB Thread dongles that can do the trick?

vapid shell
#

Make sure to read all the pinned posts in the matter channel for the current state of play.

spring bramble
ionic wasp
ionic wasp
#

Just going to return the devices and wait until Thread has baked a bit longer.

tight ingot
#

I'm trying to switch away from the Apple Home app and HomeKit home hubs. Most of my accessories have native integrations but my Eve accesories do not. They use Bluetooth and thread. My home assistant is running on ESXi which is way to far away from the majority of the devices to reach bluetooth even if the server had bluetooth, which it does not. I do not want to add a wifi device just to have a bluetooth network. Are there any particularly easy to setup ethernet (poe not required) bluetooth beacons? Also, I would prefer to have more control over the OS than Home Assistant OS appears to provide. I want to be able to install things like my custom power outage shutdown software. Exactly how hard is it to install add ons in a container or core installation? I would prefer to use Ubuntu Server Pro instead of Debian as the supervised installation requires.

vapid shell
#

It looks like it lets you have all the benefits of haos without the limitations. That is not the case. If you read the small print, lots of stuff is forbidden and will make your system unsupported.

#

All my eve devices are connected by ESPHome Bluetooth proxies directly to HA to the HA HomeKit integration.

#

With external antenna

#

For thread you should consider using haos regardless of your os preference’s, unless you are comfortable with ipv6 and eg rfc 4191 . Stock distros won’t work out of the box. Ha has kernel patches and network manager patches you’d be missing.

tight ingot
#

I'm guessing not right

tight ingot
#

let me know if this is correct understanding: when https://www.home-assistant.io/integrations/homekit_controller/#adding-a-homekit-device-to-a-thread-network-via-home-assistant says "preferred thread network" that's just a thread network you've set as preferred by installing the thread integration and selecting add an openthread border router. It is not built into HA by default. apple has a border router that runs on home hubs and that is what I see in the Eve app under thread network details but others can implement those too. I'm guessing that thread border routing is a standard but there are also some variances and that is why the thread integration specifically says "add openthread border router" instead of just any border router. that border router can be routed between subnets but the thread traffic has nothing to do with vlans because it is a wireless protocol. I need a device that has the apropriate radios to be a border router and that device could be separate from the home assistant server.

in other words I could get a home assistant yellow or other device with required radio and put it on the iot vlan and run openthread border router and connect it to HA and join all my Eve thread switches to HA without using HAOS?

vapid shell
#

You’d also need an Android device to be able to commission matter devices onto a yellow

#

(There are some problems syncing preferred networks on iOS and we’ve not had an iOS developer to look at them)

#

HA has support for controlling the OTBR addon (which is HAs downstream fork of OTBR, it has patches that are note yet upstream). So it can automatically create a thread network using one. But you don’t need to use one. Any thread router will work.

#

The problem right now is there isn’t a standard for sharing the private key for the networks

#

Basically, no, I wouldn’t do that.

#

You’d still need patched kernel on your HA vm, you’d still need to learn enough about RFC 4191 to get that vm processing RAs from the yellow running the BR. Then the yellow itself would either need to run HAOS or you’d need to make your own container image that shipped the HA OTBR patches. You’d be missing all the integration that you get on HAOS to manage the firmware, and install and wire together multiple addons and integrations.

#

And after that you’d have a single BR that doesn’t support TREL (which is not as good as multiple google or Apple BRs which do support TREL) running in a configuration which is not supported by Ha devs.

#

Thread does use standard ipv6 routing, as enshrined in RFC4191, but mainstream support is woeful. Indeed, it turns out that on desktop Linux the mere presence of a border router can cause chrome to cancel downloads once a minute.

#

It’s the same routing for all thread routers though.

#

Border routers use icmp6 to announce their routes to the network. These are non routable.

#

So the BR can be on a different machine to HA but it must be on the same vlan.

#

During commissioning your phone must also be on that vlan.

#

I have my HomePods on a dedicated vlan. I then have multiple interfaces attached to my HA container. One is a Macvlan interface that is stacked on to the vlan for that HomePod subnet.

#

When commissioning I have to put my phone on the vlan too, then I move it back to normal wifi after.

neat echo
#

Guess I gotta shelf this for now. :(. If there are any ideas beyond the pinned messages in #matter-archived please ping me! Thanks

novel furnace
vapid shell
#

No they should be fine too

#

That said a year ago most problematic setups I investigated had Apple TVs and unplugging it was often a fix

#

That was the first gen that had thread, not the latest one

#

And it was probably because Apple TVs are hidden in av cupboards with lots of wires

novel furnace
vapid shell
#

From ha’s perspective there is no master

#

All thread routes have the same weight

#

So at an IPv6 level they are both valid to use at any time

novel furnace
#

Yeah, HomeKit seems to have an opinion about HomeKit, no idea how much thread traffic bounces through that second ATV.

vast sierra
#

I just got a matter motor from them to test.

I got mine paired direct to HA, but I can't get it to respond and move outside of blinking the LEDs. Have you had success yet via Matter?

vast sierra
spring bramble
#

@vast sierra use #matter-archived channel for matter support and keep in mind that running Multi protocol is experimental

tight ingot
# vapid shell When commissioning I have to put my phone on the vlan too, then I move it back t...

dang thanks for the detailed explanation. why does the HA server need to be ipv6 and routable and stuff if the border router is separate? when I went into the integration it just wanted the url for the otbr. I assumed that everything between the br and ha is just regular http then, and all the ipv6 was inside the otbr and on the radio network and ipv6 never touched my production network. tbh this is the exact kind of crazy uncontrollable networking I want to avoid by leaving homekit. using the homepods just for thread border routing might be better than it is right now with all my security cameras going to them but I still don't want to be hopping over wifi just to get to another wireless network. those homepods have been the most unreliable thing in my home and are the main reason i want to ditch homekit. I'm moving to sonos as well and won't have homepods. the setup instructions at openthread's website don't mention any custom os, in fact they just showed using raspberry pi imager i think so what's all the customizations and patches in haos about?

vapid shell
tight ingot
#

also what are some good in wall switches for a cieling fan? I don't want them to use wifi, and I want them to just work, similarly to how I was able to connect my hue lights

vapid shell
#

The http url is for allowing Ha to control a very particular BR

#

It’s like if you were integrating your actual router with HA and you gave it your routers web admin url

#

The actually data works more like a wifi access point

tight ingot
#

oh

vapid shell
#

Or well, a router

tight ingot
#

so it is actual ipv6 going over the production network between the otbr and ha. and I would need to route that manually in my cisco router to get it to HA. yeah no thanks

vapid shell
#

Well if you even could

tight ingot
#

and if you use apple thread it translates it somehow?

vapid shell
#

No

#

So all border routers are the same on the data plane

#

They use ipv6 RAs to announce a somewhat dynamic /64 via their link local address, which is also dynamic.

#

If you have multiple BRs on Linux youll see one /64 with multiple gateways, each will be the link local of a Br, HomePod or yellow or whatever.

#

The only way for you to route that through your enterprise router is for your router to do RFC4191.

#

But actually it’s not defined how routers handle that

#

Strictly following that RFC means you don’t get dead neighbor detection so are subject to 30 minute outages when your BR changes ip

#

Even if it did work, you’d then hit the multicast issues which come up in here a lot

#

The only difference between “Apple thread” and otbr is the “control plane” - that’s the bit that picks a thread channel, sets the encryption key, etc. It’s moot because Ha can use apples, Google’s, otbr.. etc

tight ingot
#

this is worse than i even imagined

#

zigbee isn't this bad right? that's what hue runs on?

#

I want the switches to connect using a wireless protocol that's designed for them, not wifi, and I want the backhaul to be plain ip.

vapid shell
#

I have zigbee2mqtt which is connected to mqtt

scarlet juniper
#

"Got it figured out.

When I changed my Android phone to the SSID of my IoT network segment and tried the Matter onboarding process it all worked and have my HA with Skyconnect working as Thread border router for my Smartwings blinds now. Super happy."

”Your phone only needs to be on the same SSID/Network as HA during the pairing process.
Skyconnect and HA is enough to function as a Thread/Matter boarder router.”

lavish thorn
scarlet juniper
#

Only my blinds are matter over thread just to experience and tryout. All other smart devices I have are Zigbee running with ZHA integration. And I must say the experience isn't as bad as some stories going around. Think matter over Thread is early but getting more mature quick as well.

vast sierra
vast sierra
#

I'm dumb. Had to set the limits with the remote. It's working fine.

tight ingot
#

I just don’t know what’s more secure and easier to find devices for zigbee or zwave but I’m pretty sure it’s one of those cause Wi-Fi and now thread are out

still quiver
#

The new ConbeeIII has a built-in Bluetooth to help with commissioning of Thread devices. Wonder if HA-BT can used to do the same thing?

worn plinth
#

i would find walking down to my server to pair something much more annoying than just using my phone

still quiver
#

well, I have 6 BT proxies in my home. It would be nice to pair the device wherever I'm at, but you would still need to use your phone or some interface I guess

vapid shell
#

There is a wishlist goal to use the proxies

#

We do it for homekit over thread

#

But interfacing the proxies with the matter addon is a fun challenge. The proxies code is in ha, so we’d have to export an interface that the matter addon could use. Then implement that in the c++ matter sdk.

#

Kinda wonder if we could fake the bluez dbus interface but it’s a virtual wrapper over ha Bluetooth

still quiver
#

And using the BT proxy approach could allow for auto discovery in HA. Every time I put a device in pairing mode my SmartThings always pops up on my phone saying to add a new device that's actually quite nice I'm sure you guys are all working on this too

fluid python
#

Hi everone !
I got my SkyConnect and wanted to install it as thread-device.
Now I am confused, because of an error message. ("wrong firmware - multiprotocol")
What's going on? Could not find anything related in the documentation.
Any advise for me? Thanks !!

upbeat cairn
#

If you get this repair, your SkyConnect is set up to be used with ZHA as a Zigbee coordinator. If you don't plan on using it for Zigbee, remove the ZHA integration.

fluid python
#

ok. But those this flash then remove the ability to provide matter-support? (that is not apparent to me here)

upbeat cairn
#

Nothing is permanent, you can migrate back to any firmware in the future very easily. If you want to use the SkyConnect for Thread, use the beta Thread firmware by installing the OpenThread addon.

fluid python
#

excellent. Thanks a lot for clarifying.

spring bramble
# still quiver And using the BT proxy approach could allow for auto discovery in HA. Every time...

Auto discovery of commissionable devices should already be do-able because that are just ble advertisements announcing the device. We're going to look into that soon as a nice starter. But the real deal would be to use the Home Assistant Bluetooth integration (so including proxies) to commission devices but that will be a hell of a job so not possible anytime soon. For now I think we'll just start with a simple bluetooth adapter inside the HA server for this scenario and of course our current implementation where you just use the Companion App.

spice imp
bronze fog
#

@spice imp I agree. Everyone has a phone. Put more effort into other aspects of HA.

vapid shell
#

I don’t think it’s a priority on anyone’s list.

#

But also this is open source

#

“Put more effort into other aspects of ha” is wrong headed

#

Volunteers can do what they want

#

I’ve known dbus for 16 years or so, and making that kinda of bridge is something I would have done for fun in my youth, and there are people that would have benefited from it.

vapid shell
#

(That said there are problems with phones. Especially for SkyConnect users, which won’t be classed as experimental forever, and letting people use the Bluetooth on HA would solve them)

spring bramble
# spice imp would it really be worth the effort if you can just use your phone?

Exactly why we never implemented it and went for the shortcut by using the Companion App but that does only work reliable when using Apple or Google border routers, sending our own Thread credentials (to use HA as Border router) is unreliable on Google and does not work at all on iOS. Luckily nowadays HA has an iOS developer again so we really hope he can find out what's wrong. 🙏

spice imp
spice imp
#

I agree it would be a cool feature, thats probably is fun to get to work though

vapid shell
#

Is relying on vendor sdks actually the right way, or just a work around taken for speed.

spring bramble
#

Its perfectly acceptable to need a companion ap to include devices to a matter controller. Heck, that is how all controllers work

#

Problem is using your own border router in the mix and/or be able to commission using the HA frontend alone. It adds a lot of extra complexity

spice imp
spring bramble
#

I think the issues with sharing the thread credentials will eventually be worked out, it is a goal from the Thread alliance as well

spice imp
spring bramble
spice imp
#

And my point was never that the bluetooth proxy for matter should not be done. I was more questioning why people want it if there is a valid way of doing it already, since i dont think it adds a lot of value.

vapid shell
#

There are people that don’t want to sync their credentials into Google’s ecosystem, and have Android phones without google play services.

#

There are people that have BRs and Ha on a vlan, and don’t want to put their phone on that vlan.

#

I’m neither of those and wouldn’t use my free time (ha) on those

#

I do think it’s important for the ecosystem to not be reliant on google and Apple to do commissioning.

#

Otherwise it diminishes the value of matter for me quite a bit.

#

(I guess that’s because I’m a Firefox person. Safari and chrome do not make for an open web)

spring bramble
latent schooner
#

what about a Tuya border router 😛

spring bramble
latent schooner
#

you'll have to in the future because you know its coming

spring bramble
latent schooner
#

i have a glinet router too 😄

spring bramble
#

It would be super cool to have a few of those devices in your home as OTBR and bluetooth proxies

latent schooner
#

my Tuya border router got discovered by HA

spring bramble
#

(just joking)

latent schooner
#

waiting for my thread device to see if it actually works

spring bramble
#

OK cool, let us know your findings!

spice imp
spice imp
latent schooner
#

they're available to buy

spice imp
latent schooner
#

this is local CCP 😄

spice imp
static spear
#

hey all, odd question - I initially migrated a Google thread network to HA so my skyconnect can use it. I've since gotten rid of the Google devices but the name listed on my network is still the Nest one. Can I reset it back to the default 'home-assistant' one?

#

i know the name of the network doesn't actually affect functionality - this is purely just an aesthetic choice

median pagoda
#

Hi all, I have a question too.
My HA installation is on a casa os (so it's a container) and I have a skyconnect which is passed through to the container. The ZigBee integration can utilize it but I can't enable Multi protocol because that only works with HA OS. At least that's what HA tells me when I want to go into the hardware configuration of the skyconnect.
The thread integration on the other hand just directly asks for a (O)TBR.
Could I just run a OTBR in another container and make it use the skyconnect too?

arctic shore
#

Came here to ask exactly the same question ... Settings->Hardware->Multiprotocol doesnt exist ..

#

I am running HomeAssistant Supervisor

serene prawnBOT
#

@arctic shore I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
spring bramble
spring bramble
static spear
#

i moved off google because i wanted to try Alexa

vapid shell
#

I don’t think I have seen many people (if any) in here with Amazon border routers. Have you been able to extract a meshcop TLV from them? Have you found out how to make them join an existing thread network?

#

Right now the 2 best experiences for Matter/Thread and Ha are to use iPhones and HomePods or Android and nest. Anything else and you are somewhat on your own.

static spear
#

the echo reports it's only on 1.1.1 for thread so can't seem to join an existing network, and also haven't looked into extracting any TLVs - that's next on the list

vapid shell
#

Note that nest and apple are on 1.3 and also support an extension called TREL which allows them to mesh over their infrastructure link (WiFi or Ethernet) which helps to avoid thread mesh dead spots - so called partitioning - which can cause havoc for ha. Amazon won’t be able to beat multiple HomePods or multiple nest devices until they catch up.

arctic shore
#

I have managed to sort out most of the errors, but I am still stumped by the 'Failed connectivity' when trying to add a device to matter. Is there an easy test or log somewhere I can look for - the Silabs otbr logs just shows RA's and Unknown Neighbor messages

arctic shore
#

the matter server does not seem to get any provisioning requests

twin vine
arctic shore
#

I was asking here as I dont know if Thread is getting the data 😛

#

thanks 😄

#

doing a tcpdump of wpan0 shows nothing

#

khadas@Khadastest:~$ sudo tcpdump -i wpan0 -vX
tcpdump: listening on wpan0, link-type RAW (Raw IP), snapshot length 262144 bytes
...... [tumbleweeds].....

#

its like the silabs multiprotocol is not forwarding data

tacit dirge
#

Kinda feels like threads on HA needs a bit more to be stable

#

Kept losing all the thread devices but they'd come back with a full reboot sometimes 😦 think I'm just going to run them through smart things until it stabilizes

vapid shell
#

Are you / were you running on haos? What border router were you using

tacit dirge
#

Haos with skyconnect

#

Vm in truenas scale. Passing through usb device as nec-hxci

#

Honestly could be the passthrough. Wasn't very clear how to configure that

#

But it let me set up the thread network. Just kept dropping and haos sees the skyconnect

vapid shell
#

Multi-pan or thread only firmware?

tacit dirge
#

I tried multi. I am thinking to play around with passthrough options and do thread only today though

vapid shell
#

Multi is known to have crash bugs

#

In the dongle firmware

#

Thread only should be better

#

Though Apple and google brs are still the top rated way to do thread in ha right now

#

There’s some pinned posts in #matter-archived on expectations for SkyConnect thread from a maintainer

#

There’s also some discussion in there about using the “share” feature of matter

#

So you can use the smart thing brs

#

And bypass the need for SkyConnect

tacit dirge
#

Yah that was my thought

#

It feels like sky connect is issue

tacit dirge
#

I'm going to manually flash the latest thread only firmware and go from there

simple stag
#

are there any written instructions for how to make my apple (tv) and google (hub max) thread networks match my home assistant (sky connect) thread network?

#

I have some devices in my HA thread network, but would like the network roaming to work with these other border routers

vapid shell
#

Right now consolidating your brs is a bit of a myth

#

There are somethings that you can do, but the benefits are questionable. There are somethings you just cannot.

#

There are somethings that happen by accident that can’t be easily replicated

#

Eg you can’t get your Apple br to join another thread network. The best you can do is get its secret key and join another br to its thread network. But doing that isn’t straightforward. People have done it by buying particular nanoleaf products before.

#

However SkyConnect can’t do TREL to the Apple mesh so you might be subject to partition, where one part of the mesh is unreachable from another. BRs with TREL can route thread traffic over WiFi to compensate when that happens.

#

I don’t know about the google hub. Android doesn’t like you not using its network. Getting it to use another preferred network can involve resets of google play services, which might impact google pay etc.

#

But you can go the other way more easily than with iPhone, ha can sync the preferred network from google.

vapid shell
simple stag
#

Thanks for the info. I currently just have a Eve plug in switch and two aqara door sensors. I added all through home assistant Mobile app on Android

inner torrent
#

You can join your skyconnect to your Google thread network but not sure about apples

#

I started with a skyconnect only then later merged it with my Google thread network and it worked fine

arctic creek
#

I think I know the answer to this question, especially when theres no jailbreak for ios 17, but is it possible to use an iphone 15 pro as a thread border router?

#

its only me that controls the devices and I don't want to shell out money on a homepod

spice imp
upbeat void
#

Hi all, I'm trying to get HA to use my HomePod Mini as a Thread border router. Under the Thread menu it shows up as a border router, but it doesn't seem to do anything (I can't click on it or anything like that). Is the integration not working at all yet?

#

Or do I need to order some sort of Thread dongle in order to control devices that are managed by HPM?

tacit dirge
#

Thread+matter?

#

The way it works is you add device > add matter device > scan qr code or type code > auto adds to thread border router

#

devices show up under matter

upbeat void
#

I think so, it's an Eve door sensor that connects to HPM via Thread. (Or is it thread over matter? Beginner here)

#

I worked around it by having HomeKit set a dummy input boolean on HA using automation and using the value from there, but I'll see if I can get the sensor to show up under the Matter integration. Thanks!

#

Ah OK, so it apparently doesn't work once it's paired to HomeKit. I'll have to unpair it and then add it to HA, but I think this setup works fine as-is

serene prawnBOT
#

@open hamlet I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
open hamlet
#

Oh, didn’t realize line counts were limited here, not ideal .-. Apologies I was just trying to give enough info to actually describe the problem

#

TL;dr Looking at the matter server logs I noticed a massive spam of this message during setup right before it failed

SRV record already actively processed.

Any ideas on how to make it not processed to allow it to add?

mellow night
#

Bought an Eero router, how can I add it as my Thread/Zigbee hub? It has the radios.

twin vine
#

its a amazon hub?

#

oh yeah. apparently it is. not too sure how well it acts as a matter hub, and not sure it can do zigbee

mellow night
#

It has both a Zigbee radio, it's also an official Thread certified product. I was hoping HA will discover it automatically but I didn't see it

twin vine
#

uhh, no. have you tried to add a matter device at all?

#

I think the Eero only works with Alexa for its Zigbee support, so no real use.

#

it does appear as a thread border router

mellow night
twin vine
#

that was posted a while ago. so not sure

#

maybe try putting in on the same channel as your zigbee netwrok

mellow night
#

How do I even discover it on HA

twin vine
#

do you have a existing zigbee network

mellow night
#

What about Thread tho?

twin vine
#

thread it works, it acts as a border router. you need thread devices tho. and somehow get the thread creds for it

mellow night
twin vine
#

the skyconnect does as well, its just multiprotcol is kinda jank

mellow night
#

I wasn't able to connect it again through the Matter integration, IDK what happened but it got disconnected and is unavailable every since

twin vine
open hamlet
#

Continued from #matter-archived

Honestly I’m just using HomePod minis and ATVs for my thread setup, I’m not really sure how mixing vendors goes for borders I just got lucky I recently switched to iOS. I’ll be trying out a custom border to start diagnosing my network a little more and walk through where things are going wrong.

#

As far as the thread network home assistant automatically found it for me, not sure how to get the link

inner torrent
ionic plaza
#

I wonder where can I find the pskd of HomeAssistant Thread Network hosted on skyconnect? I am trying to have my esp32 h2-s3 board join the network

ionic plaza
wary mountain
#

Anyone have experience with the Google Home Hub (Gen 2)? It goes on sale tomorrow for $50, and I was thinking of getting one to help the mesh network.

But I don't want it to take over my Home Assistant and Skyconnect OTBR network.

inner torrent
#

To be clear, you can use Google's thread network without adding devices to Google home

wary mountain
#

And that should remain local, right? And not send the thread status of every device to Google?

#

Not that they have to look hard. I have the Google assistant integrated.

#

I think that's right. Thanks, @inner torrent

inner torrent
#

That's my use case, I use their hubs but only have devices in HA

arctic jasper
#

Does thread require additional border router to improve network performance just like zigbee does?

#

I would like to use sonoff dongle E as thread border router

vapid shell
arctic jasper
#

Unlike zigbee in which some of the mains powered devices don't work as routers?

vapid shell
#

I think interoperability was a problem with zigbee.

#

If you do have multiple brs and they support TREL (like apple and google) then they can mesh over thread and wifi/ethernet. That means if your mesh has dead zones, your WiFi/ethernet might be able to compensate.

#

Right now for maximum stability the advice is still to stick to apple brs if you have an iPhone and google brs if you have android. The user flows are much easier in that case. The stability with haos (if you meet the network requirements) is good. And they support TREL.

open hamlet
#

Do I need to configure ipv6 in proxmox and assure haos has a valid ipv6 configuration if there’s global ipv6 on our network?

Doing some reading as to why I can’t get this last bulb to pair for whatever reason

vapid shell
#

Your layer 2 setup (switches in hardware, bridges in software, and how your WiFi is connected to your lan) can have an impact

#

Thread is designed to work without cooperation from the host lan. The borders advertise routes to everyone on the LAN. The matter controllers talk to thread devices via those routes.

#

But yeah, vlans break that.

#

You do need haos to have ipv6 turned on, and it can’t have a static ipv6 config iirc.

#

(With global ipv6 your brs may ask for a public /64 from your router via dhcp6, and then give addresses from there to the thread devices, but it’s not mandatory). Proxmox shouldn’t be involved in that, as long as your vm has a bridged interface on the same lan as your router.

spring bramble
spring bramble
# arctic jasper Does thread require additional border router to improve network performance just...

It is not needed but is greatly recommended as it takes away the big issue that Z-Wave and Zigbee have: a single point of failure. Adding more border routers add redundancy and the bandwith is improved. Next to border routers (the gateway from thread radio to your local network) you also have the routing devices in the thread network, just like with zigbee. So major rule of thumb is the more border routers and routers, the better it is.

spring bramble
open hamlet
crude willow
#

I have been trying to add multiple thread devices on homekit/smartthings on a company network that should not have any limitations . But none of them can be added. Does anyone know what setting could be causing this issue?

surreal nimbus
#

I have problems re adding my nanleaf A19 light bulb
all the times I had to re add it before it was no problem, after I add it using the nanoleaf app it would just show up in HA and I could add it using the pairing code and the apple homekit integration

but now it doesn't show up in HA anymore
the nanoleaf app tells me its connected over thread and in the home-assistant thread network but I get nothing in HA

#

I am using the skyconnect for thread

#

Apparently restarting my phone, resetting the light bulb, trying it another few times and praying during the paring worked
I ❤️ thread + nanoleaf

spring bramble
spice imp
#

Or was it never commissioned to HA?

#

Nvm, i get it now

#

Thought it was something similar to my eve Thermostat, that showed offline for 18 hours until i restarted HomeAssistant.

digital pelican
#

Hi. Last night I lost my complete thread network. All devices are offline (3 Nanoleaf bulbs, 2 Onvis plugs). I restarted my Homepod mini and my matter container (version 4.0.2, HA version 2023.11.2). The matter container logs show that re-subscription to all my nodes is unsuccessful. Any ideas what I could try?

quick bronze
#

I see Nuki have announced their Matter over Thread lock - it'll be interesting to see how it works in reality once it's out in the wild

digital pelican
spice imp
digital pelican
open hamlet
# digital pelican So, after restarting the Homepod Mini and the matter container multiple times - ...

It seems like sometimes you just have to wait to reboot, I had the breakers off for a couple hours after a day of them being unresponsive and after a full reboot of everything they just started working again. Not entirely sure what’s going on when it fails but I’m setting up a debug environment to figure it out.

If it happens again would you mind trying to just turn all the borders, devices, and matter server off for a few minutes. Then turn them on in order of discovery borders, devices, server.

I’m waiting for mine to fail again, seems to happen every couple of days at the moment

spring bramble
quick bronze
lavish thorn
#

Google Nest Hub Max is my only Thread Border Router - is it possible (or helpful) to control what channel it chooses?

#

Slightly related: when I tried the Multi-PAN firmware for my coordinator I was in a strange situation where the ZHA zigbee network and the HA Thread instance ended up trying to use different channels

normal arch
#

I set my ZHA channel to be the same as the thread channel, no problems

lavish thorn
#

Where did you make that (those two) settings? When I tried it told me to change them in the hardware settings, but I couldn't find that

normal arch
#

settings --> devices & services --> zigbee home automation --> configure

#

I only changed that setting to match the channel my nest hub was already using

digital vine
#

Hiya I've been reading and now I'm looking to start a home assistant setup using matter based on thread -skyconnect, echo 4th (though I think it can be any as I will use sc as thread border router), maybe nanoleaf bulbs and onvis smart plugs. Are there any alternatives for either bulbs or smart plugs currently anyone would recommend for this?

slender hornet
#

Before you buy anything, I'd suggest you start by reading the pinned messages in the #matter-archived channel. I did not have good luck using the skyconnect as a border router. I wound up picking up a Google Nest hub v2 and everything worked flawlessly so far.

vapid shell
indigo rock
#

Is there a non spammy way to post a log from the border router log

#

Code block?

#

Can I post images?

#

Okay basically the biggest summary

#

otbr-agent[182]: 00:04:15.804 [W] Mle-----------: Failed to process UDP: Duplicated

#

These are filling up the log of the openthread border router addon

#

Is this a problem or can it be ignored?

#

otbr-agent[182]: 00:03:10.033 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:03:15.211 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:03:15.217 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:03:33.192 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:03:33.200 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:03:37.286 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:03:37.294 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:04:10.293 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:04:10.302 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:04:15.797 [W] Mle-----------: Failed to process UDP: Duplicated otbr-agent[182]: 00:04:15.804 [W] Mle-----------: Failed to process UDP: Duplicated

#

Etc

#

I can paste the whole boot up log but I hit the paste limit pretty fast for discord lol

vapid shell
#

It’s probably fine, unless you’ve noticed a problem. I know there are some homekit… I’m going to call them limitations.. that cause it to generate duplicate packets when the target device is battery powered.

#

(COAP timeout expires before thread delivery interval, causing a retry. And there was no knob in the COAP library to stop it).

serene prawnBOT
#

@indigo rock I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
indigo rock
#

Areas any of the errors here about failing to write, etc anything?

#

The main thing I’m hoping to do

#

Is make some HomeKit thread devices controllable from an android phone without needing a Samsung border router if possible

vapid shell
#

No idea what those start up errors are

indigo rock
#

Me either. I have two HomePods two Nanoleaf and two onvis matter plugs so far

vapid shell
#

I use HomePods for my brs, Apple and google currently have the best and most reliable.

indigo rock
#

I merged HomeAssist into the existing network

vapid shell
#

Nanoleaf make everything unstable

#

Using HomePods with otbr a bad idea

#

You nerf TREL that way

indigo rock
#

What’s TREL?

#

Any way I can completely reset all of homeassist thread settings to default and try again without having to reset the whole lot

#

It’s a fresh install so wouldn’t be a big deal

#

Just annoying

vapid shell
#

It allows BRs to mesh over thread and your infrastructure network at the same time

#

It solves network partitions

indigo rock
#

Is that why Nanoleaf is constantly becoming a mesh extender and child

#

Back and forth

vapid shell
#

Nanoleaf firmware is buggy right now

#

Everyone is waiting for the next beta

#

A day doesn’t pass without us rolling our eyes at their firmware

indigo rock
#

Is there a way I can proxy control of my thread devices onto my android without running a border router in homeassist

#

I just want to make it possible to use gps automations or something

vapid shell
#

I don’t know what you mean

#

Can’t you just use the HA app?

#

If you mean export a matter bridge, no

#

You don’t need OTBR to use the HomePods with HA

indigo rock
#

I mean

#

I have a matter/thread onvis plug

#

It’s in my iOS home app

#

I want to be able to turn it on and off from home assistant

#

Snap with the Nanoleaf

#

So I’m not the only one who can turn them on and off

#

Can I pass control over to home assistant by using the HomeKit integration? Will I need thread working?

digital vine
vapid shell
# indigo rock It’s in my iOS home app

For HomeKit the protocol: Remove it from iOS through the home app. Do not reset it. It will now be discovered by home assistant over your HomePod (if you have it on same vlan as ha). For Matter, there should be a facility to “share” from the Home app to home assistant. Again this uses your HomePods. In neither case does this require OTBR or multiprotocol addons. In neither case does it require the thread or OTBR integrations.

vapid shell
indigo rock
#

Thanks for your response too that’s great I’m gonna try one shortly

vapid shell
#

WiFi extenders are especially problematic

#

Some people have a really hard time with Unifi

#

(Again, works fine for me, or it did till my gateway starting making a cap pop noise once a second)

indigo rock
#

I’m going to try and get one of my devices over soon

#

@vapid shell can you clarify, do you have your HomePods integrated into HA? It’s detecting mine as AppleTV

vapid shell
#

Thread is like wifi

#

You don’t need to add your router as an integration to use your wifi devices with ha

#

When a device is on thread it’s reachable over ipv6 by any device on your lan

indigo rock
#

Nice

gritty niche
#

Hello everyone,
I've been trying to integrate my Eve MotionBlinds back into HomeAssistant for a few days now.
A complete reset and subsequent removal in HomeKit as well as a reset of the HomePods does not seem to be enough, as I get the following error message:

This accessory is already paired with another device. Reset the accessory and try again.

Does anyone have any ideas what else I could do?

All Devices are in the same private network

meager galleon
#

I have HA and all that set up on docker and I'm trying to setup an open thread border router, but when I give it the url it just fails to connect. Is there a special port or address it's using?

twin vine
#

Do you have some sorta thread radio somewhere connected?

#

Also, I think HAOS is needed to have OBTR’s work

meager galleon
#

I do, I'm running openthread border router in another container

#

hm there's nothing in the documentation that it's a custom fork of it

vapid shell
#

HAOS is certainly preferred

#

Because of kernel patches and all the integration to make it somewhat plug and play

meager galleon
#

Unfortunately I'm not able to wipe my OS

vapid shell
#

Container can work, but you won’t get as much support simply because it’s not the development focus

#

You shouldn’t try to use the OTBR integration in your case

#

It’s used by haos to automatically configure OTBR

#

By not using haos you have opted out of that

#

And that’s all it does, so you don’t need it

#

If you are trying to set up the thread integration you need to use the TLV method

#

Not the url

meager galleon
#

my understanding is that add-ons are mostly just containers anyways though

#

so it should be possible to configure it, right?

vapid shell
#

If you have an otbr with all the patches from the add on

#

And while you are at it patch your kernel

#

And network manager or whatever you use instead

meager galleon
#

looks like the only major change is for deleting datasets

vapid shell
#

There were 4 or so api related patches last time I looked, some might have landed upstream

#

The point is that integration is to integrate with that add on

#

And you don’t need it

#

All it does is create a thread network

#

You can do that manually and stick to upstream OTBR

meager galleon
#

How do I get my matter server to know about my thread network then?

vapid shell
#

You get the operational dataset TLV from the container and add it to ha through the … menu

twin vine
#

Doesn’t it get that information when a device is commissioned?

#

If it even “knows” in the first place

meager galleon
#

I think I found why it wasn't connecting - OTBR needs port 8081 exposed for the REST API

mellow night
#

@vapid shell You previosuly told me that I can add my Nanoleaf through Android's Matter comissioning. However I'm having issues doing so. I scan the QR and wait until I get error Can't find device. What do I do?

#

Skyconnect is my OTBR

indigo rock
#

Don’t scan the qr code

#

With matter you pair it once then use your eco system menu to generate a “pairing code”

#

Second system uses the pairing code

mellow night
#

Can't seem to find a pairing code in Nanoleaf app

#

Any alternatives?

twin vine
#

So how did you connect it in the first place, what ecosystem?

#

Only using the OBTR to sky connect which is HA?

#

Coz, if you factory reset it, (if you have paired it before without removing it properly). Might work

mellow night
#

First time was with the pairing code/qr code on the bulb to Nanoleaf app.

#

I've factory reset multiple times, can't figure out how do I get it work with HA. Should I unlink the Nanoleaf app and connect directly with HA?

twin vine
#

That would have connected over Bluetooth. Hmm not sure how that influences matter/thread pairing

mellow night
#

It did, but then I was able to get it on Thread becuse I have a SkyConnect

tacit dirge
#

Was struggling to connect new devices via thread / matter. Just poked around and somehow my thread border router got unmarked for Android credentials

#

Smh

#

And now it all just works

#

Uhgfgg

#

Probably got reset when I updated my truenass install

inner torrent
# mellow night I've factory reset multiple times, can't figure out how do I get it work with HA...

You don't interact with the nanoleaf app at all for matter commissioning.

First commission using your ecosystem (apple/Google/Samsung). Then there should be a setting to share the device to another a secondary ecosystem via QR, pairing, or directly. That's when you add it to HA. I'd suggest not using QR or pairing and just sharing directly if possible.

You can also attempt to commission to HA directly if you've not previously commissioned it (or if the bulb has been reset)

#

#matter-archived has some good pointers on the pinned posts. Note that using the skyconnect as your only BR is not recommended

#

Only add to NL app after commissioning and pairing is finished

normal compass
#

Hi, has anyone successfully connect EFR32 based network (ethernet) coordinator with zha and multiprotocol support?

upbeat cairn
#

You'd need to build firmware for it but there's no reason for why it wouldn't work. The multiprotocol addon can't natively communicate with a remote coordinator over TCP so you would have to expose it locally as a virtual serial port with socat on the device running the addon. I don't think anybody has done this before though.

rare ibex
#

I think long term I’m more interested in just using the esp32 border router project with a plain rcp fw. Espressif just released v 1.0 too.

mellow night
spring bramble
normal compass
half marlin
#

how can i see in that thread network mz devices are?
in eve app it shows me only one device, in the nanoleaf app i see all bulbs are connecte via thread

#

norlamy i should see them also in the eve app

inner torrent
ionic plaza
mellow night
#

Also to reiterate my only BR is SkyConnect, previously by some miraculous reason I had added Nanoleaf lightbulb on HA and it was though my iPhone! I reset the bulb and haven't been able to add it back ever since.

tacit dirge
#

anyone have good thread external plugs or switches?

#

Just Eve?

narrow terrace
#

Hey folks, I'm currently setting up my HA Yellow for Matter and got myself a few Nanoleaf Matter Bulbs for that purpose. i'm curently trying to figure out whether I need the "OpenThread Border router" or the "Silicon Labs Multiprotocol" Add-On.

From my understanding, I only need Silicon if I would want both Matter and Zigbee while the OpenThread Border Router is fine if I want to stick with Matter only, correct?

Is there anything else to be concerned about or to consider in terms of known issues or features (or expected support)? I only had a few Zigbee bulbs prior but removed them and would like to go full Matter for the future.

I tried looking in the documentation, HA forum and Reddit but wasn't able to find anything too conclusive. So thanks in advance for your help here 🙏

sick swan
#

Currently there are also reports of issues (sporadic crashes) with the Silabs Multiprotocol implementation, so using the pure Thread firmware on Yellow (and hence the OpenThread Border router add-on) is the better route.

#

That being said, the Matter/Thread implementation in Nanoleaf bulbs are known to be a bit buggy from what I've heard 😰

narrow terrace
#

Yeah, I accidentaly set them up in a Google nest at first because that was still in my WiFi.

but yeah, will see how well it works. This is mostly to test things out for now. Also have an Eve Smart Plug on the way.

But thank you, ten I wil try the OpenThread Border Router^^

#

Would it cause any issues to set the Baudrate from 460800 to 921600?

That would potentially just make it all faster and more responsive, right? Or what am I overlooking here?

Usually, there's a reason for default settings to be the way they are 🤔

#

or is it just abour power consumption?

sick swan
#

The Thread radio's bitrate is 250kBit/s, so a faster baudrate isn't really helping. Anyways, it would need a different firmware as well, just changing the firmware on add-on side doesn't help.

#

We bundle firmwares for SkyConnect and Yellow and then also make sure the setting is right. The setting is meant for custom/other firmwares.

narrow terrace
#

great, thank you. Then I will keep it at 460800 👍

vapid shell
#

@narrow terrace make sure to read the pinned posts in #matter-archived, they have a fairly up to date set of expectations about what works well and what works less well from the matter maintainer.

narrow terrace
#

Ah, darn. I wish I would've seen the one wit Google Home Nest devices sooner. That caused me a lot of issues.

Time to roll back and redo everything 🫠

But thank you, very helpful

pine bolt
#

hallo, new guy, etc. I read the matter pins and I have the simplest question: what's the easiest non-commercial way to get/buy a thread border router running in short order? (recommendations welcome)

vapid shell
pine bolt
#

I have beef with apple and I don't have anything Google that can do threadborder right now :/

#

plus I run HA in docker.

#

so tldr: in the immediate i'm somewhat boned, essentially?

vapid shell
#

Yes

vapid shell
pine bolt
#

absolutely

#

(I have multiple)

vapid shell
#

Usually the people that strictly want open have issues with google but not Android

#

Hence checking

pine bolt
#

i have beef with the pencil pushers who took over Google and made it (more) soulless (than before, possibly), yes.

vapid shell
#

So if you have a google account and google play services and a flat network then a skyconnect might work for you, with the caveat that it’s more beta than some of the other choices.

pine bolt
#

the only skyconnect vendor in the US has no immediate stock and only a queue for December - and I fly out in the middle of next month so that's also a bad scenario :/

#

i only learned of the thread border dependency yesterday when getting a door sensor. yes i should have read up more but nevertheless.

spice imp
pine bolt
#

is it that those sticks can be flashed to do Thread?

spice imp
#

You can flash basically every stick that runs zigbee to thread. The question is just how "easy" it is.

#

So there you need to google if you can find some thread rcp builds

pine bolt
#

welp. ordered one from amazon. we'll see if I give up 2, 5 or 50 minutes in

pine bolt
#

eugh. the stick is detected, darkxst sees it, but it ends up with a connection failure

#

even after i managed to manually flash the right firmware using SecureCRT on Linux

pine bolt
#

i have everything set up, addons running, zigbee flashed and detected

#

and when I try to add the device, android still tells me there's nothing to be had

#

still yelling about requiring a border router even though there is one

#

the one thing I did weird is that, in my nerd hubris, I kept the hostname

vapid shell
#

So you’ve got the otbr addon and matter addon, and otbr, thread and matter integrations?

#

(And not the multiprotocol addon)

#

And if you go to the thread integration, and click on configure, do you see a thread network and a border router?

#

You don’t now, but did you ever have a google nest product that might have acted as a border router?

#

Is the android and your ha on the same vlan / subnet?

pine bolt
#

Will reply when i get home. Thanks for the handholding through this

pine bolt
#

Right then

So you’ve got the otbr addon and matter addon, and otbr, thread and matter integrations?
Indeed. Matter and OTBR addons online and active; OTBR, Matter and Thread integrations also online
And if you go to the thread integration, and click on configure, do you see a thread network and a border router?
The thread integration says "no devices or entities", but clicking on configure does show an OpenThread Border Router, that also has the icon for "this is the network for mobiles"
You don’t now, but did you ever have a google nest product that might have acted as a border router?
The first thread border router to ever grace any of my apartments is this one. My only active "nest product" is a Google Home Gen1.
Is the android and your ha on the same vlan / subnet?
I believe so? but HAOS might be "under" its own virtualized subnet - the homeassistant eth0 is not on the same subnet, and chances are the OTBR node would also be under its own network device and not poking my router directly

#

though the terminal applet does give me the true HAOS IP as well, and that one is on the right subnet

#

i'm in the OTBR container, it's running in host mode and it has the right ip

vapid shell
#

And your phone has an ipv6 address starting fd something or other that matches that?

pine bolt
#

phone has fe80::b4da:3ff

vapid shell
#

Thanks your link local

#

They both need to have a ULA

#

Fe80 is like a 169 self assigned address. ULA is a bit like (but not strictly so) a 192.168.x.x address

pine bolt
#

well they do have ipv4 addresses at the very least

vapid shell
#

They need ipv6

#

Your br creates one /64 ipv6 subnet for your wifi/ethernet side and another /64 for your thread mesh

#

You’ll be able to see both in the OTBR container

#

But your phone should have seen the announcements from OTBr and have a matching one too

#

It will start fd rather than fe

pine bolt
#

unifi might be doing a unifi

#

imgur dot com/XfPvRaq

#

(dunno about the pic policy here)

#

Client Address Assignment might be the thing biting me

vapid shell
#

Your router shouldn’t be involved

#

It doesn’t need ipv6

#

Just OTBR and your phone

pine bolt
#

i know but the pic i shared is for devices on the network, i think

#

like, my mian comp has ipv6s under fe80 and 2600

vapid shell
#

PD is something your router does to share its ipv6 allocations on the subnet

#

It shouldn’t matter

pine bolt
#

all right then. still, going back to the main issue, yes the otbr container has the right ethernet device, and so i am still stumped

vapid shell
pine bolt
#

in the case of fd, none of my devices seem to have an fd

pine bolt
#

wtf

#

i re-set-up all my light bulbs and NOW google recognizes the openthread

pine bolt
#

chances are that was some cached status

narrow terrace
#

hey folks, I haves tried to set up the Open Thread Borer router on my HA Yellow for several days now but I cannot even start it anymore. If I click on the Lauch button, it just tries to launch it and then crashes.

I tried uninstalling all Thread & matter add-ons and integrations but can't see to narrow down what causes it. The protocol doesn't mention anything that would explain the add-on crashing (at least, as I read it). Will put the protocol below as separate messages.

My configuration has device set as /dev/ttyAMA1 as described in the documentation. My baudrate is at 460800 and U have hardware low control, automatic firmware flashing and the OTBR firewall all enabled. I have not actived the Web or API port.

serene prawnBOT
#

@narrow terrace I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
#

@narrow terrace I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
narrow terrace
#

I've been thinking about trying the Silcon Labs Multiprotocl add-on instead but since I don#t want to use Zigbee and I was recomended here to use the OpenThread BorderRouter here, I didn't do that yet

jolly maple
#

Hey all, I don’t know if this is the right thread but I try my best. So I have a HA configuration running on a Raspberry Pi3. For a couple of days now I try to connect the sky connect dongle. But I have a lot of issues. With the standard firmware it was not automatically shown.
With manually setting up the ZHA integration, I was able to include all of my zugebe devices rather flawlessly. But I am not able to get the multiprotocoll running or thread connectivity at all. It is also not shown in the hardware tab. Am I missing something obvious ?
I tried the multi protocol firmware , unfortunately without any results.

crude willow
#

I know this is a Home Assistant discord, but I am looking for a (matter) thread border router that I can connect with KNX. Has anyone seen such a device on the market ?

viscid swallow
#

I'm trying to setup the web interface of the SI labs multiprotocol addon to debug something. However, it says to set the rest API port (I did), and the web UI port. But the only other port I have is emberznet ezsp/ash port how do I get the web UI port to be available?

serene prawnBOT
#

@narrow terrace I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
#

@narrow terrace I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
narrow terrace
#

(appologies for the Spam. Not Sure how to else share the Protocol Here(

serene prawnBOT
#

@narrow terrace Please use a code share site to share code or logs, for example:

Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.

quick bronze
narrow terrace
#

Totally overlooked that. Apologies 🫠

#

Removed the Messages then and will Post a Pastebin later on

narrow terrace
#

both the silicon and OTBR addons crash on the same final part

fickle mantle
narrow terrace
#

The loading circle on Launch Just keeps Spinning and then it never Changes to the "Stop/Reboot" UI

quiet stirrup
#

Hi there, I'm having some troubles configuring my text to speech integration with my google nest devices, I have added my devices in Google Cast integration but after configuring it, I try to launch a test but nothing happens, opens media in the nest but fails.

quick bronze
#

Wrong channel

inner torrent
narrow terrace
#

Good suggestion. Only did a reboot form within the UI. Will try in a few

narrow terrace
inner torrent
vernal herald
#

Can someone help me out with the skyconnect? I have it setup and running great under zigbee (zha), when I enable the multi pan as I want to be able to use thread it installs and fires up but my zha does initiliaze and says that the radio was setup under zigbee only firmware and to use it flash that firmware back...am I doing something wrong? I really would love to have thread going through home assistant as my nanoleaf lights take 2 minutes to respond right now to any comman

spring bramble
#

If you want to keep your zigbee network running stable it is currently not advised to enable multi pan

#

multi pan is a bit experimental and may destabilize your zigbee network, esopecially if you have a lot of devices

vernal herald
#

but lets say when they do make it stable, how do I install it so zigbee will initiliaze and run, forget being flaky, mine doesnt even start up

#

I am following the instructions to a t

spring bramble
#

using the skyconnect for either thread or zigbee is stable but still we are working on a lot of bits to actually use HA as thread border router. Best to use prebuilt border routers that are available, such as apple homepod (mini) or Google nest hub v2

spring bramble
#

But like I said, not really recommended now.

vernal herald
#

okay I will be patient and wait, thats what I have been doing and everything installs and runs great, but then it just craps out the zha.

inner torrent
frozen flower
bronze fog
viscid swallow
vapid shell
half marlin
#

is there any chance to see all my thread networks? i think some devices are on another thenother devices

spice imp
twin vine
#

Nanoleaf does show all thread networks on a wifi network, but only shows BR's, and not edge devices

iron parcel
#

I'm trying to use the Silicon Labs Multiprotocol, and had it working fine for awhile, but now I'm getting the following error:

s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[12:11:03] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[12:11:03] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
....
Error: Failed to probe running application type
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service mdns: stopping
s6-rc: info: service banner: stopping
Default: mDNSResponder (Engineering Build) (Aug 23 2023 18:27:14) stopping
iron parcel
#

I've resolved this error with the following:

  1. Disabled thread, matter, and zigbee integrations
  2. Stopped HA,
  3. Unplugged and replugged in the SkyConnect
  4. Updated Virt to new device ID since I'm using VM (I'd appreciate if anyone knows how to make this persistent),
  5. Started HA and let the firmware flash/update, no error
  6. Enabled disabled integrations
  7. Restarted HA

However, matter integration stopped working and I had to stop using the beta version for the addon for it to start working again.

half bluff
#

I cannot update it anymore even on the Skyconnect firmware website since it cannot probe the device

crisp agate
spring bramble
frozen flower
crisp agate
frozen flower
# crisp agate Non-Pro. Just matter, no wifi or Bridge.

Okay, that's also what I am trying at the moment.
Do you have any other Thread devices in use already?
Currently I use SkyConnect with multi-pan firmware. Either that's the problem or some IPv6 config in my router.
I also have a CC2652RB stick here. I will try to use it as Thread Router. I'll keep you posted if I find a solution. Could you pls also tell me/us when you got it working?

iron parcel
latent schooner
#

No

twin vine
#

Yeah, nah, you gonna have to get two dongles for the best experience

half bluff
echo spruce
#

Hi all, is there a place in the OTBR config to set the zigbee channel for the skyconnect dongle using the multi-pan firmware? The documentation suggests that there is a central place to set the channel, under settings => hardware, but I don't have an option there to set any zigbee options (though I do see the zigbee dongle there as a readonly entry.)

vapid shell
echo spruce
vapid shell
#

Ok. It is indeed. Good luck. That will definitely have problems.

echo spruce
#

But is there a place where the OTBR config is stored? I'm looking through the homeassistant ssh console to try to find a file I can edit. Is it in the zigbee.db? Can I use qa sqlite editor to make that change?

upbeat cairn
echo spruce
#

Yes. But there is nothing on the hardware page that lets me change the setting.

upbeat cairn
#

Do you see the SkyConnect in the hardware dropdown?

echo spruce
#

I can change the channel in ZHA by uploading a backup with the changed zigbee channel.

#

But that doesn't change things for the thread router.

upbeat cairn
#

Does the "Configure" button show up for your setup under the SkyConnect?

echo spruce
#

ZHA is set to channel 11 (which tradfri wants)

upbeat cairn
#

IKEA Tradfri devices don't have channel limitations

#

Under the "Configure" button, you can configure multiprotocol and then change the channel from there

#

Changing the channel directly in the backup won't send out a channel change broadcast to your Zigbee devices, so devices on your network may not migrate

echo spruce
#

There is no configure button for the sky connect. The sky connect shows up under hardware in the list of USB devices as a read-only tree.

#

Hue already has devices on channel 11...

#

I'm just trying to get HA to use the same channel as I migrate devices over.

upbeat cairn
#

This is probably a discussion for #zigbee-archived, but why? The two meshes are entirely independent.
As for why the button doesn't show up, it may be a RP5 issue, or a Supervised issue. Let me take a look.

echo spruce
#

Is there a file I can modify to get OTBR to see that it should use channel 11?

upbeat cairn
#

You should be able to change the channel from the Thread integration. Or change the channel directly in the TLV string, add the new TLV, and then make it preferred to push it to routers

echo spruce
#

I'm having some issues with some thread devices being out of range of existing Google Home devices which are thread border routers, so I am hoping that I can use my sky connect on the same channel to give those devices an alternate border router. Do the different border routers have to be on the same channel?

echo spruce
upbeat cairn
valid wharf
#

does anyone know, if I migrate from Multiprotocol mode to Thread-only on a SkyConnect, is there a way to like keep my network and not have to re-add the devices?

inner torrent
valid wharf
#

or like, if there is a way to make Multiprotocol stable, I'd take that too, but it seems like maybe no

sick swan
#

Make sure the network config is in the Thread configuration panel and marked as preferred.

#

From what I remember the new (pure) OTBR should pick it up automtically

inner torrent
#

Depends how your thread network is setup, what other BRs you have (if any), if the end devices work correctly etc

valid wharf
#

ok, that sounds promising, thanks! I'll give it a try this evening

fickle mantle
valid wharf
#

will do!

valid wharf
#

well @fickle mantle and anyone else interested, switching over worked pretty painlessly. here's what i did:

  • delete zigbee home automation integration (is this necessary? idk)
  • uninstall silicon labs multiprotocol add-on
  • install openthread border router add-on
  • go to the config of the otbr add-on, pick the device to use (it was not autodetected)
  • start the add-on
  • wait a bit
  • observe that HA can switch the relevant devices on and off again with no further hassle
    obviously ymmv, and it's a little soon to say if it's more stable or not, but at least it didn't hose my entire network afaict
#

thanks falstaff321 and adequate-spectre for the advice!

hybrid mountain
#

Hello everyone, total newbie here, got into home assistant like last week. I flashed the zbdongle to have a thread border router, but now alexa is asking me for a network key. Where can I find that key? ty

inner torrent
hybrid mountain
inner torrent
#

Connecting to HA? Alexa? Both?

Do you have existing border routers from Amazon?

hybrid mountain
vapid shell
#

If you are using the HAOS version of openthread border router, that’s not something that currently has a ui in ha. If you don’t mean the HAOS thread border router this discord is the wrong place to get help.

inner torrent
#

Still not quite clear on what you're trying to do. Like jc2k said, this isn't the place to ask about adding border routers to Alexa. If you could explain what you're trying to do and what hardware you have in more detail it would help

" I'm trying to add a matter over thread lock to both HA and Alexa. I'm running an OTBR in HA but have no other border routers" for example

tribal knoll
#

Annyone have any success with Openthread Border Router

#

i cant seem to get my matter over thread bulb connected

#

just get seem to get past the Checking network connectivity step

#

it just says Cant connect to thread network glacier-thread

vapid shell
serene prawnBOT
#

@tribal knoll I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
tribal knoll
#

thats a log of the repeated attempts on the OTBR side

tribal knoll
#

ill take a look

inner torrent
tribal knoll
#

ah ok

#

ive taken a cursory glance over all the pinned messages that apply to my situation, and everything seems in order

#

OTBR is on its own pi, everything is configured for IPV6

#

I double checked the pi and enabled ipv6

#

and im using HAOS

#

(speaking of, i wonder how i install HACS to HAOS)

#

thats a differnt problem tho

#

for now i just want to get my bulb connected to my OTBR edge router

inner torrent
#

Do you have any other BRs? Or is it just your OTBR in HA?

tribal knoll
#

my OTBR is on a pi, its all set up on its own

#

its connected to HA but im not using the inbuilt one

#

the OTBR service on HA connects to it by api

#

seems to be no issues, it can control it no problems

#

i would send screenshots, but aparently i cant on here

tribal knoll
#

if that would help

#

but i dont have any br's that are official products

#

just official hardware

#

to make a BR

digital salmon
#

I got the new HA iOS beta app installed. The following is from the release notes.

If you are using Home Assistant 2023.12 beta you will be able to retrieve your Apple Thread network credentials using the "import credentials" on Thread network panel

This is really great news. Well done. But how does HA handle TREL with HAOS 2023.12? Is it enabled by default?

inner torrent
# tribal knoll if that would help

The "official" answer you're gonna get is that the configuration you have is unsupported (I don't think I've even seen anyone come in with trying to use HA to control an external BR via the API)

#

I'm not sure I have any pointers myself

tribal knoll
#

Are you saying I should plug my RCP straight into the machine running haos?

vapid shell
#

If the rcp looks enough like a supported rcp (like the skyconnect) it would be a more supported config, tho still would have some red flags compared to apple/google.

#

The compatibility promises around thread are mostly hype atm

tribal knoll
#

It's the Nordic nRF52840 flashed with thread 1.3

bronze fog
#

Not that it would buy me much, but now with the thread credential sharing on the Apple platform, could the Skyconnect join my Apple thread network but NOT be an OTBR? Just a matter controller than can directly send commands to the thread network instead of through my ATVs? Or would joining the thread network with the Skyconnect imply/require HA to also be a OTBR?

tribal knoll
#

and just before you ask, no im not using thread 1.2, im using thread 1.3 for matter compatability

vapid shell
#

That integration is for the ha builds of OTBR. Sometimes they have incompatible changes.

tribal knoll
#

ah, i dont think thats specified anywhere on the page

vapid shell
#

For example, much of the api that the OTBR integration uses, didn’t actually exist in the main OTBR code base

tribal knoll
#

o.o

vapid shell
#

Because ha implemented it

tribal knoll
#

interesting, wish that was in the description

#

just says The Open Thread Border Router integration allows calling an Open Thread Border Router’s REST API from Python and via WebSocket.

vapid shell
#

You don’t need that integration at all anyway

tribal knoll
#

oh?

vapid shell
#

All it does is automate creating a thread network on your br

#

Which you can do with the ot-ctl command

tribal knoll
#

yeah, thats what i did

#

although i did it from the webui

vapid shell
#

That webui is a menace and you shouldn’t get used to it

tribal knoll
#

good to know

vapid shell
#

It gets crashey as your mesh growns

#

And it’s not really meant for end users

#

I think the upstream devs talked about removing it

tribal knoll
#

makes sense

#

its disabled by default

#

api is now built into the agent instead of the webui

#

ok, removed the OTBR integration, and set my border router as the default thread border router in ha

#

gonna see if that makes any difference

#

if i connect the RCP directly to HAOS, how do i set that up?

#

is there any documentation?

#

(it didnt make a difference jsyk, still couldnt connect to thread network)

vapid shell
#

The automation is there for SkyConnect. I have no idea if other radios work.

spring bramble
tribal knoll
#

not blaming you

#

just saying

vapid shell
#

Well it’d be pretty dumb to as I don’t work on that 😂

#

Like I said a few pages back, thread interoperability is bit of a lie right now

#

It’ll hopefully work out but atm it’s a bit of a nightmare

#

Eg You can’t get Android to use a non google br if you owned a nest and then got rid of it, without partially resetting some google play internals

#

So ha has focussed on the setups in those pinned posts you looked at

tribal knoll
#

that makes sense then i guess

#

just a shame that i have to go out and BUY a border router device, when i have all the tools needed to make one

vapid shell
#

What you are doing is probably nearly working, it’s probably a network issue

tribal knoll
#

the nanoleaf app does sometimes see the thread network and say that it is connecting to it

#

home app also sees the router and tries to commission devices for it

#

it just cant successfully "test thead network connection"

#

also for some reason in the nanoleaf app, it seems to think that it cant detect ipv6, but not only does my phone have an IPV6 address, i have pihole set to default to ipv6

#

and its doing DHCP for the network

#

so IPV6 is DEFINATELY supported and enabled

vapid shell
#

Ok so thread doesn’t use the ipv6 from your host network

#

It can, but by default it’s gonna make its own ULA /64

tribal knoll
#

could that be the issue:?

#

im unfamiliar with this side of the protocol

vapid shell
#

We have certainly seen half configured ipv6 break things

tribal knoll
#

how can i check this?

vapid shell
#

So previously we’ve said turn off ipv6 on your router unless you have working ipv6 internet, sounds like you do tho?

tribal knoll
#

yes, full ipv6 support is enabled on my network

vapid shell
#

You’d have to disable it to rule it out so probably the last thing to try.

#

Do you have vlans

tribal knoll
#

ok

tribal knoll
#

so no vlans

vapid shell
#

Good

#

So after that it’s fancy network stuff that might cause isolation between devices

#

Bad IGMP implementations can be a problem

#

WiFi client isolation can be a problem

#

Mdns features on your network

tribal knoll
#

ok not going to lie i havent touched these before

#

definately not IGMP

#

and i know of MDNS, but never touched it

#

what am i looking for with these?

meager galleon
#

I'm in the same boat as you @tribal knoll I think. It gets to the point where it's checking network connectivity after generating matter credentials but then never connects

tribal knoll
vapid shell
#

Unfortunately can be completely different root causes

meager galleon
#

someone suggested trying to provision with BT on the host machine to rule out other network issues but I haven't gotten around to trying that

vapid shell
#

They cover what is expected to work well and what is expected to somewhat work

vapid shell
#

Even when you use the same vendor I’ve seen some people need it on and some off

tribal knoll
#

interesting

#

right now i dont even know what state its in so i think first step would be to figure that out

#

and where it needs configuring

vapid shell
#

If your router claims it has “enabled” mdns for your network, it’s probably doing something a bit dodgey

tribal knoll
#

interesting, i will look into mdns for my router

#

one sec

#

is there any other network device that could interupt this?

#

would UPnP be an issue for this at all?

vapid shell
#

Probably not

tribal knoll
#

ok, no MDNS settings on my router, or repeater

#

(WIFI isnt used on my repeater though)

#

its basically a glorified lan switch

vapid shell
#

Repeater?

tribal knoll
#

TPLink 5 port bridge router

#

Like i said, glorified switch

#

its connected via lan

#

none of the devices in question are connected to it

vapid shell
#

Ok

#

Repeaters have caused problems before

#

Fixed a few people’s threads by turning them off

#

Those models were not acting enough like switches

#

But if nothing is connected it should be fine

#

Ok - go to your thread integration in ha

#

Onto the “configure” page where it lists networks and border routers

#

In the … menu there is a “download diagnostics” button. Do that.

tribal knoll
#

done

#

would you like a copy?

vapid shell
#

Yep

serene prawnBOT
#

@tribal knoll I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
vapid shell
tribal knoll
#

glacier-thread.local is the hostname of the border router

vapid shell
#

Yes

#

It’s routes are not there

tribal knoll
#

i dont understand

vapid shell
#

You can’t see what’s missing so you’ll just have to believe me

tribal knoll
#

ok

vapid shell
#

So your br uses icmp6 to “announce” routes

#

That’s how ha would know to send thread traffic to that br and not its default gateway

tribal knoll
#

ah

vapid shell
#

You don’t have any ipv6 addresses in your addresses field

#

Or in your neighbours list

#

Double check that ipv6 is turned on on haos

tribal knoll
#

its set to automatic

#

so it is enabled

vapid shell
#

And then on the otbr

tribal knoll
#

IP Information
IPv4
IP Address: 192.168.1.90/24
Gateway: 192.168.1.1
Method: auto
Name Servers: 192.168.1.9
IPv6
IP Address: 2a01:4b00:f01b:1400:844d:8a4f:bcd2:a109/64, fd00::5ba2:76af:9f88:321a/64, fe80::5250:5abe:968:e789/64
Gateway: fe80::4f0:caff:feb2:fe52
Method: auto
Name Servers: fe80::1, 2a01:4b00:f01b:1400:4f0:caff:feb2:fe52

#

open thread border router ip's: 192.168.1.27
FE80::62D3:A2CD:9FF3:6B76
FE80::BA27:EBFF:FE9E:B5F6

#

opent thread border router ip a output:

#

3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:9e:b5:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.27/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 84916sec preferred_lft 74116sec
inet6 fd00::ba27:ebff:fe9e:b5f6/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 2a01:4b00:f01b:1400:ba27:ebff:fe9e:b5f6/64 scope global dynamic mngtmpaddr
valid_lft 47079sec preferred_lft 32679sec
inet6 fe80::ba27:ebff:fe9e:b5f6/64 scope link
valid_lft forever preferred_lft forever

vapid shell
#

So it doesn’t look like it’s putting any of those addresses in the mdns record it’s generating

#

You should be able to verify that with a third party mdns tool

tribal knoll
#

Is there one you would recommend?

vapid shell
#

I use “Discovery” on iOS, that’s all I know

tribal knoll
#

What service type should I look for?

vapid shell
#

_meshcop._udp

tribal knoll
#

It does find it

#

This app displays its ipv4 address however

#

Mind if I DM you the screenshot?

vapid shell
#

Sure

#

Hard to tell if it’s a limitation of that app or whether it has confirmed your br isn’t doing mdns properly

tribal knoll
#

Let me try another

#

It appears ipv6 is not available on the pi, despite having an ipv6 address

#

In the screenshot I sent you it's missing the purple 6 beside it, indicating ipv6 is not available

#

IP I ping it with prefer ipv6 it falls back to ipv4

#

Hold on I'm doublechecking /etc/modules

#

Ipv6 is definitely there and enabled

vapid shell
#

So you wouldn’t see addressses at all if that bit wasn’t working

#

Could you restart OTBR and then check in the mdns tool again?

tribal knoll
#

Yes, one second

#

Still no ipv6

#

I think I found something

vapid shell
#

I don’t think they are right

tribal knoll
#

Disregard, file does not exist for me

vapid shell
#

So some of the missing ha diagnostics data might be because the mdns records are faulty - it needs them to be valid to collect it all. It’s entirely possible that ipv6 is working, but mdns is not.

#

I would try ping6 and give it an ipv6 address directly

tribal knoll
#

Ok, I'll give that a try

#

I get network is unreachable

vapid shell
#

Which address?

tribal knoll
#

fd00::ba27:ebff:fe9e:b5f6

vapid shell
#

Ok. And where are you pinging from?

tribal knoll
#

My phone

#

Same network

#

Same ap

vapid shell
#

Does it have an ipv6 address of its own that starts fd00?

tribal knoll
#

fe80::c30:6cff:fefa:c5d0

vapid shell
#

Is that all?

tribal knoll
#

That's what it says on the phone, one sec, let me check from pihole

vapid shell
#

If so your phone isn’t getting an ipv6 address from your router OR from your border router, so it might have a problem with its ipv6 config

#

Pihole won’t see fd00 device assignments

tribal knoll
#

2A01:4B00:F01B:1400:C028:393:18AA:4F30

vapid shell
#

Is your phone set to do dhcp6 and not slaac?

tribal knoll
vapid shell
#

Well it’s 1.36 am here so not sure what else I can do

#

There is something weird with ipv6 on your network

tribal knoll
vapid shell
#

Given your phone can’t see the ipv6 of your br, I don’t think it’s ha

tribal knoll
#

Ok, I will look into it tomorrow

#

It's the same time here

#

Thanks for your help regardless

#

I've learnt a lot

digital salmon
sterile birch
#

So the way I understand this, I don't need a Thread bridge if I have an Apple device (In my case Apple TV 4k) and HA can just hop in and start accessing any thread devices (once these new versions make it to production/stable) right?

spice imp
sterile birch
#

Okay perfect, I was going to get some Thread Window/door sensors but wanted to make sure I could use them given I have HA running as a VM and the only thread device I have currently is my Apple TV

spice imp
#

Are you running HasOS as a vm?

sterile birch
#

Yes

#

The official VMware OVA

spice imp
#

Good, maybe read the pinned posts in the matter channel first

#

But sounds like this setup should work for you

sterile birch
#

Hmm I don't have IPv6 provisioned at home so that might be a sticking point

spice imp
#

you dont need to

sterile birch
#

unless the ATV runs its own network

#

Gotcha

spice imp
#

your interface can have multiple ipv6 addresses

sterile birch
#

I'm doing some research on all this right now so I'm figuring out a plan for Matter

spice imp
#

so its not like ipv4, where you need your router to assign it

sterile birch
#

Oh its just using the Link Local v6 addresses

spice imp
#

Not for thread

#

But for wifi matter devices yes

#

That should be enough

sterile birch
#

Luckily I don't plan on using wifi matter devices lol

spice imp
#

but thread is another network, so its not a "local" link

sterile birch
#

Wifi devices are absolute shit in my environment. To many talkers

#

(Condo complex downtown)

spice imp
#

so the apple tv will do some route advertisement and "give" out ipv6 addresses

#

And remember thread is 2.4ghz

sterile birch
#

Guess we will see how it works lol

spice imp
#

(it should still be fine though)

#

Yeah, threre is just nothing else to do. The reasons why 2.4ghz has so much noise is because its one of the few frequencies consumer products are allowed to use

#

so bluetooth, wifi, thread, zigbee and whatever share the same frequencies

#

the sub ghz frequencies you are allowed to use change basically from country to country

tribal knoll
#

I cannot seem to get ipv6 working on my pi

sterile birch
#

I've found luck using SDRs for subGhz emitting items like a weather station

#

That's one thing I miss about having a home

spice imp
spice imp
#

seems like you have an ipv6 address

#

or ping6

sterile birch
#

Mine just sit idly by these days, I can't get anything from where I am in my apartment, even with a high gain antenna

tribal knoll
spice imp
#

what about ping6?

tribal knoll
#

ping6 doxent work from the pi

spice imp
spice imp
tribal knoll
#

i have otbr set up on a raspbery pi 3b+ as my networks thread border router.

#

it seems to be able to commission the matter device correctly

#

but after commisioning the device, it fails to verify the connection via the thread network

spice imp
#

is homeassistant on the same device?

#

And how are you commissioning

tribal knoll
tribal knoll
spice imp
tribal knoll
#

set up on the pi

spice imp
#

On a pure debian/ubuntu install?

tribal knoll
#

raspian/debian

spice imp
#

and what you have tried is pinging this pi from your homeassistant installation?

#

and it does not work?

tribal knoll
#

no, home assistant connects to and sees the border router no issue

#

however if i attempt to ping6 ipv6.google.com from the pi, i get no response

spice imp
#

Do you even have an ipv6 connection in your home?

tribal knoll
spice imp
#

Also you dont need external access for this to work

tribal knoll
tribal knoll
spice imp
#

So the problem is most likely that your rpi's network setup is misconfigured?

#

Does your homeAssistant installation get an ipv6 address?

tribal knoll
#

yes

#

it has an ipv6 address

#

and external devices can see it has ipv6 enabled

spice imp
#

Do you have an additional sd card? Maybe its worth it to just make a fresh ubuntu install on the rpi and try to run a border on it

#

instead of figuring out what exactly is misconfigured

tribal knoll
#

im doing that now

tribal knoll
#

Ok. Complete reinstall of otbr, on a plain debian install

#

no successful connection

#

diagnostic output from thread does look different tho

spice imp
#

Are you getting assigned an IPv6 address now?

tribal knoll
#

and this time HA automatically detected the BR

#

here is the log

serene prawnBOT
#

@tribal knoll I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
tribal knoll
#

this time both ipv4 and ipv6 are detected

spice imp
#

So what is failing now?

tribal knoll
#

thats why im here

#

i genuinely dont know

#

in theory all the blocks are there

spice imp
#

But what are you trying to do, and how does it fail?

#

You are like my gf when telling me what she wants 😅

tribal knoll
#

when i try and attach a matter device it goes through all the steps and fails at "Checking network connection"

#

says cant connect to glacier-thread

#

full message is Can't connect to thread network glacier-thread

spice imp
#

I guess you can't see anything in the matter server logs?

#

can you ping the fd00 address of your border router?

tribal knoll
#

hold on let me check that

#

yes i can ping it

#

although i may have found at least part of the issue

spice imp
#

also im pretty sure that your phone should have an ipv6 address now that starts with fd00

tribal knoll
#

it dosent

#

my phone definately dosent have a fd00 address

#

just fe80

sick swan
tribal knoll
#

good to know i might try that next

serene prawnBOT
#

@tribal knoll I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
tribal knoll
#

is the problem matter?

#

"wifi_credentials_set": false, "thread_credentials_set": false

sick swan
tribal knoll
#

Google Pixel 6 Pro

spice imp
tribal knoll
#

so is my onboarding device the issue then?