Version 0.101 of Home Assistant has been released. Home Assistant is an open source home automation platform that runs on Python 3. It runs via Hassbian on a Raspberry Pi 3 or a Linux, macOS or Windows computer. It supports detecting devices such as Nest thermostats, Philips Hue, Belkin WeMo switches, Mr. Coffee coffee makers, the smart switches from IKEA and the mqtt protocol. In addition, it can control these devices and apply automation where possible. For more information, we refer to this page and our Forum. The release notes for this release can be found below.
It is almost the end of Hacktoberfest, and boy, it was a good one. We had a total of 1318 PRs merged in the last month. And most of them are in this release!
We had: 154 authors on home-assistant 184 authors on home-assistant.io 30 authors on home-assistant-polymer. A lot of thanks to all the contributors!
API Password and trusted networks
It is no longer possible to make authenticated requests using trusted networks or by appending? Api_password = X to the URL. You will now first need to get an authentication token and use that token to make requests.
These features were deprecated in Home Assistant 0.90 and 0.91 (released around April 2019). It was initially planned to be dropped in Home Assistant 0.96 (released July 17, 2019).
The support of configuring the auth providers for API Password and Trusted Networks via the HTTP configuration is also removed. It now needs to be configured in the auth provider section (docs).
Direct authentication meant that you could make an authenticated request without a bearer token by making the request from a trusted network or appending? Api_password = X to the URL.
These features are still available as authentication providers (docs).
You can use Long-Lived Access Tokens that can be created in the fronted on your profile page. These tokens will not expire and can be added in the header of the request. See the developer documentation for more info.
Or you can use a webhook-based integration. A webhook is a unique hard to guess URL that can be used to send data to Home Assistant. Requests made to webhooks do not need authentication. Your webhook should be available from the internet, if you have a cloud subscription, the cloud will take care if this. You can find the cloud webhook URLs on your cloud configuration page.
As you may have already read, we’ll be sunsetting Hassbian.
Hassbian was a superset of Raspbian optimized for Home Assistant. With limited time from the developers and easier alternatives as Hass.io it is time to sunset Hassbian.
For more info, read the blog post
This release includes improved support for alarms, covers, locks and sensors. A “for” option was added in release 0.100 which allows you to specify triggers for when a certain device has been in a certain state for a period of time, in this release we added support for it in the automation editor.
A lot has happened on the frontend; we had a ton of Hacktoberfest PRs that added localization to the frontend and made our user experience better. A special shout out to @springstan who did a lot of localization work, we now have the biggest part of our UI translatable!
Thanks a lot to all the contributors!
We now have our own confirmation dialogs thanks to @ timmo001! No more ugly browser modals.
In the last release, we changed all the JSON inputs to YAML inputs, this release we add a code editor to all the YAML and Jinja2 inputs. This makes it a lot easier to read and write YAML.
The entity registry is now also migrated to a datatable so you can easily search and sort your entities so it is easier to find the one you are looking for.
We improved the device picker in automations, you can now search them and see in what area the device is.
mdonoughe added support the activate scene action in the automation editor.
In other news
Proud to announce that the Visual Studio Code add-on for @home_assistant reached v1.0.0!
This version ships the second generation code-server, VSCode 1.39, HA extension 1.3, updates MDI ext and adds a rainbow indent function
Oh, and it is FAST pic.twitter.com/eBe8CirZ4B
– Franck Nijhof (@Frenck) October 26, 2019
– Esther Makes Tech (@esthermakestech) October 19, 2019
– Esther Makes Tech (@esthermakestech) October 19, 2019
– Gabe Scelta (@sfgabe) October 14, 2019
Restriction Card for @home_assistant released
Client-side security for your Lovelace cards
* Options to hide / block / lock / password-protect / confirm interactions with cards
* Set conditions for when to apply
* Set exemptions based on usershttps://t.co/psiVBf9U7N
– Ian Richardson (@iantrich) October 17, 2019
- Add Airly integration (@bieniu – # 26375) (airly docs) (new-integration)
- Add Apprise notification integration (@caronc – # 26868) (apprise docs) (new-integration)
- New sensor platform integration for Orange and Rockland Utility smart energy meter (@bvlaicu – # 27571) (oru docs) (new-integration)
- Add sinch integration (notify component) (@bendikrb – # 26502) (sinch docs) (new-integration)
- Add Solar-Log platform (@ Ernst79 – # 27036) (solarlog docs) (new-integration)
- New platform for Microsoft Teams (@peroyvind – # 27981) (msteams docs) (new-integration)
- UniFi – Bandwidth sensors (@ Kane610 – # 27229) (unifi docs) (breaking change) (new platform)
- Neato battery sensor (@dshokouhi – # 27286) (neato docs) (new platform)
- Add sensor platform to Airly integration (@bieniu – # 27717) (airly docs) (new platform)
- Move imports in mqtt component (@exxamalte – # 27835) (mqtt docs) (new platform)
|Operating systems||Script language|