Default entity for the indicator is sun.sun with attribute azimuth. When you select another entity from the list, the card does not clear the attribute. And the newly selected entity probably does not have an azimuth and thats why the indicator shows the default N.
Unfortunately not yet.
Iām not sure what causes this, as Iām not able to reproduce this.
Could you open an issue on the github page? Please add your config of the card, info on what themes you use?
This also helps me keeping this on my radar when I have a spare hour.
Great stuff, @tomvanswam! Just discussed with my kids that itād be cool to have wind visualized with a compassāhere it comes
North offset is awesome: now I can adjust the compass to match orientation of the display. Is it possible to put a custom image on the background? It could be a top overview of the house. So it would be nice to see, which windows wind actually goes.
I especially loved sun azimuth. However, it might be sensible to show it only when sun is actually above the horizon. Itās a little bit weird to see sun on the North. Additionally, I think sun elevation could be integrated into the compass: putting circle closer to the center depending on the angle.
This will hide the indicator for elevations less than 0.
Iām less fan of changing the location of the indicator towards the inside of the circle tbh, so I hope the config above will also serve your needs well enough.
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 entitiy and compass card falls back to default azimuth 0Ā°, north.
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.
Do you think itās feasible to integrate a general filter for āunknownā instead of the fallback to zero/north?
The sensor only works with numeric degrees (0-360) or cardinal directions abbreviated in English. Your sensor has the cardinal directions abbreviated in Dutch, so it displays the default north.
The direction abbreviation language is only for displaying the abbreviation, not for reading the abbreviation from the sensor.
Use the sensor.tuk_wind_direction_azimuth (enable in your configuration.yaml when needed) to get numeric values and use the card.