From c36fb04e253dbbcf07c21bbccc8c860ffcaf9feb Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 11 Jan 2015 22:44:25 -0800 Subject: [PATCH] Site updated at 2015-01-12 06:44:25 UTC --- atom.xml | 23 +- blog/2014/12/18/website-launched/index.html | 6 + .../index.html | 6 + .../index.html | 6 + .../index.html | 304 ++++++++++++++++++ blog/archives/index.html | 45 ++- blog/categories/architecture/atom.xml | 2 +- blog/categories/architecture/index.html | 6 + blog/categories/component/atom.xml | 22 +- blog/categories/component/index.html | 43 +++ blog/categories/website/atom.xml | 2 +- blog/categories/website/index.html | 6 + blog/index.html | 75 ++++- developers/add_new_platform.html | 2 + sitemap.xml | 27 +- 15 files changed, 558 insertions(+), 17 deletions(-) create mode 100644 blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html diff --git a/atom.xml b/atom.xml index 935c6d4671..0a0c38c3dc 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 https://home-assistant.io/ @@ -13,6 +13,27 @@ Octopress + + <![CDATA[Bootstrapping your setup with Discovery]]> + + 2015-01-11T21:49:08-08:00 + https://home-assistant.io/blog/2015/01/11/bootstrapping-your-setup-with-discovery + 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.

+]]> + + <![CDATA[Hello PushBullet, nice talking to you]]> diff --git a/blog/2014/12/18/website-launched/index.html b/blog/2014/12/18/website-launched/index.html index 47dac31a02..241b46a576 100644 --- a/blog/2014/12/18/website-launched/index.html +++ b/blog/2014/12/18/website-launched/index.html @@ -203,6 +203,12 @@
    +
  • + Bootstrapping your setup with Discovery +
    • + + +
  • Hello PushBullet, nice talking to you
    • 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 2885d875b0..b4427cc6bd 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 @@ -265,6 +265,12 @@ This article will try to explain how they all relate.

      +
    • + Bootstrapping your setup with Discovery +
      • + + +
    • Hello PushBullet, nice talking to you
      • 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 eb58bcfd41..9df63c59a2 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 @@ -247,6 +247,12 @@
        +
      • + Bootstrapping your setup with Discovery +
        • + + +
      • 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 new file mode 100644 index 0000000000..a00a589153 --- /dev/null +++ b/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html @@ -0,0 +1,304 @@ + + + + + + + + + + + + Bootstrapping your setup with Discovery - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + +
        +
        +
        + +
        + + Home Assistant + +
        + +
        + +
        + + +
        +
        +
        + + + +
        +
        + +
        + + +
        +
        + +

        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.

        + + +
        + + +
        +

        Comments

        +
        +
        +
        + + +
        + + + + +
        +
        + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/blog/archives/index.html b/blog/archives/index.html index 3b33bd18c8..f741ac2927 100644 --- a/blog/archives/index.html +++ b/blog/archives/index.html @@ -22,7 +22,7 @@ - + @@ -105,6 +105,43 @@ + + + +
        + +
        @@ -274,6 +311,12 @@
          +
        • + Bootstrapping your setup with Discovery +
          • + + +
        • Hello PushBullet, nice talking to you
          • diff --git a/blog/categories/architecture/atom.xml b/blog/categories/architecture/atom.xml index d06a4072b5..f57b927e11 100644 --- a/blog/categories/architecture/atom.xml +++ b/blog/categories/architecture/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: architecture | Home Assistant]]> - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 https://home-assistant.io/ diff --git a/blog/categories/architecture/index.html b/blog/categories/architecture/index.html index 7c4872e69c..ec54b5da22 100644 --- a/blog/categories/architecture/index.html +++ b/blog/categories/architecture/index.html @@ -197,6 +197,12 @@
            +
          • + Bootstrapping your setup with Discovery +
            • + + +
          • Hello PushBullet, nice talking to you
            • diff --git a/blog/categories/component/atom.xml b/blog/categories/component/atom.xml index 8b3026eea4..1e2af59d35 100644 --- a/blog/categories/component/atom.xml +++ b/blog/categories/component/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: component | Home Assistant]]> - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 https://home-assistant.io/ @@ -13,6 +13,26 @@ Octopress + + <![CDATA[Bootstrapping your setup with Discovery]]> + + 2015-01-11T21:49:08-08:00 + https://home-assistant.io/blog/2015/01/11/bootstrapping-your-setup-with-discovery + Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.

            + +

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

            + +

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

            + +

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

            + +
            [discovery]
+
            + +

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

            +]]>             +             + <![CDATA[Hello PushBullet, nice talking to you]]> diff --git a/blog/categories/component/index.html b/blog/categories/component/index.html index 3a0905fd56..1ae7c85bfa 100644 --- a/blog/categories/component/index.html +++ b/blog/categories/component/index.html @@ -105,6 +105,43 @@ + + + +
            + +
            @@ -197,6 +234,12 @@
              +
            • + Bootstrapping your setup with Discovery +
              • + + +
            • Hello PushBullet, nice talking to you
              • diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 5d69e9f2f8..974cce8e39 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: website | Home Assistant]]> - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 https://home-assistant.io/ diff --git a/blog/categories/website/index.html b/blog/categories/website/index.html index d1cf353248..be74332dbc 100644 --- a/blog/categories/website/index.html +++ b/blog/categories/website/index.html @@ -197,6 +197,12 @@
                +
              • + Bootstrapping your setup with Discovery +
                • + + +
              • Hello PushBullet, nice talking to you
                • diff --git a/blog/index.html b/blog/index.html index fdcec21786..616b2ab6b6 100644 --- a/blog/index.html +++ b/blog/index.html @@ -22,7 +22,7 @@ - + @@ -87,6 +87,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/developers/add_new_platform.html b/developers/add_new_platform.html index c5af081584..ae8942da47 100644 --- a/developers/add_new_platform.html +++ b/developers/add_new_platform.html @@ -130,6 +130,8 @@ Platform logic should not interface directly with the devices but use a third-pa

                +

                +

                Allowing your platform to be discovered

                Home Assistant has a discovery service running in the background to discover new devices. Whenever a new device is discovered, an SERVICE_DISCOVERED event will be fired with the found service and the information. The discovery component has some knowledge about which components handle which type of services and will ensure those are loaded and listening before firing the SERVICE_DISCOVERED event.

                diff --git a/sitemap.xml b/sitemap.xml index ddff8264d4..e3168f60dc 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1,5 +1,10 @@ + + https://home-assistant.io/blog/2015/01/11/bootstrapping-your-setup-with-discovery/ + 2015-01-11T21:49:08-08:00 + 0.8 + https://home-assistant.io/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/ 2015-01-04T13:29:07-08:00 @@ -17,67 +22,67 @@ https://home-assistant.io/developers/add_new_platform.html - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/developers/api.html - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/developers/architecture.html - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/developers/creating_components.html - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/developers/frontend.html - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/blog/ - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/blog/archives/ - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/ - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 1.0 https://home-assistant.io/components/ - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/getting-started/ - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7 https://home-assistant.io/developers/ - 2015-01-10T08:54:35-08:00 + 2015-01-11T22:44:18-08:00 weekly 0.7