mDNS
Maxim Prokhorov edited this page Nov 10, 2019
·
1 revision
| Configuration key | Build flag | Description |
|---|---|---|
MDNS_SERVER_SUPPORT |
(default:1) Enables additional ESPurna-specific values under the _arduino._tcp
|
|
MDNS_CLIENT_SUPPORT |
(default:0) Legacy option! Enables mDNS resolution for the MQTT broker.This option is no longer required when using Arduino Core version 2.5.2 and up |
When using MQTT_SUPPORT and MQTT_AUTOCONNECT, if MDNS_SERVER_SUPPORT is enabled, the device will try to search the local network for the _mqtt._tcp service. If found, it will be automatically connected to and saved into the persistent configuration.
When MDNS_SERVER_SUPPORT is enabled, ota.py script can be used to find devices on the current network.
If you're looking for support:
- Issues: this is the most dynamic channel at the moment, you might find an answer to your question by searching open or closed issues.
- Wiki pages: might not be as up-to-date as we all would like (hey, you can also contribute in the documentation!).
- Gitter channel: you have better chances to get fast answers from project contributors or other ESPurna users. (also available with any Matrix client!)
- Issue a question: as a last resort, you can open new question issue on GitHub. Just remember: the more info you provide the more chances you'll have to get an accurate answer.
- Backup the stock firmware
- Flash a pre-built binary image
- Flash a virgin Itead Sonoff device without opening
- Flash TUYA-based device without opening
- Flash Shelly device without opening
- Using PlatformIO
- from Visual Studio Code
- Using Arduino IDE
- Build the Web Interface
- Over-the-air updates
- Two-step updates
- ESPurna OTA Manager
- NoFUSS
- Troubleshooting
- MQTT
- REST API
- Domoticz
- Home Assistant
- InfluxDB
- Prometheus metrics
- Thingspeak
- Alexa
- Google Home
- Architecture
- 3rd Party Plugins
- Coding style
- Pull Requests