blog/why-your-mesh-should-switch-from-longfast/ #298
Replies: 7 comments 6 replies
-
|
Correct me if I'm wrong. I was told by people that preset names are used in MQTT topic hiddenly. That means a LongFast node which is connected to MQTT cannot talk to/see another node other than LongFast even if under the same topic. If I have to bridge two areas, A(LongFast) and B(MediumSlow), how to connect them via MQTT? |
Beta Was this translation helpful? Give feedback.
-
|
Some friend and I in California have switched over to the longMod preset and have enjoyed the lack of message clutter. The one thing that we have had problems with is that mqtt does not seem to work with longMod. We can't get it to work. Any suggestions for a solution? |
Beta Was this translation helpful? Give feedback.
-
|
I guess it's to much to ask for a node setting that can serve multiple roles. Have your long haul routers use Long. Which can in turn send Long to Medium client nodes. Then use Medium to Short for Client Mutes. The suck is you can't bounce things across MQTT between Long/Medium/Short because the topic is different. |
Beta Was this translation helpful? Give feedback.
-
|
In my opinion everything lay in good defaults and documentation. If user can easily understand in UI what any setup mean they could easily adjust. |
Beta Was this translation helpful? Give feedback.
-
|
Hello from Brno, Czech Republic. As of February 2025, the Brno mesh network became reliable on LF under the following conditions:
I assume similar requirements will be necessary to achieve a reliable MediumFast network. This is supported by the experience in Brno, where MF node clusters that don't meet these conditions have shown poor performance and unreliable connectivity. Unless you have same conditions (...even better due to MF limits) do not migrate to MF. You can find more details in my blog (in Czech), but Google Translate works well for it. |
Beta Was this translation helpful? Give feedback.
-
|
Will multi transceiver support be implemented for repeaters/routers so that they can be used to build an LF backbone with MF local presets? Or even local backhaul over MF with SF locals? Or alternatively, will Meshtastic be supporting mesh IDs so that a mesh can run in parallel and be able to bypass existing meshes with sub-optimally configured presets? |
Beta Was this translation helpful? Give feedback.
-
|
In my area, there aren't a lot of nodes.. So we are still using LongFast on all the nodes. Which is still the best default in this case. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
blog/why-your-mesh-should-switch-from-longfast/
Improve your local mesh network by moving away from the default LongFast preset to higher bandwidth options
https://meshtastic.org/blog/why-your-mesh-should-switch-from-longfast/
Beta Was this translation helpful? Give feedback.
All reactions