diff --git a/source/_components/garage_door.markdown b/source/_components/garage_door.markdown deleted file mode 100644 index 10cb067fc8e8..000000000000 --- a/source/_components/garage_door.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Garage door" -description: "Instructions how to integrate Garage doors into Home Assistant." -date: 2016-02-12 07:00 -sidebar: true -comments: false -sharing: true -footer: true ---- - -

-**This component has been deprecated in favor of the "[cover](/component/cover/)" component and will be removed in the future. Please use cover.** -

- -Home Assistant can give you an interface to control any garage door. diff --git a/source/_components/garage_door.mqtt.markdown b/source/_components/garage_door.mqtt.markdown deleted file mode 100644 index c99033a26713..000000000000 --- a/source/_components/garage_door.mqtt.markdown +++ /dev/null @@ -1,65 +0,0 @@ ---- -layout: page -title: "MQTT Garage door" -description: "Instructions how to setup the MQTT controllable garage doors within Home Assistant." -date: 2016-04-10 07:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: mqtt.png -ha_category: Deprecated -ha_release: 0.18 -ha_iot_class: depends ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.mqtt/)" platform and will be removed in the future. Please use the cover platform.** -

- -The `mqtt` garage door platform let you control your MQTT enabled garage door. - -In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with RETAIN flag, the MQTT switch will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the switch will be false/off. - -When a state topic is not available, the switch will work in optimistic mode. In this mode, the switch will immediately change state after every command. Otherwise, the switch will wait for state confirmation from device (message from `state_topic`). - -Optimistic mode can be forced, even if state topic is available. Try to enable it, if experiencing incorrect switch operation. - -To use your MQTT binary sensor in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yml entry -garage_door: - platform: mqtt - state_topic: "home-assistant/garage-door" - command_topic: "home-assistant/garage-door/set" - name: "MQTT Sensor" - optimistic: false - qos: 0 - retain: true - state_open: "STATE_OPEN" - state_closed: "STATE_CLOSED" - service_open: "SERVICE_OPEN" - service_close: "SERVICE_CLOSE" - value_template: '{% raw %}{{ value.x }}{% endraw %}' -``` - -Configuration variables: - -- **state_topic** (*Required*): The MQTT topic subscribed to receive sensor values. -- **name** (*Optional*): The name of the sensor. Default is 'MQTT Sensor'. -- **state_open** (*Optional*): The payload that represents open state. Default is"STATE_OPEN" -- **state_closed** (*Optional*): The payload that represents closed state. Default is "STATE_CLOSED" -- **service_open** (*Optional*): The payload that represents open state in service mode. Default is"SERVICE_OPEN" -- **service_close** (*Optional*): The payload that represents closed state in service mode. Default is "SERVICE_CLOSE" -- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is true if no state topic defined, else false. -- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages. -- **retain** (*Optional*): If the published message should have the retain flag on or not. -- **value_template** (*Optional*): Defines a [template](/topics/templating/) to extract a value from the payload. - -For a quick check you can use the commandline tools shipped with `mosquitto` to send MQTT messages. Set the state of your sensor manually: - -```bash -$ mosquitto_pub -h 127.0.0.1 -t home-assistant/garage-door/set -m "OFF" -``` - diff --git a/source/_components/garage_door.rpi_gpio.markdown b/source/_components/garage_door.rpi_gpio.markdown deleted file mode 100644 index 24ae200c7206..000000000000 --- a/source/_components/garage_door.rpi_gpio.markdown +++ /dev/null @@ -1,53 +0,0 @@ ---- -layout: page -title: "Raspberry Pi Garage door" -description: "Instructions how to setup the Raspberry Pi garage doors within Home Assistant." -date: 2016-02-12 07:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: raspberry-pi.png -ha_category: Deprecated -ha_release: 0.23 ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.rpi_gpio/)" platform and will be removed in the future. Please use the cover platform.** -

- -The `rpi_gpio` garage door platform allows you to use a Raspberry Pi to control your Garage door. - -It uses two pins on the Raspberry Pi. - -- The `state_pin` will detect if the door is closed, and -- the `relay_pin` will trigger the door to open or close. - -Although you do not need Andrews Hilliday's software controller when you run Home Assistant, he has written clear instructions on how to hook your garage door & sensors up to your Raspberry Pi, which can be found [here](https://github.com/andrewshilliday/garage-door-controller#hardware-setup). - -To enable Raspberry Pi Garage doors in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -garage_door: - platform: rpi_gpio - state_pull_mode: DOWN - relay_time: 1 - doors: - - relay_pin: 10 - state_pin: 11 - name: 'Left door' - - relay_pin: 12 - state_pin: 13 - name: 'Right door' -``` - -Configuration variables: - -- **doors** array (*Required*): List of your doors. - - **name** (*Optional*): Name to use in the Frontend. - - **relay_pin** (*Required*): The pin of your Raspberry Pi where the relay is connected. - - **state_pin** (*Required*): The pin of your Raspberry Pi to retrieve the state. - - **state_pull_mode** (*Optional*): The direction the State pin is pulling. It can be UP or DOWN. Default is UP. - - **relay_time** (*Optional*): The time that the relay will be on for in seconds. Default is .2 seconds. - diff --git a/source/_components/garage_door.wink.markdown b/source/_components/garage_door.wink.markdown deleted file mode 100644 index dc178e57698a..000000000000 --- a/source/_components/garage_door.wink.markdown +++ /dev/null @@ -1,30 +0,0 @@ ---- -layout: page -title: "Wink Garage door" -description: "Instructions how to setup the Wink garage doors within Home Assistant." -date: 2016-02-12 07:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: wink.png -ha_category: Deprecated -ha_release: 0.13 ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.wink/)" platform and will be removed in the future. Please use the cover platform.** -

- -Wink garage door functionality is currently limited to view only. Wink garage doors will still show the current state of the door, but control has been disabled for third parties. If you have a Chamberlain garage door, and would like to control it via Home Assistant, please contact Chamberlain and request that they re-enabled third-party control. - -The following quote is from Wink. - -
-As part of our agreement with Chamberlain, third-party access to control Chamberlain garage doors has been restricted. Please contact Chamberlain directly to inquire about permissions. -
- -~~The Wink garage door platform allows you to control your [Wink](http://www.wink.com/) enabled garage door.~~ - -The requirement is that you have setup your [Wink hub](/components/wink/). - diff --git a/source/_components/garage_door.zwave.markdown b/source/_components/garage_door.zwave.markdown deleted file mode 100644 index c07a96085fe5..000000000000 --- a/source/_components/garage_door.zwave.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Z-Wave Garage Door" -description: "Instructions how to setup the Z-Wave garage doors within Home Assistant." -date: 2015-11-15 13:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: z-wave.png -ha_category: Deprecated -ha_release: 0.23 ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.zwave/)" platform and will be removed in the future. Please use the cover platform.** -

- -To get your Z-Wave garage doors working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/). diff --git a/source/_components/hvac.markdown b/source/_components/hvac.markdown deleted file mode 100644 index db57959bf975..000000000000 --- a/source/_components/hvac.markdown +++ /dev/null @@ -1,26 +0,0 @@ ---- -layout: page -title: "HVAC" -description: "Instructions on how to integrate HVAC devices status with Home Assistant." -date: 2016-05-07 09:00 -sidebar: true -comments: false -sharing: true -footer: true -ha_release: 0.19 ---- - -

-**This component has been deprecated in favor of the "[climate](/components/climate/)" component and will be removed in the future. Please use climate.** -

- -The `hvac` component is built for the controlling and monitoring of HVAC (heating, ventilating, and air conditioning) devices. - -To enable this component, pick one of the platforms and add it to your `configuration.yaml`: - -```yaml -# Example configuration.yaml entry -hvac: - platform: demo -``` - diff --git a/source/_components/hvac.zwave.markdown b/source/_components/hvac.zwave.markdown deleted file mode 100644 index 820706cec4b2..000000000000 --- a/source/_components/hvac.zwave.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Z-Wave HVAC" -description: "Instructions on how to integrate HVAC Z-Wave devices status with Home Assistant." -date: 2016-05-07 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: z-wave.png -ha_category: Deprecated -ha_release: 0.19 ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.zwave/)" platform and will be removed in the future. Please use the climate platform.** -

- -To get your Z-Wave `hvac` devices working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/) and the [HVAC component](/components/hvac/). diff --git a/source/_components/rollershutter.command_line.markdown b/source/_components/rollershutter.command_line.markdown deleted file mode 100644 index 60db74048976..000000000000 --- a/source/_components/rollershutter.command_line.markdown +++ /dev/null @@ -1,44 +0,0 @@ ---- -layout: page -title: "Command line Rollershutter" -description: "Instructions how to have rollershutters call command line commands." -date: 2016-02-22 13:45 -sidebar: true -comments: false -sharing: true -footer: true -logo: command_line.png -ha_category: Deprecated -ha_release: 0.14 ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.command_line/)" platform and will be removed in the future. Please use the cover platform.** -

- -A `rollershutter` platform that issues specific commands when it is moved up, down and stopped. This might very well become our most powerful platform as it allows anyone to integrate any type of rollershutter into Home Assistant that can be controlled from the command line, including calling other scripts! - -To enable command_rollershutter in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -rollershutter: -- platform: command_line - rollershutters: - Kitchen Rollershutter: - upcmd: move_command up kitchen - downcmd: move_command down kitchen - stopcmd: move_command stop kitchen - statecmd: state_command kitchen - value_template: '{% raw %}{{ value }}{% endraw %}' -``` - -Configuration variables: - -- **rollershutters** (*Required*): The array that contains all command rollershutters. - - **entry** (*Required*): Name of the command rollershutter. Multiple entries are possible. - - **upcmd** (*Required*): The action to take for move up. - - **downcmd** (*Required*): The action to take for move down. - - **stopcmd** (*Required*): The action to take for stop. - - **statecmd** (*Optional*): If given, this command will be run. Returning a result code `0` will indicate that the rollershutter is fully closed, returning a result code `100` will indicate that the rollershutter is fully open. - - **value_template** (*Optional - default: '{% raw %}{{ value }}{% endraw %}'*): If specified, statecmd will ignore the result code of the command but the template evaluating will indicate the position of the rollershutter. diff --git a/source/_components/rollershutter.homematic.markdown b/source/_components/rollershutter.homematic.markdown deleted file mode 100644 index eb536f40e71b..000000000000 --- a/source/_components/rollershutter.homematic.markdown +++ /dev/null @@ -1,22 +0,0 @@ ---- -layout: page -title: "Homematic Rollershutter" -description: "Instructions how to integrate Homematic rollershutters within Home Assistant." -date: 2016-06-28 08:30 -sidebar: true -comments: false -sharing: true -footer: true -logo: homematic.png -ha_category: Deprecated -ha_release: 0.23 -ha_iot_class: "Local Push" ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.homematic/)" platform and will be removed in the future. Please use the cover platform.** -

- -The `homematic` rollershutter platform lets you control [Homematic](http://www.homematic.com/) rollershutters through Home Assistant. - -Devices will be configured automatically. Please refer to the [component](/components/homematic/) configuration on how to setup Homematic. diff --git a/source/_components/rollershutter.markdown b/source/_components/rollershutter.markdown deleted file mode 100644 index f6306a9ad99d..000000000000 --- a/source/_components/rollershutter.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Rollershutters" -description: "Instructions how to integrate rollershutters into Home Assistant." -date: 2015-12-01 12:00 -sidebar: true -comments: false -sharing: true -footer: true ---- - -

-**This component has been deprecated in favor of the "[cover](/components/cover/)" component and will be removed in the future. Please use cover.** -

- -Home Assistant can give you an interface to control any rollershutters. diff --git a/source/_components/rollershutter.mqtt.markdown b/source/_components/rollershutter.mqtt.markdown deleted file mode 100644 index 5eab5e959968..000000000000 --- a/source/_components/rollershutter.mqtt.markdown +++ /dev/null @@ -1,50 +0,0 @@ ---- -layout: page -title: "MQTT Rollershutter" -description: "Instructions how to integrate MQTT motorized devices into Home Assistant." -date: 2015-12-01 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: mqtt.png -ha_category: Deprecated -ha_release: 0.9 -ha_iot_class: depends ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.mqtt/)" platform and will be removed in the future. Please use the cover platform.** -

- -The `mqtt` rollershutter platform enables the possibility to control an MQTT rollershutter. The device state will be updated only after receiving the a new state from `state_topic`. If these messages are published with RETAIN flag, the MQTT device will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state will be `unknown`. - -There is a state attribute that stores the relative position of the device, where 0% means the device is `closed` and all other intermediate positions means the device is `open`. - -To enable this platform, add the following lines to your `configuration.yaml`: - -```yaml -# Example configuration.yaml entry -rollershutter: - platform: mqtt - name: "Bedroom Rollershutter" - state_topic: "home/bedroom/rollershutter" - command_topic: "home/bedroom/rollershutter/set" - qos: 0 - payload_up: "OPEN" - payload_down: "CLOSE" - payload_stop: "STOP" - value_template: '{% raw %}{{ value.x }}{% endraw %}' -``` - -Configuration variables: - -- **command_topic** (*Required*): The MQTT topic to publish commands to control the rollershutter. - -- **name** (*Optional*): The name of the rollershutter. Default is 'MQTT Rollershutter'. -- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates. If not defined, the rollershutter will be stateless, that is, no information about current position or open/closed. If defined, the received payload must be a integer between 0 and 100, that represents the percentage for fully closed and fully open, respectively. -- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0. This QoS will also be used to publishing messages. -- **payload_up** (*Optional*): The payload to open the rollershutter. Default is "OPEN". -- **payload_down** (*Optional*): The payload to close the rollershutter. Default is "CLOSE". -- **payload_stop** (*Optional*): The payload to stop the rollershutter. Default is "STOP". -- **value_template** (*Optional*): Defines a [template](/topics/templating/) to extract a value from the payload. diff --git a/source/_components/rollershutter.rfxtrx.markdown b/source/_components/rollershutter.rfxtrx.markdown deleted file mode 100644 index 2400be8092ab..000000000000 --- a/source/_components/rollershutter.rfxtrx.markdown +++ /dev/null @@ -1,72 +0,0 @@ ---- -layout: page -title: "RFXtrx Rollershutter" -description: "Instructions how to integrate RFXtrx roller shutters into Home Assistant." -date: 2016-06-12 12:40 -sidebar: true -comments: false -sharing: true -footer: true -logo: rfxtrx.png -ha_category: Deprecated -ha_release: 0.21 ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.rfxtrx/)" platform and will be removed in the future. Please use the cover platform.** -

- -The `rfxtrx` platform supports Siemens/LightwaveRF and RFY roller shutters that communicate in the frequency range of 433.92 MHz. - -First you have to set up your [rfxtrx hub](/components/rfxtrx/). - -### {% linkable_title Configuration %} - -##### Siemens/LightwaveRF -The easiest way to find your roller shutters is to add this to your `configuration.yaml`: - -```yaml -rollershutter: - platform: rfxtrx - automatic_add: True -``` - -Launch your homeassistant and go the website (e.g http://localhost:8123). -Push your remote and your device should be added. - -Once added it will show an ID (e.g `0b11000102ef9f210010f70`) and you can verify that it works from the frontend. -Then you should update your configuration to: - -```yaml -rollershutter: - platform: rfxtrx - devices: - 0b11000102ef9f210010f70: - name: device_name -``` - -##### RFY -The [RFXtrx433e](http://www.rfxcom.com/RFXtrx433E-USB-43392MHz-Transceiver/en) is required for RFY support, however it does not support receive for the RFY protocol - as such devices cannot be automatically added. Instead, configure the device in the [rfxmngr](http://www.rfxcom.com/downloads.htm) tool. Make a note of the assigned ID and Unit Code and then add a device to the configuration with the following id `071a0000[id][unit_code]`. Eg, if the id was `0a` `00` `01`, and the unit code was `01` then the fully qualified id would be `071a00000a000101`. - -##### Common -Example configuration: - -```yaml -# Example configuration.yaml entry -rollershutter: - platform: rfxtrx - automatic_add: False - signal_repetitions: 2 - devices: - 0b1100ce3213c7f210010f70: # Siemens/LightwaveRF - name: Bedroom Shutter - 070a00000a000101: # RFY - name: Bathroom Shutter -``` - -Configuration variables: - -- **devices** (*Required*): A list of devices with their name to use in the frontend. -- **automatic_add** (*Optional*): To enable the automatic addition of new roller shutters (Siemens/LightwaveRF only). -- **signal_repetitions** (*Optional*): Because the rxftrx device sends its actions via radio and from most receivers it's impossible to know if the signal was received or not. Therefore you can configure the roller shutter to try to send each signal repeatedly. -- **fire_event** (*Optional*): Fires an event even if the state is the same as before. Can be used for automations. diff --git a/source/_components/rollershutter.scsgate.markdown b/source/_components/rollershutter.scsgate.markdown deleted file mode 100644 index 6abb75963362..000000000000 --- a/source/_components/rollershutter.scsgate.markdown +++ /dev/null @@ -1,36 +0,0 @@ ---- -layout: page -title: "SCSGate Rollershutter" -description: "Instructions how to integrate SCSGate motorized devices into Home Assistant." -date: 2016-01-31 22:16 -sidebar: true -comments: false -sharing: true -footer: true -logo: bus_scs.png -ha_category: Deprecated ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.scsgate/)" platform and will be removed in the future. Please use the cover platform.** -

- -The SCSGate device can control motirized roller shutters connected to the BTicino MyHome system. - -To enable SCSGate roller shutters in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -rollershutter: - platform: scsgate - devices: - living_room: - name: Living Room - scs_id: XXXXX -``` - -Configuration variables: - -- **devices** (*Required*): A list of devices with their name to use in the frontend. - -**Known limitation:** it is not possible to know the current state of the roller shutter. diff --git a/source/_components/rollershutter.wink.markdown b/source/_components/rollershutter.wink.markdown deleted file mode 100644 index 0535392f21a4..000000000000 --- a/source/_components/rollershutter.wink.markdown +++ /dev/null @@ -1,24 +0,0 @@ ---- -layout: page -title: "Wink Rollershutter" -description: "Instructions how to setup the Wink rollershutter (shade) within Home Assistant." -date: 2016-02-12 07:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: wink.png -ha_category: Deprecated -ha_release: 0.22 ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.wink/)" platform and will be removed in the future. Please use the cover platform.** -

- -The `wink` rollershutter platform allows you to control your [Wink](http://www.wink.com/) enabled rollershutters. It supports Wink shades/blinds/rollershutters such as the Bali Somfy or Lutron Serena blinds. - -The Wink API currently doesn't provide status for shades. - -The requirement is that you have setup your [Wink hub](/components/wink/). - diff --git a/source/_components/rollershutter.zwave.markdown b/source/_components/rollershutter.zwave.markdown deleted file mode 100644 index ebed95ed0fcb..000000000000 --- a/source/_components/rollershutter.zwave.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Z-Wave Rollershutter" -description: "Instructions how to setup the Z-Wave rollershutters within Home Assistant." -date: 2015-11-15 13:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: z-wave.png -ha_category: Deprecated -ha_release: 0.23 ---- - -

-**This platform has been deprecated in favor of a "[cover](/components/cover.zwave/)" platform and will be removed in the future. Please use the cover platform.** -

- -To get your Z-Wave rollershutters working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/). diff --git a/source/_components/thermostat.ecobee.markdown b/source/_components/thermostat.ecobee.markdown deleted file mode 100644 index 656834694730..000000000000 --- a/source/_components/thermostat.ecobee.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Ecobee Thermostat" -description: "Instructions how to setup the Ecobee thermostats within Home Assistant." -date: 2015-11-30 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: ecobee.png -ha_category: Deprecated -ha_release: 0.9 ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.ecobee/)" platform and will be removed in the future. Please use the climate platform.** -

- -To get your Ecobee thermostats working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/). diff --git a/source/_components/thermostat.eq3btsmart.markdown b/source/_components/thermostat.eq3btsmart.markdown deleted file mode 100644 index 3715452e9dc5..000000000000 --- a/source/_components/thermostat.eq3btsmart.markdown +++ /dev/null @@ -1,67 +0,0 @@ ---- -layout: page -title: "EQ3 Bluetooth Smart Thermostats" -description: "Instructions how to integrate EQ3 Bluetooth Smart Thermostats into Home Assistant." -date: 2016-04-18 22:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: eq3.gif -ha_category: Deprecated -ha_iot_class: "Local Poll" ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.eq3btsmart/)" platform and will be removed in the future. Please use the climate platform.** -

- -This platform allows you to integrate EQ3 Bluetooth Smart Thermostats. - -The only functionality is to set the temperature, there doesn't seem to be any way to query the temperature sensor or battery level ([read more](https://forum.fhem.de/index.php/topic,39308.15.html)). - -Setup is a bit more cumbersome than for most other thermostats. It has to be paired first: - -```bash -bluetoothctl -scan on - -scan off - -pair -trust -disconnect -exit -``` - -Then check with gatttool if the connection works as expected: - -```bash -gatttool -b 00:11:22:33:44:55 -I -[00:11:22:33:44:55][LE]> connect -Attempting to connect to 00:11:22:33:44:55 -Connection successful -[00:11:22:33:44:55][LE]> char-write-req 0x0411 03 -Characteristic value was written successfully -Notification handle = 0x0421 value: 02 01 09 14 04 2d -[00:11:22:33:44:55][LE]> disconnect -[00:11:22:33:44:55][LE]> exit -``` - -Important: For gatttool or homeassistant to work, the thermostat needs to be disconnected from bluetoothd, so I found it best to modify the hass-daemon startscript by adding: - -```bash -/usr/bin/bt-device -d CC-RT-BLE -``` - -to the start function of /etc/init.d/hass-daemon. - - -```yaml -# Example configuration.yaml entry -thermostat: - platform: eq3btsmart - devices: - room1: - mac: '00:11:22:33:44:55' -``` diff --git a/source/_components/thermostat.heat_control.markdown b/source/_components/thermostat.heat_control.markdown deleted file mode 100644 index 4c580183d4bc..000000000000 --- a/source/_components/thermostat.heat_control.markdown +++ /dev/null @@ -1,48 +0,0 @@ ---- -layout: page -title: "Generic Thermostat" -description: "Turn Home Assistant into a thermostat" -date: 2015-03-23 19:59 -sidebar: true -comments: false -sharing: true -footer: true -logo: heat-control.png -ha_category: Deprecated ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.generic_thermostat/)" platform and will be removed in the future. Please use the climate platform.** -

- -Heat Control is a thermostat implemented in Home Assistant. It uses a sensor and a switch connected to a heater under the hood. If the measured temperature is cooler then the target temperature, the heater will be turned on and turned off when required temperature is reached. - -```yaml -# Example configuration.yaml entry -thermostat: - platform: heat_control - name: Study - heater: switch.study_heater - target_sensor: sensor.study_temperature - min_temp: 15 - max_temp: 21 - target_temp: 15 - min_cycle_duration: - # At least one of these must be specified: - days: 2 - hours: 1 - minutes: 10 - seconds: 5 - milliseconds: 20 -``` - -Configuration variables: - -- **name** (*Required*): Name of thermostat -- **heater** (*Required*: `entity_id` for heater switch, must be a toggle device. -- **target_sensor** (*Required*): `entity_id` for a temperature sensor, target_sensor.state must be temperature. -- **min_temp** (*Optional*): Set minimum set point available (default: 7) -- **max_temp** (*Optional*): Set maximum set point available (default: 35) -- **target_temp** (*Required*): Set intital target temperature. Failure to set this variable will result in target temperature being set to null on startup. -- **ac_mode** (*Optional*): Set the switch specified in the *heater* option to be treated as a cooling device instead of a heating device. -- **min_cycle_duration** (*Optional*): Set a minimum amount of time that the switch specified in the *heater* option must be in it's current state prior to being switched either off or on. diff --git a/source/_components/thermostat.heatmiser.markdown b/source/_components/thermostat.heatmiser.markdown deleted file mode 100644 index 8b5fe55835e7..000000000000 --- a/source/_components/thermostat.heatmiser.markdown +++ /dev/null @@ -1,44 +0,0 @@ ---- -layout: page -title: "Heatmiser Thermostat" -description: "Instructions how to integrate Heatmiser thermostats within Home Assistant." -date: 2015-12-11 12:35 -sidebar: true -comments: false -sharing: true -footer: true -logo: heatmiser.png -ha_category: Deprecated -ha_release: "0.10" ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.heatmiser/)" platform and will be removed in the future. Please use the climate platform.** -

- -The `heatmiser` thermostat platform let you control [Heatmiser DT/DT-E/PRT/PRT-E](http://www.heatmisershop.co.uk/heatmiser-slimline-programmable-room-thermostat/) thermostats from Heatmiser. The module itself is currently setup to work over a RS232 -> RS485 converter, therefore it connects over IP. - -Further work would be required to get this setup to connect over Wifi, but the HeatmiserV3 python module being used is a full implementation of the V3 protocol. If you would like to contribute to making this work over wifi, please contact @andylockran on github. - -To set it up, add the following information to your `configuration.yaml` file: - -```yaml -thermostat: - platform: heatmiser - ipaddress: YOUR_IPADDRESS - port: YOUR_PORT - tstats: - - 1: - id: THERMOSTAT_ID - name: THERMOSTAT_NAME -``` - -A single interface can handle up to 32 connected devices. - -Configuration variables: - -- **ipaddress** (*Required*): The ip address of your interface. -- **port** (*Required*): The port that the interface is listening on. -- **tstats** (*Required*): A list of thermostats activated on the gateway. -- **id** (*Required*): The id of the thermostat as configured on the device itself -- **name** (*Required*): A friendly name for the themostat diff --git a/source/_components/thermostat.honeywell.markdown b/source/_components/thermostat.honeywell.markdown deleted file mode 100644 index 0966bf7c932a..000000000000 --- a/source/_components/thermostat.honeywell.markdown +++ /dev/null @@ -1,35 +0,0 @@ ---- -layout: page -title: "Honeywell Thermostat" -description: "Instructions how to integrate Honeywell thermostats within Home Assistant." -date: 2016-02-07 22:01 -sidebar: true -comments: false -sharing: true -footer: true -logo: honeywell.png -ha_category: Deprecated ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.honeywell/)" platform and will be removed in the future. Please use the climate platform.** -

- -The `honeywell` thermostat platform let you control [Honeywell Connected](http://getconnected.honeywell.com/en/) thermostats from Home Assistant. - -To set it up, add the following information to your `configuration.yaml` file: - -```yaml -thermostat: - platform: honeywell - username: YOUR_USERNAME - password: YOUR_PASSWORD - region: REGION -``` - -Configuration variables: - -- **username** (*Required*: The username of an user with access. -- **password** (*Required*): The password for your given admin account. -- **away_temperature** (*optional*): Heating setpoint when away mode is on. If omitted it defaults to 16.0 deg C. -- **region** (*optional*): Region identifier (either 'eu' or 'us'). Defaults to 'eu' if not provided. diff --git a/source/_components/thermostat.knx.markdown b/source/_components/thermostat.knx.markdown deleted file mode 100644 index 4fc19252eb8f..000000000000 --- a/source/_components/thermostat.knx.markdown +++ /dev/null @@ -1,38 +0,0 @@ ---- -layout: page -title: "KNX Thermostat" -description: "Instructions on how to integrate KXN thermostats with Home Assistant." -date: 2016-06-24 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: knx.png -ha_category: Deprecated -ha_release: 0.25 ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.knx/)" platform and will be removed in the future. Please use the climate platform.** -

- -The `knx` thermostat platform is used as in interface with KNX thermostats. - -KNX thermostats use at least 2 group addresses: one for the current temperature and one for the target temperature (named set-point in KNX terms). - -To use your KNX thermostats in your installation, add the following to your `configuration.yaml` file: - -```yaml -thermostat: - - platform: knx - name: KNX Thermostat - temperature_address: 0/1/1 - setpoint_address: 0/1/0 -``` - -- **name** (*Optional*): A name for this devices used within Home assistant -- **address** (*Required*): The KNX group address that is used to turn on/off this actuator channel -- **temperature_address** (*Required*): The group address that is used to communicate the current temperature. Data format must be datapoint type 9.001 DPT_Value_Temp (2-Octet float value) (see http://www.knx.org/fileadmin/template/documents/downloads_support_menu/KNX_tutor_seminar_page/Advanced_documentation/05_Interworking_E1209.pdf) -- **setpoint_address** (*Required*): The group address that is used to set/read the target temperature. Data format must be datapoint type 9.001 DPT_Value_Temp (2-Octet float value). Make sure, you set the read-flag for the thermostat to allow Home Assistant to read the target temperature. - -With the current version of the module, no advanced KNX thermostat functionalities (e.g. HVAC mode) are supported. diff --git a/source/_components/thermostat.markdown b/source/_components/thermostat.markdown deleted file mode 100644 index 5a2e618b00fe..000000000000 --- a/source/_components/thermostat.markdown +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: page -title: "Thermostats" -description: "Instructions how to setup thermostats tracking within Home Assistant." -date: 2015-01-20 22:36 -sidebar: true -comments: false -sharing: true -footer: true ---- - -

-**This component has been deprecated in favor of the "[climate](/components/climate/)" component and will be removed in the future. Please use climate.** -

- -Thermostats offer Home Assistant a peek into the current and target temperature in a house. Some thermostats will also offer an away mode that will lower use of heating/cooling. - -

- -

diff --git a/source/_components/thermostat.nest.markdown b/source/_components/thermostat.nest.markdown deleted file mode 100644 index 0f6092393cde..000000000000 --- a/source/_components/thermostat.nest.markdown +++ /dev/null @@ -1,31 +0,0 @@ ---- -layout: page -title: "Nest Thermostat" -description: "Instructions how to integrate Nest thermostats within Home Assistant." -date: 2015-03-23 19:59 -sidebar: true -comments: false -sharing: true -footer: true -logo: nest_thermostat.png -ha_category: Deprecated ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.nest/)" platform and will be removed in the future. Please use the climate platform.** -

- -The `nest` thermostat platform let you control a thermostat from [Nest](https://nest.com). - -To set it up, add the following information to your `configuration.yaml` file: - -```yaml -thermostat: - platform: nest -``` - -

- -

- -

You must have the [Nest component](https://home-assistant.io/components/nest/) configured to use this sensor.

diff --git a/source/_components/thermostat.proliphix.markdown b/source/_components/thermostat.proliphix.markdown deleted file mode 100644 index bd37e067a34d..000000000000 --- a/source/_components/thermostat.proliphix.markdown +++ /dev/null @@ -1,43 +0,0 @@ ---- -layout: page -title: "Proliphix Thermostat" -description: "Instructions how to integrate Proliphix thermostats within Home Assistant." -date: 2016-01-15 08:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: proliphix.png -ha_category: Deprecated -ha_release: 0.11 ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.proliphix/)" platform and will be removed in the future. Please use the climate platform.** -

- -The `proliphix` thermostat platform let you control [Proliphix](http://www.proliphix.com) thermostat from Home Assistant. - -Currently supported and tested thermostats: - -- NT10e - -To set it up, add the following information to your `configuration.yaml` file: - -```yaml -thermostat: - platform: proliphix - host: IP_ADDRESS - username: YOUR_USERNAME - password: YOUR_PASSWORD -``` - -Configuration variables: - -- **host** (*Required*): Adress of your thermostat, eg. 192.168.1.32 -- **username** (*Required*): Username for the thermostat. -- **password** (*Required*): Password for the thermostat. - -The Proliphix NT Thermostat series are ethernet connected thermostats. They have a local HTTP interface that is based on get/set -of OID values. A complete collection of the API is available in this [API documentation](https://github.com/sdague/thermostat.rb/blob/master/docs/PDP_API_R1_11.pdf). - diff --git a/source/_components/thermostat.radiotherm.markdown b/source/_components/thermostat.radiotherm.markdown deleted file mode 100644 index 5919915ed03f..000000000000 --- a/source/_components/thermostat.radiotherm.markdown +++ /dev/null @@ -1,43 +0,0 @@ ---- -layout: page -title: "Radiotherm Thermostat" -description: "Instructions how to integrate Radiotherm thermostats within Home Assistant." -date: 2015-10-18 17:15 -sidebar: true -comments: false -sharing: true -footer: true -logo: radiotherm.png -ha_category: Deprecated ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.radiotherm/)" platform and will be removed in the future. Please use the climate platform.** -

- -The `radiotherm` thermostat platform let you control a thermostat from [Radio Thermostat](http://www.radiothermostat.com/). - -The underlaying library supports: -- CT50 V1.09 -- CT50 V1.88 -- CT50 V1.94 (also known as Filtrete 3M50) -- CT80 Rev B2 V1.03 - -To set it up, add the following information to your `configuration.yaml` file: - -```yaml -thermostat: - platform: radiotherm - host: - - 192.168.99.137 - - 192.168.99.202 - hold_temp: True -``` - -Configuration variables: - -- **host** (*Required*): List of your Radiotherm thermostats -- **hold_temp** (*Required*): Boolean to control if Home Assistant temperature adjustments hold (`True`) or are temporary (`False`). - -Temperature settings from Home Assistant will be sent to thermostat and then hold at that temperature. Set to `False` if you set a thermostat schedule on the thermostat itself and just want Home Assistant to send temporary temperature changes. - diff --git a/source/_components/thermostat.zwave.markdown b/source/_components/thermostat.zwave.markdown deleted file mode 100644 index 8be1479feddc..000000000000 --- a/source/_components/thermostat.zwave.markdown +++ /dev/null @@ -1,25 +0,0 @@ ---- -layout: page -title: "Z-Wave Thermostat" -description: "Instructions how to setup the Z-Wave thermostat within Home Assistant." -date: 2016-04-03 9:52 -sidebar: true -comments: false -sharing: true -footer: true -logo: z-wave.png -ha_category: Deprecated -ha_release: 0.17 ---- - -

-**This platform has been deprecated in favor of a "[climate](/components/climate.zwave/)" platform and will be removed in the future. Please use the climate platform.** -

- -To get your Z-Wave thermostat working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/). - -

-If your thermostat support fan modes or different operating modes, it should be considered a [HVAC component](/components/hvac.zwave/), and will also be detected as one. Thermostat component does not support setting fan or operation mode. This is controlled via the HVAC component. - -If the thermostat support different operationg modes, you will get one thermostat entity for each mode. These can be hidden with settings using the customize setting in the `configuration.yaml` file. -