Home Assistant

Visualize your IoT data

Fabian Affolter five minutes reading time
  • How-To
  • IoT-Data
 Comments

The history component is tracking everything that is going on within Home Assistant. This means that you have access to all stored information about your home. Our history is not a full-fledged graphical processing and visualization component as you may know from systems and network monitoring tools. The current limitation is that you only can select a day for a visual output of your information and not a period. Also, there is no possibility to drill down on a specific entity.

This blog post will show you ways to export data for reporting, visualization, or further analysis of automation rules.

Read on →

0.24: SQLAlchemy, KNX, Join by Joaoapps, and SimpliSafe.

Fabian Affolter three minutes reading time
  • Release-Notes
 Comments

It’s time for Home Assistant 0.24 and it’s full of new integration for your Home. It contains some structural changes to our history which requires action from your end, so please keep reading.

MapQuest discontinued their free and direct tile access by Monday, July 11, 2016. With CARTO we found a very cool and suitable solution. They allow us to use their tile for the map. Thank you, CARTO.

Roy Hooper did an amazing job migrating the history support from being tied to SQLite to use the ORM SQLAlchemy instead. This means that you can now use any SQL backend for the history. So besides SQLite you can now databases like MySQL or PostgreSQL. However, this does require that you install SQLAlchemy and run a command to migrate your existing history over. We tried to make the process as seamless as possible by introducing a new command line script:

$ pip3 install SQLAlchemy
$ hass --script db_migrator --config /path/to/config

You can omit the --config option if you use the default configuration directory. Run the script with --help to get more options.

Hotfix 0.24.1 - July 21

Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to @n8henrie and @AlucardZero.

Breaking changes

  • Migrating existing databases (see above).
  • The APCUPSd Sensor was updated. This will need that you modify your configuration.yaml file.
  • Entity IDs of Verisure locks will change. This is a one time change but should improve readability.

PocketCHIP running Home Assistant

Fabian Affolter two minutes reading time
  • How-To
 Comments

Over a year ago I participated in the kickstarter campaign for “CHIP - The World’s First Nine Dollar Computer” by Next Thing Co.. I went for the PocketCHIP because of the idea. Display, built-in storage (thus no need for SD cards), battery-powered, and a keyboard are pretty nice features. Last week a package arrives…

Read on →

0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV

Paulus Schoutsen three minutes reading time
  • Release-Notes
 Comments

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!

Breaking changes

  • Homematic thermostat configuration has changed and now depends on the new Homematic component.

Hotfix 0.23.1 - July 2

  • 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)

FAQ

  • 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: 665 to your configuration.yaml file.

Using USB webcams with Home Assistant

Fabian Affolter four minutes reading time
  • How-To
 Comments

In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.

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 →

0.22: Pandora, BT Home Hub 5 and local file camera.

Paulus Schoutsen two minutes reading time
  • Release-Notes
 Comments

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!

Breaking change

  • The new Netatmo support caused us to change how Netatmo are configured. It’s now done via it’s own component.
netatmo:
    api_key: API_KEY
    secret_key: SECRET_KEY
    username: username
    password: password

Hotfix 0.22.1 - June 20

  • Insteon Hub lights will load again

Home Assistant at PyCon 2016

Paulus Schoutsen two minutes reading time
  • Video
 Comments

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.

Home Assistant developers 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 →

0.21: Improved Web and support for EnOcean, LIRC and Osram Lightify

Paulus Schoutsen two minutes reading time
  • Release-Notes
 Comments

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:

Breaking Changes

  • 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

Hotfixes 0.21.1 and 0.21.2

We released two hotfixes to address some issues that couldn’t wait till the next release.

0.21.1 - June 12
  • 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)
0.21.2 - June 15
  • Fix input_select calling the set_option service again when changed (@persandstrom)
  • Fix more info dialog not being able to open on Safari (@balloob)
  • Add support for OPTIONS HTTP command to get CORS working (@JshWright)

Community Highlights

Paulus Schoutsen 1 minute reading time
  • Community
  • Video
 Comments

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 - cli for making scenes

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.

Videos

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.

iBeacons: How to track things that can’t track themselves (part II)

Greg Dowling eight minutes reading time
  • iBeacons
  • Device-Tracking
  • OwnTracks
 Comments

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.

Tracking things 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 →