Weekend is around the corner and that means that it’s time for the next release of Home Assistant. 0.68 brings a ton of great goodies and bug fixes.
One of the coolest features this release is by @mjg59: you are now able to control HomeKit devices. Previously, it was possible to control Home Assistant from iOS devices using the HomeKit protocol. With this release, Home Assistant is able to become the controller and use HomeKit to control lights and switches directly. Since HomeKit is vendor agnostic, it means that any HomeKit light or switch will now be compatible with Home Assistant. Very cool.
Another cool new platform, also by @mjg59, is support for Eufy devices. Eufy is the Home Automation brand of Anker and they have been producing reasonably priced devices which can now be controlled by Home Assistant too. Thanks for all your contributions @mjg59 ❤️.
New Platforms
New Features
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
Reporting Issues
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
Breaking Changes
Icons! Material Design Icons has implemented some naming guidelines and this caused 9 icons to change names, 3 of which are home automation icons: roomba -> robot-vacuum, nest-protect -> smoke-detector, nest-thermostat -> thermostat (see all changes).
I am still having issues getting Philips hue and dark sky working after 0.66.0 and I tried upgrading to 0.68.0 but I still had issues. Is there something I need to do to get them to work?
Cool to have added Kodi discovery. I had to read the full blog article to understand why some of my Kodi instances are suddenly showing up. One isn’t, I will have to investigate.
After performing this upgrade I am no longer able to save edits to Automations or Scripts with in Home Assistant I have to edit them in a separate note pad editor.
After upgrading from 0.67 to 0.68, my system is completely offline. Can’t even ping. Using a 32GB SD card that was less than 3 months old with <7% use, 2.5A power supply. Been running sweet until the attempted upgrade through the GUI. Any idea on how I even start to debug that?
Going to pull the card out to see if my backups are accessible as the first step.
same getting error when i save automation version 068.
Mon Apr 30 2018 17:19:43 GMT+1200 (New Zealand Standard Time)
Error handling request
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 381, in start
resp = await self._request_handler(request)
File "/usr/lib/python3.6/site-packages/aiohttp/web_app.py", line 322, in _handle
resp = await handler(request)
File "/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 88, in impl
return await handler(request)
File "/usr/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 68, in staticresource_middleware
return await handler(request)
File "/usr/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 27, in real_ip_middleware
return await handler(request)
File "/usr/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 68, in ban_middleware
return await handler(request)
File "/usr/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 28, in auth_middleware
return await handler(request)
File "/usr/lib/python3.6/site-packages/homeassistant/components/http/view.py", line 104, in handle
result = await result
File "/usr/lib/python3.6/site-packages/homeassistant/components/config/__init__.py", line 121, in post
self._write_value(hass, current, config_key, data)
File "/usr/lib/python3.6/site-packages/homeassistant/components/config/automation.py", line 32, in _write_value
if cur_value[CONF_ID] == config_key:
KeyError: 'id'
Looks like this caused when you copy pasted automations into the automations.yaml file and did not add an ID (as per instructions ). I’ll include a fix in 0.68.1 to correct this.
Somehow HA borked on me eating up the config. Now doing a reinstall using 0.68.1 - Add-On Store missing after fresh install. So I am stuck as I can’t enable SMB …
@xbmcnut samething here. My HASSIO was running fine on RP3 and new SD card for last 6 months until I upgrade to 0.68 and now my system is completely offline. I was hoping to debug with the console but everything seem to be lock and just having the HA logo with no login doesn’t help.
HASSIO is very nice and I still recommend for starting but I found it too dangerous for me to lose your whole home system without any way to debug it. On the SD is only the resin boot os. Unfortunately this is enough for me to not go back to HASSIO until they provide a safe login on the console for those situation.
As I’m about to be more serious on my home automation, this will be a good time to move on HA on VM and setup redundancy and DR plan if this occur again. I believe VM are more easy to backup and restart.
Also I realized that the HASSIO Supervior had no approval process to update his version and saw it update automatically his new version this last few days. May it be this new version that cause the problem? We won’t be able to tell as I can’t even log on anymore.
My suggest:
Supervisor update should be a manual update process like the HA and OS unless user accept to automatically update it (not recommend for a production system).
Config and Backup should be on the SD card accessible for recovery plan situation which there are not presently.
@Starwolf73. My SD card seems to have completely died during the process. Is not ‘seen’ by the bios in either Windows or Linux. Can’t say I’ve ever seen that before. My biggest peeve with this is no native way in HA to perform a backup to an offsite location. If it is super easy to insert a thumb drive and have HA save my weekly backup .tar files there, please show me how. Although I was doing automated weekly backups, that’s of no use whatsoever if you can’t access your card.
@xbmcnut A simple solution to backup HASSIO on Windows platform is to install Samba addon and map a drive on HASSIO backup folder with \{Hostname}\backup or \hassio\backup. After you can use any simple backup solution on Windows PC and you can automate your backup.
I finally was able to log on my RP3 via ethernet cable and for some reason the WIFI doesn’t work anymore. Will try another RP3 later but so far I did find an error in the Hardware log. ➜ ~ hassio -d ho hardware DEBUG [CmdHost]: action->‘hardware’, endpoint=‘hardware’, serverOverride->’’, GET->‘true’, options->’’, rawjson->‘false’, filter->’’ DEBUG [ExecCommand]: basepath->‘host’, endpoint->‘hardware’, serverOverride->’’, get->‘true’, Options->’’, Filter->’’, RawJSON->‘false’ DEBUG [GenerateURI]: basepath->‘host’, endpoint->‘hardware’, serverOverride->’’ DEBUG [RestCall]: data->‘http://hassio/host/hardware’, GET->‘true’, payload->’’ DEBUG [RestCall]: ResponseBody->‘404: Not Found’ Error decoding json invalid character ‘:’ after top-level value: 404: Not Found#
Update: Test the RP3 WIFI with another OS (SD card of Octopi) and work fine. My file system-connections/resin-wifi file is also good with no error. Finally I did run the configuration check and it return valide. So there is something that recently change to affect the WIFI.
). I’ll include a fix in 0.68.1 to correct this.