Set return path for repeaters

[mikecarper]

Adds repeater CLI support for viewing and controlling the current remote client's reply path.

• Adds get outpath
• Adds set outpath <hop1_hex,hop2_hex,...> 1,2,3 byte supported
• Adds set outpath clear forgets the current direct path and allows normal path discovery to repopulate it
• Adds set outpath flood forces replies to use flood packets until the client logs in again. Prevents discovered paths from overwriting flood mode while it is active

Why it's needed

This is the ideal path there, which I set
7773, 7E76, 11E1
But the path back is bad. It should be this
11E1, 7E76, 7773

I would like to be able to set the return path via the CLI
set outpath 7E76, 7773
In this case I get the login but nothing was given back to my client and so I get the timeout message.

[towerviewcams]

We need this so very much. I cant tell you how hard it is to get stats. Log in works fine but then its going to war with retries to get the info. @liamcottle hope you agree ? this would take away allot of traffic with tons of retries.

@IoTThinks can we try this in your next test firm?

[IoTThinks]

I always assume the out and return path (in reverse) are the same.
It should.

Hi @mikecarper,
Do we need to set this to all repeaters on the way back? Or just the repeater we want to remote manage to?

[mikecarper]

@IoTThinks just the one you're logged into needs the path set. Admin Repeater packets act like a DM where either side can set the path to the other end.

[IoTThinks]

@mikecarper Nice.
I will test with @towerviewcams

No idea if we can automatically set this out path when we select the path to Remote manage.
May be in next version?

I have this issue too.
But I thought due to big size of repeater stats.

[IoTThinks]

@towerviewcams This is PowerSaving 15.0.3 (based on Meshcore 1.15 main line) and this PR2586.
The code looks solid.
Please help to test.

https://github.com/IoTThinks/EasySkyMesh/tree/main/firmware/Testing/WirelessRocks/PR2586

[towerviewcams]

@towerviewcams This is PowerSaving 15.0.3 (based on Meshcore 1.15 main line) and this PR2586. The code looks solid. Please help to test.

https://github.com/IoTThinks/EasySkyMesh/tree/main/firmware/Testing/WirelessRocks/PR2586

I can confirm that this works and its sooooo nice! I have set 3 repeaters hex (3byte) and it replies with my set route for my companion. If i test with a second companion (different from first) then the return path is normal.

**Hope that next step on this can be to have a option for the "your logged in as Admin" green bar reply can auto add to reply the telemetry stats. As we all know that is always reliable as it follows the incoming path from the companion. But this is a GREAT step in the right direction and works!

very nice !!!!!!! @AI7NC @liamcottle @ripplebiz @weebl2000