[Bug]: Position log of 3rd party node fails to update after arbitrary amount of time

[b8b8]

Checklist

• I am able to reproduce the bug with the latest version.
• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.
• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the Contribution Guidelines.
• I agree to follow this project's Code of Conduct
• I actually read this list, and should be taken seriously.

Affected app version: 2.7.13
Affected Android version: 16
Affected phone model: Pixel 9a
Affected node model: T1000E HeltecV4
Affected node firmware version: 2.7.19 2.7.18

Steps to reproduce the bug

Setup:

• Personal Node: T1000E, 2.7.19 - battery operated
• Car node: Heltec V4, 2.7.18 - hardwired to car
• Private primary channel, high precision packets
• Position broadcast interval 12 hours, smart distance 40m, smart interval 1minute, GPS polling interval 8sec (always on)
• Channel utilization in area: low 3%, air time: 0% to 1%
• I am in the car with my personal node and the car node is 2 feet above me on the roof

Testing:

1. Happen to manually request car node position
2. Drive around. Position log of car node on personal node updates as expected when highway driving as per smart position settings.
3. Park at home. Stay home for multiple hours (car node still hardwired, always powered etc.)
4. Leave home and drive around. Notice position packets and breadcrumb trail for car node do not update.
5. Notice individual node map for car node still says at home.
6. Manually request car node position far from home.
7. Car node breadcrumb trail now updates according to smart position settings for some arbitrary amount of time until i drive home again and car node does not send position packets again for some arbitrary amount of time and due to smart position settings.

Notes:

• was a problem the last few app releases, wasnt a problem in December i believe.
• freshly installed the app multiple times
• believed to not be a firmware issue as the 2.7.18 firmware has been operating on the car node for months without issue
• bluetooth connected T1000E has "blips" of missing position packets in its own breadcrumb trail, though not consistently.
• even though car node is moving around and (i assume) transmitting positions, last heard time does not update until you manually request position once, then it updates as expected approx. every 1 minute.
• all power savings options disabled
• personal T1000E continues to get updated packets from random other mesh nodes while driving around, so its not like the app is locking up.

Screenshots/Screen recordings

[b8b8]

@canadamadman please add any notes you have. I believe you have also experienced this.

[b8b8]

Next test:

• completely private channels on random preset so no other nodes but mine.
• one phone connected to personal node, one phone connected to car node

[b8b8]

Telemetry coming in automatically and correctly when set to 30min interval.

[b8b8]

Periodic position broadcast working when set to 15min.
Hmmmmmm

[b8b8]

@fifieldt have you noticed any smart position issues (not updating the position while moving) like above?

[fifieldt]

@fifieldt have you noticed any smart position issues (not updating the position while moving) like above?

I once noticed fewer positions than I expected on one device (using an older firmware, with later Android), but wasn't enough to cause me to immediately investigate. I'll keep an eye out.

[canadamadman]

i find its not just contained to the positions but it all the telemetry that's not being passed for some reason. as i have to manualy ask each node for its info to have even the battery up to date.

[b8b8]

Might need another tweak or two. Drove around for an hour today and had large (roughly 7min) gaps in position updates.
Manually requesting position of node seemed to allow it to record again.

Car node set to client_base if relevant. Channel utilisation remains low during test.