fix(docs): clear stale drone/operator map markers via availability gates#53
Merged
Conversation
Drone and operator markers lingered on the HA Map long after a track was gone. The service clears tracks correctly (purge at expire_after_s -> nearest_drone topic empty-retained -> sensor unavailable), but a Map marker only disappears when its entity goes unavailable, and the example `Airspace Drone Operator` template sensor had no `availability` clause. Its state is `operator_id or 'operator'`, which never evaluates falsy, so the sensor stayed available with stale/None coordinates and the operator pin persisted indefinitely. Gate the operator sensor on the nearest drone being live and having a broadcast operator position, and tighten the aircraft/drone markers to also require a non-null latitude. Now markers clear when the service purges the track. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drone and operator markers lingered on the HA Map long after a track was gone. The service clears tracks correctly (purge at expire_after_s -> nearest_drone topic empty-retained -> sensor unavailable), but a Map marker only disappears when its entity goes unavailable, and the example
Airspace Drone Operatortemplate sensor had noavailabilityclause. Its state isoperator_id or 'operator', which never evaluates falsy, so the sensor stayed available with stale/None coordinates and the operator pin persisted indefinitely.Gate the operator sensor on the nearest drone being live and having a broadcast operator position, and tighten the aircraft/drone markers to also require a non-null latitude. Now markers clear when the service purges the track.