I have same issue. wunderground is broken…
OK: I figured it out… just get new fixed files from “dev” branch on homeassisant git and replace below files:
homeassistant/utill/ “init.py”
homeassistant/compoenents/sensor/wundeground.py
The same bug affects about 10 other sensors, so just replace the “init.py” and “your broken sensor.py”
until they merge “dev” branch into main and issue an update to HA.
Waiting for the Docker RPi3 image to be updated to 0.65.1. How long does this usually take compared to the „standard“ image homeassistant/home-assistant?
Updated today.
Device tracker using iOS app, is now showing me as ‘not_home’ instead of ‘Away’.
Is this a bug?
@onkytonk: Looks like the device tracker’s state is reported. Maybe a missing customization or localization?
It’s strange though, I haven’t changed anything apart from updating.
How do I get it back to reporting “Away”?
EDIT: Its only showing it this way in the iOS app. It’s working as per normal everywhere else.
I have a similar issue with SabNZB sensor component. Was working fine in 0.65, and have updated to 0.65.1, but the issue is still there, though Wunderground is working again.
2018-03-11 00:32:21 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform sabnzbd
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 82, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/lib/python3.5/asyncio/tasks.py", line 400, in wait_for
return fut.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/sabnzbd.py", line 152, in async_setup_platform
if not (yield from async_check_sabnzbd(SabnzbdApi, base_url, api_key)):
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/sabnzbd.py", line 62, in async_check_sabnzbd
yield from sab_api.check_available()
File "/srv/homeassistant/lib/python3.5/site-packages/pysabnzbd/__init__.py", line 43, in check_available
with aiohttp.ClientSession() as session:
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/client.py", line 742, in __enter__
raise TypeError("Use async with instead")
TypeError: Use async with instead
Also, another error I have that has popped up since 0.65 is the following. No idea what it’s about.
2018-03-11 00:32:22 ERROR (Thread-11) [homeassistant.core] Error doing job: Unclosed client session
I’m also experiencing this. I have a password for https, and really don’t want to remove it.
@cjsimmons Thanks for the sanity check! I have definitely confirmed that removing the http password fixes the issue.
@DavidFW1960 - I’ve tried it on 2 win 10 machines with both chrome and edge - same issue - also showing same from android phone as well.
Edit: Just installed 65.1 - no help with http password and menus so far.
Ok - another oddity around this - removed http password so it would go back to normal until this is sorted out. Checked with Chrome from Win 10 laptop - all is fine. No password - menu looks good.
Check from same laptop with IE 11 (not edge) - get password prompt (which I confirmed in chrome was off and double checked config file in HASS). Menu is now messed up in IE just like Chrome when password is enabled. Cleared IE cache - no difference. Refresh page again - no password prompt now (no changes made in HASS) - but menu is still messed up. Edge however on same latptop shows ok and no password prompt when I access HASS.
Also - the screenshot/gif shown in the post for changing the light name does not appear to be working for me (at least so far) - my 65.1 instance is on a test box with one yeelight it discovered via wifi, I can turn on.off/change my yeelight with this HASS instance. However - I don’t see the cog wheel when I click on the light to be able to change the name, Am I missing something or is this just because the yeelight isn’t supported for the name change from the front end or something along those lines?
had this error message when upgrading to 65.1, but everything seems to be working okay.
rpi3 raspbian stretch InRelease
Building wheels for collected packages: aiohttp
Running setup.py bdist_wheel for aiohttp … error
Complete output from command /srv/homeassistant/bin/python3 -u -c “import setuptools, tokenize;file=‘/tmp/pip-build-1lwdt1ji/aiohttp/setup.py’;f=getattr(tokenize, ‘open’, open)(file);code=f.read().replace(‘\r\n’, ‘\n’);f.close();exec(compile(code, file, ‘exec’))” bdist_wheel -d /tmp/tmp6oi8a2mqpip-wheel- --python-tag cp35:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] …]
or: -c --help [cmd1 cmd2 …]
or: -c --help-commands
or: -c cmd --helperror: invalid command ‘bdist_wheel’
Failed building wheel for aiohttp
Running setup.py clean for aiohttp
Failed to build aiohttp
Looks like your python-miio is too old. Are you sure you are running python-miio 0.3.7? Please check pip freeze|grep python-miio to see the version.
One question, I’m running hass on synology container in docker. Before upgrade it used to use about 700MB of ram, but after upgrade to 0.65.1 it uses over 2GB of RAM! I cleaned container couple times it didn’t help. Anybody noticed that?
I am also trying to upgrade python from 3.5.2 (default Ubuntu) to 3.5.5 but can’t figure out. Tried using PPA no luck it says it has already.
If someone can provide step by step details for Ubuntu 16.04 LTS how to do this will help a lot many people like me.
If I figure out will update this post with the steps.
Thansk
This is a good guide for upgrading your virtual environment 
I would love to see how to upgrade python to 3.5.5 on non-virtual environment too.
Thank you for the link though.
The same basic process applies - build Python from source, and install it. Then call the new version explicitly (eg python36 rather than just python3).
That’s the point of LTS, having a stable environment for server usage.
16.04LTS is still supported and well updated.
There should be a LTS soon (18.04 announced on Apr 26th) and this is the way to go for users having an LTS, not adding other packages from external sources.
People using LTS and sticking to it, including me, do that on purpose. I have other services on other VMs with 17.10, but Home Assistant is controling my home, some security devices, I don’t want the system to be a risk.
So right now, I stay with 0.63.3…
Here some hints on upgrading to Python 3.6 on Ubuntu 16.04 in a separate thread:
Keep in mind that do-release-upgrade on a LTS version only works with the following point release, i.e. you would need to wait for 18.04.1.
So I posted an issue earlier about my iOS device tracker setting my status as not_home. I thought it was only in the iOS app, but seems to be happening in Safari too. Also, the pull out menu items on the left are lower case, and some are missing entirely.
If I refresh the iOS app or Safari, it fixes it temporarily until it times outs.
Appreciate it.
I will try and see how it goes because I have Home Assistant running with ssl using letsencrypt certificate so I will have to see anything else I will have to do.
Thanks a lot.
