+`interface` options are for resinos based installation. On other system you can set it to `""`, for listen on every interface. +
+ ```json { "defaults": ["8.8.8.8", "8.8.4.4"], diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown index 2b7d51b470d..022911183fa 100644 --- a/source/_addons/lets_encrypt.markdown +++ b/source/_addons/lets_encrypt.markdown @@ -17,6 +17,7 @@ This add-on need port 80/443 to verify the certificate request, please stop all ```json { + "challenge": "https", "email": "example@example.com", "domains": ["example.com", "mqtt.example.com", "hass.example.com"] } @@ -24,6 +25,7 @@ This add-on need port 80/443 to verify the certificate request, please stop all Configuration variables: +- **challenge** (*Optional*): Default it use 443 ('https') you can change it to 'http' for use port 80. - **email** (*Required*): Your email address for registration on Let's Encrypt. - **domains** (*Required*): A list of domains to create/renew the certificate. diff --git a/source/_addons/mariadb.markdown b/source/_addons/mariadb.markdown new file mode 100644 index 00000000000..548d4d0c145 --- /dev/null +++ b/source/_addons/mariadb.markdown @@ -0,0 +1,55 @@ +--- +layout: page +title: "MariaDB" +description: "MariaDB Server is one of the most popular database servers in the world." +date: 2017-04-30 13:28 +sidebar: true +comments: false +sharing: true +footer: true +--- + +Set up a [mariadb](https://mariadb.org/) SQL server. It support multible database, users and permission. If you want only connect from inside use `172.17.0.1` as host address. + +```json +{ + "databases": ["homeassistant"], + "logins": [ + { + "username": "hass", + "host": "172.17.0.1", + "password": "securePassword" + } + ], + "rights": [ + { + "username": "hass", + "host": "172.17.0.1", + "database": "homeassistant", + "grant": "ALL PRIVILEGES ON" + } + ] +} +``` + +Configuration variables: + +- **databases** (*Require*): Listen of databases. +- **logins** (*Require*): Listen of logindata they will create or update. + - **username** (*Require*): Username for login. + - **host** (*Require*): Host for login, if you need a login with multibe hosts, use '%'. + - **password** (*Require*): Password for login. +- **rights** (*Require*): Listen of rights to be handle. + - **username** (*Require*): Username for grant rights. + - **host** (*Require*): Host is a part of username like above. + - **database** (*Require*): Database name to grant this user rights to. + - **grant** (*Require*): SQL grant part for access too. + +## {% linkable_title Home Assistant configuration %} + +Use the following configuration in Home Assistant to use the database above: + +```yaml +recorder: + db_url: mysql://hass:securePassword@127.0.0.1/homeassistant +``` diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown index baba4d50372..bfca0c16c01 100644 --- a/source/_addons/samba.markdown +++ b/source/_addons/samba.markdown @@ -13,6 +13,7 @@ This allows you to set up a [Samba](https://samba.org/) server to access hass.io ```json { + "name": "hassio", "workgroup": "WORKGROUP", "guest": true, "map_config": true, @@ -25,6 +26,7 @@ This allows you to set up a [Samba](https://samba.org/) server to access hass.io Configuration variables: +- **name** (*Optional*): default `hassio`. Set netbios name of hassio device. - **workgroup** (*Optional*): default `WORKGROUP`. Set network workgroup. - **guest** (*Optional*): Allow login without a username or password. Defaults to `true`. - **map_config** (*Optional*): Expose Home Assistant configuration folder. Defaults to `true`. diff --git a/source/_addons/ssh.markdown b/source/_addons/ssh.markdown index 2361e378ab4..710521d675b 100644 --- a/source/_addons/ssh.markdown +++ b/source/_addons/ssh.markdown @@ -35,3 +35,12 @@ If you're coming from Rasbian or similar, use `root` rather than `pi` when conne Permission denied (publickey,keyboard-interactive) ``` + ++If you install this addon you can use `sshfs` as well to access files from a remote system where you have git and your favourite editing tools installed. + +```bash +$ mkdir ~/ha_config +$ sshfs -o allow_other,defer_permissions root@h[your_hassio_ip]:/config ~/ha_config +``` +
diff --git a/source/_components/axis.markdown b/source/_components/axis.markdown index bdf70c5a40c..bf4736548d3 100644 --- a/source/_components/axis.markdown +++ b/source/_components/axis.markdown @@ -23,7 +23,7 @@ Home Assistant will automatically discover their presence on your network. $ sudo apt-get install python3-gi gir1.2-gstreamer-1.0 ``` -Depending on how you run Home Assistant you might be needed to symlink the `gi` module into your environment. +Depending on how you run Home Assistant, you may need to symlink the `gi` module into your environment. Hassbian: diff --git a/source/_components/binary_sensor.command_line.markdown b/source/_components/binary_sensor.command_line.markdown index 3a612d04b3a..05a482a5fb1 100644 --- a/source/_components/binary_sensor.command_line.markdown +++ b/source/_components/binary_sensor.command_line.markdown @@ -33,6 +33,7 @@ Configuration variables: - **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON". - **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF". - **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload. +- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds). ## {% linkable_title Examples %} diff --git a/source/_components/binary_sensor.verisure.markdown b/source/_components/binary_sensor.verisure.markdown new file mode 100644 index 00000000000..f6ecb7b3c9c --- /dev/null +++ b/source/_components/binary_sensor.verisure.markdown @@ -0,0 +1,15 @@ +--- +layout: page +title: "Verisure Binary Sensor" +description: "Instructions how to integrate Verisure binary sensors into Home Assistant." +date: 2016-02-23 21:31 +0100 +sidebar: true +comments: false +sharing: true +footer: true +logo: verisure.png +ha_category: Binary Sensor +ha_iot_class: "Cloud Polling" +--- + +Integrates Verisure binary sensors into Home Assistant. See the [main component](/components/verisure/) for configuration instructions. diff --git a/source/_components/blink.markdown b/source/_components/blink.markdown index 21cd6b4447b..217dcce7438 100644 --- a/source/_components/blink.markdown +++ b/source/_components/blink.markdown @@ -36,9 +36,9 @@ Once loaded, your front end will have the following components: * A camera image for each camera in your system. * A binary_sensor per camera that indicates whether motion detection is enabled. * A binary_sensor for the system that indicates if the system is armed or disarmed. -* A sesnor per camera that reports temperature. +* A sensor per camera that reports temperature. * A sensor per camera that reports battery level. -* A sensor per camera that reports unread notification (ie. detected motion events). +* A sensor per camera that reports unread notification (i.e., detected motion events). Since the cameras are battery operated, the images are only updated in Home Assistant when the user manually forces a new photo. This image can be updated with the `snap_picture` service to force Home Assistant to request an update from Blink's servers. As a note, all of the camera-specific sensors are only polled when a new image is requested from the camera. This means that relying on any of these sensors to provide timely and accurate data is not recommended. @@ -59,7 +59,7 @@ For `arm_system`, the value sent can be either `True` or `False` and will arm an } ``` -Arm camera follows a similar structure, but each indidivual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if you have a camera named "Living Room" and you want to turn off motion detection on that camera, you would call the `arm_camera` service with the following payload: +Arm camera follows a similar structure, but each individual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if you have a camera named "Living Room" and you want to turn off motion detection on that camera, you would call the `arm_camera` service with the following payload: ```json { diff --git a/source/_components/climate.knx.markdown b/source/_components/climate.knx.markdown index 6297448c231..9f951ad4990 100644 --- a/source/_components/climate.knx.markdown +++ b/source/_components/climate.knx.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: knx.png -ha_category: DIY +ha_category: Climate ha_release: 0.25 ha_iot_class: "Local Polling" --- diff --git a/source/_components/climate.maxcube.markdown b/source/_components/climate.maxcube.markdown index ac6e5299ba9..0b918cf1033 100644 --- a/source/_components/climate.maxcube.markdown +++ b/source/_components/climate.maxcube.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "eQ-3 MAX! Cube binary sensors" +title: "eQ-3 MAX! Cube thermostat" description: "Instructions on how to integrate eQ-3 MAX! components with Home Assistant via eQ-3 MAX! Cube." date: 2017-02-04 22:00 sidebar: true diff --git a/source/_components/comfoconnect.markdown b/source/_components/comfoconnect.markdown new file mode 100644 index 00000000000..fcce2b619f0 --- /dev/null +++ b/source/_components/comfoconnect.markdown @@ -0,0 +1,55 @@ +--- +layout: page +title: "Zehnder ComfoAir Q Ventilation" +description: "Instructions how to integrate Zehnder ComfoAir Q350/450/600 ventilation systems into Home Assistant." +date: 2017-06-28 18:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: zehnder.png +ha_category: Hub +ha_release: "0.48" +--- + +The `comfoconnect` component lets you control Zehnder ComfoAir [Q350](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q350-st)/[450](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q450-st)/[600](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q600-st) +ventilation units from Home Assistant. You need a [ComfoConnect LAN C](http://www.zehnder.co.uk/products-and-systems/comfortable-indoor-ventilation/ms-comfoair-q/ideal-control#node-21233) +bridge to connect the unit to your local network. + +There is an official iPhone and Android app to configure and control your unit. This platform connects with the help of +the unofficial [pycomfoconnect](https://github.com/michaelarnauts/comfoconnect) library. + +The component has a fan platform to view and control the ventilation speed, and a sensors platform to read out the outdoor temperature and humidity, the indoor temperature and humidity, and the extract and supply air flow (in m³ per hour). + +To set it up, add the following information to your `configuration.yaml` file: + +```yaml +comfoconnect: + host: 192.168.1.213 +``` + +Configuration variables: + +- **host** (*Required*): The ip or hostname of the ComfoConnect LAN C bridge. +- **name** (*Optional*): The name of this device as you want to see it in Home Assistant. +- **token** (*Optional*): The token you want to use when registering with the device. This is a random 32 char hexadecimal string. The default value is `00000000000000000000000000000001`. +- **user_agent** (*Optional*): The name you want to supply when registering with the device. The default value is `Home Assistant`. +- **pin** (*Optional*): The pin code to use when registering. This is `0000` by default. You only need to change this if you have changed the factory default pin. + +To register the sensors, add the following to your `configuration.yaml` file: + +```yaml +sensor: + - platform: comfoconnect + resources: + - current_temperature + - current_humidity + - outside_temperature + - outside_humidity + - air_flow_supply + - air_flow_exhaust +``` + ++Note that it's not possible to have multiple connection to the bridge at the same time. This component will keep the connection open, and if you open the app, it will ask you to disconnect Home Assistant. If you close the app again, Home Assistant will reconnect automatically. +
diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown index d8559db08c0..65630b80fc0 100644 --- a/source/_components/device_tracker.snmp.markdown +++ b/source/_components/device_tracker.snmp.markdown @@ -16,20 +16,23 @@ ha_release: 0.7.5 A lot WiFi access points and WiFi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of insances and metrics, like network interfaces, disks, and wifi registrations.-This device tracker needs SNMP to be enabled on the router. +This device tracker needs SNMP to be enabled on the router. It could be that you need to install the SNMP support manually.
OID examples: -- Mikrotik: `1.3.6.1.4.1.14988.1.1.1.2.1.1` (confirmed, unknown RouterOS version/model) -- Mikrotik: `1.3.6.1.2.1.4.22.1.2` (confirmed, RouterOS 6.x on RB2011) -- Aruba: `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.2` (untested) -- BiPAC 7800DXL: `1.3.6.1.2.1.17.7.1.2.2.1.1` (confirmed on firmware 2.32e) -- OpenWrt: `1.3.6.1.2.1.4.22.1.2` (tested on Chaos Calmer 15.05 firmware, need to install snmpd package) -- pfSense: `1.3.6.1.2.1.4.22.1.2` (tested on 2.2.4-RELEASE, need to enable SNMP service) -- TPLink: `1.3.6.1.2.1.3.1.1.2.19.1` (Archer VR2600v, need to enable SNMP service) -- EdgeRouter `1.3.6.1.2.1.4.22.1.2` (EdgeRouter Lite v1.9.0, need to enable SNMP service) -- Ruckus: `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` (Ruckus ZoneDirector, tested on 9.13.3) +| Brand | Device/Firmware | OID | +|---|---|---|---| +| Mikrotik | unknown RouterOS version/model | `1.3.6.1.4.1.14988.1.1.1.2.1.1` | +| Mikrotik | RouterOS 6.x on RB2011 | `1.3.6.1.2.1.4.22.1.2` | +| Aruba | (untested) | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.2` | +| pfSense | 2.2.4 | `1.3.6.1.2.1.4.22.1.2` | +| BiPAC | 7800DXL Firmware 2.32e | `1.3.6.1.2.1.17.7.1.2.2.1.1` | +| OpenWrt | Chaos Calmer 15.05 | `1.3.6.1.2.1.4.22.1.2` | +| TP-Link | Archer VR2600v | `1.3.6.1.2.1.3.1.1.2.19.1` | +| TP-Link | Archer VR600 | `1.3.6.1.2.1.3.1.1.2` | +| EdgeRouter | Lite v1.9.0 | `1.3.6.1.2.1.4.22.1.2` | +| Ruckus | ZoneDirector 9.13.3 | `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` | To use the SNMP version 1 platform in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/fan.comfoconnect.markdown b/source/_components/fan.comfoconnect.markdown index 3e1d338e6fa..d24d4eb1845 100644 --- a/source/_components/fan.comfoconnect.markdown +++ b/source/_components/fan.comfoconnect.markdown @@ -1,7 +1,7 @@ --- layout: page -title: "Zehnder ComfoAir Q Ventilation" -description: "Instructions how to integrate Zehnder ComfoAir Q350/450/600 ventilation systems into Home Assistant." +title: "Zehnder ComfoAir Q Ventilation fans" +description: "Instructions how to integrate Zehnder ComfoAir Q350/450/600 fans into Home Assistant." date: 2017-06-28 18:00 sidebar: true comments: false @@ -12,45 +12,6 @@ ha_category: Fan ha_release: "0.48" --- -The `comfoconnect` component lets you control Zehnder ComfoAir [Q350](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q350-st)/[450](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q450-st)/[600](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q600-st) -ventilation units from Home Assistant. You need a [ComfoConnect LAN C](http://www.zehnder.co.uk/products-and-systems/comfortable-indoor-ventilation/ms-comfoair-q/ideal-control#node-21233) -bridge to connect the unit to your local network. +Please see the [main component] for information how to set it up. -There is an official iPhone and Android app to configure and control your unit. This platform connects with the help of -the unofficial [pycomfoconnect](https://github.com/michaelarnauts/comfoconnect) library. - -The component has a fan platform to view and control the ventilation speed, and a sensors platform to read out the outdoor temperature and humidity, the indoor temperature and humidity, and the extract and supply air flow (in m³ per hour). - -To set it up, add the following information to your `configuration.yaml` file: - -```yaml -climate: - - platform: comfoconnect - host: 192.168.1.213 -``` - -Configuration variables: - -- **host** (*Required*): The ip or hostname of the ComfoConnect LAN C bridge. -- **name** (*Optional*): The name of this device as you want to see it in Home Assistant. -- **token** (*Optional*): The token you want to use when registering with the device. This is a random 32 char hexadecimal string. The default value is `00000000000000000000000000000001`. -- **user_agent** (*Optional*): The name you want to supply when registering with the device. The default value is `Home Assistant`. -- **pin** (*Optional*): The pin code to use when registering. This is `0000` by default. You only need to change this if you have changed the factory default pin. - -To register the sensors, add the following to your `configuration.yaml` file: - -```yaml -sensor: - - platform: comfoconnect - resources: - - current_temperature - - current_humidity - - outside_temperature - - outside_humidity - - air_flow_supply - - air_flow_exhaust -``` - --Note that it's not possible to have multiple connection to the bridge at the same time. This component will keep the connection open, and if you open the app, it will ask you to disconnect Home Assistant. If you close the app again, Home Assistant will reconnect automatically. -
+[main component]: /components/comfoconnect/ diff --git a/source/_components/group.markdown b/source/_components/group.markdown index 78005f8fb4c..ea8d1f7c221 100644 --- a/source/_components/group.markdown +++ b/source/_components/group.markdown @@ -59,7 +59,7 @@ Configuration variables: - **view** (*Optional*): If yes then the entry will be shown as a view (tab) at the top. - **name** (*Optional*): Name of the group. - **icon** (*Optional*): If the group is a view, this icon will show at the top in the frontend instead of the name. If it's not a view, then the icon shows when this group is used in another group. -- **control** (*Optional*): If hidden then the group switch will be hidden. +- **control** (*Optional*): Set value to `hidden`. If hidden then the group switch will be hidden. - **entities** (*Required*): array or comma delimited string, list of entities to group.diff --git a/source/_components/ha.markdown b/source/_components/ha.markdown index a3ae92104a6..ba629a567f3 100644 --- a/source/_components/ha.markdown +++ b/source/_components/ha.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "Home Assistant 0.47" +title: "Home Assistant 0.48" description: "" date: 2016-12-16 17:00 sidebar: true @@ -9,7 +9,7 @@ sharing: true footer: true logo: home-assistant.png ha_category: Other -ha_release: 0.47 +ha_release: 0.48 --- Details about the latest release can always be found at: diff --git a/source/_components/input_select.markdown b/source/_components/input_select.markdown index 45dbc19c0d8..d41555c13ab 100644 --- a/source/_components/input_select.markdown +++ b/source/_components/input_select.markdown @@ -43,6 +43,10 @@ Configuration variables: Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`. +
+Because YAML defines [booleans](http://yaml.org/type/bool.html) as equivalent, any variations of 'On', 'Yes', 'Y', 'Off', 'No', or 'N' (regardless of case) used as option names will be replaced by True and False unless they are defined in quotation marks. +
+ ### {% linkable_title Services %} This components provide three services to modify the state of the `input_select`: diff --git a/source/_components/light.knx.markdown b/source/_components/light.knx.markdown index 359912a3777..5726fc8ace7 100644 --- a/source/_components/light.knx.markdown +++ b/source/_components/light.knx.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: knx.png -ha_category: DIY +ha_category: Light ha_release: 0.44 ha_iot_class: "Local Polling" --- diff --git a/source/_components/media_player.denon.markdown b/source/_components/media_player.denon.markdown index f6c4ec6ac4c..b8c0e380133 100644 --- a/source/_components/media_player.denon.markdown +++ b/source/_components/media_player.denon.markdown @@ -13,8 +13,7 @@ ha_iot_class: "Local Polling" ha_release: 0.7.2 --- - -The `denon` platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. +The `denon` platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon AVR] platform. Supported devices: @@ -22,22 +21,6 @@ Supported devices: - Denon RCD-N8 (untested) - Denon RCD-N9 (partial support) - Denon AVR receivers with integrated Network support (partial support) -- Denon AVR-X2000 (via denonavr platform) -- Denon AVR-X2100W (via denonavr platform) -- Denon AVR-X4100W (via denonavr platform) -- Denon AVR-1912 (via denonavr platform) -- Denon AVR-2312CI (via denonavr platform) -- Denon AVR-3311CI (via denonavr platform) -- Marantz M-CR603 (via denonavr platform) -- Marantz M-RC610 (via denonavr platform) -- Marantz SR5008 (via denonavr platform) -- Marantz NR1604 (via denonavr platform) -- Other Denon AVR receivers (via denonavr platform (untested)) -- Marantz receivers (experimental via denonavr platform) - --If you have something else using the IP controller for your Denon AVR 3808CI, such as your URC controller, it will not work! There is either a bug or security issue with some models where only one device could be controlling the IP functionality. -To add a Denon Network Receiver to your installation, add the following to your `configuration.yaml` file: @@ -55,36 +38,11 @@ Configuration variables: - **name** (*Optional*): Name of the device. A few notes for platform: denon + - The receiver handles only one telnet connection and refuses others. - Be careful with the volume. 100% or even 50% is very loud. - To be able to wake up the receiver, activate the "remote" setting in the receiver's settings. - Play and pause are supported, toggling is not possible. - Seeking cannot be implemented as the UI sends absolute positions. Only seeking via simulated button presses is possible. - -**denonavr platform** -```yaml -# Example configuration.yaml entry -media_player: - - platform: denonavr - host: IP_ADDRESS - name: NAME - show_all_sources: True / False - zones: - - zone: Zone2 / Zone3 - name: NAME -``` - -Configuration variables: - -- **host** (*Optional*): IP address of the device. Example: 192.168.1.32. If not set, auto discovery is used. -- **name** (*Optional*): Name of the device. If not set, friendlyName of receiver is used. -- **show_all_sources** (*Optional*): If True all sources are displayed in sources list even if they are marked as deleted in the receiver. If False deleted sources are not displayed (default). Some receivers have a bug that marks all sources as deleted in the interface. In this case this option could help. -- **zones** (*Optional*): List of additional zones to be activated. They are displayed as additional media players with the same functionality Main Zone of the device supports - - **zone**: Zone which should be activated. Valid options are Zone2 and Zone3 - - **name** (*Optional*): Name of the zone. If not set the name of the main device + zone as suffix is taken. - -A few notes for platform: denonavr -- Additional option the control Denon AVR receivers with a builtin web server is using the HTTP interface with denonavr platform. -- denonavr platform supports some additional functionalities like album covers, custom input source names and auto discovery. -- Marantz receivers seem to a have quite simliar interface. Thus if you own one, give it a try. +[Denon AVR]: /components/media_player.denonavr/ diff --git a/source/_components/media_player.denonavr.markdown b/source/_components/media_player.denonavr.markdown new file mode 100644 index 00000000000..e88156d613f --- /dev/null +++ b/source/_components/media_player.denonavr.markdown @@ -0,0 +1,67 @@ +--- +layout: page +title: "Denon AVR Network Receivers" +description: "Instructions how to integrate Denon AVR Network Receivers into Home Assistant." +date: 2015-09-08 09:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: denon.png +ha_category: Media Player +ha_iot_class: "Local Polling" +ha_release: 0.7.2 +--- + + +The `denonavr` platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon] platform. + +Supported devices: + +- Denon AVR-X2000 +- Denon AVR-X2100W +- Denon AVR-X4100W +- Denon AVR-1912 +- Denon AVR-2312CI +- Denon AVR-3311CI +- Marantz M-CR603 +- Marantz M-RC610 +- Marantz SR5008 +- Marantz NR1604 +- Other Denon AVR receivers (untested) +- Marantz receivers (experimental) + +
+If you have something else using the IP controller for your Denon AVR 3808CI, such as your URC controller, it will not work! There is either a bug or security issue with some models where only one device could be controlling the IP functionality. ++ +To add a Denon Network Receiver to your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +media_player: + - platform: denonavr + host: IP_ADDRESS + name: NAME + show_all_sources: True / False + zones: + - zone: Zone2 / Zone3 + name: NAME +``` + +Configuration variables: + +- **host** (*Optional*): IP address of the device. Example: 192.168.1.32. If not set, auto discovery is used. +- **name** (*Optional*): Name of the device. If not set, friendlyName of receiver is used. +- **show_all_sources** (*Optional*): If True all sources are displayed in sources list even if they are marked as deleted in the receiver. If False deleted sources are not displayed (default). Some receivers have a bug that marks all sources as deleted in the interface. In this case this option could help. +- **zones** (*Optional*): List of additional zones to be activated. They are displayed as additional media players with the same functionality Main Zone of the device supports + - **zone**: Zone which should be activated. Valid options are Zone2 and Zone3 + - **name** (*Optional*): Name of the zone. If not set the name of the main device + zone as suffix is taken. + +A few notes: + +- Additional option the control Denon AVR receivers with a builtin web server is using the HTTP interface with denonavr platform. +- denonavr platform supports some additional functionalities like album covers, custom input source names and auto discovery. +- Marantz receivers seem to a have quite simliar interface. Thus if you own one, give it a try. + +[Denon]: /components/media_player.denon/ diff --git a/source/_components/sensor.buienradar.markdown b/source/_components/sensor.buienradar.markdown index 351e7ce3e13..750a0ae7901 100644 --- a/source/_components/sensor.buienradar.markdown +++ b/source/_components/sensor.buienradar.markdown @@ -33,8 +33,9 @@ sensor: Configuration variables: -- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar. -- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar. +- **name** (*Optional*): You can specify a name of the component, but do not have to. If you specify a name, the sensors will get an entity name of 'sensor.[name]`[monitored_condition]`, for example: `sensor.lopik_temperature`; if no name is specified the sensors will be called `sensor.br_[monitored_condition]`, for example `sensor.br_temperature`. +- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl. +- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl. - **timeframe** (*Optional*): Minutes to look ahead for precipitation (5..120) [default: 60]. - **monitored_conditions** array (*Required*): One or more conditions to display in the frontend. - **stationname**: The name of the selected meteo-station. diff --git a/source/_components/sensor.comfoconnect.markdown b/source/_components/sensor.comfoconnect.markdown new file mode 100644 index 00000000000..78d22454b9b --- /dev/null +++ b/source/_components/sensor.comfoconnect.markdown @@ -0,0 +1,17 @@ +--- +layout: page +title: "Zehnder ComfoAir Q Ventilation sensors" +description: "Instructions how to integrate Zehnder ComfoAir Q350/450/600 sensors into Home Assistant." +date: 2017-06-28 18:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: zehnder.png +ha_category: Sensor +ha_release: "0.48" +--- + +Please see the [main component] for information how to set it up. + +[main component]: /components/comfoconnect/ diff --git a/source/_components/sensor.command_line.markdown b/source/_components/sensor.command_line.markdown index c0a39d4093e..ba1bee321aa 100644 --- a/source/_components/sensor.command_line.markdown +++ b/source/_components/sensor.command_line.markdown @@ -31,7 +31,7 @@ Configuration variables: - **name** (*Optional*): Name of the command sensor. - **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any. - **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload. -- **scan_interval** (*Optional*): Defines number of seconds for polling interval. +- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds). ## {% linkable_title Examples %} @@ -104,7 +104,7 @@ sensor: ### {% linkable_title Read value out of a remote text file %} -If you own a devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value. +If you own a devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value. ```yaml sensor: diff --git a/source/_components/sensor.knx.markdown b/source/_components/sensor.knx.markdown index 6fee026f346..535f5bf3b3e 100644 --- a/source/_components/sensor.knx.markdown +++ b/source/_components/sensor.knx.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: knx.png -ha_category: DIY +ha_category: Sensor ha_release: 0.29 ha_iot_class: "Local Push" --- diff --git a/source/_components/sensor.netatmo.markdown b/source/_components/sensor.netatmo.markdown index 398a341a607..e92471bdb15 100644 --- a/source/_components/sensor.netatmo.markdown +++ b/source/_components/sensor.netatmo.markdown @@ -52,10 +52,10 @@ Configuration variables: - **rain**: Estimated rainfall for today in mm. - **sum_rain_1**: Rainfall in the last hour in mm. - **sum_rain_24**: Rainfall in mm from 00:00am - 23:59pm. - - **WindAngle**: Wind angle - - **WindStrength**: Wind strength - - **GustAngle**: Wind gust angle - - **GustStrength**: Wind gust strength + - **windangle**: Wind angle + - **windstrength**: Wind strength + - **gustangle**: Wind gust angle + - **guststrength**: Wind gust strength - **min_temp**: Min temperature for today - **max_temp**: Max temperature for today - **rf_status**: Current radio status per module. (90=low, 60=highest) @@ -69,4 +69,3 @@ You can find your modules name in your [online NetAtmo account](https://my.netat