diff --git a/atom.xml b/atom.xml index a0d56444d2..c575177758 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-03-18T09:26:34+00:00 + 2017-03-18T17:08:17+00:00 https://home-assistant.io/ diff --git a/blog/2014/12/18/website-launched/index.html b/blog/2014/12/18/website-launched/index.html index dc0640c305..50d0fb50e7 100644 --- a/blog/2014/12/18/website-launched/index.html +++ b/blog/2014/12/18/website-launched/index.html @@ -3,17 +3,14 @@ - Website launched! - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Website launched!

- - -
Paulus Schoutsen @@ -92,40 +70,23 @@
    - -
  • Website
    • - -
- Comments -
-
- -

I finally took the time to setup a simple website to help people getting started with Home Assistant. The process was super smooth thanks to the great tools Jekyll and Octopress and the great services GitHub Pages and CloudFlare.

- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html index 4844b892ac..9dcec7c0f6 100644 --- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html +++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html @@ -3,17 +3,14 @@ - Home Control, Automation & the Smart Home - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Home Control, Automation & the Smart Home

- - -
Paulus Schoutsen @@ -92,32 +70,19 @@
    - -
  • Internet-of-Things
    • - -
- Comments -
-
- -

The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home. This article will try to explain how they all relate.

-

The first thing to introduce is the Internet of Things (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.

-

There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a hub.

-

As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers home control.

-

Hub dashboard example @@ -126,61 +91,36 @@ This article will try to explain how they all relate.

A step up from home control is to have the user setup triggers to send commands based on information in the home control layer. For example, to turn on the lights when a person arrives home. A hub with these capabilities is capable of home automation.

-

Most hubs on the market today offer this in various degrees of functionality and usability. Some IoT-capable devices offer this too, but only control themselves and are usually limited to location and time-based events.

-

The last category, and this is still very much in the future, is the smart home. A self-learning and adopting system that will decide which events should impact other devices.

-

An example of a smart home in action is that it observes that when person A comes home, the lights in the living room and the kitchen switch on. While if person B comes home, the lights in the living room and the study room are switched on. The next time person A or B comes home, the smart home will turn on its preferred lights without any configuration being set by the user.

-

A glimpse today at how the future can look is the Nest thermostat. A thermostat smart enough to learn your schedule and adjust its own temperature accordingly.

-

All this results in the following overview of Home Automation.

-

Home Automation landscape Overview of the home automation landscape.

-

Challenges

-

You are probably wondering, this all seems relatively simple, why don’t I have my very own smart home yet? There are a couple of challenges today that keep us from stepping into the future.

-

More Internet of Things-capable devices

-

The majority of the IoT products out there are either lights, switches or presence detection. That’s not enough for your home to be very smart about. We need televisions, fridges, ovens and more to join the party to increase the number of devices that we can control.

-

More data

-

Most first generation IoT devices are only exposing information that is needed for controlling it. We need to be able to track all interactions with each device for our smart home to learn how interaction with devices influence other things. For example, we need to be able to track how many cups of coffee were made or how often the fridge was open. This will increase the information flow and open up a whole bunch of new possibilities. For example, the smart home can order new coffee when you’re running low.

-

Easy to use, open software that we can trust

-

To increase adoption we will need people to trust their smart home system. It will be very tough to convince people to upgrade all their devices and upload all interactions with each of them to the cloud. This data could reveal their whole life including all bad habits. That’s why such a system should be simple and open-source so people can validate that their data generated at home stays home.

-

Anoter important booster for adoption is that the software should be easy to set up and use by the average user. A lot of people are not burning their hands yet on Home Automation because they are scared of configurating it.

-

Home Assistant is trying to be this software. It is not there yet but trying hard. Device discovery and a user interface for configuring home automation are problems we hope to tackle in 2015 while not sacrificing any modularity or usability.

-

Happy new year!

- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html b/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html index bcee24187f..acc40de3d4 100644 --- a/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html +++ b/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html @@ -3,17 +3,14 @@ - Hello PushBullet, nice talking to you - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Hello PushBullet, nice talking to you

- - -
Paulus Schoutsen @@ -92,52 +70,32 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

One of the things that was missing in Home Assistant for a while was a way to communicate with users. Wouldn’t it be nice to get a message when important events happen like the lights being turned on while no one is home? Since the Home Assistant frontend runs as a web application on the phone, we have no way to bring ourselves to the front. This is where the new notify component comes in, powered by PushBullet.

-

The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome PushBullet but any other messaging platform can be easily added.

-

A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.

-

Read on to learn how to enable the notify component and integrate it with other components.

- -

Enabling the notify component

-

To enable the new notify component, add the following to your home-assistant.conf:

- 
[notify]
 platform=pushbullet
 api_key=ABCDEFGHJKLMNOPQRSTUVXYZ
-

You can get your api key from your account page on PushBullet.com.

-

Sending messages from your component

-

To be able to send messages, the notify component has to be loaded and initialized successfully.

- 
import homeassistant.loader as loader
 
 def setup(hass, config):
@@ -146,21 +104,13 @@
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html b/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html index 3a38441e9b..9ea31b172e 100644 --- a/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html +++ b/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html @@ -3,17 +3,14 @@ - Bootstrapping your setup with Discovery - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Bootstrapping your setup with Discovery

- - -
Paulus Schoutsen @@ -92,52 +70,30 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.

-

The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.

-

Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.

-

To enable the discovery component, add the following to your home-assistant.conf:

- 
[discovery]
-

A new discovery section has been added to the Adding a new platform page with instructions how to make your platform discoverable.

- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/01/13/nest-in-da-house/index.html b/blog/2015/01/13/nest-in-da-house/index.html index d655a991cf..4fefb77e14 100644 --- a/blog/2015/01/13/nest-in-da-house/index.html +++ b/blog/2015/01/13/nest-in-da-house/index.html @@ -3,17 +3,14 @@ - Nest in the house! - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Nest in the house!

- - -
Paulus Schoutsen @@ -92,33 +70,20 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as we’re expanding the supported devices. Today, we’re proud to introduce Nest Thermostat integration for Home Assistant contributed by Stefano Fiorini!

-

-

The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package python-nest by jkoelker to talk to the Nest.

-

If you own a Nest thermostat, add the following lines to your home-assistant.conf:

- 
[thermostat]
 platform=nest
 username=YOUR_USERNAME
@@ -126,21 +91,13 @@
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/01/24/release-notes/index.html b/blog/2015/01/24/release-notes/index.html index 6290cabf76..2a0f79edba 100644 --- a/blog/2015/01/24/release-notes/index.html +++ b/blog/2015/01/24/release-notes/index.html @@ -3,17 +3,14 @@ - Release notes for January 24, 2015 - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Release notes for January 24, 2015

- - -
Paulus Schoutsen @@ -92,34 +70,21 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

I have just merged the latest version of the development branch into master. Here are some of the highlights of this release:

-

Configuration via the frontend
Phliips Hue will now be auto discovered and uses the new configurator component to interact with the user to finish the setup process.

-

Wink Hub support
Thanks to the work done by John McLaughlin and Geoff Norton we now support the lights, switches and sensors that are connected to the Wink hub.

-

The getting started guide and component page have been reorganized
The getting started instructions have been split into separate pages per component and a general overview page. The goal is to have a page per component that describes:

-
  • What it does
  • How to set it up
    • @@ -127,28 +92,18 @@ The getting started instructions have been split into separate pages per compone
  • Which services it provides
  • Additional development tips
-

More reasonable errors
Home Assistant should now throw better errors and offer solutions if you do not have the right version of Python 3, forgot to clone the git submodules or install the dependencies.

-

Streamlined first launch
Home Assistant now supports --open-ui and --demo-mode command line properties to open the browser automatically and have something to show. Home Assistant now supports to be run without a password, allowing the interface to login automatically on launch.

- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html index 1b37fb0900..4cc9be01e0 100644 --- a/blog/2015/02/08/looking-at-the-past/index.html +++ b/blog/2015/02/08/looking-at-the-past/index.html @@ -3,17 +3,14 @@ - Looking at the past - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Looking at the past

- - -
Paulus Schoutsen @@ -92,71 +70,45 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

Ever since the launch of Home Assistant you have been able to track the state of your house. But the view has always been limited to what the current state is. Not what it was. Today we are going to change that by introducing two brand new components:

-
  • Recorder component that will record every event to a SQLite database
  • History component that will query and aggregate the recorded events
-

By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.

-

Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.

-

The history component will be enabled for new users by default. For current users, run scripts/update to upgrade to the latest version and add [history] to your home-assistant.conf file.

-

-

Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.

- -

Tracking history is an exciting next step for Home Assistant and will power the next generation of features. Here a list of some of the cool things that can now be build:

-
  • Time Machine: explore the state of your house at any point in the past
  • Smart Home: analyze behavior and use it to automate your house
  • Summarize usage of the different components of your house
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/02/24/streaming-updates/index.html b/blog/2015/02/24/streaming-updates/index.html index 2040a0b946..2c90833f08 100644 --- a/blog/2015/02/24/streaming-updates/index.html +++ b/blog/2015/02/24/streaming-updates/index.html @@ -3,17 +3,14 @@ - Streaming updates - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Streaming updates

- - -
Paulus Schoutsen @@ -92,56 +70,31 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.

-

A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.

-

- -

Streaming updates has been implemented using the HTML5 EventSource tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The server-side code is 50 lines and the client-side code is 80 lines of code.

-

All events that happen on the server will now also be sent to the browser. This turns any browser running the UI into a fully functioning slave instance of Home Assistant. This opens up new possibilities for Home Assistant components that live completely client-side.

-

Implementing EventSource was not without challenges. Here are some of the issues that had to be solved:

-

A connection can go stale in Chrome without any event handler being called. This happens when a device goes into standby. For computers this is rare but for phones this occurs quite often. This has been solved by sending a regular ping from the server. The frontend will assume the connection has gone stale when it hasn’t heard any communication for a while. Sending a ping will also help the server detect broken connections and clean them up.

-

Another issue that I encountered is that Safari and Firefox would not fire the open event when the connection has been opened but when the first message has been received. To work around this the server will now fire a ping when the connection gets opened.

- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html b/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html index 98515a5a89..264fee78b1 100644 --- a/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html +++ b/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html @@ -3,17 +3,14 @@ - Home Assistant moving to YAML - Home Assistant - - @@ -21,39 +18,31 @@ - - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Home Assistant moving to YAML

- - -
Theodor Lindquist @@ -92,46 +69,26 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.

-

The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.

-

The home-assistant.conf.example has been replaced with an updated configuration.yaml.example.

-

Users of Home Assistant should migrate as the old configuration format is deprecated.

- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html index 23b5fc6255..0c71dc0054 100644 --- a/blog/2015/03/08/new-logo/index.html +++ b/blog/2015/03/08/new-logo/index.html @@ -3,17 +3,14 @@ - New logo for Home Assistant - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

New logo for Home Assistant

- - -
Paulus Schoutsen @@ -92,47 +70,28 @@
    - -
  • Organisation
    • - -
- Comments -
-
- -

It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, Jeremy Geltman has come to the rescue and contributed a brand new logo for Home Assistant.

-

The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).

-

The old logo, the new detailed logo and the new simple logo.

- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html index 9782369143..287e03aece 100644 --- a/blog/2015/03/11/release-notes/index.html +++ b/blog/2015/03/11/release-notes/index.html @@ -3,17 +3,14 @@ - Release notes for March 11, 2015 - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Release notes for March 11, 2015

- - -
Paulus Schoutsen @@ -92,28 +70,17 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

It has only been a little over a week since Theodor introduced YAML support for Home Assistant but so much has already happened that it is time for a summary of recent changes. Before mentioning the highlights I want to thank andythigpen, jamespcole and theolind for numerous bug fixes, enhancements and new contributions. Thanks!

-

Monitor local resources.
Theodor has contributed a new sensor platform to allow you to monitor disk usage, memory usage, CPU usage and running processes. This platform has superseded the process component which is now considered deprecated.

- 
# Example configuration.yaml entry
 sensor:
   - platform: systemmonitor
@@ -125,47 +92,31 @@ Theodor has contributed a new sensor platform to allow you to monitor disk usage
         arg: kodi
-

Experimental Z-Wave support
There is now experimental support for connecting Z-Wave networks using a Z-Wave USB stick. Right now it only integrates Z-Wave sensors into Home Assistant. Our goal is to get this tested by more people before adding support for other Z-Wave devices.

-

The new component is built on top of python-openzwave. This package is currently not distributed on PyPi so we’ve added a script scripts/build_python_openzwave to install it on your machine. Alternatively you can use the Docker image which is ready to go.

-

The development was done using an AEON Z-Wave USB stick and an AEON Z-Wave MultiSensor.

- 
# Example configuration.yaml entry
 zwave:
   usb_path: /dev/ttyUSB0
-

Voice control
An initial version of voice control for Home Assistant has landed. The current implementation consists of two parts.

-

The first part is a component called conversation that exposes the service conversation/process. This service is capable of processing text and translating them into commands for devices. For now it will only support commands in the format of Turn <Friendly Name> <on/off>.

-

The second part is an upgrade to the frontend to use the speech-to-text in Chrome to allow users to speak commands. If you’re using Chrome, you can test this out in the demo.

- 
# Example configuration.yaml entry
 conversation:
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html index 89d737ee2f..a22f14057d 100644 --- a/blog/2015/03/22/release-notes/index.html +++ b/blog/2015/03/22/release-notes/index.html @@ -3,17 +3,14 @@ - Release notes for March 22, 2015 - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Release notes for March 22, 2015

- - -
Paulus Schoutsen @@ -92,28 +70,17 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

A new version of Home Assistant has just been pushed out. It contains bugfixes contributed by jamespcole, andythigpen, trainman419 and me. It also adds a bunch of great new features:

-

Script Andythigpen has contributed a script component. This allows users to create a sequence of service calls and delays. Scripts can be started using the service script/turn_on and interrupted using the service script/turn_off. A separate page has been added to the frontend to see the status of your scripts.

- 
# Example configuration.yaml entry
 script:
   # Turns on the bedroom lights and then the living room lights 1 minute later
@@ -133,12 +100,9 @@ Andythigpen has contributed a script component. This allows users to create a se
           entity_id: group.living_room
- -

Scene I (Paulus) have contributed a scene component. A user can create scenes that capture the states you want certain entities to be. For example a scene can contain that light A should be turned on and light B should be bright red. Deactivating a scene will restore the previous state from before the scene was activated. Just like scripts, scenes have their own separate page to see which scenes are on.

- 
# Example configuration.yaml entry
 scene:
   - name: Romantic
@@ -150,11 +114,9 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
         brightness: 200
-

SABnzbd James Cole has contributed support to integrate SABnzbd. This will allow you to monitor your downloads from within Home Assistant and setup automation based on the information.

- 
# Example configuration.yaml entry
 sensor:
   - platform: sabnzbd
@@ -171,11 +133,9 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
         - type: 'disk_free'
-

PushOver James Cole has also contributed support for the PushOver service as a platform for the notify component. This allows components to send messages to the user using PushOver.

- 
# Example configuration.yaml entry
 notify:
     platform: pushover
@@ -186,21 +146,13 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/04/25/release-notes/index.html b/blog/2015/04/25/release-notes/index.html index 4f3686fe3e..ecc8b2941b 100644 --- a/blog/2015/04/25/release-notes/index.html +++ b/blog/2015/04/25/release-notes/index.html @@ -3,17 +3,14 @@ - Release notes for April 25, 2015 - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Release notes for April 25, 2015

- - -
Paulus Schoutsen @@ -92,56 +70,37 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

It’s been a month since the latest update and a lot has happened again. Here a quick overview of the new things.

-

Line Charts James has upgraded the history in the frontend to support line graphs. Line graphs will be shown for any entity that has a unit of measurement. The line graphs will also be shown in the more info card of an entity. See the demo for a live example.

-

-

ISY994 hub support Ryan has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.

-

He has created an extensive getting started guide which can be found on the ISY994 component page.

- 
# Example configuration.yaml entry
 isy994:
-

Logbook I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. See the demo for a live example.

- 
# Example configuration.yaml entry
 logbook:
- -

Transmission support James has also contributed support for integrating Transmission into Home Assistant.

- 
# Example configuration.yaml entry
 sensor:
   platform: transmission
@@ -156,10 +115,8 @@
     - type: 'upload_speed'
-

Modbus support Kixam has contributed support for modbus, a serial communication protocol to control PLCs. It currently supports sensors and switches which can be controlled over serial, TCP and UDP connections.

- 
# Example configuration.yaml entry
 modbus:
   type: serial
@@ -197,21 +154,13 @@
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/05/09/utc-time-zone-awareness/index.html b/blog/2015/05/09/utc-time-zone-awareness/index.html index daea841c4f..546bc2bce9 100644 --- a/blog/2015/05/09/utc-time-zone-awareness/index.html +++ b/blog/2015/05/09/utc-time-zone-awareness/index.html @@ -3,17 +3,14 @@ - UTC & Time zone awareness - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

UTC & Time zone awareness

- - -
Paulus Schoutsen @@ -92,67 +70,41 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

I have recently merged code to refactor Home Assistant to use only UTC times internally. A much needed refactor. I’ve added some extra test coverage to time sensitive parts to ensure stability. The code has been live in the dev branch for the last 9 days and will be soon released to the master branch.

-

From now on all internal communication will be done in UTC: time changed events, datetime attributes of states, etc. To get the current time in UTC you can call homeassistant.util.dt.utcnow(). This is a timezone aware UTC datetime object. homeassistant.util.dt is a new util package with date helpers.

-

There is also such a thing as local time. Local time is based on the time zone that you have setup in your configuration.yaml. Local times should only be used for user facing information: logs, frontend and automation settings in configuration.yaml.

-

Setting up your time zone

Setting up a time zone happens in configuration.yaml. If you have no time zone setup, it will be auto detected using the existing detection code using freegeoip.net. You can find a list of compatible time zones on Wikipedia.

- 
homeassistant:
   time_zone: America/Los_Angeles
-

Compatibility

The changes to the code are mostly backwards compatible. The old hass.track_time_change and hass.track_point_in_time use now internally two new methods: hass.track_utc_time_change and hass.track_point_in_utc_time. The usage of the old methods have not changed and should be backwards compatible.

-

This refactor adds a new migration for the database adding a utc_offset column to events and states. This information is currently not used but can prove useful in the future when we start analyzing the historical data.

-

Backwards incompatible stuff

-

All built-in components have been upgraded. The following list is only for people that run custom components:

-
  • hass.track_time_change and hass.track_point_in_time will now return a time zone aware datetime object. Python does not allow comparing a naive with an aware datetime object.
  • the sun attributes for rising and setting are now in UTC. The methods sun.next_rising(hass) and sun.next_setting(hass) are backwards compatible, just be careful if you used to read the raw attributes.
  • the API sends all times in UTC. If you use anything else besides the frontend to talk to HA, make sure it handles it differently.
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html index fc530aeba3..81d81de828 100644 --- a/blog/2015/05/14/release-notes/index.html +++ b/blog/2015/05/14/release-notes/index.html @@ -3,17 +3,14 @@ - Release notes for May 14, 2015 - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Release notes for May 14, 2015

- - -
Paulus Schoutsen @@ -92,40 +70,24 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

Almost three busy weeks have past since the last release. We used this time to finally make the overhaul to use UTC as the internal date time format. We added a bunch of test coverage in the process to make sure the transition went smoothly. Pleas see the blog post about the UTC refactor for backwards incompatible changes.

-

This release includes a significant startup boost for the frontend and a fix for Wemo discovery after their latest firmware upgrade.

-

I would like to give a big shout out to our newest contributor fabaff for taking the time to improve the documentation.

-

To update to the latest version, run scripts/update. Please report any issues on GitHub.

- -

Overwriting Entity Attributes Before diving into the newly supported devices and services, I want to highlight an awesome configuration enhancement by rmkraus: overwriting entity attributes.

-

These new configuration settings allow you to overwrite entity state attributes. The main usage for this is being able to overwrite attributes that influence how an entity is shown in the interface.

- 
# Example configuration.yaml entry
 homeassistant:
   customize:
@@ -137,20 +99,16 @@ Before diving into the newly supported devices and services, I want to highlight
       entity_picture: http://graph.facebook.com/schoutsen/picture
-

MySensors Andythigpen and Theolind have added support for the MySensors platform to Home Assistant.

- 
# Example configuration.yaml entry
 sensor:
   platform: mysensors
   port: /dev/ttyACM0
-

OpenWeatherMap Fabaff has contributed support for OpenWeatherMap. This will allow you to integrate local meteorological data into Home Assistant.

- 
# Example configuration.yaml entry
 sensor:
   platform: openweathermap
@@ -166,10 +124,8 @@ Before diving into the newly supported devices and services, I want to highlight
     - type: 'snow'
-

InstaPush Fabaff has contributed support for InstaPush. This will allow you send messages from Home Assistant to your iOS and Android devices.

- 
# Example configuration.yaml entry
 notify:
     platform: instapush
@@ -180,10 +136,8 @@ Before diving into the newly supported devices and services, I want to highlight
     tracker: ABCDEFGHJKLMNOPQRSTUVXYZ
-

XMPP Fabaff has contributed support for Jabber/XMPP. This will allow you send messages from Home Assistant to anyone on Jabber/XMPP.

- 
# Example configuration.yaml entry
 notify:
     platform: xmpp
@@ -192,10 +146,8 @@ Before diving into the newly supported devices and services, I want to highlight
     recipient: YOUR_RECIPIENT
-

Notify My Android Fabaff has contributed support for Notify My Android. This will allow you to send messages from Home Assistant to your Android device.

- 
# Example configuration.yaml entry
 notify:
     platform: nma
@@ -203,10 +155,8 @@ Before diving into the newly supported devices and services, I want to highlight
     api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
-

Time & Date sensor Fabaff has contributed a time & date sensor. This will allow you to show the current time/date on the dashboard.

- 
# Example configuration.yaml entry
 sensor:
   platform: time_date
@@ -218,21 +168,13 @@ Before diving into the newly supported devices and services, I want to highlight
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/06/10/release-notes/index.html b/blog/2015/06/10/release-notes/index.html index 94180a82de..2d754a073f 100644 --- a/blog/2015/06/10/release-notes/index.html +++ b/blog/2015/06/10/release-notes/index.html @@ -3,17 +3,14 @@ - Release notes for June 10, 2015 - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

Release notes for June 10, 2015

- - -
Paulus Schoutsen @@ -92,41 +70,25 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

Wow, almost a month has gone by since the last release and this release is packed. The biggest part of this release is probably one that you won’t notice: the frontend has been upgraded from Polymer 0.5 to the brand new released Polymer 1.0. Polymer has been declared stable by the Google overlords which will allow us to expand functionality that was waiting for this moment to arrive.

-

This release sets a record for the amount of people involved: 8! Andythigpen, Jamespcole, Azelphur, Fabaff, Dutchy-, Fbradyirl, wind-rider and ettisan, thanks a lot for your contributions!

-

A big improvement has been brought this release by wind-rider. He took the time to revive the Chromecast support and started improving the media player integration. This triggered other people to join in resulting in a revamped media player experience and support for the Music Player Daemon.

-

Example of the new media player cards

-

To update to the latest version, run scripts/update. Please report any issues on GitHub.

- -

Before jumping into the newly supported platforms, here are the other improvements that are landing this release:

-
  • Fronted upgraded to Polymer 1.0 by @balloob
  • Include other YAML files using the !include keyword by @andythigpen
    • @@ -140,10 +102,8 @@ To update to the latest version, run scripts/update. Please report
  • Fix the device tracker getting in a deadlock by @balloob
  • Update documentation by @fabaff
-

Music Player Daemon Fabaff has contributed MusicPlayerDaemon support. The mpd platform allows you to control a Music Player Daemon from Home Assistant. Right now, only playback is supported and not playlist manipulation.

- 
# Example configuration.yaml entry
 media_player:
   platform: mpd
@@ -152,10 +112,8 @@ To update to the latest version, run scripts/update. Please report
   location: bedroom
-

Command line switch A switch platform that issues specific commands when it is turned on and off. This might very well become our most popular platform as it allows anyone to integrate any type of switch into Home Assistant that can be controlled from the command line, including calling other scripts!

- 
# Example configuration.yaml entry
 switch:
   platform: command_switch
@@ -165,10 +123,8 @@ A switch platform that issues specific commands when it is turned on and off. Th
         offcmd: switch_command off kitchen
-

LimitlessLED This new platform can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight or iLight.

- 
# Example configuration.yaml entry
 light:
   platform: limitlessled
@@ -179,10 +135,8 @@ This new platform can control your LimitlessLED lights from within Home Assistan
   group_4_name: Kitchen
-

Bitcoin sensor The bitcoin platform displays various details about the Bitcoin network. If you have an online wallet from Blockchain.info the sensor is capable to show your current balance.

- 
# Example configuration.yaml entry
 sensor:
   platform: bitcoin
@@ -213,10 +167,8 @@ This new platform can control your LimitlessLED lights from within Home Assistan
     - market_price_usd
-

SMTP notificatoin platform The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient.

- 
# Example configuration.yaml entry
 notify:
   platform: mail
@@ -229,22 +181,17 @@ This new platform can control your LimitlessLED lights from within Home Assistan
   recipient: YOUR_RECIPIENT
-

Syslog notification platform The syslog platform allows you to deliver notifications from Home Assistant to the local syslog.

- 
# Example configuration.yaml entry
 notify:
   platform: syslog
-

Swiss Public transport sensor The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the component page for more information how to set it up.

-

Transmission turtle mode switch The transmission platform allows you to control your Transmission client from within Home Assistant. The platform enables you switch to your ‘Alternative Speed Limits’ (aka ‘Turtle mode’) setting.

- 
# Example configuration.yaml entry
 switch:
   platform: transmission
@@ -255,10 +202,8 @@ The swiss public transport sensor will give you the next two departure times fro
   password: YOUR_PASSWORD
-

Hikvision camera motion detection support This switch platform allows you to control your motion detection setting on your Hikvision camera.

- 
# Example configuration.yaml entry
 switch:
     platform: hikvisioncam
@@ -269,21 +214,13 @@ This switch platform allows you to control your motion detection setting on your
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html index 2ed9edc355..3de048b220 100644 --- a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html +++ b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html @@ -3,17 +3,14 @@ - IP Cameras, Arduinos, Kodi and Efergy Energy Monitors now supported - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

IP Cameras, Arduinos, Kodi and Efergy Energy Monitors now supported

- - -
Paulus Schoutsen @@ -92,32 +70,19 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

Another month has passed and some great new features have landed in Home Assistant. This month release has been made possible by balloob, ettisan, fabaff, gyran, jamespcole, michaelarnauts, miniconfig and rmkraus.

-

This release includes some architectural changes by me. The first is that the frontend is now based on a NuclearJS JavaScript backend. This has greatly helped to organize and optimize the frontend code. Another change is that Home Assistant will now install dependencies on-demand instead of installing dependencies for all supported devices.

-

IP Camera Support James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a url can be integrated.

-

Home Assistant will route the requests to your camera via the server allowing you to expose IP camera’s inside your network via the Home Assistant app.

- 
# Example configuration.yaml entry
 camera:
   platform: generic
@@ -127,16 +92,12 @@ James has worked very hard to add support for IP cameras to Home Assistant which
   still_image_url: http://194.218.96.92/jpg/image.jpg
-

To update to the latest version, run scripts/update. Please report any issues on GitHub.

- -

Arduino Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at the docs for an extensive guide to get started.

- 
# Example configuration.yaml entry
 switch:
   platform: arduino
@@ -159,10 +120,8 @@ To update to the latest version, run scripts/update. Please report
       type: analog
-

Kodi (XBMC) Ettisan has contributed a Kodi (XBMC) platform for the media player component. This allows you to track all the media that you are playing and allow you to control it.

- 
# Example configuration.yaml entry
 media_player:
   platform: kodi
@@ -172,10 +131,8 @@ To update to the latest version, run scripts/update. Please report
   password: my_secure_password
-

TP-Link Michael has added TP-Link support to the device tracker. This allows you to now detect presence if you have a TP-Link router.

- 
# Example configuration.yaml entry
 device_tracker:
   platform: tplink
@@ -184,10 +141,8 @@ To update to the latest version, run scripts/update. Please report
   password: YOUR_ADMIN_PASSWORD
-

Efergy energy monitor Miniconfig has contributed support for the Efergy energy meters. To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click “Add token”.

- 
# Example configuration.yaml entry
 sensor:
   platform: efergy
@@ -201,10 +156,8 @@ To update to the latest version, run scripts/update. Please report
       currency: $
-

Forecast.io Fabian has added support for Forecast.io to get weather forecasts for Home Assistant. You need an API key which is free but requires a registration. To add Forecast.io to your installation, add the following to your configuration.yaml file:

- 
# Example configuration.yaml entry
 sensor:
   platform: forecast
@@ -225,21 +178,13 @@ Fabian has added support for Forecast.io to g
- -

Comments

- -
- - -
- - - \ No newline at end of file + diff --git a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html index 37e826cd22..0bc477fac3 100644 --- a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html +++ b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html @@ -3,17 +3,14 @@ - MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported - Home Assistant - - @@ -21,39 +18,32 @@ - - - -
-
Home Assistant
-
-
- - -
-
- -
-
-

MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported

- - -
Paulus Schoutsen @@ -92,28 +70,17 @@
    - -
  • Release-Notes
    • - -
- Comments -
-
- -

It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.

-

MQTT Support The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.

- 
# Example configuration.yaml entry
 mqtt:
   broker: IP_ADDRESS_BROKER
@@ -125,12 +92,9 @@
   password: your_secret_password
- -

Raspberry PI GPIO Support @gbarba has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.

- 
# Example configuration.yaml entry
 switch:
   platform: rpi_gpio
@@ -139,10 +103,8 @@
     12: Light Desk
-

ASUSWRT based routers @persandstrom has contributed support to do prescence detection using ASUSWRT based routers.

- 
# Example configuration.yaml entry
 device_tracker:
   platform: asuswrt
@@ -151,10 +113,8 @@
   password: YOUR_ADMIN_PASSWORD
-

Logitech Squeezebox media player support @persandstrom also contributed support for the Logitech Squeezebox media player. This allows you to control your Logitech Squeezebox from Home Assistant.

- 
# Example configuration.yaml entry
 media_player:
   platform: squeezebox
@@ -164,10 +124,8 @@
   password: password
-

Slack notification support @jamespcole has contributed a Slack platform for the notification platform. This allows you to deliver messages to any channel.

- 
# Example configuration.yaml entry
 notify:
   platform: slack
@@ -175,10 +133,8 @@
   default_channel: '#general'
-

Edimax Smart Switches support @rkabadi has contributed support for integrating Edimax Smart Switches into Home Assistant.

- 
# Example configuration.yaml entry
 switch:
   platform: edimax
@@ -188,43 +144,30 @@
   name: Edimax Smart Plug
-

RFXtrx sensor support @danielhiversen has contributed support for RFXtrx sensors. It supports sensors that communicate in the frequency range of 433.92 MHz.

- 
# Example configuration.yaml entry
 sensor:
   - platform: rfxtrx
     device: PATH_TO_DEVICE
-

The path to your device, e.g. /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0

-

TEMPer temperature sensor support Support for Temper temperature sensors has been contributed by @rkabadi.

- 
# Example configuration.yaml entry
 sensor:
   platform: temper
- -

Comments

- -
- -
-
-