diff --git a/atom.xml b/atom.xml index 2e91dde334..03d8edd79e 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ @@ -13,6 +13,47 @@ Octopress + + <![CDATA[UTC & Time zone awareness]]> + + 2015-05-09T23:08:00-07:00 + https://home-assistant.io/blog/2015/05/09/utc-time-zone-awareness + 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.

+ +
1
+2
+
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.
    • +
+ +]]> + + <![CDATA[Release notes for April 25, 2015]]> @@ -163,7 +204,7 @@ James has also contributed support for integrating Transmission into Home Assist <![CDATA[Release notes for March 22, 2015]]> - 2015-03-22T01:21:00-07:00 + 2015-03-22T00:21:00-08:00 https://home-assistant.io/blog/2015/03/22/release-notes 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:

@@ -294,7 +335,7 @@ James Cole has also contributed support for the <![CDATA[Release notes for March 11, 2015]]> - 2015-03-11T19:36:00-07:00 + 2015-03-11T18:36:00-08:00 https://home-assistant.io/blog/2015/03/11/release-notes 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!

diff --git a/blog/2014/12/18/website-launched/index.html b/blog/2014/12/18/website-launched/index.html index c6eeb0eb38..5ccd3e5e3f 100644 --- a/blog/2014/12/18/website-launched/index.html +++ b/blog/2014/12/18/website-launched/index.html @@ -211,6 +211,12 @@ 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 96abf63789..7e1c4d57c0 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 @@ -273,6 +273,12 @@ This article will try to explain how they all relate.

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 94b0272dd7..1a4dd8b46c 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 @@ -255,6 +255,12 @@ 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 265ce890ed..bc9d971419 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 @@ -223,6 +223,12 @@ 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 868f4bb436..a9aaa5785f 100644 --- a/blog/2015/01/13/nest-in-da-house/index.html +++ b/blog/2015/01/13/nest-in-da-house/index.html @@ -230,6 +230,12 @@ diff --git a/blog/2015/01/24/release-notes/index.html b/blog/2015/01/24/release-notes/index.html index 608f021765..f4e232da93 100644 --- a/blog/2015/01/24/release-notes/index.html +++ b/blog/2015/01/24/release-notes/index.html @@ -235,6 +235,12 @@ Home Assistant now supports --open-ui and --demo-mode 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 48550933ae..9ea75af8fc 100644 --- a/blog/2015/02/08/looking-at-the-past/index.html +++ b/blog/2015/02/08/looking-at-the-past/index.html @@ -253,6 +253,12 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D diff --git a/blog/2015/02/24/streaming-updates/index.html b/blog/2015/02/24/streaming-updates/index.html index dcf351d143..2e1452c0db 100644 --- a/blog/2015/02/24/streaming-updates/index.html +++ b/blog/2015/02/24/streaming-updates/index.html @@ -231,6 +231,12 @@ 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 e3a2cd231c..08006594e0 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 @@ -218,6 +218,12 @@ YAML allows the use of lists, which should make the configuration file a bit mor diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html index 8b8d6bdf4a..de66e7a685 100644 --- a/blog/2015/03/08/new-logo/index.html +++ b/blog/2015/03/08/new-logo/index.html @@ -219,6 +219,12 @@ The old logo, the new detailed logo and the new simple logo. diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html index b2b5ea5f7c..52f938b1f5 100644 --- a/blog/2015/03/11/release-notes/index.html +++ b/blog/2015/03/11/release-notes/index.html @@ -112,7 +112,7 @@ - + @@ -265,6 +265,12 @@ An initial version of voice control for Home Assistant has landed. The current i diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html index 9593ab7cef..301c0e0c27 100644 --- a/blog/2015/03/22/release-notes/index.html +++ b/blog/2015/03/22/release-notes/index.html @@ -112,7 +112,7 @@ - + @@ -333,6 +333,12 @@ James Cole has also contributed support for the diff --git a/blog/2015/04/25/release-notes/index.html b/blog/2015/04/25/release-notes/index.html index 03f220a2a4..8bfe916c9b 100644 --- a/blog/2015/04/25/release-notes/index.html +++ b/blog/2015/04/25/release-notes/index.html @@ -349,6 +349,12 @@ James has also contributed support for integrating Transmission into Home Assist diff --git a/blog/2015/05/09/utc-time-zone-awareness/index.html b/blog/2015/05/09/utc-time-zone-awareness/index.html new file mode 100644 index 0000000000..ac860bf407 --- /dev/null +++ b/blog/2015/05/09/utc-time-zone-awareness/index.html @@ -0,0 +1,338 @@ + + + + + + + + + + + + UTC & Time zone awareness - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+ +
+ + Home Assistant + +
+ +
+ +
+ + +
+
+
+ + + +
+
+ +
+ + +
+
+ +

UTC & Time zone awareness

+ + + +
+ + + + + + + + + + + + + + + + + Paulus Schoutsen + + two minutes reading time + + + + + + + + + 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.

+ +
1
+2
+
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/archives/index.html b/blog/archives/index.html index 978acd4e7d..0786da9335 100644 --- a/blog/archives/index.html +++ b/blog/archives/index.html @@ -22,7 +22,7 @@ - + @@ -113,6 +113,43 @@ + + + +
+ +
@@ -153,7 +190,7 @@
-
@@ -190,7 +227,7 @@
-
@@ -654,6 +691,12 @@ diff --git a/blog/categories/architecture/atom.xml b/blog/categories/architecture/atom.xml index eea49667b4..caf5c9ac85 100644 --- a/blog/categories/architecture/atom.xml +++ b/blog/categories/architecture/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: architecture | Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ diff --git a/blog/categories/architecture/index.html b/blog/categories/architecture/index.html index 8bcdb9414b..c1427b0f2c 100644 --- a/blog/categories/architecture/index.html +++ b/blog/categories/architecture/index.html @@ -205,6 +205,12 @@ diff --git a/blog/categories/branding/atom.xml b/blog/categories/branding/atom.xml index 4d77db40b9..32b11e7d6d 100644 --- a/blog/categories/branding/atom.xml +++ b/blog/categories/branding/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: branding | Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ diff --git a/blog/categories/branding/index.html b/blog/categories/branding/index.html index 737987114c..58fd85005c 100644 --- a/blog/categories/branding/index.html +++ b/blog/categories/branding/index.html @@ -205,6 +205,12 @@ diff --git a/blog/categories/component/atom.xml b/blog/categories/component/atom.xml index 6db3c31c64..ecc95ecc8b 100644 --- a/blog/categories/component/atom.xml +++ b/blog/categories/component/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: component | Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ diff --git a/blog/categories/component/index.html b/blog/categories/component/index.html index 2fe7244b84..0588f13f08 100644 --- a/blog/categories/component/index.html +++ b/blog/categories/component/index.html @@ -318,6 +318,12 @@ diff --git a/blog/categories/core/atom.xml b/blog/categories/core/atom.xml index b202a289d8..27e4ec46d9 100644 --- a/blog/categories/core/atom.xml +++ b/blog/categories/core/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: core | Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ @@ -13,6 +13,44 @@ Octopress + + <![CDATA[UTC & Time zone awareness]]> + + 2015-05-09T23:08:00-07:00 + https://home-assistant.io/blog/2015/05/09/utc-time-zone-awareness + 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.
    • +
+ +]]> + + <![CDATA[Home Assistant moving to YAML]]> diff --git a/blog/categories/core/index.html b/blog/categories/core/index.html index fe7e4b8477..06d6463b1f 100644 --- a/blog/categories/core/index.html +++ b/blog/categories/core/index.html @@ -113,6 +113,43 @@ + + + +
+ +
@@ -205,6 +242,12 @@ diff --git a/blog/categories/frontend/atom.xml b/blog/categories/frontend/atom.xml index 0913495e98..ae8363b1d6 100644 --- a/blog/categories/frontend/atom.xml +++ b/blog/categories/frontend/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: frontend | Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ diff --git a/blog/categories/frontend/index.html b/blog/categories/frontend/index.html index 312effe999..9a7bb9a3e8 100644 --- a/blog/categories/frontend/index.html +++ b/blog/categories/frontend/index.html @@ -244,6 +244,12 @@ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 4c11955cd6..655c9bb8f3 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: release-notes | Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ @@ -109,7 +109,7 @@ switch: <![CDATA[Release notes for March 22, 2015]]> - 2015-03-22T01:21:00-07:00 + 2015-03-22T00:21:00-08:00 https://home-assistant.io/blog/2015/03/22/release-notes 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:

@@ -189,7 +189,7 @@ notify: <![CDATA[Release notes for March 11, 2015]]> - 2015-03-11T19:36:00-07:00 + 2015-03-11T18:36:00-08:00 https://home-assistant.io/blog/2015/03/11/release-notes 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!

diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html index 5213f70394..59414bb4e5 100644 --- a/blog/categories/release-notes/index.html +++ b/blog/categories/release-notes/index.html @@ -153,7 +153,7 @@
-
@@ -190,7 +190,7 @@
-
@@ -316,6 +316,12 @@ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 44c273a733..39dc9d5a2e 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: website | Home Assistant]]> - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 https://home-assistant.io/ diff --git a/blog/categories/website/index.html b/blog/categories/website/index.html index 48d9bad8e3..e6fb07a249 100644 --- a/blog/categories/website/index.html +++ b/blog/categories/website/index.html @@ -205,6 +205,12 @@ diff --git a/blog/index.html b/blog/index.html index adb2e11308..805604c5c6 100644 --- a/blog/index.html +++ b/blog/index.html @@ -22,7 +22,7 @@ - + @@ -95,6 +95,99 @@ +
+
+ +

+ UTC & Time zone awareness +

+ + + +
+ + + + + + + + + + + + + + + + + Paulus Schoutsen + + two minutes reading time + + + + + + + + + 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.

+ +
1
+2
+
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.
    • +
+ + + +
+
+ + -
- - -
-
- -

- Bootstrapping your setup with Discovery -

- - - -
- - - - - - - - - - - - - - - - - Paulus Schoutsen - - less than one minute reading time - - - - - - - - - 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:

- -
1
-
[discovery]
- - -

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

- -
diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html index 54ce999861..007964d335 100644 --- a/blog/posts/2/index.html +++ b/blog/posts/2/index.html @@ -22,7 +22,7 @@ - + @@ -95,6 +95,79 @@ +
+
+ +

+ Bootstrapping your setup with Discovery +

+ + + +
+ + + + + + + + + + + + + + + + + Paulus Schoutsen + + less than one minute reading time + + + + + + + + + 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:

+ +
1
+
[discovery]
+ + +

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

+ + +
+
+ +
diff --git a/components/index.html b/components/index.html index d1ed4d413e..53dd388aa4 100644 --- a/components/index.html +++ b/components/index.html @@ -323,6 +323,12 @@ the manufacturers of these devices. OpenWeatherMap Display current meteorological data from your location + + + +Time & Date +Displays the time and the date. + diff --git a/components/sensor.time_date.html b/components/sensor.time_date.html new file mode 100644 index 0000000000..87e7c73351 --- /dev/null +++ b/components/sensor.time_date.html @@ -0,0 +1,179 @@ + + + + + + + + + + + + Time & Date support - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+ +
+ + Home Assistant + +
+ +
+ +
+ + +
+
+
+ + + +
+
+ +
+ + +
+ + +
+

+ Time & Date Support +

+
+
+ + +

The time and date platform simple displays the time, the date, or both.

+ +
1
+2
+3
+4
+5
+6
+7
+8
+
# Example configuration.yaml entry
+sensor:
+  platform: time_date
+  monitored_variables:
+    - type: 'time'
+    - type: 'date'
+    - type: 'date_time'
+    - type: 'time_date'
+
+ + +

The types date_time and time_date shows the date and the time. The other two types just the time or the date.

+ +

+ +

+ + + + + +
+ + +
+ + +
+
+ + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/components/sensor.transmission.html b/components/sensor.transmission.html index f83ef4cf0d..5b0e4b57a0 100644 --- a/components/sensor.transmission.html +++ b/components/sensor.transmission.html @@ -104,7 +104,7 @@

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

+The Transmission platform allows you to monitor your downloads from within Home Assistant and setup automation based on the information.

1
 2
@@ -133,6 +133,22 @@ James Cole has contributed support to integrate Transmission. This will allow yo
+

To use the monitoring, your transmission client needs to allow remote access. If you are running the graphical transmission client (transmission-gtk) go to Edit -> Perferences and choose the tab Remote. Check Allow remote access, enter your username and your password, and uncheck the network restriction as needed.

+ +

+ +

+ + +

If everthing is setup correctly, the details will show up in the frontend.

+ +

+ +

+ + +

James Cole has contributed the transmission platform.

+
diff --git a/images/screenshots/time_date.png b/images/screenshots/time_date.png new file mode 100644 index 0000000000..15bd96773b Binary files /dev/null and b/images/screenshots/time_date.png differ diff --git a/images/screenshots/transmission-pref.png b/images/screenshots/transmission-pref.png new file mode 100644 index 0000000000..27aeeacaa5 Binary files /dev/null and b/images/screenshots/transmission-pref.png differ diff --git a/images/screenshots/transmission.png b/images/screenshots/transmission.png new file mode 100644 index 0000000000..5737d646c8 Binary files /dev/null and b/images/screenshots/transmission.png differ diff --git a/sitemap.xml b/sitemap.xml index be7e4065e6..33918dd594 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1,5 +1,10 @@ + + https://home-assistant.io/blog/2015/05/09/utc-time-zone-awareness/ + 2015-05-09T23:08:00-07:00 + 0.8 + https://home-assistant.io/blog/2015/04/25/release-notes/ 2015-04-25T06:57:00-07:00 @@ -7,12 +12,12 @@ https://home-assistant.io/blog/2015/03/22/release-notes/ - 2015-03-22T01:21:00-07:00 + 2015-03-22T00:21:00-08:00 0.8 https://home-assistant.io/blog/2015/03/11/release-notes/ - 2015-03-11T19:36:00-07:00 + 2015-03-11T18:36:00-08:00 0.8 @@ -67,355 +72,361 @@ https://home-assistant.io/developers/add_new_platform.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/getting-started/android.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/developers/api.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/developers/architecture.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/automation.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/browser.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/getting-started/configuration.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/configurator.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/conversation.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/developers/creating_components.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/device_sun_light_trigger.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/device_tracker.luci.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/device_tracker.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/device_tracker.netgear.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/device_tracker.nmap_scanner.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/device_tracker.tomato.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/discovery.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/downloader.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/developers/frontend.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/group.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/history.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/blog/archives/ - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/blog/ - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/ - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 1.0 - https://home-assistant.io/developers/ - 2015-05-01T17:00:04-07:00 + https://home-assistant.io/getting-started/ + 2015-05-09T23:58:15-07:00 weekly 0.7 - https://home-assistant.io/getting-started/ - 2015-05-01T17:00:04-07:00 + https://home-assistant.io/developers/ + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/ - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/isy994.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/keyboard.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/light.hue.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/light.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/logbook.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/media_player.cast.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/media_player.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/modbus.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/notify.instapush.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/notify.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/notify.nma.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/notify.pushbullet.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/notify.pushover.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/scene.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/scheduler.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/script.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/sensor.openweathermap.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/sensor.sabnzbd.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/sensor.systemmonitor.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 + weekly + 0.7 + + + https://home-assistant.io/components/sensor.time_date.html + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/sensor.transmission.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/simple_alarm.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/sun.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/switch.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/switch.wemo.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/tellstick.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/thermostat.heat_control.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/thermostat.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/thermostat.nest.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/getting-started/troubleshooting.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/vera.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/wink.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7 https://home-assistant.io/components/zwave.html - 2015-05-01T17:00:04-07:00 + 2015-05-09T23:58:15-07:00 weekly 0.7