#ESPHome device adding to the system by Open Thread Border Router by openthread component is not reac

1 messages · Page 1 of 1 (latest)

twilit pewter
#

I have build open thread border router I use S3 + H2
Installed:
basic_thread_border_router on S3
ot_rcp on H2

Works fine. it starts. in logs everything works good. S3 connect to my IPv4 WiFi network. create Thread network. I am able to access WEB interface by http://192.168.1.93 address

I use http://192.168.1.93 address to add this border router to my Home Assistant in “Open Thread Border Router” extention. and it added. so Home Assistant see my border router.

After that I have took another ESP32 H2.
Installed on it ESPHome with the following config

api:
encryption:
key: "..."

ota:

* platform: esphome
password: "..."

network:
enable_ipv6: true

openthread:
device_type: FTD
tlv: ...

After that if I visit open router web interface by http://192.168.1.93 and use Topology in the bottom of page I can see that new device added to the network with “Child” role.

in case I connect with monitor to new device, I can see that all the text sensors are filled good and SRP client starts

[D][text_sensor:113]: 'Thread IP Address' >> 'fd5e:8daa:5d8e:1:5230:d7c5:c4af:8fe7'
[I][openthread:114][ot_main]: SRP client has started
[D][text_sensor:113]: 'Thread RLOC16' >> '4001'
[D][text_sensor:113]: 'Thread Device Role' >> 'child'

After that I coming to home assistant device and services and Home Assistat show me that my new device “5 ESP32 H2 Zero (5-esp32-h2-zero) ESPHome” is discovered.
I try to connect it to my Home Assistant and it writes to me that it’s unable to connect to host “fd5e:8daa:5d8e:1:5230:d7c5:c4af:8fe7”.

But if I right understand my border router should catch this host and send it to thread network?

Can somebody help please how to connect devices which connected to border router to Home Assistant?

wise patrol
#

This should be working, indeed I have it working on my own system (I use the esp thread br devkit rather than separate s3 and h2, but otherwise very similar).

#

How is home assistant installed, and how is your home network set up?

#

the discovery working means that home assistant is able to resolve mdns queries answered by the thread border router, but the unable to connect error suggests that home assistant is not receiving the ipv6 router announcements sent by the thread border router.

twilit pewter
#

home assistant installed as Home Assistant OS on rosberry PI 5
may be there is some setting that should be switched on in “idf.py menuconfig” or default values are good?

wise patrol
#

can you check your network settings on HAOS to make sure that ipv6 support is enabled?

twilit pewter
#

checked. it's look like this: screenshot attached.

Screenshot_at_Feb_22_20-23-58.png
wise patrol
#

automatic is correct, but it should have received an additional ipv6 address that starts with fd from the thread border router

#

it hasn't, which means either:

  • the thread border router isn't correctly sending the router announcements, or
  • something in your network is blocking the router announcements so home assistant doesn't receive them.
#

You never answered the second part of my question: How is your home network set up? What hardware are you using for router/wifi?

twilit pewter
#

My home network setted up by router from my service provider. it looks like some type of huawei router with custom firmware.
HA is connected by LAN
my devices and my laptop are connected by WiFi.
By I am able to connect HA by locatl adress 192.168.1.75 registered by LAN conections. traffic between networks (LAN \ WiFi) is open and not blocked.
Also I have got some more logs from my border router. I looks some strange repeated messages every several second. May be it is my problem?


I (45292) OPENTHREAD: NAT64 ready
E (45292) OPENTHREAD: Failed to probe backbone multicast listeners
I(45442) OPENTHREAD:[N] MeshForwarder-: Failed to send IPv6 UDP msg, len:110, chksum:6fd8, ecn:no, to:6e1b7858c05cb0fb, sec:no, error:NoAck, prio:net
I(45442) OPENTHREAD:[N] MeshForwarder-:     src:[fe80:0:0:0:c495:ebff:40d9:c9ee]:19788
I(45442) OPENTHREAD:[N] MeshForwarder-:     dst:[fe80:0:0:0:6c1b:7858:c05c:b0fb]:19788
I (46322) OPENTHREAD: NAT64 ready
I (46322) OPENTHREAD: NAT64 ready
I (46902) OPENTHREAD: NAT64 ready
I (46902) OPENTHREAD: NAT64 ready
I (47922) OT_STATE: Set dns server address: FD5E:8DAA:5D8E:2::808:808
I (47922) OPENTHREAD: NAT64 ready
E (49282) OPENTHREAD: Failed to get LL address, error: Invalid If index
W (49282) OPENTHREAD: Failed to send ND6 message
E(49282) OPENTHREAD:[C] BorderRouting-: RsSender: Failed to send RS 1/3: Failed
E (53302) OPENTHREAD: Failed to get LL address, error: Invalid If index
W (53302) OPENTHREAD: Failed to send ND6 message
E(53302) OPENTHREAD:[C] BorderRouting-: RsSender: Failed to send RS 1/3: Failed
E (57322) OPENTHREAD: Failed to get LL address, error: Invalid If index
W (57322) OPENTHREAD: Failed to send ND6 message
E(57322) OPENTHREAD:[C] BorderRouting-: RsSender: Failed to send RS 1/3: Failed
wise patrol
#

yeah, those logs look like a problem, but i wouldn't know where to look to debug that.