First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
+First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
diff --git a/blog/posts/3/index.html b/blog/posts/3/index.html index 128c0ee355..8ce4057f77 100644 --- a/blog/posts/3/index.html +++ b/blog/posts/3/index.html @@ -573,7 +573,7 @@ Map in Home Assistant showing two people and three zones (home, school, work)
It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
-See GitHub for more detailed release notes.
+See GitHub for more detailed release notes.
Migration note: the scheduler component has been removed in favor of the automation component.
-Inspried by a feature requests I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the systemmonitor sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
diff --git a/blog/posts/4/index.html b/blog/posts/4/index.html index 6c06ed3ce5..74642bf84f 100644 --- a/blog/posts/4/index.html +++ b/blog/posts/4/index.html @@ -373,10 +373,10 @@
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.
+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.
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
@@ -456,7 +456,7 @@ James has worked very hard to add support for IP cameras to Home Assistant which
-To update to the latest version, run scripts/update. Please report any issues on GitHub.
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
scripts/update. Please report
-To update to the latest version, run scripts/update. Please report any issues on GitHub.
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
scripts/update. Please report
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.
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
scripts/update. Please report
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.
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.
scripts/update. Please report
diff --git a/blog/posts/5/index.html b/blog/posts/5/index.html index cb1aa23b01..3528588e3e 100644 --- a/blog/posts/5/index.html +++ b/blog/posts/5/index.html @@ -344,7 +344,7 @@ The old logo, the new detailed logo and the new simple logo.
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.
+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.
@@ -770,7 +770,7 @@ password=YOUR_PASSWORDdiff --git a/blog/posts/6/index.html b/blog/posts/6/index.html index 61d65954a2..8bfc853bd7 100644 --- a/blog/posts/6/index.html +++ b/blog/posts/6/index.html @@ -273,7 +273,7 @@ This article will try to explain how they all relate.
diff --git a/components/alarm_control_panel.alarmdotcom/index.html b/components/alarm_control_panel.alarmdotcom/index.html index 33c30a8f31..0d36b8e7c9 100644 --- a/components/alarm_control_panel.alarmdotcom/index.html +++ b/components/alarm_control_panel.alarmdotcom/index.html @@ -151,7 +151,7 @@
diff --git a/components/alarm_control_panel.manual/index.html b/components/alarm_control_panel.manual/index.html index ed2c159e5f..1da217e2b9 100644 --- a/components/alarm_control_panel.manual/index.html +++ b/components/alarm_control_panel.manual/index.html @@ -183,7 +183,7 @@
diff --git a/components/alarm_control_panel.mqtt/index.html b/components/alarm_control_panel.mqtt/index.html index 654b2c0c5d..aa5f56472b 100644 --- a/components/alarm_control_panel.mqtt/index.html +++ b/components/alarm_control_panel.mqtt/index.html @@ -171,7 +171,7 @@