It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
- Support for Envisalink added (alarm control panel, binary sensor, sensor) (@cinntax)
- Support for Homematic added (binary sensor, light, rollershutter, sensor, switch) (@pvizeli, @danielperna84)
- New HDMI-CEC component (@happyleavesaoc, @lukas-hetzenecker)
- Major rewrite of Wink which now pushes changes to Home Assistant (@w1ll1am23)
- Core: new add reload core config service (@balloob)
- Support for persistent notifications added (@fabaff, @balloob)
- Garage door: Z-Wave support added (@turbokongen)
- Rollershutter: Z-Wave support added (@turbokongen)
- Media Player: Sony Bravia TV now supported (@aparraga)
- Sensor: Fixer.io now supported (@fabaff)
- Garage door: Control any garage door using Raspberry Pi GPIO pins (@kellerza)
- Sensor: OpenExchangeRates support added (@arsaboo)
- Notify: Pushover now supports target device, sound, URL and priority (@dale3h)
- Sensor: Netatmo now supports wind, battery and radio signals (@Jypy)
- Log successful and failed login attemps (@fabaff)
- Config: allow extracting account info into OS keyring or separate YAML file (@kellerza)
- Core: add option to not filter out duplicate states per entity (@philipbl)
- HTTP: Follow Mozilla SSL recommendations (@danieljkemp, @AlucardZero)
- Light: Z-Wave colorbulb support added (@armills)
- Core: new elevation config option added (@balloob)
- Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus)
- Lock: Vera now supported (@rhooper)
- HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob)
- Homematic thermostat configuration has changed and now depends on the new Homematic component.
- Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper)
- HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero)
- Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23)
elevation:was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning
[homeassistant.config] Incomplete core config. Auto detected elevation: 665to your
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.Read on →
It’s time for the 0.22 release. This was a pretty rough release cycle and we had to issue two hot fixes for our core improvements. But it seems now that all is good and a lot of people have reported that their installs are faster than ever and the occasional quirks no longer occur.
We are aware that our new web stack has caused issues installing Home Assistant on ARM-based platforms. This sadly includes the Raspberry Pi and Synology NAS systems. We’re working on getting to a better solution. For Raspberry Pi, the All-in-One installer will take care of everything for you. We’re working on updating our standalone Raspberry Pi installation guide.
There are two cool things that I want to highlight in this release. The first is Pandora support. This is based on the CLI player called pianobar. This means that your machine running Home Assistant can be connected to the speakers and provide your house with tunes.
Another cool addition is the local file camera. This seems very basic at first but will allow you to generate a graph with your favorite 3rd party graphing tool and display it on your Home Assistant dashboard. We’re looking forward to see what you can do with this!
- Media Player: Pandora media player now supported (@partofthething)
- Device Tracker: BT Home Hub 5 now supported (@lwis)
- Camera: New local file platform shows any image as camera (@Landrash)
- Add Sonos snapshot and restore services (@dansullivan86)
- Device Tracker: AsusWRT in Access Point mode now supported (@linjef)
- Device Tracker: AsusWRT login using public key now supported (@mtreinish)
- Device Tracker: AsusWRT protocol to use is now auto detected (@persandstrom)
- Camera: Netatmo now supported (@jabesq)
- API documentation added in Swagger.yaml format (@wind-rider)
- Media Player: Cast devices can now be stopped (@michaelarnauts)
- MySensors: IR switch device and service now supported (@MartinHjelmare)
- Bloomsky: Voltage sensor now supported (@arsaboo)
- Sensor: New Plex sensor monitors friends streaming from your Plex server (@nkgilley)
- Component shell command can now use templates to render arguments (@partofthething)
- Rollershutter: Wink is now supported (@philk)
- Alexa: Updated documentation to show how to call scripts and scenes (@acockburn)
- Sensor: SNMP is now supported (@fabaff)
- Sensor: Support for Swiss hydrological data (@fabaff)
- The new Netatmo support caused us to change how Netatmo are configured. It’s now done via its own component.
netatmo: api_key: API_KEY secret_key: SECRET_KEY username: username password: password
- Insteon Hub lights will load again
It’s been already almost two weeks ago that a few of the Home Assistant developers headed towards Portland for PyCon 2016 - the conference about everything Python. We were there to learn all the nifty tricks to make our code better but most of all, to talk Home Automation.
Couple of Home Assistant devs. Left to right: [Paulus (@balloob)], [Alex (@infamy)], [Ryan (@rmkraus)].
On Monday I (Paulus) gave a presentation about Home Assistant to an audience of over 400 people! It was a bit scary at first but after a couple of minutes it went all great including some great questions afterwards. Slides can be found here and the talk is embedded right below:
One of the things that really impressed me was the amount of people that approached us to tell how they love Home Assistant, how it has replaced their previous solution, how they enjoyed contributing to Home Assistant and how helpful our community is. It makes me proud of Home Assistant and especially our community.Read on →
It’s time for release 0.21 and it contains massive core improvements: replacement of our home grown HTTP stack with a standardized WSGI stack. This will improve performance, speed, security and make future development of advanced HTTP features a breeze.
This work was driven by the amazing Josh Wright. His knowledge, high standards and drive for security has helped improve Home Assistant a lot ever since he started helping out. Hip hip hurray for Josh!
Alright, time for the changes:
- New HTTP stack based on WSGI (@JshWright, @balloob)
- Frontend: lots of performance improvements (@balloob)
- Initial support for EnOcean lights, sensors and switches added (@rubund)
- Light: Osram Lightify is now supported (@olimpiurob)
- Light: Insteon Hub now supports brightness (@wkonkel)
- Add support for adding HA as Windows 10 tile (@fabaff)
- Condition: time condition can now cross midnight (@jaharkes)
- Template based sensors should now throw less warnings (@Bart274)
- New LIRC component allows receiving IR commands (@partofthething)
- The Feedreader component will now persist data to disk to prevent duplicate events (@shaftoe)
- Sun: azimuth attribute added (@fabaff)
- New Flux like switch platform to change light intensity in the evening (@nkgilley)
- We no longer crash if you live in a part of the world where the sun never sets (@balloob)
- Rollershutter: RFXTRX now supported (@jacobtomlinson)
- Switch: Template switches can now execute scripts (@kellerza)
- Z-Wave: automatically heal the network at midnight (@infamy)
- Sensor: DTE Energy Bridge now supported (@kylehendricks)
- Media Player: Kodi now supports different turn off commands (@armills)
- Our work in the WSGI stack is not fully done yet. We still have a minor issues where retrieving the error log in the about screen can raise an encoding error
- The API used to incorrectly accept a JSON body with form-url-encoded headers. Our cURL examples on the website used to be wrong and have been updated.
- Make sure your configuration.yaml file contains
frontend:to serve the frontend
We released two hotfixes to address some issues that couldn’t wait till the next release.
- Add eventlet to base requirements to resolve some installation issues (@balloob)
- GTFS will filter out routes in the wrong direction (@imrehg)
- Recover from rare error condition from LIRC (@partofthething)
- Z-Wave autoheal will no longer raise exception (@balloob)
- Alexa will now execute the script before making reply (@balloob)
- Fix MJPEG camera streaming (@stjohnjohnson)
- Fix frontend in older browsers (@balloob)
- Fix history in more info dialog being cut off (@balloob)
Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our chat room and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.
SceneGen is a new command line utility developed by Andrew Cockburn that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states.
Nick Touran has been working on integrating IR remotes with Home Assistant. He made it into a component which should be available in the next release which should arrive in a couple of days. In the meanwhile, he wrote up a blog post and has put out a video showing the new integration, very cool!
Ben from BRUH Automation has put out another great video how to get started tracking your location in Home Assistant using MQTT and OwnTracks.
Muhammed Kilic has created a video how to make your Home Assistant instance accessible from the internet using the free dynamic DNS service DuckDNS.
This post is by Home Assistant contributor Greg Dowling.
In Part 1 I talked about using iBeacons to improve presence tracking. In part 2 I’ll talk about how to track things like keys that can’t track themselves by using iBeacons.
In the first part I mentioned that iBeacons just send out I’m here packets, and we used this to trigger an update when your phone came close to a fixed beacon.
But beacons don’t have to be fixed.
Your phone knows roughly where it is located (based on mobile phone masts, Wi-Fi networks or GPS). If your phone sees an I’m here message then it knows the beacon is close.
If your phone can remember (or tell a server) where it was when it last saw the iBeacon - then it knows where the beacon was. So the result of this is that you can track where an iBeacon was - even though the iBeacon doesn’t have any tracking technology itself.
So if you put an iBeacon on your keys or in your car - then you can track them.
Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!Read on →
We are always hard at work at the virtual Home Assistant headquarters to make it easier for you to get started with Home Assistant. That’s why @patchedsoul recently introduced the all-in-one installer. It allows you to get up and running with a complete Home Assistant setup by entering one line of code into your Raspberry Pi running Raspbian Jessie:
wget -Nnv https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && bash hass_rpi_installer.sh;
This feature wouldn’t be complete if it wasn’t accompanied by a new video by Ben from BRUH Automation. The video shows how to install Raspbian Jessie on your Raspberry Pi and use the new installation script to get a full Home Assistant system up and running.
Tons of new supported things in 0.20.
- Restarting now supported without forking (@jaharkes)
- Add purge days option to recorder component (@justyns, @infamy)
- Generic load_platform mechanism for entity components (@kellerza)
- Template: new
relative_timefunction to render ie.
7 seconds ago(@robbiet480)
- Sensor: supervisord now supported (@happyleavesaoc)
- Docker: we should no longer get SSL errors with requests (@lwis)
- Media Player: Google Play Music Desktop Player now supported (@GreenTurtwig)
- Notify: Twilio SMS platform added (@robbiet480)
- Device Tracker: Asus WRT will now default to SSH (but telnet is still an option) (@froz)
- Support Nest Protect smoke alarms (@khabi)
- Configurator: allow supplying a link to the user (@mnestor)
- Media Player: Roku now supported (@bah2830)
- Sensor: Last.fm now supported (@darookee, @GreenTurtwig)
- Notify: Amazon Lambda, SNS, SQS now supported (@robbiet480)
- Light: allow human readable colors in turn_on command (@robbiet480)
- YAML: new include dir options
- Media Player: LG Netcast TVs now supported (@wokar)
- Media Player: Allow enqueuing media on Sonos (@shaftoe)
- Notify: Ecobee thermostats now supported (@nkgilley)
- Sensor: Mold indicator added (@xifle)
- Export to Logentries support added (@omgapuppy)
- Group more info dialog allows control of group domain if available (@fignuts)
- Asus WRT will now default to SSH with Telnet being an option
device_tracker: platform: asuswrt protocol: telnet
I’ve been planning to write this post for a while now as we get questions like this a lot: “Why does Home Assistant use Polymer? Why not React, Redux and what not?”
It’s understandable, Polymer is quite the underdog in the world of web frameworks. A corporate backer does not guarantee popularity or an active community and this shows in the number of projects using Polymer.
Still, we use Polymer and it’s awesome. To explain why, I’ll be referencing the React workflow quite a bit, as they do a lot of things right, and show how it is done in Polymer.
Polymer gives us components for the web, just like React, but based on web standards: web components, CSS variables. These standards don’t have wide browser support yet but it’s being implemented by every major browser: It’s the future. For now they are being polyfilled and that works just fine but in the future the Home Assistant web app will be able to run native in the browsers == fast.Read on →