@pocket are you able to assist since you have a better understanding of the NWS side of things.
Oh thatās cool. I canāt see it in my custom repositories any more so HACS must automatically take over.
Iāll try to help. What are you using for a weather integration? Iāve been using NWS, but it takes a bit of work to make it work over a calendar day.
The daily section is an assemblage of sensor templates. What I should do is post my templates file on GitHub. Itās still a work in progress, though. Iām doing things using brute force. Iād like to figure out how to make some sort of conditional variable index to make it tighter and more elegant.
Once itās on GitHub, Iāll give you a link.
1 Like
Thanks, I have several weather entities set up as well. The thing I still cant figure out is the weather icons for the daily forecast!
Hereās the templates file. It still has some content for @DavidFW1960ās Custom BOM card because Iām still using it along with the Platinum card. These are recognizable because being entities, I truncate text at 254 characters to avoid an error. Theyāve been replaced by a template to make them attributes, which donāt have a limit.
https://github.com/Sudo-Rob/NWS-Template-for-Platinum-Wx-Card/edit/main/weather.yaml
For the 5-day icons, I use nws_forecast_icon_1.
Edit: Iām still using YAML mode for a lovelace dashboard. I put the weather.yaml file under config/packages with the reference packages: !include_dir_named packages in configuration.yaml.
See: https://www.home-assistant.io/docs/configuration/packages
https://www.home-assistant.io/docs/configuration/packages#create-a-packages-folder
2 Likes
You sir, are the man! Quick change to my nws code and we are up and running! Thanks so much for sharing all the hard work!
Are you using the entire file, or just what you need?
I put the whole thing in and I am playing with it as we speak. I didnāt use the derivative but almost everything else seems to be working quite well
Derivative is something @BenCranston was working on to drive a trend arrow icon. Itās not being used at this time, so you can delete it. There are also commented lines for when system time was being use rather than datetime attributes.
If you have any suggestions for the templates, Iād like to hear them. Use PM or start a new thread.
One additional thing. @BenCranston and @theRat came up with a modification to the NWS integration to add a short forecast entity. Itās a little tricky to get working, so PM me and Iāll try to come up with a short procedure for the mod. FYI, if the NWS integration changes, youāll have to reapply the modifications.
Correct, I am in the SF area. I assumed that BOM, like other weather services, had info on other parts of the world. Obviously, I am simply trying to get this weather card working & saw other posts that solved similar issues with the BOM integration
Iām using OpenWeatherMap, but it does not have all the sensors or icons I need. Maybe I just donāt understand how to setup this card properly. Iāve gotten nowhere on getting the Daily Forecast Section setup. Suggestions? thanks.
The BoM integration is Australia only. The data is all sourced from our official weather bureau. I am about to make a fix to it to give a better error message when you try to set it up in an unsupported region.
Have a look at the previous messages between @pocket and @jsdphilly who are both in the US and are using the NWS integration. @pocket has been doing lots of testing for us and is all over how to get things working.
The BOM integration provides us 7 days worth of entities. e.g sensor.location_temp_min_0 through to _6 or _7.
That Daily Forecast config page is asking for the first one that is not today i.e for the BOM integration the relevant entity ending in _1. It then appears to automatically increment the number in the background to get the appropriate entity for the remaining 4 days of the forecast.
Trying to get forecasts working for the USA & feel like such a noob. Installed the NWS integration for my area, but there are only 13 entities and none are icons. I pasted @pocket weather.yaml Github code in Templates. Was that correct? I made no changes to the code.
Obviously there is very active development on this card and am happy to wait it out if recommended.
Try going to to http://homeassistant.local:8123/developer-tools/yaml and refresh entities. Then refresh your browser (typically Ctl-F5 on a PC). If that doesnāt work, check and see if the NWS integration is set up for daily forecasts. You might need to reload it.
Edit. 13 entities is all thatās needed. Forecasts use the attributes in weather.xxxx_daynight. The rest comes from the templates, which needs to be edited for your locale. Do an entity search and replace for what you see in the xxxx field.
Also, check http://homeassistant.local:8123/config/lovelace/resources to see if /hacsfiles/makin-things-weather-card/platinum-weather-card.js is loaded.
If HA is set up for YAML mode, the following (or something like it) is required to load the template when HA starts.
See Customising the BOM Weather and lovelace - now in HACS - #1332 by pocket
No it needs to go into your config. Then you need to search and replace all on his weather codes with yours. If you need more clarity I can write it up when I get home.
1 Like
For those using the NWS integration, I need to add yet another nugget of information. Of the 13 entities provided, the default configuration only enables the entity weather.xxxx_daynight. The easiest thing to do is enable them all, and once you get the weather card friendly with the sensor templates, disable the ones you donāt need. Thereās a link in the integration tile.
Thanks to @theRat for reminding me how bad my memory is getting.
Thanks for all your hard work on this @theRat @davidFW1960.
What entity would this be in the BOM list of entities.
Thanks
1 Like
xxxxxx Extended Text 0
1 Like
Just a quick heads up for people using the BoM integration. There are a few updates queued up for when 2022.7.0 gets released. One is to stop warnings from a architectural change. The others are pretty minor updates. These updates wonāt install on 2022.6 or earlier and if you try and force them it will break. HACS will prompt you to update probably as soon as 2022.7 is installed.