mDNS integration and Web UI connection documentation (Fixes #451)#519
Open
wbhinton wants to merge 1 commit intoExpressLRS:masterfrom
Open
mDNS integration and Web UI connection documentation (Fixes #451)#519wbhinton wants to merge 1 commit intoExpressLRS:masterfrom
wbhinton wants to merge 1 commit intoExpressLRS:masterfrom
Conversation
jurgelenas
requested changes
Apr 4, 2026
| - http://10.0.0.1/ - If you have connected to the `ExpressLRS RX` Access Point | ||
| 3. Load the Web UI on your browser. The address depends on how the Receiver is connected: | ||
|
|
||
| * **Access Point Mode:** If you are connected to the `ExpressLRS RX` WiFi hotspot, use [http://10.0.0.1/](http://10.0.0.1/). |
Member
There was a problem hiding this comment.
This is not correct. elrs_rx.local. and others should work even in AP mode.
In fact, in AP mode - all hostnames should be resolved to the device IP address.
|
|
||
| 3. Load the Web UI on your browser using these addresses: | ||
| - http://10.0.0.1/ - If you have connected to the `ExpressLRS TX` Access Point | ||
| 3. Load the Web UI on your browser. The address depends on how the TX Module is connected: |
Member
There was a problem hiding this comment.
This is not correct. elrs_rx.local. and others should work even in AP mode.
In fact, in AP mode - all hostnames should be resolved to the device IP address.
| On some devices a network login prompt might pop up. Clicking this will often show an incomplete version of the webui that won't behave as expected. Please navigate to http://10.0.0.1/ manually in your browser instead. | ||
|
|
||
| - http://elrs_tx.local - If you have previously set your Home WiFi SSID and Password into your TX Module when you flashed it. | ||
| * **Home WiFi Mode:** If the TX Module is connected to your local network, use [http://elrs_tx.local/](http://elrs_tx.local/). |
Member
There was a problem hiding this comment.
This is not correct. elrs_rx.local. and others should work even in AP mode.
In fact, in AP mode - all hostnames should be resolved to the device IP address.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR resolves Issue #451 by documenting how users access the ExpressLRS Web UI using http://elrs_rx.local/ and http://elrs_tx.local/ .
Key Changes
Glossary Expansion (glossary.md): Added a formal definition for mDNS to explain the technical foundation of .local resolution.
Web UI Access Documentation (webui.md): Restructured access instructions into clear Access Point Mode vs. Home WiFi Mode sections for both RX and TX. Integrated mDNS hostnames as the primary access method for networked devices.Added arp command guide with specific Espressif MAC prefixes (30-ae-a4, 24-4c-6a, 84-f3-eb) to help users identify ELRS hardware in a list of dynamic IPs. Added the Router DHCP guide with specific device naming conventions (elrs-tx/elrs-rx).
Connection Troubleshooting (troubleshooting.md): Added a dedicated section for "Cannot reach .local addresses," covering common blockers like AP Isolation and OS compatibility.
Related Issues
Closes #451