Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESPHome Devices #6

Open
redstorm1 opened this issue Jan 25, 2022 · 7 comments
Open

ESPHome Devices #6

redstorm1 opened this issue Jan 25, 2022 · 7 comments

Comments

@redstorm1
Copy link

Tried the tunneller with ESPHome devices such as ESP8266 that utilize mDNS for discovery.
Unfortunately the Home Assistant server still could not discover devices on the remote network.

Tried tunneller Server on HA network and client on device network and vice versa.
Networks are connected via wireguard with routing in place and tested.
192.168.1.x HA server
192.168.2.x Remote devices.

Maybe I have missed something in my config??

@toxuin
Copy link
Owner

toxuin commented Jan 25, 2022

Doesn't look like you've missed anything! Relative positions of server and client do not matter: once they connect to each other - they begin communicating both ways.

What's in your config? I don't know what type of packet does ESPHome send for discovery. You can find out by enabling debug mode and/or using something like Discovery (Mac) app or Bonjour Browser (Win).

Also, app logs with debug enabled would help me help you troubleshoot :)

@redstorm1
Copy link
Author

Debug mode, is their a config switch for enabling?
debug =true

@redstorm1
Copy link
Author

redstorm1 commented Jan 25, 2022

console output
Started server on 192.168.2.1,eth0:42069 Client connected: ::ffff:192.168.1.12:50884

@redstorm1
Copy link
Author

This might help, tcpdump on the client network.

192.168.2.4.5353 > 224.0.0.251.5353: 0*- [0q] 4/0/1 _services._dns-sd._udp.local. PTR _esphomelib._tcp.local., _esphomelib._tcp.local. PTR axolotl._esphomelib._tcp.local., axolotl._esphomelib._tcp.local. (Cache flush) SRV axolotl.local.:6053 0 0, axolotl._esphomelib._tcp.local. (Cache flush) TXT "board=nodemcuv2" "platform=ESP8266" "mac=e8db84974747" "address=axolotl.local" "version=2021.9.3" (270)

This is a ESP8266 with various sensors monitoring my Axolotl tank

Added this to the configs on both
- '_esphomelib._tcp.local'

unfortunately still not discovering

@redstorm1
Copy link
Author

redstorm1 commented Jan 25, 2022

I moved the line to the top in the serviceWhitelist and they now are discoverable but only for about 1minute then the remote ones go offline again.

`serviceWhitelist:

  • "_esphomelib._tcp.local"
  • "_homekit._tcp.local"
  • "_hap._tcp.local"
    `
    Update, they appear to drop in and out of being discoverable, so records not persisting very long before aging out

@toxuin
Copy link
Owner

toxuin commented Jan 25, 2022

Awesome, that's some progress!
You need this setting in config on both client and server by the way.
About why it drops off after 1 minute - I am not sure.

@redstorm1
Copy link
Author

Config applied to both

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants