diff --git a/atom.xml b/atom.xml index 246cbcdb95..844eb4ae94 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ @@ -34,6 +34,9 @@

Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.

+

New customization options

+

@Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.

+

Major Wink and HDMI CEC improvements

@w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.

@@ -170,6 +173,7 @@ Climate - EQ3 BT smart: Add reporting for availability ( Code of Conduct

More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we’re introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.

@@ -401,6 +405,7 @@ You have to note: The Christmas tree in action.

+

During the time by tree was set up, I had 7,366 visitors from 88 countries connect to my Home Assistant instance. This generated an estimated 100,000 clicks on the switches in my Home Assistant instance - thanks in part to some folks who posted up with macros for 6-8 hour stretches.

@@ -924,6 +929,7 @@ You have to note: https://home-assistant.io/blog/2016/10/25/explaining-the-updater On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.

+

Why we changed the updater

This change was driven by two important factors.

diff --git a/blog/2016/10/25/explaining-the-updater/index.html b/blog/2016/10/25/explaining-the-updater/index.html index 32ee978041..22d84890fd 100644 --- a/blog/2016/10/25/explaining-the-updater/index.html +++ b/blog/2016/10/25/explaining-the-updater/index.html @@ -111,6 +111,7 @@

On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.

+

Why we changed the updater

This change was driven by two important factors.

diff --git a/blog/2017/01/03/control-my-christmas-tree-stats/index.html b/blog/2017/01/03/control-my-christmas-tree-stats/index.html index e23d844b87..b68c7c5bff 100644 --- a/blog/2017/01/03/control-my-christmas-tree-stats/index.html +++ b/blog/2017/01/03/control-my-christmas-tree-stats/index.html @@ -122,6 +122,7 @@ The Christmas tree in action.

+

During the time by tree was set up, I had 7,366 visitors from 88 countries connect to my Home Assistant instance. This generated an estimated 100,000 clicks on the switches in my Home Assistant instance - thanks in part to some folks who posted up with macros for 6-8 hour stretches.

diff --git a/blog/2017/01/21/home-assistant-governance/index.html b/blog/2017/01/21/home-assistant-governance/index.html index a67c2be3c3..3d0e8f65f0 100644 --- a/blog/2017/01/21/home-assistant-governance/index.html +++ b/blog/2017/01/21/home-assistant-governance/index.html @@ -121,6 +121,7 @@

Starting today we are announcing a few initiatives to help protect our users, contributors and community members.

+

Code of Conduct

More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we’re introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.

diff --git a/blog/2017/01/28/face-coffee-wink/index.html b/blog/2017/01/28/face-coffee-wink/index.html index 6f1a2a5790..50ce0be410 100644 --- a/blog/2017/01/28/face-coffee-wink/index.html +++ b/blog/2017/01/28/face-coffee-wink/index.html @@ -88,7 +88,7 @@
Fabian Affolter et al. - eight minutes reading time + nine minutes reading time
    @@ -125,6 +125,9 @@

    Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.

    +

    New customization options

    +

    @Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.

    +

    Major Wink and HDMI CEC improvements

    @w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.

    diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 5e76a5b012..834a51b7ed 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: community | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ @@ -31,6 +31,7 @@ I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Sw The Christmas tree in action.

    + During the time by tree was set up, I had 7,366 visitors from 88 countries connect to my Home Assistant instance. This generated an estimated 100,000 clicks on the switches in my Home Assistant instance - thanks in part to some folks who posted up with macros for 6-8 hour stretches.

    diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index dd82efc21b..5d8f081b7f 100644 --- a/blog/categories/device-tracking/atom.xml +++ b/blog/categories/device-tracking/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Device-Tracking | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 14fad69276..5dc7d6ea30 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 4232e8e13b..1960093f88 100644 --- a/blog/categories/how-to/atom.xml +++ b/blog/categories/how-to/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: How-To | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 67c7dd478f..c23b492467 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index bb92d63a5a..cd26844dab 100644 --- a/blog/categories/internet-of-things/atom.xml +++ b/blog/categories/internet-of-things/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Internet-of-Things | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index b552d3f832..1bbc663c96 100644 --- a/blog/categories/iot-data/atom.xml +++ b/blog/categories/iot-data/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: IoT-Data | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 0b77709a1d..12ae44606c 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index ec87bca558..3442c6c01a 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index bdbe04bff3..40fe0bc96c 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ @@ -30,6 +30,7 @@ The Home Assistant project and community has seen enormous growth in the last th Starting today we are announcing a few initiatives to help protect our users, contributors and community members. + ## Code of Conduct More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we're introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents. @@ -118,6 +119,7 @@ We hope you understand that our desire with these changes is only to help protec https://home-assistant.io/blog/2016/10/25/explaining-the-updater ## Why we changed the updater This change was driven by two important factors. diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 1ba3d72238..970c81ddcc 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index a3bcdbd1a9..c9899defc3 100644 --- a/blog/categories/presence-detection/atom.xml +++ b/blog/categories/presence-detection/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Presence-Detection | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index bdd713d840..419984c3a5 100644 --- a/blog/categories/public-service-announcement/atom.xml +++ b/blog/categories/public-service-announcement/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Public-Service-Announcement | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 540cda50fd..eea7237d22 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]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ @@ -34,6 +34,9 @@ After a security audit by Stephen O'Conner, he found that our source for randoml Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged. +### New customization options +[@Andrey-git] has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain. + ### Major Wink and HDMI CEC improvements [@w1ll1am23] did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your `configuration.yaml` file, no `client_id` and `client_secret` are needed, and token which was generated with the generator located in the [Wink][wink] documentation. diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 86ed78e2b5..ef5ae0d754 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index ce156b8813..b956099070 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 73cdcda4ca..d71f1e7efc 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 3fc1e49e4e..4bdd3a3e91 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: User-Stories | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index 5c29909345..87407b7d93 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 06162d0b5b..74a88309a3 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2017-01-28T23:48:44+00:00 + 2017-01-28T23:52:58+00:00 https://home-assistant.io/ diff --git a/blog/index.html b/blog/index.html index 915340a8f8..fa3d96f2f6 100644 --- a/blog/index.html +++ b/blog/index.html @@ -91,7 +91,7 @@

    Fabian Affolter et al. - eight minutes reading time + nine minutes reading time
      @@ -129,6 +129,9 @@

      Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.

      +

      New customization options

      +

      @Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.

      +

      Major Wink and HDMI CEC improvements

      @w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.

      @@ -297,84 +300,10 @@ Climate - EQ3 BT smart: Add reporting for availability ( Code of Conduct - -

      More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we’re introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.

      - -

      Moving forward this Code of Conduct will be active for all projects within the Home Assistant organisation.

      - -

      Read the Code of Conduct

      - -

      Contributor License Agreement

      - -

      Moving forward we will also require that all contributors to any project have electronically signed our contributor license agreement (CLA). We have adopted the CLA that GitHub uses for their projects (see update at the top). Currently we have no plans to retroactively require a CLA for previous contributions, only those going forward.

      - -

      Until a signed CLA is on file your pull request will not be reviewed or accepted. When you open a new pull request, if you do not have a CLA on file, our helpful bot will walk you through the steps to complete the process.

      - -

      We intend to require an electronically signed contributor licensing agreement for all contributors beginning with our next release (0.37), currently scheduled for release on Saturday, January 28th, 2017 (one week from today). The CLA is being added to all repositories today.

      - -

      A CLA is difficult to describe but GitHub did an excellent job so this next section is taken from https://cla.github.com:

      - -

      What is a Contributor License Agreement?

      - -

      A Contributor License Agreement, known as a CLA, asks contributors to confirm that:

      - -
        -
      1. Anyone can use your contributions anywhere, for free, forever.
        2. -
      2. Your contributions do not infringe on anyone else’s rights.
        3. -
      - -

      The GitHub CLA helps ensure the smooth operation and usability of the open source projects that we maintain.

      - -

      Why is a CLA necessary?

      - -

      It depends on the jurisdiction, but in the United States, contributions are owned by the author or their employer. When the contribution is accepted, the project becomes a bundle of derivative works. The agreement of all contributors are necessary to maintain distribution of the complete project and to any licensing agreement.

      - -

      Isn’t that the purpose of an open source license?

      - -

      Most open source licenses deal with use of the original code, and don’t refer to contributions, or derivatives of the original.

      - -

      How does a CLA protect a project?

      - -

      If the owner of a contribution decides that they don’t want the contribution to be part of the project or in any given distribution, the law is on their side. The project, contributors, and users may be subject to legal action. This may require payment of damages and could prevent further usage or contributions until the matter is resolved.

      - -

      Even when there is no legal pursuit, too much ambiguity can jeopardize or doom a project by preventing those that can’t risk legal action from getting involved.

      - -

      Why does it seem like only “corporate” projects have a CLA?

      - -

      There are many projects without corporate ownership that use a CLA or even a copyright assignment: jQuery and Eclipse, for example. However, it is true that projects with financial backing tend to be at a higher risk of becoming a target, so they may have a lower tolerance for legal ambiguity.

      - -

      Security requirements

      - -

      With more collaborators involved with Home Assistant we are also exposing ourselves to more risk as more people have write access. As such we taking the following steps.

      - -
        -
      1. As of November 3rd, 2016, all collaborators have been required to have 2 factor authentication (2FA) enabled on their GitHub account.
        2. -
      2. Going forward, we will do an audit from time to time and strip collaborators from write access if they haven’t contributed for a while. This is in no sense meant to boot people, and you are absolutely eligible to get it back in the future when you wish start contributing again.
        3. -
      - -

      Licensing

      - -

      We will now ensure that a LICENSE.md file exists in all projects under the Home Assistant organization and is an OSI approved open source license or a Creative Commons license.

      - -

      Code License

      - -

      The chosen license for all code projects under the Home Assistant organization is the Apache 2.0 license.

      - -

      Documentation License

      - -

      All content on home-assistant.io and all other documentation/asset projects under the Home Assistant organization will be licensed under the Creative Commons License, specifically the Attribution-NonCommercial-ShareAlike 4.0 International license.

      - -

      Crediting contributors

      - -

      We have now mostly automated updating the Credits page so that contributors get their attribution more quickly.

      - -

      In closing

      - -

      We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, Twitter or Gitter.

      - + Read on → +
    @@ -624,25 +553,10 @@ You have to note: The Christmas tree in action.

    -

    During the time by tree was set up, I had 7,366 visitors from 88 countries connect to my Home Assistant instance. This generated an estimated 100,000 clicks on the switches in my Home Assistant instance - thanks in part to some folks who posted up with macros for 6-8 hour stretches.

    - -

    - - View counts of the video. -

    - -

    I’m very excited to report that Home Assistant didn’t crash a single time. In fact, it didn’t even bog down or need to be restarted. The Wemo Insight and Sonoff relays were incredibly resilient, as well. I only had one Sonoff failure and two Wemo Insight failures both of which were resolved by power cycling them. The digital LED strips also fared pretty well, hanging up only twice, aside from a loose connector.

    - -

    I would like to send a big thank you to the Home Assistant developers who have worked so hard on making Home Assistant run so well. This project is a testament to your hard work on making Home Assistant one of the best home automation platforms out there. Thank you!

    - -

    I’m looking forward to continuing my home automation adventures with Home Assistant and I can’t wait for next Christmas with an even bigger and badder tree. :)

    - -

    Wishing everyone the best in 2017!

    - -

    Cheers! -Ben

    - + Read on → +
diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html index 6e6c196f5e..436e8b42ef 100644 --- a/blog/posts/2/index.html +++ b/blog/posts/2/index.html @@ -115,48 +115,10 @@

On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.

-

Why we changed the updater

-

This change was driven by two important factors.

- -

Improving the security of the users.

- -

As a user, you will be able to be notified if you are running a Home Assistant version that includes components that have known security flaws.

- -

Although we hope to not have to use this feature often, it is important for us to be able to reach out to impacted users. We had the need for such a feature once in the past. Due to a bug the forecast.io sensor was making a huge amount of API requests causing some of our users to get charged because they went over the free quota.

- -

Please note that this functionality is not done yet but will be available in a future release.

- -

Focusing our resources where it matters

- -

As developers of Home Assistant, we will be able to see in what kind of environments Home Assistant is running. Here’s a few data points we didn’t have until now:

- - - -

Why we look up your IP address with GeoIP

-

We store the city so that we can see where our users are from. This information will be used to give us a better insight in where our users are from. This will help us gather data to see if we should for example prioritize internationalization. In addition, we previously had a nasty bug with the sun component in which users above a certain latitude were having crashes multiple times a day. Had the updater component been in place we could have targeted a special priority update notification only to them.

- -

As stated in the release blog post, the location information is not provided by your local Home Assistant installation but is instead gathered by comparing your IP address against the GeoLite2 data created by MaxMind. From their documentation:

- -
-

IP geolocation is inherently imprecise. Locations are often near the center of the population. Any location provided by a GeoIP database should not be used to identify a particular address or household.

-
- -

Why is it enabled by default

-

We decided to have it enabled by default because we consider the information that is gathered not harmful. We understand that not everyone will agree with us and so we have provided multiple ways to opt out.

- -

It is in our short-term planning to add an option to control this to our frontend.

- -

Source Code

-

The source code of our updater AWS Lambda function is now available here.

- + Read on → +
diff --git a/sitemap.xml b/sitemap.xml index 685b9aa88e..8023c158ae 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2699,62 +2699,62 @@ https://home-assistant.io/demo/frontend.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/index.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00 https://home-assistant.io/static/mdi-demo.html -2017-01-28T23:47:59+00:00 +2017-01-28T23:52:12+00:00