I added that trigger but it didn’t seem to work for me
Weird. I just tested it and it definitely works. Should look like this:
trigger:
- platform: homeassistant
event: start
- platform: state
entity_id:
- sensor.forecast_1
- sensor.forecast_2
- sensor.forecast_3
- sensor.forecast_4
- sensor.forecast_5
- sensor.forecast_6
- sensor.forecast_7
1 Like
Mine is flipped but should be the same but it wasn’t until I ran the script manually that I saw a change. I’ll keep an eye on it for the next time I restart
- alias: "Update friendly names"
initial_state: 'on'
trigger:
- platform: state
entity_id:
- sensor.forecast_1
- sensor.forecast_2
- sensor.forecast_3
- sensor.forecast_4
- sensor.forecast_5
- sensor.forecast_6
- sensor.forecast_7
- platform: homeassistant
event: startthanks will try.
So sensor.forecast_0 is always today
_1 tomorrow
_2 after 2 days
??
I like to add this in hadashboard
Yes that’s correct.
Did anyone run into the following errors:
2018-01-25 15:14:57 ERROR (SyncWorker_0) [homeassistant.util.yaml] Unable to read file /config/packages/weather.yaml: 'utf-8' codec can't decode byte 0xb0 in position 677: invalid start byte
2018-01-25 15:14:57 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: 'utf-8' codec can't decode byte 0xb0 in position 677: invalid start byte
It appears to be getting thrown from the degrees signs in the weather.yaml, based on HA won't start or produce an error log - I'm a bit panicky. How did you all get around this?
I can’t reproduce these errors, everything seems to be working fine. I’m not sure what would be different about your configuration that would cause this. What version are you running?
Why does mine look like this:
I did create a group
Forecast:
name: Dark Sky Weather
entities:
- group.weather_card_forecast
Do I need to add every entity??
(Note the weather card is my BOM weather)
I put all the icons in config/www/dark_sky - all the individual files - was I supposed to maintain a folder structure?
Just noticed in weather.yaml line 100 there is also a group and it is set to no??? Do I edit that? (Just noticed I do have a forecast tab and it’s got forecast_1 etc)
Just manually ran the script and I now have friendly names and icons… So how do I get those other elements onto a card?
Just create a hidden group for those elements
1 Like
OK I REALLY HATE to say this however this KILLED MY HA completely. Could not access at all any way.
There seemed to be a small window that I could access via SCP and I was able to copy off my conf yaml and edit out the script and package and then reboot and now it’s working again.
I was unable to access the frontend
Unable to ssh - just got a bash screen and couldn’t do anything
Unable to scp after a short limited window.
I don’t understand this but I think something is conflicting/killing my install. Phew! I thought I had a dreaded card error and had downloaded a new hassio to install.
Weirdly, just after boot I could use winscp and see the config folder but quickly I could not change folder to \backup and if I went back to \config it was empty. could not see \root. Even when config did list just after boot if I was not fast enough and I tried to edit a file I got a scp error and a suggestion to try sftp.
I think the trick was to get in before the script ran as it was still booting. Anyway, normal access has resumed. Phew.
@Mattya802 The link you posted had a workaround to get the degree symbol to show without errors, did you try that?
@DavidFW1960 No idea what’s going on and why this would cause the issues you’re having. I’m not running hass.io.
Yah, it must have something to do with me using Textpad to edit my yaml files. What are you using to edit/save your yamls?
Use Notepad ++, it’s much much easier than using textpad/notepad. I don’t know if that will solve your problem or not, but regardless…download Notepad ++.
2 Likes
Thanks, I’ll give that a try.
Something odd, 2 of the days aren’t displaying the the icons. Yesterday each day was showing properly. I tried to run the script manually however it didn’t update. Tuesday should be showing “partly-cloudy-night.png” which is the same as Wednesday. Friday should be showing “rain.png”. If anyone has encountered this or has any ideas please let me know.
Thx
Yeah beats me too.
Is anyone here using this and also using hassio on a RPi3 with v 0.61.1?
As soon as I commented out the weather.yaml and python script, hassio loaded immediately. I downloaded the .py and yaml files from your github and only edited in my API key. It was initially working but all of a sudden it just died and I no longer could see any files in Winscp and SSH only showed a bash command line (not a hassio message etc)
It is very puzzling. I thought my card was dead and only by fluke noticed I had a small window of access after a restart where I could edit files and see everything correctly so I could recover.
Yes. Got it running last night. If I get some time this weekend I’ll write up all of the things I ran into. Here are a few…
One that caused errors on home assistant loading was formatting problems from copying and pasting the python script. It was the long lines of code for each day of the week–just after value template I think–there were some extra line returns and the indention was not right.
Another was getting the script to run in the first place to create a boatload of sensors. Kudos to @DetroitEE for this little tidbit:
And for a card to show, I didn’t use the one in weather.yaml (commented it out). I already had a weather view in a groups include file, so I put the code there.
To get rid of the badges on the default view, I copied all of the dark sky sensors from the dev panel into Google Sheets, cleaned them up and formatted them for my weather groups file and made a hidden group as suggested.
Looks something like…
Hidden Dark Sky Sensors:
- sensor.dark_sky_cloud_coverage
- sensor.dark_sky_cloud_coverage_1
- sensor.dark_sky_cloud_coverage_2
- etc...
And go to Configuration > General > Reload Groups and they’ll all disappear.
EDIT: The badges will disappear from the default view, but you will then get a card with all the sensors instead. I use views in addition to the default view and didn’t see the new card until I scrolled down.
That’s a few things… 