blog/choosing-the-right-device-role/

[giscus[bot]]

blog/choosing-the-right-device-role/

When setting up your Meshtastic network, configuring the correct Role for each device can be crucial for optimizing performance and ensuring reliable communication. Conversely, the pitfalls of choosing the incorrect Role can lead to congestion and poor performance on your mesh. In this post, we'll explore why you might choose certain device roles and avoid others.

https://meshtastic.org/blog/choosing-the-right-device-role/

[Whisky-Guzzler]

Great for us helpful, but ignorant folks. This kind of information has kept me from running a repeater from on my roof.

[melroy89]

Try to set it to CLIENT_BASE maybe?

[dreimal8]

When i set client role to "client_mute", the rebroadcast setting stays still on "all". That is confusing me...

[RealityTrustLTD]

Thank you for this :)

[jwheeler188]

Further to the above, when you set your device to router/repeater/router_client any devices that can hear you, will never pass messages of others along the mesh if you pass them also. You will completely cripple the local mesh and create a mesh island. Effectively limiting anyone near you to your footprint.

[Jaramos76]

Is there any way that I can setup and use a Dragino LPS8 LoRaWAN Gateway with meshtastic

[garthvh]

No lorawan gateways are supported

[adrianTNT]

It would be nice if each device could set the right mode automatically, maybe after some packets were send/received, then over time that can again be re-evaluated.
Maybe have an "AUTO" mode default, and have the rest be selectable by user (client, router, client-mute, etc).

[dzaragoza]

Good guide! Can you please also explain the ROUTER_LATE role?

[soupysoap]

This doesn't cover all the available modes

[inlinerbutch]

Hello,
I would like to configure one device (Heltec V3) with the role Client_Base but the IOS app and Android app doesn't provide this role. Is it dependent on the hardware or region? How can I get the role working for the heltec V3?
Thanks,
Uwe