My thanks to you and @kellbot. I love my WeatherUndeground!
awesome! any chance you could submit that to the original repo as a pull request? I probably won’t have a chance to update it until after this weekend (2 jobs and 2 kids leads little time for much else lately).
Kell, feel free to include my YAML files in your distribution.
Will do next time I get a chance to sit down at a real computer, thanks!
In the example config, the UV in states.sensor.weather_underground_pws.attributes.UV needs to be in caps, as that is how the API returns it
I fixed that in the original thread but forgot about it here.
There are still a few this pending before I can create a PR, but am working on it.
Line 33 of wunderground.py needed to be changed on Raspberry Pi to self._unit_of_measurement = TEMP_FAHRENHEIT from self._unit_of_measurement = “°F” because of ‘utf-8’ codec error. TEMP_FAHRENHEIT is defined in the homeassistant package in const.py and also needs to be added after line 7: from homeassistant.const import TEMP_FAHRENHEIT
For those newbies like me, I included the following in my configuration.yaml file:
-
At the end of the homeassistant: section, I added ’ customize: !include customize.yaml’. Note the two spaces in front of the line.
-
I added wunderground as my first sensor (note there are two spaces in front of everything after sensor below
sensor:
platform: wunderground
api_key: YOURKEY
pws_id: KMANORTH112 -
I added the sensor templates file as my next sensor:
sensor 2: !include sensor_templates.yaml -
Towards the end of my configuration.yaml file, I added the group line:
group: !include group_config.yaml
Install instructions same for Pi all-in-one installer?
For Pi AIO you save to custom_components/sensor or deps folder?
I’m having a hard time getting this sensor up and running. Did everything macaroni1975 posted when I restart HA doesn’t start no log output either.
Correct. I’m on AIO as well.
Can somone with a working wundergroud setup share their .yaml files? I must be grouping or customizing something wrong.
Before you try customizing/grouping, just make sure that you are getting those sensors created with the right data (start simple). What error are you getting?
Take a look here:
I provided all the YAML files as well as screenshots.
thanks… i actually figured it out last night. was struggling with it for a few days… I used wget to grab py file so opening it revealed html code. used git to grab py file everything is working now.
Good to hear!
How will this affect the current method of display using template sensors? Will it change at all?
I guess, some minor modifications to the customize.yaml will be required based on the name of the sensors. Otherwise, should work just fine.
I finally got around to trying this but was disappointed when I saw how many attributes were missing from the original implementation and so I went back. I’d love to use the component and get rid of all the overhead associated with all the template sensors, but not at the expense of losing all that data I was getting.
Any chance the code will be updated to get all of the WU attributes that were available?