Merge branch 'current' into rc
This commit is contained in:
Paulus Schoutsen
commit
4dc03338a9
90 changed files with 466 additions and 4185 deletions
|
|
@ -28,6 +28,23 @@ This release includes a security fix. The error log was accessible via the API w
|
|||
- Tahoma switches ([@ikucuze] - [#13636]) ([tahoma docs]) ([switch.tahoma docs]) (new-platform)
|
||||
- Add support for Nanoleaf Aurora Light Panels ([@Oro] - [#13456]) ([light.nanoleaf_aurora docs]) (new-platform)
|
||||
|
||||
## {% linkable_title Release 0.67.1 - April 17 %}
|
||||
|
||||
- Fix Gogogate2 'available' attribute ([@dlbroadfoot] - [#13728])
|
||||
- Fix so it is possible to ignore discovered config entry handlers ([@Kane610] - [#13741])
|
||||
- Prevent vesync doing I/O in event loop ([@balloob] - [#13862]) ([switch.vesync docs])
|
||||
- Fix #13846 Double underscore in bluetooth address ([@aav7fl] - [#13884]) ([device_tracker docs])
|
||||
- Fix race condition for component loaded before listening ([@balloob] - [#13887]) ([config docs])
|
||||
- Missing property decorator added ([@syssi] - [#13889]) ([fan.xiaomi_miio docs])
|
||||
- Fix call to parent broadlink switch ([@Danielhiversen] - [#13906]) ([switch.broadlink docs])
|
||||
- Import operation modes from air humidifier ([@syssi] - [#13908]) ([fan.xiaomi_miio docs])
|
||||
- Upgrade pyqwikswitch to 0.71 ([@kellerza] - [#13920]) ([qwikswitch docs])
|
||||
- Upgrade somecomfort to 0.5.2 ([@balloob] - [#13940]) ([climate.honeywell docs])
|
||||
- Update pyhydroquebec to 2.2.2 ([@titilambert] - [#13946]) ([sensor.hydroquebec docs])
|
||||
- Update pyfido to 2.1.1 ([@titilambert] - [#13947]) ([sensor.fido docs])
|
||||
- Bumped pypollencom to 1.1.2 ([@bachya] - [#13959]) ([sensor.pollen docs])
|
||||
- Revert "Upgrade pyqwikswitch to 0.71 ([@balloob] - [#13920]) ([qwikswitch docs])
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
|
|
@ -395,3 +412,35 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
|||
[xiaomi_aqara docs]: /components/xiaomi_aqara/
|
||||
[zwave docs]: /components/zwave/
|
||||
[ann-ubiquiti]: /blog/2018/04/12/ubiquiti-and-home-assistant/
|
||||
[#13728]: https://github.com/home-assistant/home-assistant/pull/13728
|
||||
[#13741]: https://github.com/home-assistant/home-assistant/pull/13741
|
||||
[#13862]: https://github.com/home-assistant/home-assistant/pull/13862
|
||||
[#13884]: https://github.com/home-assistant/home-assistant/pull/13884
|
||||
[#13887]: https://github.com/home-assistant/home-assistant/pull/13887
|
||||
[#13889]: https://github.com/home-assistant/home-assistant/pull/13889
|
||||
[#13906]: https://github.com/home-assistant/home-assistant/pull/13906
|
||||
[#13908]: https://github.com/home-assistant/home-assistant/pull/13908
|
||||
[#13920]: https://github.com/home-assistant/home-assistant/pull/13920
|
||||
[#13940]: https://github.com/home-assistant/home-assistant/pull/13940
|
||||
[#13946]: https://github.com/home-assistant/home-assistant/pull/13946
|
||||
[#13947]: https://github.com/home-assistant/home-assistant/pull/13947
|
||||
[#13959]: https://github.com/home-assistant/home-assistant/pull/13959
|
||||
[@Danielhiversen]: https://github.com/Danielhiversen
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@aav7fl]: https://github.com/aav7fl
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@dlbroadfoot]: https://github.com/dlbroadfoot
|
||||
[@kellerza]: https://github.com/kellerza
|
||||
[@syssi]: https://github.com/syssi
|
||||
[@titilambert]: https://github.com/titilambert
|
||||
[climate.honeywell docs]: /components/climate.honeywell/
|
||||
[config docs]: /components/config/
|
||||
[device_tracker docs]: /components/device_tracker/
|
||||
[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
|
||||
[qwikswitch docs]: /components/qwikswitch/
|
||||
[sensor.fido docs]: /components/sensor.fido/
|
||||
[sensor.hydroquebec docs]: /components/sensor.hydroquebec/
|
||||
[sensor.pollen docs]: /components/sensor.pollen/
|
||||
[switch.broadlink docs]: /components/switch.broadlink/
|
||||
[switch.vesync docs]: /components/switch.vesync/
|
||||
|
|
|
|||
64
source/_posts/2018-04-22-hassio-2018.markdown
Normal file
64
source/_posts/2018-04-22-hassio-2018.markdown
Normal file
|
|
@ -0,0 +1,64 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Hass.io 2018"
|
||||
description: "We want to clarify how Hass.io relates to Home Assistant and talk about the roadmap for Hass.io in 2018."
|
||||
date: 2018-04-22 00:00:00
|
||||
date_formatted: "April 22, 2018"
|
||||
author: Pascal Vizeli
|
||||
author_twitter: pvizeli
|
||||
comments: true
|
||||
categories: Announcements
|
||||
og_image: /images/blog/2018-04-hassio-2018/blogpost.png
|
||||
---
|
||||
|
||||
We noticed that there is some confusion in the community about how Hass.io relates to Home Assistant and what impact the upcoming Hass.io changes will have. We will try to clarify it all in this blog post.
|
||||
|
||||
## {% linkable_title What is Hass.io %}
|
||||
Hass.io is a complete solution to run Home Assistant, by the authors of Home Assistant. The goal of Hass.io is to provide an easy to use and secure system, entirely managed from within the Home Assistant user interface.
|
||||
|
||||
Hass.io is a complete solution, which means that it comes with its own highly secure and optimized operating system, a supervisor application to maintain and configure that system, and of course Home Assistant itself.
|
||||
|
||||
When using Hass.io, you'll see a new Hass.io panel inside the Home Assistant UI. From here users can configure the system and install Home Assistant updates with a simple click of a button. Users are also able to make snapshots of their system, making it easy to migrate all their configuration to a new system or restore their system to a previous state.
|
||||
|
||||
We wanted to be able to provide the convenience of seamless updates and configuration via the UI to other applications too, and so we introduced Hass.io add-ons. Any application can be packaged up as a Hass.io add-on, allowing any user to install and manage it easily. Since the introduction, we’ve seen an amazing growth in users sharing their add-ons with the community. It’s now possible to install an adblocker for your network, an MQTT broker or Tor with a single click.
|
||||
|
||||
## {% linkable_title Upcoming changes to Hass.io %}
|
||||
We’ve introduced Hass.io [last July]. Since then, we’ve noticed some room for improvements in making Hass.io easier to use, lighter to maintain and easier to integrate with other host systems.
|
||||
|
||||
Note that the descriptions of upcoming improvements can get quite technical. Feel free to jump to [the conclusion].
|
||||
|
||||
### {% linkable_title Automatic add-on configuration %}
|
||||
Home Assistant has recently introduced configuration entries. We’re going to hook into this new functionality and allow add-ons to configure their related integration in Home Assistant automatically. For example, if a user installs the MQTT broker add-on, we will automatically set up Home Assistant to connect to it.
|
||||
|
||||
### {% linkable_title Host management %}
|
||||
To control the host system, we currently use a custom service called HostControl. This allows the user to manage here host and restart/shutdown the computer from within Home Assistant. Instead of relying on our own system, we’re going to change to use D-Bus. D-Bus is a standardized mechanism for services and applications to communicate. Using a defined standard means that all parts of the host can now be remotely configured: sound, network, etc, etc. We will be extending the Hass.io panel in Home Assistant with controls to configure various parts of the host.
|
||||
|
||||
### {% linkable_title Hass.io OS %}
|
||||
Hass.io is currently using a forked version of ResinOS as our operating system. ResinOS has been designed to run a minimal environment for Docker, simple over the air updates and connect to the ResinIO cloud. Our fork removed the ResinIO logic. Over time, ResinOS has been evolving but not in a direction that is aligned with our goals, resulting in the maintenance of our fork to take up a lot of time.
|
||||
|
||||
The ResinOS build system is based on the Yocto Project. This is a very powerful system, but also requires specific support for each hardware platform need to be specifically added and maintained (like each version of Raspberry Pi), which caused long build and development times for Hass.io.
|
||||
|
||||
All these factors made us decide to build our own, custom, operating system. We’re obviously not starting from scratch, but instead, are basing it off [Buildroot] as the foundation and use [RAUC] for over the air updates.
|
||||
|
||||
Some things that the new operating system will be able to do:
|
||||
- Easier to add support for new hardware.
|
||||
- Updating will be atomic and has a Fail-safe. If a system fails to boot after an OS upgrade, it will fallback, by booting the previous working version.
|
||||
- Updates are required to be securely signed by the Home Assistant team, adding a whole new level of security.
|
||||
- Compressing the root file system, making it faster on SD cards and slow IO-Interfaces.
|
||||
- Compressing parts of the memory so that we can store more information.
|
||||
|
||||
## {% linkable_title What Hass.io users should do to prepare for these updates %}
|
||||
At this moment: Nothing.
|
||||
|
||||
The new Hass.io supervisor still supports the old ResinOS builds (our official downloads for Raspberry Pi and Intel NUC) and generic Linux installations. If you’re using a generic Linux installation on SUSE Linux or Ubuntu, you have to update your local AppArmor profile if you want to use the new functionality (instructions will be provided upon release).
|
||||
|
||||
Once our new installation images with HassioOS are released, you have to reflash your device once. You can do this without losing any configuration by using our Snapshot feature:
|
||||
- Create a snapshot of your current installation and download it to your PC.
|
||||
- Flash the SD card with the new Hass.io OS image.
|
||||
- Restore your snapshot.
|
||||
- Enjoy a new and improved Hass.io
|
||||
|
||||
[last July]: https://www.home-assistant.io/blog/2017/07/25/introducing-hassio/
|
||||
[the conclusion]: #what-hassio-users-should-do-to-prepare-for-these-updates
|
||||
[Buildroot]: https://buildroot.org/
|
||||
[RAUC]: https://www.rauc.io/
|
||||
|
|
@ -0,0 +1,44 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Our Google Assistant skill is live!"
|
||||
description: "The Google Assistant integration for Home Assistant Cloud is now available to all."
|
||||
date: 2018-04-24 00:01:00
|
||||
date_formatted: "April 24, 2018"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Announcement
|
||||
og_image: /images/blog/2018-04-google-assistant/google-assistant-home-assistant.png
|
||||
---
|
||||
|
||||
<p class='img'>
|
||||
<img
|
||||
src='/images/blog/2018-04-google-assistant/google-assistant-home-assistant.png'
|
||||
alt='Home Assistant logo and the Works with the Google Assistant badge'
|
||||
/>
|
||||
</p>
|
||||
|
||||
Guess what? Yep, our Google Assistant Smart Home skill is live! It's a mouthful but it means that you can now control your Home Assistant devices via any Google Assistant enabled device by simply saying things like "Ok Google, turn on the lights".
|
||||
|
||||
To get started:
|
||||
|
||||
- [Enable Home Assistant Cloud](/cloud/#enabling-the-cloud)
|
||||
- Install our skill for Google Assistant. As of this writing, the link is not live yet: you can find it by opening the Google Home app -> Home Control, tap on the blue + at the bottom right and find Hass.io in the list.
|
||||
- Optional: [Tweak the devices](/cloud/google_assistant/) that are getting exposed to Google Assistant.
|
||||
|
||||
Things to note:
|
||||
|
||||
- The skill is called Hass.io, but will work with normal Home Assistant too. The name was necessary to avoid confusion between Home Assistant, Google Assistant and Google Home.
|
||||
- Works with Home Assistant 0.65.6 or later.
|
||||
- All message handling is done local and is [open source](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/google_assistant/trait.py).
|
||||
- If you have an Android device with Google Assistant, you can control your devices too.
|
||||
- Home Assistant 0.68 will introduce a button to the Cloud config panel to trigger a sync of available devices.
|
||||
|
||||
Home Assistant Cloud is still in open beta and free to use. Open beta period has been extended to June 1. Many thanks to [Quadflight] for providing the Raspberry Pis that Google used for physical testing and thanks to [Arsaboo] for helping with testing.
|
||||
|
||||
<div class='videoWrapper'>
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/TQ3CoEHz5Xs" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
[Quadflight]: https://github.com/quadflight
|
||||
[Arsaboo]: https://github.com/arsaboo
|
||||
Loading…
Add table
Add a link
Reference in a new issue