It maybe the name entity_forecast_icon (emphasis on “icon”) that is confusing, but the card is getting the “state” of the entity configured by entity_forecast_icon and then uses this state (sunny, rainy, cloudy, etc) to figure out which SVG file (i.e. icon) is to be displayed. There are several SVG files that come with the pwc card and there is an option to use a URL to point to your own SVG files, but as far as I know, the entity_forecast_icon is not intended to be an icon.
After a recent update (I honestly don’t know which, probably Pirate Weather, my weather data source), my precipitation accumulation is showing 11 digits after the decimal… which is pretty good, considering it’s barely accurate to one digit before the decimal:
There doesn’t appear to be an option within the card to truncate or round or set the number of decimals to display; that option exists only for temps and rainfall in the slots.
I glanced through the code, and I agree that there isn’t a configuration option available for this.
The only option I can think of would be to use a template sensor and use the round(2) function.
How’s that look in YAML? I have some styling code that prevents me from using the UI. I guess I can just create a dummy card next time I get in front of my PC.
Is this card still active as there hasn’t been any action on github for 2 years. I’m finding that the card no longer displays the sunrise and sunset times with the new sun2 integration in HA.
Ohh, I see. I was on my phone looking at that image… that’s just the entity settings screen. Yeah, I’ve tried that and it doesn’t actually change the value of the sensor, which is what’s displayed (in the raw) in this card.
Is the “sun2” a custom integration?
Anyway, just glancing through the code, the PWC appears to model the requirements after the HA “sun” entity as the PWC requires that the configured entity have attributes: next_rising and next_setting.
Yes it is a custom integration, it appears not to have the same attributes, I may need to sit and work out how to create the relevant sensor, or just leave both integrations there for now.
All the config options are valid in yaml as well as GUI. You can see the yaml even while you are configuring the card - it’s the code button or something like that.
It’s still supported and works fine. If you are having problems with certain data, check the configuration and make sure the sensors exist and are providing data.
I wasn’t referring the configuring the card. I was talking about trying to change the Precision of the sensor display to remove decimal places in my replay to DeltaNu1142
I never said that was an option only that anything you can do in the GUI config you could do in YAML. You seemed to be saying some things can only be done in the GUI. @DeltaNu1142 probably needs to use a template sensor and then use that entity for the card
That’s what I was telling you a second ago. That the precision cant be done in YAML via the card, ie: I wasn’t talking about the card. Sure he can create a template sensor but my original reply to him was that I was hoping to fix his issue with a simple config via the entity settings. You can’t set Precision via YAML from what I understand, hence your solution to create a template sensor.
Yes you can, I literally showed a screenshot of where to do it. Like I said, I was not talking about the card config. I was hoping that the card would adopt the display as set by the entity precision setting, but unfortunately it didn’t.
