[Feature request] Companion Node Relay.

[mcneely]

Prior Understandings:

• Moving a repeater around, destabilizes the Network
• Flood repeating creates too much noise, reduces hop count, etc..
• small devices like credit card sized have limited range and may not reach a repeater.
• there is a desire for base nodes in cars that rebroadcast short range devices to a longer range to repeaters.
• meshcore supports companion repeater for adhoc situations in remote areas but restricts you to a specific frequency. Doesn't allow repeating to the general network.

Proposal: Companion Relay.

• Involves setting a limited list of companion nodes that a designated companion will listen for and rebroadcast
• mechanism can be put in place to disallow companions rebroadcasting each other if needed.
• Allows for car nodes that won't destabilize the network as a mobile repeater would.

Nice to have:

• Ability to manage relay node from the clients on the list.

[zevaryx]

Someone was experimenting with this, here's their fork: https://github.com/ZaosDaOne/MeshCore-relay/tree/relay

[wesselah]

Feels like going back to meshtastic . The reason repeating on a companion to use fixed freq. has a reason. People would forget to disable it and the mesh is already very crowded this would make it worse. And the mesh would collapse . And when you need better range buy a decent companion

[mcneely]

Feels like going back to meshtastic . The reason repeating on a companion to use fixed freq. has a reason. People would forget to disable it and the mesh is already very crowded this would make it worse. And the mesh would collapse . And when you need better range buy a decent companion

ooh, you invoked the word "Mashtastic" maybe you should have also mentioned "Andy Kirby" in your sentence as well. I presented real world issue and your solution is "buy better hardware"? Neither Meshcore or Meshtastic get it fully right, The evil Voldemort Meshtastic does a better job at address smaller and more portable nodes, such as ones that you keep in your pocket or wear around your neck. The solution I suggested addresses this need with massive noise reduction by limiting the nodes that get repeated. 1 node repeating 1 node is way different from every node repeating every other node. It addresses issues a lot of us have particularly in place where we don't live on a island or in a large city where there is mass coverage.

If you have a better solution than "buy better hardware", by all means suggest it. Otherwise please keep your useless toxic commentary off my thread.

[wesselah]

I did not mean to be disrespectfull really not and i get your point but having a node at you with limited range that can reach your “car node” which then seems to have a better reach means yoy already have two nodes when that car node serves more companion as you suggest it just acts as an repeater. Mobile car nodes (repeaters)are not disruptive t0 the mesh , people talking about meshcore advantage is using path did not read the docs
All messages send are flooding except dm which will use flooding if user wanted to be reach is not availible through the previos learned path
So the car node if beeing a repeater will not harm the mesh because off the default behavier being using flooding
I get the point that switching a companion for a limited time to repeater modus in the normal freq settings could have some bennefit because you could use it normal when not needed
But setting up a “ normal repeater” in or on top of your car would not be a big deal and will again not harm the mesh
Again i did not want to be rude if that is what you felt

[aclaghorn]

I think this is a great idea.

Having a mobile vehicle roof repeater nearby when I'm carrying a T1000E would solve a great number of issues I have using the mesh.

This issue is similar to #2261