it seems like I can’t really test it.
Not sure if NWS is using some kind of geofencing?
I added a weather station and in the details of the entity it loads endless.
But when I go to developer tools → actions → weather.get_forecasts and try to get daily forecasts, it tells me the integration wouldn’t provide the daily type.
So yes, this most likely is the problem.
Are there more weather services that provide weather data only that way?
Never seen this before.
All my weather entities aren’t providing these twice-daily reports.
I’m not sure, I’m very new to HA in general, not to mention HACS and custum repositories (haha). Oh well, I’ll tinker with it and report back with any helpful findings. Otherwise I’ll just use Open-Meteo and depend on humidity from other sources.
Thanks for the response!
EDIT: I do see that the format twice per day actually means: “Day” which is the high for the day, and “Night” which is the low for that same day. I have no idea if it’s possible to fix this with editing some code, but I would need somebody to explain it if so. Don’t worry about it if it’s a hassle.
You can switch the chip mode to template in this case, to display your NWS humidity value, while still using the meteo weather entity for the forecast.
I use this for example to show the humidity of my own outdoor sensor: Humidity: {{ states('sensor.multisensor_zufahrt_humidity') | round(0) }}%
To use the attribute from a weather service it should look like this I guess: Humidity: {{ state_attr('weather.wetter_zuhause', 'humidity') }}%
I’m pretty sure I know what your telling me to do, but to this point I’ve only been making changes via the GUI. Which file should I edit to make those changes? I’m running HAOS on a laptop if that helps.
Ah, well. The learning curve on HA can be quite overwhelming.
A template allows you to replace the code within a text.
It uses Jinja as syntax and the general docs can be found here.
You will also find the state_attr function used in my example there.
In the weather cards UI editor, there’s an option for each of the three chips to use an attribute or a template.
This is where you can paste it.
I guess humidity is a standardized attribute name for HA weather entities (if they support it).
So replacing the entity id (weather.wetter_zuhause) should be all needed.
Thank you for the patient and detailed (not to mention timely) response! I will have to spend a little time learning this before I get to attempting it and unfortunately my real job will interrupt me during the process. I will post back if/when I make some progress, hopefully in the near future!
There have been a few reports and Github issues about line-breaks in the header causing visual glitches on narrow screens (horizontal oreientation of mobile devices).
I changed the header column with temp and condition to keep their natural width instead of breaking.
The column for the chips now take the rest and truncate their text in case of not enough space instead of adding line-breaks as well:
One minor thing I encountered that may help others is step 3 of your github installation instructions should read "Search for “Weather Card Extended” in HACS, vs. “Weather Extended Card”. Again, great job.
A little update that I already released yesterday:
Card uses now partly-cloudy images with a moon at night, also for weather integrations that don’t report “night-time” explicitly (You have to set the weather lat/long location in the card in this case, so it can calculate sunrise/sunset times).
You can set a different spacing in pixels for the daily and hourly weather in case you don’t like the default (was requested a few times on Github).
