#not sure what wifi has to do with this

1 messages · Page 1 of 1 (latest)

fading laurel
#

In fact WiFi (or better said: your local LAN) has everything to do with it... Thread devices communicate over IP and are "bridged" to your local network using Thread Border Router(s). What Border Router(s) do you have setup in your network ? For Apple iOS ecosystem, suitable routers are the Homepod (mini) and Apple TV 4K. For Google Android, you can use the Nest Hub v2 or their new WiFi Pro routers.

worthy hamlet
#

I have the open thread border router integration installed on a sky connect

worthy hamlet
#

I just tried again and it worked this time so not sure what was going on

fading laurel
#

OK, keep in mind that using the SkyConnect as Thread Border router is still considered beta and may lead to unexpected issues. We're working on adding some additional diagnostic tools and info to better support issues.

worthy hamlet
#

gotcha, so when the client indicates checking network connectivity, this is HA verifying the network path that should be created by the thread border router integration ?

#

right now I'm just messing with thread devices so I'm ok with beta, although since I am new to this it is difficult to see the distinction between support issues and I don't know what I'm doing issues

fading laurel
#

If you want something (pretty) frustration free today, best is to use WiFi matter devices (or bridges) or use Apple or Google Thread border routers. Using HA as Thread Border router is still a bit on the experimental side and we do not yet support all flows. As you're saying its just for fiddling around, the SkyConnect as Thread Border router is great.

worthy hamlet
#

got it, thanks

timber hinge
#

I'm also having this same issue. Any way to keep track on this?

fading laurel
timber hinge
#

When trying to connect a device to home assistant using matter theiugh thread and skyconnect, on android I get through the connection setup and scanning the matter id. It progresses to the point of "checking network connectivity" then just hangs here and fails

fading laurel
#

Using the SkyConnect (or HA Yellow) is still in development and not fully stable yet, in any case the multi protocol firmware is suffering some issues so for now our advice is;

  1. To use Apple or Google border router(s) instead of the SkyConnect.

  2. If you do not have an existing Apple or Google border router and want to use the SkyConnect, you can only use an Android phone to commission devices.

timber hinge
#

I don't have any other border router, and the issue im having is with an android phone, specificlly pixel 7

fading laurel
#

Also is HAOS running on bare metal or hypervisor?

timber hinge
#

Same network nothing fancy. Is running through Ubiquiti suite but everything is on the same layer. Theres no seperate networks or VLANS, no mdns forwarders.

#

HAOS running on Hypervisor through proxmox

worthy hamlet
#

I got a second thread/matter lightbulb today and was able to add that without issue

#

I do have vlans setup, phone is on the same vlan as HA

#

I used to run HA on proxmox and may again in the future but right now it is running directly on an rpi4

fading laurel
timber hinge
#

I forgot to mention I resolved my issue. It was simply my pixel phone was handing out old credentials so it never connected

#

I moved back to my separated vlans for servers iots and home devices and home assistant virtualized on proxmox

#

Setup home assistant and matter till the very end