Skip to content
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

Fallback when atimuth entity has state "unknown" #176

Open
andilge opened this issue Mar 29, 2021 · 1 comment
Open

Fallback when atimuth entity has state "unknown" #176

andilge opened this issue Mar 29, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@andilge
Copy link

andilge commented Mar 29, 2021

Hi there,

I’m using the compass card for lightnings, add-on blitzortung.org and it works flawlessly. I have one little problem though, when there is no lightning activity (95% of the time) the add-on brings back “unknown” in the azimuth entity and compass card falls back to default azimuth 0°, north. Please find cause and effect in the picture attached. I've also attached my lovelace card if it's necessary to reproduce the case.

Since “unknown” is not an integer or float value, the band filter doesn’t show any effect. As a result many times I have zero lightning in north which is a bit annoying., but not really a problem => low prio enhancement.

I'd like if there was either a filter for "unknown" or a transformation into a negative number like -361 (one more degree than a full circle).

All the best, Andi

azimuth entity + lovelace card
lovelace card.txt

@tomvanswam tomvanswam added the enhancement New feature or request label Mar 29, 2021
@tomvanswam tomvanswam self-assigned this Mar 29, 2021
tomvanswam added a commit that referenced this issue Jan 17, 2022
tomvanswam added a commit that referenced this issue Apr 13, 2022
tomvanswam added a commit that referenced this issue Apr 13, 2022
@tomvanswam
Copy link
Owner

All degrees outside of 0-359 get recalculated to be between 0 and 359.
So having a value of -361 would get recalculated to 359 and show there.

I'll look into having a separate filter for non numeric values as this could help out with issue #778

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants