Help resolving a few errors after a fresh install of HASS

Hey all. I’m running HASS on a raspberry pi. I’m encountering a few errors and I’m not quite sure what they are saying. Would anyone be able to assist me with trying to resolve them?

Error 1: This seems to be related to the “yr” sensor. Not quite sure what would be causing this. I didn’t change anything from the standard setup that comes in the default config file.

16-07-03 17:44:56 homeassistant.components.sensor: Error while setting up platform yr
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py”,
line 98, in _setup_platform
discovery_info)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/yr.py”, line
74, in setup_platform
dev.append(YrSensor(“symbol”, weather))
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/yr.py”, line
92, in init
self.update()
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/yr.py”, line
135, in update
for time_entry in self._weather.data[‘product’][‘time’]:

Error 2: Super vague. Not exactly sure what “product” would have an error with the key. I’ve setup my Ecobee3, Wink Link Hub, and Forcast.io, which all require an api key. All three are working fine so I’m not sure what else this could be referencing.

KeyError: ‘product’

Error 3: No idea what this is referencing or what the IP address is for in the list. I logged into my router settings and I don’t see it as a connected device.

16-07-03 17:45:41 netdisco.ssdp: Error fetching description at http://:2468/f68923bc->1dd1-11b2-84d3-1bea9f81aeb0

Thanks in advance. I really appreciate the help!

See YR setup issue with elevation · Issue #2435 · home-assistant/core · GitHub

There seems to be a device with is uPNP capable otherwise it could be a bug.

Thanks for the info! Since I’m quite new to all of this… I just want to make sure I’m following. Is your link github for the yr sensor saying this is a bug that was reported?

Still trying to troubleshoot my error 3. I’m thinking it might actually be my chromecast. I’ve disabled it in the configuration.yaml to see if the error continues to appear or not.