mDNS integration and Web UI connection documentation (Fixes #451)#519
mDNS integration and Web UI connection documentation (Fixes #451)#519wbhinton wants to merge 1 commit intoExpressLRS:masterfrom
Conversation
| - 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/). |
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.
There was a problem hiding this comment.
I will get that fixed. I did test out the AP mode and while all hostnames did resolve to the WebUI when I typed them in directly to the address bar, if there was a link I clicked, like a bookmark it did not always redirect to the WebUI. This was on Windows 11 in Chrome.
Does it work for you if I reword it stating that the AP mode should resolve any hostname, but that 10.0.0.1 can be used in case that doesn't work?
|
|
||
| 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: |
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/). |
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.
2 participants
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