wind nexus
Good afternoon,
I have a thread network running using ZBT-1 with nanoleaf devices connected in the nanoleaf app to the thread network.
When I go to scan the matter code, it says "connecting to [WIFI SSID] and fails. It shouldn't be trying to connect to wifi as it's a matter over thread bulb. Does anyone know what to do?
solar valve
you phone has to connect to the wifi on an ssid which is in the same network segment as the thread border router in order for part of the matter commissioning flow to work (that's how it talks to bulbs once they're on the thread network)
additionally, on android, google play services needs an internet connection during the commissioning flow in order to fetch some device information.
wind nexus
Hey from Reddit, we will chat here.
serene wigeon
Show me screenshot of your Thread integration, please. I want to see your Thread network(s).
wind nexus
Not home ATM but I will send it when I get home.
serene wigeon
Ok, let’s go on, when you are at home.
But remember… I am from Germany. It’s late here and tomorrow is Christmas. 😂
and I am not an Android user…
What network equipment is in use?
serene wigeon
Ok, that looks good. Your two Borders are in the preferred network.
So you also have a Nanoleaf Thread Border Router (Jank). Is this Border Router also in the same VLAN as your HAOS machine and your phone?
serene wigeon
So, you have to remove it from current. There is no way to disable the Thread functionality on those Nanoleaf devices.
Maybe you want to do that for testing purposes.
serene wigeon
Are all your Matter over Thread devices you already still work?
serene wigeon
No, on your OTBR Thread.
serene wigeon
Your Nanoleaf Shapes TBR and your OTBR share the same network credentials. Both TBRs are shown under your preferred Thread network. So, the bulb you have already paired should still work.
wanton plume
This is the error log when trying to connect to matter.
serene wigeon
Do you have any bulbs paired paired to HA or are they paired to the Nanoleaf app only?
wanton plume
nanoleaf app
serene wigeon
Sorry, I didn’t recognize that you are not OP. What are doing here? 😂
serene wigeon
Ah ok…
Did you try to reset one of your bulbs (switch the bulb off and on 5 times until it flashes red) and pair the bulb to HA directly? The commissioning window closes after some minutes.
wind nexus
Doing that would remove it from the app though?
serene wigeon
Upload your log files to dpaste, please:
wind nexus
serene wigeon
Doing that would remove it from the app though?
wind nexus
I'll do those exact steps
serene wigeon
https://dpaste.org/Tg8tA
I never saw that message. Don’t know what that means:
SRV record already actively processed
But you have to solve that.
wind nexus
Idk what that means?
wanton plume
should I disable TP-link and see if that fixes it?>
serene wigeon
Maybe remove all your devices from current and check your logs again. When your Matter server got quiet, you can try to pair your MoT bulbs again by the procedure I described above.
wanton plume
disabled TP-Link, will try again
serene wigeon
You need to find the source for this message.
serene wigeon
disabled TP-Link, will try again
Is your log quiet now?
wanton plume
when trying to connect the matter bulb, it still says SRV record already actively processed
serene wigeon
Did you disable your TP-Link devices?
wind nexus
Yes
serene wigeon
You removed them from current?
wind nexus
Everything is removed.
serene wigeon
And your Matter server logfile is quiet? But when you try to pair a factory resetted bulb to HA you get those SRV record messages?
Or do you see the SRV messages in your log non-stop?
wind nexus
Yes I still get those errors.
wind nexus
Nope!
serene wigeon
Ok, do you have any Matter device paired to HA?
If not, delete your Matter server completely including the addon and not only the Matter integration and start fresh.
serene wigeon
After you reinstalled your Matter server, it should be quiet.
wind nexus
Restarting home assistant to and giving it an honest try.
serene wigeon
When your log is quiet, try to reset and re-pair one of your MoT Nanoleaf bulbs.
wind nexus
Ok
Before I even try to connect the light bulb I get a bunch of logs. I'll send it in dpaste
wanton plume
serene wigeon
I don’t know. Can you disable the wrong interface via command line? Which one is right/wrong, WiFi or Ethernet?
Did you enable IPv6 on HAOS?
wind nexus
Ipv6 is configured
serene wigeon
Ok, is your HAOS connected via WiFi or Ethernet?
wind nexus
Wifi
serene wigeon
Can you connect your HAOS via Ethernet, disable your WiFi connection and check it again?
However…. IMO you need to find the source for the SRV record messages. There is something wrong.
wind nexus
I'm going to have to put this on hold again. Thank you for trying to assist but this is insanity.
serene wigeon
It’s late here. Maybe anybody else can help you. I need to go to sleep. Merry Christmas! 🎅🏻🎄🎁
wind nexus
Merry Christmas!
wanton plume
Thanks for your help Hoppel!
I think its working now. I had to uncheck the internal interface from this configuration:
Still see the network unreachable error and SRV errors but it seems to be working anyway
serene wigeon
Thanks for your help Hoppel!
I think its working now. I had to uncheck the inte...
I didn’t know that you can configure this via HA web interface. Great! 👍
serene wigeon
Still see the network unreachable error and SRV errors but it seems to be workin...
Maybe ask in the HA community thread or in the GitHub issue I posted above, if anybody found a solution or has an idea, where this SRV errors could have its source.
serene wigeon
@slender flare Is choosing the wrong network interface something you can prevent? Do you have any idea, where the following message has its source?
SRV record already actively processed
slender flare
<@461603794090852353> Is choosing the wrong network interface something you can ...
It's not very common to have the HA server on WiFi and honestly I really cant recommend that, especially not if you are going to be using TREL with multiple border routers. In general there is only one interface and for those exception cases where there are multiple, we have this setting. So the way to prevent it: select the correct interface.
As for "SRV record already actively processed" or another MDNS error spamming the log. That is caused by a (rogue) mdns forwarder, sending a flood of malformed mdns packets on the network Such as the "Multicast DNS" option in Unifi equipment but I jave also seen an add-on doing this. I believe it was the "AirCast" add-on spamming the network.
serene wigeon
@slender flare Ok, thanks for the explanation. Didn’t know about this setting. Yes, WiFi only for the HA server may not be the best choice. 😃 Merry Christmas. 🎄🎁
@wanton plume Do you have any mDNS forwarder enabled? What about the AirCast addon? Do you have it installed?
wanton plume
No aircast. I have an Asus router. I searched for mDNS config on it and looked on Google but couldn't find anything. It is on a proxmox VM which I've heard could cause issues but never found out what those issues were.
Unfortunately giving it a wifi interface was the only solution that I could use to have it on the same VLAN. The Ethernet port is shared with other VMs connected to a reverse proxy on my dmz
If it's better I connect to ha through the Ethernet. The wifi is literally setup just for the thread bulbs
slender flare
If it's better I connect to ha through the Ethernet. The wifi is literally setup...
Why not add an extra (USB) ethernet adapter then ?
wanton plume
Maybe I could, but I'm not sure. I'm realizing Asus routers have zero flexibility when it comes to their guest (IoT) network configuration settings. I'm not sure if it's going to let me put one of the interfaces on that subnet.
Is there a reason I should consider it though? Everything appears to be working now.
serene wigeon
An Ethernet interface is much more reliable than a WiFi interface.
wanton plume
That's ok. Most connections are being routed to the backend through the reverse proxy like the dashboard and such. If I notice any stability issues on things connecting to the wifi interface maybe I'll look for something better on that side of things.
I am still a bit confused though, it seems like my thread bulbs require me to have an interface on the subnet where my other thread border is on? Do the borders connect via IPv6 on the subnet, and then zbt-1 is just for the bulbs themselves?
solar valve
traffic from the bulbs to the lan can end up using either thread border router if you have multiple
so all of them have to be able to talk to HA
lost ruin
I've been fighting with this bulbs for sometime last week, so AMA.
Pretty much the same setup. Main pain in the ass is Nanoleaf app itself. Once bulbs are on Matter, you're good.
I've got 42 of them, so you can imagine 😄
tame spade
I've got 42 of them, so you can imagine 😄
That's a lot
lost ruin
That's a lot
Fingers crossed Thread is reliable 😄
wind nexus
@lost ruin have u figured out how to add scenes into home assistant?
Or a work around 🤷
lost ruin
<@118031559348453381> have u figured out how to add scenes into home assistant?
I think that's impossible, unless they expose API of some sort.
wind nexus
😭
Some reason it's avaliable on Nanoleaf integration but not on matter Nanoleaf integration
Idk if this is a matter issue, Nanoleaf or home assistant.
slender flare
Scenes are not exposed though Matter although we are working together with Nanoleeaf to see if we can change that.
wind nexus
Scenes are not exposed though Matter although we are working together with Nanol...
I really appreciate your reply! I look forward to this!
