shortwavesurfer2009 on Nostr: It appears we may be getting a new role in #Meshtastic called CLIENT_BASE. It acts as ...
It appears we may be getting a new role in #Meshtastic called CLIENT_BASE. It acts as a ROUTER for favorited nodes such as your personal T-Decks, T1000-E, MeshPocket, etc but acts as a standard CLIENT otherwise.
You would put the CLIENT_BASE node in your attic, on your flagpole, or on your roof and set your personal nodes as favorites. That way a weak 3rd party CLIENT with low SNR does not take priority over your much better positioned high node.
The OP in this github issue had a node on his house that wasn't getting utilized because another client in somebody else's house farther away was getting the signal weaker and rebroadcasting it first.
https://github.com/meshtastic/firmware/issues/7863 Published at
2025-09-17 12:58:17 CESTEvent JSON
{
"id": "885ca744a45e9b079977900e628fc88486e569726cce96db4307bdbecc68a2b4",
"pubkey": "465eb13404d7219cd91c2b4a8a7e308ad4e09bc1298dc08c5eec852e9bf5da09",
"created_at": 1758106697,
"kind": 1,
"tags": [
[
"t",
"Meshtastic"
]
],
"content": "It appears we may be getting a new role in #Meshtastic called CLIENT_BASE. It acts as a ROUTER for favorited nodes such as your personal T-Decks, T1000-E, MeshPocket, etc but acts as a standard CLIENT otherwise.\n\nYou would put the CLIENT_BASE node in your attic, on your flagpole, or on your roof and set your personal nodes as favorites. That way a weak 3rd party CLIENT with low SNR does not take priority over your much better positioned high node.\n\nThe OP in this github issue had a node on his house that wasn't getting utilized because another client in somebody else's house farther away was getting the signal weaker and rebroadcasting it first.\n\nhttps://github.com/meshtastic/firmware/issues/7863 \n\n",
"sig": "9576d9c30898b0112af9b51eab1f16b034160322f7ee1e7210e85ea36f7c33d78e6da8d78c86bbb166640a57092655cc1ef3614abd9486f7e5c5ae219fe35daa"
}