Nanoleaf Matter via Thread bulb fails to add | Home Assistant | Page 1

rich plinth Feb 15, 2024, 7:23 PM

#

I'm using a OTBR with a CC2652P and custom firmware flashed.

#

this is how my otbr starts:

s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
s6-rc: info: service otbr-agent-configure: starting
Done
s6-rc: info: service otbr-agent-configure successfully started
[20:17:50] INFO: Successfully sent discovery information to Home Assistant.
```

#

this is the error i get when i try to add the device:

otbr-agent[177]: 00:00:27.097 [N] Mle-----------: RLOC16 8000 -> fffe
otbr-agent[177]: 00:00:27.628 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[177]: 00:00:34.128 [N] RouterTable---: Allocate router id 32
otbr-agent[177]: 00:00:34.128 [N] Mle-----------: RLOC16 fffe -> 8000
otbr-agent[177]: 00:00:34.131 [N] Mle-----------: Role detached -> leader
otbr-agent[177]: 00:00:34.131 [N] Mle-----------: Partition ID 0xb00fe76
ipset v7.10: The set with the given name does not exist
otbr-agent[177]: 00:00:34.145 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[177]: 00:00:34.159 [W] Platform------: [netif] ADD [U] fde1:a347:bbfe:6ee3:0:ff:fe00:8000 failed (InvalidArgs)
otbr-agent[177]: 00:00:34.159 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:34.161 [W] Platform------: [netif] ADD [U] fde1:a347:bbfe:6ee3:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[177]: 00:00:34.161 [W] Platform------: [netif] Failed to process event, error:InvalidArgs

#

ipset v7.10: The set with the given name does not exist
otbr-agent[177]: 00:00:34.465 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[177]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[177]: 00:00:34.482 [W] Platform------: [netif] ADD [U] fde1:a347:bbfe:6ee3:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[177]: 00:00:34.482 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:34.484 [W] Platform------: [netif] ADD [U] fde1:a347:bbfe:6ee3:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[177]: 00:00:34.484 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.10: The set with the given name does not exist
otbr-agent[177]: 00:00:35.543 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[177]: 00:00:37.615 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[177]: 00:00:37.641 [W] Platform------: [netif] ADD [U] fd86:6fe2:c63a:1:4df0:761:a4c8:6bfd failed (InvalidArgs)
otbr-agent[177]: 00:00:37.641 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.10: The set with the given name does not exist
otbr-agent[177]: 00:00:43.752 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[177]: 00:00:43.752 [W] Platform------: [netif] ADD [U] fde1:a347:bbfe:6ee3:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[177]: 00:00:43.752 [W] Platform------: [netif] Failed to process event, error:InvalidArgs

rich plinth Feb 16, 2024, 8:55 AM

#

Any idea why this is failing? Android and iphone app say there is no border router on the network.

#

I have the otbr installed via the otbr integration on HA-OS

rich plinth Feb 20, 2024, 3:47 PM

#

I have since gottan a sonoff dongle with silabs chipset to rule out it's my selfmade TI dongle, and it's quite the same result but with different log messages. It seems there's no problems in the log, but both android and ios companion apps report that I need a thread border router

#

I have checked the configuration of Thread, Thread border router and Matter integration, and everything seems fine to my naked eye. What could I do to troubleshoot this?

rich plinth Feb 20, 2024, 4:21 PM

#

Ahhhhh, I just found this, I did not do this

To share the credentials with your Android phone, open the Home Assistant Companion app.

In the Companion app, go to Settings > Companion app > Troubleshooting, then select Sync Thread credentials.

#

Unfortunately in the meanwhile, I decided it's a smart idea to uninstall all matter and thread integrations and add ons and start with a fresh configuration, and now the otbr integration throws errors it didn't throw before, and the android companion cannot find the device anymore, which it did before

#

[17:13:09] INFO: Starting otbr-agent...
otbr-agent[177]: [NOTE]-AGENT---: Running 0.3.0-9bdaa91-dirty
otbr-agent[177]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[177]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[177]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM3?uart-baudrate=460800
otbr-agent[177]: [NOTE]-AGENT---: Radio URL: trel://enp0s25
otbr-agent[177]: [NOTE]-ILS-----: Infra link selected: enp0s25
otbr-agent[177]: 00:00:00.020 [N] RoutingManager: BR ULA prefix: fd06:c4c7:9f3d::/48 (loaded)
otbr-agent[177]: 00:00:00.020 [N] RoutingManager: Local on-link prefix: fd86:4721:d3c1:786c::/64
otbr-agent[177]: 00:00:00.062 [N] Mle-----------: Role disabled -> detached
otbr-agent[177]: 00:00:00.089 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[177]: 00:00:00.104 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[177]: 00:00:00.104 [W] Platform------: [netif] ADD [U] fe80:0:0:0:44d:1e73:e6f5:20bc failed (InvalidArgs)
otbr-agent[177]: 00:00:00.104 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:00.104 [W] Platform------: [netif] ADD [U] fde1:a347:bbfe:6ee3:5e78:ae37:5d87:5be failed (InvalidArgs)
otbr-agent[177]: 00:00:00.104 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:00.104 [W] Platform------: [netif] ADD [U] fde1:a347:bbfe:6ee3:0:ff:fe00:7400 failed (InvalidArgs)
otbr-agent[177]: 00:00:00.104 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:00.105 [W] Platform------: [netif] Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
s6-rc: info: service otbr-agent-configure: starting
Done
s6-rc: info: service otbr-agent-configure successfully started

rich plinth Feb 20, 2024, 4:39 PM

#

@prime mesa main issue right now is why I suddenly have these warnings in my otbr integrations after reinstalling and the bulb not being found at all in the companion app

prime mesa Feb 20, 2024, 4:40 PM

#

It’s most likely a network problem

#

Is it a vm?

rich plinth Feb 20, 2024, 4:40 PM

#

HA-OS add on

prime mesa Feb 20, 2024, 4:40 PM

#

HAOS itself

#

Some people have seen their hypervisor drop IPv6 router advertisements

#

Fiddling with promiscuous mode has helped them, has has going bare metal. I’ve never seen a satisfying root cause for that subset of people,

rich plinth Feb 20, 2024, 4:44 PM

#

?

#

it's been working before I reinstalled everything

prime mesa Feb 20, 2024, 4:45 PM

#

I thought it never worked and then you broke it more by reinstalling

rich plinth Feb 20, 2024, 4:45 PM

#

the otbr was staring fine and it would find the bulb, but it would fail adding the bulb claiming there's no otbr.

#

now it wouldnt even find the bulb

prime mesa Feb 20, 2024, 4:45 PM

#

Right

#

Then what I’m saying is correct

#

The initial discovery is by your phones Bluetooth

#

Bluetooth is used to upload the thread credentials

#

If your phone has never seen your OTBR we need to check what I’m saying

rich plinth Feb 20, 2024, 4:47 PM

#

prime mesa Fiddling with promiscuous mode has helped them, has has going bare metal. I’ve n...

if you mean this, then I have no clue what you are saying 😅

prime mesa Feb 20, 2024, 4:47 PM

#

have you checked the mdns service _meshcop._udp is visible from your phone

rich plinth Feb 20, 2024, 4:47 PM

#

no

prime mesa Feb 20, 2024, 4:47 PM

#

Do you know how to do that? Unfortunately I’m iOS so I can’t suggest an app

rich plinth Feb 20, 2024, 4:48 PM

#

i am ios as well but I have an android dashboard tablet that does exactly that: be a cheap homeassistant dashboard

#

that's the device i use to commission the nanoleaf bulb

prime mesa Feb 20, 2024, 4:48 PM

#

And it can’t see your otbr right?

#

so checking it can see the meshcop service is step 1

rich plinth Feb 20, 2024, 4:51 PM

#

prime mesa And it can’t see your otbr right?

well, if I sync thread credentials in the android app there's no error message ...

prime mesa Feb 20, 2024, 4:52 PM

#

Ok but that’s a different set of things

#

I probably need more time to explain things that I have and probably a bigger keyboard so I’ll try and come back later if I have time

rich plinth Feb 20, 2024, 4:53 PM

#

prime mesa I probably need more time to explain things that I have and probably a bigger ke...

thanks!

#

I'm trying to google the meshcop service, but I don't really know what I'm looking for

prime mesa Feb 20, 2024, 4:54 PM

#

Search the google App Store for a zeroconf or mdns browser

rich plinth Feb 20, 2024, 4:55 PM

#

sheesh, ofc, downloading mdns discovery

#

it's a bit nuts what lengths to walk when all I want to do is get started with matter via thread. I'm amazed how far this is from easy

prime mesa Feb 20, 2024, 4:55 PM

#

It will show you zeroconf services like _matter._tcp or _hap._tcp, and hopefully _meshcop._udp

#

Using a dongle is the hard mode

#

I went with HomePods at home

#

The hard bits were where I over engineered my network

rich plinth Feb 20, 2024, 4:56 PM

#

prime mesa I went with HomePods at home

i have no use for homepods and the price difference is 🤯

rich plinth Feb 20, 2024, 4:58 PM

#

prime mesa Using a dongle is the hard mode

and with all due respect, all of this stuff is from within ha-os, it should all be known good stuff ...

#

no fancy network config or anything

gusty gazelle Feb 20, 2024, 5:21 PM

#

Did you ever import your thread credentials on your phone?

#

Also I found the nanoleaf bulb stops pairing after about 5-10 minutes, might need to power cycle it if you've been going at this all day

limpid vale Feb 20, 2024, 5:24 PM

#

Do you have other Thread/Matter things to test, or only Nanoleaf? Are the Nanoleaf’s on the beta firmware?

winter moon Feb 20, 2024, 5:32 PM

#

rich plinth it's a bit nuts what lengths to walk when all I want to do is get started with m...

You're using a dongle with a custom firmware, which is far from supported, what do you expect?

prime mesa Feb 20, 2024, 5:45 PM

#

gusty gazelle Did you ever import your thread credentials on your phone?

They did. But that was definitely on my list to check. Might well have to reset google play services on their device now they nuked the first otbr 🤔

rich plinth Feb 20, 2024, 6:00 PM

#

winter moon You're using a dongle with a custom firmware, which is far from supported, what ...

the custom firmware is essentially the rcp from the SDK with the pins adjusted. I'd not consider that very custom tbh

rich plinth Feb 20, 2024, 6:01 PM

#

limpid vale Do you have other Thread/Matter things to test, or only Nanoleaf? Are the Nanole...

I just ordered the nanoleaf bulbs, I'd not expect them to be on beta firmware, but what do I know? I do have some eve plugs with matter over thread that I bougth a year ago but never got to work 😅

winter moon Feb 20, 2024, 6:06 PM

#

What was the result of the mDNS browser?

#

Did it find meshcop?

limpid vale Feb 20, 2024, 6:09 PM

#

Oh, well the NL bulbs are a pain to pair to HA in general…. They work a lot better on the beta firmware, you can sign up at https://forum.nanoleaf.me/forum then go to My Account —> My Devices

There should be another update this week (hopefully) which will update them to a newer sdk with matter 1.2, which will in turn hopefully fix more things.

You can sign up per bulb. Afterwards, just open the app and it should see the update.

#

On the “normal” firmware with Apple HomePods, it often took 20-30 tries per bulb to pair, some just didn’t work at all.

On the beta firmware, they worked all first time for me.

#

FYI if you can factory reset the Eve plugs and add them, they do work really well.

I also had issues with them like a year ago, but they work great now.

rich plinth Feb 20, 2024, 6:24 PM

#

limpid vale On the “normal” firmware with Apple HomePods, it often took 20-30 tries per bulb...

Check thanks for the info!

rich plinth Feb 20, 2024, 6:24 PM

#

winter moon Did it find meshcop?

I‘ll check when i‘m back on the computer

rich plinth Feb 20, 2024, 9:19 PM

#

yes _meshcop._udp. is available

#

on macos that is at least, but same network, so I'd be surprised if it wasnt available on the android tablet

#

and indeed it seems the bulb just stopped being in pair-mode after some time, it's now back and progressing

#Nanoleaf Matter via Thread bulb fails to add