Prerequisites
Problem Statement
I saw that Meshtastic 2.7 is going to remove the web UI from the ESP32 devices. I'd like to run the Meshtastic web client at home, and I see there are already pre-built container images published.
However, it is kind of annoying to have to remember my node's IP address each time I want to connect.
Proposed Solution
It would be nice if there was the ability to overwrite the meshtastic.local default hostname with my node's hostname/IP, using something like an environment variable in the Docker container.
|
const { control, handleSubmit, register } = useForm<FormData>({ |
|
defaultValues: { |
|
ip: ["client.meshtastic.org", "localhost"].includes( |
|
globalThis.location.hostname, |
|
) |
|
? "meshtastic.local" |
|
: globalThis.location.host, |
|
tls: isURLHTTPS ? true : false, |
|
}, |
|
}); |
That way, when I load the page, it would already be populated with my node's hostname/IP, and I would just need to click "Connect".
Current Alternatives
No response
Importance
Nice to have
Additional Context
No response
Prerequisites
Problem Statement
I saw that Meshtastic 2.7 is going to remove the web UI from the ESP32 devices. I'd like to run the Meshtastic web client at home, and I see there are already pre-built container images published.
However, it is kind of annoying to have to remember my node's IP address each time I want to connect.
Proposed Solution
It would be nice if there was the ability to overwrite the
meshtastic.localdefault hostname with my node's hostname/IP, using something like an environment variable in the Docker container.web/packages/web/src/components/PageComponents/Connect/HTTP.tsx
Lines 35 to 44 in 2e2b007
That way, when I load the page, it would already be populated with my node's hostname/IP, and I would just need to click "Connect".
Current Alternatives
No response
Importance
Nice to have
Additional Context
No response