-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filter (e.g., distance < X, altitude < Y) #12
Comments
I'm not sure yet how to implement it, but I'm thinking about something like this for the config: type: custom:fr24-card
entity: sensor.fr24_aircraft
filter:
type: or # and, or
rules:
- distance: <10
- altitude: >=5 This will work with both options for The syntax for the rules should support the operators Maybe in the future also a filter on columns with a text value. For example |
I've been looking for a solution to logging aircraft noise and being able to count aircraft within a set distance and below a set height would be great. It could also be refined further by aircraft type, speed/acceleration/etc. Is this possible? |
@robsymax I think that's beyond the scope of this card. This card is for showing the current tracked aircrafts. It won't store any data. Theoretically this is possible by calling HA's API and updating an entity, but I won't develop that. You can always fork this repo and open a PR if you have developed such functionality. |
Any update on the filtering please? Is it still planned to enable filtering by distance? |
It would be very useful if we could add filters to the aircraft displayed. E.g., I'd like to only show planes within 10 NM, under 10k altitude.
I'm not sure what the best syntax would be; there is an existing
hide: empty
option, but I'm not sure what the cleanest way to be would be represent the filters that need a value, and whether it should default toand
oror
(and how to specify the opposite behavior), which is one reason I'm not submitting a PR. (the other two are poor JS skills and extreme laziness!)The text was updated successfully, but these errors were encountered: