From the README's Development section - filing as a tracked issue.
Current state
Once a device leaves peer/captive-portal mode and joins a normal WiFi network (YY_MODE_CLIENT), there's no way to discover it on that network except knowing its IP directly (or via whatever the peer-list endpoints report while it's still in a peer network). No mDNS (ESP8266mDNS/ESPmDNS) responder is set up anywhere in YoYoWiFiManager.cpp.
Ask
Add zero-conf discovery once connected to a network, e.g.:
- mDNS/Bonjour (
MDNS.begin(hostname) + a service advertisement) - supported on both ESP8266 and ESP32 cores, so probably the more portable option, or
- iBeacon (ESP32-only, as noted in the README) if that's specifically useful for the Yo-Yo Machines use case (e.g. physical proximity discovery rather than network discovery)
Worth deciding which use case this is actually for (finding a device's IP on a LAN vs. proximity-based discovery) before picking an approach, since they solve different problems.
From the README's Development section - filing as a tracked issue.
Current state
Once a device leaves peer/captive-portal mode and joins a normal WiFi network (
YY_MODE_CLIENT), there's no way to discover it on that network except knowing its IP directly (or via whatever the peer-list endpoints report while it's still in a peer network). No mDNS (ESP8266mDNS/ESPmDNS) responder is set up anywhere inYoYoWiFiManager.cpp.Ask
Add zero-conf discovery once connected to a network, e.g.:
MDNS.begin(hostname)+ a service advertisement) - supported on both ESP8266 and ESP32 cores, so probably the more portable option, orWorth deciding which use case this is actually for (finding a device's IP on a LAN vs. proximity-based discovery) before picking an approach, since they solve different problems.