Support toggling "Mesh via UDP"

[vidplace7]

Please add support for toggling the new "UDP Multicast" feature added in

• Hello world support for UDP broadcasts over the LAN on ESP32 firmware#5779
• Add protocol flags to enable UDP broadcasts and other future local networking transports protobufs#643

Currently can only be enabled via Python with this config:

meshtastic ... --set network.enabled_protocols 1

Should be a boolean value to enable/disable, I imagine.

[github-actions]

Congratulations for your first issue

[vidplace7]

For the record, the UDP feature works great on TFT builds :) Would just be nice to be able to toggle it directly from the UI.

[mverch67]

What's the exact use case? What's the purpose of toggle?

[vidplace7]

What's the exact use case? What's the purpose of toggle?

This feature allows the node to mesh with other nodes via UDP Multicast, in addition to LoRa. This can enable some amazing stuff like bridging multiple presets / channels / etc.

The ability to toggle this on the device without having to program it via a Client would be just great!

[mverch67]

If it is toggled via MUI what data is expected to be seen in a (potentially new?) MUI panel? Just want to understand the use case for the MUI.

[vidplace7]

If it is toggled via MUI what data is expected to be seen in a (potentially new?) MUI panel? Just want to understand the use case for the MUI.

Just a toggle in the settings area is all that's expected. A new panel shouldn't be warranted.

UDP meshing simply forwards all packets to UDP Multicast (at a broadcast address) and listens for packets at that same broadcast address. For instance you could have multiple nodes on the same wifi network, each on a different modem preset / frequency, and bridge them via UDP.
MUI devices can participate in this UDP meshing if the config is enabled, and we want that to be easy.

[mverch67]

I still don't get the exact use case. The reason why I'm asking is because MUI is use case oriented. It's not a tool to toggle arbitrary switches. If there are participants in a UDP network why not show these other nodes as participants? That would make a use case. Otherwise why not have it enabled by default? What is the use case to disable the switch once it is enabled?

[aseiger]

Being able to know if it is on or off via the UI makes sense to me - otherwise it could be on or off and the user could have no idea. Once it's visible from the UI though, it makes sense to then be able to change it from the UI as well.

My 2 cents. Not really hurting anything, as having UDP meshing on all the time doesn't really hurt anything. But for testing, playing about, etc. it is nice to know the status of core communication settings like that.