#thread-archived

1 messages ยท Page 13 of 1

misty lotus
#

I posted this before. After upgrading HA to 2024.1.6 the message below came back. Seems like HA is updating the routing table after the update with the entry.

otbr-agent[180]: 06:35:07.849 [W] Nat64---------: incoming message is an IPv4 datagram but no NAT64 prefix configured, drop

vast sierra
#

The add-on I grew to distrust, since things broke.
I have it installed, but not updating to the current version since I had that and it was still busted for me. (2.4.4)

sick swan
keen mango
#

I am also trying to be a part of the solution, I wanted to get only Matter over Thread devices, but it's not feasible. Devices are either not available or way more expensive than their Zigbee alternatives.

Some examples:

  1. Temperature and air quality sensors. The only Matter over Thread option I found is TUO but it's expensive. Outfitting every room with Zigbee sensors is significantly cheaper.

  2. Various other sensors like water leak detectors, vibration sensors, mmWave presence sensors, smoke detectors etc.
    I am hoping Aqara will release more products like their P2 Door and Window sensor. Their Thread motion sensor keeps getting delayed.

  3. Light switches and smart buttons. Inovelli White series looks good, I'm not sure if it launched yet? I personally need wireless buttons though. I am waiting for Nanoleaf Sense+ to pair with my bulbs and will have both wired and wireless models, but it keeps getting delayed. For now I just picked up a bunch of cheap Zigbee wireless buttons.

  4. SwitchBot products, they are unique but work with Bluetooth, not Thread. Their new hubs support Matter but I hope they also release updated models with Thread. For now I got Zigbee Fingerbots instead.

These are just some examples of devices I care about. Going Thread-only would be very limiting and more expensive.

#

Just found out TUO also has a Matter over Thread smart button.

https://findtuo.com/pages/smart-button

Looks good but only one button, and again significantly more expensive than Zigbee equivalents. Nevertheless, it might be a good option for platforms that don't support Zigbee.

twin vine
#

its very buggy, so do be careful if you get it

#

as stated before, TUO is a 2-3 man show

vast sierra
#

What I dont want in 5 years is Zwave, zigbee, matter/thread, and some revival of X10 or something.

So, since I'm just a year in and all the zigbee stuff came with the house (bunch of Ring gear).... I have Zwave, Zigbee, and Thread for now. Hence why multiprotocol was so attractive.

#

I wont be adding to the zwave or zigbee devices, and will actively remove the one zigbee switch i do us as soon as the Inovelli White starts to ship in a few weeks

#

I never got the LED strip worked out in Home Assistant to miss the animated stuff on the White series for now anyway

spice imp
keen mango
#

Yes that's the other limitation. There are some really strange Zigbee devices with unique properties that are unlikely to be added to the Matter standard.

inner torrent
#

Where's the aqara motion P2? ๐Ÿฅฒ Eve sensors are ridiculously priced

keen mango
inner torrent
keen mango
#

At least Aqara P2 Door and Window sensor (Matter over Thread) works well. It's slightly more expensive than Zigbee contact sensors, but not too bad in my opinion (way cheaper than the Eve Door & Window).

Maybe once Aqara finally releases their M3 Thread hub they will finally release more sensors.

#

Even in CES there was a disappointing amount of Thread announcements.

inner torrent
#

That was my suspicion

#

That they delayed their matter over thread for their new hub

misty lotus
steady forge
inner torrent
#

No logo for my cursed nanoleaf BR ๐Ÿฅฒ

verbal gale
#

I'm experiencing a descent into madness with my fleet of HomeKit over Thread Nanoleaf Essentials of late. They are now spending 5 minutes working when HASS is first restarted, and then dropping off the face of the planet shortly after. A reset of HASS always brings them back. Is there a way to restart the HomeKit integration without restarting all of HASS so that I can give a sanity fix for my wife when lights just stop working?

vapid shell
#

Hey if you could get me some debug logs of what itโ€™s doing I can probably just fix the retrying

#

My light strip is stable for weeks at a time so itโ€™s difficult to debug at my end

#

But there is a reload option on the integration itself

verbal gale
verbal gale
vapid shell
#

Itโ€™s per pairing

#

Which for thread is mostly per device

#

If you have a bunch of devices that stop working at the same time that would be very interesting - would mean all of them were getting into a stuck state because of an external event (as no shared state between devices internally)

vapid shell
verbal gale
spice imp
twin vine
#

Different people maintain different things dude

verbal gale
#

Nanoleaf Essentials Disconnecting

spice imp
#

For the frontend

elder dune
steady forge
sick swan
keen mango
#

My Thread network is finally stable, now I just need those Nanoleaf logos ๐Ÿ˜‚

sick swan
spice imp
inner torrent
inner torrent
#

it kinda looks like it's a case sensitive compare, so maybe just doing vendor_name = try_decode(service_properties.get(b"vn")).lower()

Didn't have too much time to look closely though

sick swan
#

@inner torrent yeah it is case sensitive. But the strings match exactly, with correct casing. What version of HA Core are you running?

steady forge
#

Oh yeah I should've specified that I'm running an RC image of HA-Core

inner torrent
#

Ah okay that could be

#

Im on 2024.1.6

small heart
still quiver
#

trying to add a previously commiosioned NL Essentials lights strip to HA, but fails all the time. Here are the addon logs when I try to add to HA from the NL app (node 88).
http://pastie.org/p/1CdU0lxST219AKw12LwujI

#

adding it directly to HA from the QR code, leads to failure saying im not on the same network,,,which i am

#

how do you add thread devices these days?

inner torrent
#

When you went through the UI flow (connecting to device, generating matter credentials, etc) where did it get stuck? Looks like the device isn't broadcasting and HA can't find it

#

Also, did you make sure to reset the bulb?

#

Or strip rather

night moth
#

Anyone got some ideas on where i should start looking. I just changed from multipan back to Open thread only for my skyconnect, since doing that the open thread border router is crashing in like 30mins or so.
I have restarted the whole system too.

So annoying, removing multipan as its meant to be more stable and now i have gone from it being stable to crashing frequently ๐Ÿ˜ฆ

sick swan
#

I have two OTBR add-on running, one with SkyConnect and one on Yellow, no crashes so far ๐Ÿค”

night moth
#

Start of crash says FATAL ERROR: Caught signal: 6 (Aborted)

#

I have just uninstalled OTBR and rebooting and installing again to see if it helps

night moth
# sick swan Anything specific in the OpenThread add-on logs?

Crash gives this in the log

otbr-agent[187]: 00:00:54.261 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:96, src:0x3c00, dst:0xe400, tag:29429, offset:304, dglen:1083, sec:yes
otbr-agent: ../../src/mdns/mdns_mdnssd.cpp:951: virtual void otbr::Mdns::PublisherMDnsSd::UnsubscribeService(const string&, const string&): Assertion `it != mSubscribedServices.end()' failed.
otbr-agent[187]: 00:00:54.359 [C] Platform------: ------------------ BEGINNING OF CRASH -------------
otbr-agent[187]: 00:00:54.359 [C] Platform------: *** FATAL ERROR: Caught signal: 6 (Aborted)
otbr-agent[187]: 00:00:54.370 [C] Platform------: # 0: /usr/sbin/otbr-agent(+0x21d228) [0xaaaaadb8d228]
otbr-agent[187]: 00:00:54.370 [C] Platform------: # 1: /usr/sbin/otbr-agent(+0x21d36c) [0xaaaaadb8d36c]

sick swan
#

Hm, I remember there were some bugfixes around mdns subscription/unsubscription ๐Ÿค”
And you are using the latest version of the OTBR add-on?

night moth
#

Yea 2.4.5, latest one.
And it seems my zigbee has also stopped working, devices show connected but none of them update or respond ๐Ÿ˜ฆ
Zigbee is running off a sonoff stick now

I should have just stuck with multipan haha

spice imp
#

Why does the skyconnect cost 40 euros? Is the money going to HomeAssistant or just some resellers?

twin vine
#

i mean, the resellers on their websites would no doubt take a flat commission rate or %, but no doubt HA would have some margins in there

#

but thats just how every company works

spice imp
twin vine
#

i mean, its up to you at the end of the day, but most people wouldnt know whats under the hood of a skyconnect

spice imp
twin vine
#

i can confidently say that a % would go to the offical resellers, and a % would go to nabu casa

spice imp
twin vine
#

eh, nabu casa would work with nordic directly to some capacity, so doubt youll ever know. same as the yellow, blue or green

night moth
twin vine
#

back on multipan?

night moth
#

No, not really sure what i did, but maybe its not crashing cause zigbee isnt working lol :S

night moth
#

seems things have started working again. fingers crossed it holds haha

sick swan
#

So I've played a bit with the OpenWrt openthread package and it works ๐ŸŽ‰ ๐Ÿ˜…

#

There is not much UI support yet, but it has the REST API enabled, so setting up the BR from HA is a breeze

twin vine
#

it only took ya about an hour or so after some misconfigurations ๐Ÿคฃ

sick swan
#

Wait, you saw that? ๐Ÿ˜…

#

Yeah I discovered their readme much too late. And then is just super annoying to onboard Matter devices on a random Thread network currently, due to those Android restrictions ๐Ÿ˜ข

twin vine
#

i mean the end user could prolly use config/matter/dashboard instead of web-sockets to make it a ton easier in terms of guiding them, but yeah ble can be a pain especially when there is no "right" way to do it all

sick swan
#

I was actually searching for that at one point, but somehow I didn't found it/I assumed it is gone with the latest beta

#

good to see it is still there ๐Ÿ˜…

#

I mean, if I had that BR on my main net, I woudl have just added it into my existing Thread network, removed all the other BRs and proven that it works ๐Ÿ˜„

#

But I was using my test VLAN, where I don't have a commissioner

#

I probably should get an Android phone specifically for my test VLAN. Then I can also just blow away the Play Services data whenever I feel ๐Ÿ˜…

twin vine
#

haha yeah, i remember you saying something about that. that absolute legend was 6 months ahead of his time

#

what you did was a very cool proof of concept, thats for sure

#

just obviously needs some loose ends tied up, mostly on the openwrt side ๐Ÿ˜…

night moth
vapid shell
#

If anyone has HomeKit over thread devices and they are running the beta this month, let me know how you get on with b4 or laterโ€ฆ

#

(Itโ€™s building right now)

serene prawnBOT
viscid anvil
#

Can only assume it is to do with 'Failed to bind UDP socket: Address already in use' but unsure how to resolve it, any help would be much appreciated!

twin vine
#

so you set the OBTR add-on to use the usb in the config area?

#

and you dont have any zigbee add-on using the stick?

viscid anvil
#

I did have an zigbee addon initally but removed it, do I need it?

Yes the USB is configured in the config area

#

/dev/serial/by-id/usb-Nabu_Casa..

twin vine
#

you followed this?

viscid anvil
#

I did not come across that! Will go through it now and report back, thanks!

#

it asks for a port, do I manually need to enter the really long one from OTBR config?

twin vine
#

asks in the add-on config?

viscid anvil
#

when install Zigbee Home Automation it asks to select a serial port, which finds SkyConnect, then radio type which I choose EZSP I assume

twin vine
#

wait, are you using multipan?

#

or just thread?

viscid anvil
#

just thread

twin vine
#

huh? you got an image. you shouldnt have to specify radio type if you follow the guide above

viscid anvil
#

ah so now I see this:

'Your device is running the wrong firmware and cannot be used with ZHA until the correct firmware is installed. '

#

Your Zigbee radio was previously used with multiprotocol (Zigbee and Thread) and still has multiprotocol firmware installed: (SPINEL). To run your radio exclusively with ZHA, you need to install Zigbee firmware. Follow your Zigbee radio manufacturer's instructions for how to do this

twin vine
#

in the settings of the otbr, is the auto flash firmware on?

viscid anvil
#

It is

twin vine
#

maybe give that a go, yeah

#

or this if you want

viscid anvil
#

struggling to get the firmware to install on dietpi ๐Ÿ˜ฆ I'll give it another go earlier, 5 hours into it lol

twin vine
#

wait your running HAOS yeah?

sick swan
#

If so, it would be good if you can capture more of the logs. I wonder if there are some logs entry before that whiciih give a hint what is going on exactly.

sick swan
#

It is on our todo to improve this expierence, ZHA currently thinks it owns SkyConnect ๐Ÿ˜…

night moth
viscid anvil
sick swan
viscid anvil
# viscid anvil DietPi so assume HA Supervised?

To add the Zigbee addons states this:

Your Zigbee radio was previously used with multiprotocol (Zigbee and Thread) and still has multiprotocol firmware installed: (SPINEL). To run your radio exclusively with ZHA, you need to install Zigbee firmware. Follow your Zigbee radio manufacturer's instructions for how to do this.

Do I need to use the Zigbee firmware if I just want to use it as a Thread router?

sick swan
#

The OpenThread Border Router add-on will flash the right firmware on its own. You don't need to flash the firmware manually.

#

@viscid anvil that is still your goal right? That is what you wrote initially:

I want to use it as an OpenThread Border Router,

viscid anvil
#

Correct, I actually removed all addons, rebooted and installed just the OTBR addon, firmware was skipped as it already had the right firmware. I can now see it as a router in the Thread addon under devices! So getting closer!

Now just trying to add a Matter device and it says no Thread Bourder Router is on the network, anything else I should do?

sick swan
#

What OS is your phone using?

viscid anvil
#

iOS

#

I do have an Android device I could use if thats better

sick swan
#

Yeah we don't have Thread credential synchronization in the iOS App yet ๐Ÿ˜ข

#

In Android, use the companion app, and make sure the Thread credential is synced to your Android device under Settings > Companion App > Troubleshooting > Sync Thread credentails.

viscid anvil
#

Amazing, doing that now

#

Says added, let me give it a go ๐Ÿ™‚

#

Currently hanging on 'Checking network connectivity' whilst adding, further than last time but has been on that screen for a while. Fingers crossed!

sick swan
#

Do you have the phone and the HA server running the OTBR add-on on the same network (e.g. no separated VLANs)?

viscid anvil
#

Yea same network

#

Trying to connect a Nuki device in case that changes anything

still quiver
#

I just realized my samsung tv can act as a matter hub, any know if it has thread border router capabilities?

sick swan
twin vine
viscid anvil
sick swan
#

@viscid anvil can you check the Thread integration configuration page, is the Home Assistant Border router in the right Thread network, and is the Thread network the preferred one?

still quiver
twin vine
still quiver
#

Yeah I just enabled it and can it can commission devices.

twin vine
#

thats kinda dope

viscid anvil
#

Also it says Dietpi.local, could this mean that its not being seen outside of that?

sick swan
#

This is just the hostname of that particular border router.

sick swan
#

Did commissioning work? Otherwise run the Thread credentials sync again, just to be sure. It should say that the phone and HA Core use the same preferred network.

viscid anvil
#

When adding the device it went through steps of connecting to device, then very quickly something about credentials then hangs on connecting to network and eventually says cant reach device, but it seems to see the border rotuer as it isn't saying that there isn't one installed anymore.
What do you mean about commissioning sorry?
I'll try another sync.

#

the sync says Home Assistant and this device use the same network

#

Thats on the Android device

#

Ok this time it just says Can't connect to the thread network home-assistant

#

Not sure if this means anything under the Matter addon logs:

Logger: homeassistant.components.matter
Source: components/hassio/addon_manager.py:380
Integration: Matter (BETA) (documentation, issues)
First occurred: 17:48:46 (1 occurrences)
Last logged: 17:48:46

Failed to set the Matter Server add-on options: not a valid value for dictionary value @ data['options']. Got {}

sick swan
#

It sounds to me like a RF/link quality issue.

viscid anvil
#

Just found a thread about enabling 'NAT64' so just trying that

sick swan
sick swan
#

But I also don't think that this will solve your problem ๐Ÿ˜ข What is the distance between the lock and the SkyConnect?

viscid anvil
#

Yea you're right not sure its related at this point, the distance is maybe 3 meters on the same floor (under the stairs and device is on the front door)

Will try removing the device from the door and stick in right next to it

#

same issue when right next to the skyconnect device

sick swan
#

Same as which one of the two errors? ๐Ÿ˜…

viscid anvil
#

sorry Can't connect to the thread network home-assistant

sick swan
#

Hm, that is strange. The phone talks to the device via Bluetooth, and instructs it to jump on that network. It seems the device reports back that it can't ๐Ÿค” Maybe restart the OTBR add-on?

viscid anvil
#

I'll reboot HA altogether perhaps

sick swan
#

Shouldn't be necessary, but can't hurt ๐Ÿ˜…

viscid anvil
#

Whilst its doing that, is it possible to be a network issue? I got the service as I have a Google Hub v2 but couldn't be seen as a border rotuer what ever I tried

#

However the issue with SkyConnect seems to suggest that the network sees a router but can't connect

serene prawnBOT
twin vine
#

Wow, its nice to see vendors make HA specific help guides for people!

sick swan
#

Now that you say it: You are using Supervised right? ๐Ÿค”

viscid anvil
viscid anvil
#

dietpi / rock64

sick swan
#

However, acting as BR I don't think there shouuld be anythign missing by default ๐Ÿค”

#

Unless.. Maybe net.ipv6.conf.all.forwarding is not enabled on Supervised? ๐Ÿค”

viscid anvil
#

Will take a look now, by the way I think these may have come up when adding the device:

otbr-agent[183]: 00:04:41.960 [W] Nat64---------: no mapping found for the IPv4 address

still quiver
#

Anybody where I can find my 32 characters network id?

sick swan
#

However I then would expect the error you first posted ("eventually says cant reach device")...

sick swan
sick swan
viscid anvil
sick swan
#

sysctl net.ipv6.conf.all.forwarding

viscid anvil
#

ah ok tried that and doesn't recognise the sysctl command

#

should I install it

sick swan
#

Yeah I guess. Make sure to run on the OS shell (not in the HA Web Terminal, as this is not on the OS itself).

still quiver
#

This would be smart things I presume

twin vine
#

you can use imgur for a photo

#

oh wait, its maybe asking for network key?

still quiver
#

Oh sorry yes it's network key

#

Not ID my bad

twin vine
#

hmm, i dont think HA shows network key

viscid anvil
#

that command doesn't work, and dependencies seem to be installed (dietpi runs on Debian).

However in etc/sysctl.conf the following is commented out:
#net.ipv6.conf.all.forwarding=1

Should I uncomment?

twin vine
#

i can see it in the nanoleaf app, but not natively in HA

#

wait

#

the network key is in the tlv

sick swan
#

Is that a vanilla Debian or a derivate?

viscid anvil
#

Just that the sysctl command is not found

viscid anvil
sick swan
#

I doubt that uncommenting then works tbh. But I don't know DietPi well enough.

twin vine
#

@still quiver my network key in tlv is from characters 70 - 102, not sure if every tlv has a set lengths for everything tho?

sick swan
viscid anvil
sick swan
viscid anvil
# 
otbr-agent[183]: 00:05:30.289 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[183]: 00:05:30.425 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure```
sick swan
#

Hm, that sounds like your network is quite jammed

#

Do you use the USB extension cable?

#

Make sure to be as far away from USB 3.0 deviices as possible. They mess with IEEE 802.15.4 devices (Thread/Zigbee)

viscid anvil
#

So next to the device I have a mini home lab set up with a couple of HDD bays, but I have it as far as the extender goes and lower down if that makes sense

twin vine
#

The only issue is that DHCPv6 doesnโ€™t work yet

viscid anvil
#

Ok cool, yea latest version

still quiver
#

thanks! if I didn;t have the NL app, I would have used this git script but much more simpler (for me) just to use tha app. Cheers

viscid anvil
#

Does my ISP need to support IPv6?

twin vine
#

have you got v6 within your network working fine?

#

like your devices get a local link address?

viscid anvil
#

Yes ipconfig on a windows device seems to show an IPv6 address for my LAN

#

and I can ping that ipv6 address

#

ip a in dietpi seems to return ipv6 addresses

#

4: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:24:41:a1:e1 brd ff:ff:ff:ff:ff:ff inet 172.30.32.1/23 brd 172.30.33.255 scope global hassio valid_lft forever preferred_lft forever inet6 fe80::42:24ff:fe41:xxxx/64 scope link

sick swan
#

You want to look out for your main network interface (eno0 or so).

#

So even after sysctl.d change did not work?

viscid anvil
#

Yup, I tried to disable ipv6 and re-enable and the logs on OpenThread show this
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface

sick swan
#

Yeah that is normal. The OTBR tries to use the Docker veth devices.

#

I recommend trying out HAOS. You can just flash it on a SD card. If it works on there, then it is DietPi or some configuration of it...

night moth
# sick swan OTBR crashing? Same error as you posted previously? ``` otbr-agent: ../../src/md...

Sadly and frustratingly still crashing ๐Ÿ˜ฆ Im at a loss at what to even try.
Pulled what looked relevant from the log (and can fit into discord)

otbr-agent[183]: 04:28:21.527 [I] DnssdServer---: Send response, rcode:0
otbr-agent: ../../src/sdp_proxy/discovery_proxy.cpp:200: void otbr::Dnssd::DiscoveryProxy::OnServiceDiscovered(const string&, const otbr::Mdns::Publisher::DiscoveredInstanceInfo&): Assertion `splitError == OTBR_ERROR_NONE' failed.
otbr-agent[183]: 04:28:21.527 [C] Platform------: ------------------ BEGINNING OF CRASH -------------
otbr-agent[183]: 04:28:21.528 [C] Platform------: *** FATAL ERROR: Caught signal: 6 (Aborted)
otbr-agent[183]: 04:28:21.536 [C] Platform------: # 0: /usr/sbin/otbr-agent(+0x21d228) [0xaaaad3b8d228]
otbr-agent[183]: 04:28:21.536 [C] Platform------: # 1: /usr/sbin/otbr-agent(+0x21d36c) [0xaaaad3b8d36c]
otbr-agent[183]: 04:28:21.536 [C] Platform------: # 2: linux-vdso.so.1 __kernel_rt_sigreturn+0x0 [0xa60d47bc]
------: # 7: /usr/sbin/otbr-agent otbr::Dnssd::DiscoveryProxy::OnServiceDiscovered(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, otbr::Mdns::Publisher::DiscoveredInstanceInfo const&)+0x254 [0xd3ca2b48]
12: /usr/sbin/otbr-agent std::function<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, otbr::Mdns::Publisher::DiscoveredInstanceInfo const&)>::operator()(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, otbr::Mdns::Publisher::DiscoveredInstanceInfo const&) const+0x64 [0xd3b4fb48]
#13: /usr/sbin/otbr-agent otbr::Mdns::Publisher::OnServiceResolved(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, otbr::Mdns::Publisher::DiscoveredInstanceInfo)+0x34c [0xd3b4a974]

viscid anvil
twin vine
#

i mean, could you do proxmox and then haos through that?

viscid anvil
#

might just get a cheap nuc

#

btw I managed to get sysctl to work by running export PATH=$PATH:/usr/sbin:/sbin

#

echo $PATH didn't have sbin

#

sudo sysctl -a | grep 'accept_ra ' shows:
net.ipv6.conf.all.accept_ra = 1 net.ipv6.conf.default.accept_ra = 1 net.ipv6.conf.docker0.accept_ra = 0 net.ipv6.conf.eth0.accept_ra = 0 net.ipv6.conf.hassio.accept_ra = 0 net.ipv6.conf.lo.accept_ra = 1 net.ipv6.conf.veth0658cd9.accept_ra = 1 net.ipv6.conf.veth283d37c.accept_ra = 1 net.ipv6.conf.veth3d3a16a.accept_ra = 1 net.ipv6.conf.veth4d8e041.accept_ra = 1 net.ipv6.conf.veth6823d97.accept_ra = 1 net.ipv6.conf.veth7e40360.accept_ra = 1 net.ipv6.conf.wpan0.accept_ra = 1

twin vine
#

is eth0 your main interface?

viscid anvil
#

yea

#

Ive now added net.ipv6.conf.all.forwarding via sysctl... lets see

#

seems to have got rid of the ipv4 mapping error and can just see these now
otbr-agent[183]: 00:02:52.390 [N] MeshForwarder-: src:[fd5a:9750:d93c:285c:247b:af72:77e9:9956]:40135 otbr-agent[183]: 00:02:52.391 [N] MeshForwarder-: dst:[fd1a:ecf3:49b1:1:cf74:7505:efda:759a]:5540 otbr-agent[183]: 00:02:57.779 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:214, chksum:7dc4, ecn:no, sec:yes, error:Drop, prio:low, radio:all

vapid shell
sick swan
#

Trying to mount my MotionBlind with tesa Powerstrips, not sure if that is a good idea ๐Ÿ˜…

viscid anvil
#

oh my days... after all of that, the last hurdle was actually enabling ipv6 in settings of HA.... ffs lol

twin vine
#

opps

#

well

#

it happens to the best of us at times ๐Ÿคฃ

viscid anvil
#

literally spent ALL day on it lol, but oh well its done now lmao. Just need to figure out how to keep sysctl net.ipv6.conf.all.forwarding=1
on a reboot but that shouldn't be too hard to figure out, one for another day. Thanks all haha

sick swan
#

Ok so forwarding and IPv6 was it then in the end?

viscid anvil
#

yup

sick swan
#

Hm make sense. Should have known, sorry about that!

#

We should have a checklist ๐Ÿ˜…

viscid anvil
#

I noticed that I had those ipv4 errors again when I restarted dietpi, and the config had disappeared. Popped it back on and applied, and they disappeared from logs. Was searching one of the error and came across a thread about enabling it - although the errors about 'InvalidArgs' seem to be a red herring

viscid anvil
#

this Matter/Thread stuff is soooo confusing to troubleshoot lol

spice imp
sick swan
#

Yeah especially with Thread, it's a two level thing

spice imp
#

Once everything matures a bit you hopefully donโ€™t have to troubleshoot a lot of these parts anymore

#

The first Wi-Fi devices probably also had a lot of problems, today in 99% of the cases it just works or you have to increase your signal strength

viscid anvil
#

I guess there are so many different factors as well, which make it hard to troubleshoot. For example I have an asus router with merlin wrt, running HA on a probably pretty rare dietpi / rock64 setup

strong tusk
#

If my only thread border router is a Sonoff dongle (flashed with thread firmware), thereโ€™s no way for me to commission devices with an iPhone right? Trying to add some Nanoleaf Essentials

keen mango
wheat temple
#

Hello,
I am using Sonevoe Eve Motion Blinds and integrated them to Home Assistant trough HomeKit. It works for some time but then it just stops working for no reason. When I manually open or close it it shows the status. But I can not control it. As soon as the manual movement stops it goes missing again. I am not sure why. Can it be some kind of battery saving stuff?

vapid shell
wheat temple
#

Okay are there any changes especially on eve decices? Since other thread work as they should :)

vapid shell
#

Homekit encryption uses a counter to create a new encryption key for every message. If you have enough packet loss or you have devices on the mesh that have crashed that counter still goes up even if packets arenโ€™t delivered.

#

Some devices ignore messages they canโ€™t decrypt

#

But we never reset the counter in this case

#

So control of a remote device would become impossible

#

If restarting HA fixes it for a while you are probably hitting this problem

#

If you find itโ€™s better after trying the feb release then what it means is your mesh is weak near the blinds

#

Youโ€™ll probably want to add more thread devices or border routers if thatโ€™s the case

#

Note that homekit has seperate encryption keys for receiving data

#

So itโ€™s entirely possible that receiving status updates from the device could still work

#

We try hard to recover from dropped packets on the receive path - even guessing the counter if we have to - which is how the RX path can be more stable than the TX path

wheat temple
vapid shell
#

Any mains powered device can be a router. The leader decides which of those router capable devices are a router tho.

#

One of the problems is when some devices become routers that arenโ€™t very good ones (like nanoleaf - I wish I could force them never to be one)

wheat temple
#

Okay, I restarted HAS and it aktually works again!
So a workaround would be to make an automation that restarts HAS at night

#

Until the update

twin vine
#

i mean, or you could just use the beta

static spear
#

using the google home sample app for matter now shows me the TLV for my Amazon thread network for some reason - was able to add the set into home assistant and add my skyconnect as a BR. I've yet to try and add/control a device to see if it actually works so ill have a look later

#

i can't see any updates for the echo device that's already a BR so i have no idea how they popped up

autumn merlin
#

Hi All, every now and again my eve energy light strip (which is connectted via thread to Skyconnect in multi protocol mode) becomes unavaialble. Here is the log. Was just wanting to know do i need to report a bug for this to start working on how to fix it? https://hastebin.com/share/kubipaciza.vbnet

vapid shell
#

Timeout errors like the one you posted are more than likely environment issues. Unfortunately with thread that covers a lot of ground.

#

How far away is the light strip from the SkyConnect?

#

Do you have any other thread devices on that network?

#

Have you tried the thread only firmware for the SkyConnect instead of multiprotocol?

autumn merlin
#

Thanks for the reply @vapid shell - in answers, about 2 meters from the SkyConnect (if that) however the SkyConnect is under the wooden floor (central to the house) to the lightstrip controller. I have another one about a further meter or 2 away from that, which seems to work better. Only 2 devices on the HA thread network - I also have a ATV4K on the same ip network.

#

I really need the SkyConnect Zigbee side of things as well as I have approx 60 Zigbee devices.

#

So have not tried just thread. Maybe I need to get another SkyConnect or other Zigbee stick?

spice imp
vapid shell
#

You could use the Apple TV for thread

#

And keep the SkyConnect for zigbee

#

My SkyConnect has about 60 devices and I have a couple of thread devices attached to my Apple HomePods

autumn merlin
#

Hmm.. so change the Nanoleaf light strips over to HomeKit right

vapid shell
#

Ah you have nanoleaf

#

So read the docs for homekit_controller (now just Homekit device) and it will tell you 2 ways to use Apple border routers

autumn merlin
#

And this is the current HomeKit Device setup

vapid shell
#

The iOS HA app can import the creds from your Apple border router, then you can make it the preferred one. In theory at least.

#

Then re-add the devices to HA like you did originally (youโ€™ll need to reset them to change networks)

#

If you have nanoleaf itโ€™s still going to be crashy

autumn merlin
#

OK, yea im guessing this is Nanoleaf right? Crashy. I actually replaced the entire kitchen bench light strip with hue, but hue has a slight green tinge when making a white (I guess its RGB) where as the Nanoleaf lightstrip is a nice white, The WAF was not good with the hue lights on the bench top ๐Ÿ˜„

#

Thanks for the tips. Would seperate Thread and Zigbee controllers make any difference or is it Nanoleaf in the end that is the problem here.

vapid shell
#

I think nanoleaf is likely the root cause but if you add lots of thread devices youโ€™ll probably start to hit the problems with multipan and wish youโ€™d sorted it out sooner ๐Ÿ˜‚

#

Some people have nanoleaf crashes once a day

#

Mine lasts a few weeks between crashes

#

2024.2 should recover Ha from the crashes better

autumn merlin
#

Mine is like 1 a week or so.

#

Just enough to be annoying

#

Not planning on adding any more thread devices ATM.

twin vine
#

whatever you do, do not update to the matter version if you can

crude willow
#

@vapid shell are they causing issue's to thread network ?

#

Because if that's the case i'm not going to add them to my network.

vapid shell
#

With small numbers of devices itโ€™s kind of ok

#

I have 2 light strips - a homekit one and a matter one - and they are ok

#

The HomeKit one breaks about once every couple of weeks but a restart fixes it

#

Some people (especially but not limited to those with lots of nanoleaf devices) see frequent crashes

#

And as they are routers not only does it disrupt the mesh, i suspect it cascades

keen mango
#

I previously had extremely frequent Thread network crashes, however since updating SkyConnect to Multiprotocol firmware v2.4.4, it has been significantly more stable.

crude willow
#

Thanks @vapid shell Will see how it goes. Will first try some things with Eve plugs to get lighting fixed.

#

Don't want to risk it

keen mango
half bluff
#

@sick swan When trying to add my thread credentials I keep running into an error code 74? Any idea what might be going on?

sick swan
#

Yeah I remember you mentioning that, i have to look into it

#

Did you open an issue or something somewhere? I remember I've read that somewhere ๐Ÿ˜…

half bluff
#

I dmโ€™d you ๐Ÿ˜…

keen mango
#

Now my Thread network is back online but my actual internet is down (regional outage). Pretty cool that all locally-controlled devices still work, including all Thread devices. Even the Nest Hub TBR still meshes, despite being offline.

sick swan
#

But we should be able to add it so it will be possible to import such datasets.

autumn merlin
# vapid shell So read the docs for homekit_controller (now just Homekit device) and it will te...

Hey again, so i just wanted to confirm my understanding. Currently 2 nanoleaf lightstrips connected to Skyconnect/HA thread network (I orginally reset them, then in HA connected them directly, this would have been done by BT onboarding via HA). So to change them to the Apple thread network: Disconnect them from HA, reset device, connect them to Apple HomeKit, then remove from Homekit without resetting - they should show up in HA again. This time when you add, they will be on the Apple thread network.

vapid shell
#

If you do make preferred network first

#

Then reset them

#

Then onboard them through Ha again

#

It should work

#

The thing where you add them to HomeKit, then remove them, then add them to ha should work too

#

Itโ€™s a fallback for when Ha doesnโ€™t know the apple thread secret key

autumn merlin
autumn merlin
#

OK @vapid shell some feedback for you on this process. To confirm: Remove from HA, reset device, make apple thread network preferred network in HA, pair device to apple home via iphone home app, check nanoleaf app to make sure on thread network, remove from apple home, click configure in HA, enter pairing code:
Then i get this message: "This accessory is already paired to another device. Please reset the accessory and try again."

quiet stirrup
#

Is there a way to use skyconnect with just Thread/Matter?

twin vine
quiet stirrup
#

device is still Multiprotocol?

twin vine
#

uhh, what

#

what add-ons have you got installed?

#

shouldnt be if you ONLY have the OTBR add on installed and running

quiet stirrup
#

got it

#

"This guide installs a firmware which supports only Thread! If you use your SkyConnect to control Zigbee devices, you will no longer be able to control them after installing the Thread firmware."

  • I need to read more lol
twin vine
#

hahah all good, happens to the best of us ๐Ÿ˜†

autumn merlin
quiet stirrup
#

I am about to try to do the same thing lol

autumn merlin
quiet stirrup
#

did you add the nanoleaf lights through the home app and not the nano leafapp itself?

autumn merlin
#

Correct

#

only used the nanoleaf app to verify they were running on thread not bt once connected.

livid obsidian
#

Hi,
does someone uses his rpi5 as a border router for Thread?

twin vine
#

you would need an external radio like the skyconnect iirc

vapid shell
night moth
#

Is there a guide anywhere to troubleshoot OTBR crashes?
Mine has just started crashing like every couple mins after being happy for a period of time.

spice imp
#

Or posting them here

#

What are you using for the OTBR?

night moth
#

Skyconnect thread only. It seems to have stabilised again. was weird went from stable to crashing every couple mins, unplugged and plugged back in and did full system restart and seems to have settled down again :S

twin vine
#

Newest OTBR add on version?

night moth
#

yep 2.4.5

undone kelp
#

Just a note, thread support in HA is really impressive now. I just factory reset some eve light switches, configured them in HA over BLE with homekit controller, then provisionned them onto thread from HA, and it all worked.

vapid shell
#

Should fix one of the more annoying bugs where devices get stuck offline if the mesh destabilised for too long

#

and in 2024.3 the airversa air purifier should finally work without local patching ๐Ÿ˜‚

undone kelp
#

I should mention I also fully unified my thread network with nanoleaf, Apple, and Google BRs all together and so far it's been working.

vapid shell
#

blimey

undone kelp
#

I know, it's crazy. The future is here :p

twin vine
inner torrent
#

I dunno if there is even an option for this in the OTBR but it would be nice if log timestamps were absolute, not relative to the startupt

#

Similar to the matter logs that have m/d/yr and h/m/s

steady forge
keen mango
vapid shell
#

Let me know how you get on - not had much beta feedback!

keen mango
#

I'll need to test it long-term. As in seeing if my Thread network feels more stable after the update

hidden ledge
keen mango
keen mango
twin vine
#

prolly not

#

not for him atleast

keen mango
#

Why not?

twin vine
#

i mean, it depends if nanoleaf displays as his vendor

keen mango
#

It works for my two Shapes Thread Border Routers. Nanoleaf also has TBRs in their Elements and Lines controllers.

inner torrent
#

I haven't gotten the update hence it's missing still

twin vine
#

Ah right ๐Ÿ˜…

sick swan
trim venture
pine wave
#

Help is appreciated

twin vine
#

Do you have any other external border router?

And what are you using to commission? iOS or android?

pine wave
sick swan
inner torrent
#

Not sure if concidence that microwave knocks down some of my thread devices

twin vine
#

A few people here have mentioned that happens ๐Ÿ™ˆ

vapid shell
#

Yes

#

One of my 2 brs gets knocked out by it

fickle mantle
#

Yeah microwave ovens are known to leak radiation in the 2.4GHz regions

pine wave
twin vine
#

Tizen? What Samsung TV have ya got?

pine wave
#

A M80C smart screen.. I also have a dongle, which is connected to the screen... unfortunately disabling the Hub removing the screen from the network didn't help neither

#

on the web I found this:

"Unfortunately there is no way change the preferred Thread network on Android devices currently. The only 'solution' we know about is to clear all data for the Google Play Services app (system settings > Apps > All apps > Google Play Services > Storage & cache > Manage space), which stores the Thread networks. Keep in mind that clearing this will also clear other Google data that only exists on your device such as your Google Wallet cards (๐Ÿ˜ฅ)."

which was from july 13 2023. might have changed? does anyone know?

keen mango
#

SmartThings is awful, don't use it for Matter. Any other Thread Border Router would work better.

keen mango
pine wave
#

I currently don't use the smartthings feature at all.. I don't know how to add my eve energy or eve motion to home assistant without android trying to add it to the smartthings network

#

this is the reason why I get the "Unable to connect to thread network st-tizen" error message, isn't it?

twin vine
#

@sick swan would know, but I donโ€™t think things have changed

pine wave
#

I deleted play service data and now its working. great! thank you for assistance

twin vine
#

Itโ€™s wack to see a TV have a OBTR, but hey I guess its 2024

spice imp
keen mango
#

We all know this but Home Assistant is significantly better. I sometimes see SmartThings fans which claim it is easier, but this has not been my experience.

twin saffron
# vapid shell B4 apparently managed to build now ๐Ÿ˜‚ anyway if anyone keeps having to restart H...

@vapid shell thank you so much for this! Iโ€™ve been using an automation for months now to reboot HA whenever one of the Nanoleaf thread bulbs became unavailable. This would fix it but having HA reboot 5-10 times a day was no fun. Since installing 2024.2 the other day, I noticed that no reboots have occurred because the bulbs have all stayed available. I came here to see if I could find any explanation for that and found this. Thank you again! I was about ready to get rid of all of those bulbs.

vapid shell
twin saffron
#

Cool well as long as HA is able to reconnect them without me having to reboot, thatโ€™s good enough for me! Haha

vapid shell
#

Just keep an eye on it as your mesh grows

#

As they act as routers so they can take other devices offline

#

Size seems to be a factor in frequency of problems too

twin saffron
#

Will do thanks. Iโ€™m definitely hesitant to add more to the thread mesh at the moment.

serene prawnBOT
peak hill
#

Hi! I'm kind of new here and, although I have some developer experience, I'm just starting with HA. I would appreciate any help with me adding matter over thread devices to my HA. Sorry for the long post:

  • So, first I have HA installed in a Raspberry Pi 5 and all updated. I have a Sky Connect, and the open thread border router add-on and integration on and running. The Sky Connect has the appropiate firmware to support thread. I have the Zigbee integration disabled. MAtter add-on is installed and updated to last version too
    I've tried to add three devices:
  • Onvis 5-Key switch, It's installed under HomeKit device Integration via WiFi. I tried to switch it to thread by clicking on "Press" under configuration but the Thread Status of the device is still "Disabled". Under the logbook appears "Provision Preferred Thread Credentials" but It throws the following error:
    Failed to call service button/press. Onvis-HS2-66080A [DC:35:E3:66:08:0A] (id=21:47:34:28:2D:45) - DC:35:E3:66:08:0A: Failed to connect after 5 attempt(s): TimeoutError
  • Tapo P125M plugs. I wasn't able to add it directly to HA. I had to add it to the Tapo app, connect it to the wifi, and then add it to HA by adding the integration directly with its IP. I don't see any option to switch it to Thread.
serene prawnBOT
peak hill
#

Then I try to add the device via websocket too

    "message_id": "2",
    "command": "commission_with_code",
    "args": {
      "code": "30846023139"
    }
  }```
But it fails. Looking at the Matter server log I see this:
```2024-02-11 20:17:23 core-matter-server matter_server.server.device_controller[126] INFO Starting Matter commissioning with code using Node ID 5 (attempt 1/3).
2024-02-11 20:17:33 core-matter-server chip.CTL[126] ERROR Commissioning discovery over BLE failed: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
2024-02-11 20:17:33 core-matter-server chip.-[126] ERROR src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout at src/controller/SetUpCodePairer.cpp:324
2024-02-11 20:17:33 core-matter-server chip.BLE[126] ERROR BLE scan error: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
2024-02-11 20:17:53 core-matter-server chip.CTL[126] ERROR Discovery timed out
2024-02-11 20:17:53 core-matter-server chip.ZCL[126] ERROR Secure Pairing Failed
2024-02-11 20:17:54 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2024-02-11 20:17:58 core-matter-server matter_server.server.device_controller[126] INFO Starting Matter commissioning with code ```
#

I have the Bluetooth integration up and running on active scanning

sick swan
sick swan
#

@peak hill do you use Home Assistant OS?

bronze fog
peak hill
sick swan
#

The port assignment for add-on which use host network is not ideal.

bronze fog
sick swan
#

8080 and 8081. But that is only the case if you enabled them in the add-on config.

bronze fog
sick swan
#

I think I upstreamed support to change this at one point ๐Ÿค”

#

Ah I remember now. The problem is the web interface served on port 8080 accesses the REST API, and the port is essentially defined at compile time (or source even) ๐Ÿ™ˆ

#

I mean, ideally we want to get rid of that web interface entirly, and have a nice visualization in HA Core.

twin vine
#

Thatโ€™s an interesting concept

#

Not sure how well it would exactly work as google and co canโ€™t get the topology that reliable

bronze fog
#

Whooohoo..got Skyconnect joined to my Apple thread network.

twin vine
#

Nice work, you got any google BRโ€™a to add now? ๐Ÿ˜›

bronze fog
#

I hate Google. No.

twin vine
#

Haha fair

sick swan
sick swan
twin vine
#

Must of gotten more reliable recently, used to the case of you had to refresh the topology (in the web GUI of the OTBR) to get everything to confidently show up

vapid shell
#

dunno if they fixed OTBR, but at one point it would crash you had more than like 30 decides

#

and random missing data used to kick in before then

twin vine
#

Yup

sick swan
#

Uh I see. Yeah didn't get to that amount of devices ๐Ÿ˜…

bronze fog
vapid shell
#

someone did submit a patch for the 2nd one (increasing some timeouts), dunno if it went anywhere

sick swan
# bronze fog Actually Apple is rock solid. Google, not so much.

I mean I mostly kidding. In the end whatever floats your boat ๐Ÿ˜…

It is kinda interesting, Apple BR have been on Thread 1.2 for a long time, when Google was at 1.3 already. Suddenly they jumped to 1.3 and enabled TREL.

Now Google seems to be a bit behind. I think what sucks in Google world is the whole Fuchsia transition. It seems to me that the Thread BR integration suffered a bit with that transition. But that is my personal observation/thoughts, not sure how much to it is in reality.

#

In the end, I don't like both. You essentially have no control over their BRs they just do whatever they feel is right ๐Ÿ˜ข

twin vine
#

They havenโ€™t released a new fuchsia version since early October, or a new nest software version since early December.

They must of been hit hard by the layoffs

sick swan
#

Yeah looks like

#

What surprises me with Apple BR a bit is that they prefer global IPv6 prefixes if available.

#

Which is kida cool. But also, maybe I don't want that? ๐Ÿ˜…

twin vine
#

they do seem to be still working on it, just strange that its been radio silence for over 5 months

sick swan
#

Here, you may ping my Eve Motion sensor ๐Ÿ˜… 2a02:169:3c09:14:58c1:176a:fa9b:3480

#

So Apple is not firwalling anything

#

I opened the firewall on my router, but I am not sure how consumer routers behave by default. I am guessing/hoping they firewall incomming IPv6 traffic? ๐Ÿค”

twin vine
#

thats really bad

sick swan
#

DoS by battery draining ๐Ÿ˜…

twin vine
#

maybe its a side-effect of apples home hub implementation

inner torrent
twin vine
#

i mean, i trust you. but do you have any proof of that?

#

i dont deny that for one second, but i see nothing relating to AI at all in the fucsia patch notes

#

not that i would anyways

inner torrent
twin vine
#

fair

keen mango
#

What is the issue with Nest Thread Border Routers? Is it that they don't use TREL?

spring bramble
spring bramble
spring bramble
# sick swan So Apple is not firwalling anything

I don't think Apple should do the firewalling - the router needs to do that - but yeah - It kind of doesn't hurt if they would also put a firewall on the border router but maybe that is difficult with all matter controllers on the network ?

sick swan
#

Yeah, typically WAN -> LAN zone forwarding is blocked by default.

sick swan
spring bramble
#

It will be the big plus of our solution - we can have that kind of fine control to better secure it

vapid shell
#

Homekit has a protocol for telling your router what devices there are, IPs, ports, etc, and you can set a trust level too. Is it allowed internet? Can app use its own protocol? Is it homekit only?

#

Be great to be able to manage outbound ipv6 access with the SkyConnect

wispy lava
#

Hey! I just got my SkyConnect - is there a guide how to use it for Thread devices? It got listed as a device for zigbee instantly in HA but thats it ๐Ÿ˜

twin vine
wispy lava
#

Thanks that worked but how do i add devices now ๐Ÿ˜‚ - I just installed HA yesterday and never used Thread/Matter before

twin vine
#

oh right. a few things.

#

you on ios or android?

what devices you trying to add?

do you have any other border routers (apple homepod, google nest hub, amazon echo)?

#

the current supported way of adding devices is on the mobile app, go to add intergration, and you should see matter up the top, then you scan the QR code on the device

wispy lava
#

i just bought a few smart plugs to start of with Home Automation stuff and integrade WLED stuff i build and lights to home assistant

I do have an echo dot 5

twin vine
#

yep, seems like its supported. you should have no isses with it all

wispy lava
#

I was able to scan the QR Code via the HA App and now it says i need a thread border router first

#

didn't i just configured my sky connect as one?

twin vine
#

you are on IOS?

wispy lava
#

no android 14

twin vine
#

and there is no vlans or nothing on your network?

wispy lava
#

nah just a plain home network

#

but my HA runs under proxmox as a vm

twin vine
#

you got working ipv6 in your network? and have not restricted any mdns?

toxic vector
#

Same issue here

#

though I am using a sonoff dongle I reflashed instead, but having opened logs

wispy lava
#

ipv6 is working, HA Server also got IPv6 adresses

toxic vector
#

I have a bunch of errors in it

# 
otbr-agent[181]: 00:00:07.823 [N] Mle-----------: RLOC16 fffe -> 4c00
otbr-agent[181]: 00:00:07.825 [N] Mle-----------: Role detached -> leader
otbr-agent[181]: 00:00:07.825 [N] Mle-----------: Partition ID 0x1fe38cda
otbr-agent[181]: 00:00:07.911 [W] Platform------: [netif] ADD [U] fdd7:62c5:da3c:e937:0:ff:fe00:4c00 failed (InvalidArgs)
otbr-agent[181]: 00:00:07.912 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[181]: 00:00:07.914 [W] Platform------: [netif] ADD [U] fdd7:62c5:da3c:e937:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[181]: 00:00:07.915 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[181]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[181]: 00:00:08.183 [W] Platform------: [netif] ADD [U] fdd7:62c5:da3c:e937:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[181]: 00:00:08.184 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[181]: 00:00:08.189 [W] Platform------: [netif] ADD [U] fdd7:62c5:da3c:e937:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[181]: 00:00:08.189 [W] Platform------: [netif] Failed to process event, error:InvalidArgs```
#

This goes on non stop for about 8 hours and then the addon crashes

#

Seen multiple github issues for this as far back as OpenThread border router 2.4.3 having been released, seems widespread among multiple border router devices, but I am not seeing anyone posting fixes yet

twin vine
#

right, that issue is more a @sick swan thing ๐Ÿ˜…

twin vine
#

and try re-adding it, maybe it will work then

wispy lava
#

Poshy, it says device is connected ! ๐Ÿ˜„

twin vine
#

nice work!

wispy lava
#

Nice Guiding!

#

Wow i can turn on and off stuff, fancy

twin vine
#

yeah, and even better. its all local!

wispy lava
#

Now time to figure out how to read wattage and stuff

twin vine
wispy lava
#

Onvis S4EU

toxic vector
#

I dont think that does power monitoring

wispy lava
#

lol

#

my 10โ‚ฌ kasa plug could do that

toxic vector
#

looks like it doesnt

wispy lava
#

wow

#

i fcked up big time

#

xD

toxic vector
#

matter also has no official support for that either

twin vine
#

currently, only the eve smart plug has wattage features, its releasing to the matter 1.3 spec officially in a few months

#

yeah and i dont think your plug can monitor power, feels bad man

wispy lava
#

feels really bad

#

i wasted so much money

toxic vector
#

was gonna say, eve have one but its not done to current matter standard, they basically just assumed what such an endpoint would look like and did it (and hey, 1.3 is indeed the same when it hits)

twin vine
#

yea, no doubt they will comply with the spec officially (and HA will remove custom cluster support for power) when it releases and the device is updated

wispy lava
#

wow i messed up soooo hard

twin vine
#

can you return them? ๐Ÿ˜…

wispy lava
#

man gonna try and chat with big A to get that retoured or something Haha

wispy lava
twin vine
#

oh shit haha, maybe try to get a refund out of amazon, might get lucky?

wispy lava
#

yes maybe it'll work

#

but no idea what to say as it was a pack of 4 haha

twin vine
#

just say the device/s doesnt connect at all and is broken when you recived it, might get lucky

wispy lava
#

gonna do it now

#

wish me luck

#

So what do you guys recommend for measuring power, maybe get infos to grafana

twin vine
#

currently, via matter. the only devices that report power are the eve. plugs (in home assistant)

wispy lava
#

so you're german too i see

twin vine
#

no, im australian. just over in europe at the moment ๐Ÿ˜…

wispy lava
#

oh lol

#

i messed up again

toxic vector
#

non matter wise I have some frient smart plugs that I think come in EU socket variants and work over zigbee. A shelly 3em monitors power at the breakers and I have some other shelly power monitoring stuff over wifi too

twin vine
#

how'd it go with amazon?

wispy lava
#

Looking good

twin vine
#

nice nice

wispy lava
#

ye i got a label haha

toxic vector
#

amazon dont tend to be stingy with refunds

wispy lava
#

i know haha

#

i ordered this 4 pack, and a pack of 2

#

tommorow i gonna do the same for the pack of 2 ahaha

toxic vector
#

but do watch it, most cheap smart sockets dont do power monitoring, and even some of those that do, are woefully inaccurate

wispy lava
#

Well time to figure out what to buy then

twin vine
#

yep, normally its best to go a reliable brand like eve, where you know they are trusted

#

but they are quite expensive in comparision

toxic vector
#

Case in point, one of my frient devices records the extension cord my PC runs off of as consuming 20W of power overnight

#

Unplugging and plugging in devices to find the culprit? Its my monitor

wispy lava
#

lool

toxic vector
#

It records the monitor as consuming over 15W on its own

#

But if I use a current clamp and a high voltage differential probe with my oscilloscope to measure the RMS voltage and RMS current, and also make a math channel for instaneous power and take the mean of that channel to get active power. Neither figure is anywhere near 15W

#

Further investigation, it appears the crest factor for the monitor in standby is quite high, and this throws off whatever the power monitoring IC in the smart plug is doing

wispy lava
#

Wow the eve ones are way to expensive for just one plug

#

thats insane

twin vine
#

Yeah, they are quite highly priced

wispy lava
#

i mean i dont need matter at all now

twin vine
#

Maybe wait for the 1.3 matter spec to release, and see which ones offer it

wispy lava
#

oh thats an idea

#

oh looks like the pack of 2 i ordered from a different vendor got power measuring

#

gonna try them now haha

toxic vector
#

Ive also seen them arbitrarily decide that the grid is 655.36V (suspicious number for those that know binary). But only for a single sample once in a blue moon, and you know its no lightning strike because they'd all record it if it was

wispy lava
toxic vector
#

theres a non zero chance that again due to matter not having power monitoring features that the power monitoring only works in the meross app

#

theyre also wifi plugs but oh well, I'm using a shelly device and thats wifi too

wispy lava
#

Theyre matter or wifi

toxic vector
#

Matter is application layer protocol

wispy lava
#

but hyeah you probably right and they will only show the measurements in their own app

toxic vector
#

doesnt have to be thread underneath

wispy lava
#

oh

toxic vector
#

Matter over ethernet and matter over wifi are also things

#

those are matter over wifi not matter over thread

wispy lava
#

ah

toxic vector
#

Technically speaking matter over anything IPv6 is possible, so if you really want to, you can go right ahead with matter over RFC6214

wispy lava
#

you sound like a sysadmin

toxic vector
#

Just because I can use google to double check the RFC numbers for IP over Avian Carrier

wispy lava
#

yeah but most people have no idea that RFC numbers are a thing

toxic vector
#

I'm a software engineer

#

some good news though, 3rd times the charm

#

having uninstalled and reinstalled the necessary addons a few times

#

I have 1 matter over thread bulb working on my network

#

A bulb I know isnt overly exciting, and it was entirely pointless replacing a perfectly functioning zigbee bulb with a thread bulb, bought me no advantage whatsoever. But I like playing with stuff

twin vine
#

Nanoleaf bulb?

wispy lava
#

uh a software engineer ๐Ÿ˜„

#

does anyone got experience of getting data from HA to InfluxDB or some other time series?

serene prawnBOT
quick bronze
toxic vector
# twin vine Nanoleaf bulb?

yup, its cheap, proves whether the thread network is working or not before I potentially start messing around with making my own thread devices etc etc

keen mango
#

Funnily enough the Nanoleaf bulb was my very first smart device.

#

This was a few months ago... My apartment is much smarter now.

toxic vector
#

Its only my first matter one

#

22 zigbee devices apparently, then again remotes and bulbs add up (its not that I think this is a ludicrously huge amount, I just have a small house)

#

a few ESPHome devices, and some stock firmware Shelly devices too

#

small enough home that with the british ring main system, a single shelly 3em gets me per breaker power monitoring already

inner torrent
toxic vector
#

Eh, its currently working, which means my thread network must be working. If my network wasnt, then the nanoleaf wouldnt either

digital salmon
muted parcel
#

In my setup I have I KVM VM running HAOS with a skyconnect passed to the VM. I have Theard installed and showing a network with not boarder routers. I have the OpenThread Border Router app installed. I have only got the OBR to work once. The skyconnect I used the online flasher to push the OpenThreadRCP firmware. I also have the SkyConnect CP2102N Programmer app installed that seams to come into play. Network is a cisco switch with unfi wifi with everything on the same vlan.

My question's
How do I get the OBR to work reliably.
once the OBR is up I should just be able to open google home app and add the lights right?

twin vine
#

Do you have a google nest device that is a border router?

muted parcel
#

No isn't that the point of having a obr? Does it have to be Google to work with Google??

twin vine
#

You got iOS or android device?

muted parcel
#

Android

sick swan
muted parcel
#

On it

sick swan
muted parcel
#

the sync is done, thanks um let see what i got over here

#

OK I haven't got the open thread router to start it will not start for the lifeme . I had it working once But I had to do a reboot and it's been screwed up ever since so I don't know what to tell you.

sick swan
#

Can you share the logs of a start attempt?

muted parcel
sick swan
#

Hm it seems to fail probing the application type. Can you double check nothing else is (trying to) use the stick? E.g. make sure ZHA is not using that device

muted parcel
#

i dont see any integration for zigbee nothing hiddden

sick swan
#

So from the logs it seems that flasing fails. Flashing on your PC using web flasher is really not necessary, but it also shouldn't hurt. Can you try to flash again using the web flasher and see if that works?

muted parcel
#

Yeah I'll do that tomorrow. Thank you

toxic vector
#

So alas
I'm not really sure what actually fixed it

#

I did find a good half dozen to a dozen forum threads and GitHub issues of folk with same issue without any resolution. Mixture of border router hardware across them. Mines a sonoff zbdongle-E that has been reflashed

sick swan
toxic vector
#

No

sick swan
#

Ok.

toxic vector
#

I am not using multiprotocol

#

It was a pure OTBR firmware, and I have a separate zigbee radio running purely a zigbee firmware.

sick swan
#

I am wondering mostlyi about these InvalidArgs messages. I am actually not sure if those are really critical though.

otbr-agent[181]: 00:00:07.911 [W] Platform------: [netif] ADD [U] fdd7:62c5:da3c:e937:0:ff:fe00:4c00 failed (InvalidArgs)
otbr-agent[181]: 00:00:07.912 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
toxic vector
#

Yeah that was the search term I used while looking to see if others have issues

sick swan
#

And as soon as those disappeared things started working?

toxic vector
#

I am at work for the next 8 hours so cant go and check logs to see if theyre still there

sick swan
#

The problem is, OTBR is running in host network context. So an add-on restart doesn't give a "clean slate" in that sense. There might be things left in a intermeadate state, especially when the OTBR actually really crashes. Only a host reboot of course makes the network config pristine again...

sick swan
toxic vector
#

It has died while I was out

#

I errm, slightly forgot to get the logs before seeing if it would successfully restart

#

Post restart there's a few more instances of the same error, but it is operational again

#

And only a few instances of it. Taking a shower butnill stick it on pastebin after

toxic vector
muted parcel
#

i got OBR up and phone synced with thread now google is giving me can't reach device make sure your phone is connected to wifi and it is connected

inner torrent
#

You sure your device is in pairing mode?

muted parcel
#

yea it pop's up on my phone saying add deive i also reset the nanoleaf contoller to be sure

muted parcel
#

So everything I've read Google home on Android just sucks. I wonder if anyone's got the nanoleaf to pair with Google home app on Android. Freaking ridiculous

twin vine
#

holy shit the gods have spoken, new nest updates

#

it seems to be using Fuchsia 16?

#

verison 16.20231130.3.59

normal arch
#

Gods of perpetual beta

muted parcel
night moth
# muted parcel So everything I've read Google home on Android just sucks. I wonder if anyone's ...

Google home has been the most consistent to pair with for nanoleaf. Pair to that then HA has been the easiest way to get nanoleaf into HA. Or using nanoleaf app, go devices, go into one and click connect to connect it to google home.
Also make sure you get on the nanoleaf beta, the current .136 firmware is way more stable - https://helpdesk.nanoleaf.me/en-US/how-do-i-sign-up-for-beta-software-updates-for-my-nanoleaf-lights-341522****

inner torrent
sick swan
#

However, no TREL (yet) it seems ๐Ÿ˜ข

twin vine
#

Yeah, maybe just wait for the fuchsia patch notes for v15 and/or 16 to come out, might give some better indication about whatโ€™s happening with it all

merry bison
#

So, I have a Skyconnect flashed with Thread-only firmware (no Zigbee), but I can't figure out how to configure OTBR integration to use it. It's asking for a URL. I've never used thread before. Help!!

bronze fog
#

@merry bison Go go add-ons, then add OTBR. The configuration tab of the add-on will show you the serial devices, baud rates, and other options. Ensure your skyconnect is found, then start the add-on and monitor the logs. No URL is needed.

wispy lava
sick swan
#

The Silicon Labs Flasher add-on by default installs the Zigbee fiirmware

wispy lava
#

Oh and this is safe to use with the skyconnect?

sick swan
#

Generally yes. Still probably a good idea to not remove the SkyConnect during flashing ๐Ÿ˜… Observe the logs to see flashing progress. The add-on will automatically stop after finished.

wispy lava
#

Haha ye got it working thanks! ๐Ÿ˜„

sick swan
#

For those using the OpenThread Border Router add-on: The newe release 2.4.6 is mostly bug fix. A visible change is caused by the right order of service shutdowns. Now mDNS stays active when OTBR get shutdown, this allows the OTBR to send out a proper mDNS remove of the _meshcop._udp service. In practice I can see that non-local running OTBRs disappear immeaditly from the list of BRs when stopping the add-on. I don't think that BRs themself use the mDNS to learn about each other, so this probably has little effect in practice. But I stumbled upon this while debugging container shutdown in error cases, and it seemed a nice cleanup ๐Ÿ˜…

vapid shell
#

Not that it seems to matter much with the neighbour detection stuff

merry bison
#

I suspect however, this means I need to (Independently) install a separately docker image - will look into this.

twin vine
#

do you have the OTBR docker container?

merry bison
#

No. Checking that out soon. Working on some things. I realized after Traveler99845 mentioned the add-on, that there must be a corresponding Docker container for use with my setup. Thanks!
I'll make sure to forward /dev/ttyUSB0 to the OTBR container instead of my HA.

sick swan
#

When you run OTBR yourself, keep in mind you'll have to do some OS configs, e.g. enable IPv6 routing and make sure NDP is properly handled. The Python Matter Server README has some hints.

scarlet seal
#

Can anyone recommend a thread router that I can plug into an outlet? I have a door lock that communicates over thread but it's far away from my usual thread routers (e.g. Apple TV)

sick swan
#

The Onvis S4 smart plug are kinda nice. And you can keep using the outlet ๐Ÿ˜…

scarlet seal
#

Great thanks will check it out!

scarlet seal
tacit dirge
#

Any thread bulbs that don't suck

#

The beta nanoleaf firmware is just worse and worse

twin vine
#

Not at the moment

#

I did see when I was in the UK that wiz had some maybe?

sick swan
sick swan
twin vine
#

Oh wait maybe?

toxic vector
#

What precisely is it that folk find wrong with the nanoleaf bulbs? I've seen a lot of mention of them being dodgy but not a single elaboration of how they're dodgy

#

I have one that seems to be working just fine and trying to figure out whether this is a difference in my usage that I'm not running into the problems or the issues are overstated

worn plinth
toxic vector
#

Hmm, not had a single disconnect yet, but I also only have a teeny tiny thread network at moment

#

probably not got enough devices to notice the issues

worn plinth
#

consider yourself lucky! i only have like 6 thread things but i noticed the disconnect instantly in HA. it's quick, so it's not super likely to disrupt automations, but it was pretty apparent when i looked in the state history

#

imo the worst thing about them is what is wrong with tons of home automation crap - you have to think about them. they go offline so they screw up their state, you have to fuss with them when they lose power too long, etc. the fact that you can't not think about them is aggravating as hell for me personally

toxic vector
#

yeah so thats the thing, I literally only bought one because it was all of ยฃ17. Making it the single cheapest thread device I could get

#

No real reason to sidegrade into it from the zigbee bulb I already had in that spot

#

Just wanted to test, "does my border router work full stop?" Yes, yes it does

#

Ultimately if its problematic, eh, it was 17 quid and has done its job. I can swap back easily

inner torrent
#

The beta FW has improved a lot over the general FW

flat drum
#

Looking for help building an OTBR using an EFR21 and SimplicityStudio5

keen mango
# vapid shell Let me know how you get on - not had much beta feedback!

I promised long-term feedback. To update my experience, I'm not using the Nanoleaf beta and I've previously had a ton of issues. However since updating to Home Assistant 2023.2.1 my Thread network is significantly more stable. I still get occasional disconnects but I no longer have the issue where the entire Thread network crashes. Thread devices also reconnect much faster.

modern root
#

if you want further feedback, seems fine, I have OTBR running in HA and also a espressif-otbr device as border routers, the thread network is stable and seems to rebuild quickly. The matter server seems to have ate itself unfortunately

vapid shell
#

Only interested in homekit over thread so no thanks!

vapid shell
#

Unless itโ€™s some sort of spooky action at a distance

#

Maybe nanoleaf devices choke on incorrectly encrypted packets, and we were generating them at least once a minute in this edge case.

#

Then they fail to act as routers and any sibling or child devices become unreachable

#

But if you are see king your devices reconnect and you arenโ€™t having to restart HA because of disconnected homekit devices Iโ€™m happy

keen mango
vapid shell
#

Then itโ€™s definitely not the thing I was talking about โœ”๏ธ

#

The matter server addon is much better at reconnecting from what I recall

keen mango
#

Yep I've definitely noticed that Matter devices reconnect faster. But more importantly for me is that the Thread mesh network no longer crashes. It's fine if some devices occasionally disconnect, but what used to happen for me is that the entire Thread network would become inaccessible. This used to happen several times a week but has not happened even once since updating to HA 2024.2.1.

foggy wyvern
#

hello
i am trying to follow along with running a multipan container in my docker-compose file, next to my ha container.
i flashed the 4.3.1 firmware to my skyconnect, and the multipan container seems to be running fine.
i think i need to set up the otbr right now, but i am not sure what to do there. should i fill in some values under the "form" menu option on the left?

foggy wyvern
#

hello

urban sierra
#

Guys.. In my house there are only de-googled android phones, I have some thread capable devices and skyconnect (in a machine with HAOS) but no other thread border router. Is there a way for me to connect the devices to skyconnect? Or is there something being developed to enable that?

vapid shell
#

Depends what devices you have

#

If your HAOS has Bluetooth and SkyConnect, homekit over thread devices will work today without needing any android or iOS devices.

#

Thereโ€™s no built in way to pair a matter over thread device without google or Apple sdks on a google or apple device

#

Itโ€™s on the todo I think

urban sierra
#

Thanks @vapid shell. But maybe I can use google SDK somehow on my custom ROM.. I need to know basically what is needed from google SDK

spice imp
thorny agate
#

I'm trying to get Matter+Thread working with SkyConnect (no branded border router available) and HA on Docker. I'm aware that this is not officially supported, but I was able to commission and run basic tests with an Eve Energy just fine using a community-provided Docker image for multipan. However, I don't need Zigbee, and it is now recommended to run thread-only, so I'm now experimenting with how to switch to that setup. I have the thread-only firmware flashed onto the SkyConnect, but now I'm trying to work out how to run the OTBR in Docker.
I've got it starting up openthread/otbr successfully and I'm getting the web UI and can (apparently) form a network. But I'm not sure how to continue from there, how to test it, and how to integrate it with HA. I'm not even sure if the REST API is enabled on OTBR, as all the guides I found only export the web UI port and not a separate REST API (as the multipan image does). Has anyone gotten a setup like this working?

# 

services:

  otbr:
    image: openthread/otbr
    volumes:
      - /dev/ttyUSB0:/dev/ttyUSB0
    privileged: true
    sysctls:
      net.ipv6.conf.all.disable_ipv6: 0
      net.ipv4.conf.all.forwarding: 1
      net.ipv6.conf.all.forwarding: 1
    ports:
      - 8086:80
    dns: 127.0.0.1
    command: ["--radio-url", "spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800"]```
#

This is my Docker Compose config โ˜๏ธ

vapid shell
#

one is sort of trying to pretend you have HAOS, but without having HAOS

#

one is treating OTBR as a seperate service in your home network that you manage directly

#

theres no real reason (at the moment, at least) to worry about the REST api if you do (2)

#

and as it doesn't yet have auth, depending on how your network is set up, you might prefer (2) for that reason alone

#

OTBR needs to route packets between your home network and your thread mesh, so it needs to have host networking (there are more advanced setups like macvlan that can avoid host networking, but the point is it needs a direct connection to your LAN)

#

if you fix that, then the only other thing you need to do is get your new networks TLV and import it into HA

#

you can get the hex form of it by running 'ot-ctl dataset active -x' inside the otbr container

#

then in your thread dashboard in HA, click on the "..." menu in the top right and choose "Add dataset from TLV" - job done

#

if you changed your network parameters and you have a google device and have a matter eve energy device, i believe you are in for a hard time - google likes to remember your credentials and last i heard we can't overwrite them. hopefully someone else will share the steps here if they are still needed.

#

with a homekit eve energy device, you should just be able to hard reset it and pair it again (assuming you set it up over bluetooth in the first place)

#

if you want to go for option (1) you'll need to make sure you track the patches in the HA version of OTBR

#

as the HA OTBR sometimes has different features to the upstream ones (until they are merged upstream)

thorny agate
#

Thanks a lot for the detailed response! Yes, I think just going with option (2) seems like the best choice for me. I was under the impression that I needed the REST API, as when I set it up with that multipan container, I entered that into HA. But if that's not needed and I can just import it directly, that's good as well. I will try it later.

#

The networking options are copied from some example code I found, I can change it to host networking for sure. I guess then all the sysctls are irrelevant, and also the dns, right?

#

Previously I got it to work by commissioning via websocket RPC on the matter server directly (with bluetooth on the server itself), not with an Android device. That's not the best option but is what worked, so maybe I can get that working, too now. I'll try it.

#

One more question: How/where does the OTBR container persist data (like the network settings)? The multipan container had a Docker volume, but this one seems to not have it or at least not explicitly documented some place I've seen.

peak ocean
#

So the Nanoleaf downlights still aren't released in Australia, but is the general consensus on the Nanoleaf matter/thread devices absolute garbage? I'm just deciding between waiting for them to eventually be reused or just getting Philips Hues

vapid shell
covert flare
vapid shell
twin vine
#

Mine got shipped out mid-jan

peak ocean
twin vine
#

Huh right, I preordered early December, so maybe they are low on stock?

Also the beta firmware is a ton better than the current GA firmware e

#

And Nanoleaf is pretty relaxed on refunds due to the shitty firmware

vapid shell
peak ocean
#

I mainly just prefer to deal with JB in store just in case, but good to know that they at least exist

twin vine
#

Yeah, might have to ask JB If/when they will be releaed, no doubt they have a backlog tho

peak ocean
#

Worth the wait or ehh?

twin vine
#

They are not too bad, but they can be annoying if you have physical switches turning them on/off

peak ocean
#

What do the physical switches do to them?

vapid shell
twin vine
#

And with Nanoleaf firmware, it can take a while for devices to recover

peak ocean
#

Do they turn back on straight away (the light part) and eventually rejoin the thread network reliably every time?

twin vine
#

They take maybe a second? And they recover to the last state

#

But can take a while to re-appear on the network

peak ocean
#

What's a while?

#

That doesn't sound too bad so far

twin vine
#

Itโ€™s alright, they are working on improving the firmware

#

Slowly that is

peak ocean
#

How many are you running?

twin vine
#

4 atm

peak ocean
#

Any weirdness where one of them randomly drops out etc?

#

I've currently got a handful of Nanoleaf thread lightstrips and seems like one drops out on average every 2 months and needs a power cycle, but it's a random one each time

twin vine
#

There is the odd occasion they donโ€™t all turn on at once (they are a group in HA) but thatโ€™s mostly due to them being overloaded I rekon, so maybe a new fw will improve it

twin vine
#

@peak ocean appears officeworks has them

keen mango
# peak ocean What's a while?

Reconnecting to Thread can take anywhere from several seconds to several days! But the latest Matter server for Home Assistant is able to handle reconnections much more gracefully.

peak ocean
peak ocean
#

They don't have the 4 pack, that's annoying

#

Oh hey Mwave and Amazon have them, excellent

twin vine
#

Nice!

peak ocean
#

Thanks for giving me the heads up so that I checked other sellers

static spear
thorny agate
# vapid shell With those sysctls youโ€™ll disable dead neighbour detection. Probably not critica...

Ah ok, thanks again for the hints! I was assuming that those are just needed to get it working with bridge network (or in a somewhat working state) as per the examples I've seen. But it should not be an issue to set those sysctls on the host machine with host networking, too, if they are still required/useful. Although as you say, I do want to run the matter server on the same machine also with host networking, and plan to have just one BR for now.

thorny agate
brave crown
#

Since Mid December 2023 I was operating without any issues a joint thread network between my SkyConnect/Home Assistant Yellow OTBR and my Apple TV TBR. However, yesterday for this first time all my 6 Eve Thermo devices became unavailable. Rebooting was unsuccessful, so I deleted the OTBR config on Home Assistant and started over by reinstalling the OTBR Add on, joining the Apple Thread network again and have it as a preferred network, then adding successfully all 6 Eve Thermos again. This worked for I guess about 24 hours until the whole thing crashed again today. I ended up now adding the Eve Thermos to a separate Home Assistant OTBR configuration, essentially leaving the Apple TBR with its own thread network. Does anybody have a glue, why suddenly this kind of issues appeared with a joint HA/OTBR <-> Apple TV TBR thread network? May it have anything to do with some of the recent Home Assistant OTBR add-on update releases?

vapid shell
#

when did you last update the OTBR add-on?

#

a while ago TREL support was aded to the HA OTBR, and we discovered a potential route loop because of it. in the course of debugging that i think we discovered that a setup like yours would only be using the Apple BR's. the fix for TREL would have meant that only the HA OTBR was used (though because of TREL, the Apple BR would have been used more indirectly).

#

but there have been 3 more updates since then

#

do you see any errors in the OTBR logs?

modern root
twin vine
#

Rolled out TREL which aims to reduce Thread partition and reduce Thread network usage when possible.

#

hmmmmmmm

#

maybe it only enables it when prompted somehow?

brave crown
# vapid shell do you see any errors in the OTBR logs?

Yes, I saw some errors in the log, but could not make sense of it. Letโ€™s see. Just wanted to touch base whether there is a known error or bug with the latest OTBR release. Seemingly not. With OTBR forming a separate thread network things are stable so far. I may do some additional troubleshooting at the weekend.

peak ocean
#

neat

#

So first batch of Nanoleaf downlights seem to work okay so far, will give it about a week before I replace all the rest

#

Now just need to also add smart dimmer switches, are there any thread based ones yet?

inner torrent
peak ocean
#

later this year sounds gud, though it's uh, not the best looking thing

twin vine
#

but then again, who knows how long delayed a local au release will be

peak ocean
twin vine
#

one of the nanoleaf devs sent out a link a while ago in the NL discord

peak ocean
#

ah righto

#

But something that is like this would be great

twin vine
#

yeah for sure

peak ocean
#

everyone likes spinny things

#

Alright looks like JB HiFi has the Tapo things and it can bridge on to matter, so that's probably good enough

#

so unless someone else comes up with a better thread based spinny switch, that might be the way to go for now

twin vine
peak ocean
twin vine
#

hey not bad!

peak ocean
#

Yeah, they're battery powered so no expensive electrician to put them in, but need to be sure it actually works first :V

#

but if they're matter, they should in theory work

brave crown
keen mango
inner torrent
#

I think the wall switches look great but I'm not a fan of the remote

#

It looks like the right amount of functionality. I have some inovelli on order but actually think the NL looks more functional

white mango
#

Hi, i have a nanoleaf stripe and no Thread Router. How can i add the stripe to my Homeassistant?

My Homeassistant run at a Raspberry 4 Model B with a 32-bit OS and i have a Sonoff zigbee zbdongle-p must i buy a zbdongle-e or skyconnect stick?

twin vine
#

do you have a skyconnect/other thread dongle?

#

ah wait 32 bit OS, i dont think you can run even the matter server

vapid shell
#

Yep pretty sure you are right there - the upstream matter code doesnโ€™t support 32bit Linux at all

white mango
twin vine
#

to have a chance, yes

#

and currently pairing devices direct to a skyconnect or other thread dongle without a external BR is a bit flaky

white mango
twin vine
#

its supported well if you have a external BR, like a homepod mini, google nest device etc etc

vapid shell
#

Ideally youโ€™d be running HAOS too as some scenarios require kernel patches and patches to other system components like network manager

white mango
white mango
twin vine
#

multi pan has its own issues

#

also, have you got ios or android? i dont think you can pair a device direct to a skyconnect/other if you have an ios device

vapid shell
white mango
vapid shell
#

multi-pan is discouraged because it seems to crash more

#

but more than that, you end up restricting the bandwidth of your zigbee AND thread network. not just by forcing them on to the same channel, but because the bandwidth of the dongle itself is less than if you had 2.

white mango
#

i can use my zbdongle-p for my zigbee devices and use the skyconnect for the other. so this is not a problem

#

than i have 1 Dongle for Zigbee and one for OpenThread/Matter

twin vine
#

yeah that works

#

i believe once you sync thread credentials on the android companion app, you can pair direct to the skyconnect

white mango
vapid shell
#

fingers crossed!

white mango
twin vine
#

OTBR add-on

#

it does all the work

#

just gotta sync the creds once you started the add-on

#

then add the device and you should be good to go

vapid shell
#

^ the addon triggers the installation of the OTBR integration, which in turn creates a network for you and then imports the creds from it into HA ready for the app to use.

#

then the sync button is in the android app

#

(does it still sync the first time you try to add a device too?)

white mango
#

ok, thanks for now. i try it at the weekend and when i need help i come back ๐Ÿ˜„

twin vine
#

good luck, you can always ask here if ya get stuck

queen plume
#

Hi, Iโ€™ve recently bought a Wisdom Matter over Thread TRV (WISZWDM-TRV031) and have been trying to set it up with Home Assistant using Sky Connect set up with Thread. However I get the dreaded Thread Border Router required message. Everything is up to date and Iโ€™ve tried some of the things mentioned here and elsewhere- use an android phone, turn on BT - but still the same. Has anyone got that device working? Anything else I can try? Thanks

toxic vector
#

Imported the credentials in the companion app on your phone?

queen plume
#

Yes, a short time after scanning the QR code it goes to a new screen saying Border Router required. But HA has the integrations installed for the OTBR, Thread and Matter, and the Sky Connect is flashed for Thread only.

queen plume
#

Tried the companion app on iOS and android but just the same

vapid shell
#

Have you got any other thread devices working?

#

Are you using HAOS? If your phone on the same network as HA? No VLANSs? Whats the distance between the Wisdom and your phone when you try this? What about the Wisdom and the BR?

#

Don't waste your time with iOS here - it works perfectly well with HomePod's (and with TREL, some would say thats the best option if your daily driver is an iPhone), but for SkyConnect you are better off with Android atm.

queen plume
#

Thanks. This is my first thread device, maybe not the best one to start with, so Iโ€™m feeling my way with it. Iโ€™ve just checked - yes, itโ€™s HAOS, same WiFi network as phone. Running on a RPi4 with zwave & BT dongles, zigbee shield and Sky Connect for Thread only. All the devices are within about a couple of feet of each other. Iโ€™ll have another go this afternoon with the android in case this mornings updates help and check the logs. Presumably the OTBR logs are the ones of interest?

vapid shell
#

Well if Android is correct that the OTBR canโ€™t be found, what we are looking for is nothing in the logs when you try to do add your device.

toxic vector
#

I can't post images in this channel it seems, can in some others. But in the android home assistant app, go to settings > companion app > troubleshooting > sync thread credentials.
If you are sure you've done that before, do it again anyway. I did have unexplainable issues myself having uninstalled and reinstalled otbr a few times and syncing the credentials each time, but eventually it just worked TM

#

Essentially this step is required so your phone has the network IDs and encryption keys it can send to the matter device by ble to allow the matter device to join network in the first place

queen plume
#

Thank you and I was just re-reading the instructions here https://www.home-assistant.io/integrations/thread and realised Iโ€™d missed that step. Using the android app, it all went through first time. Thatโ€™ll teach me to read the docs properly rather than get carried away with installing the integrations which all happens intuitively. Grateful for your patience.

toxic vector
#

No problem, glad you got it sorted

#

It's an easy enough step to skip by accident, dunno if there are plans to streamline it one day (a more useful error message would certainly be appreciable)

keen mango
toxic vector
#

didnt on any of my attempts

keen mango
#

Yeah it was a bit unpredictable. I remember when this was the only option I sometimes had to try several times adding a Matter device. It was also annoying when I already added all my Matter devices and needed to import credentials again. So the recent addition of that button is much appreciated.

white mango
#

Servs, boys and girls. Short question. is it ok when i run Openthread and Matter? I have now new installed my Homeassistant and install both of them. Also i have the skyconnect stick and a stick for Zigbee connected.

toxic vector
#

I do

white mango
toxic vector
#

yes though using separate radios

white mango
#

ok, thanks

toxic vector
#

the multiprotocol firmware for some radios is an option, but not one many would recommend, too unreliable

#

but I have a home assistant yellow, running ZHA with the onboard radio with 20 devices and then OTBR with a plugged in USB radio, and then the matter server with 2 matter over thread devices

fresh marlin
#

Hello everyone! I would like to ask for some guidance on how to tackle the commissioning issues I have with thread.

#

I have an up-to-date RP4 installation of HAOS. I have a GL-INET S200 thread border router which is recognized by HA, I also imported the TLV data of the thread network created by the S200 without issues into HA. My issue is that the commissioning fails after a number of seemingly successful steps. After scanning the QR code, I briefly get "searching for device", "connecting to device", "creating matter credentials", all of which seem to work fine, but I finally get "checking network connectivity" which fails after about 2 min with "can't reach device, make sure phone is connected to wifi". The thread device is an Eve Energy.

#

I can add Matter/wifi smart plugs, but the thread plug doesn't work.

#

If I do not sync the thread credentials to the phone, the commissioning tool actually complains that there is no thread border router, so I believe that the TBR is actually working, but I don't know how to check this. Unfortunately, this is also (for now) my only thread device, because I want to test matter/thread before going all-in on the smart-home thingy in general.

#

I should also mention that I do not have any other TBR, and I'm not planning to jump on the Apple/Google/Amazon/etc. train anytime soon.

#

The S200 TBR is based on OpenWRT, and I have access to it's web interface, luci interface, and I can access it via ssh. I just don't know what to look for to find out how to fix this... which is why I'm here.

white mango
white mango
#

Ok forget it. I have the solution. Thanks

queen plume
#

I think the issue I had was I didnโ€™t realise I had to use an android (at the moment) for more than just adding the device.. Iโ€™d managed to install everything else using web or the ios companion app, but hadnโ€™t realised that I needed to use the android companion app to import the credentials as well as adding the new device. The Import Credentials error message on iOS didnโ€™t get me on the right track, but maybe thatโ€™s just me. So thanks for the extra guidance.

peak ocean
#

JB has Nanoleaf downlights finally, but only the two packs

twin vine
open wigeon
#

Morning all. I am having an issue with deleting a thread network. I no longer plan to use my Google Wifi Nest Pro network. I have deleted this network (using the trash can icon) on both the PC and companion app. I then set my HA thread network as the preferred network on both. I then go to sync the thread credentials via the companion app and get an error message saying โ€œHome Assistant and this device prefer different networks (device prefers: NEST-PAN-103E).โ€ Then, when I go look back in the thread integration the Google network is re-invented?! Any ideas how to stop this Google network re-appearing please?

spring bramble
open wigeon
spring bramble
open wigeon
spring bramble
open wigeon
open wigeon
#

For clarity, I have followed the documentation for "creating a HA border router when there is an existing network." However, it keeps adding a new network, perhaps because the NEST network does not have a norder router associated with it?

spice imp
spring bramble
sick swan
merry bison
#

What is the correct radio url to pass to otbr docker command for a NabuCasa SkyConnect running thread-only firmware?

#

I know the device is ///dev/ttyUSB0

#

I see the example url of spinel+hdlc+uart:///dev/ttyUSB0 on the otbr docs, but I'm not sure they were using the same chipset in their reference.

spice imp
open wigeon
#

Thank you all for the guidance on deleting the Google thread network. All done, just a single HA network now. First device added, time to add many more!

full canopy
#

Will there be a way (in the future maybe) to move devices to another network from within HA? I still have my Google Nest devices on a separate network and Iโ€™d prefer to move then to my Apple Network (where the SkyConnect is too). I imported my thread credentials for the Google network (but I leant an Android from someone to do this) in the hope that some day I could do this in HA. Can I reset all the play services details without an Android?

still quiver
spring bramble
spring bramble
full canopy
inner torrent
full canopy
twin vine
#

make sure your nest deivces were on public preview (fuchia 16......)

#

factory reset all of them

#

and unplug them all once they are reset

#

then turn one on at a time, and make sure once its set up, its joins the apple/skyconnect network

#

then turn the other onces on and repat

#

thats a perk of thread 1.3

#

worked for me

full canopy
twin vine
#

i dont think so? i dont have any tho

full canopy
#

I will try againโ€ฆ

twin vine
#

make sure only one is powered on at once as you factory reset them

#

well, factory reset them all, but once they are ready to active/set, turn them all off but one

full canopy
#

Mine are on Fuchsia 14.2xx

twin vine
#

yeah, go onto the preview firmware if you can

#

after joining the program, you may need to reboot your devices a few times

#

i should work on fuchisia 14.2 tho

full canopy
#

Nope, came back again under a nest network

#

Which device did you do first?

#

Iโ€™m trying on a max, maybe I should go try a mini

twin vine
#

i had 1 nest hub max, and a nest hub 2nd gen

#

factory reset both, turned off then gen 2, set up the max, confirmed it was on the myhomexx network (made by apple), then set up the gen 2 hub

full canopy
#

Nope, no luck on the mini either

#

Maybe I should just nuke my whole Google Home

twin vine
#

you factory reset them all at the same time?

#

and made sure nothing as broadcasting any nest thread channel stuff?

full canopy
#

Yup, I donโ€™t have anything else

#

Unplugged the GoogleTV too now just in case

#

Nope, nuked the entire Google Home, still coming back under the NEST network

twin vine
#

Strange, try enrolling all of your devices in the device program preview, it will update most of them and see if that works

still quiver
still quiver
#

Also, on boot up from that system crash, that same thread device gave an error like unable to serialize with keyword "matter"

full canopy
#

I already was in the preview program

#

I decided to just give up, and added all of them back

#

And when I checked again, they were in the Apple network ๐ŸŽ‰

#

Which is weird, since when I first checked, they made a new NEST network

#

But apparently, they felt bad for me and decided to move over ๐Ÿ™ƒ

sick swan
full canopy
#

Does anyone have any advice on a border router (other than Apple or Google devices). I was just looking for something simple and out of the way.

Something like this maybe?

https://www.gl-inet.com/products/gl-s20/

steady forge
#

has anyone tried the new ot-rcp-2.4.1 firmware for ZBDongle-E yet?

spice imp
#

Im not sure if it still works though.

#

Nvm, i can see you fixed it

night moth
full canopy
#

Ah, can of worms these Google Nest devices. My network has gone dodgey since I added them to the same Thread Network as my other devices.

full canopy
#

Anyone know what this means?

otbr-agent[183]: 2d.05:19:39.742 [N] Mle-----------: Different partition (peer:1993145260, local:1976230236)
otbr-agent[183]: 2d.05:19:39.742 [W] Mle-----------: Failed to process Advertisement: LinkMarginLow
otbr-agent[183]: 2d.05:20:13.357 [N] Mle-----------: Different partition (peer:1993145260, local:1976230236)
otbr-agent[183]: 2d.05:20:13.357 [W] Mle-----------: Failed to process Advertisement: LinkMarginLow
otbr-agent[183]: 2d.05:20:48.240 [N] Mle-----------: Different partition (peer:1993145260, local:1976230236)

vapid shell
#

Partitioning means your mesh has split into isolated sub meshes

#

Google doesnโ€™t have TREL (Apple and SkyConnect do) which can mitigate weak meshes by tunnelling thread over WiFi and Ethernet

#

You need more router capable devices to make up for the gaps in your mesh

#

Or lots of HomePods

full canopy
#

Arenโ€™t all powered devices routers?

#

I figured that the Nest devices were filling the gaps

toxic vector
#

Whether a device is a router or not is purely a firmware decision on the device, this also happens to apply for zigbee and zwave too

#

I have here a matter over thread device running off of a battery yet routing, and a mains based zigbee device which is not

#

also zigbee and thread are both 2.4ghz ISM so their range can be quite short, and theyre both susceptible to interference

full canopy
#

In a sick twist of fate, my NEST network came back to life, and my Apple devices all moved into that network, including my SkyConnect, and now all my devices are slowly moving into it as wellโ€ฆ