Danielhiversen
Met.no is also a new weather component in this release. Uses the same data as the yr.no sensor.
2 replies
Met.no is also a new weather component in this release. Uses the same data as the yr.no sensor.
2 replies
…and there IKEA tradfri breaks, yet again … its alredy configured, why does it always insist on discovery after updates?
…works after removing tradfri config and configure in gui, but really…should be listed under breaking changes.
Great work with the integration part. I really like it, as a long time user, I believe that this is a move in the right direction; making Home Assistant easy to configure. Keep the good work!
Are these new integration features also available if configured from the config file? (Is this even possible? Still searching for how to auto add the chromecast integration Edit: seems to be fixed in a later release thx @balloob for letting me try again )
1 reply
Just add cast: to your config file
What new does met.no offer? Is there any reason to use it over yr? Unable to test it myself atm.
1 reply
I think it is because there are no forecast data:
But anyway it is great progress and I’m looking forward for next update 
How does Mqtt: Configuration.yaml work?
Al it says is: This integration has no devices.
4 replies
I moved over to hass.io back on .75 and had a issue with auto discovery of my G-Homes causing the front page not to load.
I could only resolve this by adding cast devices manually.
While on .78 I had the issue where my G-Homes and minis would appear unavailable. Removing the manual config and allowing auto discovery resolved this issue.
I updated to .79 and again the front page wouldn’t load. Adding cast manually, again resolved the issue.
This means I’m unable to see my groups which are found via discovery 
In the integration panel, i have OpenUV, and all the entities for it. Then it givs a list of “entities without devices…”, but seems pretty useless. What’s the point of this?
There is currently no forecast data, but I am working on it: https://github.com/home-assistant/home-assistant/compare/met_weather?expand=1
A weather component has a different view in the frontend
0.79 reverted the change made in 0.78 regarding chromecast discovery logic. Only fixed one issue related with cast manually configuration. Some user reported that under 0.77/0.79 logic, your system startup might be blocked for 5 minutes, but eventually it will give up and resume the startup.
1 reply
am I the only one who has problems with zoneminder after upgrading to 0.79? I get " Connection error logging into ZoneMinder".
I see that some changes have been made to the ZoneMinder component, are any changes to the configuration required?
Sorry, are you saying discovery will work?
And would this 5mins delay happen every time I restart?
Is anyone else having problems starting after upgrading? Seems the startup is hung on “Collecting restrictedpython==4.0b5”. A manual install results in the same thing.
Tried yesterday and again this morning in case it was a server issue. Thoughts?
Edit: the fix was to dump the ~/.cache folder. Something must have gotten corrupt.
I am as well. I reverted back to 78.0 and it is working again.
My working Zoneminder setup broke when I updated to 0.79.
Clarification: My ZM server (running ZM 1.32.0) is still working fine, i just get login errors from Home Assistant.
2018-09-29 14:20:02 ERROR (SyncWorker_6) [zoneminder.zm] Connection error logging into ZoneMinder
2018-09-29 14:20:02 ERROR (MainThread) [homeassistant.setup] Setup failed for zoneminder: Component failed to initialize.
2018-09-29 14:20:02 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of camera.zoneminder. Setup failed for dependencies: zoneminder
2018-09-29 14:20:02 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform camera.zoneminder: Could not set up all dependencies.
Nice work guys! and hard keep up with the upgrades!
I am in process of upgrading from 0.76.2 and I have heavily invested in third party integration like Google Home, Amazon Echo, AppDaemon and custom apps using python which does http post (https://my-domain.ord/api/states/m_entity_name?api_password=mypass).
Any documentation link about how to handle user authentication where I am still using legacy user and have one common password from http component?
Appreciate it.
After updating to 0.79 I encountered errors with zoneminder and lost developers tool pages.
For now reverting back to 0.78. till I have more time to search for a fix.
@patrikron88 @hulkstang66 @pbcrunch @Akriss
Here’s the PR that fixes it: https://github.com/home-assistant/home-assistant/pull/16979
same question
Curious too
Where are the release notes for 79.1? The home page links here but that gives a 404 Page Not Found.
1 reply
79.1 seems to have killed my Hive thermostat, not showing up on the front end.
was working fine on 79
1 reply
hi @gazzaman2k
I just upgraded to 0.79.1 and all looks ok so far with my Hive, do you get any errors in the log?
2 replies
i have 404 error,
upgraded from 78.3 to 79.1 via
$ sudo -u homeassistant -H -s
$ source /srv/homeassistant/bin/activate
$ pip3 install --upgrade homeassistant
ubuntu 18.04, back to 78.3 all works
well it seems to have fixed itself i downgraded back to 79 and then today upgraded to 79.1 and its now fine, strange unless hive was down for that moment i installed it and restarted home assistant?
2 replies
yes could have been, or also internet access to the Hive from your HA server at the time of the service starting back up.
If the Hive component cant log in successfully to Hive when HA starts up then it wont get added, so would need another HA service restart to try again
looking through my HA log it looks like Hive could have been down between 21:40 and 22:50 Sunday night
If this was the case and if you upgraded then, when you upgraded HA instance came up it would have not been able to successfully log in to Hive so not load he Hive component.
A restart of HA after Hive was backup should have been enough to add Hive back to your HA instance
I’ve upgraded from 0.77.3 to 0.79. The user interface doesn’t load anymore. I think it has something to do with one of my Hue lights. It’s a Hue beyond ceiling lamp. The error log show a lot of the following messages.
File "/usr/src/app/homeassistant/helpers/entity.py", line 218, in async_update_ha_state
"No entity id specified for entity {}".format(self.name))
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity Hue beyond
At the moment I’ve reverted back to 0.77.3 which works fine.
root@ubuntu:~# sudo -u homeassistant -H -s
homeassistant@ubuntu:/root$ source /srv/homeassistant/bin/activate
(homeassistant) homeassistant@ubuntu:/root$ pip3 install --upgrade homeassistant
Collecting homeassistant
Downloading https://files.pythonhosted.org/packages/83/6a/633532bd1c9302e047646bb3b1c66f48a5d1b6344b9e34dca7abe392f49c/homeassistant-0.79.2-py3-non e-any.whl (3.1MB)
100% |████████████████████████████████| 3.1MB 1.9MB/s
Requirement already satisfied, skipping upgrade: pip>=8.0.3 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (18.0)
Requirement already satisfied, skipping upgrade: aiohttp==3.4.4 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (3.4.4)
Requirement already satisfied, skipping upgrade: certifi>=2018.04.16 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (2018.8.2 4)
Requirement already satisfied, skipping upgrade: attrs==18.2.0 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (18.2.0)
Requirement already satisfied, skipping upgrade: astral==1.6.1 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (1.6.1)
Requirement already satisfied, skipping upgrade: PyJWT==1.6.4 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (1.6.4)
Requirement already satisfied, skipping upgrade: cryptography==2.3.1 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (2.3.1)
Requirement already satisfied, skipping upgrade: pytz>=2018.04 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (2018.5)
Requirement already satisfied, skipping upgrade: voluptuous==0.11.5 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (0.11.5)
Requirement already satisfied, skipping upgrade: voluptuous-serialize==2.0.0 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) ( 2.0.0)
Requirement already satisfied, skipping upgrade: async-timeout==3.0.0 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (3.0.0)
Requirement already satisfied, skipping upgrade: requests==2.19.1 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (2.19.1)
Requirement already satisfied, skipping upgrade: jinja2>=2.10 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (2.10)
Requirement already satisfied, skipping upgrade: bcrypt==3.1.4 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (3.1.4)
Requirement already satisfied, skipping upgrade: pyyaml<4,>=3.13 in /srv/homeassistant/lib/python3.6/site-packages (from homeassistant) (3.13)
Requirement already satisfied, skipping upgrade: chardet<4.0,>=2.0 in /srv/homeassistant/lib/python3.6/site-packages (from aiohttp==3.4.4->homeassist ant) (3.0.4)
Requirement already satisfied, skipping upgrade: idna-ssl>=1.0; python_version < "3.7" in /srv/homeassistant/lib/python3.6/site-packages (from aiohtt p==3.4.4->homeassistant) (1.1.0)
Requirement already satisfied, skipping upgrade: yarl<2.0,>=1.0 in /srv/homeassistant/lib/python3.6/site-packages (from aiohttp==3.4.4->homeassistant ) (1.2.6)
Requirement already satisfied, skipping upgrade: multidict<5.0,>=4.0 in /srv/homeassistant/lib/python3.6/site-packages (from aiohttp==3.4.4->homeassi stant) (4.4.2)
Requirement already satisfied, skipping upgrade: six>=1.4.1 in /srv/homeassistant/lib/python3.6/site-packages (from cryptography==2.3.1->homeassistan t) (1.11.0)
Requirement already satisfied, skipping upgrade: idna>=2.1 in /srv/homeassistant/lib/python3.6/site-packages (from cryptography==2.3.1->homeassistant ) (2.7)
Requirement already satisfied, skipping upgrade: asn1crypto>=0.21.0 in /srv/homeassistant/lib/python3.6/site-packages (from cryptography==2.3.1->home assistant) (0.24.0)
Requirement already satisfied, skipping upgrade: cffi!=1.11.3,>=1.7 in /srv/homeassistant/lib/python3.6/site-packages (from cryptography==2.3.1->home assistant) (1.11.5)
Requirement already satisfied, skipping upgrade: urllib3<1.24,>=1.21.1 in /srv/homeassistant/lib/python3.6/site-packages (from requests==2.19.1->home assistant) (1.23)
Requirement already satisfied, skipping upgrade: MarkupSafe>=0.23 in /srv/homeassistant/lib/python3.6/site-packages (from jinja2>=2.10->homeassistant ) (1.0)
Requirement already satisfied, skipping upgrade: pycparser in /srv/homeassistant/lib/python3.6/site-packages (from cffi!=1.11.3,>=1.7->cryptography== 2.3.1->homeassistant) (2.19)
Installing collected packages: homeassistant
Found existing installation: homeassistant 0.78.3
Uninstalling homeassistant-0.78.3:
Successfully uninstalled homeassistant-0.78.3
Successfully installed homeassistant-0.79.2
reboot and
2018-10-02 09:04:52 WARNING (MainThread) [homeassistant.components.http] legacy_api_password support has been enabled. If you don't require it, remove the 'api_password' from your http config.
2018-10-02 09:05:32 ERROR (SyncWorker_2) [homeassistant.util.package] Unable to install package home-assistant-frontend==20180927.0: Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/srv/homeassistant/lib/python3.6/site-packages/hass_frontend/.DS_Store'
Consider using the `--user` option or check the permissions.
2018-10-02 09:05:32 ERROR (MainThread) [homeassistant.requirements] Not initializing frontend because could not install requirement home-assistant-frontend==20180927.0
2018-10-02 09:05:32 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: Could not install all requirements.
2018-10-02 09:05:42 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform speedtest is taking over 10 seconds.
2018-10-02 09:06:13 ERROR (MainThread) [homeassistant.components.websocket_api] WS 139997883461472: Received invalid command: get_panels
2018-10-02 09:06:13 ERROR (MainThread) [homeassistant.components.websocket_api] WS 139997883461472: Received invalid command: frontend/get_themes
2018-10-02 09:06:13 ERROR (MainThread) [homeassistant.components.websocket_api] WS 139997883461472: Received invalid command: frontend/get_translations
2018-10-02 09:05:48 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of logbook. Setup failed for dependencies: frontend
2018-10-02 09:05:48 ERROR (MainThread) [homeassistant.setup] Setup failed for logbook: Could not set up all dependencies.
2018-10-02 09:05:48 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of panel_iframe. Setup failed for dependencies: frontend
2018-10-02 09:05:48 ERROR (MainThread) [homeassistant.setup] Setup failed for panel_iframe: Could not set up all dependencies.
finaly:
404: Not Found
Looks like something that is not user homeassistant has been messing with your virtual environment - all files in /srv/homeassistant are always owned by user homeassistant. You could try and fix the ownership problems, but its simpler just to move that virtual environment aside and create a fresh one.
It would be interesting to find out the fragmentation of installed versions people have. (Like Google does for Android)
I imagine most will be on the newest version (or almost newest .1 version) but there is a really interesting smattering of people who are on older versions.
It’s making me wonder if I actually need to update every two weeks (I only use it locally so it’s not opened up) as there’s been nothing added lately that I was excited to try out and Auth just broke all of my Tasker automations…
Is there a way to access older image versions (last version pre-Auth?), so that I can roll back?
1 reply
fixed, persmission looked ok, but need to uninstall ha, delete this folder, install, reboot and all works now
This got my interest to👀
I’ve the same issue with Home Assistant iOs.
I’ve tried with and without ios: in the config file, but I still get “This integration has no devices”
Here are the details of my issues:
After an upgrade to 0.79.3 from 0.78.3, I simply get a white screen with a blue bar.
I tried rolling back to 0.78.3 but it still doesn’t work so I’m at the point of either getting this fixed or scrapping and reinstalling.
Hopefully this is fixable.
Here’s the error I get when I try to access the page.
2 replies2018-10-03 15:20:20 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web_protocol.py”, line 390, in start
resp = await self._request_handler(request)
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web_app.py”, line 339, in _handle
match_info = await self._router.resolve(request)
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web_urldispatcher.py”, line 799, in resolve
match_dict, allowed = await resource.resolve(request)
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web_urldispatcher.py”, line 281, in resolve
match_dict = self._match(request.rel_url.raw_path)
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web_urldispatcher.py”, line 406, in _match
for key, value in match.groupdict().items()}
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web_urldispatcher.py”, line 406, in
for key, value in match.groupdict().items()}
TypeError: build() got an unexpected keyword argument ‘encoded’
I get something similar:
2018-10-04 14:09:06 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 242, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp\_http_parser.pyx", line 523, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: invalid HTTP method
Missing netifaces:
I did a brand new install of HA yesterday using 0.79.3 (Ubuntu 18.04 venv)
and came across an issue with apple tv.
It autodiscovered my apple TVs and did a setup but errored out due to missing netifaces module.
I had to manually add netifaces (pip install netifaces) and after that it worked fine.
Will be in 0.81