Stale Meshtastic nodes not filtered out

[paulmandal]

Stale Meshtastic nodes not filtered out

[paulmandal]

This should fix it: #69

Sorry I haven't been around much this week, super busy at work. I am going to be working on Play Store assets and getting everything else ready for signing by the TAK Product Center in the next couple of days.

[a-f-G-U-C]

Thanks for fixing, and don't worry about the delays. I hope all is good at work.

I think the fix was successful in filtering the stale node noise, however now I had one case of an active standalone node that didn't get picked up at all! I didn't get a chance to check the source (will do later today), but: are you still querying the node list from the device at all, or are you relying 100% on transition events?

Asking because this may explain my observation - a pre-existent, unmoving node wouldn't generate transition events and would therefore remain completely undetected by the plugin - which is probably not what we want.

[a-f-G-U-C]

Yes, issue confirmed. Static non-TAK nodes are not being picked up at the moment.

[a-f-G-U-C]

This could be just an unfortunate coincidence with a Meshtastic-device issue occurring around the same time.
See meshtastic/firmware#506

For now, please disregard my previous comment.

[a-f-G-U-C]

closing - not a real issue