-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Comments
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 :) |
Debug mode, is their a config switch for enabling? |
console output |
This might help, tcpdump on the client network.
This is a ESP8266 with various sensors monitoring my Axolotl tank Added this to the configs on both unfortunately still not discovering |
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:
|
Awesome, that's some progress! |
Config applied to both |
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??
The text was updated successfully, but these errors were encountered: