The notify component makes it possible to send notifications to a wide variety of platforms. Please check the sidebar for a full list of platforms that are supported.
-
Configuration
+
Configuration
# Example configuration.yaml entry
@@ -118,7 +118,7 @@
The name parameter is optional but needed if you want to use multiple platforms. The platform will be exposed as service notify/<name>. The name will default to notify if not supplied.
-
Service
+
Service
Once loaded, the notify platform will expose a service that can be called to send notifications.
@@ -149,7 +149,7 @@
-
Test if it works
+
Test if it works
A simple way to test if you have set up your notify platform correctly is to use Call Service from the Developer Tools to call your notify service. Choose your service (notify/xyz) from the list of Available services: and enter something like the sample below into the Service Data field and hit CALL SERVICE.
The arest switch platform allows you to toggle pins of your devices (like Arduino boards with a ethernet/wifi connection, ESP8266 based devices, and the Raspberry Pi) running the aREST RESTful framework.
-
To use your aREST enabled device in your installation, add the following to your configuration.yaml file:
+
To use your aREST enabled device with pins in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
@@ -119,19 +119,46 @@
+
If you want to use custom functions, then add the following to your configuration.yaml file:
resource (Required): IP address and schema of the device that is exposing an aREST API, eg. http://192.168.1.10.
+
resource (Required): IP address and schema of the device that is exposing an aREST API, eg. http://192.168.1.10 (no-trailing slash)
name (Optional): Let you overwrite the the name of the device. By default name from the device is used.
-
pins array (Required): An array with all used pins of your board.
+
pins array (Required): An array with all used pins.
-
name (Required): The name of the pin you wish to toggle.
+
name (Required): The name of the pin to use in the frontend.
-
You can still switch your pins with a web browser or a command line tool. Use the http://192.168.1.10/digital/8/1 to set pin 8 to high/on, the JSON response will give you some feedback.
+
or
+
+
+
functions array (Required): An array with all used functions.
+
+
name (Required): The name to use in the frontend.
+
+
+
+
+
You can still switch your pins with a web browser or a command line tool. Use the URL http://192.168.1.10/digital/8/1 to set pin 8 to high/on, the JSON response will give you the feedback.
{"message": "Pin D8 set to 1", "id": "sensor02", "name": "livingroom", "connected": true}
@@ -214,6 +241,9 @@
diff --git a/components/switch.command_switch/index.html b/components/switch.command_switch/index.html
index 246fc8b8b3..7f5949f263 100644
--- a/components/switch.command_switch/index.html
+++ b/components/switch.command_switch/index.html
@@ -233,6 +233,9 @@ This switch will shudown your host immediately, there will be no confirmation.
diff --git a/components/switch.modbus/index.html b/components/switch.modbus/index.html
index dc7c3e31f0..ad0b2c09d9 100644
--- a/components/switch.modbus/index.html
+++ b/components/switch.modbus/index.html
@@ -230,6 +230,9 @@ Each named bit will create a switch.
The mystrom switch platform allows you to control the state of your myStrom switches. The built-in sensor is measuring the power consumption while the switch is on.
+
+
To use your myStrom switch in your installation, add the following to your configuration.yaml file:
diff --git a/components/switch.rest/index.html b/components/switch.rest/index.html
index 0b0a2867de..101bf836a4 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -200,6 +200,9 @@ Make sure that the URL matches exactly your endpoint or resource.
The homematic thermostat platform let you control Homematic thermostat from Home Assistant. Currently there is support for Homematic (HM-TC-IT-WM-W-EU, HM-CC-RT-DN) thermostats using Homegear or Homematic central (CCU1/CCU2).
+
+
To set it up, add the following information to your configuration.yaml file:
To get started with the Wink API, you will first need to get yourself an API access token. Because it is very difficult right now to get access to their API, John McLaughlin has created the form below to get you one.
-
- We’re having some issues handing out API access tokens to new users.
-
-
After you have gotten your access token, add the following to your configuration.yaml:
Home Assistant will be able to automatically discover and configure any Google Chromecasts, Netgear routers, Belkin WeMo switches, Philips Hue bridges and Sonos speakers in your network if you have the discovery component enabled (which is by default).
-
See the components overview page to find installation instructions for your devices and services. Many components use the sensor platform. Sensors need to be added into the configuration.yaml as sensor:, sensor 2:, sensor 3:, etc. There should not be gaps in the sequence or your sensors might not load correctly.
If you prefer to place your entries somewhere in the configuration.yaml file then you just choose this style. You need to append numbers (see example below) or strings (like media_player livingroom: or media_player kitchen:) to differentiate the entries. The appended number or string must be unique.
Once you get a bunch of devices set up, it is time to organize them. This can be done using groups. Each group exists of a name and a list of entity IDs. Entity IDs can be retrieved from the web interface by using the Set State page in the Developer Tools (icon in the middle).
+
+ 
+
+ 
Home Assistant
+