[Feature Request]: Conditional muting

[Jckf]

Platform

Cross-Platform

Description

Would it make sense to implement conditional muting, where a CLIENT automatically goes into CLIENT_MUTE when within range of one or more of a pre-defined list of nodes?

Example: I have a roof node, a car node, and both my SO and I have personal nodes on us. When we're at home, all four nodes are within 15 meters of each other at all times and are likely to see a lot of the same traffic. But the ONLY one of these nodes that should be rebroadcasting in this scenario is the roof node, because it has the best position and range.

Then imagine we take the car and leave home, and that we stay within range of the car where ever we go. It then makes sense for the car to be the only node rebroadcasting, because we are likely inside a building - while the car is outside on the street.

And the third scenario is that we've left home and are NOT in range of the car. Then the nodes we carry on us should act as normal CLIENTs.

Having to manually configure this when we move around is not feasible, so if we could configure the nodes to automatically switch between CLIENT and CLIENT_MUTE based on the nodes within 0 hops (and some signal strength), then that would likely be a benefit to the mesh.

EDIT: Instead of switching to CLIENT_MUTE, it probably makes sense to instead change the rebroadcast mode.

[b8b8]

This has been suggested before as a "home zone" radius to automatically switch to client_mute.

Perhaps it can be rolled into the new client_base role so if you are in range your base, you automatically become client_mute.

[pedjas]

Assuming that "within range of node" means has direct link to it, I would add suggestion that another criteria should be used together with being in range - distance from node.

I would like it to switch to non rebroadcasting mode only in near proximity of a master node.

[Jckf]

This has been suggested before as a "home zone" radius to automatically switch to client_mute.

That would work for the roof node, but not the car node. Unless we could have multiple homes, and the homes dynamically followed the nodes ofc.

Assuming that "within range of node" means has direct link to it, I would add suggestion that another criteria should be used together with being in range - distance from node.

Yes, I wrote "within 0 hops", but some limits for signal strength would probably also have to be a part of it.