Tracking a Client Not Working After Moving Between Areas

[rookster1984]

I have set it all up and set the tracking duration. It worked at first but stopped working even when it comes back to orginal place.

I think its due to it been moved between repeaters, the path is still wrong when it comes back home even after hours, then the gps goes to unavaible.
I have tried to look for a way to reset the path in the HA meshcore gui. I tried to find a away to reset it too using a automation but cant see how.

[awolden]

Make sure you are on the latest version. There have been some bug fixes around repeater path resetting. It should reset after 3 failures now.

[rookster1984]

I did got the files off here 2 days ago and uploaded them all manually, when was this fixed please?

[rookster1984]

Just checked i have this version: Version 2.1.10

[rookster1984]

Its been next to the base station for the last 2 hours, i can connect fine on the app.

[awolden]

Check the routing path sensor did it ever change? It’s also weird that it’s taking 2 hops to get to it despite being right next to it

[rookster1984]

Is this what you need?

[rookster1984]

So the tracker went out this morning about 5 hours ago its set it to that path and not reset it since i think.

[awolden]

So it looks like it reset 3 hours ago.

https://github.com/meshcore-dev/meshcore-ha/blob/main/custom_components/meshcore/coordinator.py#L475 the logic is there

When you say connect fine on the app are you connecting directly or from another node? I would also try reloading the integration. If it’s still not working I might need to try to reproduce or get debug logs.

[rookster1984]

So direct yes, tried via the house repeater that also works, tried the path its trying to use on the Meshcore HA and that doesnt work. restarted the integration and it said changed to 72d6 15:59:45 - 2 minutes ago, which is the wrong path still. I tried a full HA Restart and now its reset the path to 0 hops and works again.

[rookster1984]

Is it supposed to reset path after each fail? or is it set to some other thing.

[awolden]

No it only resets after 3 failures in a row if it has a path

[rookster1984]

Oh could that be a issue? is there a way for me to force a reset at all? or change the setting?

[awolden]

Yes you can execute a service/action that should reset the path

service: meshcore.execute_command
    data:
      command: "reset_path {PREFIX}"

[awolden]

Just pushed a v2.1.11 that may potentially improve this. It's a fix to make sure the integration doesn't inadvertently miss resetting the path. Haven't been able to test it, but it has a decent chance of improving the situation for you.