diff --git a/atom.xml b/atom.xml index 2c9830a767..29fe2532a5 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ @@ -54,11 +54,23 @@

FAQ

-

Will Home Assistant and Hass.io remain open source?

+

Last updated: December 23, 2017

+ +

I thought the Home Assistant crew didn’t like the cloud?

+ +

You are right, we don’t! The Home Assistant Cloud is not an alternative to running your local Home Assistant instance. All control and automations are still running locally.

+ +

Instead, the Home Assistant Cloud is an extension of your local instance. It allows to communicate with companies that force us to communicate via a public available cloud endpoint like Amazon Alexa and Google Assistant.

+ +

Home Assistant Cloud is only used to route the messages to your Home Assistant instance. All messages are processed locally.

+ +

(Some people have suggested we rename to Home Assistant Bridge to avoid this confusion)

+ +

Will Home Assistant and Hass.io remain open source?

Yes. Yes. Yes! Home Assistant is the work of hundreds of developers all working together in creating something amazing. The only thing that will require a subscription is the optional cloud functionality.

-

What other features will come to the cloud?

+

What other features will come to the cloud?

We have a lot of ideas! We are not going to make any promises but here are some things that we’re looking into:

@@ -67,18 +79,31 @@
  • Allow easy linking of other cloud services to Home Assistant. No more local juggling with OAuth flows. For example, link your Fitbit account and the Fitbit component will show up in Home Assistant.
  • Encrypted backups of your Hass.io data
  • Text to speech powered by AWS Polly
    • -
  • Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on - top of the Home Assistant cloud.
    • +
  • Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on top of the Home Assistant cloud.
  • IFTTT integration
  • Alexa shopping list integration
    • -

    What countries are supported?

    +

    What countries are supported at launch?

    -

    Only US is currently supported. Expect more countries to be supported soon. The reason there is a country limitation is that we need to do extra steps and certifications for each country’s Alexa skill.

    +

    Only US is currently supported. The reason for this limitation is that we need to do extra steps and certifications for each country’s Alexa skill. This is in progress but the timeline depends on Amazon.

    -

    How is the connection made to the cloud?

    +

    How is the connection made to the cloud?

    The connection is made using a WebSocket connection over HTTPS. See the source here.

    + +

    I think that the price is too high for what I get.

    + +

    The Home Assistant Cloud functionality is a perk for becoming a supporter of the Home Assistant project. As a supporter you will help fund development, cover our operating costs and gives you access to use Home Assistant Cloud. You are not paying to just maintain the cloud servers.

    + +

    The perks offered for being a supporter will also extend over time, as noted in this answer.

    + +

    What will the Home Assistant organization do with the funds ?

    + +

    The plan is to hire developers to work fulltime on Home Assistant. We have grown a lot in the last 4 years and the work load is pushing the limits of what our core developers can do. Open source burn out is very common (1, 2) and we want to avoid this by moving most organization and release chores to a paid position.

    + +

    For more background on these topics, check out HASS Podcast 15.

    + ]]> diff --git a/blog/2017/12/17/introducing-home-assistant-cloud/index.html b/blog/2017/12/17/introducing-home-assistant-cloud/index.html index f491455a32..e32a960988 100644 --- a/blog/2017/12/17/introducing-home-assistant-cloud/index.html +++ b/blog/2017/12/17/introducing-home-assistant-cloud/index.html @@ -74,7 +74,7 @@
    Paulus Schoutsen - four minutes reading time + six minutes reading time
      @@ -106,23 +106,35 @@

      Once you’re done, ask Alexa to discover devices (“Alexa, discover devices”) and you are all set to control them: “Alexa, turn on <device name>”.

      See the Cloud component configuration to learn how to filter which devices get exposed to Alexa.

      FAQ

      -

      Will Home Assistant and Hass.io remain open source?

      +

      Last updated: December 23, 2017

      +

      I thought the Home Assistant crew didn’t like the cloud?

      +

      You are right, we don’t! The Home Assistant Cloud is not an alternative to running your local Home Assistant instance. All control and automations are still running locally.

      +

      Instead, the Home Assistant Cloud is an extension of your local instance. It allows to communicate with companies that force us to communicate via a public available cloud endpoint like Amazon Alexa and Google Assistant.

      +

      Home Assistant Cloud is only used to route the messages to your Home Assistant instance. All messages are processed locally.

      +

      (Some people have suggested we rename to Home Assistant Bridge to avoid this confusion)

      +

      Will Home Assistant and Hass.io remain open source?

      Yes. Yes. Yes! Home Assistant is the work of hundreds of developers all working together in creating something amazing. The only thing that will require a subscription is the optional cloud functionality.

      -

      What other features will come to the cloud?

      +

      What other features will come to the cloud?

      We have a lot of ideas! We are not going to make any promises but here are some things that we’re looking into:

      • Google Home / Google Assistant Smart Home skill
      • Allow easy linking of other cloud services to Home Assistant. No more local juggling with OAuth flows. For example, link your Fitbit account and the Fitbit component will show up in Home Assistant.
      • Encrypted backups of your Hass.io data
      • Text to speech powered by AWS Polly
        • -
      • Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on - top of the Home Assistant cloud.
        • +
      • Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on top of the Home Assistant cloud.
      • IFTTT integration
      • Alexa shopping list integration
      -

      What countries are supported?

      -

      Only US is currently supported. Expect more countries to be supported soon. The reason there is a country limitation is that we need to do extra steps and certifications for each country’s Alexa skill.

      -

      How is the connection made to the cloud?

      +

      What countries are supported at launch?

      +

      Only US is currently supported. The reason for this limitation is that we need to do extra steps and certifications for each country’s Alexa skill. This is in progress but the timeline depends on Amazon.

      +

      How is the connection made to the cloud?

      The connection is made using a WebSocket connection over HTTPS. See the source here.

      +

      I think that the price is too high for what I get.

      +

      The Home Assistant Cloud functionality is a perk for becoming a supporter of the Home Assistant project. As a supporter you will help fund development, cover our operating costs and gives you access to use Home Assistant Cloud. You are not paying to just maintain the cloud servers.

      +

      The perks offered for being a supporter will also extend over time, as noted in this answer.

      +

      What will the Home Assistant organization do with the funds ?

      +

      The plan is to hire developers to work fulltime on Home Assistant. We have grown a lot in the last 4 years and the work load is pushing the limits of what our core developers can do. Open source burn out is very common (1, 2) and we want to avoid this by moving most organization and release chores to a paid position.

      +

      For more background on these topics, check out HASS Podcast 15.

      Comments

      diff --git a/blog/categories/announcements/atom.xml b/blog/categories/announcements/atom.xml index 8504314579..19159b7c93 100644 --- a/blog/categories/announcements/atom.xml +++ b/blog/categories/announcements/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Announcements | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ @@ -54,11 +54,23 @@ See the [Cloud component configuration](/components/cloud/) to learn how to filt ## FAQ -**Will Home Assistant and Hass.io remain open source?** +_Last updated: December 23, 2017_ + +#### I thought the Home Assistant crew didn't like the cloud? + +You are right, [we don't](https://home-assistant.io/blog/2016/01/19/perfect-home-automation/#your-system-should-run-at-home-not-in-the-cloud)! The Home Assistant Cloud is not an alternative to running your local Home Assistant instance. All control and automations are still running locally. + +Instead, the Home Assistant Cloud is an extension of your local instance. It allows to communicate with companies that force us to communicate via a public available cloud endpoint like Amazon Alexa and Google Assistant. + +Home Assistant Cloud is only used to route the messages to your Home Assistant instance. All messages are processed locally. + +_(Some people have suggested we rename to Home Assistant Bridge to avoid this confusion)_ + +#### Will Home Assistant and Hass.io remain open source? Yes. Yes. Yes! Home Assistant is the work of hundreds of developers all working together in creating something amazing. The only thing that will require a subscription is the optional cloud functionality. -**What other features will come to the cloud?** +#### What other features will come to the cloud? We have a lot of ideas! We are not going to make any promises but here are some things that we’re looking into: @@ -66,17 +78,32 @@ We have a lot of ideas! We are not going to make any promises but here are some - Allow easy linking of other cloud services to Home Assistant. No more local juggling with OAuth flows. For example, link your Fitbit account and the Fitbit component will show up in Home Assistant. - Encrypted backups of your Hass.io data - Text to speech powered by AWS Polly -- Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on - top of the Home Assistant cloud. +- Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on top of the Home Assistant cloud. - IFTTT integration - Alexa shopping list integration -**What countries are supported?** +#### What countries are supported at launch? -Only US is currently supported. Expect more countries to be supported soon. The reason there is a country limitation is that we need to do extra steps and certifications for each country's Alexa skill. +Only US is currently supported. The reason for this limitation is that we need to do extra steps and certifications for each country's Alexa skill. This is in progress but the timeline depends on Amazon. -**How is the connection made to the cloud?** +#### How is the connection made to the cloud? The connection is made using a WebSocket connection over HTTPS. [See the source here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/cloud/iot.py). + +#### I think that the price is too high for what I get. + +The Home Assistant Cloud functionality is a perk for becoming a supporter of the Home Assistant project. As a supporter you will help fund development, cover our operating costs and gives you access to use Home Assistant Cloud. You are not paying to just maintain the cloud servers. + +The perks offered for being a supporter will also extend over time, as noted in [this answer](#what-other-features-will-come-to-the-cloud). + +#### What will the Home Assistant organization do with the funds ? + +The plan is to hire developers to work fulltime on Home Assistant. We have grown a lot in the last 4 years and the work load is pushing the limits of what our core developers can do. Open source burn out is very common ([1], [2]) and we want to avoid this by moving most organization and release chores to a paid position. + +_For more background on these topics, check out [HASS Podcast 15](https://hasspodcast.io/ha015/)._ + +[1]: https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-an-open-source-maintainer/ +[2]: https://www.kennethreitz.org/essays/the-reality-of-developer-burnout ]]> diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 043caeb3b2..68a7331024 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 2573db350b..c43e014a90 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 060c043021..7c24fb0699 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 4c0da73849..d701c91f09 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index c814cc84cb..eba335eebb 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+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 c2f5afe1ab..f9bdccd7b5 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index 70ac9d473c..3e4144a1cf 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/media/atom.xml b/blog/categories/media/atom.xml index d77f003d86..fa012680f7 100644 --- a/blog/categories/media/atom.xml +++ b/blog/categories/media/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Media | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/merchandise/atom.xml b/blog/categories/merchandise/atom.xml index 79a28bc218..2e14b97992 100644 --- a/blog/categories/merchandise/atom.xml +++ b/blog/categories/merchandise/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Merchandise | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 7ec1982763..3bdd020a36 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 109d64fba5..423d62ebfe 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 8ff0f99086..fc7eae0607 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index d35752d7f2..2fc30449d0 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index 5343b9274d..ac2a92c5b4 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+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 7e175a1815..181bfd382d 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index aea0a3ebf4..7c613b3c2e 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 52184afd7c..2635b4b281 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index bca51cc26d..2b10a079ab 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index e873298b51..88b0be44bc 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 2dd3529925..f17f3bcf13 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-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index ccf9fd84f7..37423af75f 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 95abc2ce93..2ea7bb3b1c 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2017-12-22T20:48:42+00:00 + 2017-12-23T22:25:21+00:00 https://home-assistant.io/ diff --git a/blog/index.html b/blog/index.html index c225f35790..27c57d7c1a 100644 --- a/blog/index.html +++ b/blog/index.html @@ -75,7 +75,7 @@
      Paulus Schoutsen - four minutes reading time + six minutes reading time
        @@ -108,23 +108,35 @@

        Once you’re done, ask Alexa to discover devices (“Alexa, discover devices”) and you are all set to control them: “Alexa, turn on <device name>”.

        See the Cloud component configuration to learn how to filter which devices get exposed to Alexa.

        FAQ

        -

        Will Home Assistant and Hass.io remain open source?

        +

        Last updated: December 23, 2017

        +

        I thought the Home Assistant crew didn’t like the cloud?

        +

        You are right, we don’t! The Home Assistant Cloud is not an alternative to running your local Home Assistant instance. All control and automations are still running locally.

        +

        Instead, the Home Assistant Cloud is an extension of your local instance. It allows to communicate with companies that force us to communicate via a public available cloud endpoint like Amazon Alexa and Google Assistant.

        +

        Home Assistant Cloud is only used to route the messages to your Home Assistant instance. All messages are processed locally.

        +

        (Some people have suggested we rename to Home Assistant Bridge to avoid this confusion)

        +

        Will Home Assistant and Hass.io remain open source?

        Yes. Yes. Yes! Home Assistant is the work of hundreds of developers all working together in creating something amazing. The only thing that will require a subscription is the optional cloud functionality.

        -

        What other features will come to the cloud?

        +

        What other features will come to the cloud?

        We have a lot of ideas! We are not going to make any promises but here are some things that we’re looking into:

        • Google Home / Google Assistant Smart Home skill
        • Allow easy linking of other cloud services to Home Assistant. No more local juggling with OAuth flows. For example, link your Fitbit account and the Fitbit component will show up in Home Assistant.
        • Encrypted backups of your Hass.io data
        • Text to speech powered by AWS Polly
          • -
        • Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on - top of the Home Assistant cloud.
          • +
        • Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on top of the Home Assistant cloud.
        • IFTTT integration
        • Alexa shopping list integration
        -

        What countries are supported?

        -

        Only US is currently supported. Expect more countries to be supported soon. The reason there is a country limitation is that we need to do extra steps and certifications for each country’s Alexa skill.

        -

        How is the connection made to the cloud?

        +

        What countries are supported at launch?

        +

        Only US is currently supported. The reason for this limitation is that we need to do extra steps and certifications for each country’s Alexa skill. This is in progress but the timeline depends on Amazon.

        +

        How is the connection made to the cloud?

        The connection is made using a WebSocket connection over HTTPS. See the source here.

        +

        I think that the price is too high for what I get.

        +

        The Home Assistant Cloud functionality is a perk for becoming a supporter of the Home Assistant project. As a supporter you will help fund development, cover our operating costs and gives you access to use Home Assistant Cloud. You are not paying to just maintain the cloud servers.

        +

        The perks offered for being a supporter will also extend over time, as noted in this answer.

        +

        What will the Home Assistant organization do with the funds ?

        +

        The plan is to hire developers to work fulltime on Home Assistant. We have grown a lot in the last 4 years and the work load is pushing the limits of what our core developers can do. Open source burn out is very common (1, 2) and we want to avoid this by moving most organization and release chores to a paid position.

        +

        For more background on these topics, check out HASS Podcast 15.

      diff --git a/sitemap.xml b/sitemap.xml index ae0152a1c8..38e98a9c90 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -3826,7 +3826,7 @@ https://home-assistant.io/components/switch.hook/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/cookbook/automation_for_rainy_days/ @@ -4502,99 +4502,99 @@ https://home-assistant.io/docs/autostart/init.d/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/api/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/configuration/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/example_apps/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/installation/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/operation/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/reboot/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/running/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/tutorial/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/updating/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/windows/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/certificates/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/hadashboard/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/hass-configurator/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/ios/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/nginx/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/notebooks/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/scenegen/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/ecosystem/synology/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/tools/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/tools/dev-tools/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/tools/hass/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/docs/tools/scripts/ -2017-12-22T20:48:42+00:00 +2017-12-23T22:25:21+00:00 https://home-assistant.io/faq/after-upgrading/ @@ -5726,62 +5726,62 @@ https://home-assistant.io/demo/frontend.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/index.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00 https://home-assistant.io/static/mdi-demo.html -2017-12-22T20:47:59+00:00 +2017-12-23T22:24:37+00:00