And the result still has all of the metrics in it:
Unless I misunderstood what you meant by “setting only the sensors you want in the yaml”. What did work for me, all be it rather hackish, is to remove the attributes i dont want to see from the DOM in a helper.js file I’m loading in the custom skin I’m working on.
Like I said hackish at best but for now it does the trick. Now I just have to remember to never rename my weather widget or this code won’t do anything.
i meant setting only the sensors you want in the sensors part, but i guess you already did that.
i guess that in this widget some sensors are hardcoded, so if your solution works then its a good workaround.
Been trying to set up a layout similar to the one in OP myself yesterday, and ran into a new issue, courtesy of Dark Sky…
It turns out the API (and so sensor) names for sensor.dark_sky_daily_low_temperature_1 and sensor.dark_sky_daily_high_temperature_1 have changed. They should now be:
Yes, you’re reading this correctly. Low is overnight, high is daytime.
It might be a regional thing or something, but it drove me seriously crazy last night.
No worries, just that i couldn’t figure out what’s happening for a bit (in my defense, it was 5am), and thought i’d leave a note here in case someone else stumbles upon it.
I so want this users forecast and weather widgets! They are perfect. The forecast with the friendly names and extended forecast, and the weather widget with the icon, temp, and summary. Perfect!
untill now i only seen this pic and others wanting it.
to make something like that you first have to have all that information in HA and then create quite some HTML and javascript.
its possible, but not easy.
easier is it to use one of the many online weather widgets that are already out there.
google for “online weather widgets” and you get a lot of different weather widgets and some of them highly customisable