diff --git a/_config.yml b/_config.yml index d08fca10a6c..0ed1eca7007 100644 --- a/_config.yml +++ b/_config.yml @@ -144,8 +144,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 86 -current_patch_version: 1 -date_released: 2019-01-24 +current_patch_version: 3 +date_released: 2019-01-26 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_addons/nginx_proxy.markdown b/source/_addons/nginx_proxy.markdown index 471ec08c5f8..4bf6c3ad9af 100644 --- a/source/_addons/nginx_proxy.markdown +++ b/source/_addons/nginx_proxy.markdown @@ -11,7 +11,7 @@ footer: true Sets up an SSL proxy with NGINX and redirect port 80 to 443. Make sure you have generated a certificate before you start this add-on. -In the `http` section of the `configuration.yaml` file remove `ssl_certificate` and `ssl_key` and don't enter the port in the `base_url` to avoid an HTTP 502 error. +In the `http` section of the `configuration.yaml` file remove `ssl_certificate`, `ssl_key` and `server_port` and don't enter the port in the `base_url` to avoid an HTTP 502 error. ```json { diff --git a/source/_addons/tellstick.markdown b/source/_addons/tellstick.markdown index eb6075fdbde..5c9f9aebe74 100644 --- a/source/_addons/tellstick.markdown +++ b/source/_addons/tellstick.markdown @@ -92,6 +92,8 @@ code: type: string {% endconfiguration %} +For more information about the configuration including protocols, see the [telldus documentation](https://developer.telldus.com/wiki/TellStick_conf). + ## {% linkable_title Service calls %} If you wish to teach a self-learning device in your TellStick configuration: diff --git a/source/_components/binary_sensor.ecobee.markdown b/source/_components/binary_sensor.ecobee.markdown deleted file mode 100644 index 103c818d495..00000000000 --- a/source/_components/binary_sensor.ecobee.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Ecobee Binary Sensor" -description: "Instructions on how to setup the Ecobee sensors within Home Assistant." -date: 2015-11-30 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: ecobee.png -ha_category: Environment -ha_release: 0.9 -ha_iot_class: "Local Push" ---- - -To get your Ecobee binary sensors working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/). diff --git a/source/_components/binary_sensor.enocean.markdown b/source/_components/binary_sensor.enocean.markdown deleted file mode 100644 index 9414cf563b7..00000000000 --- a/source/_components/binary_sensor.enocean.markdown +++ /dev/null @@ -1,76 +0,0 @@ ---- -layout: page -title: "EnOcean Binary Sensor" -description: "Instructions on how to set up EnOcean binary sensors within Home Assistant." -date: 2016-05-25 23:49 -sidebar: true -comments: false -sharing: true -footer: true -logo: enocean.png -ha_category: Binary Sensor -ha_release: 0.21 -ha_iot_class: "Local Push" ---- - -This can typically be one of those batteryless wall switches. -Tested with: - -- Eltako FT55 which uses the EnOcean PTM 215 module -- [TRIO2SYS Wall switches](http://www.trio2sys.fr/index.php/fr/produits-enocean-sans-fil-sans-pile-interoperable/emetteur-sans-fils-sans-pile-interoperable-enocean) which uses the EnOcean PTM210 DB module - -All switches using theses modules are expected to work. Other devices will most likely not work without changing the Home Assistant code. - -## {% linkable_title Configuration %} - -To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -binary_sensor: - - platform: enocean - id: [0x01,0x90,0x84,0x3C] -``` - -{% configuration %} -id: - description: The ID of the device. This is the 4 bytes long number written on the dimmer. - required: true - type: list -name: - description: An identifier for the switch in the frontend. - required: false - type: string - default: EnOcean binary sensor -device_class: - description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend. - required: false - type: device_class -{% endconfiguration %} - -EnOcean binary sensors only generate 'button_pressed' events. The event data has following four fields: - - - **id**: The ID of the device (see configuration). - - **pushed**: `1` for a button press, `0` for a button release. - - **which**: Always `0` when using the single rocket. `0` or `1` when using the dual rocket switch. - - **onoff**: `0` or `1` for either side of the rocket. - -## {% linkable_title Automation example %} - -Sample automation to switch lights on and off: - -```yaml -# Example automation to turn lights on/off on button release -automation: - - alias: hall light switches - trigger: - platform: event - event_type: button_pressed - event_data: - id: [0xYY, 0xYY, 0xYY, 0xYY] - pushed: 0 - action: - service_template: "{% raw %}{% if trigger.event.data.onoff %} light.turn_on {% else %} light.turn_off {%endif %}{% endraw %}" - data_template: - entity_id: "{% raw %}{% if trigger.event.data.which == 1 %} light.hall_left {% else %} light.hall_right {%endif %}{% endraw %}" -``` diff --git a/source/_components/binary_sensor.fritzbox.markdown b/source/_components/binary_sensor.fritzbox.markdown deleted file mode 100644 index 774e0597b45..00000000000 --- a/source/_components/binary_sensor.fritzbox.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Fritzbox Binary Sensor" -description: "Instructions on how to integrate an AVM Fritzbox alarm sensor." -date: 2018-10-01 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: avm.png -ha_category: Binary Sensor -ha_release: "0.80" -ha_iot_class: "Local Polling" ---- - -To get AVM fritzbox binary sensor follow the instructions for the [Fritzbox component](/components/fritzbox/). diff --git a/source/_components/binary_sensor.isy994.markdown b/source/_components/binary_sensor.isy994.markdown deleted file mode 100644 index 64735b86517..00000000000 --- a/source/_components/binary_sensor.isy994.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: page -title: "ISY994 Binary Sensor" -description: "Instructions on how to integrate ISY994 binary sensors into Home Assistant." -date: 2016-09-03 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: universal_devices.png -ha_category: Binary Sensor -ha_iot_class: "Local Push" -ha_release: pre 0.7 ---- - -The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) binary sensors from within Home Assistant. - -They will be automatically discovered if the `isy994` component is loaded. diff --git a/source/_components/binary_sensor.maxcube.markdown b/source/_components/binary_sensor.maxcube.markdown deleted file mode 100644 index ac6e5299ba9..00000000000 --- a/source/_components/binary_sensor.maxcube.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "eQ-3 MAX! Cube binary sensors" -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 -comments: false -sharing: true -footer: true -logo: maxcube.png -ha_category: Climate -ha_release: "0.40" -ha_iot_class: "Local Polling" ---- - -See instructions at the [main component](/components/maxcube/). diff --git a/source/_components/binary_sensor.mqtt.markdown b/source/_components/binary_sensor.mqtt.markdown index d972e37862c..392f2af5af2 100644 --- a/source/_components/binary_sensor.mqtt.markdown +++ b/source/_components/binary_sensor.mqtt.markdown @@ -69,8 +69,8 @@ payload_not_available: type: string default: offline json_attributes_topic: - description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. - reqired: false + description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Usage example can be found in [MQTT sensor](/components/sensor.mqtt/#json-attributes-topic-configuration) documentation. + required: false type: string qos: description: The maximum QoS level to be used when receiving messages. diff --git a/source/_components/binary_sensor.mychevy.markdown b/source/_components/binary_sensor.mychevy.markdown deleted file mode 100644 index 7ae1881a48a..00000000000 --- a/source/_components/binary_sensor.mychevy.markdown +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: page -title: "MyChevy Binary Sensor" -description: "Instructions on how to integrate Chevy Bolt binary sensors car into Home Assistant." -date: 2017-08-28 17:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: chevy.png -ha_category: Car -ha_release: 0.62 -ha_iot_class: "Cloud Polling" ---- - -The `mychevy` binary sensor platform allows you to monitor your Chevy Bolt car from within Home Assistant. - -The binary sensor platform will be automatically configured if the `mychevy` component is configured. - -For configuration instructions, see the [`mychevy` component](/components/mychevy/) documentation. diff --git a/source/_components/binary_sensor.raspihats.markdown b/source/_components/binary_sensor.raspihats.markdown deleted file mode 100644 index 05d4b5cbac8..00000000000 --- a/source/_components/binary_sensor.raspihats.markdown +++ /dev/null @@ -1,120 +0,0 @@ ---- -layout: page -title: "Raspihats Binary Sensor" -description: "Instructions on how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor." -date: 2017-05-01 04:09 -sidebar: true -comments: false -sharing: true -footer: true -logo: raspihats.png -ha_category: DIY -ha_release: 0.44 -ha_iot_class: "Local Push" ---- - -The `raspihats` binary sensor platform allows you to read sensor values ​​using the digital inputs of the [raspihats](http://www.raspihats.com/) boards. - -## {% linkable_title Configuration %} - -To use your `raspihats` boards in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -binary_sensor: - - platform: raspihats - i2c_hats: - - board: DI6acDQ6rly - address: 0x60 - channels: - - index: 0 - name: PIR Office - invert_logic: true - device_class: motion - - index: 1 - name: PIR Bedroom -``` - -{% configuration %} -i2c_hats: - description: An array of used I2C-HATs. - required: false - type: list - keys: - board: - description: The board name either Di16, Di6Rly6, DI16ac or DI6acDQ6rly. - required: true - type: string - address: - description: The board I2C address as HEX value. - required: true - type: string - channels: - description: Array of used digital input channels. - required: true - type: list - keys: - index: - description: Digital input channel index. - required: true - type: integer - name: - description: Friendly name to use for the frontend. - required: true - type: string - invert_logic: - description: Inverts the input logic. - required: false - default: false - type: boolean - device_class: - description: See device classes in [binary_sensor component](/components/binary_sensor/). - required: false - default: "None" - type: string -{% endconfiguration %} - -## {% linkable_title Directions for installing smbus support on Raspberry Pi %} - -Enable I2c interface with the Raspberry Pi configuration utility: - -```bash -# pi user environment: Enable i2c interface -$ sudo raspi-config -``` - -Select `Interfacing options->I2C` choose `` and hit `Enter`, then go to `Finish`. - -Install dependencies for use the `smbus-cffi` module and enable your _homeassistant_ user to join the _i2c_ group: - -```bash -# pi user environment: Install i2c dependencies and utilities -$ sudo apt-get install build-essential libi2c-dev i2c-tools python-dev libffi-dev - -# pi user environment: Add homeassistant user to the i2c group -$ sudo usermod -a -G i2c homeassistant -``` - -### {% linkable_title Check the i2c address of the sensor %} - -After installing `i2c-tools`, a new utility is available to scan the addresses of the connected sensors, so you can see the sensor address: - -```bash -$ /usr/sbin/i2cdetect -y 1 -``` - -It will output a table like this: - -```text - 0 1 2 3 4 5 6 7 8 9 a b c d e f -00: -- -- -- -- -- -- -- -- -- -- -- -- -- -10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -20: -- -- -- 23 -- -- -- -- -- -- -- -- -- -- -- -- -30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -40: 40 -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- -50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -70: -- -- -- -- -- -- -- 77 -``` - -For more details about the `raspihats` add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). diff --git a/source/_components/binary_sensor.sleepiq.markdown b/source/_components/binary_sensor.sleepiq.markdown deleted file mode 100644 index 3f355cc2780..00000000000 --- a/source/_components/binary_sensor.sleepiq.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "SleepIQ Binary Sensor" -description: "Instructions for how to integrate SleepIQ sensors within Home Assistant." -date: 2016-08-28 8:56 -sidebar: true -comments: false -sharing: true -footer: true -logo: sleepiq.png -ha_category: Health -ha_release: 0.29 -ha_iot_class: "Local Polling" ---- - -To get your SleepIQ binary sensors working with Home Assistant, follow the instructions for the general [SleepIQ component](/components/sleepiq/). diff --git a/source/_components/binary_sensor.tahoma.markdown b/source/_components/binary_sensor.tahoma.markdown deleted file mode 100644 index 1ba160f706d..00000000000 --- a/source/_components/binary_sensor.tahoma.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Tahoma Binary Sensor" -description: "Instructions on how to integrate Tahoma binary sensors into Home Assistant." -date: 2018-06-14 21:57 -sidebar: true -comments: false -sharing: true -footer: true -logo: tahoma.png -ha_category: Binary Sensor -ha_release: 0.73 ---- - -The `tahoma` binary sensor platform lets you see binary sensors added to your Tahoma Box in Home Assistant. For example smoke detectors. - -Binary sensors will be added automatically. Please refer to the [component](/components/tahoma/) configuration on how to setup Tahoma. diff --git a/source/_components/binary_sensor.tellduslive.markdown b/source/_components/binary_sensor.tellduslive.markdown deleted file mode 100644 index 8fea7f57c3e..00000000000 --- a/source/_components/binary_sensor.tellduslive.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "Telldus Binary Sensor" -description: "Instructions on how to integrate Telldus Live binary sensors into Home Assistant." -date: 2017-10-24 10:09 -sidebar: true -comments: false -sharing: true -footer: true -logo: telldus.png -ha_category: Binary Sensor -featured: false ---- - -Integrates Telldus Live binary sensors into Home Assistant. See the [main component](/components/tellduslive/) for configuration instructions. diff --git a/source/_components/binary_sensor.zha.markdown b/source/_components/binary_sensor.zha.markdown deleted file mode 100644 index 94910f8892a..00000000000 --- a/source/_components/binary_sensor.zha.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "Zigbee Home Automation Binary Sensor" -description: "Instructions on how to setup Zigbee Home Automation binary sensors within Home Assistant." -date: 2017-02-22 00:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: zigbee.png -ha_category: Binary Sensor -ha_iot_class: "Local Polling" ---- - -To get your Zigbee binary sensors working with Home Assistant, follow the instructions for the general [Zigbee Home Automation component](/components/zha/). diff --git a/source/_components/calendar.caldav.markdown b/source/_components/calendar.caldav.markdown index 8f27342be6c..01fe75d358d 100644 --- a/source/_components/calendar.caldav.markdown +++ b/source/_components/calendar.caldav.markdown @@ -180,7 +180,7 @@ calendar: alias: worktime wakeup trigger: platform: time - at: 06:40:00 + at: '06:40:00' action: - service: media_player.media_play entity_id: media_player.bedroom diff --git a/source/_components/camera.uvc.markdown b/source/_components/camera.uvc.markdown index a0f8ef896c1..63d773f0915 100644 --- a/source/_components/camera.uvc.markdown +++ b/source/_components/camera.uvc.markdown @@ -34,7 +34,6 @@ camera: - platform: uvc nvr: IP_ADDRESS key: API_KEY - ssl: USE_SSL ``` {% configuration %} diff --git a/source/_components/climate.ecobee.markdown b/source/_components/climate.ecobee.markdown deleted file mode 100644 index 99ff2b9b892..00000000000 --- a/source/_components/climate.ecobee.markdown +++ /dev/null @@ -1,291 +0,0 @@ ---- -layout: page -title: "Ecobee Thermostat" -description: "Instructions on how to setup the Ecobee thermostats within Home Assistant." -date: 2016-08-26 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: ecobee.png -ha_category: Climate -ha_release: 0.9 -ha_iot_class: "Cloud Push" ---- - -

-To get your Ecobee thermostats working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/). -

- -## {% linkable_title Concepts %} - -The Ecobee Thermostat supports the following key concepts. - -The _target temperature_ is the temperature that the device attempts -to achieve. The target temperature is either determined by the -currently active climate or it may be overridden by a hold. When the -thermostat is not in auto mode, there is a single target -temperature. When the thermostat is in auto operation mode, there is a -pair of target temperatures: the lower target temperature determines -the lowest desired temperature, while the higher target temperature -determines the highest desired temperature (the thermostat will switch -between heating and cooling to keep the temperature within these -limits). - -A _climate_ is a predefined or user-defined set of states that the -thermostat aims to achieve. The ecobee thermostat provides three predefined -climates: Home, Away, and Sleep. The user can define additional climates. - -A _hold_ is an override of the target temperature defined in the -currently active climate. The temperature targeted in the hold mode may be -explicitly set (temperature hold), it may be derived from a reference -climate (home, away, sleep, etc.), or it may be derived from a vacation -defined by the thermostat. All holds are temporary. Temperature and -climate holds expire when the thermostat transitions to the next climate -defined in its program. A vacation hold starts at the beginning of the -defined vacation period, and expires when the vacation period ends. - -When in _away mode_, the target temperature is permanently overridden by -the target temperature defined for the away climate. The away mode is a -simple way to emulate a vacation mode. - -The _operation mode_ of the device is the currently active operational -modes that the Ecobee thermostat provides: heat, auxHeatOnly, cool, -auto, and off. - - -## {% linkable_title Attributes %} - -The following attributes are provided by the Ecobee Thermostat: -`name`, `temperature_unit`, `current_temperature`, `target_temperature`, -`target_temperature_low`, `target_temperature_high`, `desired_fan_mode`, -`fan`, `current_hold_mode`, `current_operation`, `operation_list`, -`operation_mode`, `mode`, `fan_min_on_time`, `device_state_attributes`, -`is_away_mode_on`, `vacation`, `climate_list`, `aux_heat`. -The attributes `min_temp` and `max_temp` are meaningless constant values. - - -### {% linkable_title Attribute `name` %} - -Returns the name of the Ecobee Thermostat. - -| Attribute type | Description | -| ---------------| ----------- | -| String | Name of the Ecobee Thermostat - -### {% linkable_title Attribute `temperature_unit` %} - -Returns the unit of measurement used for temperature by the thermostat. - -| Attribute type | Description | -| ---------------| ----------- | -| String | Name of the temperature unit - -### {% linkable_title Attribute `current_temperature` %} - -Returns the current temperature measured by the thermostat. - -| Attribute type | Description | -| ---------------| ----------- | -| Integer | Currently measured temperature - -### {% linkable_title Attribute `target_temperature` %} - -Returns the target temperature of the thermostat, when the thermostat is -not in auto operation mode. - -| Attribute type | Description | -| ---------------| ----------- | -| Integer | Target temperature - -### {% linkable_title Attribute `target_temperature_low` %} - -Returns the desired heating temperature set in the thermostat when in -auto operation mode. - -| Attribute type | Description | -| ---------------| ----------- | -| Integer | Target temperature - -### {% linkable_title Attribute `target_temperature_high` %} - -Returns the desired cooling temperature set in the thermostat when in -auto operation mode. - -| Attribute type | Description | -| ---------------| ----------- | -| Integer | Target temperature - -### {% linkable_title Attribute `desired_fan_mode` %} - -Returns the desired fan mode of the current operation. - -| Attribute type | Description | -| ---------------| ----------- | -| String | 'on', 'off' - -### {% linkable_title Attribute `fan` %} - -Returns the current fan state. - -| Attribute type | Description | -| ---------------| ----------- | -| String | 'on', 'off' - -### {% linkable_title Attribute `current_hold_mode` %} - -Returns the current temperature hold, if any. - -| Attribute type | Description | -| ---------------| ----------- | -| String | 'temp', 'vacation', 'home', 'away', etc., None - -### {% linkable_title Attribute `current_operation` %} - -Returns the current operation of the thermostat. - -| Attribute type | Description | -| ---------------| ----------- | -| String | 'auto', 'cool', 'heat', 'off' - -### {% linkable_title Attribute `operation_list` %} - -Returns the list of available operation modes. - -| Attribute type | Description | -| ---------------| ----------- | -| List of String | Available operation modes - -### {% linkable_title Attribute `operation_mode` %} - -Returns the current operation mode of the thermostat. - -| Attribute type | Description | -| ---------------| ----------- | -| String | Currently active operation mode - -### {% linkable_title Attribute `mode` %} - -Returns the climate currently active on the thermostat. The mode -is returned as the user-visible name (rather than the internally used name). - -### {% linkable_title Attribute `fan_min_on_time` %} - -Returns the current fan minimum on time. - -| Attribute type | Description | -| ---------------| ----------- | -| Integer | Current fan minimum on time in minutes - -### {% linkable_title Attribute `is_away_mode_on` %} - -Returns whether the thermostat is in away mode (see the corresponding -service for more detail). - -### {% linkable_title Attribute `actual humidity` %} - -Returns the humidity as measured by the thermostat. - -| Attribute type | Description | -| ---------------| ----------- | -| Integer | Current humidity - -### {% linkable_title Attribute `vacation` %} - -Returns the currently active vacation or `None`. - -| Attribute type | Description | -| ---------------| ----------- | -| String | Name of currently active vacation | - -### {% linkable_title Attribute `climate_list` %} - -Returns the list of climates defined in the thermostat. - -### {% linkable_title Attribute `aux_heat` %} - -Returns the current auxiliary heat state. - -| Attribute type | Description | -| ---------------| ----------- | -| String | 'on', 'off' - -## {% linkable_title Services %} - -The following services are provided by the Ecobee Thermostat: -`set_away_mode`, `set_hold_mode`, `set_temperature`, `set_operation_mode`, -`fan_min_on_time`, `resume_program`. -The services `set_aux_heat`, `set_humidity`, `set_fan_mode`, and -`set_swing_mode` offered by the [Climate component](/components/climate/) -are not implemented for this thermostat. - - - -### {% linkable_title Service `set_away_mode` %} - -Turns the away mode on or off for the thermostat. - -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. -| `away_mode` | no | 'on' or 'off' - - -### {% linkable_title Service `set_hold_mode` %} - -Puts the thermostat into the given hold mode. For 'home', 'away', 'sleep', -and any other hold based on a reference climate, the -target temperature is taken from the reference climate. -For 'temp', the current temperature is taken as the target temperature. -When None is provided as parameter, the hold_mode is turned off. -It is not possible to set a vacation hold; such hold has to be -defined on the thermostat directly. However, a vacation hold can be -canceled. - -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. -| `hold_mode` | no | `temp`, `home`, `away`, `sleep`, `None`, `smart1`, `smart2`, etc. - -NOTE: If you create custom hold modes (also known as "Comfort Settings") on your ecobee.com dashboard, their hold_modes are `smart1`, `smart2`, `smart3`, etc. The number for each custom mode should match the mode's icon on your ecobee.com dashboard. Also note that the mode numbers/icons in the ecobee mobile app *may not match* the numbers/icons from the ecobee.com web dashboard. The ones on the website are the ones you shoud use to determine the correct `smartX` hold_mode IDs. - -### {% linkable_title Service `set_temperature` %} - -Puts the thermostat into a temporary hold at the given temperature. - -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. -| `target_temp_low` | no | Desired heating target temperature (when in auto mode) -| `target_temp_high` | no | Desired cooling target temperature (when in auto mode) -| `temperature` | no | Desired target temperature (when not in auto mode) - -Only the target temperatures relevant for the current operation mode need to -be provided. - -### {% linkable_title Service `set_operation_mode` %} - -Sets the current operation mode of the thermostat. - -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. -| `operation_mode` | no | 'auto', 'auxHeatOnly', 'cool', 'heat', 'off' - -### {% linkable_title Service `fan_min_on_time` %} - -Sets the fan minimum on time. - -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. -| `fan_min_on_time` | no | Desired fan minimum on time - -### {% linkable_title Service `resume_program` %} - -Resumes the currently active schedule. - -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. -| `resume_all` | no | true or false diff --git a/source/_components/climate.fritzbox.markdown b/source/_components/climate.fritzbox.markdown deleted file mode 100644 index 81b0533ed93..00000000000 --- a/source/_components/climate.fritzbox.markdown +++ /dev/null @@ -1,32 +0,0 @@ ---- -layout: page -title: "Fritzbox Thermostat" -description: "Instructions on how to integrate the AVM Fritzbox thermostat." -date: 2017-11-12 17:10 -sidebar: true -comments: false -sharing: true -footer: true -logo: avm.png -ha_category: Climate -ha_release: 0.68 -ha_iot_class: "Local Polling" ---- - -

-To get AVM fritzbox thermostat follow the instructions for the general [Fritzbox](/components/fritzbox/). -

- -### {% linkable_title Attributes %} - -The are several attributes that can be useful for automations and templates. - -| Attribute | Description | -| --------- | ----------- | -| `device_locked` | The state of the key lock at the device. -| `locked` | The state of the lock for configuring the device via the app or the Fritzbox web interface. -| `low_battery` | The low battery state indication. -| `battery_level` | The battery level (only available since Fritz!OS 7). -| `holiday_mode` | The state of the holiday mode (only available since Fritz!OS 7). -| `summer_mode` | The state of the summer mode (only available since Fritz!OS 7). -| `window_open` | The state of the window open detection (only available since Fritz!OS 7). diff --git a/source/_components/climate.maxcube.markdown b/source/_components/climate.maxcube.markdown deleted file mode 100644 index 0b918cf1033..00000000000 --- a/source/_components/climate.maxcube.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -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 -comments: false -sharing: true -footer: true -logo: maxcube.png -ha_category: Climate -ha_release: "0.40" -ha_iot_class: "Local Polling" ---- - -See instructions at the [main component](/components/maxcube/). diff --git a/source/_components/coinbase.markdown b/source/_components/coinbase.markdown index 1b8211a9578..226652d8d6a 100644 --- a/source/_components/coinbase.markdown +++ b/source/_components/coinbase.markdown @@ -8,14 +8,18 @@ comments: false sharing: true footer: true logo: coinbase.png -ha_category: Finance +ha_category: + - Finance + - Sensor ha_release: 0.61 ha_iot_class: "Cloud Polling" +redirect_from: + - /components/sensor.coinbase/ --- The `coinbase` component lets you access account balances and exchange rates from [coinbase](https://coinbase.com). -You will need to obtain an API key from coinbase's [developer site](https://www.coinbase.com/settings/api) to use this component. You need to give read access to `wallet:accounts` in order for the component to access relevant data. +You will need to obtain an API key from coinbase's [developer site](https://www.coinbase.com/settings/api) to use this component. You need to give read access to `wallet:accounts` in order for the component to access relevant data. ## {% linkable_title Configuration %} diff --git a/source/_components/comfoconnect.markdown b/source/_components/comfoconnect.markdown index 6494ed5c8a6..b2c3660ec80 100644 --- a/source/_components/comfoconnect.markdown +++ b/source/_components/comfoconnect.markdown @@ -8,8 +8,13 @@ comments: false sharing: true footer: true logo: zehnder.png -ha_category: Hub +ha_category: + - Fan + - Sensor ha_release: "0.48" +redirect_from: + - /components/fan.comfoconnect/ + - /components/sensor.comfoconnect/ --- 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) @@ -25,7 +30,7 @@ To set it up, add the following information to your `configuration.yaml` file: ```yaml comfoconnect: - host: 192.168.1.213 + host: IP_ADDRESS ``` {% configuration %} diff --git a/source/_components/cover.isy994.markdown b/source/_components/cover.isy994.markdown deleted file mode 100644 index 929afac31d1..00000000000 --- a/source/_components/cover.isy994.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "ISY994 Cover" -description: "Instructions on how to integrate ISY994 covers into Home Assistant." -date: 2016-09-03 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: universal_devices.png -ha_category: Cover -ha_iot_class: "Local Push" ---- - -The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) cover from within Home Assistant. - -They will be automatically discovered if the `isy994` component is loaded. diff --git a/source/_components/cover.lutron.markdown b/source/_components/cover.lutron.markdown deleted file mode 100644 index ffd2c100b28..00000000000 --- a/source/_components/cover.lutron.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Lutron Cover" -description: "Instructions on how to setup the Lutron shades within Home Assistant." -date: 2018-01-11 20:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Cover -ha_iot_class: "Local Polling" -ha_release: 0.61 ---- - -To get your Lutron roller shades working with Home Assistant, follow the instructions for the general [Lutron component](/components/lutron/). diff --git a/source/_components/cover.lutron_caseta.markdown b/source/_components/cover.lutron_caseta.markdown deleted file mode 100644 index ee64257f1ab..00000000000 --- a/source/_components/cover.lutron_caseta.markdown +++ /dev/null @@ -1,22 +0,0 @@ ---- -layout: page -title: "Lutron Caseta Cover" -description: "Instructions on how to setup the Lutron Caseta covers within Home Assistant." -date: 2017-05-20 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Cover -ha_iot_class: "Local Polling" -ha_release: 0.45 ---- - -To get Lutron Caseta roller and honeycomb shades working with Home Assistant, first follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/). - -After setup, shades will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a shade called 'Living Room Window' will appear in Home Assistant as `cover.living_room_window`. - -For more information on working with shades in Home Assistant, see the [Covers component](/components/cover/). - -Available services: `cover.open_cover`, `cover.close_cover` and `cover.set_cover_position`. Cover `position` ranges from `0` for fully closed to `100` for fully open. \ No newline at end of file diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown index 0c469351f50..0cd7c71de9d 100644 --- a/source/_components/cover.mqtt.markdown +++ b/source/_components/cover.mqtt.markdown @@ -83,7 +83,7 @@ state_closed: position_topic: description: The MQTT topic subscribed to receive cover position messages. If `position_topic` is set `state_topic` is ignored. required: false - type: integer + type: string position_open: description: Number which represents open position. required: false diff --git a/source/_components/cover.tahoma.markdown b/source/_components/cover.tahoma.markdown deleted file mode 100644 index a67537ca112..00000000000 --- a/source/_components/cover.tahoma.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Tahoma Cover" -description: "Instructions on how to integrate Tahoma covers into Home Assistant." -date: 2017-07-18 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: tahoma.png -ha_category: Cover -ha_release: 0.59 ---- - -The `tahoma` cover platform lets you control covers added to your Tahoma Box in Home Assistant. - -Covers will be added automatically. Please refer to the [component](/components/tahoma/) configuration on how to setup Tahoma. diff --git a/source/_components/cover.tellduslive.markdown b/source/_components/cover.tellduslive.markdown deleted file mode 100644 index a988bb1761b..00000000000 --- a/source/_components/cover.tellduslive.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Telldus Live Cover" -description: "Instructions on how to integrate Telldus Live Covers into Home Assistant." -date: 2016-01-17 15:49 -sidebar: true -comments: false -sharing: true -footer: true -logo: telldus.png -ha_category: Cover -featured: false ---- - -Integrates Telldus Live Covers into Home Assistant. See the [main component](/components/tellduslive/) for configuration instructions. - diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown index 05a5b2fb867..1e28695a6bd 100644 --- a/source/_components/device_tracker.snmp.markdown +++ b/source/_components/device_tracker.snmp.markdown @@ -23,23 +23,24 @@ The following OID examples pull the current MAC Address table from a router. Thi | Brand | Device/Firmware | OID | |---|---|---|---| +| Aerohive | AP230 | `1.3.6.1.4.1.26928.1.1.1.2.1.2.1.1` | +| Apple | Airport Express (2nd gen.) 7.6.9 | `1.3.6.1.2.1.3.1.1.2` or `1.3.6.1.2.1.4.22.1.2`| +| Aruba | IAP325 on AOS 6.5.4.8 | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.1` | +| BiPAC | 7800DXL Firmware 2.32e | `1.3.6.1.2.1.17.7.1.2.2.1.1` | +| DD-WRT | unknown version/model | `1.3.6.1.2.1.4.22.1.2` | | 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 | IAP325 on AOS 6.5.4.8 | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.1` | -| 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` | +| pfSense | 2.2.4 | `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` | | 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` | -| DD-WRT | unknown RouterOS version/model | `1.3.6.1.2.1.4.22.1.2` | -| Apple Airport Express (2nd gen.) | 7.6.9 | `1.3.6.1.2.1.3.1.1.2` or `1.3.6.1.2.1.4.22.1.2`| +| Ubiquiti | Edgerouter Lite v1.9.0 | `1.3.6.1.2.1.4.22.1.2` | -To use the SNMP version 1 platform in your installation, add the following to your `configuration.yaml` file: +To use the SNMP version 1 or 2c platform in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry for SNMP version 1 +# Example configuration.yaml entry for SNMP version 1 or 2c device_tracker: - platform: snmp host: 192.168.1.1 diff --git a/source/_components/ecobee.markdown b/source/_components/ecobee.markdown index 7940b41e73c..49441989472 100644 --- a/source/_components/ecobee.markdown +++ b/source/_components/ecobee.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "ecobee" +title: "Ecobee" description: "Instructions for how to integrate Ecobee thermostats and sensors within Home Assistant." date: 2015-11-30 17:54 sidebar: true @@ -8,14 +8,27 @@ comments: false sharing: true footer: true logo: ecobee.png -ha_category: Hub +ha_category: + - Sensor + - Binary Sensor + - Notify + - Climate + - Weather featured: true ha_release: 0.9 ha_iot_class: "Cloud Push" +redirect_from: + - /components/sensor.ecobee/ + - /components/binary_sensor.ecobee/ + - /components/notify.ecobee/ + - /components/climate.ecobee/ + - /components/weather.ecobee/ --- The `ecobee` component lets you control a thermostats and view sensor data from [ecobee](https://ecobee.com) thermostats. +## {% linkable_title Configuration %} + You will need to obtain an API key from ecobee's [developer site](https://www.ecobee.com/developers/) to use this component. To get the key, first you need to register your thermostat which should be done as part of the ecobee installation. Once you have done that perform the following steps. 1. Click on the **Become a developer** link on the [developer site](https://www.ecobee.com/developers/). @@ -24,7 +37,7 @@ You will need to obtain an API key from ecobee's [developer site](https://www.ec 4. Fill in the fields. 5. Click **save**. -Now login to the regular consumer portal, and in the hamburger menu there will be a new option **Developer**. Now we can create the Application to hook up to Home Assistant. +Now login to the regular consumer portal, and in the hamburger menu there will be a new option **Developer**. Now we can create the Application to hook up to Home Assistant. 1. Select the Developer option. 2. Select **Create New**. @@ -33,11 +46,11 @@ Now login to the regular consumer portal, and in the hamburger menu there will b 5. You don't need an Application Icon or Detailed Description. 6. Click **Create**. -Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the **X** to close the Developer section. +Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the **X** to close the Developer section. -The first time you run Home Assistant with this component it will give you a PIN code that you need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by clicking **Add Application** in the **My Apps** section in the sidebar. +The first time you run Home Assistant with this component it will give you a PIN code that you need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by clicking **Add Application** in the **My Apps** section in the sidebar. -The PIN can be found from the Home Assistant portal on the Ecobee card or from the **configurator.ecobee** entity in states in the portal. +The PIN can be found from the Home Assistant portal on the Ecobee card or from the **configurator.ecobee** entity in states in the portal. - If you do not have an ecobee card, you may be using groups with `default_view` that don't show the card. To get around this you can temporarily comment out the `default_view` section or add the `configurator.ecobee` component to your `default_view` and restart Home Assistant. @@ -48,7 +61,7 @@ To set it up, add the following information to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry ecobee: - api_key: YOUR_API_KEY + api_key: YOUR_API_KEY ``` {% configuration %} @@ -69,3 +82,296 @@ hold_temp:

If for whatever reason you delete and re-create your ecobee app at ecobee.com such that your developer API key changes, you will need to delete your `/conf/ecobee.conf file`. You will also need to update the `api_key:` in the `configuration.yaml` or `secrets.yaml` file. + +## {% linkable_title Notifications %} + +To get your Ecobee notifications working with Home Assistant, you must first have the main Ecobee component loaded and running. Once you have that configured, you can setup this component to send messages to your Ecobee device. + +To use this notification platform in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +notify: + - name: NOTIFIER_NAME + platform: ecobee +``` + +{% configuration %} +name: + description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`. + required: false + default: "`notify`" + type: string +{% endconfiguration %} + +To use notifications, please see the [getting started with automation page](/getting-started/automation/). + +## {% linkable_title Thermostat %} + +### {% linkable_title Concepts %} + +The Ecobee Thermostat supports the following key concepts. + +The _target temperature_ is the temperature that the device attempts +to achieve. The target temperature is either determined by the +currently active climate or it may be overridden by a hold. When the +thermostat is not in auto mode, there is a single target +temperature. When the thermostat is in auto operation mode, there is a +pair of target temperatures: the lower target temperature determines +the lowest desired temperature, while the higher target temperature +determines the highest desired temperature (the thermostat will switch +between heating and cooling to keep the temperature within these +limits). + +A _climate_ is a predefined or user-defined set of states that the +thermostat aims to achieve. The ecobee thermostat provides three predefined +climates: Home, Away, and Sleep. The user can define additional climates. + +A _hold_ is an override of the target temperature defined in the +currently active climate. The temperature targeted in the hold mode may be +explicitly set (temperature hold), it may be derived from a reference +climate (home, away, sleep, etc.), or it may be derived from a vacation +defined by the thermostat. All holds are temporary. Temperature and +climate holds expire when the thermostat transitions to the next climate +defined in its program. A vacation hold starts at the beginning of the +defined vacation period, and expires when the vacation period ends. + +When in _away mode_, the target temperature is permanently overridden by +the target temperature defined for the away climate. The away mode is a +simple way to emulate a vacation mode. + +The _operation mode_ of the device is the currently active operational +modes that the Ecobee thermostat provides: heat, auxHeatOnly, cool, +auto, and off. + +## {% linkable_title Attributes %} + +The following attributes are provided by the Ecobee Thermostat: +`name`, `temperature_unit`, `current_temperature`, `target_temperature`, +`target_temperature_low`, `target_temperature_high`, `desired_fan_mode`, +`fan`, `current_hold_mode`, `current_operation`, `operation_list`, +`operation_mode`, `mode`, `fan_min_on_time`, `device_state_attributes`, +`is_away_mode_on`, `vacation`, `climate_list`, `aux_heat`. +The attributes `min_temp` and `max_temp` are meaningless constant values. + +### {% linkable_title Attribute `name` %} + +Returns the name of the Ecobee Thermostat. + +| Attribute type | Description | +| ---------------| ----------- | +| String | Name of the Ecobee Thermostat + +### {% linkable_title Attribute `temperature_unit` %} + +Returns the unit of measurement used for temperature by the thermostat. + +| Attribute type | Description | +| ---------------| ----------- | +| String | Name of the temperature unit + +### {% linkable_title Attribute `current_temperature` %} + +Returns the current temperature measured by the thermostat. + +| Attribute type | Description | +| ---------------| ----------- | +| Integer | Currently measured temperature + +### {% linkable_title Attribute `target_temperature` %} + +Returns the target temperature of the thermostat, when the thermostat is +not in auto operation mode. + +| Attribute type | Description | +| ---------------| ----------- | +| Integer | Target temperature + +### {% linkable_title Attribute `target_temperature_low` %} + +Returns the desired heating temperature set in the thermostat when in +auto operation mode. + +| Attribute type | Description | +| ---------------| ----------- | +| Integer | Target temperature + +### {% linkable_title Attribute `target_temperature_high` %} + +Returns the desired cooling temperature set in the thermostat when in +auto operation mode. + +| Attribute type | Description | +| ---------------| ----------- | +| Integer | Target temperature + +### {% linkable_title Attribute `desired_fan_mode` %} + +Returns the desired fan mode of the current operation. + +| Attribute type | Description | +| ---------------| ----------- | +| String | 'on', 'off' + +### {% linkable_title Attribute `fan` %} + +Returns the current fan state. + +| Attribute type | Description | +| ---------------| ----------- | +| String | 'on', 'off' + +### {% linkable_title Attribute `current_hold_mode` %} + +Returns the current temperature hold, if any. + +| Attribute type | Description | +| ---------------| ----------- | +| String | 'temp', 'vacation', 'home', 'away', etc., None + +### {% linkable_title Attribute `current_operation` %} + +Returns the current operation of the thermostat. + +| Attribute type | Description | +| ---------------| ----------- | +| String | 'auto', 'cool', 'heat', 'off' + +### {% linkable_title Attribute `operation_list` %} + +Returns the list of available operation modes. + +| Attribute type | Description | +| ---------------| ----------- | +| List of String | Available operation modes + +### {% linkable_title Attribute `operation_mode` %} + +Returns the current operation mode of the thermostat. + +| Attribute type | Description | +| ---------------| ----------- | +| String | Currently active operation mode + +### {% linkable_title Attribute `mode` %} + +Returns the climate currently active on the thermostat. The mode +is returned as the user-visible name (rather than the internally used name). + +### {% linkable_title Attribute `fan_min_on_time` %} + +Returns the current fan minimum on time. + +| Attribute type | Description | +| ---------------| ----------- | +| Integer | Current fan minimum on time in minutes + +### {% linkable_title Attribute `is_away_mode_on` %} + +Returns whether the thermostat is in away mode (see the corresponding +service for more detail). + +### {% linkable_title Attribute `actual humidity` %} + +Returns the humidity as measured by the thermostat. + +| Attribute type | Description | +| ---------------| ----------- | +| Integer | Current humidity + +### {% linkable_title Attribute `vacation` %} + +Returns the currently active vacation or `None`. + +| Attribute type | Description | +| ---------------| ----------- | +| String | Name of currently active vacation | + +### {% linkable_title Attribute `climate_list` %} + +Returns the list of climates defined in the thermostat. + +### {% linkable_title Attribute `aux_heat` %} + +Returns the current auxiliary heat state. + +| Attribute type | Description | +| ---------------| ----------- | +| String | 'on', 'off' + +## {% linkable_title Services %} + +The following services are provided by the Ecobee Thermostat: +`set_away_mode`, `set_hold_mode`, `set_temperature`, `set_operation_mode`, +`fan_min_on_time`, `resume_program`. +The services `set_aux_heat`, `set_humidity`, `set_fan_mode`, and +`set_swing_mode` offered by the [Climate component](/components/climate/) +are not implemented for this thermostat. + +### {% linkable_title Service `set_away_mode` %} + +Turns the away mode on or off for the thermostat. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. +| `away_mode` | no | 'on' or 'off' + +### {% linkable_title Service `set_hold_mode` %} + +Puts the thermostat into the given hold mode. For 'home', 'away', 'sleep', +and any other hold based on a reference climate, the +target temperature is taken from the reference climate. +For 'temp', the current temperature is taken as the target temperature. +When None is provided as parameter, the hold_mode is turned off. +It is not possible to set a vacation hold; such hold has to be +defined on the thermostat directly. However, a vacation hold can be +canceled. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. +| `hold_mode` | no | `temp`, `home`, `away`, `sleep`, `None`, `smart1`, `smart2`, etc. + +NOTE: If you create custom hold modes (also known as "Comfort Settings") on your ecobee.com dashboard, their hold_modes are `smart1`, `smart2`, `smart3`, etc. The number for each custom mode should match the mode's icon on your ecobee.com dashboard. Also note that the mode numbers/icons in the ecobee mobile app *may not match* the numbers/icons from the ecobee.com web dashboard. The ones on the website are the ones you shoud use to determine the correct `smartX` hold_mode IDs. + +### {% linkable_title Service `set_temperature` %} + +Puts the thermostat into a temporary hold at the given temperature. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. +| `target_temp_low` | no | Desired heating target temperature (when in auto mode) +| `target_temp_high` | no | Desired cooling target temperature (when in auto mode) +| `temperature` | no | Desired target temperature (when not in auto mode) + +Only the target temperatures relevant for the current operation mode need to +be provided. + +### {% linkable_title Service `set_operation_mode` %} + +Sets the current operation mode of the thermostat. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. +| `operation_mode` | no | 'auto', 'auxHeatOnly', 'cool', 'heat', 'off' + +### {% linkable_title Service `fan_min_on_time` %} + +Sets the fan minimum on time. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. +| `fan_min_on_time` | no | Desired fan minimum on time + +### {% linkable_title Service `resume_program` %} + +Resumes the currently active schedule. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all. +| `resume_all` | no | true or false diff --git a/source/_components/enocean.markdown b/source/_components/enocean.markdown index e22c07ec2af..5e49cd1d6fc 100644 --- a/source/_components/enocean.markdown +++ b/source/_components/enocean.markdown @@ -8,9 +8,19 @@ comments: false sharing: true footer: true logo: enocean.png -ha_category: Hub +ha_category: + - Hub + - Binary Sensor + - Sensor + - Light + - Switch ha_release: 0.21 ha_iot_class: "Local Push" +redirect_from: + - /components/binary_sensor.enocean/ + - /components/sensor.enocean/ + - /components/light.enocean/ + - /components/switch.enocean/ --- The [EnOcean](https://en.wikipedia.org/wiki/EnOcean) standard is supported by many different vendors. There are switches and sensors of many different kinds, and typically they employ energy harvesting to get power such that no batteries are necessary. @@ -19,10 +29,10 @@ The `enocean` component adds support for some of these devices. You will need a There is currently support for the following device types within Home Assistant: -- [Binary Sensor](/components/binary_sensor.enocean/) (wall switches) -- [Sensor](/components/sensor.enocean/) (power meters) -- [Light](/components/light.enocean/) (dimmers) -- [Switch](/components/switch.enocean/) +- Binary Sensor (wall switches) +- Sensor (power meters) +- Light (dimmers) +- Switch However, only a few devices have been confirmed to work. These are: @@ -47,3 +57,168 @@ device: required: true type: string {% endconfiguration %} + +## {% linkable_title Binary Sensor %} + +This can typically be one of those batteryless wall switches. +Tested with: + +- Eltako FT55 which uses the EnOcean PTM 215 module +- [TRIO2SYS Wall switches](http://www.trio2sys.fr/index.php/fr/produits-enocean-sans-fil-sans-pile-interoperable/emetteur-sans-fils-sans-pile-interoperable-enocean) which uses the EnOcean PTM210 DB module + +All switches using theses modules are expected to work. Other devices will most likely not work without changing the Home Assistant code. + +## {% linkable_title Configuration %} + +To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +binary_sensor: + - platform: enocean + id: [0x01,0x90,0x84,0x3C] +``` + +{% configuration %} +id: + description: The ID of the device. This is the 4 bytes long number written on the dimmer. + required: true + type: list +name: + description: An identifier for the switch in the frontend. + required: false + type: string + default: EnOcean binary sensor +device_class: + description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend. + required: false + type: device_class +{% endconfiguration %} + +EnOcean binary sensors only generate 'button_pressed' events. The event data has following four fields: + +- **id**: The ID of the device (see configuration). +- **pushed**: `1` for a button press, `0` for a button release. +- **which**: Always `0` when using the single rocket. `0` or `1` when using the dual rocket switch. +- **onoff**: `0` or `1` for either side of the rocket. + +## {% linkable_title Automation example %} + +Sample automation to switch lights on and off: + +```yaml +# Example automation to turn lights on/off on button release +automation: + - alias: hall light switches + trigger: + platform: event + event_type: button_pressed + event_data: + id: [0xYY, 0xYY, 0xYY, 0xYY] + pushed: 0 + action: + service_template: "{% raw %}{% if trigger.event.data.onoff %} light.turn_on {% else %} light.turn_off {%endif %}{% endraw %}" + data_template: + entity_id: "{% raw %}{% if trigger.event.data.which == 1 %} light.hall_left {% else %} light.hall_right {%endif %}{% endraw %}" +``` + +## {% linkable_title Light %} + +An EnOcean light can take many forms. Currently only one type has been tested: Eltako FUD61 dimmer. + +To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +light: + - platform: enocean + id: [0x01,0x90,0x84,0x3C] + sender_id: [0xFF,0xC6,0xEA,0x04] +``` + +{% configuration %} +id: + description: The ID of the device. This is the 4 bytes long number written on the dimmer. + required: true + type: list +sender_id: + description: The Sender ID of the device. This is a 4 bytes long number. + required: true + type: list +name: + description: An identifier for the Ligh in the frontend. + required: false + default: EnOcean Light + type: string +{% endconfiguration %} + +## {% linkable_title Sensor %} + +The `enocean` sensor platform currently only allows reading out the power measured in a Permundo PSC234 switch. + +To use your EnOcean device, you first have to set up your [EnOcean hub](../enocean) and then add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + - platform: enocean + name: Television + id: [0x01,0x90,0x84,0x3C] +``` + +{% configuration %} +id: + description: The ID of the device. This is a 4 bytes long number. + required: true + type: list +name: + description: An identifier for the switch + required: true + default: EnOcean sensor + type: string +{% endconfiguration %} + +## {% linkable_title Switch %} + +An EnOcean switch can take many forms. Currently, only a few types have been tested: Permundo PSC234 and Nod On SIN-2-1-01. + +To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +switch: + - platform: enocean + id: [0x01,0x90,0x84,0x3C] +``` + +{% configuration %} +id: + description: The ID of the device. This is a 4 bytes long number. + required: true + type: list +name: + description: An identifier for the switch. + required: false + default: EnOcean Switch + type: string +channel: + description: The number of the channel (typically 0 or 1) for the output channel to switch. + required: false + default: 0 + type: integer +{% endconfiguration %} + +```yaml +# Example entries for a switch with 2 outputs (channels), e.g., the Nod On SIN-2-1-01 +switch nodon01_0: + - platform: enocean + id: [0x05,0x04,0x03,0x02] + name: enocean_nodon01_0 + channel: 0 + +switch nodon01_1: + - platform: enocean + id: [0x05,0x04,0x03,0x02] + name: enocean_nodon01_1 + channel: 1 +``` diff --git a/source/_components/fan.comfoconnect.markdown b/source/_components/fan.comfoconnect.markdown deleted file mode 100644 index f1ac6f944f3..00000000000 --- a/source/_components/fan.comfoconnect.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Zehnder ComfoAir Q Ventilation fans" -description: "Instructions on how to integrate Zehnder ComfoAir Q350/450/600 fans into Home Assistant." -date: 2017-06-28 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: zehnder.png -ha_category: Fan -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/fan.isy994.markdown b/source/_components/fan.isy994.markdown deleted file mode 100644 index 4c47e76fc40..00000000000 --- a/source/_components/fan.isy994.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "ISY994 Fan" -description: "Instructions on how to integrate ISY994 fans into Home Assistant." -date: 2016-09-03 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: universal_devices.png -ha_category: Fan -ha_iot_class: "Local Push" ---- - -The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) fan from within Home Assistant. - -They will be automatically discovered if the `isy994` component is loaded. diff --git a/source/_components/fan.zha.markdown b/source/_components/fan.zha.markdown deleted file mode 100644 index 60d316e5926..00000000000 --- a/source/_components/fan.zha.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Zigbee Home Automation Fan" -description: "Instructions how to setup Zigbee Home Automation fans within Home Assistant." -date: 2018-02-10 00:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: zigbee.png -ha_category: Fan -ha_iot_class: "Local Polling" -ha_release: 0.66 ---- - -To get your Zigbee fans working with Home Assistant, follow the instructions for the general [Zigbee Home Automation component](/components/zha/). diff --git a/source/_components/fritzbox.markdown b/source/_components/fritzbox.markdown index e49c19c4245..a3c5ac12eee 100644 --- a/source/_components/fritzbox.markdown +++ b/source/_components/fritzbox.markdown @@ -8,9 +8,16 @@ comments: false sharing: true footer: true logo: avm.png -ha_category: Hub +ha_category: + - Binary Sensor + - Climate + - Switch ha_release: 0.68 ha_iot_class: "Local Polling" +redirect_from: + - /components/binary_sensor.fritzbox/ + - /components/switch.fritzbox/ + - /components/climate.fritzbox/ --- The [AVM](https://en.avm.de) Fritzbox component for Home Assistant allows you to integrate the switch and climate devices. @@ -22,7 +29,6 @@ The [AVM](https://en.avm.de) Fritzbox component for Home Assistant allows you to - [FRITZ!DECT 200](https://en.avm.de/products/fritzdect/fritzdect-200/) - [Eurotronic Comet DECT](https://eurotronic.org/produkte/elektronische-heizkoerperthermostate/sparmatic-comet/) - ## {% linkable_title Setup %} ```yaml @@ -53,3 +59,25 @@ devices: required: true type: string {% endconfiguration %} + +## {% linkable_title Switch & Thermostat %} + +To get AVM Fritzbox switch and thermostat follow the instructions above. + +### {% linkable_title Attributes %} + +The are several attributes that can be useful for automations and templates. + +| Attribute | Description | +| --------- | ----------- | +| `device_locked` | The state of the key lock at the device. +| `locked` | The state of the lock for configuring the device via the app or the Fritzbox web interface. +| `low_battery` | The low battery state indication. +| `battery_level` | The battery level (only available since Fritz!OS 7). +| `holiday_mode` | The state of the holiday mode (only available since Fritz!OS 7). +| `summer_mode` | The state of the summer mode (only available since Fritz!OS 7). +| `window_open` | The state of the window open detection (only available since Fritz!OS 7). +| `temperature_unit` | The unit of the temperature sensor (only available if the device support temperature sensor). +| `temperature` | The current temperature sensor reading (only available if the device supports temperature sensor). +| `total_consumption` | The total power consumption since the beginning of operation (only available if the device supports power meter function). +| `total_consumption_unit` | The unit of the total_consumption (only available if the device supports power meter function). \ No newline at end of file diff --git a/source/_components/frontend.markdown b/source/_components/frontend.markdown index 5edb773e4b7..5c8944c7a74 100644 --- a/source/_components/frontend.markdown +++ b/source/_components/frontend.markdown @@ -77,7 +77,7 @@ Check our [community forums](https://community.home-assistant.io/c/projects/them There are 2 themes-related services: - `frontend.reload_themes`: reloads theme configuration from your `configuration.yaml` file. - - `frontend.set_theme(name)`: sets backend-preferred theme name. + - `frontend.set_theme(name)`: sets backend-preferred theme name. Example in automation: @@ -96,7 +96,7 @@ automation: name: happy ``` -To enable "night mode": +To enable "night mode": ```yaml automation: @@ -104,7 +104,7 @@ automation: initial_state: true trigger: - platform: time - at: '21:00' + at: '21:00:00' action: - service: frontend.set_theme data: diff --git a/source/_components/gpslogger.md b/source/_components/gpslogger.md index a0739c3098b..5d19da193d7 100644 --- a/source/_components/gpslogger.md +++ b/source/_components/gpslogger.md @@ -49,7 +49,7 @@ Right after enabling, the app will take you to the **Log to custom URL** setting The relevant endpoint starts with: `/api/webhook/` and ends with a unique sequence of characters. This is provided by the integrations panel in the configuration screen (configured above). ```text -https://YOUR.DNS.HOSTNAME:PORT/api/webook/WEBHOOK_ID +https://YOUR.DNS.HOSTNAME:PORT/api/webhook/WEBHOOK_ID ``` - Add the above URL (updating YOUR.DNS.HOSTNAME:PORT to your details) into the **URL** field. @@ -60,7 +60,7 @@ https://YOUR.DNS.HOSTNAME:PORT/api/webook/WEBHOOK_ID ```text latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT ``` -- You can change the name of your device name by replacing `&device=%SER` with `&device=DEVICE_NAME`. +- You can change the name of your device name by replacing `&device=%SER` with `&device=%DEVICE_NAME`. - Check that the **HTTP Headers** setting contains ```text Content-Type: application/x-www-form-urlencoded diff --git a/source/_components/isy994.markdown b/source/_components/isy994.markdown index 23452d0b6b7..b9b4781ad88 100644 --- a/source/_components/isy994.markdown +++ b/source/_components/isy994.markdown @@ -8,14 +8,40 @@ comments: false sharing: true footer: true logo: universal_devices.png -ha_category: Hub +ha_category: + - Hub + - Binary Sensor + - Cover + - Fan + - Light + - Lock + - Sensor + - Switch ha_release: 0.28 ha_iot_class: "Local Push" +redirect_from: + - /components/binary_sensor.isy994/ + - /components/cover.isy994/ + - /components/fan.isy994/ + - /components/light.isy994/ + - /components/lock.isy994/ + - /components/sensor.isy994/ + - /components/switch.isy994/ --- The ISY994 is a home automation controller that is capable of controlling Insteon and X10 devices. Some models of the ISY994 can even control Z-Wave devices. The ISY994 controller is manufactured by [Universal Devices](https://www.universal-devices.com/residential/isy994i-series/). +There is currently support for the following device types within Home Assistant: + +- Binary Sensor +- Cover +- Light +- Fan +- Lock +- Sensor +- Switch + ### {% linkable_title Basic Configuration %} Home Assistant is capable of communicating with any binary sensor, cover, fan, light, lock, sensor and switch that is configured on the controller. Using the programs on the controller, custom binary sensors, cover, fan, lock, and switches can also be created. diff --git a/source/_components/light.enocean.markdown b/source/_components/light.enocean.markdown deleted file mode 100644 index 1933e8f4390..00000000000 --- a/source/_components/light.enocean.markdown +++ /dev/null @@ -1,43 +0,0 @@ ---- -layout: page -title: "EnOcean Light" -description: "Instructions on how to set up EnOcean lights within Home Assistant." -date: 2016-05-25 23:49 -sidebar: true -comments: false -sharing: true -footer: true -logo: enocean.png -ha_category: Light -ha_release: 0.21 -ha_iot_class: "Local Push" ---- - -An EnOcean light can take many forms. Currently only one type has been tested: Eltako FUD61 dimmer. - - -To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -light: - - platform: enocean - id: [0x01,0x90,0x84,0x3C] - sender_id: [0xFF,0xC6,0xEA,0x04] -``` - -{% configuration %} -id: - description: The ID of the device. This is the 4 bytes long number written on the dimmer. - required: true - type: list -sender_id: - description: The Sender ID of the device. This is a 4 bytes long number. - required: true - type: list -name: - description: An identifier for the Ligh in the frontend. - required: false - default: EnOcean Light - type: string -{% endconfiguration %} diff --git a/source/_components/light.flux_led.markdown b/source/_components/light.flux_led.markdown index 33efa06d021..72c02ef8c43 100644 --- a/source/_components/light.flux_led.markdown +++ b/source/_components/light.flux_led.markdown @@ -67,7 +67,7 @@ devices: {% endconfiguration %}

-Depending on your controller or bulb type, there are two ways to configure brightness. +Depending on your controller or bulb type, there are two ways to configure brightness. The component defaults to rgbw. If your device has a separate white channel, you do not need to specify anything else; changing the white value will adjust the brightness of white channel keeping rgb color constant. However, if your device does not have a separate white channel, you will need to set the mode to rgb. In this mode, the device will keep the same color, and adjust the rgb values to dim or brighten the color.

@@ -98,7 +98,7 @@ light: automation: alias: random_flux_living_room_lamp trigger: - platform: time + platform: time_pattern seconds: '/45' action: service: light.turn_on diff --git a/source/_components/light.isy994.markdown b/source/_components/light.isy994.markdown deleted file mode 100644 index 6c03413c8b0..00000000000 --- a/source/_components/light.isy994.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "ISY994 Light" -description: "Instructions on how to integrate ISY994 lights into Home Assistant." -date: 2016-09-03 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: universal_devices.png -ha_category: Light -ha_iot_class: "Local Push" ---- - -The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) light from within Home Assistant. - -They will be automatically discovered if the `isy994` component is loaded. diff --git a/source/_components/light.lightwave.markdown b/source/_components/light.lightwave.markdown deleted file mode 100644 index 234a04d8273..00000000000 --- a/source/_components/light.lightwave.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: page -title: "Lightwave Light" -description: "Instructions on how to integrate Lightwave lights with Home Assistant." -date: 2018-12-05 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lightwave.png -ha_category: Light -ha_release: 0.84 -ha_iot_class: "Assumed State" ---- -The `lightwave` light platform integrates your Lightwave lights into Home Assistant. -

-Configuration details for the Lightwave platform can be found on the main [Lightwave component](/components/lightwave/) page. -

\ No newline at end of file diff --git a/source/_components/light.litejet.markdown b/source/_components/light.litejet.markdown deleted file mode 100644 index fedc9fa2bec..00000000000 --- a/source/_components/light.litejet.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "LiteJet Light" -description: "Instructions on how to setup the LiteJet lights within Home Assistant." -date: 2016-10-26 13:00 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Light -ha_release: 0.32 -ha_iot_class: "Local Polling" ---- - -To get your LiteJet lights working with Home Assistant, follow the instructions for the general [LiteJet component](/components/litejet/). diff --git a/source/_components/light.lutron.markdown b/source/_components/light.lutron.markdown deleted file mode 100644 index 9e380e8d7ce..00000000000 --- a/source/_components/light.lutron.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "Lutron Light" -description: "Instructions on how to setup the Lutron lights within Home Assistant." -date: 2017-04-30 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Light -ha_iot_class: "Local Polling" ---- - -To get your Lutron lights working with Home Assistant, follow the instructions for the general [Lutron component](/components/lutron/). diff --git a/source/_components/light.lutron_caseta.markdown b/source/_components/light.lutron_caseta.markdown deleted file mode 100644 index 4c61accdc60..00000000000 --- a/source/_components/light.lutron_caseta.markdown +++ /dev/null @@ -1,23 +0,0 @@ ---- -layout: page -title: "Lutron Caseta Light" -description: "Instructions on how to setup the Lutron Caseta lights within Home Assistant." -date: 2017-04-30 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Light -ha_iot_class: "Local Polling" ---- - -To get Lutron Caseta lights working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/). - -After setup, dimmable lights including wall and plug-in dimmers will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a light called 'Bedroom Lamp' will appear in Home Assistant as `light.bedroom_lamp`. - -For non-dimmable lights or switched loads, see [Lutron Caseta Switch](/components/switch.lutron_caseta/). - -For more information on working with lights in Home Assistant, see the [Lights component](/components/light/). - -Available services: `light.turn_on`, `light.turn_off` and `light.toggle`. The `light.turn_on` service supports attributes `brightness` and `brightness_pct`. \ No newline at end of file diff --git a/source/_components/light.tellduslive.markdown b/source/_components/light.tellduslive.markdown deleted file mode 100644 index 5a923d1566a..00000000000 --- a/source/_components/light.tellduslive.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Telldus Live Light" -description: "Instructions on how to integrate Telldus Live Lights into Home Assistant." -date: 2016-01-17 15:49 -sidebar: true -comments: false -sharing: true -footer: true -logo: telldus.png -ha_category: Light -featured: false ---- - -Integrates Telldus Live Lights into Home Assistant. See the [main component](/components/tellduslive/) for configuration instructions. - diff --git a/source/_components/light.zha.markdown b/source/_components/light.zha.markdown deleted file mode 100644 index 0285626c619..00000000000 --- a/source/_components/light.zha.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "Zigbee Home Automation Light" -description: "Instructions on how to setup Zigbee Home Automation lights within Home Assistant." -date: 2017-02-22 00:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: zigbee.png -ha_category: Light -ha_iot_class: "Local Polling" ---- - -To get your Zigbee lights working with Home Assistant, follow the instructions for the general [Zigbee Home Automation component](/components/zha/). diff --git a/source/_components/lightwave.markdown b/source/_components/lightwave.markdown index 84c10c35a41..72b38afdaf4 100644 --- a/source/_components/lightwave.markdown +++ b/source/_components/lightwave.markdown @@ -8,13 +8,22 @@ comments: false sharing: true footer: true logo: lightwave.png -ha_category: Hub +ha_category: + - Hub + - Light + - Switch ha_release: 0.84 ha_iot_class: "Assumed State" +redirect_from: + - /components/light.lightwave/ + - /components/switch.lightwave/ --- -The `lightwave` component links Home Assistant with your Lightwave WiFi link for controlling Lightwave lights and switches. + +The `lightwave` component links Home Assistant with your Lightwave WiFi link for controlling Lightwave lights and switches. + This component uses the official API published by Lightwave on their website [https://api.lightwaverf.com/](https://api.lightwaverf.com/). To add your Lightwave devices into your Home Assistant installation, add the following to your `configuration.yaml` file: + ```yaml # Example configuration.yaml entry lightwave: @@ -45,5 +54,6 @@ Each `switch` or `light` requires an `id` and a `name`. The `id` takes the form The first use of a light or switch will try to register with your Lightwave WiFi Link hub. If the hub has not been registered a message on your hub will be displayed asking you to pair the device. You have 12 seconds to push the button on your hub to accept this. Once done, you should be able to control your lights and switches via Home Assistant. This only needs to be done if the hub has not been registered. The Lightwave Home Assistant component currently supports the following Lightwave devices: + - Lightwave lights - Lightwave switches \ No newline at end of file diff --git a/source/_components/litejet.markdown b/source/_components/litejet.markdown index ae6b94a24a9..0aec4126924 100644 --- a/source/_components/litejet.markdown +++ b/source/_components/litejet.markdown @@ -7,9 +7,16 @@ sidebar: true comments: false sharing: true footer: true -ha_category: Hub +ha_category: + - Light + - Scene + - Switch ha_iot_class: "Local Push" ha_release: 0.32 +redirect_from: + - /components/light.litejet/ + - /components/scene.litejet/ + - /components/switch.litejet/ --- LiteJet is a centralized lighting system that predates most home automation technology. All lights and wall switches are wired to a central panel. This central panel has a serial port interface that allows a computer to control the system via LiteJet's third party protocol. diff --git a/source/_components/lock.isy994.markdown b/source/_components/lock.isy994.markdown deleted file mode 100644 index b019662a68c..00000000000 --- a/source/_components/lock.isy994.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "ISY994 Lock" -description: "Instructions on how to integrate ISY994 locks into Home Assistant." -date: 2016-09-03 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: universal_devices.png -ha_category: Lock -ha_iot_class: "Local Push" ---- - -The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) lock from within Home Assistant. - -They will be automatically discovered if the `isy994` component is loaded. diff --git a/source/_components/lutron.markdown b/source/_components/lutron.markdown index ced06e77a34..c8e8be66113 100644 --- a/source/_components/lutron.markdown +++ b/source/_components/lutron.markdown @@ -8,15 +8,25 @@ comments: false sharing: true footer: true logo: lutron.png -ha_category: Hub +ha_category: + - Hub + - Cover + - Light + - Scene + - Switch featured: false ha_release: 0.37 ha_iot_class: "Local Polling" +redirect_from: + - /components/cover.lutron/ + - /components/light.lutron/ + - /components/scene.lutron/ + - /components/switch.lutron/ --- [Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The `lutron` component in Home Assistant is responsible for communicating with the main hub for these systems. -Presently, there's only support for communicating with the [RadioRA 2](http://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/RadioRA2/Overview.aspx) Main Repeater and only handle light switches and dimmers. +Presently, there's only support for communicating with the [RadioRA 2](http://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/RadioRA2/Overview.aspx) Main Repeater and only handle light switches, dimmers, and seeTouch keypad scenes. ## {% linkable_title Configuration %} @@ -62,3 +72,11 @@ The `action` attribute varies depending on the button type. For raise/lower buttons (dimmer buttons, shade controls, etc.) there will be two values, `pressed` and `released`, fired when the button is pressed and when it's released, respectively. For single-action buttons (scene selection, etc.), `action` will be `single`, and there will only be one event fired. This is a limitation of the Lutron controller which doesn't give Home Assistant any way of knowing when a single-action button is released. + +## {% linkable_title Scene %} + +This component uses keypad programming to identify scenes. Currently, it only works with SeeTouch keypads. +The Lutron scene platform allows you to control scenes programmed into your SeeTouch keypads. + +After setup, scenes will appear in Home Assistant using the area, keypad and button name. + diff --git a/source/_components/lutron_caseta.markdown b/source/_components/lutron_caseta.markdown index 64fc354a4f3..2889bc32526 100644 --- a/source/_components/lutron_caseta.markdown +++ b/source/_components/lutron_caseta.markdown @@ -8,10 +8,20 @@ comments: false sharing: true footer: true logo: lutron.png -ha_category: Hub +ha_category: + - Hub + - Cover + - Light + - Scene + - Switch featured: false ha_release: 0.41 ha_iot_class: "Local Polling" +redirect_from: + - /components/cover.lutron_caseta/ + - /components/light.lutron_caseta/ + - /components/scene.lutron_caseta/ + - /components/switch.lutron_caseta/ --- [Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` component in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](http://www.casetawireless.com) product line of dimmers, switches and shades. @@ -20,10 +30,10 @@ This component only supports the [Caseta](http://www.casetawireless.com) line of The currently supported Caseta devices are: -- Wall and plug-in dimmers as Home Assistant [lights](/components/light.lutron_caseta/) -- Wall switches as Home Assistant [switches](/components/switch.lutron_caseta/) -- Scenes as Home Assistant [scenes](/components/scene.lutron_caseta/) -- Lutron shades as Home Assistant [covers](/components/cover.lutron_caseta/) +- Wall and plug-in dimmers as Home Assistant +- Wall switches as Home Assistant +- Scenes as Home Assistant +- Lutron shades as Home Assistant When configured, the `lutron_caseta` component will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Lamp' in a room called 'Bedroom' becomes `light.bedroom_lamp` in Home Assistant. @@ -64,3 +74,43 @@ It is recommended to assign a static IP address to your Lutron Smart Bridge. Thi
Use a DHCP reservation on your router to reserve the address or in the PRO model of the Smart Bridge, set the IP address under Network Settings in the Advanced / Integration menu in the mobile app.

+ +To get Lutron Caseta roller, honeycomb shades, lights, scene and switch working with Home Assistant. First follow the instructions for the general Lutron Caseta component above. + +## {% linkable_title Cover %} + +After setup, shades will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a shade called 'Living Room Window' will appear in Home Assistant as `cover.living_room_window`. + +For more information on working with shades in Home Assistant, see the [Covers component](/components/cover/). + +Available services: `cover.open_cover`, `cover.close_cover` and `cover.set_cover_position`. Cover `position` ranges from `0` for fully closed to `100` for fully open. + +## {% linkable_title Light %} + +After setup, dimmable lights including wall and plug-in dimmers will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a light called 'Bedroom Lamp' will appear in Home Assistant as `light.bedroom_lamp`. + +For non-dimmable lights or switched loads, see the switch section on this page. + +For more information on working with lights in Home Assistant, see the [Lights component](/components/light/). + +Available services: `light.turn_on`, `light.turn_off` and `light.toggle`. The `light.turn_on` service supports attributes `brightness` and `brightness_pct`. + +## {% linkable_title Scene %} + +The Lutron Caseta scene platform allows you to control your Smart Bridge Scenes that are created in the Lutron mobile app. + +After setup, scenes will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a scene called 'Entertain' will appear in Home Assistant as `scene.entertain`. + +For more information on working with scenes in Home Assistant, see the [Scenes component](/components/scene/). + +Available services: `scene.turn_on`. + +## {% linkable_title Switch %} + +After setup, switches will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a light switch called 'Master Bathroom Vanity' will appear in Home Assistant as `switch.master_bathroom_vanity`. + +For dimmable lights including wall and plug-in dimmers, see the light section on this page. + +For more information on working with switches in Home Assistant, see the [Switches component](/components/switch/). + +Available services: `switch.turn_on` and `switch.turn_off`. \ No newline at end of file diff --git a/source/_components/maxcube.markdown b/source/_components/maxcube.markdown index 223d962f68f..a95d1ce13bc 100644 --- a/source/_components/maxcube.markdown +++ b/source/_components/maxcube.markdown @@ -8,18 +8,30 @@ comments: false sharing: true footer: true logo: maxcube.png -ha_category: Climate +ha_category: + - Climate + - Binary Sensor ha_release: "0.40" ha_iot_class: "Local Polling" +redirect_from: + - /components/binary_sensor.maxcube/ + - /components/climate.maxcube/ --- [eQ-3 MAX!](http://www.eq-3.com/products/max.html) integration for Home Assistant allows you to connect eQ-3 MAX! components via the eQ-3 MAX! Cube. The components connects to the eQ-3 MAX! Cube via TCP and automatically makes all supported components available in Home Assistant. The name for each device is created by concatenating the MAX! room and device names. +There is currently support for the following device types within Home Assistant: + +- Binary Sensor +- Climate + Limitations: + - Configuring weekly schedules is not possible. - Implementation is based on the reverse engineered [MAX! protocol](https://github.com/Bouni/max-cube-protocol). Supported Devices: + - MAX! Radiator Thermostat (tested) - MAX! Radiator Thermostat+ - MAX! Window Sensor (tested) diff --git a/source/_components/media_player.nad.markdown b/source/_components/media_player.nad.markdown index 0725043437b..2804632301f 100644 --- a/source/_components/media_player.nad.markdown +++ b/source/_components/media_player.nad.markdown @@ -13,16 +13,23 @@ ha_release: 0.36 ha_iot_class: "Local Polling" --- -The `nad` platform allows you to control a [NAD receiver](http://nadelectronics.com) through RS232 from Home Assistant. +The `nad` platform allows you to control a [NAD receiver](http://nadelectronics.com) through RS232, TCP and Telnet from Home Assistant. To add an NAD receiver to your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yaml entry for RS232 configuration media_player: - platform: nad serial_port: /dev/ttyUSB0 ``` +```yaml +# Example configuration.yaml entry for TCP configuration +media_player: + - platform: nad + type: TCP + host: IP_ADDRESS +``` {% configuration %} type: diff --git a/source/_components/mychevy.markdown b/source/_components/mychevy.markdown index f5574e12b27..6be1ce7dbc5 100644 --- a/source/_components/mychevy.markdown +++ b/source/_components/mychevy.markdown @@ -11,14 +11,17 @@ logo: chevy.png ha_category: Car ha_release: 0.62 ha_iot_class: "Cloud Polling" +redirect_from: + - /components/binary_sensor.mychevy/ + - /components/sensor.mychevy/ --- -The `mychevy` component communicates with the [my.chevrolet](https://my.chevrolet.com) website using the javascript API that the website uses (as of Dec 2018). The mychevy website has been known to be both unstable (interfaces changing somewhat willy nilly) and have substantial outages. So be forwarned in using this component. +The `mychevy` component communicates with the [my.chevrolet](https://my.chevrolet.com) website using the javascript API that the website uses (as of Dec 2018). The MyChevy website has been known to be both unstable (interfaces changing somewhat willy nilly) and has substantial outages. So be forwarned in using this component. This component provides the following platforms: - - Binary sensors: if the car is plugged in - - Sensors: Battery Level, Charge Mode, EST Range, Total Distance Traveled +- Binary sensors: if the car is plugged in +- Sensors: Battery Level, Charge Mode, EST Range, Total Distance Traveled ## {% linkable_title Configuration %} @@ -47,13 +50,12 @@ country: type: string {% endconfiguration %} - ### {% linkable_title Limitations %} The architecture of the GM automotive networking imposes some limitations on the functionality of the component. -The OnStar network link is very slow, and takes 1 - 3 minutes to get information back from the car. As such the mychevy component only polls every 30 minutes to not overwhelms that connection. +The OnStar network link is very slow, and takes 1 - 3 minutes to get information back from the car. As such the `mychevy` component only polls every 30 minutes to not overwhelms that connection. The OnStar network (or more specifically the gateway used by the my.chevrolet website) appears to suffer more than most networks when the car is a) in a garage, and b) it's cold outside (like < 15 degrees F). One of the provided sensors is a status sensor which indicates if we got connectivity with the car on the last polling cycle or not. -The "API" for this is written through using some existing API calls from the Javascript web user interfae. As such, it only currently is known to work if you have a Chevy Bolt EV or a Chevy Volt, and only 1 Chevy car connected to OnStar. Patches for extended support should go to the [https://github.com/sdague/mychevy](https://github.com/sdague/mychevy) project first, then Home Assistant can be extended. +The "API" for this is written through using some existing API calls from the Javascript web user interface. As such, it only currently is known to work if you have a Chevy Bolt EV or a Chevy Volt, and only 1 Chevy car connected to OnStar. Patches for extended support should go to the [https://github.com/sdague/mychevy](https://github.com/sdague/mychevy) project first, then Home Assistant can be extended. diff --git a/source/_components/nest.markdown b/source/_components/nest.markdown index 1be1081a97f..60a2a1e0824 100644 --- a/source/_components/nest.markdown +++ b/source/_components/nest.markdown @@ -9,14 +9,10 @@ sharing: true footer: true logo: nest.png ha_category: Hub -featured: false +featured: true ha_iot_class: "Cloud Push" --- -

-Nest is [no longer accepting new developer accounts](/blog/2019/01/24/nest-cannot-access-data/). If you don't have an account already, you will not be able to sign up and access your own data. -

- The Nest component is the main component to integrate all [Nest](https://nest.com/) related platforms. To connect Nest, you will have to [sign up for a developer account](https://developers.nest.com/products) and get a `client_id` and `client_secret`. ### {% linkable_title Setting up developer account %} diff --git a/source/_components/notify.ecobee.markdown b/source/_components/notify.ecobee.markdown deleted file mode 100644 index 0dbdf6b8ade..00000000000 --- a/source/_components/notify.ecobee.markdown +++ /dev/null @@ -1,34 +0,0 @@ ---- -layout: page -title: "Ecobee Notify" -description: "Instructions on how to setup the Ecobee notification component within Home Assistant." -date: 2016-05-12 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: ecobee.png -ha_category: Notifications -ha_release: "0.20" ---- - -To get your Ecobee notifications working with Home Assistant, you must first have the main [Ecobee component](/components/ecobee/) loaded and running. Once you have that configured, you can setup this component to send messages to your Ecobee device. - -To use this notification platform in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -notify: - - name: NOTIFIER_NAME - platform: ecobee -``` - -{% configuration %} -name: - description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`. - required: false - default: "`notify`" - type: string -{% endconfiguration %} - -To use notifications, please see the [getting started with automation page](/getting-started/automation/). diff --git a/source/_components/openuv.markdown b/source/_components/openuv.markdown index fe70de77001..ede5c5838db 100644 --- a/source/_components/openuv.markdown +++ b/source/_components/openuv.markdown @@ -142,8 +142,7 @@ automation: - alias: Update OpenUV every 30 minutes during the daytime trigger: platform: time_pattern - minutes: "/30" - seconds: 00 + minutes: '/30' condition: condition: and conditions: @@ -164,8 +163,7 @@ automation: - alias: Update OpenUV every hour (24 of 50 calls per day) trigger: platform: time_pattern - minutes: "/60" - seconds: 00 + minutes: '/60' action: service: openuv.update_data ``` diff --git a/source/_components/raspihats.markdown b/source/_components/raspihats.markdown index fbe53d3d90f..08b9a556420 100644 --- a/source/_components/raspihats.markdown +++ b/source/_components/raspihats.markdown @@ -8,9 +8,231 @@ comments: false sharing: true footer: true logo: raspihats.png -ha_category: DIY +ha_category: + - DIY + - Binary Sensor + - Switch ha_release: 0.45 ha_iot_class: "Local Push" +redirect_from: + - /components/binary_sensor.raspihats/ + - /components/switch.raspihats/ --- -The `raspihats` component is the base for all related Raspihats platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages. +The `raspihats` component is the base for all related Raspihats platforms in Home Assistant. There is no setup needed for the component itself. + +## {% linkable_title Binary Sensor %} + +The `raspihats` binary sensor platform allows you to read sensor values ​​using the digital inputs of the [raspihats](http://www.raspihats.com/) boards. + +## {% linkable_title Configuration %} + +To use your `raspihats` boards in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +binary_sensor: + - platform: raspihats + i2c_hats: + - board: DI6acDQ6rly + address: 0x60 + channels: + - index: 0 + name: PIR Office + invert_logic: true + device_class: motion + - index: 1 + name: PIR Bedroom +``` + +{% configuration %} +i2c_hats: + description: An array of used I2C-HATs. + required: false + type: list + keys: + board: + description: The board name either Di16, Di6Rly6, DI16ac or DI6acDQ6rly. + required: true + type: string + address: + description: The board I2C address as HEX value. + required: true + type: string + channels: + description: Array of used digital input channels. + required: true + type: list + keys: + index: + description: Digital input channel index. + required: true + type: integer + name: + description: Friendly name to use for the frontend. + required: true + type: string + invert_logic: + description: Inverts the input logic. + required: false + default: false + type: boolean + device_class: + description: See device classes in [binary_sensor component](/components/binary_sensor/). + required: false + default: "None" + type: string +{% endconfiguration %} + +## {% linkable_title Directions for installing smbus support on Raspberry Pi %} + +Enable I2c interface with the Raspberry Pi configuration utility: + +```bash +# pi user environment: Enable i2c interface +$ sudo raspi-config +``` + +Select `Interfacing options->I2C` choose `` and hit `Enter`, then go to `Finish`. + +Install dependencies for use the `smbus-cffi` module and enable your _homeassistant_ user to join the _i2c_ group: + +```bash +# pi user environment: Install i2c dependencies and utilities +$ sudo apt-get install build-essential libi2c-dev i2c-tools python-dev libffi-dev + +# pi user environment: Add homeassistant user to the i2c group +$ sudo usermod -a -G i2c homeassistant +``` + +### {% linkable_title Check the i2c address of the sensor %} + +After installing `i2c-tools`, a new utility is available to scan the addresses of the connected sensors, so you can see the sensor address: + +```bash +$ /usr/sbin/i2cdetect -y 1 +``` + +It will output a table like this: + +```text + 0 1 2 3 4 5 6 7 8 9 a b c d e f +00: -- -- -- -- -- -- -- -- -- -- -- -- -- +10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +20: -- -- -- 23 -- -- -- -- -- -- -- -- -- -- -- -- +30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +40: 40 -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- +50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +70: -- -- -- -- -- -- -- 77 +``` + +For more details about the `raspihats` add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). + +## {% linkable_title Switch %} + +The `raspihats` switch platform allows you to control the digital outputs of your [Raspihats](http://www.raspihats.com/) boards. + +## {% linkable_title Configuration %} + +To use your Raspihats boards in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +switch: + - platform: raspihats + i2c_hats: + - board: DI6acDQ6rly + address: 0x60 + channels: + - index: 0 + name: Fan Office + invert_logic: true + initial_state: true + - index: 1 + name: Light Office +``` + +{% configuration %} +i2c_hats: + description: An array of used I2C-HATs. + required: false + type: list + keys: + board: + description: The board name. + required: true + type: string + address: + description: The board I2C address as HEX value. + required: true + type: string + channels: + description: An array of used digital input channels. + required: true + type: list + keys: + index: + description: The digital input channel index. + required: true + type: integer + name: + description: The friendly name to use for the frontend. + required: true + type: string + invert_logic: + description: Inverts the input logic. + required: false + default: false + type: boolean + initial_state: + description: "The initial state, can be either `true` or `false`. `none` means no state is forced on the corresponding digital output when this switch is instantiated." + required: false + default: None + type: boolean +{% endconfiguration %} + +## {% linkable_title Directions for installing smbus support on Raspberry Pi %} + +Enable I2c interface with the Raspberry Pi configuration utility: + +```bash +# pi user environment: Enable i2c interface +$ sudo raspi-config +``` + +Select `Interfacing options->I2C` choose `` and hit `Enter`, then go to `Finish`. + +Install dependencies for use the `smbus-cffi` module and enable your _homeassistant_ user to join the _i2c_ group: + +```bash +# pi user environment: Install i2c dependencies and utilities +$ sudo apt-get install build-essential libi2c-dev i2c-tools python-dev libffi-dev + +# pi user environment: Add homeassistant user to the i2c group +$ sudo usermod -a -G i2c homeassistant +``` + +## {% linkable_title Check the i2c address of the sensor %} + +After installing `i2c-tools`, a new utility is available to scan the addresses of the connected sensors, so you can see the sensor address: + +```bash +/usr/sbin/i2cdetect -y 1 +``` + +It will output a table like this: + +```text + 0 1 2 3 4 5 6 7 8 9 a b c d e f +00: -- -- -- -- -- -- -- -- -- -- -- -- -- +10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +20: -- -- -- 23 -- -- -- -- -- -- -- -- -- -- -- -- +30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +40: 40 -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- +50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +70: -- -- -- -- -- -- -- 77 +``` + +For more details about the Raspihats add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). \ No newline at end of file diff --git a/source/_components/scene.litejet.markdown b/source/_components/scene.litejet.markdown deleted file mode 100644 index 511c1cb6fa2..00000000000 --- a/source/_components/scene.litejet.markdown +++ /dev/null @@ -1,14 +0,0 @@ ---- -layout: page -title: "LiteJet Scenes" -description: "Instructions on how to setup LiteJet scenes within Home Assistant." -date: 2016-10-26 16:00 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Scene -ha_release: 0.32 ---- - -To get your LiteJet scenes working with Home Assistant, follow the instructions for the general [LiteJet component](/components/litejet/). diff --git a/source/_components/scene.lutron.markdown b/source/_components/scene.lutron.markdown deleted file mode 100644 index 384bbd92e54..00000000000 --- a/source/_components/scene.lutron.markdown +++ /dev/null @@ -1,21 +0,0 @@ ---- -layout: page -title: "Lutron Scene" -description: "Instructions on how to set up the Lutron scenes within Home Assistant." -date: 2018-10-09 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Scene -ha_iot_class: "Local Polling" -ha_release: 0.85 ---- - -To get your Lutron scenes working with Home Assistant, follow the instructions for the general [Lutron component](/components/lutron/). - -This component uses keypad programming to identify scenes. Currently, it only works with SeeTouch keypads. -The Lutron scene platform allows you to control scenes programmed into your SeeTouch keypads. - -After setup, scenes will appear in Home Assistant using the area, keypad, and button name. diff --git a/source/_components/scene.lutron_caseta.markdown b/source/_components/scene.lutron_caseta.markdown deleted file mode 100644 index 7e07ed485e6..00000000000 --- a/source/_components/scene.lutron_caseta.markdown +++ /dev/null @@ -1,24 +0,0 @@ ---- -layout: page -title: "Lutron Caseta Scene" -description: "Instructions on how to setup Lutron Caseta Scenes within Home Assistant." -date: 2017-07-28 16:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Scene -ha_release: 0.49.2 -ha_iot_class: "Cloud Polling" ---- - -To get Lutron Caseta Scenes working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/). - -The Lutron Caseta scene platform allows you to control your Smart Bridge Scenes that are created in the Lutron mobile app. - -After setup, scenes will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a scene called 'Entertain' will appear in Home Assistant as `scene.entertain`. - -For more information on working with scenes in Home Assistant, see the [Scenes component](/components/scene/). - -Available services: `scene.turn_on`. diff --git a/source/_components/scene.tahoma.markdown b/source/_components/scene.tahoma.markdown deleted file mode 100644 index b5cd1c42940..00000000000 --- a/source/_components/scene.tahoma.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Tahoma Scene" -description: "Instructions on how to integrate Tahoma scenes into Home Assistant." -date: 2018-02-18 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: tahoma.png -ha_category: Scene -ha_release: 0.64 ---- - -The `tahoma` scene platform lets you trigger scenes added to your Tahoma Box in Home Assistant. - -Scenes will be added automatically. Please refer to the [component](/components/tahoma/) configuration on how to setup Tahoma. diff --git a/source/_components/scene.velux.markdown b/source/_components/scene.velux.markdown deleted file mode 100644 index e94928d889a..00000000000 --- a/source/_components/scene.velux.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Velux Scene" -description: "Instructions on how to integrate Velux Scene with Home Assistant." -date: 2017-07-09 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: velux.png -ha_category: Scene -ha_release: 0.49 -ha_iot_class: "Local Polling" ---- - - -The `velux` scene platform allows you to control your [VELUX](http://www.velux.com/) windows. - -The requirement is that you have setup the [VELUX](/components/velux/) component. diff --git a/source/_components/sensor.coinbase.markdown b/source/_components/sensor.coinbase.markdown deleted file mode 100644 index 537b10f9973..00000000000 --- a/source/_components/sensor.coinbase.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "Coinbase Sensor" -description: "Instructions on how to setup Coinbase sensors within Home Assistant." -date: 2017-12-08 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: coinbase.png -ha_category: Finance -ha_release: 0.61 ---- - -To get your coinbase sensors working with Home Assistant, follow the instructions for the general [Coinbase component](/components/coinbase/). diff --git a/source/_components/sensor.comfoconnect.markdown b/source/_components/sensor.comfoconnect.markdown deleted file mode 100644 index 0d9400f5ce1..00000000000 --- a/source/_components/sensor.comfoconnect.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Zehnder ComfoAir Q Ventilation sensors" -description: "Instructions on 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.ecobee.markdown b/source/_components/sensor.ecobee.markdown deleted file mode 100644 index e05a714d371..00000000000 --- a/source/_components/sensor.ecobee.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Ecobee Sensor" -description: "Instructions on how to setup the Ecobee sensors within Home Assistant." -date: 2015-11-30 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: ecobee.png -ha_category: Environment -ha_release: 0.9 -ha_iot_class: "Local Push" ---- - -To get your Ecobee sensors working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/). diff --git a/source/_components/sensor.enocean.markdown b/source/_components/sensor.enocean.markdown deleted file mode 100644 index d75ef524801..00000000000 --- a/source/_components/sensor.enocean.markdown +++ /dev/null @@ -1,39 +0,0 @@ ---- -layout: page -title: "EnOcean Sensor" -description: "Instructions on how to integrate TellStick sensors into Home Assistant." -date: 2016-05-26 01:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: enocean.png -ha_category: Sensor -ha_release: 0.21 -ha_iot_class: "Local Push" ---- - - -The `enocean` sensor platform currently only allows reading out the power measured in a Permundo PSC234 switch. - -To use your EnOcean device, you first have to set up your [EnOcean hub](../enocean) and then add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -sensor: - - platform: enocean - name: Television - id: [0x01,0x90,0x84,0x3C] -``` - -{% configuration %} -id: - description: The ID of the device. This is a 4 bytes long number. - required: true - type: list -name: - description: An identifier for the switch - required: true - default: EnOcean sensor - type: string -{% endconfiguration %} diff --git a/source/_components/sensor.google_travel_time.markdown b/source/_components/sensor.google_travel_time.markdown index 0ccd46ee2fa..8159addfd4c 100644 --- a/source/_components/sensor.google_travel_time.markdown +++ b/source/_components/sensor.google_travel_time.markdown @@ -146,9 +146,8 @@ You can also use the `sensor.google_travel_sensor_update` service to update the alias: "Commute - Update morning commute sensor" initial_state: 'on' trigger: - - platform: time + - platform: time_pattern minutes: '/2' - seconds: 00 condition: - condition: time after: '08:00:00' diff --git a/source/_components/sensor.isy994.markdown b/source/_components/sensor.isy994.markdown deleted file mode 100644 index 0be49fb0e15..00000000000 --- a/source/_components/sensor.isy994.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "ISY994 Sensor" -description: "Instructions on how to integrate ISY994 sensors into Home Assistant." -date: 2016-09-03 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: universal_devices.png -ha_category: Sensor -ha_iot_class: "Local Push" ---- - -The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) sensor from within Home Assistant. - -They will be automatically discovered if the `isy994` component is loaded. diff --git a/source/_components/sensor.mqtt.markdown b/source/_components/sensor.mqtt.markdown index 6275510999d..f065d0dd55d 100644 --- a/source/_components/sensor.mqtt.markdown +++ b/source/_components/sensor.mqtt.markdown @@ -132,7 +132,7 @@ In this section you find some real-life examples of how to use this sensor. ### {% linkable_title JSON attributes topic configuration %} -The example sensor below shows a configuration example which uses a JSON dict: `{"ClientName": , "IP": , "MAC": , "RSSI": , "HostName": , "ConnectedSSID": }` in a separate topic to add extra attributes. It also makes use of the `availability` topic. Attributes can then be extracted in [Templates](/docs/configuration/templating/#attributes). For example, to extract the `ClientName` attribute from the sensor below, use a template similar to: {% raw %}`{{ state_attr('sensor.bs_rssi', 'ClientName') }}`{% endraw %}. +The example sensor below shows a configuration example which uses a JSON dict: `{"ClientName": , "IP": , "MAC": , "RSSI": , "HostName": , "ConnectedSSID": }` in a separate topic `home/sensor1/attributes` to add extra attributes. It also makes use of the `availability` topic. Extra attributes will be displayed in the frontend and can also be extracted in [Templates](/docs/configuration/templating/#attributes). For example, to extract the `ClientName` attribute from the sensor below, use a template similar to: {% raw %}`{{ state_attr('sensor.bs_rssi', 'ClientName') }}`{% endraw %}. {% raw %} ```yaml @@ -146,13 +146,7 @@ sensor: availability_topic: "home/sensor1/status" payload_available: "online" payload_not_available: "offline" - json_attributes: - - ClientName - - IP - - MAC - - RSSI - - HostName - - ConnectedSSID + json_attributes_topic: "home/sensor1/attributes" ``` {% endraw %} diff --git a/source/_components/sensor.mychevy.markdown b/source/_components/sensor.mychevy.markdown deleted file mode 100644 index 33747f5aab1..00000000000 --- a/source/_components/sensor.mychevy.markdown +++ /dev/null @@ -1,22 +0,0 @@ ---- -layout: page -title: "MyChevy Sensor" -description: "Instructions on how to integrate Chevy Bolt sensors car into Home Assistant." -date: 2017-08-28 17:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: chevy.png -ha_category: Car -ha_release: 0.62 -ha_iot_class: "Cloud Polling" ---- - - -The `mychevy` sensor platform allows you to monitor your Chevy Bolt car from within Home Assistant. - -The sensor platform will be automatically configured if the `mychevy` component is configured. - -For configuration instructions, see the [`mychevy` component](/components/mychevy/) documentation. - diff --git a/source/_components/sensor.scrape.markdown b/source/_components/sensor.scrape.markdown index ccc6bebdf5f..86ebfe26ce2 100644 --- a/source/_components/sensor.scrape.markdown +++ b/source/_components/sensor.scrape.markdown @@ -68,7 +68,7 @@ headers: ## {% linkable_title Examples %} -In this section you find some real-life examples of how to use this sensor. There is also a [Jupyter notebook](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/web-scraping.ipynb) available for this example to give you a bit more insight. +In this section you find some real-life examples of how to use this sensor. There is also a [Jupyter notebook](https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/web-scraping.ipynb) available for this example to give you a bit more insight. ### {% linkable_title Home Assistant %} diff --git a/source/_components/sensor.sleepiq.markdown b/source/_components/sensor.sleepiq.markdown deleted file mode 100644 index 616c54e56ba..00000000000 --- a/source/_components/sensor.sleepiq.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "SleepIQ Sensor" -description: "Instructions for how to integrate SleepIQ sensors within Home Assistant." -date: 2016-08-28 8:56 -sidebar: true -comments: false -sharing: true -footer: true -logo: sleepiq.png -ha_category: Health -ha_release: 0.29 -ha_iot_class: "Local Polling" ---- - -To get your SleepIQ sensors working with Home Assistant, follow the instructions for the general [SleepIQ component](/components/sleepiq/). diff --git a/source/_components/sensor.tahoma.markdown b/source/_components/sensor.tahoma.markdown deleted file mode 100644 index d5dbf0530e7..00000000000 --- a/source/_components/sensor.tahoma.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Tahoma Sensor" -description: "Instructions on how to integrate Tahoma sensors into Home Assistant." -date: 2017-07-18 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: tahoma.png -ha_category: Sensor -ha_release: 0.59 ---- - -The `tahoma` sensor platform lets you see sensors added to your Tahoma Box in Home Assistant. - -Sensors will be added automatically. Please refer to the [component](/components/tahoma/) configuration on how to setup Tahoma. diff --git a/source/_components/sensor.tellduslive.markdown b/source/_components/sensor.tellduslive.markdown deleted file mode 100644 index 4e136af4760..00000000000 --- a/source/_components/sensor.tellduslive.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Telldus Live sensor" -description: "Instructions on how to integrate Telldus Live sensors into Home Assistant." -date: 2016-01-17 15:49 -sidebar: true -comments: false -sharing: true -footer: true -logo: telldus.png -ha_category: Sensor -ha_iot_class: "Local Polling" ---- - -Integrates Telldus Live sensors into Home Assistant. See the [main component](/components/tellduslive/) for configuration instructions. - diff --git a/source/_components/sensor.template.markdown b/source/_components/sensor.template.markdown index ab4eb3002e3..238407e63f1 100644 --- a/source/_components/sensor.template.markdown +++ b/source/_components/sensor.template.markdown @@ -286,9 +286,8 @@ sensor: automation: - alias: 'nonsmoker_update' trigger: - - platform: time + - platform: time_pattern minutes: '/5' - seconds: 0 action: - service: homeassistant.update_entity entity_id: sensor.nonsmoker diff --git a/source/_components/sensor.tibber.markdown b/source/_components/sensor.tibber.markdown index 2daf9e4a8b1..8e7e0e946ea 100644 --- a/source/_components/sensor.tibber.markdown +++ b/source/_components/sensor.tibber.markdown @@ -31,10 +31,9 @@ The electricity price can be used to make automations. The sensor has a `max_pri ```yaml - alias: "Electricity price" trigger: - platform: time + platform: time_pattern # Matches every hour at 1 minutes past whole minutes: 1 - seconds: 00 condition: condition: template value_template: '{{ float(states.sensor.electricity_price_hamretunet_10.state) > 0.9 * float(states.sensor.electricity_price_hamretunet_10.attributes.max_price) }}' diff --git a/source/_components/sensor.zha.markdown b/source/_components/sensor.zha.markdown deleted file mode 100644 index 993031476f5..00000000000 --- a/source/_components/sensor.zha.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Zigbee Home Automation Sensor" -description: "Instructions on how to setup Zigbee Home Automation sensors within Home Assistant." -date: 2017-02-22 00:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: zigbee.png -ha_category: Sensor -ha_iot_class: "Local Polling" ---- - -To get your Zigbee sensors working with Home Assistant, follow the instructions for the general [Zigbee Home Automation Component](/components/zha/). - diff --git a/source/_components/sleepiq.markdown b/source/_components/sleepiq.markdown index bb006c23cdc..6baf6193649 100644 --- a/source/_components/sleepiq.markdown +++ b/source/_components/sleepiq.markdown @@ -8,9 +8,15 @@ comments: false sharing: true footer: true logo: sleepiq.png -ha_category: Health +ha_category: + - Health + - Sensor + - Binary Sensor ha_release: 0.29 ha_iot_class: "Local Polling" +redirect_from: + - /components/binary_sensor.sleepiq/ + - /components/sensor.sleepiq/ --- The SleepIQ implementation lets you view sensor data from [SleepIQ by SleepNumber](http://www.sleepnumber.com/sn/en/sleepiq-sleep-tracker). In particular, it lets you see the occupancy and current SleepNumber (ie current firmness) of each side of a SleepNumber bed. @@ -40,4 +46,3 @@ password: required: true type: string {% endconfiguration %} - diff --git a/source/_components/switch.enocean.markdown b/source/_components/switch.enocean.markdown deleted file mode 100644 index f891b939306..00000000000 --- a/source/_components/switch.enocean.markdown +++ /dev/null @@ -1,57 +0,0 @@ ---- -layout: page -title: "EnOcean Switch" -description: "Instructions on how to set up EnOcean switches within Home Assistant." -date: 2016-05-25 23:49 -sidebar: true -comments: false -sharing: true -footer: true -logo: enocean.png -ha_category: Switch -ha_release: 0.21 -ha_iot_class: "Local Push" ---- - -An EnOcean switch can take many forms. Currently, only a few types have been tested: Permundo PSC234 and Nod On SIN-2-1-01. - -To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -switch: - - platform: enocean - id: [0x01,0x90,0x84,0x3C] -``` - -{% configuration %} -id: - description: The ID of the device. This is a 4 bytes long number. - required: true - type: list -name: - description: An identifier for the switch. - required: false - default: EnOcean Switch - type: string -channel: - description: The number of the channel (typically 0 or 1) for the output channel to switch. - required: false - default: 0 - type: integer -{% endconfiguration %} - -```yaml -# Example entries for a switch with 2 outputs (channels), e.g., the Nod On SIN-2-1-01 -switch nodon01_0: - - platform: enocean - id: [0x05,0x04,0x03,0x02] - name: enocean_nodon01_0 - channel: 0 - -switch nodon01_1: - - platform: enocean - id: [0x05,0x04,0x03,0x02] - name: enocean_nodon01_1 - channel: 1 -``` diff --git a/source/_components/switch.fritzbox.markdown b/source/_components/switch.fritzbox.markdown deleted file mode 100644 index 3a257701e5d..00000000000 --- a/source/_components/switch.fritzbox.markdown +++ /dev/null @@ -1,29 +0,0 @@ ---- -layout: page -title: "Fritzbox Switch" -description: "Instructions on how to integrate the AVM Fritzbox switch." -date: 2017-11-12 17:10 -sidebar: true -comments: false -sharing: true -footer: true -logo: avm.png -ha_category: Switch -ha_release: 0.68 -ha_iot_class: "Local Polling" ---- - -To get AVM Fritzbox switch follow the instructions for the [Fritzbox component](/components/fritzbox/). - -### {% linkable_title Attributes %} - -The are several attributes that can be useful for automations and templates. - -| Attribute | Description | -| --------- | ----------- | -| `device_locked` | The state of the key lock at the device. -| `locked` | The state of the lock for configuring the device via the app or the Fritzbox web interface. -| `temperature_unit` | The unit of the temperature sensor (only available if the device support temperature sensor). -| `temperature` | The current temperature sensor reading (only available if the device supports temperature sensor). -| `total_consumption` | The total power consumption since the beginning of operation (only available if the device supports power meter function). -| `total_consumption_unit` | The unit of the total_consumption (only available if the device supports power meter function). diff --git a/source/_components/switch.isy994.markdown b/source/_components/switch.isy994.markdown deleted file mode 100644 index eacf1a002dd..00000000000 --- a/source/_components/switch.isy994.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "ISY994 Switch" -description: "Instructions on how to integrate ISY994 switch into Home Assistant." -date: 2016-09-03 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: universal_devices.png -ha_category: Switch -ha_iot_class: "Local Push" ---- - -The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) switch from within Home Assistant. - -They will be automatically discovered if the `isy994` component is loaded. diff --git a/source/_components/switch.lightwave.markdown b/source/_components/switch.lightwave.markdown deleted file mode 100644 index 0734a9a8370..00000000000 --- a/source/_components/switch.lightwave.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: page -title: "Lightwave Switch" -description: "Instructions on how to integrate Lightwave Switches with Home Assistant." -date: 2018-12-05 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lightwave.png -ha_category: Switch -ha_release: 0.84 -ha_iot_class: "Assumed State" ---- -The `lightwave` switch platform integrates your Lightwave switches into Home Assistant. -

-Configuration details for the Lightwave platform can be found on the main [Lightwave component](/components/lightwave/) page. -

\ No newline at end of file diff --git a/source/_components/switch.litejet.markdown b/source/_components/switch.litejet.markdown deleted file mode 100644 index 34f90d9badb..00000000000 --- a/source/_components/switch.litejet.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "LiteJet Switch" -description: "Instructions on how to setup the LiteJet switches within Home Assistant." -date: 2016-10-26 13:00 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Switch -ha_release: 0.32 -ha_iot_class: "Local Polling" ---- - -To get your LiteJet switches working with Home Assistant, follow the instructions for the general [LiteJet component](/components/litejet/). diff --git a/source/_components/switch.lutron.markdown b/source/_components/switch.lutron.markdown deleted file mode 100644 index 11ce9f1611f..00000000000 --- a/source/_components/switch.lutron.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Lutron Switch" -description: "Instructions on how to setu p the Lutron switches within Home Assistant." -date: 2018-10-09 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Switch -ha_iot_class: "Local Polling" -ha_release: 0.85 ---- - -To get your Lutron switches working with Home Assistant, follow the instructions for the general [Lutron component](/components/lutron/). diff --git a/source/_components/switch.lutron_caseta.markdown b/source/_components/switch.lutron_caseta.markdown deleted file mode 100644 index 100e044b1bd..00000000000 --- a/source/_components/switch.lutron_caseta.markdown +++ /dev/null @@ -1,23 +0,0 @@ ---- -layout: page -title: "Lutron Caseta Switch" -description: "Instructions on how to setup the Lutron Caseta switches within Home Assistant." -date: 2017-04-30 09:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: lutron.png -ha_category: Switch -ha_iot_class: "Local Polling" ---- - -To get Lutron Caseta switches working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/). - -After setup, switches will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a light switch called 'Master Bathroom Vanity' will appear in Home Assistant as `switch.master_bathroom_vanity`. - -For dimmable lights including wall and plug-in dimmers, see [Lutron Caseta Light](/components/light.lutron_caseta/). - -For more information on working with switches in Home Assistant, see the [Switches component](/components/switch/). - -Available services: `switch.turn_on` and `switch.turn_off`. \ No newline at end of file diff --git a/source/_components/switch.raspihats.markdown b/source/_components/switch.raspihats.markdown deleted file mode 100644 index 7cd9fccddfd..00000000000 --- a/source/_components/switch.raspihats.markdown +++ /dev/null @@ -1,120 +0,0 @@ ---- -layout: page -title: "Raspihats Switch" -description: "Instructions on how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a switch." -date: 2017-05-15 04:20 -sidebar: true -comments: false -sharing: true -footer: true -logo: raspihats.png -ha_category: DIY -ha_release: 0.45 -ha_iot_class: "Local Push" ---- - -The `raspihats` switch platform allows you to control the digital outputs of your [Raspihats](http://www.raspihats.com/) boards. - -## {% linkable_title Configuration %} - -To use your Raspihats boards in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -switch: - - platform: raspihats - i2c_hats: - - board: DI6acDQ6rly - address: 0x60 - channels: - - index: 0 - name: Fan Office - invert_logic: true - initial_state: true - - index: 1 - name: Light Office -``` - -{% configuration %} -i2c_hats: - description: An array of used I2C-HATs. - required: false - type: list - keys: - board: - description: The board name. - required: true - type: string - address: - description: The board I2C address as HEX value. - required: true - type: string - channels: - description: An array of used digital input channels. - required: true - type: list - keys: - index: - description: The digital input channel index. - required: true - type: integer - name: - description: The friendly name to use for the frontend. - required: true - type: string - invert_logic: - description: Inverts the input logic. - required: false - default: false - type: boolean - initial_state: - description: "The initial state, can be either `true` or `false`. `none` means no state is forced on the corresponding digital output when this switch is instantiated." - required: false - default: None - type: boolean -{% endconfiguration %} - -## {% linkable_title Directions for installing smbus support on Raspberry Pi %} - -Enable I2c interface with the Raspberry Pi configuration utility: - -```bash -# pi user environment: Enable i2c interface -$ sudo raspi-config -``` - -Select `Interfacing options->I2C` choose `` and hit `Enter`, then go to `Finish`. - -Install dependencies for use the `smbus-cffi` module and enable your _homeassistant_ user to join the _i2c_ group: - -```bash -# pi user environment: Install i2c dependencies and utilities -$ sudo apt-get install build-essential libi2c-dev i2c-tools python-dev libffi-dev - -# pi user environment: Add homeassistant user to the i2c group -$ sudo usermod -a -G i2c homeassistant -``` - -## {% linkable_title Check the i2c address of the sensor %} - -After installing `i2c-tools`, a new utility is available to scan the addresses of the connected sensors, so you can see the sensor address: - -```bash -/usr/sbin/i2cdetect -y 1 -``` - -It will output a table like this: - -```text - 0 1 2 3 4 5 6 7 8 9 a b c d e f -00: -- -- -- -- -- -- -- -- -- -- -- -- -- -10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -20: -- -- -- 23 -- -- -- -- -- -- -- -- -- -- -- -- -30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -40: 40 -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- -50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -70: -- -- -- -- -- -- -- 77 -``` - -For more details about the Raspihats add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). diff --git a/source/_components/switch.tahoma.markdown b/source/_components/switch.tahoma.markdown deleted file mode 100644 index a7c3338fee4..00000000000 --- a/source/_components/switch.tahoma.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Tahoma Switch" -description: "Instructions on how to integrate Tahoma switches into Home Assistant." -date: 2017-07-18 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: tahoma.png -ha_category: Sensor -ha_release: 0.59 ---- - -The `tahoma` switch platform lets you see switches added to your Tahoma Box in Home Assistant. - -Switches will be added automatically. Please refer to the [component](/components/tahoma/) configuration on how to setup Tahoma. diff --git a/source/_components/switch.tellduslive.markdown b/source/_components/switch.tellduslive.markdown deleted file mode 100644 index e6f2309c108..00000000000 --- a/source/_components/switch.tellduslive.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "Telldus Live Switch" -description: "Instructions on how to integrate Telldus Live switches into Home Assistant." -date: 2016-01-17 15:49 -sidebar: true -comments: false -sharing: true -footer: true -logo: telldus.png -ha_category: Switch -featured: false ---- - -Integrates Telldus Live switches into Home Assistant. See the [main component](/components/tellduslive/) for configuration instructions. diff --git a/source/_components/switch.zha.markdown b/source/_components/switch.zha.markdown deleted file mode 100644 index e23f6751ff3..00000000000 --- a/source/_components/switch.zha.markdown +++ /dev/null @@ -1,15 +0,0 @@ ---- -layout: page -title: "Zigbee Home Automation Switch" -description: "Instructions on how to setup Zigbee Home Automation switches within Home Assistant." -date: 2017-02-22 00:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: zigbee.png -ha_category: Switch -ha_iot_class: "Local Polling" ---- - -To get your Zigbee switches working with Home Assistant, follow the instructions for the general [Zigbee Home Automation component](/components/zha/). diff --git a/source/_components/tahoma.markdown b/source/_components/tahoma.markdown index 323d51bee5a..2d030091900 100644 --- a/source/_components/tahoma.markdown +++ b/source/_components/tahoma.markdown @@ -8,13 +8,33 @@ comments: false sharing: true footer: true logo: tahoma.png -ha_category: Hub +ha_category: + - Hub + - Binary Sensor + - Cover + - Scene + - Switch + - Sensor ha_release: 0.59 ha_iot_class: "Cloud Polling" +redirect_from: + - /components/binary_sensor.tahoma/ + - /components/cover.tahoma/ + - /components/scene.tahoma/ + - /components/switch.tahoma/ + - /components/sensor.tahoma/ --- The `Tahoma` component platform is used as an interface to the [tahomalink.com](https://www.tahomalink.com) website. It adds covers, scenes and a sun sensor from the Tahoma platform. +There is currently support for the following device types within Home Assistant: + +- Binary Sensor +- Sensor +- Cover +- Switch +- Scene + ## {% linkable_title Configuration %} To use your Tahoma devices in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/tellduslive.markdown b/source/_components/tellduslive.markdown index 4af2502e318..27c9d7fa637 100644 --- a/source/_components/tellduslive.markdown +++ b/source/_components/tellduslive.markdown @@ -8,9 +8,22 @@ comments: false sharing: true footer: true logo: telldus.png -ha_category: Hub +ha_category: + - Hub + - Binary Sensor + - Cover + - Light + - Sensor + - Switch featured: false ha_release: 0.11 +ha_config_flow: true +redirect_from: + - /components/binary_sensor.tellduslive/ + - /components/cover.tellduslive/ + - /components/light.tellduslive/ + - /components/sensor.tellduslive/ + - /components/switch.tellduslive/ --- The `tellduslive` component let you connect to [Telldus Live](https://live.telldus.com). It's cloud platform that connects to your Tellstick Net or Tellstick ZNet connected gear at home. diff --git a/source/_components/velux.markdown b/source/_components/velux.markdown index 2a6731b25e3..697d9a617e0 100644 --- a/source/_components/velux.markdown +++ b/source/_components/velux.markdown @@ -8,12 +8,15 @@ comments: false sharing: true footer: true logo: velux.png -ha_category: Hub +ha_category: + - Scene ha_release: 0.49 ha_iot_class: "Local Polling" +redirect_from: + - /components/scene.velux/ --- -[Velux](http://www.velux.com) integration for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200. +[Velux](http://www.velux.com) integration for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200. ## {% linkable_title Configuration %} diff --git a/source/_components/weather.ecobee.markdown b/source/_components/weather.ecobee.markdown deleted file mode 100644 index 33f1983ecd5..00000000000 --- a/source/_components/weather.ecobee.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "Ecobee Weather" -description: "Instructions on how to setup the Ecobee weather within Home Assistant." -date: 2017-11-29 21:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: ecobee.png -ha_category: Weather -ha_release: 0.59 -ha_iot_class: "Local Push" ---- - -To get your Ecobee weather component working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/). diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown index a2921fe5c9d..da056f7a9c3 100644 --- a/source/_components/zha.markdown +++ b/source/_components/zha.markdown @@ -8,9 +8,20 @@ comments: false sharing: true footer: true logo: zigbee.png -ha_category: Hub +ha_category: + - Binary Sensor + - Fan + - Light + - Sensor + - Switch ha_release: 0.44 ha_iot_class: "Local Polling" +redirect_from: + - /components/binary_sensor.zha/ + - /components/fan.zha/ + - /components/light.zha/ + - /components/sensor.zha/ + - /components/switch.zha/ --- [Zigbee Home Automation](http://www.zigbee.org/zigbee-for-developers/applicationstandards/zigbeehomeautomation/) @@ -18,11 +29,11 @@ integration for Home Assistant allows you to connect many off-the-shelf Zigbee b There is currently support for the following device types within Home Assistant: -- [Binary Sensor](../binary_sensor.zha) (e.g., motion and door sensors) -- [Sensor](../sensor.zha) (e.g., temperature sensors) -- [Light](../light.zha) -- [Switch](../switch.zha) -- [Fan](../fan.zha) +- Binary Sensor +- Sensor +- Light +- Switch +- Fan Known working Zigbee radio modules: diff --git a/source/_cookbook/automation_first_light.markdown b/source/_cookbook/automation_first_light.markdown index 098036db77f..be4770c4f7e 100644 --- a/source/_cookbook/automation_first_light.markdown +++ b/source/_cookbook/automation_first_light.markdown @@ -30,8 +30,8 @@ automation: - alias: Enable First Morning Trigger trigger: - platform: time - at: '5:00' - action: + at: '05:00:00' + action: service: homeassistant.turn_on entity_id: input_boolean.trigger_first_morning @@ -41,12 +41,12 @@ automation: - platform: sun event: sunrise offset: "01:00:00" - action: + action: service: homeassistant.turn_off entity_id: input_boolean.trigger_first_morning - + # This is the main automation. It triggers when my motion sensor is triggered # (in this case, a motion sensor from a security system attached to my Vera) - alias: First Morning Motion @@ -59,17 +59,17 @@ automation: condition: state entity_id: input_boolean.trigger_first_morning state: 'on' - + action: # turn off the "waiting" boolean regardless of whether lights will turn on # so that this happens only once - service: homeassistant.turn_off entity_id: input_boolean.trigger_first_morning - + # But only turn on lights if the living room and kitchen lights are off or dimmed - # If a condition tests false, the automation will end + # If a condition tests false, the automation will end - condition: and - conditions: + conditions: - condition: numeric_state entity_id: light.livingroom_ec # if light is off, force a 0, otherwise use the brightness value @@ -84,13 +84,13 @@ automation: entity_id: light.kitchen_ceiling value_template: {% raw %}'{% if states.light.kitchen_ceiling.state == "on" %}{{ states.light.kitchen_ceiling.attributes.brightness }}{% else %}0{% endif %}'{% endraw %} below: 128 - + # Trigger a scene # You could add as many services or scenes as you'd like - service: scene.turn_on entity_id: scene.morning_first_motion - + ``` #### {% linkable_title The Scene %} @@ -98,7 +98,7 @@ automation: Here is the Scene that is called via the Automations above. ```yaml -# here's the scene that gets called. Lights in +# here's the scene that gets called. Lights in # my living room and kitchen turn on. scene: - name: Morning First Motion diff --git a/source/_cookbook/automation_knx.markdown b/source/_cookbook/automation_knx.markdown new file mode 100644 index 00000000000..5092d6b09a3 --- /dev/null +++ b/source/_cookbook/automation_knx.markdown @@ -0,0 +1,217 @@ +--- +layout: page +title: "KNX automation and interaction with other systems" +description: "General KNX set up and communication with other systems like the Philips Hue." +date: 2019-01-20 22:00 +0100 +sidebar: true +comments: false +sharing: true +footer: true +ha_category: Automation Examples +--- + +This cookbook shows a general KNX set up and communication with other systems like the Philips Hue. + +## {% linkable_title General KNX setup %} + +``` yaml +knx: + # This is all you need to get the KNX component up and running. + # Auto config works nicely and usually no config data for your KNX ip tunnel is needed. + # If the KNX router is not found automatically, check the docs and add the IP config here. + +# get some sensor data from KNX to HA +sensor: + - platform: knx + name: Helligkeit Treppe oben + address: '6/1/0' + type: 'illuminance' + # The entity_id of this sensor will be generated from the name by a slug function. + # In this case, it will be sensor.helligkeit_treppe_oben + # See dev tools' state page (icons at the bottom of left side menu) for a list of all entity_ids + +light: + # See "sensor" remarks above for an explanation of the resulting entity_ids + - platform: knx + # switched light + name: 'Eltern Decke' + address: '1/2/10' + state_address: '1/2/11' + + - platform: knx + # dimmed light + name: 'Eltern Bett' + address: '1/2/12' + state_address: '1/2/15' + brightness_address: '1/2/13' + brightness_state_address: '1/2/16' + +cover: + # KNX Covers are roller shutters and blinds. + # These items currently expose a bug with the invert_position setting: + # Either you will get 100% for an open shutter and 0% for a closed one + # or you will get the function of up and down arrows exchanged wrongly. + # Hope this is resolved soon. + # --- + # See "sensor" remarks above for an explanation of the resulting entity_ids + - platform: knx + name: "Eltern" + move_long_address: '3/2/0' + move_short_address: '3/2/1' + position_address: '3/2/3' + position_state_address: '3/2/2' + travelling_time_up: 23 + travelling_time_down: 21 + invert_position: true + + - platform: knx + name: "Büro" + move_long_address: '3/2/4' + move_short_address: '3/2/5' + position_address: '3/2/7' + position_state_address: '3/2/6' + travelling_time_up: 23 + travelling_time_down: 21 + invert_position: true +``` + +## {% linkable_title Using some values from HA within KNX %} + +``` yaml +# configuration.yaml example +sensor: +# Register with Dark Sky to retrieve current environment data. +# Registration is free for the amount of requests we need here. +- platform: openweathermap + name: OpenWeather + language: de + api_key: YOUR_API_KEY + monitored_conditions: + - weather + - temperature + - wind_speed + - wind_bearing + - humidity + - pressure + - clouds + - rain + - snow + - weather_code + +knx: + # Expose the above sensor data from HA to KNX group addresses. + # To find the right "type" setting for each parameter, create a group address in ETS, + # add a consuming actor for this kind of parameter to it and check the properties pane. + # ETS will show you a data type (DPT) that you can compare to the available DPTs in the + # documentation of the HA KNX component. + expose: + - type: 'temperature' + entity_id: 'sensor.dark_sky_temperature' + address: '0/1/10' + - type: 'humidity' + entity_id: 'sensor.dark_sky_humidity' + address: '0/1/11' + - type: 'temperature' + entity_id: 'sensor.dark_sky_pressure' + address: '0/1/12' + - type: 'DPT-9' + entity_id: 'sensor.dark_sky_wind_speed' + address: '0/1/13' + - type: 'DPT-14' + entity_id: 'sensor.dark_sky_wind_bearing' + address: '0/1/14' +``` + +## {% linkable_title Basic KNX automation %} + +This example uses an automation that is activated by a KNX switch. + +The automation then triggers a script that controls a KNX light and dims it down in 5 steps from 80% to 0% over a time span of 5 minutes. + +Care must be taken to stop the script, when the light is otherwise switched (i.e., by its normal on/off KNX switch). If we don't do that, the light will first switch correctly, but then the script will continue to run in the background and after the next delay has passed it will kick in again and activate its next dim level. + +```yaml +knx: + +switch: +- platform: knx + # The normal on/off switch for the light + name: "Licht, Eltern Bett" + address: '1/2/12' +- platform: knx + # The switch that triggers the dim script + # This switch must be configured in ETS to send on when pressed and off when released + name: "Licht, Eltern Bett, Fadeout" + address: '1/2/17' + +light: + # This is the light that we want to dim (more precisely it is the dimming actuator of the light). + # It is directly controlled through the first switch above. + # (Note that the switch shares its group address with this light and thus controls it over the KNX bus.) + - platform: knx + name: 'Eltern Bett' + address: '1/2/12' + state_address: '1/2/15' + brightness_address: '1/2/13' + brightness_state_address: '1/2/16' + +automation: +# start the dim script, if the dim switch is pressed +- id: light_eltern_bett_fadeout + alias: Licht Eltern Bett Fade-Out + trigger: + - entity_id: switch.licht_eltern_bett_fadeout + platform: state + to: 'on' + condition: [] + action: + # in case the script was already running, we first stop it + - service: script.turn_off + entity_id: script.light_eltern_bett_fadeout + - service: script.turn_on + entity_id: script.light_eltern_bett_fadeout + +# stop the dim script, if light is switched manually +- id: light_eltern_bett_fadeout_stop + alias: Licht Eltern Bett Fade-Out STOP + trigger: + - entity_id: switch.licht_eltern_bett + platform: state + # no argument here = trigger with ANY state change + condition: [] + action: + - service: script.turn_off + entity_id: script.light_eltern_bett_fadeout + +script: + light_eltern_bett_fadeout: + alias: Licht Eltern Bett Fade-Out + sequence: + - service: light.turn_on + entity_id: light.eltern_bett + data: + brightness_pct: 80 + - delay: '00:01:00' + - service: light.turn_on + entity_id: light.eltern_bett + data: + brightness_pct: 60 + - delay: '00:01:00' + - service: light.turn_on + entity_id: light.eltern_bett + data: + brightness_pct: 40 + - delay: '00:01:00' + - service: light.turn_on + entity_id: light.eltern_bett + data: + brightness_pct: 20 + - delay: '00:01:00' + - service: light.turn_on + entity_id: light.eltern_bett + data: + brightness_pct: 10 + - delay: '00:01:00' + - service: light.turn_off + entity_id: light.eltern_bett +``` diff --git a/source/_cookbook/automation_using_timeinterval_inputboolean.markdown b/source/_cookbook/automation_using_timeinterval_inputboolean.markdown index d5edc5e9613..af46927fe5f 100644 --- a/source/_cookbook/automation_using_timeinterval_inputboolean.markdown +++ b/source/_cookbook/automation_using_timeinterval_inputboolean.markdown @@ -25,9 +25,8 @@ automation: # Changes Hue light every two minutes to random color if input boolean is set to on - alias: 'Set LivingColors to random color' trigger: - platform: time + platform: time_pattern minutes: '/2' - seconds: 0 condition: condition: state entity_id: input_boolean.loop_livingcolors diff --git a/source/_cookbook/send_a_reminder.markdown b/source/_cookbook/send_a_reminder.markdown index e08d2c9767d..9b965a77bc5 100644 --- a/source/_cookbook/send_a_reminder.markdown +++ b/source/_cookbook/send_a_reminder.markdown @@ -30,13 +30,9 @@ automation: - alias: Send message at a given time trigger: platform: time - hours: 12 - minutes: 15 - seconds: 0 + at: '12:15:00' action: service: notify.jabber data: message: 'Time for lunch' ``` - - diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 6b3868bf5b4..44621c53896 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -10,7 +10,7 @@ footer: true redirect_from: /getting-started/automation-trigger/ --- -Triggers are what starts the processing of an automation rule. It is possible to specify multiple triggers for the same rule - when _any_ of the triggers becomes true then the automation will start. Once a trigger starts, Home Assistant will validate the conditions, if any, and call the action. +Triggers are what starts the processing of an automation rule. It is possible to specify [multiple triggers](/docs/automation/trigger/#multiple-triggers) for the same rule - when _any_ of the triggers becomes true then the automation will start. Once a trigger starts, Home Assistant will validate the conditions, if any, and call the action. ### {% linkable_title Event trigger %} @@ -209,8 +209,9 @@ automation 3: minutes: '/5' ``` -As mentioned in the Sun trigger section, sunrise is a different day than any time prior to midnight. If you want to trigger an action with a large enough amount of time before sunrise that it precedes midnight, this must be accounted for properly. One way is to convert the sunrise time to a timestamp (seconds since 1 Jan 1970). Then do the same for the offset desired (in seconds). This is done with the _as_timestamp_ method explained in the [Templating - Home Assistant template extensions](/docs/configuration/templating/#home-assistant-template-extensions) section. - +

+ Do not prefix numbers with a zero - using `'00'` instead of '0' for example will result in errors. +

### {% linkable_title Webhook trigger %} @@ -262,9 +263,8 @@ When your want your automation rule to have multiple triggers, just prefix the f automation: trigger: # first trigger - - platform: time + - platform: time_pattern minutes: 5 - seconds: 00 # our second trigger is the sunset - platform: sun event: sunset diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown index 18c39443b4d..a8fd1310717 100644 --- a/source/_docs/tools/dev-tools.markdown +++ b/source/_docs/tools/dev-tools.markdown @@ -102,5 +102,5 @@ Even though MQTT in general provides deeper functionality, the developer tools s The Information tab simply provides information about the current installed version, additional links and credits. The tab also contains a section that shows `syslog` information, and the contents of `home-assistant.log` with an option to clear and refresh the logs. -The Information tab also allows makes it possible to try out the Lovelace User Interface (UI) by clicking "Try out the new Lovelace UI (experimental)" or set Lovelace as the default UI, so that when the "Overview" link in the Sidebar is selected, the Lovelace UI will load by default. +The Information tab also allows makes it possible to try out the Lovelace User Interface (UI) by clicking "Try out the new Lovelace UI" or set Lovelace as the default UI, so that when the "Overview" link in the Sidebar is selected, the Lovelace UI will load by default. diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html index 4d9912c1253..a8222bb72cb 100644 --- a/source/_includes/asides/docs_navigation.html +++ b/source/_includes/asides/docs_navigation.html @@ -68,7 +68,7 @@
  • {% active_link /docs/frontend/mobile/ Android/iOS Homescreen %}
  • {% active_link /docs/frontend/browsers/ Browser Compatibility List %}
    • -
  • {% active_link /lovelace Lovelace UI (Experimental) %}
    • +
  • {% active_link /lovelace Lovelace UI %}
  • diff --git a/source/_includes/asides/lovelace_navigation.html b/source/_includes/asides/lovelace_navigation.html index fd5b58c70ab..8f9a1cd3b10 100644 --- a/source/_includes/asides/lovelace_navigation.html +++ b/source/_includes/asides/lovelace_navigation.html @@ -7,7 +7,6 @@
    • {% active_link /lovelace/ Introduction %}
    • {% active_link /lovelace/changelog/ Changelog %}
      • -
    • {% active_link /lovelace/tips/ Tips and Tricks %}
    @@ -17,7 +16,7 @@
  • {% active_link /lovelace/how-it-works/ How it works %}
  • {% active_link /lovelace/yaml-mode/ YAML mode %}
  • {% active_link /lovelace/views/ Views %}
    • -
  • Custom Cards (for developers)
    • +
  • Developing Custom Cards
    • diff --git a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown index 07cc25a196c..7a6a19be5e1 100644 --- a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown +++ b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown @@ -54,9 +54,8 @@ rest_command: automation: alias: HTTP to MQTT keep alive trigger: - platform: time + platform: time_pattern minutes: '/10' - seconds: 00 condition: condition: time after: '7:30:00' diff --git a/source/_posts/2019-01-23-lovelace-released.markdown b/source/_posts/2019-01-23-lovelace-released.markdown index 0d08119c6c9..5c332f4b8ae 100644 --- a/source/_posts/2019-01-23-lovelace-released.markdown +++ b/source/_posts/2019-01-23-lovelace-released.markdown @@ -32,7 +32,11 @@ For a deep dive into all the new features, check out the [latest episode of the For an overview of all the different features, check out the [Lovelace documentation](/lovelace/). -1: If you prefer YAML, Lovelace also includes a [YAML mode](/lovelace/yaml-mode/) that supports the use of `!include` and `!secret`. +1: If you prefer to write your Lovelace config in YAML, Lovelace also includes an optional [YAML mode](/lovelace/yaml-mode/). + +## {% linkable_title Migrating to Lovelace %} + +You have to do… nothing! If not configured, Lovelace will use the same algorithm to built-up the UI as the old UI did. ## {% linkable_title History %} diff --git a/source/_posts/2019-01-23-release-86.markdown b/source/_posts/2019-01-23-release-86.markdown index 5e527613949..6fd29d8ee4c 100644 --- a/source/_posts/2019-01-23-release-86.markdown +++ b/source/_posts/2019-01-23-release-86.markdown @@ -38,9 +38,17 @@ The Zigbee team is also planning a bunch of cool things for 2019. Direct device ## {% linkable_title Noteworthy breaking changes %} +Update: the entity ID one was too harsh, it's not a warning. + This release also includes two noteworthy breaking changes. One is a follow-up on the slugify breaking change from last release. We did not update the validation check for config options that need to be valid slugs. This means that some of your config values might be invalid. Keep an eye at the console as we have a new message to tell you which ones are wrong. -This issue also impacts the entity registry, which could contain in some rare cases invalid entity IDs. Expect entity IDs to change if they contained a double underscore (which becomes 1) or if they started/ended in an underscore (which will be removed). +The following things are not allowed in entity IDs: + + - No capital letters + - No leading or ending underscores + - No double underscores + +This issue also impacts the entity registry, which could contain in some cases invalid entity IDs. Expect entity IDs to change if they contained a double underscore (which becomes 1) or if they started/ended in an underscore (which will be removed). Another noteworthy breaking change (sorry!), is that the automation `time` trigger has been split into two: `time` and `time_pattern`. If you had a time trigger containing the keys `hours`, `minutes` or `seconds`, update the platform from `time` to `time_pattern`. @@ -72,6 +80,28 @@ Another noteworthy breaking change (sorry!), is that the automation `time` trigg [blink docs]: /components/blink/ [sensor.gtt docs]: /components/sensor.gtt/ +## {% linkable_title Release 0.86.2 - January 24 %} + +- Philips Hue - Remove unnessesary warning ([@starkillerOG] - [#20394]) ([hue docs]) +- history allowed to load states with invalid entity IDs ([@balloob] - [#20399]) + +[#20394]: https://github.com/home-assistant/home-assistant/pull/20394 +[#20399]: https://github.com/home-assistant/home-assistant/pull/20399 +[@balloob]: https://github.com/balloob +[@starkillerOG]: https://github.com/starkillerOG +[hue docs]: /components/hue/ + +## {% linkable_title Release 0.86.3 - January 26 %} + +- Philips Hue, include debug message for color gamut ([@starkillerOG] - [#20455]) ([hue docs]) +- Warn instead of break for old slugs/entity ids ([@balloob] - [#20478]) + +[#20455]: https://github.com/home-assistant/home-assistant/pull/20455 +[#20478]: https://github.com/home-assistant/home-assistant/pull/20478 +[@balloob]: https://github.com/balloob +[@starkillerOG]: https://github.com/starkillerOG +[hue docs]: /components/hue/ + ## {% linkable_title If you need help... %} ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks. diff --git a/source/components/index.html b/source/components/index.html index d6d9ade957f..a55d60425b6 100644 --- a/source/components/index.html +++ b/source/components/index.html @@ -50,8 +50,9 @@ Support for these components is provided by the Home Assistant community. Added in {{ added_two_ago_version }} ({{ two_ago_version_components_count }}) {%- for category in categories -%} - {%- if category and category != 'Other' -%} - {{ category }} ({{ components | where: 'ha_category', category | size }}) + {%- assign components_count = components | where: 'ha_category', category | size -%} + {%- if category and category != 'Other' and components_count != 0 -%} + {{ category }} ({{ components_count }}) {%- endif -%} {%- endfor -%} diff --git a/source/developers/credits.markdown b/source/developers/credits.markdown index f41d05d0102..23367e06ab3 100644 --- a/source/developers/credits.markdown +++ b/source/developers/credits.markdown @@ -2,7 +2,7 @@ layout: page title: "Credits" description: "Credits for the developers who contributed to Home Assistant." -date: 2019-01-13, 20:14:10 +0000 +date: 2019-01-24, 22:39:22 +0000 sidebar: true comments: false sharing: true @@ -13,14 +13,14 @@ This page contains a list of people who have contributed in one way or another t ### {% linkable_title Author %} -- [Paulus Schoutsen (@balloob)](https://github.com/balloob "8578 total commits to the home-assistant organization: -4724 commits to home-assistant -1753 commits to home-assistant.io -1309 commits to home-assistant-polymer +- [Paulus Schoutsen (@balloob)](https://github.com/balloob "8673 total commits to the home-assistant organization: +4744 commits to home-assistant +1777 commits to home-assistant.io +1354 commits to home-assistant-polymer 237 commits to home-assistant-js -146 commits to developers.home-assistant +148 commits to developers.home-assistant 132 commits to netdisco -116 commits to home-assistant-js-websocket +120 commits to home-assistant-js-websocket 43 commits to hass-release 20 commits to data.home-assistant 17 commits to LabelBot @@ -32,14 +32,14 @@ This page contains a list of people who have contributed in one way or another t 6 commits to custom-panel-starter-kit-react 5 commits to home-assistant-notebooks 4 commits to ui-schema -3 commits to hassio-build 3 commits to hassio-addons +3 commits to hassio-build 2 commits to lambda-home-assistant-github 2 commits to home-assistant-iOS -2 commits to issue-bot 2 commits to hassio-addons-example -1 commit to architecture +2 commits to issue-bot 1 commit to warrant +1 commit to architecture ") ### {% linkable_title Contributors %} @@ -73,12 +73,18 @@ This page contains a list of people who have contributed in one way or another t - [a\-r\-j\-a\-n (@a-r-j-a-n)](https://github.com/a-r-j-a-n "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [aapjeisbaas (@aapjeisbaas)](https://github.com/aapjeisbaas "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Aaron (@mcd1992)](https://github.com/mcd1992 "5 total commits to the home-assistant organization: 5 commits to open-zwave ") -- [Aaron Bach (@bachya)](https://github.com/bachya "125 total commits to the home-assistant organization: -93 commits to home-assistant -32 commits to home-assistant.io +- [Aaron Bach (@bachya)](https://github.com/bachya "130 total commits to the home-assistant organization: +97 commits to home-assistant +33 commits to home-assistant.io +") +- [Aaron Godfrey (@boralyl)](https://github.com/boralyl "1 total commits to the home-assistant organization: +1 commit to home-assistant ") - [Aaron Linville (@linville)](https://github.com/linville "3 total commits to the home-assistant organization: 2 commits to appdaemon @@ -156,10 +162,10 @@ This page contains a list of people who have contributed in one way or another t - [Adam Knight (@ahknight)](https://github.com/ahknight "1 total commits to the home-assistant organization: 1 commit to open-zwave ") -- [Adam Mills (@armills)](https://github.com/armills "365 total commits to the home-assistant organization: -196 commits to home-assistant -96 commits to home-assistant-polymer -63 commits to home-assistant.io +- [Adam Mills (@armills)](https://github.com/armills "368 total commits to the home-assistant organization: +197 commits to home-assistant +97 commits to home-assistant-polymer +64 commits to home-assistant.io 3 commits to home-assistant-js 3 commits to developers.home-assistant 2 commits to python-openzwave @@ -206,7 +212,8 @@ This page contains a list of people who have contributed in one way or another t - [Adriaan Peeters (@apeeters)](https://github.com/apeeters "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Adrian Campos (@adriancampos)](https://github.com/adriancampos "1 total commits to the home-assistant organization: +- [Adrian Campos (@adriancampos)](https://github.com/adriancampos "2 total commits to the home-assistant organization: +1 commit to home-assistant-polymer 1 commit to home-assistant.io ") - [Adrian Goins (@oskapt)](https://github.com/oskapt "1 total commits to the home-assistant organization: @@ -246,9 +253,6 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant 1 commit to home-assistant.io ") -- [AHS (@ahofelt)](https://github.com/ahofelt "1 total commits to the home-assistant organization: -1 commit to home-assistant-polymer -") - [aisbergde (@aisbergde)](https://github.com/aisbergde "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") @@ -280,8 +284,8 @@ This page contains a list of people who have contributed in one way or another t - [Alastair D'Silva (@deece)](https://github.com/deece "5 total commits to the home-assistant organization: 2 commits to hassos 1 commit to hassio-homeassistant -1 commit to hassio-build 1 commit to hassio +1 commit to hassio-build ") - [Albatross (@DyingAlbatross)](https://github.com/DyingAlbatross "2 total commits to the home-assistant organization: 2 commits to home-assistant.io @@ -410,8 +414,8 @@ This page contains a list of people who have contributed in one way or another t - [Alexandre Prates Dias (@pratesbh)](https://github.com/pratesbh "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Alexei Chetroi (@Adminiuga)](https://github.com/Adminiuga "24 total commits to the home-assistant organization: -23 commits to home-assistant +- [Alexei Chetroi (@Adminiuga)](https://github.com/Adminiuga "25 total commits to the home-assistant organization: +24 commits to home-assistant 1 commit to home-assistant-polymer ") - [Alexis Iglauer (@ax42)](https://github.com/ax42 "4 total commits to the home-assistant organization: @@ -447,9 +451,9 @@ This page contains a list of people who have contributed in one way or another t - [Almost Engineer (@almostengr)](https://github.com/almostengr "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "162 total commits to the home-assistant organization: +- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "163 total commits to the home-assistant organization: 92 commits to home-assistant.io -57 commits to home-assistant +58 commits to home-assistant 7 commits to home-assistant-polymer 3 commits to developers.home-assistant 1 commit to pi-gen @@ -482,8 +486,8 @@ This page contains a list of people who have contributed in one way or another t - [Anders Gjendem (@agjendem)](https://github.com/agjendem "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "296 total commits to the home-assistant organization: -241 commits to home-assistant +- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "302 total commits to the home-assistant organization: +247 commits to home-assistant 46 commits to home-assistant.io 6 commits to pyharmony 3 commits to home-assistant-polymer @@ -494,9 +498,9 @@ This page contains a list of people who have contributed in one way or another t - [andig (@andig)](https://github.com/andig "2 total commits to the home-assistant organization: 2 commits to pi-gen ") -- [Andre Lengwenus (@alengwenus)](https://github.com/alengwenus "2 total commits to the home-assistant organization: -1 commit to home-assistant -1 commit to home-assistant.io +- [Andre Lengwenus (@alengwenus)](https://github.com/alengwenus "7 total commits to the home-assistant organization: +4 commits to home-assistant +3 commits to home-assistant.io ") - [Andrea (@BubiDevs)](https://github.com/BubiDevs "2 total commits to the home-assistant organization: 2 commits to home-assistant.io @@ -605,6 +609,9 @@ This page contains a list of people who have contributed in one way or another t - [Andrew Riley (@andrewcr7)](https://github.com/andrewcr7 "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [Andrew Sayre (@andrewsayre)](https://github.com/andrewsayre "3 total commits to the home-assistant organization: +3 commits to home-assistant +") - [Andrew Smith (@andrewmichaelsmith)](https://github.com/andrewmichaelsmith "2 total commits to the home-assistant organization: 2 commits to pi-gen ") @@ -643,9 +650,9 @@ This page contains a list of people who have contributed in one way or another t - [Andrey Jr\. Melnikov (@LynxChaus)](https://github.com/LynxChaus "1 total commits to the home-assistant organization: 1 commit to dehydrated ") -- [Andrey Kupreychik (@foxel)](https://github.com/foxel "16 total commits to the home-assistant organization: -11 commits to home-assistant -5 commits to home-assistant.io +- [Andrey Kupreychik (@foxel)](https://github.com/foxel "18 total commits to the home-assistant organization: +12 commits to home-assistant +6 commits to home-assistant.io ") - [Andrey Mikhaylov \(lolmaus\) (@lolmaus)](https://github.com/lolmaus "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -707,8 +714,8 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant.io ") - [Antoine Bertin (@Diaoul)](https://github.com/Diaoul "5 total commits to the home-assistant organization: -2 commits to home-assistant.io 2 commits to home-assistant +2 commits to home-assistant.io 1 commit to home-assistant-polymer ") - [Antoine GRÉA (@grea09)](https://github.com/grea09 "4 total commits to the home-assistant organization: @@ -781,8 +788,8 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant.io ") - [Ardetus (@Ardetus)](https://github.com/Ardetus "4 total commits to the home-assistant organization: -2 commits to home-assistant.io 2 commits to home-assistant +2 commits to home-assistant.io ") - [Ardi Mehist (@omgapuppy)](https://github.com/omgapuppy "3 total commits to the home-assistant organization: 2 commits to home-assistant.io @@ -798,8 +805,9 @@ This page contains a list of people who have contributed in one way or another t - [aribarreto (@aribarreto)](https://github.com/aribarreto "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [arigilder (@arigilder)](https://github.com/arigilder "4 total commits to the home-assistant organization: +- [arigilder (@arigilder)](https://github.com/arigilder "5 total commits to the home-assistant organization: 4 commits to home-assistant +1 commit to home-assistant.io ") - [arjenfvellinga (@arjenfvellinga)](https://github.com/arjenfvellinga "6 total commits to the home-assistant organization: 5 commits to home-assistant.io @@ -878,9 +886,9 @@ This page contains a list of people who have contributed in one way or another t - [Austin (@trainman419)](https://github.com/trainman419 "9 total commits to the home-assistant organization: 9 commits to home-assistant ") -- [Austin Drummond (@adrum)](https://github.com/adrum "8 total commits to the home-assistant organization: +- [Austin Drummond (@adrum)](https://github.com/adrum "10 total commits to the home-assistant organization: +6 commits to home-assistant.io 4 commits to home-assistant -4 commits to home-assistant.io ") - [austinlg96 (@austinlg96)](https://github.com/austinlg96 "2 total commits to the home-assistant organization: 1 commit to home-assistant @@ -895,8 +903,9 @@ This page contains a list of people who have contributed in one way or another t 1 commit to pi-gen 1 commit to home-assistant.io ") -- [awkwardDuck (@awkwardDuck)](https://github.com/awkwardDuck "2 total commits to the home-assistant organization: +- [awkwardDuck (@awkwardDuck)](https://github.com/awkwardDuck "3 total commits to the home-assistant organization: 2 commits to home-assistant +1 commit to home-assistant.io ") - [Axel (@axel8viii)](https://github.com/axel8viii "2 total commits to the home-assistant organization: 2 commits to open-zwave @@ -964,8 +973,9 @@ This page contains a list of people who have contributed in one way or another t - [Bartek Celary (@bcelary)](https://github.com/bcelary "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Bas (@basbl)](https://github.com/basbl "1 total commits to the home-assistant organization: +- [Bas (@basbl)](https://github.com/basbl "2 total commits to the home-assistant organization: 1 commit to home-assistant +1 commit to home-assistant.io ") - [Bas Schipper (@basschipper)](https://github.com/basschipper "10 total commits to the home-assistant organization: 8 commits to home-assistant @@ -977,10 +987,10 @@ This page contains a list of people who have contributed in one way or another t - [basst22778 (@basst22778)](https://github.com/basst22778 "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [bastshoes (@bastshoes)](https://github.com/bastshoes "4 total commits to the home-assistant organization: +- [bastshoes (@bastshoes)](https://github.com/bastshoes "5 total commits to the home-assistant organization: 2 commits to home-assistant +2 commits to home-assistant.io 1 commit to home-assistant-polymer -1 commit to home-assistant.io ") - [battistaar (@battistaar)](https://github.com/battistaar "1 total commits to the home-assistant organization: 1 commit to homebridge-homeassistant @@ -1114,9 +1124,12 @@ This page contains a list of people who have contributed in one way or another t - [bestlibre (@bestlibre)](https://github.com/bestlibre "16 total commits to the home-assistant organization: 8 commits to home-assistant 5 commits to home-assistant.io -1 commit to home-assistant-polymer -1 commit to hassio-build 1 commit to hassio +1 commit to hassio-build +1 commit to home-assistant-polymer +") +- [bforbird (@bforbird)](https://github.com/bforbird "1 total commits to the home-assistant organization: +1 commit to home-assistant.io ") - [bigbadblunt (@bigbadblunt)](https://github.com/bigbadblunt "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -1251,6 +1264,9 @@ This page contains a list of people who have contributed in one way or another t 6 commits to home-assistant 2 commits to home-assistant.io ") +- [Br4veSt4rr (@Br4veSt4rr)](https://github.com/Br4veSt4rr "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [brad (@oakbrad)](https://github.com/oakbrad "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -1282,8 +1298,8 @@ This page contains a list of people who have contributed in one way or another t - [Brahma Fear (@brahmafear)](https://github.com/brahmafear "8 total commits to the home-assistant organization: 8 commits to home-assistant.io ") -- [Bram Kragten (@bramkragten)](https://github.com/bramkragten "78 total commits to the home-assistant organization: -43 commits to home-assistant-polymer +- [Bram Kragten (@bramkragten)](https://github.com/bramkragten "94 total commits to the home-assistant organization: +59 commits to home-assistant-polymer 25 commits to home-assistant 9 commits to home-assistant.io 1 commit to home-assistant-notebooks @@ -1458,8 +1474,8 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant-polymer ") - [Cameron Bulock (@cbulock)](https://github.com/cbulock "5 total commits to the home-assistant organization: -2 commits to home-assistant.io 2 commits to home-assistant +2 commits to home-assistant.io 1 commit to netdisco ") - [Cameron Llewellyn (@camrun91)](https://github.com/camrun91 "2 total commits to the home-assistant organization: @@ -1494,8 +1510,9 @@ This page contains a list of people who have contributed in one way or another t 2 commits to home-assistant.io 1 commit to home-assistant ") -- [Casper (@casperklein)](https://github.com/casperklein "1 total commits to the home-assistant organization: +- [Casper (@casperklein)](https://github.com/casperklein "2 total commits to the home-assistant organization: 1 commit to hassio +1 commit to home-assistant.io ") - [Casper Weiss Bang (@C0DK)](https://github.com/C0DK "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -1516,9 +1533,9 @@ This page contains a list of people who have contributed in one way or another t - [cclauss (@cclauss)](https://github.com/cclauss "1 total commits to the home-assistant organization: 1 commit to appdaemon ") -- [cdce8p (@cdce8p)](https://github.com/cdce8p "205 total commits to the home-assistant organization: +- [cdce8p (@cdce8p)](https://github.com/cdce8p "206 total commits to the home-assistant organization: 130 commits to home-assistant -50 commits to home-assistant.io +51 commits to home-assistant.io 14 commits to home-assistant-polymer 6 commits to developers.home-assistant 5 commits to hass-release @@ -1548,9 +1565,10 @@ This page contains a list of people who have contributed in one way or another t - [Cenk Gündoğan (@cgundogan)](https://github.com/cgundogan "1 total commits to the home-assistant organization: 1 commit to libcoap ") -- [Censored3 (@Censored3)](https://github.com/Censored3 "6 total commits to the home-assistant organization: +- [Censored3 (@Censored3)](https://github.com/Censored3 "7 total commits to the home-assistant organization: 4 commits to hassio-addons 1 commit to developers.home-assistant +1 commit to home-assistant 1 commit to home-assistant.io ") - [Cezar Sá Espinola (@cezarsa)](https://github.com/cezarsa "2 total commits to the home-assistant organization: @@ -1572,9 +1590,9 @@ This page contains a list of people who have contributed in one way or another t 12 commits to home-assistant 7 commits to home-assistant.io ") -- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "55 total commits to the home-assistant organization: +- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "56 total commits to the home-assistant organization: 25 commits to home-assistant -18 commits to home-assistant.io +19 commits to home-assistant.io 12 commits to home-assistant-polymer ") - [Charles Spirakis (@srcLurker)](https://github.com/srcLurker "8 total commits to the home-assistant organization: @@ -1608,6 +1626,9 @@ This page contains a list of people who have contributed in one way or another t - [chocomega (@chocomega)](https://github.com/chocomega "1 total commits to the home-assistant organization: 1 commit to home-assistant ") +- [choss (@choss)](https://github.com/choss "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Chris (@chennin)](https://github.com/chennin "15 total commits to the home-assistant organization: 11 commits to home-assistant.io 4 commits to home-assistant @@ -1829,10 +1850,10 @@ This page contains a list of people who have contributed in one way or another t 1 commit to open-zwave 1 commit to home-assistant ") -- [Clifford W\. Hansen (@cliffordwhansen)](https://github.com/cliffordwhansen "4 total commits to the home-assistant organization: +- [Clifford W\. Hansen (@cliffordwhansen)](https://github.com/cliffordwhansen "5 total commits to the home-assistant organization: 2 commits to appdaemon +2 commits to home-assistant.io 1 commit to home-assistant -1 commit to home-assistant.io ") - [clyra (@clyra)](https://github.com/clyra "3 total commits to the home-assistant organization: 3 commits to appdaemon @@ -1846,8 +1867,8 @@ This page contains a list of people who have contributed in one way or another t - [Codepadawan (@Codepadawan)](https://github.com/Codepadawan "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [cogneato (@cogneato)](https://github.com/cogneato "26 total commits to the home-assistant organization: -19 commits to home-assistant.io +- [cogneato (@cogneato)](https://github.com/cogneato "27 total commits to the home-assistant organization: +20 commits to home-assistant.io 4 commits to developers.home-assistant 3 commits to hassos ") @@ -1906,8 +1927,8 @@ This page contains a list of people who have contributed in one way or another t 18 commits to home-assistant.io 1 commit to home-assistant ") -- [Corey Edwards (@heytensai)](https://github.com/heytensai "2 total commits to the home-assistant organization: -1 commit to home-assistant +- [Corey Edwards (@heytensai)](https://github.com/heytensai "3 total commits to the home-assistant organization: +2 commits to home-assistant 1 commit to home-assistant.io ") - [Corey Pauley (@devspacenine)](https://github.com/devspacenine "5 total commits to the home-assistant organization: @@ -1960,6 +1981,10 @@ This page contains a list of people who have contributed in one way or another t - [CV (@dagobert)](https://github.com/dagobert "9 total commits to the home-assistant organization: 9 commits to home-assistant.io ") +- [cvwillegen (@cvwillegen)](https://github.com/cvwillegen "4 total commits to the home-assistant organization: +2 commits to home-assistant +2 commits to home-assistant.io +") - [cweakland (@cweakland)](https://github.com/cweakland "1 total commits to the home-assistant organization: 1 commit to open-zwave ") @@ -1983,8 +2008,8 @@ This page contains a list of people who have contributed in one way or another t - [Dallas Opelt (@DallasO)](https://github.com/DallasO "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [damarco (@damarco)](https://github.com/damarco "13 total commits to the home-assistant organization: -13 commits to home-assistant +- [damarco (@damarco)](https://github.com/damarco "15 total commits to the home-assistant organization: +15 commits to home-assistant ") - [Dan (@danieljkemp)](https://github.com/danieljkemp "23 total commits to the home-assistant organization: 16 commits to home-assistant @@ -2075,8 +2100,9 @@ This page contains a list of people who have contributed in one way or another t 4 commits to home-assistant 1 commit to netdisco ") -- [Daniel Chesterton (@dchesterton)](https://github.com/dchesterton "1 total commits to the home-assistant organization: +- [Daniel Chesterton (@dchesterton)](https://github.com/dchesterton "2 total commits to the home-assistant organization: 1 commit to home-assistant +1 commit to home-assistant.io ") - [Daniel Claes (@daenny)](https://github.com/daenny "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -2084,8 +2110,8 @@ This page contains a list of people who have contributed in one way or another t - [Daniel Escoz (@Darkhogg)](https://github.com/Darkhogg "3 total commits to the home-assistant organization: 3 commits to home-assistant.io ") -- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "403 total commits to the home-assistant organization: -274 commits to home-assistant +- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "410 total commits to the home-assistant organization: +281 commits to home-assistant 126 commits to home-assistant.io 3 commits to home-assistant-polymer ") @@ -2152,10 +2178,10 @@ This page contains a list of people who have contributed in one way or another t - [Danijel Stojnic (@danijelst)](https://github.com/danijelst "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [Daniyar Yeralin (@yeralin)](https://github.com/yeralin "3 total commits to the home-assistant organization: +- [Daniyar Yeralin (@yeralin)](https://github.com/yeralin "4 total commits to the home-assistant organization: +2 commits to home-assistant.io 1 commit to homebridge-homeassistant 1 commit to home-assistant -1 commit to home-assistant.io ") - [Daniël van de Giessen (@DvdGiessen)](https://github.com/DvdGiessen "2 total commits to the home-assistant organization: 2 commits to open-zwave @@ -2263,9 +2289,9 @@ This page contains a list of people who have contributed in one way or another t - [David Earl (@davidearl)](https://github.com/davidearl "1 total commits to the home-assistant organization: 1 commit to dehydrated ") -- [David F\. Mulcahey (@dmulcahey)](https://github.com/dmulcahey "24 total commits to the home-assistant organization: -20 commits to home-assistant -3 commits to home-assistant-polymer +- [David F\. Mulcahey (@dmulcahey)](https://github.com/dmulcahey "26 total commits to the home-assistant organization: +21 commits to home-assistant +4 commits to home-assistant-polymer 1 commit to home-assistant.io ") - [David Fiel (@dfiel)](https://github.com/dfiel "3 total commits to the home-assistant organization: @@ -2367,8 +2393,8 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant ") - [Dean Camera (@abcminiuser)](https://github.com/abcminiuser "4 total commits to the home-assistant organization: -2 commits to home-assistant.io 2 commits to home-assistant +2 commits to home-assistant.io ") - [definitio (@definitio)](https://github.com/definitio "4 total commits to the home-assistant organization: 2 commits to home-assistant @@ -2488,8 +2514,8 @@ This page contains a list of people who have contributed in one way or another t - [Diogo Alves (@killercode)](https://github.com/killercode "2 total commits to the home-assistant organization: 2 commits to open-zwave ") -- [Diogo Gomes (@dgomes)](https://github.com/dgomes "88 total commits to the home-assistant organization: -59 commits to home-assistant +- [Diogo Gomes (@dgomes)](https://github.com/dgomes "89 total commits to the home-assistant organization: +60 commits to home-assistant 28 commits to home-assistant.io 1 commit to developers.home-assistant ") @@ -2608,9 +2634,9 @@ This page contains a list of people who have contributed in one way or another t - [dtorner (@dtorner)](https://github.com/dtorner "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [DubhAd (@DubhAd)](https://github.com/DubhAd "537 total commits to the home-assistant organization: -531 commits to home-assistant.io -2 commits to developers.home-assistant +- [DubhAd (@DubhAd)](https://github.com/DubhAd "540 total commits to the home-assistant organization: +533 commits to home-assistant.io +3 commits to developers.home-assistant 2 commits to hassos 1 commit to appdaemon 1 commit to home-assistant @@ -2682,11 +2708,11 @@ This page contains a list of people who have contributed in one way or another t 9 commits to home-assistant 3 commits to home-assistant.io ") -- [ehendrix23 (@ehendrix23)](https://github.com/ehendrix23 "32 total commits to the home-assistant organization: -26 commits to home-assistant +- [ehendrix23 (@ehendrix23)](https://github.com/ehendrix23 "34 total commits to the home-assistant organization: +28 commits to home-assistant 4 commits to home-assistant.io -1 commit to home-assistant-polymer 1 commit to pyharmony +1 commit to home-assistant-polymer ") - [eiaro (@eiaro)](https://github.com/eiaro "4 total commits to the home-assistant organization: 4 commits to home-assistant @@ -2718,8 +2744,8 @@ This page contains a list of people who have contributed in one way or another t - [Elias Karakoulakis (@ekarak)](https://github.com/ekarak "8 total commits to the home-assistant organization: 8 commits to open-zwave ") -- [Eliseo Martelli (@eliseomartelli)](https://github.com/eliseomartelli "17 total commits to the home-assistant organization: -12 commits to home-assistant +- [Eliseo Martelli (@eliseomartelli)](https://github.com/eliseomartelli "19 total commits to the home-assistant organization: +14 commits to home-assistant 5 commits to home-assistant.io ") - [Ellis Percival (@flyte)](https://github.com/flyte "31 total commits to the home-assistant organization: @@ -2771,9 +2797,9 @@ This page contains a list of people who have contributed in one way or another t - [Emmanuel Mwangi (@cloudbring)](https://github.com/cloudbring "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [emontnemery (@emontnemery)](https://github.com/emontnemery "111 total commits to the home-assistant organization: -89 commits to home-assistant -21 commits to home-assistant.io +- [emontnemery (@emontnemery)](https://github.com/emontnemery "125 total commits to the home-assistant organization: +102 commits to home-assistant +22 commits to home-assistant.io 1 commit to developers.home-assistant ") - [Emre Saglam (@emresaglam)](https://github.com/emresaglam "1 total commits to the home-assistant organization: @@ -2917,12 +2943,12 @@ This page contains a list of people who have contributed in one way or another t - [Ezra Bowden (@bn0)](https://github.com/bn0 "2 total commits to the home-assistant organization: 2 commits to warrant ") -- [Fabian Affolter (@fabaff)](https://github.com/fabaff "5311 total commits to the home-assistant organization: -3241 commits to home-assistant.io -1838 commits to home-assistant -47 commits to home-assistant-cli +- [Fabian Affolter (@fabaff)](https://github.com/fabaff "5326 total commits to the home-assistant organization: +3250 commits to home-assistant.io +1842 commits to home-assistant +48 commits to home-assistant-cli 36 commits to home-assistant-notebooks -35 commits to developers.home-assistant +36 commits to developers.home-assistant 33 commits to home-assistant-assets 18 commits to organization-internal 12 commits to hassio-build @@ -2944,9 +2970,9 @@ This page contains a list of people who have contributed in one way or another t - [Fabian Heredia Montiel (@fabianhjr)](https://github.com/fabianhjr "4 total commits to the home-assistant organization: 4 commits to home-assistant ") -- [Fabien Piuzzi (@reefab)](https://github.com/reefab "8 total commits to the home-assistant organization: -4 commits to home-assistant -3 commits to home-assistant.io +- [Fabien Piuzzi (@reefab)](https://github.com/reefab "12 total commits to the home-assistant organization: +7 commits to home-assistant +4 commits to home-assistant.io 1 commit to home-assistant-polymer ") - [Fabrice Fontaine (@ffontaine)](https://github.com/ffontaine "7 total commits to the home-assistant organization: @@ -3028,6 +3054,9 @@ This page contains a list of people who have contributed in one way or another t 8 commits to home-assistant 1 commit to home-assistant.io ") +- [finity69x2 (@finity69x2)](https://github.com/finity69x2 "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [firstmentoring (@firstmentoring)](https://github.com/firstmentoring "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") @@ -3111,19 +3140,21 @@ This page contains a list of people who have contributed in one way or another t - [fran1987 (@fran1987)](https://github.com/fran1987 "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Franck Nijhof (@frenck)](https://github.com/frenck "99 total commits to the home-assistant organization: -52 commits to home-assistant.io +- [Franck Nijhof (@frenck)](https://github.com/frenck "116 total commits to the home-assistant organization: +66 commits to home-assistant.io 15 commits to hassio-cli -11 commits to hassio +12 commits to hassio 8 commits to developers.home-assistant +5 commits to hassio-addons 5 commits to home-assistant -4 commits to hassio-addons -2 commits to home-assistant-polymer +3 commits to home-assistant-polymer 1 commit to appdaemon 1 commit to data.home-assistant ") -- [Frank (@syphernl)](https://github.com/syphernl "1 total commits to the home-assistant organization: +- [Frank (@syphernl)](https://github.com/syphernl "3 total commits to the home-assistant organization: 1 commit to home-assistant-polymer +1 commit to home-assistant +1 commit to home-assistant.io ") - [Frank Niesten (@Frankniesten)](https://github.com/Frankniesten "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -3158,8 +3189,8 @@ This page contains a list of people who have contributed in one way or another t 1 commit to developers.home-assistant 1 commit to home-assistant ") -- [Fredrik Erlandsson (@fredrike)](https://github.com/fredrike "28 total commits to the home-assistant organization: -26 commits to home-assistant +- [Fredrik Erlandsson (@fredrike)](https://github.com/fredrike "29 total commits to the home-assistant organization: +27 commits to home-assistant 2 commits to home-assistant.io ") - [Fredrik Fjeld (@fredrikfjeld)](https://github.com/fredrikfjeld "2 total commits to the home-assistant organization: @@ -3205,9 +3236,9 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant.io ") - [Gabriel Oliveira (@gabrielboliveira)](https://github.com/gabrielboliveira "4 total commits to the home-assistant organization: -1 commit to home-assistant-polymer 1 commit to hassio-addons 1 commit to hassos +1 commit to home-assistant-polymer 1 commit to home-assistant.io ") - [GadgetReactor (@GadgetReactor)](https://github.com/GadgetReactor "2 total commits to the home-assistant organization: @@ -3219,8 +3250,8 @@ This page contains a list of people who have contributed in one way or another t - [Galtwise (@Galtwise)](https://github.com/Galtwise "3 total commits to the home-assistant organization: 3 commits to home-assistant.io ") -- [Gamester17 (@Gamester17)](https://github.com/Gamester17 "2 total commits to the home-assistant organization: -2 commits to home-assistant.io +- [Gamester17 (@Gamester17)](https://github.com/Gamester17 "4 total commits to the home-assistant organization: +4 commits to home-assistant.io ") - [Garret Heaton (@powdahound)](https://github.com/powdahound "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -3228,6 +3259,9 @@ This page contains a list of people who have contributed in one way or another t - [garrettbeachy (@garrettbeachy)](https://github.com/garrettbeachy "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") +- [Gary Barclay (@Bodge-IT)](https://github.com/Bodge-IT "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [GaryOkie (@GaryOkie)](https://github.com/GaryOkie "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -3295,13 +3329,13 @@ This page contains a list of people who have contributed in one way or another t - [georgroehl (@georgroehl)](https://github.com/georgroehl "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [Gerard (@erorus)](https://github.com/erorus "1 total commits to the home-assistant organization: +1 commit to dehydrated +") - [Gerard (@gerard33)](https://github.com/gerard33 "22 total commits to the home-assistant organization: 13 commits to home-assistant.io 9 commits to home-assistant ") -- [Gerard (@erorus)](https://github.com/erorus "1 total commits to the home-assistant organization: -1 commit to dehydrated -") - [Gerardo Castillo (@altersis)](https://github.com/altersis "1 total commits to the home-assistant organization: 1 commit to home-assistant ") @@ -3388,8 +3422,8 @@ This page contains a list of people who have contributed in one way or another t - [Glenn Waters (@gwww)](https://github.com/gwww "19 total commits to the home-assistant organization: 11 commits to home-assistant 6 commits to home-assistant.io -1 commit to home-assistant-polymer 1 commit to developers.home-assistant +1 commit to home-assistant-polymer ") - [glenn20 (@glenn20)](https://github.com/glenn20 "2 total commits to the home-assistant organization: 1 commit to home-assistant @@ -3658,6 +3692,9 @@ This page contains a list of people who have contributed in one way or another t - [henryk (@henryk)](https://github.com/henryk "1 total commits to the home-assistant organization: 1 commit to home-assistant ") +- [Heriberto Madrigal (@magic-madrigal)](https://github.com/magic-madrigal "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Hermann Kraus (@herm)](https://github.com/herm "2 total commits to the home-assistant organization: 1 commit to home-assistant 1 commit to home-assistant.io @@ -3771,6 +3808,9 @@ This page contains a list of people who have contributed in one way or another t - [IainPHay (@IainPHay)](https://github.com/IainPHay "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") +- [iainsmacleod (@iainsmacleod)](https://github.com/iainsmacleod "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Ian (@Apocrathia)](https://github.com/Apocrathia "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -3783,9 +3823,9 @@ This page contains a list of people who have contributed in one way or another t - [Ian Day (@iandday)](https://github.com/iandday "16 total commits to the home-assistant organization: 16 commits to pyharmony ") -- [Ian Richardson (@iantrich)](https://github.com/iantrich "145 total commits to the home-assistant organization: -112 commits to home-assistant-polymer -25 commits to home-assistant.io +- [Ian Richardson (@iantrich)](https://github.com/iantrich "150 total commits to the home-assistant organization: +113 commits to home-assistant-polymer +29 commits to home-assistant.io 6 commits to home-assistant 2 commits to developers.home-assistant ") @@ -3828,8 +3868,8 @@ This page contains a list of people who have contributed in one way or another t - [IIIdefconIII (@IIIdefconIII)](https://github.com/IIIdefconIII "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") -- [ikifar2012 (@ikifar2012)](https://github.com/ikifar2012 "2 total commits to the home-assistant organization: -2 commits to home-assistant.io +- [ikifar2012 (@ikifar2012)](https://github.com/ikifar2012 "3 total commits to the home-assistant organization: +3 commits to home-assistant.io ") - [ikonixx (@ikonixx)](https://github.com/ikonixx "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -3959,6 +3999,9 @@ This page contains a list of people who have contributed in one way or another t - [Jake McCrary (@jakemcc)](https://github.com/jakemcc "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") +- [jakecolman (@jakecolman)](https://github.com/jakecolman "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Jakob Reiter (@jakommo)](https://github.com/jakommo "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -4090,8 +4133,8 @@ This page contains a list of people who have contributed in one way or another t - [Jason Hite (@jasonmhite)](https://github.com/jasonmhite "6 total commits to the home-assistant organization: 6 commits to appdaemon ") -- [Jason Hu (@awarecan)](https://github.com/awarecan "168 total commits to the home-assistant organization: -109 commits to home-assistant +- [Jason Hu (@awarecan)](https://github.com/awarecan "169 total commits to the home-assistant organization: +110 commits to home-assistant 27 commits to home-assistant.io 21 commits to home-assistant-polymer 9 commits to developers.home-assistant @@ -4128,8 +4171,8 @@ This page contains a list of people who have contributed in one way or another t - [Jason Woodward (@woodwardjd)](https://github.com/woodwardjd "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Jasper van der Neut \- Stulen (@jvanderneutstulen)](https://github.com/jvanderneutstulen "7 total commits to the home-assistant organization: -7 commits to hassos +- [Jasper van der Neut \- Stulen (@jvanderneutstulen)](https://github.com/jvanderneutstulen "8 total commits to the home-assistant organization: +8 commits to hassos ") - [javicalle (@javicalle)](https://github.com/javicalle "6 total commits to the home-assistant organization: 4 commits to home-assistant @@ -4171,8 +4214,8 @@ This page contains a list of people who have contributed in one way or another t 7 commits to home-assistant.io 6 commits to home-assistant ") -- [Jc2k (@Jc2k)](https://github.com/Jc2k "2 total commits to the home-assistant organization: -2 commits to home-assistant +- [Jc2k (@Jc2k)](https://github.com/Jc2k "3 total commits to the home-assistant organization: +3 commits to home-assistant ") - [jchasey (@jchasey)](https://github.com/jchasey "1 total commits to the home-assistant organization: 1 commit to developers.home-assistant @@ -4418,8 +4461,8 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant 1 commit to home-assistant.io ") -- [Joakim Nohlgård (@gebart)](https://github.com/gebart "2 total commits to the home-assistant organization: -2 commits to libcoap +- [Joakim Lindbom (@JoakimLindbom)](https://github.com/JoakimLindbom "1 total commits to the home-assistant organization: +1 commit to home-assistant ") - [Joakim Plate (@elupus)](https://github.com/elupus "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -4442,6 +4485,9 @@ This page contains a list of people who have contributed in one way or another t - [Joe Francis (@lostapathy)](https://github.com/lostapathy "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [Joe Garcia\, CISSP (@infamousjoeg)](https://github.com/infamousjoeg "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Joe Gross (@joegross)](https://github.com/joegross "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -4509,9 +4555,9 @@ This page contains a list of people who have contributed in one way or another t 3 commits to home-assistant.io 1 commit to appdaemon ") -- [Johann Kellerman (@kellerza)](https://github.com/kellerza "190 total commits to the home-assistant organization: -154 commits to home-assistant -35 commits to home-assistant.io +- [Johann Kellerman (@kellerza)](https://github.com/kellerza "194 total commits to the home-assistant organization: +157 commits to home-assistant +36 commits to home-assistant.io 1 commit to developers.home-assistant ") - [Johannes Innerbichler (@jinnerbichler)](https://github.com/jinnerbichler "2 total commits to the home-assistant organization: @@ -4588,9 +4634,9 @@ This page contains a list of people who have contributed in one way or another t - [Jon Calderín Goñi (@jcalderin)](https://github.com/jcalderin "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Jon Caruana (@joncar)](https://github.com/joncar "5 total commits to the home-assistant organization: -3 commits to home-assistant -2 commits to home-assistant.io +- [Jon Caruana (@joncar)](https://github.com/joncar "7 total commits to the home-assistant organization: +4 commits to home-assistant +3 commits to home-assistant.io ") - [Jon Evans (@craftyjon)](https://github.com/craftyjon "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -4613,12 +4659,14 @@ This page contains a list of people who have contributed in one way or another t 1 commit to hassio-build 1 commit to home-assistant ") -- [Jonas Pedersen (@JonasPed)](https://github.com/JonasPed "2 total commits to the home-assistant organization: +- [Jonas Pedersen (@JonasPed)](https://github.com/JonasPed "5 total commits to the home-assistant organization: +2 commits to home-assistant.io 1 commit to appdaemon -1 commit to home-assistant.io +1 commit to developers.home-assistant +1 commit to home-assistant ") -- [Jonas Skoogh (@hAmpzter)](https://github.com/hAmpzter "6 total commits to the home-assistant organization: -5 commits to home-assistant.io +- [Jonas Skoogh (@hAmpzter)](https://github.com/hAmpzter "7 total commits to the home-assistant organization: +6 commits to home-assistant.io 1 commit to home-assistant ") - [Jonatan Castro (@jcastro)](https://github.com/jcastro "7 total commits to the home-assistant organization: @@ -4633,9 +4681,9 @@ This page contains a list of people who have contributed in one way or another t - [Jonathan Herlin (@Jonher937)](https://github.com/Jonher937 "3 total commits to the home-assistant organization: 3 commits to home-assistant.io ") -- [Jonathan Keljo (@jkeljo)](https://github.com/jkeljo "7 total commits to the home-assistant organization: +- [Jonathan Keljo (@jkeljo)](https://github.com/jkeljo "9 total commits to the home-assistant organization: +5 commits to home-assistant.io 4 commits to home-assistant -3 commits to home-assistant.io ") - [Jonathan Martens (@jmartens)](https://github.com/jmartens "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -4677,13 +4725,13 @@ This page contains a list of people who have contributed in one way or another t 40 commits to home-assistant 3 commits to home-assistant.io ") -- [Jorim Tielemans (@tjorim)](https://github.com/tjorim "91 total commits to the home-assistant organization: -76 commits to home-assistant.io +- [Jorim Tielemans (@tjorim)](https://github.com/tjorim "94 total commits to the home-assistant organization: +79 commits to home-assistant.io 6 commits to home-assistant 2 commits to hassio-cli +2 commits to developers.home-assistant 2 commits to hassio-addons 2 commits to hassio -2 commits to developers.home-assistant 1 commit to hassio-build ") - [jorisc90 (@jorisc90)](https://github.com/jorisc90 "1 total commits to the home-assistant organization: @@ -4961,8 +5009,8 @@ This page contains a list of people who have contributed in one way or another t 2 commits to home-assistant.io 1 commit to home-assistant ") -- [kbickar (@kbickar)](https://github.com/kbickar "8 total commits to the home-assistant organization: -6 commits to home-assistant +- [kbickar (@kbickar)](https://github.com/kbickar "9 total commits to the home-assistant organization: +7 commits to home-assistant 2 commits to home-assistant.io ") - [KD4SIR (@scotthibbs)](https://github.com/scotthibbs "1 total commits to the home-assistant organization: @@ -5009,9 +5057,9 @@ This page contains a list of people who have contributed in one way or another t 13 commits to home-assistant.io 2 commits to appdaemon ") -- [kennedyshead (@kennedyshead)](https://github.com/kennedyshead "45 total commits to the home-assistant organization: +- [kennedyshead (@kennedyshead)](https://github.com/kennedyshead "46 total commits to the home-assistant organization: 41 commits to home-assistant -4 commits to home-assistant.io +5 commits to home-assistant.io ") - [Kenny Millington (@kmdm)](https://github.com/kmdm "2 total commits to the home-assistant organization: 2 commits to home-assistant @@ -5022,8 +5070,9 @@ This page contains a list of people who have contributed in one way or another t - [Kent Hua (@kenthua)](https://github.com/kenthua "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [kernehed (@kernehed)](https://github.com/kernehed "7 total commits to the home-assistant organization: +- [kernehed (@kernehed)](https://github.com/kernehed "11 total commits to the home-assistant organization: 7 commits to home-assistant.io +4 commits to home-assistant-polymer ") - [Kerwin Bryant (@ileler)](https://github.com/ileler "3 total commits to the home-assistant organization: 2 commits to home-assistant @@ -5051,8 +5100,8 @@ This page contains a list of people who have contributed in one way or another t - [Kevin Fowlks (@kfowlks)](https://github.com/kfowlks "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "31 total commits to the home-assistant organization: -19 commits to home-assistant +- [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "32 total commits to the home-assistant organization: +20 commits to home-assistant 12 commits to home-assistant.io ") - [Kevin Gisi (@gisikw)](https://github.com/gisikw "5 total commits to the home-assistant organization: @@ -5125,12 +5174,12 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant.io ") - [Klaas Hoekema (@KlaasH)](https://github.com/KlaasH "12 total commits to the home-assistant organization: -5 commits to home-assistant 5 commits to home-assistant.io +5 commits to home-assistant 2 commits to home-assistant-polymer ") -- [Klaas Schoute (@klaasnicolaas)](https://github.com/klaasnicolaas "286 total commits to the home-assistant organization: -286 commits to home-assistant.io +- [Klaas Schoute (@klaasnicolaas)](https://github.com/klaasnicolaas "287 total commits to the home-assistant organization: +287 commits to home-assistant.io ") - [Klaudiusz Staniek (@kstaniek)](https://github.com/kstaniek "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -5167,8 +5216,9 @@ This page contains a list of people who have contributed in one way or another t - [kophinos (@kophinos)](https://github.com/kophinos "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [koreth (@koreth)](https://github.com/koreth "1 total commits to the home-assistant organization: -1 commit to home-assistant +- [koreth (@koreth)](https://github.com/koreth "4 total commits to the home-assistant organization: +3 commits to home-assistant +1 commit to home-assistant.io ") - [Kory Prince (@korylprince)](https://github.com/korylprince "4 total commits to the home-assistant organization: 4 commits to home-assistant-polymer @@ -5192,8 +5242,13 @@ This page contains a list of people who have contributed in one way or another t - [KristjanLaane (@KristjanLaane)](https://github.com/KristjanLaane "8 total commits to the home-assistant organization: 8 commits to open-zwave ") -- [kroimon (@kroimon)](https://github.com/kroimon "1 total commits to the home-assistant organization: +- [kroimon (@kroimon)](https://github.com/kroimon "2 total commits to the home-assistant organization: 1 commit to netdisco +1 commit to hassio-addons +") +- [krygal (@krygal)](https://github.com/krygal "2 total commits to the home-assistant organization: +1 commit to home-assistant +1 commit to home-assistant.io ") - [Kumar Gaurav Pandey (@gaurav1911)](https://github.com/gaurav1911 "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -5225,6 +5280,9 @@ This page contains a list of people who have contributed in one way or another t - [kylerw (@kylerw)](https://github.com/kylerw "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [labrunning (@labrunning)](https://github.com/labrunning "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [lamiskin (@lamiskin)](https://github.com/lamiskin "6 total commits to the home-assistant organization: 4 commits to home-assistant.io 2 commits to home-assistant @@ -5409,6 +5467,10 @@ This page contains a list of people who have contributed in one way or another t - [Louis Laureys (@louis-lau)](https://github.com/louis-lau "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") +- [Louis Matthijssen (@LouisMT)](https://github.com/LouisMT "3 total commits to the home-assistant organization: +2 commits to home-assistant.io +1 commit to home-assistant +") - [Louis Orleans (@dudeofawesome)](https://github.com/dudeofawesome "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -5618,9 +5680,9 @@ This page contains a list of people who have contributed in one way or another t 3 commits to home-assistant 2 commits to home-assistant.io ") -- [Malte Franken (@exxamalte)](https://github.com/exxamalte "45 total commits to the home-assistant organization: -28 commits to home-assistant -13 commits to home-assistant.io +- [Malte Franken (@exxamalte)](https://github.com/exxamalte "47 total commits to the home-assistant organization: +29 commits to home-assistant +14 commits to home-assistant.io 3 commits to home-assistant-polymer 1 commit to developers.home-assistant ") @@ -5630,8 +5692,8 @@ This page contains a list of people who have contributed in one way or another t - [Manuel de la Rosa (@manuel-jrs)](https://github.com/manuel-jrs "2 total commits to the home-assistant organization: 2 commits to home-assistant ") -- [Marat Levit (@mlevit)](https://github.com/mlevit "1 total commits to the home-assistant organization: -1 commit to home-assistant.io +- [Marat Levit (@mlevit)](https://github.com/mlevit "3 total commits to the home-assistant organization: +3 commits to home-assistant.io ") - [Marc (@marc-gist)](https://github.com/marc-gist "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -5676,8 +5738,8 @@ This page contains a list of people who have contributed in one way or another t 90 commits to home-assistant 67 commits to home-assistant.io 1 commit to home-assistant-assets -1 commit to home-assistant-polymer 1 commit to hassio-build +1 commit to home-assistant-polymer ") - [Marcin Domański (@kabturek)](https://github.com/kabturek "6 total commits to the home-assistant organization: 4 commits to appdaemon @@ -5964,6 +6026,10 @@ This page contains a list of people who have contributed in one way or another t 2 commits to home-assistant 1 commit to home-assistant.io ") +- [Mateusz Korniak (@matkor)](https://github.com/matkor "2 total commits to the home-assistant organization: +1 commit to home-assistant +1 commit to home-assistant.io +") - [Mathew Peterson (@mathewpeterson)](https://github.com/mathewpeterson "4 total commits to the home-assistant organization: 2 commits to home-assistant.io 1 commit to homebridge-homeassistant @@ -6085,6 +6151,9 @@ This page contains a list of people who have contributed in one way or another t 2 commits to home-assistant 1 commit to home-assistant.io ") +- [Matthew Scoville (@Chaotic)](https://github.com/Chaotic "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Matthew T\. Kelley (@mkelley88)](https://github.com/mkelley88 "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") @@ -6092,6 +6161,10 @@ This page contains a list of people who have contributed in one way or another t 16 commits to home-assistant 9 commits to home-assistant.io ") +- [Matthew Wegner (@mwegner)](https://github.com/mwegner "2 total commits to the home-assistant organization: +1 commit to home-assistant +1 commit to home-assistant.io +") - [Matthew Wire (@mattwire)](https://github.com/mattwire "6 total commits to the home-assistant organization: 6 commits to open-zwave ") @@ -6115,9 +6188,9 @@ This page contains a list of people who have contributed in one way or another t - [Mattias Ryrlén (@mattiasr)](https://github.com/mattiasr "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Mattias Welponer (@mxworm)](https://github.com/mxworm "27 total commits to the home-assistant organization: -17 commits to home-assistant -9 commits to home-assistant.io +- [Mattias Welponer (@mxworm)](https://github.com/mxworm "29 total commits to the home-assistant organization: +18 commits to home-assistant +10 commits to home-assistant.io 1 commit to home-assistant-polymer ") - [mattie47 (@mattie47)](https://github.com/mattie47 "3 total commits to the home-assistant organization: @@ -6161,10 +6234,10 @@ This page contains a list of people who have contributed in one way or another t - [Max Rumpf (@Maxr1998)](https://github.com/Maxr1998 "15 total commits to the home-assistant organization: 15 commits to home-assistant.io ") -- [Max Rydahl Andersen (@maxandersen)](https://github.com/maxandersen "60 total commits to the home-assistant organization: -54 commits to home-assistant-cli +- [Max Rydahl Andersen (@maxandersen)](https://github.com/maxandersen "65 total commits to the home-assistant organization: +58 commits to home-assistant-cli +3 commits to developers.home-assistant 3 commits to home-assistant.io -2 commits to developers.home-assistant 1 commit to home-assistant ") - [Max von Webel (@343max)](https://github.com/343max "1 total commits to the home-assistant organization: @@ -6260,6 +6333,9 @@ This page contains a list of people who have contributed in one way or another t - [Michael (@splunty)](https://github.com/splunty "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [Michael (@mischsa)](https://github.com/mischsa "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Michael Auchter (@auchter)](https://github.com/auchter "13 total commits to the home-assistant organization: 13 commits to home-assistant ") @@ -6442,6 +6518,9 @@ This page contains a list of people who have contributed in one way or another t - [mikebarris (@mikebarris)](https://github.com/mikebarris "1 total commits to the home-assistant organization: 1 commit to home-assistant ") +- [mikehole (@mikehole)](https://github.com/mikehole "1 total commits to the home-assistant organization: +1 commit to developers.home-assistant +") - [Mikkel Hoegh (@mikl)](https://github.com/mikl "3 total commits to the home-assistant organization: 3 commits to home-assistant.io ") @@ -6566,10 +6645,14 @@ This page contains a list of people who have contributed in one way or another t - [Moos (@moos)](https://github.com/moos "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [mopolus (@mopolus)](https://github.com/mopolus "5 total commits to the home-assistant organization: -3 commits to home-assistant +- [mopolus (@mopolus)](https://github.com/mopolus "6 total commits to the home-assistant organization: +4 commits to home-assistant 2 commits to home-assistant.io ") +- [Morgan Kesler (@keslerm)](https://github.com/keslerm "3 total commits to the home-assistant organization: +2 commits to home-assistant +1 commit to home-assistant.io +") - [MORITA Hajime (@omo)](https://github.com/omo "3 total commits to the home-assistant organization: 3 commits to home-assistant.io ") @@ -6682,6 +6765,9 @@ This page contains a list of people who have contributed in one way or another t 13 commits to home-assistant 6 commits to home-assistant.io ") +- [Nate Kleven (@nkleven)](https://github.com/nkleven "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Nate Robinson (@NateRobinsonS)](https://github.com/NateRobinsonS "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -6799,9 +6885,9 @@ This page contains a list of people who have contributed in one way or another t 3 commits to home-assistant.io 2 commits to home-assistant ") -- [Nick Whyte (@nickw444)](https://github.com/nickw444 "13 total commits to the home-assistant organization: +- [Nick Whyte (@nickw444)](https://github.com/nickw444 "14 total commits to the home-assistant organization: 7 commits to home-assistant -6 commits to home-assistant.io +7 commits to home-assistant.io ") - [Nick Zelei (@zelein)](https://github.com/zelein "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -6810,6 +6896,9 @@ This page contains a list of people who have contributed in one way or another t 7 commits to home-assistant 2 commits to home-assistant.io ") +- [nickrout (@nickrout)](https://github.com/nickrout "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Niclas (@nicmar)](https://github.com/nicmar "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -6889,10 +6978,10 @@ This page contains a list of people who have contributed in one way or another t 1 commit to home-assistant 1 commit to home-assistant.io ") -- [Nikolay Vasilchuk (@Anonym-tsk)](https://github.com/Anonym-tsk "11 total commits to the home-assistant organization: -8 commits to home-assistant +- [Nikolay Vasilchuk (@Anonym-tsk)](https://github.com/Anonym-tsk "13 total commits to the home-assistant organization: +9 commits to home-assistant 2 commits to home-assistant-polymer -1 commit to home-assistant.io +2 commits to home-assistant.io ") - [Nils Kristian Brekke (@Brekkjern)](https://github.com/Brekkjern "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -6931,10 +7020,10 @@ This page contains a list of people who have contributed in one way or another t - [normakm (@normakm)](https://github.com/normakm "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [NotoriousBDG (@notoriousbdg)](https://github.com/notoriousbdg "6 total commits to the home-assistant organization: +- [NotoriousBDG (@notoriousbdg)](https://github.com/notoriousbdg "7 total commits to the home-assistant organization: 3 commits to hassio-addons +2 commits to home-assistant 2 commits to home-assistant.io -1 commit to home-assistant ") - [NovapaX (@NovapaX)](https://github.com/NovapaX "60 total commits to the home-assistant organization: 50 commits to home-assistant-polymer @@ -6978,6 +7067,9 @@ This page contains a list of people who have contributed in one way or another t - [Odianosen Ejale (@Odianosen25)](https://github.com/Odianosen25 "53 total commits to the home-assistant organization: 53 commits to appdaemon ") +- [Odin Hørthe Omdal (@odinho)](https://github.com/odinho "1 total commits to the home-assistant organization: +1 commit to home-assistant-polymer +") - [Odin Ugedal (@odinuge)](https://github.com/odinuge "2 total commits to the home-assistant organization: 1 commit to home-assistant 1 commit to home-assistant.io @@ -7103,8 +7195,8 @@ This page contains a list of people who have contributed in one way or another t - [ottersen (@ottersen)](https://github.com/ottersen "11 total commits to the home-assistant organization: 11 commits to home-assistant.io ") -- [Otto Winter (@OttoWinter)](https://github.com/OttoWinter "134 total commits to the home-assistant organization: -98 commits to home-assistant +- [Otto Winter (@OttoWinter)](https://github.com/OttoWinter "136 total commits to the home-assistant organization: +100 commits to home-assistant 25 commits to home-assistant.io 5 commits to home-assistant-polymer 3 commits to hass-release @@ -7156,15 +7248,15 @@ This page contains a list of people who have contributed in one way or another t - [Pascal Jungblut (@pascalj)](https://github.com/pascalj "1 total commits to the home-assistant organization: 1 commit to dehydrated ") -- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "4094 total commits to the home-assistant organization: -1476 commits to hassio -723 commits to hassos -510 commits to home-assistant -479 commits to hassio-build -393 commits to hassio-addons -345 commits to home-assistant.io +- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "4119 total commits to the home-assistant organization: +1486 commits to hassio +729 commits to hassos +511 commits to home-assistant +481 commits to hassio-build +397 commits to hassio-addons +346 commits to home-assistant.io 56 commits to hassio-homeassistant -29 commits to developers.home-assistant +30 commits to developers.home-assistant 20 commits to hassio-cli 20 commits to hassio-base 18 commits to hassio-auth @@ -7183,14 +7275,17 @@ This page contains a list of people who have contributed in one way or another t - [Pat Thoyts (@patthoyts)](https://github.com/patthoyts "2 total commits to the home-assistant organization: 2 commits to netdisco ") +- [patatman (@patatman)](https://github.com/patatman "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [patkap (@patkap)](https://github.com/patkap "2 total commits to the home-assistant organization: 2 commits to home-assistant ") - [patock (@patock)](https://github.com/patock "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Patrick (@tradiuz)](https://github.com/tradiuz "6 total commits to the home-assistant organization: -6 commits to home-assistant.io +- [Patrick (@tradiuz)](https://github.com/tradiuz "7 total commits to the home-assistant organization: +7 commits to home-assistant.io ") - [Patrick Aikens (@duckpuppy)](https://github.com/duckpuppy "3 total commits to the home-assistant organization: 3 commits to home-assistant.io @@ -7287,9 +7382,9 @@ This page contains a list of people who have contributed in one way or another t - [Pavol Babinčák (@scrool)](https://github.com/scrool "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Pawel (@pszafer)](https://github.com/pszafer "10 total commits to the home-assistant organization: +- [Pawel (@pszafer)](https://github.com/pszafer "11 total commits to the home-assistant organization: 6 commits to home-assistant -4 commits to home-assistant.io +5 commits to home-assistant.io ") - [Pawel Winogrodzki (@PawelWMS)](https://github.com/PawelWMS "12 total commits to the home-assistant organization: 12 commits to libcoap @@ -7424,8 +7519,8 @@ This page contains a list of people who have contributed in one way or another t - [Phil (@godloth)](https://github.com/godloth "10 total commits to the home-assistant organization: 10 commits to home-assistant.io ") -- [Phil (@pnbruckner)](https://github.com/pnbruckner "3 total commits to the home-assistant organization: -2 commits to home-assistant +- [Phil (@pnbruckner)](https://github.com/pnbruckner "4 total commits to the home-assistant organization: +3 commits to home-assistant 1 commit to home-assistant.io ") - [Phil Cole (@filcole)](https://github.com/filcole "9 total commits to the home-assistant organization: @@ -7750,6 +7845,9 @@ This page contains a list of people who have contributed in one way or another t - [rctgamer3 (@rctgamer3)](https://github.com/rctgamer3 "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [rdkayman (@rdkayman)](https://github.com/rdkayman "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [Rebecca Cran (@bcran)](https://github.com/bcran "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -7835,8 +7933,9 @@ This page contains a list of people who have contributed in one way or another t - [Richard Lucas (@lucasweb78)](https://github.com/lucasweb78 "9 total commits to the home-assistant organization: 9 commits to home-assistant ") -- [Richard Mitchell (@mitchellrj)](https://github.com/mitchellrj "1 total commits to the home-assistant organization: -1 commit to home-assistant +- [Richard Mitchell (@mitchellrj)](https://github.com/mitchellrj "4 total commits to the home-assistant organization: +2 commits to home-assistant +2 commits to home-assistant.io ") - [Richard Niemand (@rniemand)](https://github.com/rniemand "1 total commits to the home-assistant organization: 1 commit to example-custom-config @@ -7900,8 +7999,8 @@ This page contains a list of people who have contributed in one way or another t - [Rob Slifka (@rslifka)](https://github.com/rslifka "5 total commits to the home-assistant organization: 5 commits to home-assistant.io ") -- [Robbert Müller (@mjrider)](https://github.com/mjrider "5 total commits to the home-assistant organization: -2 commits to hassio-cli +- [Robbert Müller (@mjrider)](https://github.com/mjrider "9 total commits to the home-assistant organization: +6 commits to hassio-cli 2 commits to home-assistant.io 1 commit to home-assistant ") @@ -7924,19 +8023,19 @@ This page contains a list of people who have contributed in one way or another t 6 commits to netdisco 5 commits to organization-internal 3 commits to scenegen +3 commits to home-assistant-js 3 commits to hadashboard 3 commits to organization -3 commits to hassbot -3 commits to home-assistant-js-websocket 3 commits to home-assistant-cli +3 commits to home-assistant-js-websocket +3 commits to hassbot 3 commits to appdaemon -3 commits to home-assistant-js 3 commits to open-zwave -2 commits to fabric-home-assistant -2 commits to lambda-home-assistant-github 2 commits to home-assistant-notebooks -2 commits to LabelBot +2 commits to fabric-home-assistant 2 commits to home-assistant-assets +2 commits to LabelBot +2 commits to lambda-home-assistant-github 2 commits to micropython-home-assistant ") - [Robby Grossman (@freerobby)](https://github.com/freerobby "3 total commits to the home-assistant organization: @@ -7977,8 +8076,8 @@ This page contains a list of people who have contributed in one way or another t 1 commit to appdaemon 1 commit to home-assistant ") -- [Robert Svensson (@Kane610)](https://github.com/Kane610 "97 total commits to the home-assistant organization: -63 commits to home-assistant +- [Robert Svensson (@Kane610)](https://github.com/Kane610 "99 total commits to the home-assistant organization: +65 commits to home-assistant 30 commits to home-assistant.io 2 commits to developers.home-assistant 1 commit to netdisco @@ -7987,8 +8086,8 @@ This page contains a list of people who have contributed in one way or another t - [robhuls (@robhuls)](https://github.com/robhuls "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [Robin (@robmarkcole)](https://github.com/robmarkcole "74 total commits to the home-assistant organization: -48 commits to home-assistant.io +- [Robin (@robmarkcole)](https://github.com/robmarkcole "75 total commits to the home-assistant organization: +49 commits to home-assistant.io 20 commits to home-assistant 2 commits to home-assistant-notebooks 2 commits to home-assistant-assets @@ -8015,9 +8114,9 @@ This page contains a list of people who have contributed in one way or another t 6 commits to home-assistant.io 3 commits to open-zwave ") -- [Rohan Kapoor (@rohankapoorcom)](https://github.com/rohankapoorcom "45 total commits to the home-assistant organization: -32 commits to home-assistant -13 commits to home-assistant.io +- [Rohan Kapoor (@rohankapoorcom)](https://github.com/rohankapoorcom "70 total commits to the home-assistant organization: +51 commits to home-assistant +19 commits to home-assistant.io ") - [Roi Dayan (@roidayan)](https://github.com/roidayan "7 total commits to the home-assistant organization: 6 commits to home-assistant @@ -8030,6 +8129,9 @@ This page contains a list of people who have contributed in one way or another t - [Rolf Schäuble (@rschaeuble)](https://github.com/rschaeuble "6 total commits to the home-assistant organization: 6 commits to appdaemon ") +- [rolfberkenbosch (@rolfberkenbosch)](https://github.com/rolfberkenbosch "1 total commits to the home-assistant organization: +1 commit to home-assistant +") - [rollbrettler (@rollbrettler)](https://github.com/rollbrettler "2 total commits to the home-assistant organization: 1 commit to home-assistant 1 commit to home-assistant.io @@ -8162,8 +8264,8 @@ This page contains a list of people who have contributed in one way or another t 5 commits to home-assistant.io 2 commits to home-assistant ") -- [Ryan Bray (@rbray89)](https://github.com/rbray89 "17 total commits to the home-assistant organization: -14 commits to hassos +- [Ryan Bray (@rbray89)](https://github.com/rbray89 "19 total commits to the home-assistant organization: +16 commits to hassos 2 commits to home-assistant.io 1 commit to hassio-build ") @@ -8316,6 +8418,9 @@ This page contains a list of people who have contributed in one way or another t - [Saurabh Sharma (@saurabhsharma001)](https://github.com/saurabhsharma001 "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [Sbaa1 (@Sbaa1)](https://github.com/Sbaa1 "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [sbYm (@GongT)](https://github.com/GongT "1 total commits to the home-assistant organization: 1 commit to home-assistant-polymer ") @@ -8440,9 +8545,9 @@ This page contains a list of people who have contributed in one way or another t - [Sebastian (@sgso)](https://github.com/sgso "3 total commits to the home-assistant organization: 3 commits to libcoap ") -- [Sebastian Muszynski (@syssi)](https://github.com/syssi "174 total commits to the home-assistant organization: -114 commits to home-assistant -55 commits to home-assistant.io +- [Sebastian Muszynski (@syssi)](https://github.com/syssi "177 total commits to the home-assistant organization: +116 commits to home-assistant +56 commits to home-assistant.io 3 commits to netdisco 2 commits to home-assistant-polymer ") @@ -8505,6 +8610,9 @@ This page contains a list of people who have contributed in one way or another t - [Shawna (@cherrykoda)](https://github.com/cherrykoda "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") +- [shbatm (@shbatm)](https://github.com/shbatm "1 total commits to the home-assistant organization: +1 commit to home-assistant +") - [Shiny (@Br3nda)](https://github.com/Br3nda "4 total commits to the home-assistant organization: 3 commits to home-assistant.io 1 commit to developers.home-assistant @@ -8512,8 +8620,8 @@ This page contains a list of people who have contributed in one way or another t - [shker (@serhtt)](https://github.com/serhtt "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [shred86 (@shred86)](https://github.com/shred86 "3 total commits to the home-assistant organization: -2 commits to home-assistant +- [shred86 (@shred86)](https://github.com/shred86 "4 total commits to the home-assistant organization: +3 commits to home-assistant 1 commit to home-assistant.io ") - [shuaiger (@shuaiger)](https://github.com/shuaiger "1 total commits to the home-assistant organization: @@ -8548,9 +8656,9 @@ This page contains a list of people who have contributed in one way or another t ") - [Simon Holzmayer (@sholzmayer)](https://github.com/sholzmayer "5 total commits to the home-assistant organization: 2 commits to hassos -1 commit to home-assistant-polymer -1 commit to hassio 1 commit to developers.home-assistant +1 commit to hassio +1 commit to home-assistant-polymer ") - [Simon Hörrle (@CM000n)](https://github.com/CM000n "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -8626,9 +8734,9 @@ This page contains a list of people who have contributed in one way or another t - [snizzleorg (@snizzleorg)](https://github.com/snizzleorg "5 total commits to the home-assistant organization: 5 commits to hadashboard ") -- [SNoof85 (@SNoof85)](https://github.com/SNoof85 "4 total commits to the home-assistant organization: +- [SNoof85 (@SNoof85)](https://github.com/SNoof85 "5 total commits to the home-assistant organization: 3 commits to home-assistant -1 commit to home-assistant.io +2 commits to home-assistant.io ") - [so3n (@so3n)](https://github.com/so3n "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -8652,8 +8760,9 @@ This page contains a list of people who have contributed in one way or another t - [spektren (@spektren)](https://github.com/spektren "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [Spencer Oberstadt (@soberstadt)](https://github.com/soberstadt "1 total commits to the home-assistant organization: -1 commit to home-assistant +- [Spencer Oberstadt (@soberstadt)](https://github.com/soberstadt "3 total commits to the home-assistant organization: +2 commits to home-assistant +1 commit to home-assistant.io ") - [Spencer Owen (@spuder)](https://github.com/spuder "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -8693,11 +8802,11 @@ This page contains a list of people who have contributed in one way or another t - [staraxis (@staraxis)](https://github.com/staraxis "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [starkillerOG (@starkillerOG)](https://github.com/starkillerOG "12 total commits to the home-assistant organization: -6 commits to home-assistant +- [starkillerOG (@starkillerOG)](https://github.com/starkillerOG "13 total commits to the home-assistant organization: +7 commits to home-assistant 4 commits to home-assistant.io -1 commit to home-assistant-polymer 1 commit to developers.home-assistant +1 commit to home-assistant-polymer ") - [Stavros Korokithakis (@skorokithakis)](https://github.com/skorokithakis "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -8754,8 +8863,8 @@ This page contains a list of people who have contributed in one way or another t ") - [Stephen Vanterpool (@blackgold9)](https://github.com/blackgold9 "115 total commits to the home-assistant organization: 113 commits to home-assistant-iOS -1 commit to home-assistant-polymer 1 commit to developers.home-assistant +1 commit to home-assistant-polymer ") - [Stephen Yeargin (@stephenyeargin)](https://github.com/stephenyeargin "27 total commits to the home-assistant organization: 24 commits to hubot-home-assistant @@ -8886,8 +8995,8 @@ This page contains a list of people who have contributed in one way or another t 6 commits to home-assistant.io 2 commits to home-assistant-cli 2 commits to home-assistant -1 commit to hassio-build 1 commit to developers.home-assistant +1 commit to hassio-build ") - [szaroubi (@szaroubi)](https://github.com/szaroubi "1 total commits to the home-assistant organization: 1 commit to home-assistant.io @@ -8950,8 +9059,8 @@ This page contains a list of people who have contributed in one way or another t 9 commits to home-assistant.io 1 commit to home-assistant-js ") -- [Ted Drain (@TD22057)](https://github.com/TD22057 "6 total commits to the home-assistant organization: -4 commits to home-assistant +- [Ted Drain (@TD22057)](https://github.com/TD22057 "7 total commits to the home-assistant organization: +5 commits to home-assistant 2 commits to home-assistant.io ") - [Ted Kulp (@tedkulp)](https://github.com/tedkulp "1 total commits to the home-assistant organization: @@ -8975,9 +9084,9 @@ This page contains a list of people who have contributed in one way or another t - [Teemu Patja (@tpatja)](https://github.com/tpatja "2 total commits to the home-assistant organization: 2 commits to home-assistant ") -- [Teemu R\. (@rytilahti)](https://github.com/rytilahti "68 total commits to the home-assistant organization: -52 commits to home-assistant -10 commits to home-assistant.io +- [Teemu R\. (@rytilahti)](https://github.com/rytilahti "72 total commits to the home-assistant organization: +54 commits to home-assistant +12 commits to home-assistant.io 4 commits to netdisco 2 commits to home-assistant-cli ") @@ -9000,6 +9109,9 @@ This page contains a list of people who have contributed in one way or another t 2 commits to home-assistant.io 1 commit to home-assistant ") +- [Test GITHub account (@YogoGit)](https://github.com/YogoGit "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [tfitts (@tfitts)](https://github.com/tfitts "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -9084,9 +9196,9 @@ This page contains a list of people who have contributed in one way or another t - [ThinkPadNL (@ThinkPadNL)](https://github.com/ThinkPadNL "4 total commits to the home-assistant organization: 4 commits to home-assistant.io ") -- [Thom Troy (@ttroy50)](https://github.com/ttroy50 "16 total commits to the home-assistant organization: +- [Thom Troy (@ttroy50)](https://github.com/ttroy50 "17 total commits to the home-assistant organization: +9 commits to home-assistant 8 commits to home-assistant.io -8 commits to home-assistant ") - [Thomas (@ktpx)](https://github.com/ktpx "2 total commits to the home-assistant organization: 2 commits to home-assistant.io @@ -9110,9 +9222,9 @@ This page contains a list of people who have contributed in one way or another t - [Thomas Krüger (@thomaskr)](https://github.com/thomaskr "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [Thomas Lovén (@thomasloven)](https://github.com/thomasloven "42 total commits to the home-assistant organization: -23 commits to home-assistant-polymer -13 commits to home-assistant.io +- [Thomas Lovén (@thomasloven)](https://github.com/thomasloven "46 total commits to the home-assistant organization: +26 commits to home-assistant-polymer +14 commits to home-assistant.io 6 commits to home-assistant ") - [Thomas Petazzoni (@tpetazzoni)](https://github.com/tpetazzoni "1 total commits to the home-assistant organization: @@ -9194,6 +9306,9 @@ This page contains a list of people who have contributed in one way or another t - [Tim Clephas (@Timple)](https://github.com/Timple "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") +- [Tim Gerla (@tgerla)](https://github.com/tgerla "1 total commits to the home-assistant organization: +1 commit to home-assistant +") - [Tim Gray (@tgray)](https://github.com/tgray "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") @@ -9285,8 +9400,8 @@ This page contains a list of people who have contributed in one way or another t - [Tobias Nordahl Kristensen (@exetico)](https://github.com/exetico "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Tobias Sauerwein (@cgtobi)](https://github.com/cgtobi "57 total commits to the home-assistant organization: -28 commits to home-assistant.io +- [Tobias Sauerwein (@cgtobi)](https://github.com/cgtobi "58 total commits to the home-assistant organization: +29 commits to home-assistant.io 27 commits to home-assistant 1 commit to appdaemon 1 commit to data.home-assistant @@ -9353,8 +9468,8 @@ This page contains a list of people who have contributed in one way or another t - [Tom J Nowell (@tomjn)](https://github.com/tomjn "2 total commits to the home-assistant organization: 2 commits to home-assistant.io ") -- [Tom L (@Qu3uk)](https://github.com/Qu3uk "4 total commits to the home-assistant organization: -4 commits to home-assistant.io +- [Tom L (@Qu3uk)](https://github.com/Qu3uk "5 total commits to the home-assistant organization: +5 commits to home-assistant.io ") - [Tom Matheussen (@Tommatheussen)](https://github.com/Tommatheussen "15 total commits to the home-assistant organization: 6 commits to home-assistant @@ -9406,14 +9521,17 @@ This page contains a list of people who have contributed in one way or another t - [Tommy Goode (@airdrummingfool)](https://github.com/airdrummingfool "1 total commits to the home-assistant organization: 1 commit to open-zwave ") -- [Tommy Jonsson (@quazzie)](https://github.com/quazzie "12 total commits to the home-assistant organization: -9 commits to home-assistant -2 commits to home-assistant-polymer -1 commit to home-assistant.io +- [Tommy Jonsson (@quazzie)](https://github.com/quazzie "17 total commits to the home-assistant organization: +10 commits to home-assistant +4 commits to home-assistant.io +3 commits to home-assistant-polymer ") - [tonire1702 (@tonire1702)](https://github.com/tonire1702 "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [Tontze (@Tontze)](https://github.com/Tontze "1 total commits to the home-assistant organization: +1 commit to home-assistant-polymer +") - [tony chang (@idealisms)](https://github.com/idealisms "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -9450,6 +9568,9 @@ This page contains a list of people who have contributed in one way or another t 13 commits to home-assistant.io 3 commits to home-assistant ") +- [towerhand (@towerhand)](https://github.com/towerhand "1 total commits to the home-assistant organization: +1 commit to home-assistant.io +") - [travellingkiwi (@travellingkiwi)](https://github.com/travellingkiwi "4 total commits to the home-assistant organization: 4 commits to open-zwave ") @@ -9514,8 +9635,8 @@ This page contains a list of people who have contributed in one way or another t - [twendt (@twendt)](https://github.com/twendt "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [txNgineer (@txNgineer)](https://github.com/txNgineer "1 total commits to the home-assistant organization: -1 commit to home-assistant.io +- [txNgineer (@txNgineer)](https://github.com/txNgineer "2 total commits to the home-assistant organization: +2 commits to home-assistant.io ") - [Tyler (@TFenby)](https://github.com/TFenby "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -9539,8 +9660,8 @@ This page contains a list of people who have contributed in one way or another t ") - [ubnt\-marc\-khouri (@ubnt-marc-khouri)](https://github.com/ubnt-marc-khouri "6 total commits to the home-assistant organization: 2 commits to home-assistant-polymer -1 commit to hassio-build 1 commit to developers.home-assistant +1 commit to hassio-build 1 commit to home-assistant 1 commit to home-assistant.io ") @@ -9642,6 +9763,9 @@ This page contains a list of people who have contributed in one way or another t - [Victor Jalencas (@victor)](https://github.com/victor "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") +- [Victor Vostrikov (@gorynychzmey)](https://github.com/gorynychzmey "1 total commits to the home-assistant organization: +1 commit to home-assistant +") - [Vidar Tyldum (@tyldum)](https://github.com/tyldum "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") @@ -9659,16 +9783,16 @@ This page contains a list of people who have contributed in one way or another t 3 commits to home-assistant 1 commit to home-assistant.io ") -- [Ville Skyttä (@scop)](https://github.com/scop "158 total commits to the home-assistant organization: -107 commits to home-assistant +- [Ville Skyttä (@scop)](https://github.com/scop "160 total commits to the home-assistant organization: +109 commits to home-assistant 20 commits to home-assistant.io 13 commits to netdisco 5 commits to hassio-addons 4 commits to developers.home-assistant 3 commits to hassio-cli 2 commits to home-assistant-polymer -2 commits to hassio-build 2 commits to hassio +2 commits to hassio-build ") - [vincemic (@vincemic)](https://github.com/vincemic "3 total commits to the home-assistant organization: 3 commits to open-zwave @@ -9792,8 +9916,8 @@ This page contains a list of people who have contributed in one way or another t 19 commits to home-assistant.io 1 commit to fabric-home-assistant ") -- [Will Hughes (@insertjokehere)](https://github.com/insertjokehere "3 total commits to the home-assistant organization: -2 commits to home-assistant.io +- [Will Hughes (@insertjokehere)](https://github.com/insertjokehere "4 total commits to the home-assistant organization: +3 commits to home-assistant.io 1 commit to home-assistant ") - [Will Marler (@wmarler)](https://github.com/wmarler "1 total commits to the home-assistant organization: @@ -9955,8 +10079,8 @@ This page contains a list of people who have contributed in one way or another t - [yingzong (@yingzong)](https://github.com/yingzong "1 total commits to the home-assistant organization: 1 commit to warrant ") -- [yosilevy (@yosilevy)](https://github.com/yosilevy "3 total commits to the home-assistant organization: -3 commits to home-assistant-polymer +- [yosilevy (@yosilevy)](https://github.com/yosilevy "6 total commits to the home-assistant organization: +6 commits to home-assistant-polymer ") - [yulongying (@yulongying)](https://github.com/yulongying "1 total commits to the home-assistant organization: 1 commit to home-assistant-js-websocket @@ -10007,6 +10131,10 @@ This page contains a list of people who have contributed in one way or another t - [ZERBIB Mickael (@Hellorheaven)](https://github.com/Hellorheaven "2 total commits to the home-assistant organization: 2 commits to open-zwave ") +- [zewelor (@zewelor)](https://github.com/zewelor "2 total commits to the home-assistant organization: +1 commit to home-assistant +1 commit to home-assistant.io +") - [zgmnkv (@zgmnkv)](https://github.com/zgmnkv "4 total commits to the home-assistant organization: 4 commits to open-zwave ") @@ -10019,9 +10147,9 @@ This page contains a list of people who have contributed in one way or another t - [Zhong Jianxin (@azuwis)](https://github.com/azuwis "1 total commits to the home-assistant organization: 1 commit to home-assistant ") -- [zhujisheng (@zhujisheng)](https://github.com/zhujisheng "3 total commits to the home-assistant organization: -2 commits to home-assistant.io -1 commit to home-assistant +- [zhujisheng (@zhujisheng)](https://github.com/zhujisheng "5 total commits to the home-assistant organization: +3 commits to home-assistant.io +2 commits to home-assistant ") - [zhumuht (@zhumuht)](https://github.com/zhumuht "1 total commits to the home-assistant organization: 1 commit to home-assistant @@ -10049,8 +10177,8 @@ This page contains a list of people who have contributed in one way or another t - [zuccs (@zuccs)](https://github.com/zuccs "1 total commits to the home-assistant organization: 1 commit to home-assistant.io ") -- [Åskar Andersson (@olskar)](https://github.com/olskar "11 total commits to the home-assistant organization: -7 commits to home-assistant.io +- [Åskar Andersson (@olskar)](https://github.com/olskar "12 total commits to the home-assistant organization: +8 commits to home-assistant.io 3 commits to home-assistant 1 commit to hassbian-scripts ") @@ -10060,4 +10188,4 @@ This page contains a list of people who have contributed in one way or another t This page is irregularly updated using the [`hass-release` tool](https://github.com/home-assistant/hass-release). If you think that you are missing, please let us know. -This page was last updated Sunday, January 13 2019, 20:14:10 UTC. +This page was last updated Thursday, January 24 2019, 22:39:22 UTC. diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown index 118d3c05078..65e8f8753f9 100644 --- a/source/lovelace/index.markdown +++ b/source/lovelace/index.markdown @@ -29,7 +29,8 @@ To try it yourself, check out [the demo](https://demo.home-assistant.io). ## {% linkable_title Discuss Lovelace %} -Lovelace is still under development and we're always looking at making things better. Discussion and suggestions are welcome in the [ui-schema repository](https://github.com/home-assistant/ui-schema) and in the [chat](/join-chat/) in #lovelace. +- Suggestions are welcome in the [ui-schema repository](https://github.com/home-assistant/ui-schema) +- For help with Lovelace, join the #lovelace channel on [our chat](/join-chat/) or [our forums](https://community.home-assistant.io/c/projects/frontend) ## {% linkable_title Additional Lovelace Resources %} diff --git a/source/lovelace/tips.markdown b/source/lovelace/tips.markdown deleted file mode 100644 index bcd77df37e3..00000000000 --- a/source/lovelace/tips.markdown +++ /dev/null @@ -1,69 +0,0 @@ ---- -layout: page -title: "Lovelace Tips and Tricks" -description: "Helpful tips and tricks for using the Lovelace UI in Home Assistant." -date: 2018-07-23 21:57 +00:00 -sidebar: true -comments: false -sharing: true -footer: true ---- - -The Lovelace UI is a very powerful UI. Here are a few tips and tricks that -might help you when working with Lovelace. - -*Have a tip or trick of your own? Click the "Edit this page on GitHub" at the -top of this page to share it with everyone!* - -## {% linkable_title Tips & Tricks %} - -### {% linkable_title Add your your own image to Lovelace %} - -Home Assistant allows you to make files in `/www/example_image.jpg` available to Lovelace as `/local/example_image.jpg`. When you create the `www` directory, you will need to once restart Home Assistant to pick it up. After that, any new file placed in the directory will automatically be available. - -Check out [Share the love][sharethelove] for a few great examples of what you can do with lovelace (no affiliation). - -### {% linkable_title Disable Click on Elements %} - -If you do not want an element to be clickable you can add `pointer-events: none` -to the element's `style:` configuration. This is quite useful when building a -[Picture Elements][picture-elements] card that will be viewed mostly in a -mobile browser. (@Toast) - -### {% linkable_title Header Using Panel and Stacks %} - -You can create a header by using `panel: true` with nested -[Vertical Stack][vertical-stack] and [Horizontal Stack][horizontal-stack] -cards. See the code [here][header-stacks]. ([@dale3h]) - -## {% linkable_title Tools %} - -We have some amazing users that have created various tools to help you get -started with Lovelace. - -### {% linkable_title Lovelace Migration Script %} - -The [Lovelace Migration Script][migration-script] by [@dale3h] converts your -current "old UI" configuration to the new Lovelace format. The idea behind -this tool is to help give you something to start playing with right away. - -### {% linkable_title Lovelace Config Generator %} - -The [Lovelace Config Generator][config-generator] by [@thomasloven] provides -you with the ability to split your Lovelace configuration into multiple files. - -### {% linkable_title Lovelace Config Generator (Jinja2 Script) %} - -The [Lovelace Jinja2 Script][lovelace-jinja] by [@skalavala] is a simple Jinja2 script that you run in the template editor to generate lovelace configuration based on the entities that are already setup. - -[@dale3h]: https://github.com/dale3h -[@thomasloven]: https://github.com/thomasloven -[@skalavala]: https://github.com/skalavala -[config-generator]: https://github.com/thomasloven/homeassistant-lovelace-gen -[header-stacks]: https://gist.github.com/dale3h/37b34aebb0c336ffd5fb877c2651097a -[horizontal-stack]: /lovelace/horizontal-stack/ -[migration-script]: https://github.com/dale3h/python-lovelace -[picture-elements]: /lovelace/picture-elements/ -[vertical-stack]: /lovelace/vertical-stack/ -[lovelace-jinja]: https://sharethelove.io/tools/jinja-magic-scripts -[sharethelove]: https://sharethelove.io/