#thread-archived

1 messages ยท Page 10 of 1

spice imp
#

your thread credentials are not set

#

have you added them under home asssistant?

#

the three dots in the top right corner

tribal knoll
#

does thread not auto configure those creds?

spice imp
#

and there should be some options with default thread network and so on

sick swan
#

The thread credentials in our Matter add-on are only necessasry when we do onboarding from our Matter Server directly. But that is not exposed the user interface currenlty.

tribal knoll
#

So when i click configure on the thread ad-on

#

i see Prefered network > Home-assistant, Other networks => OpenThread-c9d1 => 1 border router

#

when i click the 3 dots in the corner, i see download diagnostics, add dataset from TLV, add an openthread border router

#

thats it

spice imp
sick swan
#

So, the way Matter comissioning works with Google (roughtly)

  1. Your phone connects via Bluetooth to the device
  2. encrypted PASE session is established (using QR code/pin)
  3. Your Google phone sets up the Thread network on your device (presumably, in your case, the Thread network information have previously been shared via Home Assistant Thread credentials sharing)
  4. Your Google phone adds your device to a temporary Matter fabric
  5. Your Google phone tires to communicate with your device through Thread to establish a CASE session
  6. Your Google phone shares the device with Home Assistant
#

I guess step 5 fails in your case. The Matter server is not in the picture at that point.

spice imp
tribal knoll
#

i think its failing to set up the thread network on my phone

spice imp
#

Aren't there also still some problems with changing the credentials after they have been synced once?

sick swan
#

That kinda/sorta sounds like the Thread device can't connect on a Thread network level? ๐Ÿค” Thread credentials missmatch? ๐Ÿค”

tribal knoll
#

posibly

sick swan
#

The thing is with the Google Play store Thread network API's is that once a preferred network is configured you can't really change it on your phone. So maybe credentials from an earlier attempt are stored? On your phone, when you go to Settings > Companion app > Troubleshooting > Sync Thread credentials, what is it saying?

spice imp
tribal knoll
#

oh wait it said updated now

sick swan
#

Your phone named it right in the error no? So sounds as if the phone does try to add your Thread device to a Thread network with the name "glacier-thread"

sick swan
#

Try again, it says updated again, correct?

tribal knoll
#

trying

#

yeah it said updated thread network

sick swan
#

this is what you should see.

tribal knoll
#

wait you can send images?

#

that isnt what i see

#

mind if i send you a screenshot?

sick swan
#

I don't mind. But yeah I know the problem ๐Ÿ˜ข

tribal knoll
#

whats the problem?

sick swan
sick swan
#

I tried to find references to Google sample code, but couldn't. In short, the problem is that changing the Thread credentials don't work.

#

What you can do is sestting the one you uses on your phone as preferred in Home Assistant (double check until you get that "uses the same network" above)

#

If you don't have thoses credentials (anymore) or somehow the compare just won't work, you can reset your phone, but it has side effects.

tribal knoll
sick swan
#

The Thread network credentials are stored as part of "Google Play Services"

tribal knoll
#

bruh

#

so factory then

sick swan
#

Not it is possible to delete data specificlaly. Go to Apps > All Apps

#

Find "Google Play services" > Storage & cache > then select "Clear storage"

#

It will clear out things like your credit cards in your wallet

#

(I discovered that once next day standing at the checkout in a store ๐Ÿ™ˆ )

tribal knoll
#

that shoule be fine

#

all of my banks support wallet integration its easy to reconnect them

sick swan
#

I think I also had to uninstall and reinstall Home Assistant App when I tried it back then. YMMV

#

Just make sure before you sync the first time, that the correct Thread crednetials are set as preferred on Core side ๐Ÿ˜„

tribal knoll
tribal knoll
#

thankyou @sick swan problem resolved. google play was caching a previous version of the thread credentials.

#

now to figure out why my nanoleaf bulb dosent like my thread network

#

:grumble:

spice imp
#

just try a few times

tribal knoll
spice imp
tribal knoll
#

who does that handgesture

spice imp
tribal knoll
#

interesting

tribal knoll
#

power cycled it and it dosent want to work

#

as in connection mode power cycle

#

5 on /off cycles in 3 seconds each

#

flashed red

sick swan
tribal knoll
#

yeah thats whay i did

sick swan
#

Oh says non-Matter there ๐Ÿ™ˆ

#

I mean, do you get a pop-up on your phone?

tribal knoll
#

yeah

#

wont go away

sick swan
#

That isually indicates that the device is ready and in pairing mode

#

as in, advertises via BLE

tribal knoll
#

yup, i get the notification that the device wants to pair

#

it asks to scan the qr code, i scan it and it blazes through the whole process

#

just to show cant connet to your device

#

check your device instructions

sick swan
#

So the error you had before was earlier?

tribal knoll
#

no, different this time

#

the last image i sent you in dms

sick swan
#

I mean the one even earlier

#

about not beeing able to connect to Thread network. That one was earlier right? So it seems to connect to the Thread network now?

tribal knoll
#

yeah, it seems to connect, but then something happens it it just falls over

sick swan
#

You can check on the OTBR if the device appears (using ot-ctl child list)

tribal knoll
#

empty list

#

nothing there

sick swan
sick swan
# tribal knoll empty list

I guess the device goes back to pairing state... You have to check continously during commissioning if it appears (and then disappears again)

tribal knoll
#

ok

#

just double checking, these sysctl changes need to be made to the border router?

# 
net.ipv6.conf.ens18.accept_ra_rt_info_max_plen=64
net.ipv6.conf.all.forwarding=0```
#

i added these 3 lines

#

the network interface for the lan side is indeed ens18, i doublechecked

sick swan
#

๐Ÿค”

#

I think its for the "other side" (so the device which want to communicate through Thread.

#

Any case, it shouldn't hurt.

tribal knoll
#

yeah it still didnt work

sick swan
#

I think what I would try here is shutdown your OTBR, and install the OpenThread Border Router add-on. This really should work. Since you have the credentials in the store, it should be straight forward to configure the Add-on OTBR with the same credentials.

tribal knoll
#

ok, how can i back up the creds so i dont have to do the whole google play dance again

tribal knoll
#

@sick swan if you have a second

sick swan
#

They are in the HA Thread storage now

tribal knoll
#

ah ok

#

so shut down the current otbr vm, then how am i attaching my coprocessor to ha? just plug it in and hope home assistant recognises it?

sick swan
#

It won't autodetect

#

You'll have to install the "OpenThread Border Router" add-on from the add-on store and configure to use the serial port your nRF dongle is exposing (I think /dev/ttyACM0 by default)

tribal knoll
#

instead of a url to an api like i have right now?

sick swan
#

The integration should get autodetected when you sstart the add-on

#

But you'll have to deletee the one you have now

tribal knoll
#

ok

sick swan
#

Only a single instance is allowed

#

(currently)

tribal knoll
sick swan
#

HACS is not needed

tribal knoll
#

i dont see any openthread addon

#

found the repo

#

but it isnt showing up in my home assistant instance

#

found it, had to enable advanced mode

tribal knoll
#

how can i access the HAOS bash console?

sick swan
quick bronze
#

Do note the warning there though ๐Ÿ˜‰

tribal knoll
#

mine dosent seem to be exposed over 22222

#

i get no route to host

sick swan
#

No route to host? How do you access the web interface then?

tribal knoll
#

sorry, i meant connectoin refused

#

not no route to host

sick swan
#

did you setup the ssh keys as documented?

tribal knoll
#

yeah

#

but its not important right now

#

ok

#

otbr addon has been started

#

logs look good

#

thread has picked up the openthread border router hass plugin too

#

still no dice

sick swan
#

Same error? On the phone?

tribal knoll
patent nymph
#

Hi all.

#

I have an issue with setting up thread

#

everything seems to be ok, but when I try to add a device I get can't connect to thread network home-assistant.

#

I am using usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230830091610-if00 as a device with Openthread RCP flashed on it.

meager galleon
#

That's pretty similar to what LiteLotus was just looking at. should read up the past couple days of chat here

patent nymph
#

the strange thing is today I've set it up just fine on HA yellow

#

now I'm trying on my other HA instance ...

tribal knoll
#

for me that issue ended up being the credentials saved in the comissioning device were incorrect, if your bridge hasnt changed and/or you havent set up your thread network again since, it might not be that

#

but the conversation chain above will at least give you some places to look

#

im still having no luck with my device

#

im tempted to throw in the towel for now and take a break

patent nymph
#

It is completely another thread network

#

the device worked fine with HA Yellow

tribal knoll
#

yeah then your credentials will be incorrect

meager galleon
#

But same phone to commission with?

patent nymph
#

I've reset the device

#

yep same phone

#

can it be the phone ?

tribal knoll
#

youll need to reset you google play services

tribal knoll
patent nymph
#

it is connected to another HA instance now

tribal knoll
#

yeah

#

the credentials get stored on the device for commisioning

#

when the thread network changes, the credentials dont

#

causing a mismatch

patent nymph
#

even though it is completely different HA instance ?

tribal knoll
#

yup

patent nymph
#

just a second I will reset now

#

only Google Play services ?

tribal knoll
#

just be aware, resetting google play services causes other things to become invalid, like google wallet cards

#

and some bank apps

patent nymph
#

I can try from an iphone?

tribal knoll
#

but yeah, clear both the cache and storage from your device

tribal knoll
#

as long as that iphone hasnt been used to commision thread devices

patent nymph
#

it was not

tribal knoll
#

then gove it a go

meager galleon
#

does iphone have support for that?

tribal knoll
#

yeah

patent nymph
#

trying now

tribal knoll
#

uses homekit over thread, so i would assume it would be able to use matter

patent nymph
#

well iphone says TBR required ...

#

๐Ÿ˜„

#

it does not detect it at all

tribal knoll
#

yeah if it dosent detect the border router, your out of luck

patent nymph
#

trying to clear GPS

#

now it says Matter is currently unavailable

#

should I reboot the phone ?

tribal knoll
#

reboot it or give it a while

#

thread is stored in GPS if what i understand is correct

#

so it will need a sec to rebuild / replace it

patent nymph
#

what if it gets it from the cloud with the old creds?

tribal knoll
#

as long as that old border router dosent exist anymore, neither do the creds

patent nymph
#

it exists, but it is turned off

#

atm

tribal knoll
#

then there are no creds to grab

patent nymph
#

waiting for it to reboot or be available again ..

tribal knoll
#

you'll also want to sync your HA thread network again

patent nymph
#

how ?

tribal knoll
#

go into settings > companion app > troubleshooting> sync thread

#

in the home assistant app on android

patent nymph
#

lets see

#

it seems to hand at the same place

#

otbr-agent[176]: 00:00:32.731 [W] Platform------: [netif] Failed to process request#6: File exists

#

otbr-agent[176]: 00:00:25.571 [W] Platform------: [netif] Failed to process request#5: Operation not supported

#

is this normal ?

tribal knoll
#

no clue, thats a question for someon with more knowledge than myself

patent nymph
#

now it gave a different error

#

cannot reach device

#

๐Ÿ™‚

patent nymph
#

one more thing

#

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::e859:52ff:feb4:8de5/veth18db442/35

#

is this normal ?

#

I think it is related as thread needs ipv6

patent nymph
#

managed to do it

#

comissioned directly from HA

#

follow this guide with the websocket stuff

#

basically this is what you need

#

and it wors

patent nymph
#

this is the 1st one you need

#

var socket = new WebSocket("ws://192.168.30.128:5580/ws");
socket.addEventListener("message", (eventa) => {
console.log("Message from server ", event.data);
});

socket.addEventListener("open", (event) => {
console.log("WebSocket is open");
var message = {
"message_id": "1",
"command": "set_thread_dataset",
"args": {
"dataset": "0e080000000000020000000300001435060004001fffe00208cbde9f033aa599b30708fd2ddd645495f0b2051007993e3ad39a91be7b2ebd7594af046a030e686f6d652d617373697374616e740102b1830410b3961d49319d749942263146b2d6aba30c0402a0f7f8"
}
};
socket.send(JSON.stringify(message));
});

#

replace dataset with yours

#

and also address

#

var socket = new WebSocket("ws://192.168.30.128:5580/ws");
socket.addEventListener("message", (eventa) => {
console.log("Message from server ", event.data);
});

socket.addEventListener("open", (event) => {
console.log("WebSocket is open");
var message = {
"message_id": "2",
"command": "commission_with_code",
"args": {
"code": "1261-990-9698"
}
};
socket.send(JSON.stringify(message));
});

#

here you replace address and code with pairing code of the device

serene prawnBOT
#

@patent nymph Please use a code share site to share code or logs, for example:

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

quick bronze
#

(rather than flooding the channel ๐Ÿ˜‰ )

patent nymph
#

@tribal knoll do you have more than one networks at home ?

tribal knoll
patent nymph
#

I've managed to add it with the phone also

#

just needed to be on a wifi which is in the same subnet

#

I think you're dealing with nanoloeaf essentials as well ?

tribal knoll
#

i am yeah

#

but everything is on the same subnet

patent nymph
#

did you try the websocket method ?

tribal knoll
#

not yet

#

would you mind taking me through your method

#

i know you posted the code above

#

buti dont want to make any mistakes

patent nymph
#

just replace the urls with yours

#

and the dataset

#

you can get it from the thread i button

tribal knoll
#

that url is for the thread border router?

patent nymph
#

no

#

for Matter Server

#

and for it to work you may need to enable the port in the configuration of matter server

#

also do you use multiprotocol or strictly matter ?

tribal knoll
#

just matter

#

i have no other protocols in my home

patent nymph
#

?

#

also do you enable ipv6 on the interface of HA ?

tribal knoll
#

yup and yup

patent nymph
#

because this is more importand than the sysctl thing

#

paste what you get in the browser

#

should be something like this

#

{
"fabric_id": 2,
"compressed_fabric_id": 7383086655979279088,
"schema_version": 4,
"min_supported_schema_version": 2,
"sdk_version": "2023.10.2",
"wifi_credentials_set": false,
"thread_credentials_set": false
}

tribal knoll
#

oh yeah, just use the console

#

i keep forgetting every browser is a js engine

#

if i do it in the browser console, it tries to upgrade the ws to wss

patent nymph
#

from the console

#

you should try only this

#

var socket = new WebSocket("ws://192.168.30.128:5580/ws");
socket.addEventListener("message", (eventa) => {
console.log("Message from server ", event.data);
});

#

to get any result

#

replace your url

tribal knoll
#

yeah i replaced my url, but it comes back as failed because it ends up trying to connect via wss instead of ws

patent nymph
#

blah

pliant badge
#

Hello people ๐Ÿ™‚ !
I have a request of help

From an Android phone with the home assistant companion app, I try to add the Matter device Smart Plug S4EU (Matter over Thread) from ONVIS : https://www.onvistech.com/product_details/S4EU
But I have failed to generate device credentials error

This home assistant companion app is connected to a a Home Assistant Supervised with the enabled plugins Silicon Labs Multiprotocol, Matter Server, Zigbee2MQTT, Open Thread Border Router and Thread
I have this logs for :

Do is it a problem with my device? Or with the Matter Server which is perhaps not yet ready?
Your help will be appreciated a lot

ivory dew
#

I was just going to ask the same question. The option is there in today's release to add them, but I keep getting "You don't have credentials available on your iCloud Keychain" after Error Message: Failed to retrieve all active boarder router records.

bronze fog
#

I have a Skyconnect...just want thread not zigbee. How do I flash the proper thread only firmware?

spring bramble
#

@patent nymph be aware that the route you are advising here is experimental and hidden for a reason. It will require bluetooth on the HA host as well as the device to be commissioned ion close range of the bluetooth adapter. It will also break the bluetooth integration of HA. Just keep that in mind while walking this experimental route. There is a reason we have not yet exposed the websocket commands.

For now I highly encourage you to just use your Android phone for Matter device commisioning instead of hacking around your way around the websocket api.

#

@pliant badge see the Matter channel's pinned post first please, you have several red flags in your setup.

spring bramble
pliant badge
bronze fog
#

@spring bramble ok I want to try apple credential sharing, but do NOT want HA as a OTBR.

spring bramble
spring bramble
ivory dew
spring bramble
#

I have just tested it on HA 2023.12 and its indeed not working.
@old niche FYI

image.png
bronze fog
#

ya I get the credential error too

pliant badge
spring bramble
pliant badge
#

Thank's ๐Ÿ™‚

spring bramble
#

Maybe just fire up a VM with HAOS and try to reproduce the issue there ?

tribal knoll
#

thats a good point

#

how unsupported is my setup?

#

HAOS in a VM with a nordic nrf548xx dongle

#

im running OTBR as a home assistant addon now

spring bramble
#

Not supported does not mean it could potentially work. It just means we might ask you to reproduce something on the supported installs if you run into issues.

tribal knoll
#

has anyone had a "cant reach device" error?

#

says make sure that you are connected to wifi

#

this one is new

bronze fog
#

and I was all excited for Apple credential sharing....then it's broken LOL

tribal knoll
#

now im back to "cant connect to your device"

#

this time i tried doing it through the nanoleaf app, but even though it says its connected, nothing else can see it

#

dosent show up as a matter device on HA, nothing in google home

#

nada

#

just says its connected in the app

#

even though it isnt

tribal knoll
#

ngl, starting to feel like nanoleaf scammed me

inner torrent
tribal knoll
#

i would agree if i hadnt just reset it

tribal knoll
#

its clearly broadcasting

#

im going to bed, ive had enough of this

#

see you tomorrow probably

inner torrent
tribal knoll
#

ok, now im really pissed, i tried it from my GF's phone just to see if there was any difference AND THERE WAS!

#

it got so much further and then after saying "adding device to home assistant" it just hangs there and eventually says "something went wrong"

#

and prompts me to close the matter connection

#

inconsistent, lacking docs and most importantly impossible to debug. this is infuriating

old niche
old niche
meager galleon
civic cosmos
#

are we able to add skyconnect thread radio to hass yet?

spring bramble
spring bramble
# meager galleon Would be much better if there was some information about what parts worked and w...

There is information: that you need to wait. If you insist on trying this out already (while it is not yet ready) you are on your own. We keep telling everybody that the way to use Thread based Matter devices TODAY in a stable fashion is by using existing Thread border routers by Apple or Google. In the meanwhile we're working on getting HA itself working reliable in all paths to act as a fully functional BR but we're not there yet.

spring bramble
thorn elbow
#

Hi all, Iโ€™m looking to add an eve energy plug to my setup and understood that energy metering is now supported. Does anyone know how often changes are reported by the plug?

spring bramble
#

btw: this is the thread channel. use the matter channel for matter related questions

thorn elbow
#

Thanks Marcel! Wasnโ€™t sure if I should have asked here or in the matter channel (as the plug talks thread), but will use matter channel in the future. Thanks again!

spring bramble
thorn elbow
#

Learning every day ๐Ÿ˜„

patent nymph
frozen flower
spring bramble
# frozen flower Just to be sure: The only real tested route at the moment is using an external O...

Yes, that is the most stable and tested route. We're still working on using HA as OTBR but it is not yet considered stable and has a few downsides. In january we'll do a blog update about the current state and the roadmap. Still, if we even can get the thread radio working reliable within the HA server, a thread border router in the neighbourhood of your devices (like a nest hub or homepod) is always going to perform better, especially if you have multiple of them.

#

Do note that there is no requirement to actually add your devices to apple home or google home. We can just use the network infrastructure and only add the devices to HA (so they're not shared with google) - you just us etheir hardware for the thread access

frozen flower
spring bramble
patent nymph
#

@spring bramble what is the most compatible/reliable hub for thread/matter ?

tribal knoll
twin vine
#

that is if you have ios

tribal knoll
patent nymph
#

which apple deivce ? Home Pod ?

twin vine
#

Homepod mini is the most reliable in my experience

patent nymph
#

so the mini supports thread/matter ?

twin vine
#

ya

spring bramble
spring bramble
patent nymph
#

I have a Home Pod 2023 model (not mini) laying around does it also work ?

twin vine
#

ya

spring bramble
twin vine
#

all currently on market homepods support thread, and therefore are a matterhub

patent nymph
#

ookay so it's just a matter of finding it ๐Ÿ˜„

#

@spring bramble HP2 yes

spring bramble
#

The Google Nest Wifi Pro also had thread bodrer router builtin which is interesting

#

Also Samsung is releasing products with the BR builtin such as their latest TV and soundbar

#

In a few years you have BR's spread over your house and have a super redundant thread network. If only all these vendors could inter operate so instead of 999 thread networks they form one

patent nymph
#

yeah that is stupid ...

#

maybe at some point they will ...

#

who knows

tribal knoll
patent nymph
#

the reason I went the HA route was that I have full control over the setup

twin vine
#

oh you will, just not yet

patent nymph
#

I have fixed all the issues I've had, so currently it is working just fine ๐Ÿ™‚

inner torrent
#

So just a word of warning for those that have NL shapes, the latest update says it improves the border router, well that's a lie. It completely destroyed my thread network (couldn't even add devices anymore). After reconstructing part of it and doing some testing, it's really causing problems routing (lots of case errors). Avoid 9.3.2 firmware, or better yet never connect it to your thread network if possible

twin vine
#

Where are the patch notes? Iโ€™m yet to see anything?

#

I have updated, but itโ€™s seems alright atm

civic cosmos
bronze fog
#

Hey thread credential sharing is still broken with the fresh 2023.488 build. It's stuck in a loop asking for home network access (which I allow, and is allowed in settings), and the 'failed to retriece all active border router records" message.

#

I have to force quit the companion app to get out of the loop

patent nymph
#

found the homepod and also found one mini

#

so how to add them to HA to be used as border router ?

spice imp
tribal knoll
#

is it really that hard to just switch from acting like a router to acting like a client?

patent nymph
#

apples threat shit is not working good as well ๐Ÿ™‚

#

when I add something it stays in no responce

#

state

spice imp
bronze fog
#

@patent nymph Apple border routers are rock solid. If you are seeing unresponsive devices then it's probably your network or faulty firmware on the device (like nano leaf).

#

I have two Apple TVs which are my border routers and Matter on HA and in the Apple Home app are rock solid. I have 20 thread/matter devices.,,

patent nymph
#

maybe

#

yeah fact that it is a nanoleaf device

#

but it does not work

#

with apple can I use home assistant to add devices or I have to go via the home app ?

tribal knoll
patent nymph
#

I was able to connect mine, but not to apple homekit

#

to HA with Sonoff stick flashed for thread only

#

and now with the Downlight it is the same

#

again nanoleaf

#

it pairs with Apple Home, but it is shown as not reachable

#

i just restored the setup with HA+OTBR+Sonoff Dongle Plus V2 and after waiting like 20-30 minutes for everything to settle I was able to add it no issues ...

#

and it works

bronze fog
#

Nano Leaf firmware is currently garbage. I don't have any NL devices, but it's widely known they suck. Beta firmware is in the works, but nonone knows when it will drop and if it will be stable.

patent nymph
#

sure it seems so

#

because it resets the light when turned off from power ๐Ÿ˜„

#

but it is working with OTBR and not working with HomePod ๐Ÿ™‚

#

i don't know the range of the homepod though

#

but the HA is further away than the homepod and still works just fine

tribal knoll
#

lol, i cant even get mine working with the otbr

patent nymph
#

something is wrong with your network

#

what is the last it is giving you as errors ?

tribal knoll
#

and then i check the matter logs and i see this

# 
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
    result = await result
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 230, in commission_on_network
    raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission on network failed for node 12023-12-07 14:06:32 core-matter-server matter_server.server.client_handler[126] ERROR [139790075868240] Error handling message: CommandMessage(message_id='4df5545060164f8bbd35872618729f9c', command='commission_on_network', args={'setup_pin_code': 74287396})
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
    result = await result
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 230, in commission_on_network
    raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission on network failed for node 1
#

2023-12-07 14:06:32 core-matter-server chip.CTL[126] ERROR Mdns discovery timed out

patent nymph
#

how far is it ?

tribal knoll
#

About a meter and a half away

#

Line of sight

#

No obstruction

patent nymph
#

strange

#

have you tried to start from scratch on the HA side ?

#

remove everything thread related and install and configure

tribal knoll
#

I havent, but I can try

patent nymph
#

try

#

I did this at least 20 times

#

until it started working properly

#

remove also matter stuff

civic cosmos
old niche
#

I updated the latest iOS beta, can someone test if you can retrieve Thread credentials now?

bronze fog
#

@old niche Test flight hasn't noticed the new version yet

old niche
#

Do you see 2023.12 (2023.488)?

bronze fog
#

yes I got that notice a couple of hours ago

old niche
bronze fog
#

as mentioned above (in the iOS channel) I'm in an endless local network access loop with .488

#

someone else echoed they see an endless loop too

old niche
bronze fog
#

it's like the companion app isn't correctly recognizing it has the local network right

old niche
#

Thatโ€™s weird, we donโ€™t directly ask for that, we use the ThreadNetwork framework to ask for credentials, so it may be a bug there. Anyway, Iโ€™ll be back when I have some news

old niche
bronze fog
#

ya allow/retry loop

#

in settings-> privacy/security the HA app has local network permission

rapid umbra
#

Iโ€™ve been out of the loop on thread development for the past few months

#

Is there a way to join a Sky connect to the apple thread network yet?

bronze fog
#

@rapid umbra well the 2023.12 iOS app has that feature...but it's currently broken

rapid umbra
#

Well at least progress is being made lol

#

Iโ€™ll check back in after the new year

bronze fog
#

BUT, it's only credential sharing. That's separate from being a border router. That's still not production ready

#

I hope @old niche is able to fix the credential sharing in short order. The code is there..just hit a snag. So maybe in the next few days it could work?

patent nymph
#

something weird just happend

#

as my thread network was working just fine suddenly it stopped

#

and now all devices are not available

#

otbr-agent[417]: 00:01:46.790 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:96, src:0x4c00, dst:0xd000, tag:57451, offset:688, dglen:1070, sec:yes

#

this started appearing in the logs

spice imp
old niche
#

Currently the API succeeds consistently on my devices, now I'm trying to find out what problem can it be that it doesn't succeed for other iCloud accounts.
I setup an iPhone 11 from scratch and I was able to successfuly retrieve credentials

#

Any volunteers to test 2023.12 (2023.490)?

plain cedar
#

Yep... .490 is working for me

#

I was able to import credentials after hitting the "Allow" prompt

old niche
#

Nice!!

#

CC: @bronze fog

bronze fog
#

I can re try later today

rare ibex
#

.490 worked here where as the previous version just looped as others reported

bronze fog
#

So with a skyconnect and credentials, not using HA OTBR , will HA talk directly to the thread network via IPv6 on the skyconnect?

old niche
#

I think skyconnect is not even needed if you already have a BR from apple but @spring bramble can confirm how it would work

patent nymph
#

testing after a minute

#

worked for me as well

#

but now what ๐Ÿ™‚

#

i changed the BR from apple to default one

#

will see now

spice imp
#

Its also working for me now on a 12 Pro with 17.1.2 and a 14 with iOS 17.2

half bluff
#

And if devices jump off the ship waiting for there life vests

spice imp
#

And I have been running this for I think over a month now

#

Without problems

half bluff
#

Has the google ever been first on that list when you check?

patent nymph
#

yep I've managed to add a device to HA without OTBR via the iphone HA app

patent nymph
#

it seems to work great, don't know why the HomeKit app does not work with this lights but HA works just fine

spice imp
half bluff
tribal knoll
#

ok

#

uninstalled all the addons, and deleted the services

#

im gonna go for a from scratch reinstall

#

see if i can get this working

#

Installing OpenThread Border Router. configurations are set to /dev/serial/by-id/usb-Nordic_Semiconductor_nRF528xx_OpenThread_Device_F498ED3EBA87-if00 for the device, Baudrate set to 115200. log is set to debug.
Harware flow control, and firewall are enabled, autoflashing is disabled.

#

thread and matter integrations got autodetected immediately, enabling them.

#

matter integration auto installed the matter addon.

#

(resetting GPS while i wait for those to install)

#

Matter integration errored during setup. Invalid flow specified.

#

debugging

#

using Matter 5.0.1. appearsto have installed fine, checking log

#

some data appears to have persisted. removing and attempting to clear.

#

Adding Matter again

#

again, Invalid flow specified.

#

seems to have installed correctly, logs are fresh, no persisted data

#

(logs have been set to debug)

#

syncing thread settings, and factory resetting bulb and attempting connection

#

bulb broadcasting, Thread credentials synced. attempting to connect

#

wish me luck

#

Disregard, getting a Matter is unavailable notification on the commissioning device.

#

getting nothing but matter is unavailable.

#

restarting home assistant

#

starting the whole process again. going to do the same settings

#

got the same matter message, switching it to the beta, see if i see any difference

patent nymph
#

the error with the flow is somehow "normal"

#

mine works just fine with this error

#

is there somewhere a thread network map like Z2MQTT where you can see what is connected to what ?:)

tribal knoll
#

however its disabled by default

patent nymph
#

not using it anymore

tribal knoll
#

taking the "non nuclear but still in the megatonne range option" of reverting to a post install backup of HA.

#

nvm, tsar bomba being released. full home assistant reinstall incomming

patent nymph
#

there is something wrong with your network

tribal knoll
tribal knoll
#

after a fresh re-install of home assistant and doing nothing but setting up matter and thread, im getting Matter is not available when i try and add a matter device

#

before the update to 5.0.1, i could bring up the commisioning system but since the update thats all i get.

patent nymph
#

could it be matter on phone

#

not HA ?

tribal knoll
#

factory resetting it is what i went with

#

gonna give that a try

patent nymph
#

do you have another phone to try

tribal knoll
#

this is the second phone

patent nymph
#

blah

#

I've seen that on mine when I reset GPS

#

for a while

tribal knoll
#

interesting, that didnt happen the last couple times i reset gps.

#

ill try again in the morning

#

couldnt wait, had to try the factory reset, same message

#

๐Ÿคทโ€โ™‚๏ธ

spring bramble
# bronze fog So with a skyconnect and credentials, not using HA OTBR , will HA talk directly ...

It always did that way, the credentials import into HA is only needed if we want to join other BR's to the existing Apple network. Adding the SkyConnect to the Apple network is something I won't yet recommend due to fact we do not yet support TREL and Apple does. So unless the SkyConnect sits in a much better place towards your devices than your Homepod(s), I wouldnt use it yet for Thread if you have an existing Thread network from Apple

spring bramble
digital salmon
spring bramble
digital salmon
#

Ok, thanks for the information. ๐Ÿ˜‰

trim venture
#

This channel is meant only for questions related to the Thread radio protocol. Please use #matter-archived for anything else that matters. ๐Ÿ˜ƒ

trim venture
raw vault
#

I have a HomeKit Thread QingPing sensor. When i try the usual install procedure (add to Apple Home, remove accessory, add into HA HomeKit Devices integration, it says the device is already paired. The device pairs with BT then Thread; how can i add this device into HA? DEFINITELY not Matter (has HomeKit code)

vapid shell
#

The 2 options are either (a) pairing to Apple home and make sure itโ€™s connected by thread. turn all your border routers off and make sure the sensor is connected to Apple home by Bluetooth. Now unpair. Then turn the Brs back on.

#

Or (b) apparently there is a beta release of the iOS app that can sync the keys out of iOS.

#

So if you can do that you pair it directly to Bluetooth in ha

#

Then there is a button to migrate it to thread

#

(B) will be preferred when itโ€™s out of beta

#

(A) should work but making sure the Bluetooth connection is up is very important. When you remove a device from apple home it always โ€œworksโ€ but I might leave the device in a paired stage. So itโ€™s important to have a connection and to be near it with your phone

#

The eve app has an โ€œidentifyโ€ feature which can help

inner torrent
#

I have a more casual question someone can hopefully speak to. I see references to thread supporting an "unlimited" number of devices, but there's finite bandwidth (250 kbit/s) so how can that be?

#

Adding more BRs doesn't increase the bandwidth available on a particular thread channel

vapid shell
#

So with TREL you can actually ease the pressure on the thread channel.

#

If without TREL it takes 4 hops to get from a BR to your device over the mesh, that means that one packet is transmitted 4 times. If you can reduce the hops, you reduce the number of transmissions.

#

TREL does that - your BR can re-route packets via WiFi to a much much closer BR so the packet only has one โ€œhopโ€ on the thread spectrum right at the end.

#

But i think the answer to your question is likely more boring than that, and that it just means there is no theoretical limit or bound defined by the protocol.

#

Like the protocol doesnโ€™t require a state table that has an unbounded size to track all peers in the mesh.

spice imp
#

Also, unlike fx Bluetooth, thread is not a flooding mesh, so the message is only send to the device that is supposed to recieved the message.

raw vault
raw vault
raw vault
vapid shell
#

HA can then push them over homekit Bluetooth to put devices on the mesh by itself

vapid shell
#

For that device thread doesnโ€™t add much value when you have Bluetooth coverage. Homekit has a pretty good power efficient and fast way to push sensor updates over Bluetooth.

#

So maybe itโ€™s just decided to prefer it

tacit dirge
#

Looks like belkins thread switches are out now

#

Any idea if they would work on HA? They talk only about homekit but thread is thread sooo

#

Otherwise I've got twenty inovelli switches coming to try out

#

(March)

raw vault
ionic plaza
#

But I didnโ€™t notice any changes after the import, I had indirectly shared Apple thread network key (extracted from NL) with HA before and able to use Appleโ€™s thread network as a โ€œpreferredโ€

tough snow
#

I had been using SkyConnect MultiProtocol for a few months now. I literally only have one bulb (a NanoLeaf). that uses Matter over Thread. A few days ago it stopped working and now I cant seem to be able to add the bulb anymore. I have tried deleting everything and re-adding but for the life of me I always get stuck in the "can't connect to thread network home-assistant check that your device can work with this network type and try again." error.

Where should I be looking for relevant logs to understand why it fails to pair the bulb?

tacit dirge
#

I had nothing but pain with nano leaf bulbs and multiprotocol

#

Swapped to thread only and it all worked

#

Bulbs still drop off occasionally but that's apparently a nano leaf problem

potent vortex
#

๐Ÿ‘

tough snow
#

I tried that too. I have a total of 6 nanoleaves and not a single one connects. How do I make sure my config is correct? I am using the open thread border router add on that supposedly reflashed the SkyConnect so that it's Thread only.

spring bramble
#

For support for matter devices use the matter channel please, thanks

night sinew
#

Hi all... Hi have a SkyConnect USB dongle.
I would like to install the Zigbee+Thread firmware...
When I try to do it from the web installer:
https://skyconnect.home-assistant.io/firmware-update/
the web installer freeze during the connect process. I see: "connecting" but it never connects

#

any idea?

frozen flower
night sinew
#

chrome on two different PCs

frozen flower
#

Did you get a notification of the website to allow accessing your USB devices?

night sinew
#

sure

#

I clicked connect to PORT9 (the one from skyconnect) and then it shows the "connecting" loader... and it hangs there

frozen flower
#

Weird. But as far as I understood you don't need to flash it via the flasher. You can configure it from HomeAssistant and just tick the box for using multiprotocol. It will reflash then

night sinew
#

I see no options to do it in HA, how can I do it?

#

Using docker, not HA OS... in any case the web installer should work ๐Ÿ˜ฆ

inner torrent
#

There's instructions for how to do so

night sinew
#

it seems that the web installer is broken

vapid shell
tough snow
spring bramble
inner torrent
#

@spring bramble it might be helpful to add some more context to the existing pinned post;

E.g. This channel is for discussing thread communication issues (setting up OTBR in HA, debugging thread communication issues, etc). Debugging and discussion of Matter over Thread devices should be in #matter-archived

digital salmon
vapid shell
honest jasper
tough snow
#

How do I check what firmware my SkyConnect dongle is running? I want it to be Thread only. I have no zigbee devices.

inner torrent
#

It's configured with ZigBee only out of the box

unreal island
#

I am testing the matter-server and otbr container with a skyconnect dongle for a while now. Dongle is flashed. otbr advertises over mdns. I switched from containers to kvm hassos to have the networking a bit easier. But I wantd to askโ€ฆ is it normal that the advertised port of the otbr is closed?
dns-sd -B _meshcop._udp local shown:
Home Assistant Silicon Labs Multiprotocol #D2C0

and dns-sd -L "Home Assistant Silicon Labs Multiprotocol #D2C0" _meshcop._udp local shows:
.. can be reached at homeassistant.local.:49154 (interface 15)
but the port is not used/listened on.

unreal island
#

or in other wordsโ€ฆ is the border router a service reachable via tcp connection or is the traffic for the thread ipv6 network sent directly to that host and the border router has iptables rules to get them?

fickle mantle
# unreal island I am testing the matter-server and otbr container with a skyconnect dongle for a...

I was curious and tried this out on my setup which uses the SiLabs Multiprotocol AddOn as the OTBR and ended up with the same results (port not open). I'm by far not an expert on Thread, but my understanding is that meshcop is used for commissioning a device and the commissioner device can be internal to a Thread network (usually BLE is used for commissioning using a mobile device) or external to Thread in which case I think port 49154 would be used by the external commissioner to reach the BR (as Joiner Router) via tcp/ip and the BR in turn relays DTLS session packets with the joining device. Why the port is not open, I don't know. Perhaps its a build option to turn it off so as to only use internal commissioning??

spring bramble
#

@sick swan did you see this post above ?

sick swan
# unreal island or in other wordsโ€ฆ is the border router a service reachable via tcp connection o...

In OTBR world, from what I understand, mDNS is mainly used to tell the network that there is a BR and which Thread network it routes to (see all the TXT records). The API of the OTBR itself (e.g. how to configure it etc.) depends on the particular implementation. There is no common protocol on a TCP/IP port. So the port which is announced by the _meshcop._udp service is really a dummy port (see also https://github.com/openthread/ot-br-posix/blob/main/src/border_agent/border_agent.cpp#L77 and https://github.com/openthread/ot-br-posix/blob/main/src/border_agent/border_agent.cpp#L434-L438).

IPv6 wise the OTBR is just like a regular router: It announces the network it is able to route using IPv6 Neighbor Discovery Protocol (particularly the Routing Option) to announce what network he can route. Then IP traffic can transparently flow between the networks.

To on-board a Thread device to the Thread network several mechnism exist. The OpenThread reference implementation has some commissioning logic which I think involve the OTBR itself. But it is not actively used/supported afaik. Matter has its very own commissioning logic which supports Thread. HomeKit has a Thread commissioning flow. Both of these just need a Thread dataset from however operates the Thread border router. Android and Apple iOS have mobile app APIs to get the credentials for their routers. We have our Thread credentials store for that.

The OpenThread Border Router reference implementation has (example) API's bulit-in to configure: A local only D-Bus API and a HTTP based REST API. In Home Assistant we use the latter to configure the OTBR (setting network settings etc). All that information is then stored in the Thread store in Home Assistant and transferred to whoever wants to commissions a device to the Thread network (currently Matter compaignion apps and HomeKit integration make use of the Thread credentials).

inner torrent
#

@sick swan since you are knowledgeable about the OTBR can you comment on the firewall? I usually keep it off because it seems kinda buggy. Sometimes it enters a perpetual startup/teardown loop for the firewall. Not really a problem to keep it turned off, but just curious

sick swan
#

@inner torrent the add-on is based on the upstream firewall script at https://github.com/openthread/ot-br-posix/blob/27ed99f3751f738bc7647256d3f54f2af54d72f3/script/otbr-firewall

There are some tricky things around firewall: The OTBR runs in host network, and it applies iptable rules to the host network stack. These survive through a add-on restart (that is why a add-on restart continues to show problems).

In theory, rules get applied on startup (as indicated by the Setup OTBR firewall... message) and removed on shutdown (as indicated by OTBR firewall teardown completed.). Afaik, the shutdown (as executed in the finish script of the s6 init system inside the container) should always execute. It seems that sometimes this isn't the case for you then? ๐Ÿค”

Which add-on are you using? The pure OTBR or the SiLabs Multiprotocol one?

inner torrent
#

No I'll have some case where it will startup fine then later get stuck in a firewall startup/teardown loop some time (hours) later.

#

I haven't looked into it too much because it seems it can just be left off but was just curious about it

sick swan
#

Hm, I see. Question is what happens exactly before it gets into that startup/teardown loop ๐Ÿค”

#

I remember I have seen such thigns in earlier version, but the scripts received some tuning/hardining over time. I have not encountered that issue recently

unreal island
#

@sick swan thx for the explanationโ€ฆ makes sense. I have another question. Does the IOS HA companion app store/retrive/sync the IOS keychain border router information with the HA thread store?

#

I am asking bc I set up otbr and afterwards had a nanoleaf shape border router and they could have ended up beeing in the same thread network if both apps would sync the credentials and prefered network via the ios api. But it did not happen.

sick swan
#

Afaik, the iOS API's (and Android is very similar in that regard) does not allow to write default credentials if there is already a Apple BR known by the iOS ecosystem.

#

But once you synced the credentails, you can reconfigure the OTBR to use the Apple credentials (at least in theeory this should all work ๐Ÿ˜… )

sick swan
#

@unreal island so the latest version of the add-on should no longer restart if otbr-agent crashes (and Watchdog is disabled on the add-on main page). This might make it easier to catch the situation you are running into.

inner torrent
#

Is there a diminishing return on number of BRs? Is there any benefit to a second one in the same area if your thread devices have a good connection to an existing one?

spice imp
delicate drum
#

Is there any work being done to add thread visualization to HA? Iโ€™ve seen white sheets from silicon labs talking about it.

spring bramble
unreal island
#

Puhh I finally got my 2 BR into the same thread network. (Nanoleaf and otbr). But Homeassistant still does not see it as its prefered network. Btw there is no other. How do I tell Homeassistant to not be so picky and take the one that is there? ;D

#

I have an Eve Room (HomeKit over Thread) also on that Thread network but not paired to HomeKit anymore. It was showing up in HA shortly but weird errors when trying to pair it.

#

Nevermind the question ;/ I configured the otbr in the HA OTBR integration and then it showed a button in the thread integration.

#

Weird that the Eve Room is fully advertising mDNS and reachable via IP but cant be found to integrate into HA.

vapid shell
#

If a HomeKit device is visible in mdns but not in HA that usually means it thinks it is paired already

#

(HomeKit devices can only be paired to a single controller at once)

#

Youโ€™ll have to reset it and try again

unreal island
#

Thx I will try.

sick swan
#

@vapid shell, have you seen that the OTBR now allows NAT64! Internet for all the things ๐Ÿ˜… ๐ŸŽ‰ ๐Ÿ˜Ž

vapid shell
#

๐Ÿ˜ฑ

sick swan
#

It is opt-in ๐Ÿ˜…

vapid shell
#

lol

unreal island
#

I am so happy atm I finally got an Eve Motion (Matter over Thread) paired throught IOS Companion App. I dont have another Matter controller and only OTBR + Nanoleaf TBR.

#

I thought it is not yet supported

sick swan
#

Nice! So it is probably connected through OTBR then?

half bluff
unreal island
#

@sick swan At first I had only the OTBR and it did not work. CompanionApp complained there is no TBR and Apple Home complaining there is no Matter controller. The I set up the Nanoleaf as a different Thread network and finally moved the OTBR on the same Thread network and marked it as the prefered.

sick swan
#

NAT64 allows Thread devices behind the border router to reach IPv4 addresses. This works even when there is no global IPv6 support in your network. With that it will be possible for Thread devices to talk to servers on the Internet.

inner torrent
#

What's the use case for that?

sick swan
#

There are Thread IoT devices which talk directly to their cloud.

half bluff
#

otbr-agent[177]: 00:01:42.426 [W] Nat64---------: incoming message is an IPv4 datagram but no NAT64 prefix configured, drop

inner torrent
vapid shell
#

NAT64 is like those devices can now talk directly to their own clouds.

sick swan
normal arch
#

Without a way to disable it probably, hopefully not though

still quiver
#

hi, has something changed recently with Nanoleaf? my devices are hardly disconnecting now, some have not disconnected in 1 or 2 days. This is great! The only thing that changed (besides HA matter/core updates) is that all 6 of my googles TBRs got Fuchsia 14 OS now. Was this a fix?

inner torrent
still quiver
#

Oh good to know I just updated the nanoleaf firmware to 3.6 is this beta firmware?

inner torrent
#

Yes

still quiver
#

nice! just in time for xmas....i may just buy more NL products now

inner torrent
#

I was told to not expect the general release until after the holidays tho. Just FYI

still quiver
#

but even the beta is really promising.

worn plinth
#

has anyone tried tuo's temperature sensors? maybe they haven't yet reached users, might still be in delivery. i'm very tempted, replacing my zigbee ones would be great and nearly let me drop zigbee altogether but if the battery life on their buttons is similar to the temp sensors then i'd rather wait for something else

spice imp
#

This is literally the difference between all my bulbs working flawless and most only half of my bulbs turning on and off and everything going crazy

bronze fog
#

@worn plinth I have a couple on order.

still quiver
#

I have not had a disconnect in over 24hrs with my NL products. This is a world record ๐Ÿ™‚

shy lake
#

Do I need to enable a thread border router setting within my google nest hub so HA can see it? Im not sure how everyone is utilizing the thread border routers within their google devices. Been googling how to set the is up and Iโ€™m coming up empty.

#

I have sky connect and everything setup where thatโ€™s my preferred network. But I donโ€™t see the ability to add other thread border routers.

inner torrent
iron parcel
#

Is there a way I can use my Nanoleaf Elements as the primary Thread border router? It shows up under thread integration but there's no 3 dots menu to have it be used for credentials

still quiver
inner torrent
#

I should specify nanoleaf has mentioned it can't be a lead BR or something

#

(can't remember exactly)

spice imp
still quiver
# spice imp Well sometimes they would change states a long time after pressing a button or n...

Yes, that is what I'm experiencing now with one of led strips on the beta firmware. Sometimes I try to turn it on or off using the button but it doesn't immediately respond and just goes back to the state that it was originally on. So perhaps it's caching the request and then doing it at a later time. This particular device is the farthest from the TBRs, so that could be part of the problem

spice imp
delicate drum
#

Any idea how to make amazons eero and echos pair together? I have three echos and eero mesh. Two echos at opposite ends of home joined together and third echo joined the eero in another.

opaque wedge
tacit dirge
#

There is a toggle for restore status after power cycle

#

Change that?

inner torrent
#

You should be able to check the device log in HA to also see what's triggering at least (UI? Automation?)

still quiver
inner torrent
#

Interesting

#

I haven't had that yet

#

They do have a beta discord so I'd make sure to tell them that it's being strange

delicate mirage
#

Same experience here, happened 3 times the last hour ๐Ÿคฅ

inner torrent
#

I'm curious how many bulbs you guys have total and how many on beta firmware?

#

I wonder if they are still crashing

opaque wedge
inner torrent
opaque wedge
inner torrent
#

Something that would be worth checking is if you can download the diagnostics of the bulb that randomly turned on and open that up and note the node number. Check if your matter logs has any errors related to that node -- anything you notice will help them debug it

shy lake
#

After switching to sky connect and configuring thread, everything seemed fine and all my zigbee devices worked. After 24 hours my zigbee integration is stuck on โ€œinitializingโ€

For some reason it loses connection to sky connect. But it still appears under hardware

Within the Thread integration, sky connect appears missing and I have to setup a preferred network again.

If try to configure the zigbee integration and select the multi protocol, it will say โ€œunknown errorโ€

Then Iโ€™ll have to stop and start the multiprotocol add-on to allow my to select the multiprotocol add-on but it will fail when selecting a network setting.

twin vine
shy lake
still quiver
#

BTW for those running multi-pan on skyconnect, and experience zha crashes, you may wish to try puddly's test firmware for the skyconnect

shy lake
still quiver
#

Yes

#

Exactly that

shy lake
#

Thanks! I will try this now.

shy lake
#

Worked perfectly

Edit. Crashed in less than 6 hours.

still quiver
inner torrent
#

No idea, but that at least provides a data point it's something in HA rather than nanoleaf

inner torrent
digital salmon
blazing grove
#

I hope I'm in the right channel, I'm currently trying to use Thread for my Schlage Encode Plus locks. When I provision them with the configuration button in HA, they seem to move over without any issues and identify as Thread Status Child etc. but at that point, I can't lock/unlock them anymore. They are reporting the status of the lock when I manually lock/unlock it which means that they are connected, I just lost control over them. Does anyone know how to fix that?

inner torrent
#

Oh apparently it's thread without matter

blazing grove
#

Its tagged as "Sleepy End Device" and "Child" which it wasn't before the provisioning

inner torrent
#

What integration does it show up under?

blazing grove
#

When I try to lock/unlock, the count of this warning in the log goes up

Logger: aiohomekit.controller.coap.pdu
Source: components/homekit_controller/connection.py:897
First occurred: 14:42:29 (4 occurrences)
Last logged: 14:43:05

Transaction 0 failed with error 6 (Invalid request

blazing grove
inner torrent
blazing grove
#

No worries, thanks for trying to help though! ๐Ÿ™‚

vapid shell
# blazing grove I hope I'm in the right channel, I'm currently trying to use Thread for my Schla...

So in the HomeKit protocol there are 2 types of โ€œwriteโ€ request. Locks use the more obscure โ€œtimed writeโ€ variant (for security). My hunch is that we never got to reverse engineer what a timed write looks like on thread (thereโ€™s no sdk or docs for HomeKit over thread, and one guy on the forums figured out the protocol using nanoleaf bulbs which wouldnโ€™t need timed writes).

#

If that hunch is right, given the lack of documentation, lack of other implementations of homekit over thread, and no one with time/ability to reverse engineer it who has that lock, you probably canโ€™t fix it yourself and will be waiting a while for anyone else to,

#

Did it work over Bluetooth?

#

(Another complication is that quite a few locks with actually work without help from the vendor app, so will never completely work either home assistant - if it doesnโ€™t work with Bluetooth either then it likely falls into that category)

blazing grove
# vapid shell Did it work over Bluetooth?

As far as I know, the lock is using Bluetooth only for the initial setup and is using wifi after that without any Bluetooth connection, at least thats how I think I understand how it works but I could be wrong. So far I tested the lock directly through the Schlage integration in HA which requires me to set up the lock in the app and is then using the app credentials etc. and that seems to work fine. I then did a factory reset on the lock and added it directly through HomeKit in HA which doesn't need any credentials at all, that also works without any problems. The only thing that seems to only work 50% is the connection through thread

vapid shell
#

It would be weird for it to have wifi and thread. Is it battery powered?

#

Did you press a button that says something like โ€œprovision threadโ€ on the locks device page?

blazing grove
vapid shell
#

And that worked in so much as the state changed to child

blazing grove
blazing grove
vapid shell
#

That button is only implemented for Bluetooth homekit

#

Before you moved it to thread, it was working in ha and you could lock and unlock?

blazing grove
blazing grove
vapid shell
#

Anyway now itโ€™s on thread, the state is correct (you can see if itโ€™s locked or not) but you can no longer lock and unlock?

#

Can you see a button on the device page that says โ€œidentifyโ€

#

Does that make the lock do anything

blazing grove
vapid shell
#

Flash a light or sing a song etc

blazing grove
#

That button works

vapid shell
blazing grove
#

Every time I press it, it beeps

vapid shell
blazing grove
vapid shell
#

It can be โ€œdisconnectedโ€, but then ha canโ€™t read the state and the lock would just be unavailable

blazing grove
#

Would the indentify send a different command to the lock though? I would understand if it could only read and nothing else, but if it can send a command and make it beep, I would expect it to also be able to lock/unlock it which is confusing me ๐Ÿ˜„

vapid shell
#

An identify doesnโ€™t need a timed write

#

A lock / unlock does

blazing grove
#

Ah I thought it would be a general "everything related to locks" thing ๐Ÿ˜„

#

I guess that makes sense though

vapid shell
#

Does your lock say that it is a sleepy end device on the Device page?

blazing grove
#

Yup

vapid shell
#

Sleepy end devices are.. sleepy

#

They power down and any commands queue on the border router

#

And then every 5s wake up and check their mailbox

#

(The actual interval varies)

#

That means that thereโ€™s no significant advantage over homekit over Bluetooth, which must have been working to get you this far

#

So if you can convince it to disconnect from thread Iโ€™d stick with Bluetooth for now

#

However it might be hard to do that without doing a full reset of the thing

blazing grove
#

I guess I'll just reset it one more time and stick to homekit if the speed is the same on all of them anyways

#

That way it'll at least be local

vapid shell
#

Baffled that it would be connected to your router and thread at the same time. Seems utterly pointless and missing the point. Youโ€™d want to connect to thread and then turn wifi off to conserve power. If you are connecting over WiFi youโ€™d just use homekit over tcp/ip (ie over wifi) and that would be instant. Not use an entirely seperate radio to do HomeKit. Madness.

#

Makes me question the entire brand

blazing grove
#

ยฏ_(ใƒ„)_/ยฏ

inner torrent
#

@sick swan my OTBR died yet again and I grabbed the logs, is there anything useful I can contribute from them?

#

(skyconnect)

#

pretty sure this is the offender, but I do have more logs

#

Write() at hdlc_interface.cpp:253: Input/output error

#

looks like between verifyordie it chose death ๐Ÿ™‚

sterile yoke
#

hi all

#

I've recently received my SkyConnect, and tried to use it with the Thread only firmware (which I flashed through the web tool)

#

so far I can't get OpenThread to successfully talk to the device

#

Failed to communicate with RCP - no response from RCP during initialization

#

I'm not sure what the correct Radio URL should be

sterile yoke
#

spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-flow-control worked

sick swan
silver mango
#

How to add seperate multiple esp32 voice assistant according to area??

I have multiple esp32 voice assistant in different rooms but the thing is I have many devices lights having the same name to its very difficult to control them. So I was hoping is their any method to seperate voice assistant according to area so that I can use a to allow only specific voice assistant to control devices present in that room.

digital salmon
serene prawnBOT
inner torrent
#

See above from dmesg that looks relevant

#

urb stopped looks like there was an issue with the rpi talking to the skyconnect

#

i use a powered USB hub for the skyconnect with a zigbee adapter on another port, so power shouldn't be a problem

#

if this was an issue with the USB hub I'd expect the zigbee dongle to go down at the same time

#

although it does say 1.1.2-port4 - maybe an issue with that port?

inner torrent
#

Actually could just be a bad extension cable, I'll just replace it and see if that fixes the issue

sick swan
#

What IEEE 802.15.4 channel do you run Zigbee/Thread on?

# 
[1202286.352674] cp210x ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1202286.353233] cp210x ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1202286.512971] usb 1-1.2-port4: disabled by hub (EMI?), re-enabling...
#

Uh, that sounds like some serious USB level communication issue. I'd try different cable/USB hub inbetween (with/without).

inner torrent
inner torrent
karmic summit
#

Hello, i have bought a second SkyConnect. My plan SkyConnect #1 is to make only Zigbee SkyConnect #2 thread.

I have shut down to set up the SkyConnect #1 removed from the system and SkyConnect #2 with Thread connected to HA. If I want to add the Open Thread Border Router I now have to "Enter the URL for the REST API of the Open Thread Border Router". Where can I find this?

inner torrent
#

? You should be able to just configure it via the addon

#

Sounds like you are trying to add it in the integration?

karmic summit
scenic crystal
#

So I need to read back through all these messages. Someone just clued me in to this discord ๐Ÿ™‚

I have a sky connect and a Sonoff zdongle-p. I recently flashed the sky connect to multiprotocol and moved some zigbee devices to it. I have no thesd devices.

Is the general consensus that this is not a good idea and I should just set up dedicated thread and zigbee?

I thought using multiprotocol would reduce signal interference since it sounds like not thread and zigbee would share a radio band

#

I did that with the plan to retire the zdongle-p because I thought that was better for signal interference

inner torrent
#

YMMV but I run ZigBee 15 and Thread 20 for example and it works fine for me

#

Skyconnect isn't the most stable but thread only is definitely more stable

scenic crystal
#

Where do I find thread only? I only see the option to have zigbee or multiprotocol firmware

inner torrent
#

Once you start the OTBR addon, you should see it flash the firmware in the logs

spark cliff
#

Is there a good guide for using the Sonoff Dongle E flashed with the multi-protocol firmware to do zigbee and thread simultaneously? The guide I followed got me to the point where I think everything should be working, but I still have not been able to add any thread devices to my HA. I do have my zigbee stuff up and running again.

spark cliff
#

Actually, I think I may have partially discovered my issue. My HA network settings had v6 disabled. I set it to Auto. I was shortly after able to adopt my nanoleaf essentials light strip. However, now I am wrestling with the nanoleaf essentials bulbs to get them to work. They seem to negotiate correctly with the thread radio, but then when it finalizes and wants to add the matter device, it poops out. ๐Ÿ˜ฆ

spring bramble
spark cliff
#

I have actually managed to get both working at this point, mostly by beating my head into a wall repeatedly. ๐Ÿ˜„

I will keep that in mind though, and if I need to I will buy an additional dongle to stabilize things.

spring bramble
#

Yes but be advised that one of the bugs currently with multi-pan is a complete crash so it will take down your zigbee network as well. keep that in mind.

spark cliff
#

Noted! I appreciate your help.

knotty citrus
#

I'm trying to use a Sonoff ZBdongle-E with RCP multi-pan firmware as my thread border router. And I've HA installed in a container. I know it's somewhat tricky, but I do have it all set up with additional containers running for the multipan integration and the matter-server.
Is there a way to verify that I've everything set up correctly?

karmic summit
#

I have reset my Thread network and now have the problem that the Eve-Energy can no longer be added (i have also reset this to the factory setting). The network check takes forever and then it cancels "No connection to the device available"
Before I reset my Thread network I had no problem. I know don't touch a running system :x my bad

spring bramble
karmic summit
#

When I want to add new Thread devices (Eve-Energy) to my network and scan the QR code with the HA app (Android), I get to "Network connection is being checked..." and it is cancelled. Any idea what the problem is?

twin vine
karmic summit
scarlet seal
#

Can anyone recommend a cheap thread border router that is pretty reliable and can communicate with my Schlage locks? I find that my Apple TVs, home minis are not that reliable as a thread router to these locks

twin vine
#

Huh really? How far is the BR from the device?

#

Typically apple has some of the best BRโ€™s

inner torrent
#

You're not going to find anything more stable than the big companies atm

#

It's more likely it's the device or you have some networking issue

scarlet seal
#

Hmm I think maybe it's because my Homepod is not accessible from a network outside my home network?

#

I'm abroad and all my Schlage locks have no response

#

They can communicate via WiFi but not over Thread

autumn tulip
#

Does anyone know how I can enumerate the devices connected to my Thread network, and especially to get their ipv6 addresses? I have an eero Thread network that I've joined with with an OTBR instance on my HA Yellow, and I'm not convinced things are working correctly. I'm trying to do basic network diagnostics to see if things can even talk to each other.

mossy viper
autumn tulip
# mossy viper <@1030074093590036550> - I was just reading through the following blog where the...

Thanks! The mDNS discovery app is showing me the stuff I need to proceed. The OTBR web interface gives a lot of very confusing information. I'm trying to sort out what's really going on. For example, I've already joined my eero thread network, so it seems disingenuous or confusing to list all of my eero devices separately as networks I might be able to join. At minimum I'd expect it to hide any border routers for the network I'm already a part of. Also, asking me the on-mesh prefix is probably not great since nothing tells me what that prefix is.

inner torrent
#

OTBR web interface isn't reliable/stable so I wouldn't rely on it

autumn tulip
#

Also, the topology diagram is very flaky. It doesn't show any of the child devinces at all, which makes me wonder if any of them are successfully connected. It doesn't consistently show all my border routers either. I'm not confident at all about the state of things based on what this interface shows me.

autumn tulip
mossy viper
#

about all I've been able to do is use ping6 and traceroute6 once i have addresses.

autumn tulip
mossy viper
#

๐Ÿ™‚ I've found them with "Discover" and "flame" as the blog author details - but he goes much, much deeper than I have

inner torrent
#

As @mossy viper mentioned, there might be platform specific tools (I think discover and flame are iOS? Could be wrong)

mossy viper
#

I use them on my macbook - but I think that avahi-browse is similar - i.e. just list mdns broadcasts on the net

autumn tulip
#

I think I've found part of my problem. The OTBR is set with a different on-mesh prefix compared to the eero network. I have a mix of prefixes on the network, which will surely screw things up.

#

The default OTBR prefix was fd11:20:: . I don't know how many bytes of these addresses I see are my real prefix though.

mossy viper
#

I'm a novice at all this - reading that blog trying to decipher what the various ipv6 addresses are for and what the prefixes mean

autumn tulip
#

Is it possible to not actually run a border router on my local device but still commission matter over thread devices? It seems like I need the thread integration running to provide the credentials when commissioning, and it seems like the integration wants the OTBR addon running. I'd like to try removing OTBR from the equation to see if my network problems get better.

vapid shell
#

You absolutely do not need OTBR

inner torrent
#

No you don't need the OTBR addon.

Thread integration doesn't require the OTBR addon -- there's an OTBR integration which needs the OTBR addon

autumn tulip
#

Ok, I seem to have been confusing the OTBR integration and the normal Thread integration. I've got OTBR disabled now and I'll see what happens. The Thread integration is still reporting it as a present router, so there's probably some sort of TTL involved. I'll give it 30 mins and try more debugging.

#

Does it matter which of my border routers i pick to provide ios and android credentials? Is commissioning going to fail if that router happens to be too far away from the commissionee?

inner torrent
#

I actually don't know what that means (in my thread network I never selected a BR to use for that).

@vapid shell do you have any insight?

autumn tulip
#

In the thread integration config there is a 3-dot menu next to each of the border routers. The only menu item is labeled "Use router for Android + iOS credentials". I assume it does something, otherwise why would someone have bothered to add it?

inner torrent
#

Yea I'm sure I does something but I never used that option and I'm not sure what it does

vapid shell
#

It shouldnโ€™t matter

#

Itโ€™s a really boring thing to describe in bed on my phone but basically itโ€™s an undocumented part of the commissioning API in iOS and Android

#

They donโ€™t say why

autumn tulip
#

After disabling OTBR, power cycling my Nanoleaf Essential bulbs automatically reconnected them in HA for the first time I think ever. I think OTBR was part of my problem (also their finniky firmware contributes).

vapid shell
#

We suspect itโ€™s to check that your border router is actually on the right vlan or similar

#

But itโ€™s not used outside of commissioning

autumn tulip
#

Commissioning is a big part of where the wheels are falling off my wagon. The Nanoleaf bulbs lose connectivity after power cycles and apparenty too many cosmic rays, and the only way to restore them is to fully reset them and recommission them. > 50% of the time commissioning fails, and it's unclear where the failure is. So I'm just trying to rule out network level issues, which brought me to trying to disable OTBR.

inner torrent
#

There's some known problems with commissioning, which a patch was pushed to the matter beta server (again you can toggle this in HA or wait for the next core release)

autumn tulip
#

Iโ€™m using the beta firmware for the bulbs now, but commissioning to either Apple home or HA is not often successful. Iโ€™ve wasted a lot of time this week trying to stabilize all my light bulbs ๐Ÿ˜•

inner torrent
#

Hm interesting, commissioning to apple home should be pretty stable

#

But then again I'm still seeing evidence that the bulbs are crashing despite the latest FW so could still be firmware hasn't fixed the problem

austere bridge
karmic summit
sick swan
#

@inner torrent @spice imp let's move over here since it is about Thread.

The thing I was wondering the other day is TREL even important for the typical Matter network today? Most traffic flows from a Matter Controller on the main network (WiFi/Ethernet) to a specific Thread device. From the description in the standard:

Thread Radio Encapsulation Link (TREL) enables Thread Devices to communicate directly over
IPv6-based link technologies other than IEEE 802.15.4, including Wi-Fi and Ethernet.

So this is about Thread to Thread communication ๐Ÿค”

#

I guess the question is when operating two border routers, how does the traffic makes it from the Matter Controller to the Thread device through the optimal BR. From what I understand the same routes to the Thread network's OMR prefix are pushed by the BR's, so technically a Matter controller knows all the Thread Border routers.

However, a Matter controller doesn't know which one of the BR it should send the messge to to reach through the optimal path, as it only knows the target IPv6 without having knowledge about the mesh network. So TREL maybe is actually important for the BRs to forward also (mainly?) incomming packages to the best router then? ๐Ÿค”

inner torrent
spice imp
#

When sending packages from the outside

sick swan
#

Yeah unless there is another technique. But I don't think so.

#

They basically generalized the problem...

#

@spice imp

Same here, i did before though...
They switched from Linux to Fuchsia at one point. Was that maybe a feature loss there? ๐Ÿค”

sick swan
# spice imp When sending packages from the outside

Ok. Yeah before I really was really wondering whats the fuzz about TREL, Thread device to Thread device communication is really not that common ๐Ÿคทโ€โ™‚๏ธ But when this is the only way for incoming packages to get routed throught the optimial BR this becomes a quite nice feature pretty quickly I'd imagine.

#

Now my question becomes why does our BR claims it has TREL enabled:

# ot-ctl trel
Enabled
Done

And there is no mDNS annoucment? ๐Ÿค”

Also I have a Google BR, and no working trel as it seems:

# ot-ctl trel peers
| No  | Ext MAC Address  | Ext PAN Id       | IPv6 Socket Address                              |
+-----+------------------+------------------+--------------------------------------------------+
Done
twin vine
#

Strange, maybe itโ€™s been turned off in the latest fuchsia update

vapid shell
# sick swan Yeah unless there is another technique. But I don't think so.

Homekit over thread is udp so I toyed with whether I could open a raw socket and write my own l2 header for outbound packets, so I could pick the Br. Then have a map of thread address -> br based on where the last inbound packet came from, as the mesh would have presumably sent it to the best br. Thankfully for everyoneโ€™s sake I donโ€™t have any spare time these days ๐Ÿ˜‚ but I wondered if that sort of trickery was how Apple seemingly had more stable thread than us pre trel.

#

You could do that sort of thing with a tun driver I guess. Effectively a vpn client, but you are just rewriting the layer 2 MAC address and squirting it out the right interface

#

The big thing we used to see causing problems last year (other than stale routes) was when someone had an appletv that was in an av closet. Surrounded by power, usb, hdmi, etc.

#

Turning it off would be the fix

#

Partitioning should have been enough in those cases I think? But it wasnโ€™t enough. Maybe merging and partitioning too quickly?

#

With trel the ATV should just forward to a valid br

#

Which makes it pretty essential quite quickly imo

#

(In the absence of my mad stuff)

sick swan
deep mortar
#

I am having an issue while trying to connect my Nanoleaf A19 bulb to HASS using the Homekit integration. I type in the pairing code and get the error Invalid flow specified. I have had issues before with this bulb, as it doesn't connect to Google Home as it is supposed to. Any ideas? Note, I don't have another Homekit device, but I do have Nanoleaf Shapes which connect to HASS fine.

My Nanoleaf Shapes apparently act as a "Thread Border Router", so I was wondering if I could use the thread integration to connect them.

spice imp
spice imp
#

Because i have been running on Fuchsia with trel

twin vine
#

Huh right

#

Updated TREL to be disabled unless enabled by feature flags or CLI.

#

Interesting

#

So I doubt there is any way to force a activation of it, as there is no easy way to CLI into a Google nest etc etc

spice imp
#

That is from Google

#

But maybe they also just didnโ€™t look into this and just updated

twin vine
#

Itโ€™s possible; will have to look when I get home

vapid shell
#

With thread you can add into the mix that it was discovered in Bluetooth, but then disappeared from Bluetooth and never became visible to ha on thread.

deep mortar
#

I managed to get it working somehow

vapid shell
#

Personally would ditch it for the matter version, I have the homekit and matter versions of the light strip and guess which one had spent most of today not responding to ha ๐Ÿ™‚

deep mortar
#

how can I find the REST api url of my nanoleaf shapes tho

#

any idea?

vapid shell
#

It doesnโ€™t have one

deep mortar
#

oh

#

hmm

#

isnt it a border router tho?

#

i thought they are supposed to

vapid shell
#

There isnโ€™t a standard for Brs to be compatible with each other

#

At least in terms of managing and configuring

deep mortar
#

๐Ÿ‘

vapid shell
#

The mortal way is probably to get a HomePod, get the nanoleaf app to add your shapes br to the Apple network, then use the beta version of the iOS companion app to sync the Apple credentials over to ha.

#

Otherwise you need a hex string called a TLV that includes the channel, network name, network key, pan id and ext pan id. In matter format, not homekit format.

#

But as with the matter vs homekit version of nanoleaf.. thereโ€™s a reason my shapes is not currently acting as a br

inner torrent
vapid shell
#

It was the straw that broke me and made me move my Eve Thermos back to Bluetooth ๐Ÿ˜

knotty citrus
#

I couldn't quite get the multiprotocol firmware to work, so I've flashed the openthread firmware and trying to set that up. What all addons & integrations do I need?
I installed the "Open Thread Border Router" addon. Do I also need the integration? Maybe I don't understand the concept of addons vs. integrations well enough yet.

spice imp
#

And in general you should not use the multiprotocol firmware at the moment since its not stable. So its better to just flash the thread firmware.
I have read that you need to have the multiprotocol addon installed beside the border router addon. I think this addon then creates a device on the system you can select in the border router addon. I have never tried doing it this way myself though, so i might be wrong.

knotty citrus
#

Yep, so I installed the ot-rcp firmware and installed the "Open Thread Border Router" addon, and the integration of the same name.
But I still can't provision a new thread device. I keep getting "can't connect to Thread Network" error on my Android companion app.

#

This is my first time with Home Assistant and all this smart home stuff, and even though I'm well familiar with linux and software programming in general... I don't know where to look for errors either ๐Ÿ˜ฆ. At this point I wonder if my devices are straight up broken or what

spice imp
#

So maybe its the wrong network synced to your phone or something

knotty citrus
gaunt valve
knotty citrus
gaunt valve
#

I got my first matter/thread device for Christmas. It's an Aqara Door and Window Sensor P2. I don't have any TBRs (my Apple TV 4K is first gen, my Google speakers are even older). I am, however, using a SkyConnect, but I have a container-based install and haven't been brave enough to try the beta firmware. (I have a 40-ish ZigBee devices, so outages would be quickly noticed by the wife.) I have installed the Python Matter Server in my docker-compose.yml, and as far as I can tell, it appears to work. What's the current recommendation for getting one of these devices to work? What's the state of the firmware? Should I get an Apple Mini pod, or whatever it's called instead?

spice imp
#

And then maybe remove and add the Google home app again to force Google playservices matter apis to redownload

#

And then probably press sync credentials of something similar on your home assistant app under the thread integration, where the 3 dots are

#

(Not 100% sure it exists, donโ€™t have an android phone to check right now)

inner torrent
gaunt valve
sick swan
#

Anyone experience with the Thread border routers includd in Nanoleaf products (Lines/Shapes/Elements)? Are they stable? Is TREL enababled?

vapid shell
#

Trel wasnโ€™t enabled in October, since then I removed it from my prod network because after I powered down a HomePod the entire mesh died

sick swan
#

Hm, ok thanks for the heads up. Might give it a try in January and see what happens on my end

#

My mesh is Google + OTBR (with SkyConnect pure Thread) currenlty.

#

So far solid

inner torrent
#

I've got a similar setup (Google, OTBR) with an elements BR: no TREL

#

Hard to say about stability since I have a lot of NL bulbs

twin vine
#

Yep, got the shapes and no TREL

digital salmon
knotty citrus
sick swan
#

One thing I noticed is that Google Play Services don't allow to update even our own credentials. The API claims it updated the credentials, but it seems not to work (as in, trying to sync again will lead to the same message again). What message do you get when manually syncing?

knotty citrus
sick swan
#

Only way out of this is to delete Google Play Services data...

knotty citrus
#

How exactly do I do it -- just App Info => Delete storage data?

Found official google documentation: https://support.google.com/googleplay/answer/9037938?hl=en
#

Alright, that's done now -- I used the same Troubleshooting tool and it reported Added network from Home Assistant to this device and after trying it again, now I get Home Assistant and this device use the same network. Let's see if this works now ๐Ÿ˜„

#

And it finally works! Cheers!

#

I think the recommendation to go to the Troubleshooting page on the Android companion app to sync the credentials, and debug that until you get Home Assistant and this device use the same network is critical advice.

#

This should be more documented. I stumbled upon that Troubleshooting page almost luckily! Maybe some of this stuff should be well written and pinned to this channel if nothing else.

#

When I was using the "Open Thread Border Router" standalone docker container (outside of home assistant), it had a nice web based UI to view/debug/visualize the thread network.
When using the addon, is there a way to access that web UI?

inner torrent
spring bramble
#

Now that we're getting more and more steps working, we will start to document the known working setups soon

knotty citrus
#

I appreciate that it's all experimental, but there's people like me who're brave enough (more likely foolish, like me) to try and make this work. And nowhere in any logs or steps does anyone mention "Troubleshooting" page on the Companion App. Just stumbled upon them by fluke while reading some forum down a rathole, after someone here suggested that credentials could be the problem. I just wish it was somewhat easier to find.

#

I had written-off my devices and raised the Amazon request to return. I'd have literally returned the devices tomorrow morning, had it not been for above suggestion. And now it all works.

vapid shell
#

Itโ€™s a difficult trade off. Non-developer users trying to use experimental unfinished code paths reporting problems - is it useful? Or is it noise? I think itโ€™s probably the right choice for a small dev team to encourage users to stick to setups they expect to work.

#

I was in a similar position with the homekit integration where Iโ€™d spend literal hours with users effectively teaching them how to use tools like tcpdump to debug problems and it was 99% of the time not something I could do anything about. Was that a good use of my time? Probably not, because Iโ€™ve still not been able to fix the bugs in that code that do very much exist.

#

And if Iโ€™d had the list of supported stuff back then, itโ€™d have been a lot easier to triage and focus on the bugs I could do something about

#

The problem with some of the known problematic setups is they can seem to work to a newbie, until a week later you wake up and the mesh is down and wonโ€™t come back up ๐Ÿคทโ€โ™‚๏ธ

knotty citrus
#

Fair enough

#

I hope Google improves the whole Thread credential storage mechanism on Android and allows for some menu options to reset / change them without having to reset Google Play Services. Even some setting under developer options would be nice.

stable kettle
#

hi, just random question whatโ€™s recommend to use with thread, i have like 3 apple tvโ€™s 4k with thread i can use as boarder router or the home assistant with skyconnect?

#

I need to select prefererd right

autumn merlin
#

Once I import the credentials in the iOS app, do you then make the apple thread network the preferred network? What is the benefit this? https://imgur.com/a/Kwqiead

stable kettle
autumn merlin
#

lol

inner torrent
autumn merlin
inner torrent
#

It could make a difference yeah, but I think you should be able to join them which would be the best option

#

I'm not an iOS expert but you should be able to make the apple one preferred and have the skyconnect join it

#

That's how it worked for me on Android

pale nymph
#

i cannot for the life of me get them on a Thread network, despite having at least 3-thread compatible routers in the house

#

you also cannot control scenes with Essentials on any ecosystem except through the Nanoleaf iOS app. which is in stark contrast to the Smarter series Canvas and Shapes, which expose scene control to any ecosystem you want

#

using matter over wifi and pairing with Home Assistant gives bare minimum support. Transitions are not supported, and if there is a Nanoleaf animated scene playing, you cannot override it from HA

inner torrent
inner torrent
#

This is not a HA limitation, but a result of nanoleaf support for matter

#

I'm not sure what you mean by "transitions not supported"

pale nymph
#

there is no smooth transitioning between on/off/colors

#

not even with the service call options

inner torrent
#

On/off should have a 0.5 s transition as part of the nanoleaf vendor spec (mine do this at least)

Regarding a more overall transition time (between colors for example) it's in the works. There's a parameter for transition time but the dev team has been working on other issues

pale nymph
#

i can understand that. what's most frustrating though is having scenes running from the Nanoleaf app, then not being able to stop them from HA

inner torrent
#

It's likely because HA is sending a matter command and nanoleaf isn't. For scenes, nanoleaf is communicating over their proprietary protocol, so it's not really a HA problem if they send a matter command but the bulb doesn't respond correctly; that's a bulb firmware problem

#

You can enable matter debug and tail the log to see the commands being passed; HA passes the correct call

#

Youd see the same behavior using Google home or apple home

pale nymph
#

i'm sure it's as you say. i start "crackling fire" animation from the app, then try to set the lights to white via HA, and it flashes white for a second, but then instantly resumes the animation from the app

#

either way, sounds like the Holiday Strings lights have nothing to do with Thread, and are purely matter based protocols

inner torrent
# pale nymph either way, sounds like the Holiday Strings lights have nothing to do with Threa...

Correct, you can open an app to view open ports on network devices.

For your string lights you'll see:
_matter._tcp 5540
_ltpdu._udp 5653

When you set scenes, the nanoleaf is communicating on the _ltpdu protocol and HA is communicating on the _matter port

HA sends a matter command and the lights just don't respond correctly because the scene they're running was executed over the _ltpdu and there's some internal conflict and it doesn't respond

This is entirely on nanoleaf to fix

#

Matter DOES support scenes, but the fact that they are unavailable is because nanoleaf doesn't support scenes through matter

pale nymph
#

Hmm. Is there an API I can use directly with the HSL lights?

#

Iโ€™ve tapped into the UDP stream before to read Canvas touch events

inner torrent
#

Do report back tho if it works

pale nymph
#

Thanks!

sick swan
knotty citrus
#

Also, given there's the bug where Android doesn't actually update the credentials when the tool is run, but falsely reports as "Updated ...", that message is misleading. A better approach might be to rerun the comparison after the supposed update and report an additional error message along the lines of "Credentials differ. Attempt to update the device credentials failed."

#

If the android build environment hadn't been so complicated to set up, I'd myself have submitted a PR for this ๐Ÿ˜…

flint zodiac
#

So there's an iOS companion app update that allows me to import the Thread credentials from Apple. This still won't allow commissioning to OTBR directly?

steep moth
#

Hi! Successfully added a Eve Door & Window, but the second one doesnt work, getting these error messages in the OTBR Log (Skyconnect):

otbr-agent[300]: 00:08:08.246 [W] SrpServer-----: Name conflict: service name A3C9565B8CD5E5AD-000000000000002B._matter._tcp.default.service.arpa. has already been allocated
otbr-agent[300]: 00:08:08.246 [W] SrpServer-----: Failed to process DNS Update section: Duplicated
otbr-agent[300]: 00:08:08.246 [W] SrpServer-----: Send fail response: 6

Any idea? Tried it multiple times to add the sensor with HA restarts, Matter Server restarts and Multiprotocoll Add On restart. The Sensor is factory resetted before every try.

#

Unifi Setup, mDNS is off, Multicast Enhancement also. Everything is on the same subnet

spring bramble
#

@steep moth use the matter server stable version 5.0.3 and not the current beta 5.1.x

broken inlet
#

I have a Sonoff ZBDongle-E Plus flashed with MultiPAN RCP and Silicon Labs Multiprotocol add-on installed.

knotty citrus
#

Is there no matter-over-thread switches/dimmers available out there?
I found 1-2 products with HomeKit over thread, and a handful products with matter-over-wifi support, but nothing with matter-over-thread. Are my internet skills failing me or there's nothing out there?

spring bramble
#

There is some stuff coming soon but not yet available on the market.

inner torrent
#

Just to add, CES is coming up soon -- so some stuff might be unveiled there soon. Although there's plenty of stuff that was shown last year that still didn't make it to market this year

bronze fog
#

@knotty citrus You can pre-order Inovelli thread/matter US Dimmers from their site. Estimated ship is March 2024.

inner torrent
bronze fog
twin vine
#

Seems perfect honestly

#

Are they the ones they are always connected to power? Or battery operated?