diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index bfbe7bd2c02..9938ea6ddb2 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -5,7 +5,7 @@ ## Checklist: -- [ ] Branch: Fixes, changes and adjustments should be created against `current`. New documentation for platforms/components and features should go to `next`. +- [ ] Branch: `next` is for changes and new documentation that will go public with the next [home-assistant](https://github.com/home-assistant/home-assistant) release. Fixes, changes and adjustments for the current release should be created against `current`. - [ ] The documentation follow the [standards][standards]. [standards]: https://home-assistant.io/developers/documentation/standards/ diff --git a/.gitignore b/.gitignore index f02128325f5..933ece07209 100644 --- a/.gitignore +++ b/.gitignore @@ -20,3 +20,4 @@ source/.jekyll-metadata /.vs/slnx.sqlite-journal /.vs/VSWorkspaceState.json .vscode +*.suo diff --git a/_config.yml b/_config.yml index e56a21fade4..ad7f9d183c9 100644 --- a/_config.yml +++ b/_config.yml @@ -141,14 +141,14 @@ social: # Home Assistant release details current_major_version: 0 -current_minor_version: 77 -current_patch_version: 2 -date_released: 2018-08-31 +current_minor_version: 78 +current_patch_version: 3 +date_released: 2018-09-22 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. # Major release: -patch_version_notes: "#release-0772---august-31" +patch_version_notes: "#release-0783---september-22" # Minor release (Example #release-0431---april-25): # Date we moved to Discourse for comments diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown index 2f910f75b06..38c947eb6e3 100644 --- a/source/_addons/duckdns.markdown +++ b/source/_addons/duckdns.markdown @@ -10,7 +10,7 @@ footer: true featured: true --- -[Duck DNS](https://www.duckdns.org/) is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice. This add-on includes support for Let's Encrypt and will automatically create and renew your certificates. +[Duck DNS](https://www.duckdns.org/) is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice. This add-on includes support for Let's Encrypt and will automatically create and renew your certificates. You will need to sign up for a Duck DNS account before using this add-on. ```json { @@ -28,7 +28,7 @@ featured: true Configuration variables: - **lets_encrypt.accept_terms** (*Required*): If you accept the [Let's Encrypt Subscriber Agreement](https://letsencrypt.org/repository/), it will generate and update Let's Encrypt certificates for your DuckDNS domain. -- **token** (*Required*): Your Duck DNS API key. +- **token** (*Required*): Your Duck DNS API key, from your DuckDNS account page. - **domains** (*Required*): A list of domains to update DNS. - **seconds** (*Required*): Seconds between updates to Duck DNS. diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown index 2150b1a3080..70f591520c0 100644 --- a/source/_addons/mosquitto.markdown +++ b/source/_addons/mosquitto.markdown @@ -89,10 +89,11 @@ See the following links for more information: Add the following configuration to enable ACLs: -1. Set `customize` flag to `true` in your configuration. +1. Set the `active` flag within the `customize` section to `true` in your configuration. 2. Create a file in `/share/mosquitto` named `acl.conf` with the following contents: - ```text acl_file /share/mosquitto/accesscontrollist ``` 3. Create a file in `/share/mosquitto` named `accesscontrollist` and add contents according to your requirements. + +The `/share` folder can be found on the host filesystem under `/usr/share/hassio/share`, or via the `Share` folder through SMB (Samba). diff --git a/source/_components/alarm_control_panel.ialarm.markdown b/source/_components/alarm_control_panel.ialarm.markdown index d72261c908f..44895675cf4 100644 --- a/source/_components/alarm_control_panel.ialarm.markdown +++ b/source/_components/alarm_control_panel.ialarm.markdown @@ -46,3 +46,4 @@ alarm_control_panel: type: string {% endconfiguration %} +This platform has also been confirmed to work with the alarm system brands Meian and Emooluxr. diff --git a/source/_components/alarm_control_panel.yale_smart_alarm.markdown b/source/_components/alarm_control_panel.yale_smart_alarm.markdown new file mode 100644 index 00000000000..f2dc607b157 --- /dev/null +++ b/source/_components/alarm_control_panel.yale_smart_alarm.markdown @@ -0,0 +1,60 @@ +--- +layout: page +title: "Yale Smart Alarm Control" +description: "Instructions on how to integrate Yale Smart Alarms into Home Assistant." +date: 2018-09-01 11:11 +sidebar: true +comments: false +sharing: true +footer: true +ha_category: Alarm +ha_release: 0.78 +--- + +The `yale_smart_alarm` platform provides connectivity with the Yale Smart Alarm systems and Smart Hub through Yale's API. + +This platform supports the following services: `alarm_arm_away`, `alarm_arm_home`, `alarm_arm_night` (duplicate of home) and `alarm_disarm`. +Currently only one alarm is supported. + + +To enable, add the following lines to your `configuration.yaml`: + +```yaml +# Example configuration.yaml entry +alarm_control_panel: + - platform: yale_smart_alarm + username: YOUR_USERNAME + password: YOUR_PASSWORD +``` + +Configuration variables: + +- **name** (*Optional*): Name of device in Home Assistant. +- **username** (*Required*): Username used to sign into the Yale app/web client. +- **password** (*Required*): Password used to sign into the Yale app/web client. +- **area_id** (*Optional*): Area ID of the device when talking to Yale's API if required ('1' by default). + +Automation example: + +```yaml +automation: + - alias: "Alarm: Disarmed Daytime" + trigger: + platform: state + entity_id: alarm_control_panel.yale_smart_alarm + to: 'disarmed' + condition: + condition: sun + before: sunset + action: + service: scene.turn_on + entity_id: scene.OnDisarmedDaytime + - alias: "Alarm: Armed Away" + trigger: + platform: state + entity_id: alarm_control_panel.yale_smart_alarm + to: 'armed_away' + action: + service: scene.turn_on + entity_id: scene.OnArmedAway +``` diff --git a/source/_components/android_ip_webcam.markdown b/source/_components/android_ip_webcam.markdown index c616b33a35e..b11ac13595e 100644 --- a/source/_components/android_ip_webcam.markdown +++ b/source/_components/android_ip_webcam.markdown @@ -37,6 +37,10 @@ Configuration variables: - **switches** array (*Optional*): Conditions to display settings in the frontend. See the list of supported settings. - **motion_sensor** (*Optional*): Activate motion sensor if auto_discovery is disabled. +

+ You need to enable logging in the Android app (`Data logging` > `Enable data logging`), if you wish to see the sensor states in Home Assistant. The sensor states stays as `unknown`, until it's enabled. +

+ ### {% linkable_title Supported features %} Sensors: diff --git a/source/_components/apcupsd.markdown b/source/_components/apcupsd.markdown index ff6f732484e..44265218d24 100644 --- a/source/_components/apcupsd.markdown +++ b/source/_components/apcupsd.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: apcupsd.png -ha_category: Hub +ha_category: System Monitor ha_release: 0.13 --- diff --git a/source/_components/apple_tv.markdown b/source/_components/apple_tv.markdown index 93d192a00c2..e9008af6385 100644 --- a/source/_components/apple_tv.markdown +++ b/source/_components/apple_tv.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: apple.png -ha_category: Hub +ha_category: Multimedia ha_iot_class: "Local Push" ha_release: 0.49 --- diff --git a/source/_components/august.markdown b/source/_components/august.markdown index 2d079065ec7..9231f7d2f13 100644 --- a/source/_components/august.markdown +++ b/source/_components/august.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: august.png -ha_category: Door bell +ha_category: Doorbell ha_release: "0.64" ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/auth.markdown b/source/_components/auth.markdown index 96d0ab055a2..cc7ec923920 100644 --- a/source/_components/auth.markdown +++ b/source/_components/auth.markdown @@ -12,4 +12,4 @@ ha_category: Other ha_release: 0.73 --- -This component creates the endpoints for the authentication system that is built into Home Assistant. There are no configuration options for this component directly as it relies on the auth system in the core. +This component creates the endpoints for the [authentication system](/docs/authentication/) that is built into Home Assistant. There are no configuration options for this component directly as it relies on the auth system in the core. diff --git a/source/_components/axis.markdown b/source/_components/axis.markdown index 6f9a2cc4826..6662b55300a 100644 --- a/source/_components/axis.markdown +++ b/source/_components/axis.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: axis.png -ha_category: Hub +ha_category: Camera ha_release: "0.45" ha_iot_class: "Local Polling" --- @@ -17,6 +17,8 @@ ha_iot_class: "Local Polling" Home Assistant will automatically discover their presence on your network. +## {% linkable_title Configuration %} + You can also manually configure your devices by adding the following lines to your `configuration.yaml` file: ```yaml @@ -28,8 +30,6 @@ axis: - camera ``` -Configuration variables: - ## {% linkable_title Configuration variables %} - **device** (*Required*): Unique name diff --git a/source/_components/binary_sensor.august.markdown b/source/_components/binary_sensor.august.markdown index 20d2aec19d0..4af76c345bc 100644 --- a/source/_components/binary_sensor.august.markdown +++ b/source/_components/binary_sensor.august.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: august.png -ha_category: Door bell +ha_category: Doorbell ha_release: "0.64" ha_iot_class: "Cloud Polling" --- @@ -20,3 +20,4 @@ If you have August Doorbell, once you have enabled the [August component](/compo * Doorbell ding sensor * Doorbell motion sensor * Doorbell online sensor + diff --git a/source/_components/binary_sensor.bmw_connected_drive.markdown b/source/_components/binary_sensor.bmw_connected_drive.markdown old mode 100755 new mode 100644 diff --git a/source/_components/binary_sensor.knx.markdown b/source/_components/binary_sensor.knx.markdown index d51c9effbb4..6f5ff097906 100644 --- a/source/_components/binary_sensor.knx.markdown +++ b/source/_components/binary_sensor.knx.markdown @@ -15,26 +15,24 @@ ha_iot_class: "Local Polling" The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) binary sensors. +## {% linkable_title Configuration %} + The `knx` component must be configured correctly, see [KNX Component](/components/knx). ```yaml # Example configuration.yaml entry binary_sensor: - platform: knx - name: "Entrance.Motion.Sensor" address: '6/0/2' - device_class: 'motion' - #significant_bit: 2 - #reset_after: 100 ``` Configuration variables: +- **address** (*Required*): KNX group address of the binary sensor. - **name** (*Optional*): A name for this device used within Home Assistant. -- **address**: KNX group address of the binary sensor. -- **device_class** (Optional): HASS device class e.g., "motion". -- **significant_bit** (Optional): Specify which significant bit of the KNX value should be used. Default is 1. -- **reset_after** (Optional): Reset back to OFF state after specified milliseconds. +- **device_class** (*Optional*): HASS device class e.g., "motion". +- **significant_bit** (*Optional*): Specify which significant bit of the KNX value should be used. Default is 1. +- **reset_after** (*Optional*): Reset back to OFF state after specified milliseconds. You can also attach actions to binary sensors (e.g., to switch on a light when a switch was pressed). In this example, one light is switched on when the button was pressed once and two others when the button was pressed a second time. diff --git a/source/_components/binary_sensor.pilight.markdown b/source/_components/binary_sensor.pilight.markdown index b34cc955bfa..ef71c754602 100644 --- a/source/_components/binary_sensor.pilight.markdown +++ b/source/_components/binary_sensor.pilight.markdown @@ -39,7 +39,7 @@ Configuration variables: A full configuration example could look like this: ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry binary_sensor: - platform: pilight name: 'Motion' diff --git a/source/_components/binary_sensor.upcloud.markdown b/source/_components/binary_sensor.upcloud.markdown index 6cae22e876c..2723cefa5bf 100644 --- a/source/_components/binary_sensor.upcloud.markdown +++ b/source/_components/binary_sensor.upcloud.markdown @@ -15,6 +15,8 @@ ha_iot_class: Cloud Polling The `upcloud` binary sensor platform allows you to monitor your UpCloud servers. +## {% linkable_title Configuration %} + To use your UpCloud servers, you first have to set up your [UpCloud hub](/components/upcloud/) and then add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/bloomsky.markdown b/source/_components/bloomsky.markdown index 620b390e69b..1139ee7a9ad 100644 --- a/source/_components/bloomsky.markdown +++ b/source/_components/bloomsky.markdown @@ -8,15 +8,19 @@ comments: false sharing: true footer: true logo: bloomsky.png -ha_category: Hub +ha_category: Environment ha_release: 0.14 ha_iot_class: "Cloud Polling" --- The `bloomsky` component allows you to access your [BloomSky](https://www.bloomsky.com/) weather station's [sensors](/components/sensor.bloomsky), [binary sensors](/components/binary_sensor.bloomsky), and [camera](/components/camera.bloomsky) from Home Assistant. +## {% linkable_title Setup %} + Obtain your API key from your [BloomSky dashboard](https://dashboard.bloomsky.com). Click `developers` in the bottom left of the screen. +## {% linkable_title Configuration %} + To integrate your BloomSky hub with Home Assistant, add the following section to your `configuration.yaml` file: ```yaml @@ -25,6 +29,9 @@ bloomsky: api_key: YOUR_API_KEY ``` -Configuration variables: - -- **api_key** (*Required*): Your BloomSky API key. +{% configuration %} +api_key: + description: Your BloomSky API key. + required: true + type: string +{% endconfiguration %} diff --git a/source/_components/camera.bloomsky.markdown b/source/_components/camera.bloomsky.markdown index bd6f8a58b9e..6c600b20a84 100644 --- a/source/_components/camera.bloomsky.markdown +++ b/source/_components/camera.bloomsky.markdown @@ -16,6 +16,8 @@ ha_iot_class: "Local Polling" The `bloomsky` camera component allows you to view the current photo created by the camera in the [BloomSky](https://www.bloomsky.com) weather station. This can work in concert with [BloomSky sensors](/components/sensor.bloomsky). +## {% linkable_title Configuration %} + To enable this camera in your installation, set up the [BloomSky component](/components/bloomsky) with your API key and add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/camera.generic.markdown b/source/_components/camera.generic.markdown index b9bf15bf46a..e8c457086f5 100644 --- a/source/_components/camera.generic.markdown +++ b/source/_components/camera.generic.markdown @@ -37,6 +37,7 @@ Configuration variables: - **limit_refetch_to_url_change** (*Optional*): True/false value (default: false). Limits re-fetching of the remote image to when the URL changes. Only relevant if using a template to fetch the remote image. - **content_type** (*Optional*): Set the content type for the IP camera if it is not a jpg file (default: `image/jpeg`). Use `image/svg+xml` to add a dynamic svg file. - **framerate** (*Optional*): The number of frames-per-second (FPS) of the stream (setting this too high may cause too much traffic on the network or be heavy on the camera). +- **verify_ssl** (*Optional*): True/false value (default: true). Enable or disable SSL certificate verification.

@@ -68,6 +69,7 @@ camera: - platform: generic name: Some Image still_image_url: https://127.0.0.1:8123/local/your_image.png + verify_ssl: false ``` ### {% linkable_title Sharing a camera feed from one Home Assistant instance to another %} diff --git a/source/_components/camera.logi_circle.markdown b/source/_components/camera.logi_circle.markdown new file mode 100644 index 00000000000..1b525400700 --- /dev/null +++ b/source/_components/camera.logi_circle.markdown @@ -0,0 +1,69 @@ +--- +layout: page +title: "Logi Circle Camera" +description: "Instructions on how to integrate your Logi Circle cameras within Home Assistant." +date: 2018-09-08 11:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: logi_circle.png +ha_category: Camera +ha_release: 0.79 +ha_iot_class: "Cloud Polling" +--- + +The `logi_circle` camera platform allows you to watch the still frames of your [Logi Circle](https://circle.logi.com/) camera's live stream in Home Assistant. + +

+You must have the [Logi Circle component](/components/logi_circle/) configured to use this camera platform. +

+ +Logi Circle cameras support the `camera.turn_on` and `camera.turn_off` services. This will set the streaming mode property of your camera accordingly, controlling whether the live stream is available and activity recordings are captured. + +## {% linkable_title Configuration %} + +Once you have enabled the [Logi Circle component](/components/logi_circle), add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +camera: + - platform: logi_circle +``` + +Configuration variables: + +- **scan_interval**: (*Optional*): How frequently to query for new camera stills. Defaults to 60 seconds. + +### {% linkable_title Service `camera.logi_circle_livestream_record` %} + +Initiates a recording of the camera's live stream. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | Name(s) of entities to initiate a recording for, e.g., `camera.living_room_camera`. If blank, targets all Logi Circle cameras. | +| `filename ` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/snapshot_{{ entity_id }}.mp4`{% endraw %}. | +| `duration` | no | Duration of recording, in seconds. + +The path part of `filename` must be an entry in the `whitelist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file. + +### {% linkable_title Service `camera.logi_circle_livestream_snapshot` %} + +Take a snapshot from a camera's live stream. This differs from the generic [snapshot](/components/camera/#service-snapshot) service in that it sources the snapshot from the camera's live stream. For battery powered devices, this will wake your camera from sleep to perform this action. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | Name(s) of entities to create a live stream snapshot from, e.g., `camera.living_room_camera`. If blank, targets all Logi Circle cameras. | +| `filename` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/snapshot_{{ entity_id }}.jpg`{% endraw %}. | + +The path part of `filename` must be an entry in the `whitelist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file. + +### {% linkable_title Service `camera.logi_circle_set_config` %} + +Sets an configuration property for your camera. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | Name(s) of entities to set the operation mode for, e.g., `camera.living_room_camera`. If blank, targets all Logi Circle cameras. | +| `mode` | no | Configuration property to set. Allowed values: `BATTERY_SAVING`, `LED`, `PRIVACY_MODE` | +| `value` | no | Mode value. Allowed values: `true`, `false` | \ No newline at end of file diff --git a/source/_components/camera.mqtt.markdown b/source/_components/camera.mqtt.markdown index f0e903a37a9..411a37d19de 100644 --- a/source/_components/camera.mqtt.markdown +++ b/source/_components/camera.mqtt.markdown @@ -30,4 +30,5 @@ Configuration variables: - **topic** (*Required*): MQTT topic to subscribe to. - **name** (*Optional*): Name of the camera + - **unique_id** (*Optional*): An ID that uniquely identifies this camera. If two cameras have the same unique ID, Home Assistant will raise an exception. diff --git a/source/_components/camera.push.markdown b/source/_components/camera.push.markdown index c70dee014c0..be639978032 100644 --- a/source/_components/camera.push.markdown +++ b/source/_components/camera.push.markdown @@ -25,11 +25,9 @@ The `push` camera can as an example be used with [motionEye](https://github.com/ In motionEye, under **File Storage -> Run A Command** type in: ```bash -curl -X POST -F "image=@%f" http://my.hass.server.com:8123/api/camera_push/camera.push_camera +curl -X POST -F "image=@%f" http://my.hass.server.com:8123/api/camera_push/camera.push_camera?token=12345678 ``` -Please take note that you might need to add `-H "x-ha-access: YOUR_PASSWORD"` if you have API authentication enabled. - Optionally configure motionEye to save only motion triggered images by going into **Still Images -> Capture Mode** and setting **Motion Triggered**. Tune your preferences under **Motion Detection**. In this setup, you can configure the push camera to continuously replay the last motion triggered event using a configuration such as: @@ -40,6 +38,7 @@ camera: name: MotionEye Outdoor buffer: 3 timeout: 5 + token: 12345678 ``` ## {% linkable_title Configuration %} @@ -51,6 +50,7 @@ To enable this camera in your installation, add the following to your `configura camera: - platform: push name: My Push Camera + token: 12345678 ``` {% configuration %} @@ -69,6 +69,10 @@ timeout: required: false default: 5 seconds type: time +token: + description: User provided token acting as access control, should be a large string (more then 8 chars). Required if you can't use HA new auth system (0.77). + required: false + type: string field: description: HTTP POST field containing the image file required: false diff --git a/source/_components/climate.daikin.markdown b/source/_components/climate.daikin.markdown index 2201872a15b..904b3e5fa13 100644 --- a/source/_components/climate.daikin.markdown +++ b/source/_components/climate.daikin.markdown @@ -23,11 +23,7 @@ The `daikin` climate platform integrates Daikin air conditioning systems into Ho Current temperature is displayed. -

-Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant. BRP069A42 does not support setting of fan speed or fan swing mode. -

- -The platform has been integrated with discovery so all your Daikin AC's climate devices can be automatically discovered. +## {% linkable_title Configuration %} To enable the platform, add the following lines to your `configuration.yaml` file: diff --git a/source/_components/climate.modbus.markdown b/source/_components/climate.modbus.markdown index 62163a316aa..164ae4a4877 100644 --- a/source/_components/climate.modbus.markdown +++ b/source/_components/climate.modbus.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "Modbus" +title: "Modbus Climate" description: "Instructions how to integrate a Modbus thermostat within Home Assistant." date: 2018-01-29 9:35 sidebar: true diff --git a/source/_components/climate.opentherm_gw.markdown b/source/_components/climate.opentherm_gw.markdown new file mode 100644 index 00000000000..4b67af4667b --- /dev/null +++ b/source/_components/climate.opentherm_gw.markdown @@ -0,0 +1,65 @@ +--- +layout: page +title: "OpenTherm Gateway" +description: "Control your OpenTherm Gateway from Home Assistant." +date: 2018-08-29 16:23 +sidebar: true +comments: false +sharing: true +footer: true +logo: opentherm.png +ha_category: Climate +ha_release: 0.78 +ha_iot_class: "Local Push" +--- + + +The `opentherm_gw` climate platform is used to control the [OpenTherm Gateway](http://otgw.tclcode.com/) from Home Assistant. + +# {% linkable_title Configuration %} + +```yaml +# Example configuration.yaml entry +climate: + - platform: opentherm_gw + device: /dev/ttyUSB0 +``` + +{% configuration %} +device: + description: "Path to OpenTherm Gateway device as supported by [PySerial](https://pythonhosted.org/pyserial/url_handlers.html)." + required: true + type: string +name: + description: The name for the device within Home Assistant. + required: false + type: string + default: OpenTherm Gateway +precision: + description: "The desired precision for this device. Can be used to match your actual thermostat's precision. Supported values are `0.1`, `0.5` and `1.0`." + required: false + type: float + default: "`0.5` for Celsius and `1.0` for Fahrenheit." +floor_temperature: + description: Some thermostats round all temperatures down to the lower value according to their precision. Default behaviour for Home Assistant is to round temperatures to the nearest value. Set this to `True` to override Home Assistant and round to the lower value according to the configured `precision`. + required: false + type: boolean +{% endconfiguration %} + +

+The OpenTherm protocol is based on polling. The thermostat sends requests to the boiler at specific intervals. As a result, it may take some time for changes to propagate between Home Assistant and the thermostat. +

+ +# {% linkable_title Example %} + +A full configuration example with the OpenTherm Gateway connected to a remote host running `ser2net` looks like the one below. + +```yaml +# Full example configuration.yaml entry +climate: + - platform: opentherm_gw + device: socket://otgw.example.org:2345 + name: Thermostat + precision: 0.5 + floor_temperature: True +``` diff --git a/source/_components/cloud.markdown b/source/_components/cloud.markdown index 3008a52cac4..5b6417906c4 100644 --- a/source/_components/cloud.markdown +++ b/source/_components/cloud.markdown @@ -7,13 +7,13 @@ sidebar: true comments: false sharing: true footer: true -logo: home-assistant.png +logo: nabu-casa.svg ha_release: "0.60" ha_category: Voice ha_iot_class: "Cloud Push" --- -The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa. [Learn more.](/cloud) +The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa and Google Assistant. [Learn more.](/cloud) ```yaml # Example configuration.yaml entry to enable the cloud component diff --git a/source/_components/cover.aladdin_connect.markdown b/source/_components/cover.aladdin_connect.markdown index ca3576dce58..f0f35c71027 100644 --- a/source/_components/cover.aladdin_connect.markdown +++ b/source/_components/cover.aladdin_connect.markdown @@ -19,14 +19,16 @@ The `aladdin_connect` cover platform lets you control Genie Aladdin Connect gara Only doors that are owned by your Aladdin Connect account will be available. Doors that your account has been granted shared access to are not yet supported.

+## {% linkable_title Configuration %} + To use your Aladdin Connect cover in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry cover: - platform: aladdin_connect - username: user@email.com - password: password + username: YOUR_USERNAME + password: YOUR_PASSWORD ``` {% configuration %} diff --git a/source/_components/cover.deconz.markdown b/source/_components/cover.deconz.markdown new file mode 100644 index 00000000000..1b721a581c1 --- /dev/null +++ b/source/_components/cover.deconz.markdown @@ -0,0 +1,26 @@ +--- +layout: page +title: "deCONZ Covers" +description: "Instructions on how to integrate Zigbee covers from deCONZ into Home Assistant." +date: 2018-09-20 23:32 +sidebar: true +comments: false +sharing: true +footer: true +logo: deconz.jpeg +ha_category: Cover +ha_release: "0.79" +ha_iot_class: "Local Push" +--- + +See the [deCONZ main component](/components/deconz/) for configuration instructions. + +Covers are devices like ventilation dampers. + +Note that devices in the cover platform identify as lights, so there is a manually curated list that defines which "lights" are covers. + +The `entity_id` name will be `cover.device_name`, where `device_name` is defined in deCONZ. + +#### {% linkable_title Verified supported covers %} + +- Keen vents diff --git a/source/_components/cover.markdown b/source/_components/cover.markdown index a530768096f..f276c9b398a 100644 --- a/source/_components/cover.markdown +++ b/source/_components/cover.markdown @@ -15,7 +15,7 @@ The display style of each entity can be modified in the [customize section](/get | Attribute | Default | Description | | --------- | ------- | ----------- | -| `device_class` | | `none` Generic cover device
`window` Window controller
`garage` Garage door controller +| `device_class` | | `none` Generic cover device
`damper` Ventilation damper controller
`garage` Garage door controller
`window` Window controller | `assumed_state` | `false` | If set to `true`, cover buttons will always be enabled ## {% linkable_title Services %} diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown old mode 100755 new mode 100644 diff --git a/source/_components/daikin.markdown b/source/_components/daikin.markdown index 84624b5af04..d4b25765958 100644 --- a/source/_components/daikin.markdown +++ b/source/_components/daikin.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: daikin.png -ha_category: Hub +ha_category: Climate ha_release: 0.59 ha_iot_class: "Local Polling" --- @@ -16,11 +16,15 @@ ha_iot_class: "Local Polling" The `daikin` component integrates Daikin air conditioning systems into Home Assistant. -To automatically add all your Daikin devices (ACs and associated sensors) into your Home Assistant installation, add the following to your 'configuration.yaml' file: +## {% linkable_title Supported hardware %} -

-Please note, the Daikin platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant. -

+**Only** the european versions of Daikin ACs (models BRP069A41, 42, 43, 45). + +The model BRP069A42 does not support setting of fan speed or fan swing mode. + +Please note that some AC devices may report outside temperature only when they are turned on. + +## {% linkable_title Configuration %} To automatically add all your Daikin devices (ACs and associated sensors) into your Home Assistant installation, add the following to your `configuration.yaml` file: @@ -52,7 +56,3 @@ monitored_conditions: description: The current temperature measured outside the house. {% endconfiguration %} -

-Please note that some AC devices may report outside temperature only when they are turned on. -

- diff --git a/source/_components/deconz.markdown b/source/_components/deconz.markdown index 211e683fe15..869a441c8a9 100644 --- a/source/_components/deconz.markdown +++ b/source/_components/deconz.markdown @@ -29,7 +29,7 @@ See [deCONZ wiki](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/ Home Assistant will automatically discover deCONZ presence on your network, if `discovery:` is present in your `configuration.yaml` file. -If you don't have the API key, you can generate an API key for deCONZ by using the one-click functionality similar to Philips Hue. Go to **Menu** -> **Settings** -> **Unlock Gateway** in deCONZ and then use the deCONZ configurator in Home Assistant frontend to create an API key. When you're done setting up deCONZ it will be stored as a config entry. +If you don't have the API key, you can generate an API key for deCONZ by using the one-click functionality similar to Philips Hue. Go to **Settings** -> **Gateway** -> **Advanced** -> **Authenticate app** in deCONZ and then use the deCONZ configurator in Home Assistant frontend to create an API key. When you're done setting up deCONZ it will be stored as a config entry. You can add the following to your `configuration.yaml` file if you are not using the `discovery:` component: @@ -79,16 +79,16 @@ logger: ## {% linkable_title Device services %} -Available services: `configure`. +Available services: `configure` and `deconz.refresh_devices`. #### {% linkable_title Service `deconz.configure` %} -Set attribute of device in Deconz using [Rest API](http://dresden-elektronik.github.io/deconz-rest-doc/rest/). +Set attribute of device in deCONZ using [Rest API](http://dresden-elektronik.github.io/deconz-rest-doc/rest/). | Service data attribute | Optional | Description | |-----------|----------|-------------| | `field` | No | String representing a specific device in deCONZ. | -| `entity` | No | String representing a specific HASS entity of a device in deCONZ. | +| `entity` | No | String representing a specific Home Assistant entity of a device in deCONZ. | | `data` | No | Data is a JSON object with what data you want to alter. | Field and entity are exclusive, i.e you can only use one in a request. @@ -99,9 +99,15 @@ Field and entity are exclusive, i.e you can only use one in a request. { "field": "/config", "data": {"permitjoin": 60} } +#### {% linkable_title Service `deconz.refresh_devices` %} + +Refresh with devices added to deCONZ after Home Assistants latest restart. + +Note: deCONZ automatically signals Home Assistant when new sensors are added, but other devices must at this point in time (deCONZ v2.05.35) be added manually using this service or a restart of Home Assistant. + ## {% linkable_title Remote control devices %} -Remote controls (ZHASwitch category) will be not be exposed as a regular entity, but as events named 'deconz_event' with a payload of 'id' and 'event'. Id will be the device name from deCONZ and Event will be the momentary state of the switch. However, a sensor entity will be created that shows the battery level of the switch as reported by deCONZ, named sensor.device_name_battery_level. +Remote controls (ZHASwitch category) will be not be exposed as regular entities, but as events named `deconz_event` with a payload of `id` and `event`. Id will be the device name from deCONZ and Event will be the momentary state of the switch. However, a sensor entity will be created that shows the battery level of the switch as reported by deCONZ, named sensor.device_name_battery_level. Typical values for switches, the event codes are 4 numbers where the first and last number are of interest here. @@ -173,6 +179,36 @@ automation: ### {% linkable_title Appdaemon %} +#### {% linkable_title Appdaemon event helper %} +Helper app that creates a sensor `sensor.deconz_event` with a state that represents the id from the last event and an attribute to show the event data. + +{% raw %} +```yaml +deconz_helper: + module: deconz_helper + class: DeconzHelper +``` + +```python +import appdaemon.plugins.hass.hassapi as hass +import datetime +from datetime import datetime + +class DeconzHelper(hass.Hass): + def initialize(self) -> None: + self.listen_event(self.event_received, "deconz_event") + + def event_received(self, event_name, data, kwargs): + event_data = data["event"] + event_id = data["id"] + event_received = datetime.now() + + self.log("Deconz event received from {}. Event was: {}".format(event_id, event_data)) + self.set_state("sensor.deconz_event", state = event_id, attributes = {"event_data": event_data, "event_received": str(event_received)}) +``` +{% endraw %} + + #### {% linkable_title Appdaemon remote template %} {% raw %} diff --git a/source/_components/device_tracker.bbox.markdown b/source/_components/device_tracker.bbox.markdown index 35bae013f02..5efa022bad2 100644 --- a/source/_components/device_tracker.bbox.markdown +++ b/source/_components/device_tracker.bbox.markdown @@ -16,9 +16,11 @@ ha_iot_class: "Local Polling" The `bbox` platform offers presence detection by looking at connected devices to a [Bbox](https://fr.wikipedia.org/wiki/Bbox) based router from [Bouygues](https://www.bouyguestelecom.fr/), which is one of the main Internet provider in France. -

-Bbox is a generic name for different hardware routers. The platform has only been tested on a Sagem F@st 5330b because it's the only model the developer owns. -

+Bbox is a generic name for different hardware routers. The platform has been tested with the following devices: + +- Sagem F@st 5330b + +## {% linkable_title Configuration %} To use an Bbox router in your installation, add the following to your `configuration.yaml` file: @@ -28,8 +30,17 @@ device_tracker: - platform: bbox ``` +{% configuration %} +host: + description: IP address of your Bbox device. + required: false + type: string + default: 192.168.1.254 +{% endconfiguration %} + +

-For now and due to third party limitation, the Bbox must be on the same local network as the Home Assistant installation. And with the default IP configuration (IP of the router must be 192.168.1.254). +For now and due to third party limitation, the Bbox must be on the same local network as the Home Assistant installation.

See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.bluetooth_le_tracker.markdown b/source/_components/device_tracker.bluetooth_le_tracker.markdown index ce1dab50002..83c21c615b7 100644 --- a/source/_components/device_tracker.bluetooth_le_tracker.markdown +++ b/source/_components/device_tracker.bluetooth_le_tracker.markdown @@ -13,10 +13,6 @@ ha_iot_class: "Local Poll" ha_release: 0.27 --- -

-We have received numerous reports that this integration will have a big impact on the performance of the server. -

- This tracker discovers new devices on boot and in regular intervals and tracks Bluetooth low-energy devices periodically based on interval_seconds value. It is not required to pair the devices with each other. Devices discovered are stored with 'BLE_' as the prefix for device mac addresses in `known_devices.yaml`. @@ -24,7 +20,7 @@ Devices discovered are stored with 'BLE_' as the prefix for device mac addresses This platform requires pybluez to be installed. On Debian based installs, run ```bash -$ sudo apt install bluetooth libbluetooth-dev pkg-config libboost-python-dev libboost-thread-dev libglib2.0-dev python-dev +$ sudo apt install bluetooth ``` Before you get started with this platform, please note that: @@ -42,9 +38,7 @@ device_tracker: Configuration variables: -- **device_id** (*Optional*): The device ID for the Bluetooth device to be used for tracking. Defaults to `hci0`. - **track_new_devices** (*Optional*): If new discovered devices are tracked by default. Defaults to `True`. -- **scan_duration** (*Optional*): How long should the scanner be looking for BLE devices. Defaults to `10` seconds. - **interval_seconds** (*Optional*): Seconds between each scan for new devices. Defaults to `12` seconds. As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times. @@ -59,12 +53,6 @@ $ sudo apt-get install libcap2-bin $ sudo setcap 'cap_net_raw,cap_net_admin+eip' `readlink -f \`which python3\`` ``` -If you have installed Home Assistant with [AIO](/getting-started/installation-raspberry-pi-all-in-one/), you need to do the following command, this will grant access to Home Assistant to run the required command. - -```bash -$ sudo setcap cap_net_raw,cap_net_admin+eip /srv/homeassistant/homeassistant_venv/bin/python3 -``` - A restart of Home Assistant is required. For additional configuration variables check the [Device tracker page](/components/device_tracker/). diff --git a/source/_components/device_tracker.huawei_lte.markdown b/source/_components/device_tracker.huawei_lte.markdown new file mode 100644 index 00000000000..7beb8c788cc --- /dev/null +++ b/source/_components/device_tracker.huawei_lte.markdown @@ -0,0 +1,32 @@ +--- +layout: page +title: "Huawei LTE Router Device Tracker" +description: "Instructions on how to use Huawei LTE routers to track devices within Home Assistant." +date: 2018-09-08 20:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: huawei.svg +ha_category: Presence Detection +ha_release: 0.79 +--- + + +This platform offers presence detection by looking at connected devices to a [Huawei LTE router](https://consumer.huawei.com/en/smart-home/). + +This requires you to have set up the [Huawei LTE component](/components/huawei_lte/). + +## {% linkable_title Configuration %} + +To enable the sensor, add the following lines to your +`configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +device_tracker: + - platform: huawei_lte +``` + +See the [device tracker component page](/components/device_tracker/) +for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.nmap_tracker.markdown b/source/_components/device_tracker.nmap_tracker.markdown index 74ace37e238..11b0e0531db 100644 --- a/source/_components/device_tracker.nmap_tracker.markdown +++ b/source/_components/device_tracker.nmap_tracker.markdown @@ -2,7 +2,7 @@ layout: page title: "Nmap" description: "Instructions on how to integrate Nmap into Home Assistant." -date: 2015-03-23 19:59 +date: 2018-09-21 18:59 sidebar: true comments: false sharing: true @@ -15,6 +15,10 @@ featured: false As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (`192.168.1.1/24`) and the range notation (`192.168.1.1-255`). +

+ Please keep in mind that modern smart phones will usually turn off WiFi when they are idle. Simple trackers like this may not be reliable on their own. +

+ You might have to install the packages for `arp` and `nmap`. On Debian based hosts (for example Hassbian and Raspbian) do so by running `$ sudo apt-get install net-tools nmap`. On a Fedora host run `$ sudo dnf -y install nmap`.

@@ -39,6 +43,7 @@ Configuration variables: - **exclude** (*Optional*): Hosts not to include in nmap scanning. Scanning the host where Home Assistant is running can cause problems (websocket error), so excluding that host is a good idea. - **scan_options** (*Optional*): Configurable scan options for nmap. Default to `-F --host-timeout 5s` +## {% linkable_title Examples %} A full example for the `nmap` tracker could look like the following sample: @@ -69,10 +74,13 @@ In the above example, Nmap will be call with the process: An example of how the Nmap scanner can be customized: -Add the capabilities to Nmap. Be sure to specify the full path to wherever you installed Nmap: +### {% linkable_title Linux capabilities %} -`sudo setcap cap_net_raw,cap_net_admin,cap_net_bind_service+eip /usr/bin/nmap -` +On Linux systems you can extend the functionality of Nmap, without having to run it as root, by using *Linux capabilities*. Be sure to specify the full path to wherever you installed Nmap: + +```bash +$ sudo setcap cap_net_raw,cap_net_admin,cap_net_bind_service+eip /usr/bin/nmap +``` And you can set up the device tracker as ```yaml @@ -81,5 +89,4 @@ And you can set up the device tracker as scan_options: " --privileged -sP " ``` - See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.ping.markdown b/source/_components/device_tracker.ping.markdown index 04d2e764420..675150cb18c 100644 --- a/source/_components/device_tracker.ping.markdown +++ b/source/_components/device_tracker.ping.markdown @@ -15,6 +15,10 @@ ha_release: 0.36 The `ping` device tracker platform offers presence detection by using `ping` to send ICMP echo requests. This can be useful when devices are running a firewall and are blocking UDP or TCP packets but responding to ICMP requests (like Android phones). This tracker doesn't need to know the MAC address since the host can be on a different subnet. This makes this an option to detect hosts on a different subnet when `nmap` or other solutions don't work since `arp` doesn't work. +

+ Please keep in mind that modern smart phones will usually turn off WiFi when they are idle. Simple trackers like this may not be reliable on their own. +

+ ## {% linkable_title Configuration %} To use this presence detection in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown index faea7253981..1131fb1e1d2 100644 --- a/source/_components/device_tracker.snmp.markdown +++ b/source/_components/device_tracker.snmp.markdown @@ -13,7 +13,7 @@ ha_release: 0.7.5 --- -A lot WiFi access points and WiFi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of instances and metrics, like network interfaces, disks, and WiFi registrations. +A lot of WiFi access points and WiFi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of instances and metrics, like network interfaces, disks, and WiFi registrations.

This device tracker needs SNMP to be enabled on the router. It could be that you need to install the SNMP support manually. diff --git a/source/_components/digital_ocean.markdown b/source/_components/digital_ocean.markdown index fd5d744376b..c0dc3175c29 100644 --- a/source/_components/digital_ocean.markdown +++ b/source/_components/digital_ocean.markdown @@ -16,11 +16,11 @@ ha_iot_class: "Local Polling" The `digital_ocean` component allows you to access the information about your [Digital Ocean](https://www.digitalocean.com/) droplets from Home Assistant. -### {% linkable_title Setup %} +## {% linkable_title Setup %} Obtain your API key from your [Digital Ocean dashboard](https://cloud.digitalocean.com/settings/api/tokens). -### {% linkable_title Configuration %} +## {% linkable_title Configuration %} To integrate your Digital Ocean droplets with Home Assistant, add the following section to your `configuration.yaml` file: diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index 1edebdc702b..5ab929d212e 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -99,7 +99,7 @@ Valid values for ignore are: * `tellstick`: Telldus Live * `wink`: Wink Hub * `yamaha`: Yamaha media player - * `yeelight`: Yeelight Sunflower bulb + * `yeelight`: Yeelight lamps and bulbs (not only Yeelight Sunflower bulb) * `xiaomi_gw`: Xiaomi Aqara gateway Valid values for enable are: diff --git a/source/_components/doorbird.markdown b/source/_components/doorbird.markdown index 43f30816d94..839a77a2e91 100644 --- a/source/_components/doorbird.markdown +++ b/source/_components/doorbird.markdown @@ -8,13 +8,15 @@ comments: false sharing: true footer: true logo: doorbird.png -ha_category: Hub +ha_category: Doorbell ha_release: "0.54" ha_iot_class: "Local Polling" --- The `doorbird` implementation allows you to integrate your [DoorBird](http://www.doorbird.com/) device in Home Assistant. +## {% linkable_title Configuration %} + To connect your device, add the following to your `configuration.yaml` file: ```yaml @@ -94,4 +96,4 @@ Enabling any monitored condition will delete all registered notification service action: service: light.turn_on entity_id: light.side_entry_porch -``` \ No newline at end of file +``` diff --git a/source/_components/edp_redy.markdown b/source/_components/edp_redy.markdown new file mode 100644 index 00000000000..ed1bbdef7fe --- /dev/null +++ b/source/_components/edp_redy.markdown @@ -0,0 +1,45 @@ +--- +layout: page +title: "EDP re:dy" +description: "Instructions on how to integrate the EDP re:dy platform into Home Assistant." +date: 2018-09-04 16:30 +sidebar: true +comments: false +sharing: true +footer: true +logo: edp_redy.png +ha_category: Hub +ha_release: "0.79" +ha_iot_class: "Cloud Polling" +--- + +[EDP re:dy](https://www.edp.pt/particulares/servicos/redy/) is a Home Automation platform from Portuguese energy provider EDP, that allows control of appliances and other devices, as well as monitoring power consumption. This component allows integrating EDP re:dy into Home Assistant. + +## {% linkable_title Configuration %} + +You will need your re:dy login information (username and password) to use this component. + +To set it up, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +edp_redy: + username: YOUR_USERNAME + password: YOUR_PASSWORD +``` + +{% configuration %} +username: + description: The username for accessing your re:dy account. + required: true + type: string +password: + description: The password for accessing your re:dy account. + required: true + type: string +{% endconfiguration %} + +After configuring the component, it will automatically add to Home Assistant: + +* A switch per toggleable device (switch, plug, etc). +* A sensor per each device that reports power consumption (SmartMeter, plug, meter) diff --git a/source/_components/eufy.markdown b/source/_components/eufy.markdown index 60ec2a470dd..e2c00424fd5 100644 --- a/source/_components/eufy.markdown +++ b/source/_components/eufy.markdown @@ -38,17 +38,21 @@ eufy: name: Smart Switch ``` -access_token can be obtained by running: +`access_token can be obtained by running: -``` -curl -H "Content-Type: application/json" -d '{"client_id":"eufyhome-app", "client_Secret":"GQCpr9dSp3uQpsOMgJ4xQ", "email":"USERNAME", "password":"PASSWORD"}' https://home-api.eufylife.com/v1/user/email/login | jq +```bash +$ curl -H "Content-Type: application/json" \ + -d '{"client_id":"eufyhome-app", "client_Secret":"GQCpr9dSp3uQpsOMgJ4xQ", "email":"USERNAME", "password":"PASSWORD"}' \ + https://home-api.eufylife.com/v1/user/email/login \ + | jq ``` -replacing USERNAME and PASSWORD with the Eufy username and password. This will give an access_token. Then run: +replacing USERNAME and PASSWORD with the Eufy username and password. This will give an `access_token`. Then run: -``` -curl -H token:TOKEN -H category:Home https://home-api.eufylife.com/v1/device/list/devices-and-groups | jq +```bash +$ curl -H token:TOKEN -H category:Home \ + https://home-api.eufylife.com/v1/device/list/devices-and-groups | jq ``` -replacing TOKEN with the access_token from the previous command. This will provide the local_code for each device. +replacing TOKEN with the `access_token` from the previous command. This will provide the local_code for each device. diff --git a/source/_components/geo_location.geo_json_events.markdown b/source/_components/geo_location.geo_json_events.markdown new file mode 100644 index 00000000000..3be0ccc2fb2 --- /dev/null +++ b/source/_components/geo_location.geo_json_events.markdown @@ -0,0 +1,57 @@ +--- +layout: page +title: "GeoJSON Events" +description: "Instructions on how to integrate GeoJSON feeds into Home Assistant." +date: 2018-09-19 08:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: geo_location.png +ha_category: Geo Location +ha_iot_class: "Cloud Polling" +ha_release: "0.79" +--- + +The `geo_json_events` platform lets you integrate GeoJSON feeds. It retrieves events from a feed and shows information of those events filtered by distance to Home Assistant's location. +All entries in the GeoJSON feed must define a `geometry` which typically is a point or polygon with geo coordinates. In addition, this platform will look for a `title` key in the entry's `properties` and use that as the entity's name. + +Entities are generated, updated and removed automatically with each update from the GeoJSON feed. Each entity defines latitude and longitude and will be shown on the map automatically. The distance in kilometers is available as the state of each entity. + +The data is updated every 5 minutes. + +## {% linkable_title Configuration %} + +To integrate a GeoJSON feed, add the following lines to your `configuration.yaml`. This is an example configuration showing [earthquake data provided by the U.S. Geological Survey](https://earthquake.usgs.gov/earthquakes/feed/v1.0/geojson.php). + +```yaml +# Example configuration.yaml entry +geo_location: + - platform: geo_json_events + url: https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.geojson +``` + +{% configuration %} +url: + description: Full URL of the GeoJSON feed. + required: true + type: string +radius: + description: The distance in kilometers around the Home Assistant's coordinates in which events are considered. + required: false + type: string + default: 20km +{% endconfiguration %} + +## {% linkable_title Advanced Configuration Example %} + +When integrating several GeoJSON feeds, it may be useful to distinguish the entities of different feeds. The easiest way to do that is by defining an [`entity_namespace`](/docs/configuration/platform_options/#entity-namespace/) for each platform which will prefix each entity ID with the defined value. + +```yaml +# Example configuration.yaml entry +geo_location: + - platform: geo_json_events + url: https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.geojson + radius: 250 + entity_namespace: 'usgs_earthquakes' +``` diff --git a/source/_components/geo_location.markdown b/source/_components/geo_location.markdown index 2990c019514..c77243971a8 100644 --- a/source/_components/geo_location.markdown +++ b/source/_components/geo_location.markdown @@ -7,7 +7,7 @@ sidebar: true comments: false sharing: true footer: true -ha_category: Other +logo: geo_location.png ha_release: "0.78" --- diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown index 3530db78161..3cee8f16401 100644 --- a/source/_components/google_assistant.markdown +++ b/source/_components/google_assistant.markdown @@ -25,6 +25,37 @@ The Google Assistant component requires a bit more setup than most due to the wa To use Google Assistant, your Home Assistant configuration has to be externally accessible with a hostname and SSL certificate. If you haven't already configured that, you should do so before continuing.

+## {% linkable_title Setup %} + +You need to create an API Key with the [Google Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see [below](/#troubleshooting-the-request_sync-service)). If you don't provided it the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have setup this component you will need to call this service (or command) each time you add a new device that you wish to control via the Google Assistant integration. + +1. Create a new project in the [developer console](https://console.actions.google.com/). + a. Add/Import project, give it a name + b. Click on `Home Control` card, select the `Smart home` recommendation. + c. Create an Action, under the build section. Add in your Home Assistant URL: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant`, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / ip address and the port under which your Home Assistant is reachable. If you have set `api_password:` add this password to the URL. E.g., `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant?api_password=[YOUR API PASSWORD]`) + d. Click `Done`. Then click on `Overview`, which will lead you back to the app details screen. +2. `Account linking` is required for your app to interact with Home Assistant. Set this up under the `Quick Setup` section + a. Leave it at the default `No, I only want to allow account creation on my website` and select Next + b. For the `Linking type` select `OAuth` and `Implicit` + c. Client ID: The `client_id` from your Home Assistant configuration above + d. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant/auth`. If you have set `api_password:` add this password to the URL `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant/auth?api_password=[YOUR API PASSWORD]`) + e. Configure your client. Add scopes for `email` and `name`. + f. Testing instructions: Enter anything. It doesn't matter since you won't submit this app. +3. Back on the overview page. Click `Simulator` under `TEST`. You don't have to actually test . +4. If you haven't already added the component configuration to `configuration.yaml` file and restarted Home Assistant, you'll be unable to continue until you have. +5. Open the Google Assistant app and go into `Settings > Home Control` +6. Click the `+` sign, and near the bottom, you should have `[test] your app name`. Selecting that should lead you the screen where you can set rooms for your devices or nicknames for your devices. +7. If you want to allow other household users to control the devices: + a. Go to the settings for the project you created in point 1 in the developer console. + b. Under the gear icon, click `Permissions` + c. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role + d. Have the new user go to [developer console](https://console.actions.google.com/) and repeat steps starting from point 3 +8. If you want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project: + a. Go to the [cloud console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) + b. Select your project and click Enable Homegraph API + c. Go to Credentials, which you can find on the left navigation bar under the key icon, and select API Key from Create Credentials + d. Note down the generated API Key and use this in the configuration + ## {% linkable_title Configuration %} To enable this, add the following lines to your `configuration.yaml` file: @@ -73,11 +104,11 @@ agent_user_id: required: false type: string api_key: - description: An API Key generated for the project from [Google Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see step 9 below). If not provided then the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have setup this component you will need to call this service (or command) each time you add a new device that you wish to control via the Google Assistant integration. + description: Your API key. required: false type: string expose_by_default: - description: Expose devices in all supported domains by default. If set to false, you need to either expose domains or add the expose configuration option to each entity in entity_config and set it to true. + description: "Expose devices in all supported domains by default. If set to false, you need to either expose domains or add the expose configuration option to each entity in `entity_config` and set it to true." required: false default: True type: boolean @@ -114,6 +145,7 @@ entity_config: {% endconfiguration %} ### {% linkable_title Available domains %} + Currently, the following domains are available to be used with Google Assistant, listed with their default types: - group (on/off) @@ -135,35 +167,6 @@ $ cat /dev/urandom | fold -w 120 | head -n 1 | base64 -w 0 | tr -dc '0-9A-Za-z' If you're not using Linux, you can use sites such as [this one](https://www.browserling.com/tools/random-string) to generate a random string (containing mixed case letters and numbers) of up to 80 characters. -### {% linkable_title Setup %} - -1. Create a new project in the [developer console](https://console.actions.google.com/). - a. Add/Import project, give it a name - b. Click on `Home Control` card, select the `Smart home` recommendation - c. Create an Action, under the build section. Add in your home assistant url: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant`, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / ip address and the port under which your Home Assistant is reachable. If you have set `api_password:` add this password to the URL - eg `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant?api_password=[YOUR API PASSWORD]`) - d. Click `Done`. Then click on `Overview`, which will lead you back to the app details screen. -2. `Account linking` is required for your app to interact with Home Assistant. Set this up under the `Quick Setup` section - a. Leave it at the default `No, I only want to allow account creation on my website` and select Next - b. For the `Linking type` select `OAuth` and `Implicit` - c. Client ID: The `client_id` from your Home Assistant configuration above - d. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant/auth`. If you have set `api_password:` add this password to the URL `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant/auth?api_password=[YOUR API PASSWORD]`) - e. Configure your client. Add scopes for `email` and `name`. - f. Testing instructions: Enter anything. It doesn't matter since you won't submit this app. -3. Back on the overview page. Click `Simulator` under `TEST` - you don't have to actually test . -4. If you haven't already added the component configuration to `configuration.yaml` and restarted Home Assistant, you'll be unable to continue until you have. -5. Open the Google Assistant app and go into `Settings > Home Control` -6. Click the `+` sign, and near the bottom, you should have `[test] your app name`. Selecting that should lead you the screen where you can set rooms for your devices or nicknames for your devices. -7. If you want to allow other household users to control the devices: - a. Go to the settings for the project you created in point 1 in the developer console. - b. Under the gear icon, click `Permissions` - c. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role - d. Have the new user go to [developer console](https://console.actions.google.com/) and repeat steps starting from point 3 -8. If you want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project: - a. Go to the [cloud console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) - b. Select your project and click Enable Homegraph API - c. Go to Credentials, which you can find on the left navigation bar under the key icon, and select API Key from Create Credentials - d. Note down the generated API Key and use this in the configuration - ### {% linkable_title Troubleshooting the request_sync service %} The request_sync service requires that the initial sync from Google includes the agent_user_id. If not, the service will log an error that reads something like "Request contains an invalid argument". If this happens, then [unlink the account](https://support.google.com/googlehome/answer/7506443?hl=en-GB) from Home Control and relink. diff --git a/source/_components/habitica.markdown b/source/_components/habitica.markdown new file mode 100644 index 00000000000..fbd51c31267 --- /dev/null +++ b/source/_components/habitica.markdown @@ -0,0 +1,132 @@ +--- +layout: page +title: "Habitica" +description: "Instructions on enabling Habitica support for your Home Assistant" +date: 2018-08-09 00:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: habitica.png +ha_category: Hub +ha_version: 0.78 +ha_iot_class: "Cloud Polling" +--- + +This component allows you to monitor and manage your Habitica profile. This component exposes the [Habitica's API](https://habitica.com/apidoc/) as a Home Assistant service. It supports multiple users and allows you to automate checking out your habits and daily tasks or casting magics using Home Assistant. +This component enables usage of [`sensor.habitica` platform.](/components/sensor.habitica/) +To use the component you should use this example configuration: + +```yaml +# Minimum viable configuration.yaml entry +habitica: + - api_user: 'REPLACE_ME_WITH_YOUR_USER_ID' + api_key: 'REPLACE_ME_WITH_YOUR_API_KEY' +``` + +You can specify several users, providing `api_user` and `api_key` for each. +At runtime you will be able to use API for each respective user by their Habitica's username. +You can override this by passing `name` key, this value will be used instead of the username. +If you are hosting your own instance of Habitica, you can specify a URL to it in `url` key. + +{% configuration %} +api_user: + description: "Habitica's API user ID. This value can be grabbed from [account setting](https://habitica.com/user/settings/api)" + required: true + type: string +api_key: + description: "Habitica's API password (token). This value can be grabbed from [account setting](https://habitica.com/user/settings/api) by pressing 'Show API token'" + required: true + type: string +name: + description: "Override for Habitica's username. Will be used for service calls" + required: false + type: string + default: Deduced at startup +url: + description: "URL to your Habitica instance, if you are hosting your own" + required: false + type: string + default: http://habitica.com +sensors: + description: List of sensors to generate for this user. If you don't specify this entry then the default (all sensors) will be generated. If you specify this entry empty then no sensors will be generated. + required: false + type: list + default: all (`name`, `hp`, `maxHealth`, `mp`, `maxMP`, `exp`, `toNextLevel`, `lvl`, `gp`, `class`) +{% endconfiguration %} + +### {% linkable_title API Service Parameters %} + +The API is exposed to Home Assistant as a service called `habitica.api_call`. To call it you should specify this keys in service data: + +| Service data attribute | Required | Type | Description | +|----------------------|--------|--------|----------------| +| `name` | yes | string | Habitica's username as per `configuration.yaml` entry. | +| `path` | yes | [string] | Items from API URL in form of an array with method attached at the end. See the example below. | +| `args` | no | map | Any additional json or url parameter arguments. See the example below and [apidoc](https://habitica.com/apidoc/). | + +A successful call to this service will fire an event `habitica_api_call_success`. + +| Event data attribute | Type | Description | +|----------------------|--------|----------------| +| `name` | string | Copied from service data attribute. | +| `path` | [string] | Copied from service data attribute. | +| `data` | map | Deserialized `data` field of JSON object Habitica's server returned in response to api call. For more info see [docs](https://habitica.com/apidoc/). | + +#### Let's consider some examples on how to call the service. + +For example, let's say that there is a configured `habitica` platform for user `xxxNotAValidNickxxx` with their respective `api_user` and `api_key`. +Let's create a new task (a todo) for this user via Home Assistant. There is an [API call](https://habitica.com/apidoc/#api-Task-CreateUserTasks) for this purpose. +To create a new task one should hit `https://habitica.com/api/v3/tasks/user` endpoint with `POST` request with a json object with task properties. +So let's call the API on `habitica.api_call`. +* The `name` key becomes `xxxNotAValidNickxxx`. +* The `path` key is trickier. + * Remove 'https://habitica.com/api/v3/' at the beginning of the endpoint URL. + * Split the remaining on slashes (/) and **append the lowercase method** at the end. + * You should get `["tasks", "user", "post"]`. To get a better idea of the API you are recommended to try all of the API calls in IPython console [using this package](https://github.com/ASMfreaK/habitipy/blob/master/README.md). +* The `args` key is more or less described in the [docs](https://habitica.com/apidoc/). + +Combining all together: +call `habitica.api_call` with data +``` +{ + "name": "xxxNotAValidNickxxx", + "path": ["tasks", "user", "post"], + "args": {"text": "Use API from Home Assistant", "type": "todo"} +} +``` + +This call will create a new todo on `xxxNotAValidNickxxx`'s account with text `Use API from Home Assistant` like this: + +![example task created](/images/screenshots/habitica_new_task.png) + +Also an event `habitica_api_call_success` will be fired with the following data: +``` +{ + "name": "xxxNotAValidNickxxx", + "path": ["tasks", "user", "post"], + "data": { + "challenge": {}, + "group": {"approval": {"required": false, + "approved": false, + "requested": false}, + "assignedUsers": [], + "sharedCompletion": "recurringCompletion"}, + "completed": false, + "collapseChecklist": false, + "type": "todo", + "notes": "", + "tags": [], + "value": 0, + "priority": 1, + "attribute": "str", + "text": "Use API from Home Assistant", + "checklist": [], + "reminders": [], + "_id": "NEW_TASK_UUID", + "createdAt": "2018-08-09T18:03:27.759Z", + "updatedAt": "2018-08-09T18:03:27.759Z", + "userId": "xxxNotAValidNickxxx's ID", + "id": "NEW_TASK_UUID"} +} +``` diff --git a/source/_components/homekit.markdown b/source/_components/homekit.markdown index 74bb8a7c48a..b1ea53ff54d 100644 --- a/source/_components/homekit.markdown +++ b/source/_components/homekit.markdown @@ -272,6 +272,7 @@ The following components are currently supported: | sensor | TemperatureSensor | All sensors that have `Celsius` or `Fahrenheit` as their `unit_of_measurement` or `temperature` as their `device_class`. | | sensor | HumiditySensor | All sensors that have `%` as their `unit_of_measurement` and `humidity` as their `device_class`. | | sensor | AirQualitySensor | All sensors that have `pm25` as part of their `entity_id` or `pm25` as their `device_class` | +| sensor | CarbonMonoxideSensor | All sensors that have `co` as their `device_class` | | sensor | CarbonDioxideSensor | All sensors that have `co2` as part of their `entity_id` or `co2` as their `device_class` | | sensor | LightSensor | All sensors that have `lm` or `lx` as their `unit_of_measurement` or `illuminance` as their `device_class` | | switch | Switch | Represented as a switch by default but can be changed by using `type` within `entity_config`. | diff --git a/source/_components/homematicip_cloud.markdown b/source/_components/homematicip_cloud.markdown index 2a4c981e2e0..42ee4b27e2a 100644 --- a/source/_components/homematicip_cloud.markdown +++ b/source/_components/homematicip_cloud.markdown @@ -65,9 +65,11 @@ authtoken: - homematicip_cloud.binary_sensor - Window and door contact (*HmIP-SWDO*) - - Smoke sensor and alarm (*HmIP-SWSD*) + - Rotary Handle Sensor (*HmIP-SRH*) + - Smoke sensor and alarm (*HmIP-SWSD*) - Motion detectors (*HmIP-SMI*) - Motion detectors and push button (*HmIP-SMI55*) + - Water detector (*HmIP-SWD*) - homematicip_cloud.climate - Radiator thermostat (*HmIP-eTRV,-2*) @@ -82,6 +84,7 @@ authtoken: - Wall-mounted thermostat (*HmIP-WTH*) - Temperature and humidity sensor (*HmIP-STH*) - Temperature and humidity Sensor with display (*HmIP-STHD*) + - Outdoor temperature and humidity sensor (*HmIP-STHO*) - Illuminance sensor (*HmIP-SMI, 55*) - homematicip_cloud.switch diff --git a/source/_components/huawei_lte.markdown b/source/_components/huawei_lte.markdown new file mode 100644 index 00000000000..7d6afd4afa6 --- /dev/null +++ b/source/_components/huawei_lte.markdown @@ -0,0 +1,49 @@ +--- +layout: page +title: "Huawei LTE Routers" +description: "Instructions on how to integrate Huawei LTE routers with Home Assistant." +date: 2018-09-08 20:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: huawei.svg +ha_category: Network +ha_release: 0.79 +--- + +The Huawei LTE router integration for Home Assistant allows you to observe +and control [Huawei LTE routers](https://consumer.huawei.com/en/smart-home/). + +The integration provides: + +* a sensor with device, signal, and traffic information +* a device tracker for connected devices + +## {% linkable_title Configuration %} + +To enable the component, add the following lines to your +`configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +huawei_lte: + - url: http://192.168.100.1/ + username: YOUR_USERNAME + password: YOUR_PASSWORD +``` + +{% configuration %} +url: + description: URL of the router web interface. + required: true + type: url +username: + description: The username used for the router web interface. + required: true + type: string +password: + description: The password used for the router web interface. + required: true + type: string +{% endconfiguration %} diff --git a/source/_components/insteon.markdown b/source/_components/insteon.markdown index e2518a09784..7cb8e635ec7 100644 --- a/source/_components/insteon.markdown +++ b/source/_components/insteon.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon" -description: "Instructions on how to setup an Insteon Modem (PLM or Hub) locally within Home Assistant." +description: "Instructions on how to set up an Insteon Modem (PLM or Hub) locally within Home Assistant." date: 2018-08-20 16:00 sidebar: true comments: false @@ -18,19 +18,20 @@ linked INSTEON devices to be used within Home Assistant as binary sensors, lights, fans, sensors and switches. Device support is provided by the underlying [insteonplm] package. It is known to work with the [2413U] USB and [2412S] RS242 flavors of PLM and the [2448A7] USB stick. It has also been -tested to work with the [2245] Hub. +tested to work with the [2242] and [2245] Hubs. [insteonplm]: https://github.com/nugget/python-insteonplm [2413U]: https://www.insteon.com/powerlinc-modem-usb [2412S]: https://www.insteon.com/powerlinc-modem-serial [2448A7]: https://www.smarthome.com/insteon-2448a7-portable-usb-adapter.html [2245]: https://www.insteon.com/insteon-hub/ +[2242]: https://www.insteon.com/support-knowledgebase/2014/9/26/insteon-hub-owners-manual ### {% linkable_title INSTEON Modem configuration %} -To setup a Powerline Modem (PLM) device such as the [2413U], use the following -configuration: +To set up an INSTEON Powerline Modem (PLM) device such as the [2413U], use the +following configuration: ```yaml # PLM configuration variables @@ -38,15 +39,26 @@ insteon: port: SERIAL_PORT ``` -To setup an INSTEON Hub such as the [2245], use the following configuration: - +To set up an INSTEON Hub model [2245], use the following configuration: + ```yaml -# Hub configuration variables +# Hub 2245 configuration variables insteon: host: HOST ip_port: IP_PORT username: USERNAME password: PASSWORD + hub_version: 2 +``` + +To set up an INSTEON Hub model [2242], use the following configuration: + +```yaml +# Hub 2242 configuration variables +insteon: + host: HOST + ip_port: IP_PORT + hub_version: 1 ``` Addtional configuration items are available: @@ -71,14 +83,23 @@ insteon: ``` Configuration variables: - **port** (*Required for PLM setup*): The serial or USB port for your device, - e.g., `/dev/ttyUSB0` -- **host** (*Required for Hub setup*): The host name or IP address of the Hub -- **ip_port** (*Optional for Hub setup*): The IP port number of the Hub. - (default value is 25105) -- **username** (*Required for Hub setup*): The username to login to the local - Hub -- **password** (*Required for Hub setup*): The password to login to the local - Hub + e.g., `/dev/ttyUSB0` or `COM3` +- **host** (*Required for Hub setup*): The host name or IP address of the Hub. +- **ip_port** (*Optional for Hub setup*): The IP port number of the Hub. For + Hub model [2245] (i.e. Hub version 2) the default port is 25105. For the Hub + model [2242] (i.e. Hub version 1) the default port is 9761. Use the Insteon + app to find the port number for your specific Hub. +- **username** (*Required for Hub version 2 setup*): The username to login in + to the local Hub. This is required for Hub [2245] (i.e. Hub version 2) setup. + You can find your Hub username on the bottom of the Hub or you can use the + Insteon app. +- **password** (*Required for Hub version 2 setup*): The password to login in + to the local Hub. This is required for Hub [2245] (i.e. Hub version 2) setup. + You can find your Hub password on the bottom of the Hub or you can use the + Insteon app. +- **hub_version** (*Required for Hub version 1 setup*): The Hub version number + where model [2242] is Hub version 1 and model [2245] is Hub version 2. + (Default is 2) - **device_override** (*Optional*): Override the default device definition - *ADDRESS* is found on the device itself in the form 1A.2B.3C or 1a2b3c - *CATEGORY* is found in the back of the device's User Guide in the form of @@ -92,16 +113,16 @@ Configuration variables: - *UNITCODE* is the X10 unit code values 1 - 16 - *PLATFORM* is the Home Assistant Platform to associate the device with. The following platforms are supported - - binary_sensor: Used for on/off devices or keypad buttons that are read only. + - binary_sensor: Used for on/off devices or keypad buttons that are read-only. - light: Used for dimmable X10 devices - switch: Used for On/Off X10 devices - *STEPS* is the number of dim/bright steps the device supports. Used for dimmable X10 devices only. Default value is 22. -- **x10_all_units_off** (*Optional*): Creates an binary_sensor that responds +- **x10_all_units_off** (*Optional*): Creates a binary_sensor that responds to the X10 standard command for All Units Off. -- **x10_all_lights_on** (*Optional*): Creates an binary_sensor that responds +- **x10_all_lights_on** (*Optional*): Creates a binary_sensor that responds to the X10 standard command for All Lights On -- **x10_all_lights_off** (*Optional*): Creates an binary_sensor that responds +- **x10_all_lights_off** (*Optional*): Creates a binary_sensor that responds to the X10 standard command for All Lights Off ### {% linkable_title Autodiscovery %} @@ -111,27 +132,27 @@ per device. Subsequent startups will occur much quicker using cached device information. If a device is not recognized during autodiscovery, you can add the device to the **device_override** configuration. -In order for a device to be discovered it must be linked to the INSTEON Modem +In order for a device to be discovered, it must be linked to the INSTEON Modem as either a responder or a controller. ### {% linkable_title Linking Devices to the INSTEON Modem %} In order for any two Insteon devices to talk with one another, they must be -linked. For an overview of device linking please read the Insteon page on +linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Development Tools] service calls. The following services are available: - **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking -mode. The IM can be set as as controller or a responder. If the IM is a -controler, put the IM into linking mode then press the SET button on the -device. If the IM is a responer, press the SET button on the device then +mode. The IM can be set as a controller or a responder. If the IM is a +controller, put the IM into linking mode then press the SET button on the +device. If the IM is a responder, press the SET button on the device then put the IM into linking mode. - **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an All-Link record from the All-Link Database of the IM and a device. Once the IM is set to delete the link, press the SET button on the corresponding device to complete the process. - **insteon.load_all_link_database**: Load the All-Link Database for a -device. WARNING - Loading a device All-Link database may take a LONG time and +device. WARNING - Loading a device All-Link database may take a LONG time and may need to be repeated to obtain all records. - **insteon.print_all_link_database**: Print the All-Link Database for a device. Requires that the All-Link Database is loaded first. @@ -174,7 +195,7 @@ devices. INSTEON devices are added to Home Assistant using the platform(s) that make the most sense given the model and features of the hardware. The features of the -INSTEON device are built into the Home Assistant platform. Changing the +INSTEON devices are built into the Home Assistant platform. Changing the platform is not recommended. There are two primary uses for the **device_override** feature. - Devices that do not respond during autodiscovery. This is common for battery @@ -185,7 +206,7 @@ platform is not recommended. There are two primary uses for the ### {% linkable_title Example Configuration with Options%} ```yaml -# Full example of insteon configuration with customizations and overrides +# Full example of Insteon configuration with customizations and overrides homeassistant: customize: @@ -205,7 +226,7 @@ insteon: ### {% linkable_title What NOT to do %} -Insteon Modem is a top level component and device discovery will identify +Insteon Modem is a top-level component and device discovery will identify the Home Assistant platform the device belongs in. As such, do not declare Insteon devices in other platforms. For example, this configuration will NOT work: @@ -224,19 +245,18 @@ events. The following events are available: - **insteon.button_on** - **address**: (required) The Insteon device address in lower case without dots (e.g. 1a2b3c) - - **button**: (Optional) The button id in lower case. For an 4 button remote - the values are a to d. For an 8 button remote the values are a to g. For - a one button remote this field is not used. + - **button**: (Optional) The button id in lower case. For a 4-button remote + the values are `a` to `d`. For an 8 button remote the values are `a` to `g`. For + a one-button remote this field is not used. - **insteon.button_of** - **address**: (required) The Insteon device address in lower case without dots (e.g. 1a2b3c) - - **button**: (Optional) The button id in lower case. For an 4 button remote - the values are a to d. For an 8 button remote the values are a to g. For - a one button remote this field is not used. + - **button**: (Optional) The button id in lower case. For a 4-button remote + the values are a to d. For an 8 button remote the values are `a` to `g`. For + a one-button remote this field is not used. -This allows the mini-remotes to be configured as - -Here is an example of how to use these events for automations: +This allows the mini-remotes to be configured as triggers for automations. Here +is an example of how to use these events for automations: ``` automation: @@ -276,8 +296,8 @@ The INSTEON Hub has three known issues that are inherent to the design of the Hub: 1. If you see multiple error messages in the log file stating the Hub -connection is closed and reconnection has failed, this generally requires -the Hub to be restarted in order to reconnect. +connection is closed, and reconnection has failed, this generally requires +the Hub to be restarted to reconnect. 2. You cannot use both Home Assistant and the INSTEON app. If you do, the changes made in the app will not appear in Home Assistant. Changes made in diff --git a/source/_components/knx.markdown b/source/_components/knx.markdown index 89e9a0c4129..802b288f4c2 100644 --- a/source/_components/knx.markdown +++ b/source/_components/knx.markdown @@ -33,7 +33,7 @@ There is currently support for the following device types within Home Assistant: - [Notify](/components/notify.knx) - [Scene](/components/scene.knx) -### {% linkable_title Configuration %} +## {% linkable_title Configuration %} To use your KNX in your installation, add the following lines to your `configuration.yaml` file: @@ -77,8 +77,8 @@ knx: ```yaml knx: - fire_event: True - fire_event_filter: ["1/0/*", "6/2,3,4-6/*"] + fire_event: True + fire_event_filter: ["1/0/*", "6/2,3,4-6/*"] ``` - **fire_event** (*Optional*): If set to True, platform will write all received KNX messages to event bus @@ -105,21 +105,20 @@ KNX component is able to expose time or sensor values to KNX bus. The component ```yaml # Example configuration.yaml entry knx: - expose: - - type: 'temperature' - entity_id: 'sensor.owm_temperature' - address: '0/0/2' - - type: 'time' - address: '0/0/1' - - type: 'datetime' - address: '0/0/23' + expose: + - type: 'temperature' + entity_id: 'sensor.owm_temperature' + address: '0/0/2' + - type: 'time' + address: '0/0/1' + - type: 'datetime' + address: '0/0/23' ``` * **type**: Type of the exposed value. Either time or datetime or any supported type of [KNX Sensor](/components/sensor.knx/) (e.g., "temperature" or "humidity"). * **entity_id**: Entity id of the HASS component to be exposed. Not necessary for types time and datetime. * **address**: KNX group address. - ### {% linkable_title Known issues %} Due to lame multicast support the routing abstraction and the gateway scanner only work with Python >=3.5. diff --git a/source/_components/konnected.markdown b/source/_components/konnected.markdown index df50d5abc37..1467787a493 100644 --- a/source/_components/konnected.markdown +++ b/source/_components/konnected.markdown @@ -25,20 +25,20 @@ This component requires the [`discovery`](https://www.home-assistant.io/componen ### {% linkable_title Configuration %} -A `konnected` section must be present in the `configuration.yml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them: +A `konnected` section must be present in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them: ```yaml # Example configuration.yaml entry konnected: access_token: REPLACE_ME_WITH_A_RANDOM_STRING devices: - - id: 6001948bcd53 + - id: 438a388bcd53 binary_sensors: - zone: 1 type: door switches: - zone: out - - id: 5ccf7f438a38 + - id: 8bcd53438a38 binary_sensors: - pin: 2 type: door @@ -62,7 +62,7 @@ devices: type: list keys: id: - description: The MAC address of the NodeMCU WiFi module with colons/punctuation removed, for example `68c63a8bcd53`. You can usually find the mac address in your router's client list. Or, check the home-assistant.log for log messages from automatically discovered devices. + description: The MAC address of the NodeMCU WiFi module with colons/punctuation removed, for example `68c63a8bcd53`. You can usually find the mac address in your router's client list. Or, check the home-assistant.log for log messages from automatically discovered devices. required: true type: string binary_sensors: @@ -83,6 +83,11 @@ devices: description: The name of the device used in the front end. required: false default: automatically generated + inverse: + type: boolean + description: Inverts the open/closed meaning of a binary sensor circuit. Commonly needed for normally open wired smoke alarm circuits. + required: false + default: false switches: description: A list of actuators (on/off switches) connected to the device. See [Konnected Switch](/components/switch.konnected/) for configuration variables. required: false @@ -105,12 +110,12 @@ devices: momentary: description: Duration of the momentary pulse in milliseconds. To make a half-second momentary contact using a relay for a garage door opener, set this value to `500`. required: false - pause: + pause: description: Time of the pause between pulses in milliseconds when also used with _momentary_ and _repeat_. To make a door chime "beep" with piezo buzzer, set this value to `55`, set _momentary_ to `65`, and _repeat_ to `3` or `4`. required: false repeat: description: Number of times to repeat a momentary pulse. Set to `-1` to make an infinite repeat. This is useful as an alarm or warning when used with a piezo buzzer. - required: false + required: false {% endconfiguration%} #### {% linkable_title Configuration Notes %} @@ -133,6 +138,7 @@ konnected: - zone: 2 type: smoke name: 'Bedroom Smoke Detector' + inverse: true - zone: 3 type: motion name: 'Test Motion' @@ -143,7 +149,7 @@ konnected: name: 'Beep Beep' momentary: 65 pause: 55 - repeat: 4 + repeat: 4 - zone: 5 name: Warning momentary: 65 @@ -182,6 +188,9 @@ Konnected runs on an ESP8266 board with the NodeMCU firmware. It is commonly use ### {% linkable_title Revision History %} +#### 0.79 +* Added `inverse` configuration option for binary sensors. + #### 0.77 * Added support for momentary and beep/blink switches. [[#15973](https://github.com/home-assistant/home-assistant/pull/15973)] * Decouple entity initialization from discovery, enabling devices to recover faster after a Home Assistant reboot. [[#16146](https://github.com/home-assistant/home-assistant/pull/16146)] @@ -191,4 +200,4 @@ Konnected runs on an ESP8266 board with the NodeMCU firmware. It is commonly use * Adds `api_host` configuration option [[#14896](https://github.com/home-assistant/home-assistant/pull/14896)] #### 0.70 -* Initial release +* Initial release diff --git a/source/_components/light.blinksticklight.markdown b/source/_components/light.blinksticklight.markdown index d5cc53a99fc..bdd41852704 100644 --- a/source/_components/light.blinksticklight.markdown +++ b/source/_components/light.blinksticklight.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "Blinkstick" +title: "Blinkstick Light" description: "Instructions on how to setup Blinkstick lights within Home Assistant." date: 2015-10-08 10:00 sidebar: true diff --git a/source/_components/light.blinkt.markdown b/source/_components/light.blinkt.markdown index 69b72eb1d13..cee02bd7118 100644 --- a/source/_components/light.blinkt.markdown +++ b/source/_components/light.blinkt.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "Blinkt!" +title: "Blinkt! Light" description: "Instructions on how to setup Blinkt! RGB LED lights within Home Assistant." date: 2017-04-30 9:00 sidebar: true diff --git a/source/_components/light.knx.markdown b/source/_components/light.knx.markdown index 5587f134ecc..4a229b62586 100644 --- a/source/_components/light.knx.markdown +++ b/source/_components/light.knx.markdown @@ -18,6 +18,8 @@ The `knx` light component is used as in interface to switching/light actuators. The `knx` component must be configured correctly, see [KNX Component](/components/knx). +## {% linkable_title Configuration %} + To use your KNX light in your installation, add the following lines to your `configuration.yaml` file: ```yaml @@ -31,12 +33,14 @@ light: Configuration variables: +- **address** (*Required*): KNX group address for switching the light on and off. - **name** (*Optional*): A name for this device used within Home Assistant. -- **address**: KNX group address for switching the light on and off. - **brightness_address** (Optional): KNX group address for dimming light. - **state_address** (*Optional*): separate KNX group address for retrieving the switch state of the light. - **brightness_state_address** (*Optional*): separate KNX group address for retrieving the dimmed state of the light. - **color_address** (*Optional*): separate KNX group address for setting the color of the light. +- **color_state_address** (*Optional*): separate KNX group address for retrieving the color of the light. Some KNX devices can change their state internally without any messages on the KNX bus, e.g., if you configure a timer on a channel. The optional `state_address` can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object. For switching/light actuators that are only controlled by a single group address and can't change their state internally, you don't have to configure the state address. + diff --git a/source/_components/light.mqtt_json.markdown b/source/_components/light.mqtt_json.markdown index 6e70c8be891..cd4f65737e5 100644 --- a/source/_components/light.mqtt_json.markdown +++ b/source/_components/light.mqtt_json.markdown @@ -56,6 +56,10 @@ name: required: false type: string default: MQTT JSON Light +unique_id: + description: An ID that uniquely identifies this light. If two lights have the same unique ID, Home Assistant will raise an exception. + required: false + type: string command_topic: description: The MQTT topic to publish commands to change the light’s state. required: true @@ -262,4 +266,4 @@ Home Assistant expects the hue values to be in the range 0 to 360 and the satura - [esphomelib](https://github.com/OttoWinter/esphomelib) is a library for ESP8266 and ESP32 boards that has many of Home Assistant's MQTT features (like [discovery](/docs/mqtt/discovery/)) pre-implemented and provides high-level abstractions for components such as lights or sensors. -- [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/components/light.mqtt_json/) platform and supports ON/OFF, RGBW colours, brightness, colour temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/docs/mqtt/discovery/)) and the MQTT Last Will and Testament is enabled as well. \ No newline at end of file +- [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/components/light.mqtt_json/) platform and supports ON/OFF, RGBW colours, brightness, colour temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/docs/mqtt/discovery/)) and the MQTT Last Will and Testament is enabled as well. diff --git a/source/_components/light.template.markdown b/source/_components/light.template.markdown old mode 100755 new mode 100644 diff --git a/source/_components/light.yeelight.markdown b/source/_components/light.yeelight.markdown index c446d5950f7..d5d5adb4e80 100644 --- a/source/_components/light.yeelight.markdown +++ b/source/_components/light.yeelight.markdown @@ -28,7 +28,7 @@ light: name: Living Room transition: 1000 use_music_mode: True #(defaults to False) - save_on_change: False #(defaults to True) + save_on_change: True #(defaults to False) 192.168.1.13: name: Front Door ``` @@ -39,10 +39,11 @@ Configuration variables: - **name** (*Optional*): A friendly name for the device. - **transition** (*Optional*, default 350): Smooth transitions over time (in ms). - **use_music_mode** (*Optional*, default False): Enable music mode. -- **save_on_change** (*Optional*, default True): Saves the bulb state when changed from Home Assistant. +- **save_on_change** (*Optional*, default False): Saves the bulb state in its nonvolatile memory when changed from Home Assistant. #### {% linkable_title Music mode %} Per default the bulb limits the amount of requests per minute to 60, a limitation which can be bypassed by enabling the music mode. In music mode the bulb is commanded to connect back to a socket provided by the component and it tries to keep the connection open, which may not be wanted in all use-cases. +**Also note that bulbs in music mode will not update their state to "unavailable" if they are disconnected, which can cause delays in Home Assistant**. ### {% linkable_title Initial setup %}

@@ -59,6 +60,7 @@ This component is tested to work with the following models. If you have a differ - **YLDP01YL**: LED Bulb (White) - **YLDP02YL**: LED Bulb (Color) - **YLDP03YL**: LED Bulb (Color) - E26 +- **YLDP05YL**: LED Bulb (White) II - **YLDP06YL**: LED Bulb (Color) II - **YLDD01YL**: Lightstrip (Color) - **YLDD02YL**: Lightstrip (Color) diff --git a/source/_components/linode.markdown b/source/_components/linode.markdown index 581f4822c16..ccd090b47e8 100644 --- a/source/_components/linode.markdown +++ b/source/_components/linode.markdown @@ -15,7 +15,7 @@ ha_iot_class: "Cloud Polling" The `linode` component allows you to access the information about your [Linode](https://linode.com) systems from Home Assistant. -## {% linkable_title sETUP %} +## {% linkable_title Setup %} Obtain your oAuth2 Access Token from Linode account. diff --git a/source/_components/lock.bmw_connected_drive.markdown b/source/_components/lock.bmw_connected_drive.markdown old mode 100755 new mode 100644 diff --git a/source/_components/lock.mqtt.markdown b/source/_components/lock.mqtt.markdown index ff8eb051702..a1689fbd199 100644 --- a/source/_components/lock.mqtt.markdown +++ b/source/_components/lock.mqtt.markdown @@ -101,8 +101,9 @@ In this section you will find some real life examples of how to use this lock. The example below shows a full configuration for a MQTT lock. +{% raw %} ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry lock: - platform: mqtt name: Frontdoor @@ -113,8 +114,9 @@ lock: optimistic: false qos: 1 retain: true - value_template: '{% raw %}{{ value.x }}{% endraw %}' + value_template: '{{ value.x }}' ``` +{% endraw %} Keep an eye on retaining messages to keep the state as you don't want to unlock your door by accident when you restart something. diff --git a/source/_components/logi_circle.markdown b/source/_components/logi_circle.markdown new file mode 100644 index 00000000000..5b891755da2 --- /dev/null +++ b/source/_components/logi_circle.markdown @@ -0,0 +1,40 @@ +--- +layout: page +title: "Logi Circle" +description: "Instructions on how to integrate your Logi Circle cameras within Home Assistant." +date: 2018-09-08 11:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: logi_circle.png +ha_category: Camera +ha_release: 0.79 +ha_iot_class: "Cloud Polling" +--- + +The `logi_circle` implementation allows you to integrate your [Logi Circle](https://circle.logi.com/) cameras in Home Assistant. + +## {% linkable_title Configuration %} + +To integrate cameras linked with your [Logi Circle](https://circle.logi.com/) account, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +logi_circle: + username: YOUR_USERNAME + password: YOUR_PASSWORD +``` + +{% configuration %} +username: + description: The username for accessing your Logi Circle account. + required: true + type: string +password: + description: The password for accessing your Logi Circle account. + required: true + type: string +{% endconfiguration %} + +Finish its configuration by visiting the [Logi Circle camera](/components/camera.logi_circle/) or [Logi Circle sensor](/components/sensor.logi_circle/) documentation. diff --git a/source/_components/mailbox.asterisk_cdr.markdown b/source/_components/mailbox.asterisk_cdr.markdown new file mode 100644 index 00000000000..61597bdfeff --- /dev/null +++ b/source/_components/mailbox.asterisk_cdr.markdown @@ -0,0 +1,15 @@ +--- +layout: page +title: "Asterisk Call Data Recorder" +description: "Instructions on how to integrate an Asterisk CDR within Home Assistant." +date: 2018-09-12 06:30 +sidebar: true +comments: false +sharing: true +footer: true +logo: asterisk.png +ha_category: Mailbox +ha_release: 0.79 +--- + +The Asterisk Call Data Recorder provides access to Asterisk call logs on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail component](/components/asterisk_mbox/) configuration if the `asterisk_mbox_server` is configured to provide CDR data. More information on configuring the server can be found in the [Asterisk PBX configuration guide](/docs/asterisk_mbox/). diff --git a/source/_components/map.markdown b/source/_components/map.markdown old mode 100755 new mode 100644 diff --git a/source/_components/media_player.onkyo.markdown b/source/_components/media_player.onkyo.markdown index 630182ba6df..0737d7a9124 100644 --- a/source/_components/media_player.onkyo.markdown +++ b/source/_components/media_player.onkyo.markdown @@ -79,3 +79,26 @@ List of source names: - multi-ch - xm - sirius + +### {% linkable_title Example `play_media` script %} + +The `play_media` function can be used in script to play radio station by preset number. +Not working for NET radio. + +```yaml +# Example play_media script +# +script: + radio1: + alias: "Radio 1" + sequence: + - service: media_player.turn_on + data: + entity_id: media_player.onkyo + - service: media_player.play_media + data: + entity_id: media_player.onkyo + media_content_type: "radio" + media_content_id: "1" + +``` diff --git a/source/_components/media_player.spotify.markdown b/source/_components/media_player.spotify.markdown index 8de7240135f..0f2c27f5d05 100644 --- a/source/_components/media_player.spotify.markdown +++ b/source/_components/media_player.spotify.markdown @@ -75,3 +75,6 @@ You can send playlists to spotify via the "media_content_type": "playlist" and " In this example this is a URI link to the Reggae Infusions playlist, [this support document from Spotify](https://support.spotify.com/us/using_spotify/share_music/why-do-you-have-two-different-link-formats/) explains how to get this URI value to use for playlists in the Spotify component. +## {% linkable_title Unsupported devices %} + +- **Sonos**: Although its a Spotify Connect device, it is not supported by the official Spotify API. diff --git a/source/_components/microsoft_face.markdown b/source/_components/microsoft_face.markdown index d7d8cdc7ed0..2d9cb4318f4 100644 --- a/source/_components/microsoft_face.markdown +++ b/source/_components/microsoft_face.markdown @@ -8,14 +8,18 @@ comments: false sharing: true footer: true logo: microsoft.png -ha_category: Hub +ha_category: Image Processing ha_release: "0.37" --- The `microsoft_face` component platform is the main component for Microsoft Azure Cognitive service [Face](https://www.microsoft.com/cognitive-services/en-us/face-api). All data are stored in your own private instance in the Azure cloud. +## {% linkable_title Setup %} + You need an API key, which is free, but requires an [Azure registration](https://azure.microsoft.com/de-de/free/) using your Microsoft ID. The free resource (*F0*) is limited to 20 requests per minute and 30k requests in a month. If you don't want to use the Azure cloud, you can also get an API key by registering with [cognitive-services](https://www.microsoft.com/cognitive-services/en-us/subscriptions). Please note that all keys on cognitive services must be recreated every 90 days. +## {% linkable_title Configuration %} + To enable the Microsoft Face component, add the following to your `configuration.yaml`: ```yaml diff --git a/source/_components/mqtt.markdown b/source/_components/mqtt.markdown index 275cac866ed..c9d73254459 100644 --- a/source/_components/mqtt.markdown +++ b/source/_components/mqtt.markdown @@ -11,19 +11,14 @@ logo: mqtt.png ha_category: Hub featured: true ha_release: pre 0.7 -ha_iot_class: depends +ha_iot_class: local push --- MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport. Your first step to get MQTT and Home Assistant working is to choose a [broker](/docs/mqtt/broker). -To integrate MQTT into Home Assistant, add the following section to your `configuration.yaml` file. Keep in mind that the minimal setup will run with [an embedded MQTT broker](/docs/mqtt/broker#embedded-broker): - -```yaml -# Example configuration.yaml entry -mqtt: -``` +To integrate MQTT into Home Assistant, add the following section to your `configuration.yaml` file. To connect to your [own MQTT broker](/docs/mqtt/broker#run-your-own): @@ -33,9 +28,15 @@ mqtt: broker: IP_ADDRESS_BROKER ``` -

-The minimal setup uses the embedded MQTT broker, however a separate broker is advised for more stability. -

+You can also use the [embedded MQTT broker](/docs/mqtt/broker#embedded-broker). A separate broker is advised for more stability. + +```yaml +# Example configuration.yaml entry +mqtt: + password: hello +``` + +This allows you to connect to the MQTT broker with user `homeassistant` and password `hello`. ## {% linkable_title Additional features %} diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 57e6ce10e38..1578015218b 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -72,13 +72,24 @@ The `html5` platform can only function if all of the following requirements are Assuming you have already added the platform to your configuration: 1. Open Home Assistant in Chrome or Firefox. -2. Assuming you have met all the [requirements](#requirements) above, you should see a new slider for Push Notifications through the profile page Profile > Push notifications. +2. Load profile page by clicking on the badge next to the Home Assistant title in the sidebar. Assuming you have met all the [requirements](#requirements) above then you should see a new slider for Push Notifications. If the slider is greyed out, ensure you are viewing Home Assistant via its external HTTPS address. If the slider is not visible, ensure you are not in the user configuration (Sidebar, Configuration, Users, View User). 3. Slide it to the on position. 4. Within a few seconds you should be prompted to allow notifications from Home Assistant. 5. Assuming you accept, that's all there is to it! 6. (Optional, but highly recommended!) Open the `html5_push_registrations.conf` file in your configuration directory. You will see a new entry for the browser you just added. Rename it from `unnamed device` to a name of your choice, which will make it easier to identify later. _Do not change anything else in this file!_ You need to restart Home Assistant after making any changes to the file. +### {% linkable_title Testing %} + +Assuming the previous test completed successfully and your browser was registered, you can test the notification as follows: + +1. Open Home Assistant in Chrome or Firefox. +2. Open the sidebar and click the Services button at the bottom (shaped like a remote control), located below the Developer Tools. +3. From the Services dropdown, search for your HTML5 notify service (E.G. notify.NOTIFIER_NAME) and select it. +4. In the Service Data text box enter: {"message":"hello world"}, then press the CALL SERVICE button. +5. If everything worked you should see a popup notification. + + ### {% linkable_title Usage %} The `html5` platform accepts a standard notify payload. However, there are also some special features built in which you can control in the payload. diff --git a/source/_components/notify.knx.markdown b/source/_components/notify.knx.markdown index 78945fc3761..4e81f1e2362 100644 --- a/source/_components/notify.knx.markdown +++ b/source/_components/notify.knx.markdown @@ -17,6 +17,8 @@ The `knx` notify platform allows you to send notifications to [KNX](http://www.k The `knx` component must be configured correctly, see [KNX Component](/components/knx). +## {% linkable_title Configuration %} + To use your KNX switch in your installation, add the following lines to your `configuration.yaml` file: ```yaml @@ -26,5 +28,8 @@ notify: address: '5/1/10' ``` +Configuration variables: + +* **address** (*Required*): KNX group address of the notification. * **name** (*Optional*): A name for this device used within Home Assistant. -* **address**: KNX group address of the notification + diff --git a/source/_components/notify.nfandroidtv.markdown b/source/_components/notify.nfandroidtv.markdown index e1bf8659ba8..6ec1639edb2 100644 --- a/source/_components/notify.nfandroidtv.markdown +++ b/source/_components/notify.nfandroidtv.markdown @@ -10,15 +10,14 @@ footer: true logo: nfandroidtv.png ha_category: Notifications ha_release: 0.32 -ha_iot_class: "Local Polling" --- -Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google). +Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google). You can use this plarform to send notifications to your Android TV device. An overlay with the message content will appear for a configurable amount of seconds and then disapper again. Sending images (e.g. security cam) is supported too. The notifications are in the global scope of your Android TV device. They will be displayed regardless of which application is running. -When setting this up be aware, that there are two apps: one for your smartphone to send notifications (not required for this platform) and one for your Android TV device to receive the notifications. The app available in the store of your target device is the one that is needed to display notifications sent from Home Assistant. The In-App purchases only apply to the client for Android smartphones, so there isn't any limit when pushing notifications from Home Assistant. +When setting this up be aware, that there are two apps: one for your smartphone to send notifications (not required for this platform) and one for your Android TV device to receive the notifications. The app available in the store of your Android TV device is the one that is needed to display notifications sent from Home Assistant. The In-App purchases only apply to the client for Android smartphones, so there isn't any limit when pushing notifications from Home Assistant. To enable the notification platform, add the following to your `configuration.yaml` file: @@ -35,6 +34,7 @@ Configuration variables: - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **host** (*Required*): IP address of the Android TV / FireTV device. - **duration** (*Optional*): The duration in seconds for which the notification will be displayed. Default is 5 seconds. +- **fontsize** (*Optional*): Has to be one of: small, medium (default), large, max - **position** (*Optional*): Has to be one of: bottom-right (default), bottom-left, top-right, top-left, center - **color** (*Optional*): Has to be one of: grey (default), black, indigo, green, red, cyan, teal, amber, pink - **transparency** (*Optional*): Has to be one of: 0%, 25% (default), 50%, 75%, 100% @@ -48,6 +48,7 @@ This is a fully customized JSON you can use to test how the final notification w "message": "Messagetext", "title": "My Notification", "data":{ + "fontsize": "large", "position":"center", "duration":2, "transparency":"0%", @@ -56,3 +57,48 @@ This is a fully customized JSON you can use to test how the final notification w } } ``` + +### {% linkable_title Service data for sending images %} + +The following attributes can be placed inside `data` to send images. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `file` | yes | Groups the attributes for file upload. If present, either `url` or `path` have to be provided. +| `path ` | yes | Local path of an image file. Is placed inside `file`. +| `url` | yes | URL of an image file. Is placed inside `file`. +| `username` | yes | Username if the url requires authentication. Is placed inside `file`. +| `password` | yes | Password if the url requires authentication. Is placed inside `file`. +| `auth` | yes | If set to `digest` HTTP-Digest-Authentication is used. If missing, HTTP-BASIC-Authentication is used. Is placed inside `file`. + +Example for posting file from URL: + +```json +{ + "message":"Messagetext", + "title":"My Notification", + "data":{ + "file":{ + "url":"http://[url to image file]", + "username":"optional user, if necessary", + "password":"optional password, if necessary", + "auth":"digest" + } + } +} +``` + +Example for posting file from local path: + +```json +{ + "message":"Messagetext", + "title":"My Notification", + "data":{ + "file":{ + "path":"/path/to/file.ext" + } + } +} +``` +Please note that `path` is validated against the `whitelist_external_dirs` in the `configuration.yaml`. diff --git a/source/_components/notify.pushsafer.markdown b/source/_components/notify.pushsafer.markdown index 5b1ce8ed54c..6060016e1c5 100644 --- a/source/_components/notify.pushsafer.markdown +++ b/source/_components/notify.pushsafer.markdown @@ -12,7 +12,6 @@ ha_category: Notifications ha_release: 0.39 --- - The [Pushsafer service](https://www.pushsafer.com/) is a platform for the notify component. This allows you to send messages to the user using Pushsafer. In order to get a private or alias key you need to go to the [Pushsafer website](https://www.pushsafer.com) and register. @@ -90,6 +89,10 @@ Message to two devices and one device group with formatted text and local image. "url": "https://www.home-assistant.io/", "urltitle": "Open Home Assistant", "time2live": "10", + "priority": "2", + "retry": "60", + "expire": "600", + "answer": "1", "picture1": { "path":"C:\\Users\\Kevin\\AppData\\Roaming\\.homeassistant\\image-760-testimage.jpg" } diff --git a/source/_components/notify.slack.markdown b/source/_components/notify.slack.markdown index 3e384990109..699a57ec236 100644 --- a/source/_components/notify.slack.markdown +++ b/source/_components/notify.slack.markdown @@ -15,12 +15,22 @@ ha_release: pre 0.7 The `slack` platform allows you to deliver notifications from Home Assistant to [Slack](https://slack.com/). -If you are planning to use Slack as yourself then you need to obtain a [Slack API token](https://api.slack.com/web?sudo=1) to be able to send notifications. +## {% linkable_title Setup %} + +If you are planning to use Slack as yourself then you'll need to create a [new app](https://api.slack.com/apps) under your Slack.com account. After creating the app, access the OAuth & Permissions link under the Features heading in the sidebar. Your OAuth Access Token should be located there. This is the key that you'll use in your `configuration.yaml` file. + +

+There is an app credential Verification Token on the Basic Settings of your app. This is **not** the API key you want. +

+ +You will also need to ensure that you have added the appropriate scope when configuring your app. In this case, in the Scopes section, add the `Send messages as user` scope, e.g., (chat:write:user). It is also possible to use Slack bots as users. Just create a new bot at https://[YOUR_TEAM].slack.com/apps/build/custom-integration and use the provided token for that. You can add an icon from the frontend for Home Assistant and give the bot a meaningful name. Don't forget to invite the bot to the room where you want to get the notifications. +## {% linkable_title Configuration %} + To enable the Slack notification in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -85,6 +95,7 @@ Example for posting file from local path: } } ``` + Please note that `path` is validated against the `whitelist_external_dirs` in the `configuration.yaml`. Example for posting formatted attachment: @@ -106,4 +117,3 @@ Example for posting formatted attachment: Please note that both `message` is a required key, but is always shown, so use an empty (`""`) string for `message` if you don't want the extra text. 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 a4893d35c97..acb6f184bed 100644 --- a/source/_components/openuv.markdown +++ b/source/_components/openuv.markdown @@ -74,7 +74,7 @@ sensors: description: the conditions to create sensors from required: false type: list - default: all ( `current_ozone_index`, `current_uv_index`, `current_uv_level`, `max_uv_index`, `safe_exposure_time_type_1`, `safe_exposure_time_type_2`, `safe_exposure_time_type_3`, `safe_exposure_time_type_4`, `safe_exposure_time_type_5`, `safe_exposure_time_type_6` ) + default: all ( `current_ozone_level`, `current_uv_index`, `current_uv_level`, `max_uv_index`, `safe_exposure_time_type_1`, `safe_exposure_time_type_2`, `safe_exposure_time_type_3`, `safe_exposure_time_type_4`, `safe_exposure_time_type_5`, `safe_exposure_time_type_6` ) {% endconfiguration %} ## {% linkable_title Binary Sensor Types %} diff --git a/source/_components/plant.markdown b/source/_components/plant.markdown index 6beaa00557f..df2947e19da 100644 --- a/source/_components/plant.markdown +++ b/source/_components/plant.markdown @@ -8,12 +8,14 @@ comments: false sharing: true footer: true logo: home-assistant.png -ha_category: Other +ha_category: Environment ha_release: 0.44 --- This`plant`component lets you merge moisture, conductivity, light intensity, temperature and battery level for a plant into a single UI element. It also supports setting minimum and maximum values for each measurement and will change its state to "problem" if it is not within those limits. +## {% linkable_title Configuration %} + To use your `plant` sensor in your installation, add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/rainmachine.markdown b/source/_components/rainmachine.markdown index 7bb254ef5d3..61ebb649104 100644 --- a/source/_components/rainmachine.markdown +++ b/source/_components/rainmachine.markdown @@ -10,7 +10,7 @@ footer: true logo: rainmachine.png ha_category: Irrigation ha_release: 0.69 -ha_iot_class: "Cloud Polling" +ha_iot_class: "Local Polling" --- The `rainmachine` component is the main component to integrate all platforms diff --git a/source/_components/recorder.markdown b/source/_components/recorder.markdown index 8c8b5a4cbc0..d843e6f1200 100644 --- a/source/_components/recorder.markdown +++ b/source/_components/recorder.markdown @@ -18,7 +18,7 @@ Home Assistant uses [SQLAlchemy](http://www.sqlalchemy.org/) as Object Relationa The default database engine is [SQLite](https://www.sqlite.org/) which doesn't require any configuration. The database is stored in your Home Assistant configuration directory (`.homeassistant`) and called `home-assistant_v2.db`. -To setup the `recorder` component in your installation, add the following to your `configuration.yaml` file: +To change the defaults for `recorder` component in your installation, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -73,7 +73,7 @@ recorder: type: List {% endconfiguration %} -Define domains and entities to `exclude` (aka. blacklist). This is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like `weblink`) or rarely change (`updater` or `automation`). +Define domains and entities to `exclude` (aka. blacklist). This is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains. Usually, these are entities/domains which do not change (like `weblink`) or rarely change (`updater` or `automation`). ```yaml # Example configuration.yaml entry with exclude @@ -103,7 +103,7 @@ recorder: - media_player ``` -Use the `include` list to define the domains/entities to record, and exclude some of them with in the `exclude` list. This makes sense if you for instance include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in. +Use the `include` list to define the domains/entities to record, and exclude some of them within the `exclude` list. This makes sense if you, for instance, include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in. ```yaml # Example configuration.yaml entry with include and exclude @@ -119,7 +119,7 @@ recorder: - sensor.date ``` -If you only want to hide events from e.g., your history, take a look at the [`history` component](/components/history/). Same goes for logbook. But if you have privacy concerns about certain events or neither want them in history or logbook, you should use the `exclude`/`include` options of the `recorder` component, that way they aren't even in your database. That way you can save storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`). +If you only want to hide events from e.g., your history, take a look at the [`history` component](/components/history/). Same goes for the logbook. But if you have privacy concerns about certain events or neither want them in history or logbook, you should use the `exclude`/`include` options of the `recorder` component, that way they aren't even in your database. That way you can save storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`). ### {% linkable_title Service `purge` %} @@ -128,7 +128,7 @@ Call the service `recorder.purge` to start a purge task which deletes events and | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `keep_days` | yes | The number of history days to keep in recorder database (defaults to the component `purge_keep_days` configuration) -| `repack` | yes | Rewrite the entire database, possibly saving some disk space (only supported for SQLite) +| `repack` | yes | Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses. ### {% linkable_title Restore State %} @@ -154,18 +154,28 @@ If the `recorder` component is activated then some components support `restore_s | MySQL (pymysql) | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | | PostgreSQL | `postgresql://SERVER_IP/DB_NAME` | | PostgreSQL | `postgresql://scott:tiger@SERVER_IP/DB_NAME` | +| PostgreSQL (Socket) | `postgresql://@/DB_NAME` | | MS SQL Server | `mssql+pymssql://user:pass@SERVER_IP/DB_NAME?charset=utf8` |

If you use MariaDB 10 you need to add port 3307 to the SERVER_IP, e.g., `mysql://user:password@SERVER_IP:3307/DB_NAME?charset=utf8`. +

-+If you are running a database server instance on the same server as Home Assistant then you must ensure that this service starts before Home Assistant. For a Linux instance running Systemd (Raspberry Pi, Debian, Ubuntu and others) then you should edit the service file. +

+Unix Socket connections always bring performance advantages over TCP, if the database on the same host as the `recorder` instance (i.e. `localhost`).

+ +

+If you want to use Unix Sockets for PostgreSQL you need to modify the `pg_hba.conf`. See [PostgreSQL](#postgresql)

+ +### {% linkable_title Database startup %} + +If you are running a database server instance on the same server as Home Assistant then you must ensure that this service starts before Home Assistant. For a Linux instance running Systemd (Raspberry Pi, Debian, Ubuntu and others) then you should edit the service file. ```bash $ sudo nano /etc/systemd/system/home-assistant@homeassistant.service ``` -and add the service for PostgreSQL: +and add the service for the database, for example, PostgreSQL: ``` [Unit] @@ -178,7 +188,6 @@ Save the file then reload `systemctl`: ```bash $ sudo systemctl daemon-reload ``` -

## {% linkable_title Installation notes %} @@ -212,7 +221,7 @@ $ pip3 install mysqlclient After installing the dependencies, it is required to create the database manually. During the startup, Home Assistant will look for the database specified in the `db_url`. If the database doesn't exist, it will not automatically create it for you. -Once Home Assistant finds the database, with right level of permissions, all the required tables will then be automatically created and the data will be populated accordingly. +Once Home Assistant finds the database, with the right level of permissions, all the required tables will then be automatically created and the data will be populated accordingly. ### {% linkable_title PostgreSQL %} @@ -223,6 +232,22 @@ $ sudo apt-get install postgresql-server-dev-X.Y $ pip3 install psycopg2 ``` +For using Unix Sockets, add the following line to your [`pg_hba.conf`](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html): + +`local DB_NAME USER_NAME peer` + +Where `DB_NAME` is the name of your database and `USER_NAME` is the name of the user running the Home Assistant instance (see [securing your installation](/docs/configuration/securing/)). + +Reload the PostgreSQL configuration after that: +```bash +$ sudo -i -u postgres psql -c "SELECT pg_reload_conf();" + pg_reload_conf +---------------- + t +(1 row) +``` +A service restart will work as well. + ### {% linkable_title MS SQL Server %} For MS SQL Server you may have to install a few dependencies: diff --git a/source/_components/remote.harmony.markdown b/source/_components/remote.harmony.markdown old mode 100755 new mode 100644 diff --git a/source/_components/remote.itach.markdown b/source/_components/remote.itach.markdown old mode 100755 new mode 100644 diff --git a/source/_components/remote.markdown b/source/_components/remote.markdown old mode 100755 new mode 100644 diff --git a/source/_components/scene.knx.markdown b/source/_components/scene.knx.markdown index e77b6571811..7fd18417d87 100644 --- a/source/_components/scene.knx.markdown +++ b/source/_components/scene.knx.markdown @@ -16,6 +16,10 @@ The `knx` scenes platform allows you to trigger [KNX](http://www.knx.org) scenes The `knx` component must be configured correctly, see [KNX Component](/components/knx). +## {% linkable_title Configuration %} + +To use your KNX scence in your installation, add the following to your `configuration.yaml` file: + ```yaml # Example configuration.yaml entry scene: @@ -27,8 +31,7 @@ scene: Configuration variables: +- **address** (*Required*): KNX group address of the binary sensor. +- **scene_number** (*Required*): Zero-indexed KNX scene number to be activated. - **name** (*Optional*): A name for this device used within Home Assistant. -- **address**: KNX group address of the binary sensor. -- **scene_number** KNX scene number to be activated. - diff --git a/source/_components/sensor.bloomsky.markdown b/source/_components/sensor.bloomsky.markdown index 61b850de1e1..d2e1ca31a50 100644 --- a/source/_components/sensor.bloomsky.markdown +++ b/source/_components/sensor.bloomsky.markdown @@ -16,6 +16,8 @@ ha_iot_class: "Cloud Polling" The `bloomsky` sensor component allows you to view the measurements made by sensors in the [BloomSky](https://www.bloomsky.com) weather station. This can work in concert with the [BloomSky camera](/components/camera.bloomsky). +## {% linkable_title Configuration %} + To enable these sensors in your installation, set up the [BloomSky component](/components/bloomsky) with your API key add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/sensor.bom.markdown b/source/_components/sensor.bom.markdown index af149f35bf9..7774077d9cf 100644 --- a/source/_components/sensor.bom.markdown +++ b/source/_components/sensor.bom.markdown @@ -39,6 +39,8 @@ sensor: - gust_kt - air_temp - dewpt + - local_date_time + - local_date_time_full - press - press_qnh - press_msl diff --git a/source/_components/sensor.cert_expiry.markdown b/source/_components/sensor.cert_expiry.markdown index 23682318933..99b0578b76b 100644 --- a/source/_components/sensor.cert_expiry.markdown +++ b/source/_components/sensor.cert_expiry.markdown @@ -8,13 +8,15 @@ comments: false sharing: true footer: true logo: home-assistant.png -ha_category: System Monitor +ha_category: Network ha_release: 0.44 ha_iot_class: "depends" --- The `cert_expiry` sensor fetches information from a configured URL and displays the certificate expiry in days. +## {% linkable_title Configuration %} + To add the Certificate Expiry sensor to your installation, add these options to `configuration.yaml` file: ```yaml diff --git a/source/_components/sensor.daikin.markdown b/source/_components/sensor.daikin.markdown index 250da44a727..5d9ba959592 100644 --- a/source/_components/sensor.daikin.markdown +++ b/source/_components/sensor.daikin.markdown @@ -16,12 +16,8 @@ ha_iot_class: "Local Polling" The `daikin` sensor platform integrates Daikin air conditioning systems into Home Assistant, enabling displaying the following parameters: -- **inside temperature** -- **outside temperature** - -

-Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant. -

+- Inside temperature +- Outside temperature ## {% linkable_title Configuration %} @@ -54,6 +50,3 @@ monitored_conditions: description: The current temperature measured outside the house. {% endconfiguration %} -

- Please note that some AC devices may report outside temperature only when they are turned on. -

diff --git a/source/_components/sensor.edp_redy.markdown b/source/_components/sensor.edp_redy.markdown new file mode 100644 index 00000000000..4071a509467 --- /dev/null +++ b/source/_components/sensor.edp_redy.markdown @@ -0,0 +1,18 @@ +--- +layout: page +title: "EDP re:dy Sensor" +description: "Instructions on how to integrate the EDP re:dy sensors into Home Assistant." +date: 2018-09-04 16:30 +sidebar: true +comments: false +sharing: true +footer: true +logo: edp_redy.png +ha_category: Sensor +ha_release: "0.79" +ha_iot_class: "Cloud Polling" +--- + +See the [EDP re:dy main component](/components/edp_redy/) for configuration instructions. + +This sensor platform will provide a sensor per each EDP re:dy device that reports power consumption (SmartMeter, plug, meter). \ No newline at end of file diff --git a/source/_components/sensor.fints.markdown b/source/_components/sensor.fints.markdown index e871ba3cb97..986e84e7c79 100644 --- a/source/_components/sensor.fints.markdown +++ b/source/_components/sensor.fints.markdown @@ -10,66 +10,73 @@ footer: true ha_category: Finance ha_release: "0.70" ha_iot_class: "Local Push" -logo: home-assistant.png --- With the FinTS sensor, you can fetch your account information from your bank. This only works with banks that support the FinTS (aka. HBCI) standard. The FinTS standard used by many German banks. So if you do not have a German bank account, this will most likely not work for you. To find out if your bank supports FinTS, check the bank's website or call their hotline. ## {% linkable_title Configuration %} +To find out the configuration for your bank, check their website or call their hotline. Do not use random information you find on the Internet! As you're storing your bank account information in the Home Assistant configuration: Make sure that this configuration is not accessible to anyone. + For each account you have with the bank, a separate sensor is created. If you have several accounts with a bank, you can select which ones you want to have, and you can also give the accounts a name. {% raw %} ```yaml # Example configuration.yaml entry sensor: - - platform: fints - bank_identification_number: - username: - pin: - url: + - platform: fints + bank_identification_number: ID_FOR_YOUR_BANK + username: YOUR_FINTS_USERNAME + pin: YOUR_PIN + url: URL_FOR_YOUR_BANK ``` {% endraw %} -To find out the configuration for your bank, check their website or call their hotline. Do not use random information you find on the Internet! As you're storing your bank account information in the Home Assistant configuration: make sure that this configuration is not accessible to anyone. - {% configuration %} - sensors: - description: List of your sensors. - required: true - type: map - keys: - name: - description: (optional) name of the bank. - required: false - type: string - bank_identification_number: - description: Bank identification number, in most cases the "Bankleitzahl". - required: true - type: string - username: - description: Your FinTS username. - required: true - type: string - pin: - description: Your FinTS PIN or password. - required: true - type: string - url: - description: URL of your bank's FinTS server. - required: true - type: string - accounts: - description: (optional) You can configure with of the accounts of your bank shall be shown in Home Assistant. If this attribute is set, only the accounts listed here are shown. - required: false - type: list - keys: - account: - description: For balance accounts use the IBAN of the account for holdings accounts use the classic account number. - required: true - type: string - name: - description: (optional) Use this field to give the account a meaningful name. - required: false - type: string +name: + description: Name of the bank. + required: false + type: string +bank_identification_number: + description: Bank identification number, in most cases the "Bankleitzahl". + required: true + type: string +username: + description: Your FinTS username. + required: true + type: string +pin: + description: Your FinTS PIN or password. + required: true + type: string +url: + description: URL of your bank's FinTS server. + required: true + type: string +accounts: + description: The balance accounts to show. If not set then all accounts will show up. + required: false + type: list + keys: + account: + description: The IBAN of the blance account. + required: true + type: string + name: + description: Use this field to give the account a meaningful name. + required: false + type: string +holdings: + description: The holding accounts of your bank. If not set then all accounts will show up. + required: false + type: list + keys: + account: + description: The classic account number. + required: true + type: string + name: + description: Use this field to give the account a meaningful name. + required: false + type: string {% endconfiguration %} diff --git a/source/_components/sensor.geizhals.markdown b/source/_components/sensor.geizhals.markdown index c9780740569..636751da35b 100644 --- a/source/_components/sensor.geizhals.markdown +++ b/source/_components/sensor.geizhals.markdown @@ -13,7 +13,6 @@ ha_iot_class: "Cloud Polling" ha_release: "0.51" --- - The `geizhals` sensor will give you the best price of a product from [Geizhals](https://geizhals.de) or related site. With this information can be used in e.g., automations to notify you when a price drops. To enable this sensor, add the following lines to your `configuration.yaml` file: @@ -23,16 +22,16 @@ To enable this sensor, add the following lines to your `configuration.yaml` file sensor: - platform: geizhals name: qc35 - product_id: 1453021 + product_id: 1696985 ``` Configuration variables: - **name** (*Required*): The internal name of the product in Home Assistant. -- **product_id** (*Required*): ID of the product. Get the ID from the geizhals website of your chosen product by clicking on the *Price History* tab, e.g., [here](https://geizhals.de/?phist=1453021). The URL of this site reveals the ID, e.g., with `product_id: 1453021`. +- **product_id** (*Required*): ID of the product. Get the ID from the Geizhals website of your chosen product by opening the *Price History* in a new browser tab (right-click on the price history > open in new tab). +The URL of this site reveals the ID, e.g. `https://geizhals.de/?phist=1696985` with a `product_id` of `1696985`. - **description** (*Optional*): The name of the product in the front end. -- **domain** (*Optional*): Domain which should be used for the request. Set this to `geizhals.at`, `geizhals.eu`, `geizhals.de`, `skinflint.co.uk` or `cenowarka.pl`. Defaults to `geizhals.de`. -- **regex** (*Optional*): Regular expression to parse the price. Default: `\D\s(\d*)[\,|\.](\d*)`. +- **locale** (*Optional*): Localisation which should be used for the request. Set this to `AT`, `EU`, `DE`, `UK` or `PL`. Defaults to `DE`. #### {% linkable_title Extended example %} @@ -41,8 +40,7 @@ Configuration variables: sensor: - platform: geizhals name: qc35 - product_id: 1453021 + product_id: 1696985 description: "Bose QC35" - domain: 'geizhals.de' - regex: '\D\s(\d*)[\,|\.](\d*)' + locale: "DE" ``` diff --git a/source/_components/sensor.habitica.markdown b/source/_components/sensor.habitica.markdown new file mode 100644 index 00000000000..4e94148bb9f --- /dev/null +++ b/source/_components/sensor.habitica.markdown @@ -0,0 +1,21 @@ +--- +layout: page +title: "Habitica Sensor" +description: "Instructions on enabling Habitica support for your Home Assistant" +date: 2018-08-09 00:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: habitica.png +ha_category: Sensor +ha_iot_class: "Cloud Polling" +ha_version: 0.78 +--- + +The `habitica` sensor platform allows you to view and monitor your player data from [Habitica](https://habitica.com/) in Home Assistant. + +

+You must have the [`habitica` component](/components/habitica/) +configured to use this platform. After configuring that component, sensors specified there will automatically appear. +

diff --git a/source/_components/sensor.huawei_lte.markdown b/source/_components/sensor.huawei_lte.markdown new file mode 100644 index 00000000000..682d3bc0518 --- /dev/null +++ b/source/_components/sensor.huawei_lte.markdown @@ -0,0 +1,51 @@ +--- +layout: page +title: "Huawei LTE Router Sensor" +description: "Instructions on how to integrate Huawei LTE router sensors into Home Assistant." +date: 2018-09-08 20:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: huawei.svg +ha_category: Network +ha_iot_class: "Local Polling" +ha_release: 0.79 +--- + +The `huawei_lte` sensor platform allows you to monitor Huawei LTE routers. + +This requires you to have set up the [Huawei LTE component](/components/huawei_lte/). + +## {% linkable_title Configuration %} + +To enable the sensor, add the following lines to your +`configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + - platform: huawei_lte + monitored_conditions: + - device_information.SoftwareVersion + - device_signal.rssi + - traffic_statistics.CurrentDownloadRate + - traffic_statistics.TotalConnectTime +``` + +Configuration variables: + +**monitored_conditions** array (*Optional*): Defines the data to monitor as sensors. Defaults to a few generally available data items expected to be available on most boxes. The names here are dot separated paths to information returned by the router. The data set varies by router model; to see what your router provides, set logging level to debug and watch homeassistant.components.huawei_lte debug entries. The following list contains a few example paths just to illustrate the syntax; these may not be available on all routers or their semantics may differ, and there are quite likely many more that are not listed here. + + - **device_information.SoftwareVersion**: Software version. + - **device_information.WanIPAddress**: WAN interface IP address. + - **device_information.WanIPv6Address**: WAN interface IP address. + - **device_signal.rsrq**: The signal RSRQ value. + - **device_signal.rsrp**: The signal RSRP value. + - **device_signal.rssi**: The signal RSSI value. + - **device_signal.sinr**: The signal SINR value. + - **traffic_statistics.CurrentDownloadRate**: Current download rate, bytes/sec. + - **traffic_statistics.CurrentUploadRate**: Current upload rate, bytes/sec. + - **traffic_statistics.TotalUpload**: Total bytes uploaded since last reset. + - **traffic_statistics.TotalDownload**: Total bytes downloaded since last reset. + - **traffic_statistics.TotalConnectTime**: Total time connected since last reset. diff --git a/source/_components/sensor.jewish_calendar.markdown b/source/_components/sensor.jewish_calendar.markdown new file mode 100644 index 00000000000..c9f6f8c7ec6 --- /dev/null +++ b/source/_components/sensor.jewish_calendar.markdown @@ -0,0 +1,104 @@ +--- +layout: page +title: "Jewish Calendar" +description: "Instructions on how to integrate the Jewish Calendar sensor within Home Assistant." +date: 2018-09-09 00:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: home-assistant.png +ha_category: Calendar +ha_iot_class: "Local Push" +ha_release: "0.80" +--- + +The Jewish Calendar (`jewish_calendar`) sensor platform displays a variety of information related to the Jewish Calendar as a variety of sensors. + +## {% linkable_title Configuration %} + +To enable this sensor in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + - platform: jewish_calendar +``` + +{% configuration %} +language: + required: false + default: hebrew + description: Whether to represent the sensors in Hebrew (א' תשרי תשע"ט) or English characters (1 Tishri 5779). + type: string +latitude: + required: false + description: Latitude for time calculations of the sensor. + default: Home Assistant location + type: int +longitude: + required: false + description: Longitude for time calculations of the sensor. + default: Home Assistant location + type: int +disapora: + required: false + description: Consider the location as diaspora or not for calculation of the weekly portion and holidays. + default: False + type: string +sensors: + required: false + default: date + description: List of available sensors. + keys: + date: + description: Show the hebrew date for today. + weekly_portion: + description: Show the weekly portion (parshat hashavu'a) - _At the moment only shows up on Saturday's_. + holiday_name: + description: If it is a holiday, show the name of the holiday. + holyness: + description: On a scale of 1 to 9 show the level of holyness _(see below)_. + first_light: + description: First light of dawn (Alot Hashachar - עלות השחר). + gra_end_shma: + description: Last time for reading of the Shma according to the GR"A. + mga_end_shma: + description: Last time for reading of the Shma according to the MG"A. + plag_mincha: + description: Time of the Plag Hamincha. + first_stars: + description: Time at which the first stars are visible (Tset Hakochavim - צאת הכוכבים). +{% endconfiguration %} + +### {% linkable_title Holyness levels %} + +1. Mido'rayta - by Torah ordination (Rosh Hashana, Yom Kippur, Pesach, Shavuot, Sukkot) +2. Erev Yom Kippur +3. Hol Hamo'ed +4. Hanukka and Purim +5. Fast days +6. Yom Yerushalayim and Yom Haatsmaut +7. Lag ba'omer and Tu bishvat +8. Memorial days: yom hazikaron and yom hashoah +9. Days mentioned by the Israeli parliament: Rabin memorial day, Ze'ev Zhabotinsky day, etc. + +## {% linkable_title Full configuration sample %} + +```yaml +# Example configuration.yaml entry +sensor: + - platform: jewish_calendar + language: english + disapora: True + sensors: + - date + - weekly_portion + - holiday_name + - holyness + - first_light + - gra_end_shma + - mga_end_shma + - plag_mincha + - first_stars +``` diff --git a/source/_components/sensor.knx.markdown b/source/_components/sensor.knx.markdown index f7e78920229..6e0921c341a 100644 --- a/source/_components/sensor.knx.markdown +++ b/source/_components/sensor.knx.markdown @@ -17,8 +17,26 @@ The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) sensor The `knx` component must be configured correctly, see [KNX Component](/components/knx). +## {% linkable_title Configuration %} + To use your KNX sensor in your installation, add the following lines to your `configuration.yaml` file: +```yaml +# Example configuration.yaml entry +sensor: + - platform: knx + name: Heating.Valve1 + address: '2/0/0' +``` + + + +- **address** (*Required*): KNX group address of the sensor. +- **name** (*Optional*): A name for this device used within Home Assistant. +- **type** (*Optional*): "percent", "temperature", "humidity", "illuminance", "brightness", "speed_ms", "current", "power", "electric_current", "electric_potential", "energy", "frequency", "heatflowrate", "phaseanglerad", "phaseangledeg", "powerfactor" or "speed". + +## {% linkable_title Full example %} + ```yaml # Example configuration.yaml entry sensor: @@ -31,8 +49,3 @@ sensor: address: '6/2/1' type: 'temperature' ``` - -- **name** (*Optional*): A name for this device used within Home Assistant. -- **address**: KNX group address of the sensor. -- **type** (Optional): "percent", "temperature", "humidity", "illuminance", "brightness", "speed_ms", "current", "power", "electric_current", "electric_potential", "energy", "frequency", "heatflowrate", "phaseanglerad", "phaseangledeg", "powerfactor" or "speed". - diff --git a/source/_components/sensor.linky.markdown b/source/_components/sensor.linky.markdown new file mode 100644 index 00000000000..a6f60920053 --- /dev/null +++ b/source/_components/sensor.linky.markdown @@ -0,0 +1,41 @@ +--- +layout: page +title: "Linky Sensor" +description: "Instructions on how to integrate Linky daily data within Home Assistant." +date: 2018-09-06 08:35 +sidebar: true +comments: false +sharing: true +footer: true +logo: enedis.png +ha_release: 0.79 +ha_category: Energy +ha_iot_class: "Cloud Polling" +--- + + +The `linky` sensor platform is showing the last day consumption of your home from the [Linky electric meter](https://www.enedis.fr/english). + +## {% linkable_title Configuration %} + +To add the Linky sensor to your installation, add your Enedis account credentials to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + - platform: linky + username: YOUR_LINKY_USERNAME + password: YOUR_LINKY_PASSWORD +``` + +{% configuration %} +username: + description: The Enedis account username. + required: true + type: string +password: + description: The Enedis account password. + required: true + type: string +{% endconfiguration %} + diff --git a/source/_components/sensor.logi_circle.markdown b/source/_components/sensor.logi_circle.markdown new file mode 100644 index 00000000000..aa42c0218c8 --- /dev/null +++ b/source/_components/sensor.logi_circle.markdown @@ -0,0 +1,43 @@ +--- +layout: page +title: "Logi Circle Sensor" +description: "Instructions on how to integrate your Logi Circle cameras within Home Assistant." +date: 2018-09-08 11:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: logi_circle.png +ha_category: Camera +ha_release: 0.79 +ha_iot_class: "Cloud Polling" +--- + +The `logi_circle` sensor platform lets you monitor sensors connected to your [Logi Circle](https://circle.logi.com) cameras in Home Assistant. + +

+You must have the [Logi Circle component](/components/logi_circle/) configured to use this sensor platform. +

+ +## {% linkable_title Configuration %} + +Once you have enabled the [Logi Circle component](/components/logi_circle), add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + - platform: logi_circle +``` + +Configuration variables: + +- **monitored_conditions** array (*Optional*): Conditions to display in the frontend. The following conditions can be monitored. If not specified, all conditions supported by your camera will be enabled. + - **battery_level**: Return the battery level percentage from the camera. + - **last_activity_time**: Return the timestamp from the last time the Logi Circle camera detected any activity. + - **privacy_mode**: Return the privacy mode status from the camera. + - **signal_strength_category**: Return the WiFi signal level from the camera. + - **signal_strength_percentage**: Return the WiFi signal percentage from the camera. + - **speaker_volume**: Return the relative speaker volume from the camera (0-100%). + - **streaming_mode**: Return the streaming mode status from the camera. + +Currently it supports all 1st and 2nd generation cameras. Cameras without an internal battery will not expose a `battery_level` sensor. \ No newline at end of file diff --git a/source/_components/sensor.miflora.markdown b/source/_components/sensor.miflora.markdown index 85ad3cd03b5..0e82f9a6e32 100644 --- a/source/_components/sensor.miflora.markdown +++ b/source/_components/sensor.miflora.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: miflora.png -ha_category: DIY +ha_category: Environment ha_release: 0.29 ha_iot_class: "Local Polling" --- @@ -70,13 +70,10 @@ sensor: - **name** (*Optional*): The name displayed in the frontend. - **force_update** (*Optional*): Sends update events even if the value hasn't changed. - **median** (*Optional*): Sometimes the sensor measurements show spikes. Using this parameter, the poller will report the median of the last 3 (you can also use larger values) measurements. This filters out single spikes. Median: 5 will also filter double spikes. If you never have problems with spikes, `median: 1` will work fine. -- **timeout** (*Optional*): Define the timeout value in seconds when polling (defaults to 10 if not defined) -- **retries** (*Optional*): Define the number of retries when polling (defaults to 2 if not defined) -- **cache_value** (*Optional*): Define cache expiration value in seconds (defaults to 1200 if not defined) - **adapter** (*Optional*): Define the Bluetooth adapter to use (defaults to hci0). Run `hciconfig` to get a list of available adapters.

-By default the sensor is only polled once every 20 minutes. So, if you set `median: 3` it will take _at least_ 40 minutes before the sensor will report a value after a Home Assistant restart. Since the values usually change very slowly, this usually isn't a big problem. Keep in mind though that reducing polling intervals will have a negative effect on the battery life. +By default the sensor is only polled once every 20 minutes (`scan_interval` is 1200 seconds by default). On a Home Assistant restart sensor will report initial value. If you set `median: 3`, it will take _at least_ 40 minutes before the sensor will report an average value. Keep in mind though that reducing polling intervals will have a negative effect on the battery life.

A full configuration example could look like the one below: diff --git a/source/_components/sensor.mold_indicator.markdown b/source/_components/sensor.mold_indicator.markdown index 6b337c6967f..e2d870f7924 100644 --- a/source/_components/sensor.mold_indicator.markdown +++ b/source/_components/sensor.mold_indicator.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: home-assistant.png -ha_category: Climate +ha_category: Environment ha_release: '0.20' ha_iot_class: "Local Polling" --- diff --git a/source/_components/sensor.netatmo_public.markdown b/source/_components/sensor.netatmo_public.markdown index c1c61a1a05c..0f70887c115 100644 --- a/source/_components/sensor.netatmo_public.markdown +++ b/source/_components/sensor.netatmo_public.markdown @@ -13,7 +13,14 @@ ha_iot_class: "Cloud Polling" ha_release: 0.77 --- -The `netatmo_public` sensor allows you to expose data from [Netatmo](https://weathermap.netatmo.com/) to Home Assistant, even if you don't have a Netatmo device yourself. Currently, only live rain data is supported. +The `netatmo_public` sensor allows you to expose data from [Netatmo](https://weathermap.netatmo.com/) to Home Assistant, even if you don't have a Netatmo device yourself. Currently the following conditions are supported: + +* temperature +* pressure +* humidity +* rain +* windstrength +* guststrength To enable the Netatmo sensor, you have to set up [netatmo](/components/netatmo/). @@ -30,6 +37,13 @@ sensor: lon_ne: -73.735 lat_sw: 40.552 lon_sw: -74.105 + monitored_conditions: + - temperature + - pressure + - humidity + - rain + - windstrength + - guststrength ``` {% configuration %} @@ -54,14 +68,18 @@ areas: description: Longitude of south-western corner of area. required: true type: string + monitored_conditions: + description: List of environment conditions to monitor. + required: true + type: list name: description: Name of the sensor. required: false type: string default: Netatmo Public Data - type: + mode: description: "How to calculate the value of the sensor if there are multiple stations reporting data. Accepts `max` or `avg`." required: false type: string - default: max + default: avg {% endconfiguration %} diff --git a/source/_components/sensor.netdata.markdown b/source/_components/sensor.netdata.markdown index 6cf4c3e1d86..0a1a4df622d 100644 --- a/source/_components/sensor.netdata.markdown +++ b/source/_components/sensor.netdata.markdown @@ -51,9 +51,11 @@ To add this platform to your installation, add the following to your `configurat sensor: - platform: netdata resources: - system.load: + load: + data_group: system.load element: load15 - system.cpu: + cpu: + data_group: system.cpu element: system ``` @@ -78,19 +80,19 @@ resources: required: true type: map keys: - data_group: - description: "Name of the data group to monitor, e.g., `system.cpu`." + name: + description: Name to use for the sensor in the frontend. required: true + type: string keys: + data_group: + description: "Name of the data group to monitor, e.g., `system.cpu`." + required: true + type: string element: description: The element of the group to monitor. required: true type: string - name: - description: Name to use for the sensor in the frontend. - required: false - type: string - default: element name icon: description: Icon to use for the sensor. required: false diff --git a/source/_components/sensor.onewire.markdown b/source/_components/sensor.onewire.markdown index d8d9076f8c1..8cd5751d780 100644 --- a/source/_components/sensor.onewire.markdown +++ b/source/_components/sensor.onewire.markdown @@ -27,17 +27,22 @@ Supported devices: The 1-Wire bus can be connected directly to the IO pins of Raspberry Pi or using dedicated interface adapter (e.g [DS9490R](https://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf)). -#### Raspberry Pi setup +## {% linkable_title Raspberry Pi setup %} + In order to setup 1-Wire support on Raspberry Pi, you'll need to edit `/boot/config.txt` following [this documentation](https://www.waveshare.com/wiki/Raspberry_Pi_Tutorial_Series:_1-Wire_DS18B20_Sensor#Enable_1-Wire). Don't use the `mount_dir` option. -#### Interface adapter setup +## {% linkable_title Interface adapter setup %} + +### {% linkable_title owfs %} + When an interface adapter is used, sensors can be accessed on Linux hosts via [owfs 1-Wire file system](http://owfs.org/). When using an interface adapter and the owfs, the `mount_dir` option must be configured to correspond a directory, where owfs device tree has been mounted. -

-This component has been modified to work with devices with multiple sensors which will cause a discontinuity in recorded values. Existing devices will receive a new ID and therefore show up as new devices. +### {% linkable_title Units with multiple sensors %} + +This platform works with devices with multiple sensors which will cause a discontinuity in recorded values. Existing devices will receive a new ID and therefore show up as new devices. If you wish to maintain continuity it can be resolved in the database by renaming the old devices to the new names. -Connect to your database using the instructions from [home-assistant.io/docs/backend/database/](/docs/backend/database/). Check the names of sensors: +Connect to your database using the instructions from [Database section](/docs/backend/database/). Check the names of sensors: ```sql SELECT entity_id, COUNT(*) as count FROM states GROUP BY entity_id ORDER BY count DESC LIMIT 10; @@ -49,10 +54,10 @@ UPDATE states SET entity_id='sensor._temperature' WHERE entity_id L UPDATE states SET entity_id='sensor._pressure' WHERE entity_id LIKE 'sensor.%' AND attributes LIKE '%mb%'; UPDATE states SET entity_id='sensor._humidity' WHERE entity_id LIKE 'sensor.%' AND attributes LIKE '%%%' ESCAPE ''; ``` -Remember to replace `` with the actual name of the sensor as seen in the `SELECT` query. -

-#### Home Assistant setup +Remember to replace `` with the actual name of the sensor as seen in the `SELECT` query. + +## {% linkable_title Configuration %} To enable One wire sensors in your installation, add the following to your `configuration.yaml` file: @@ -64,8 +69,14 @@ sensor: some_id: your name ``` -Configuration variables: - -- **names** array (*Optional*): ID and friendly name of your sensors. -- **mount_dir** (*Optional*): Location of device tree if owfs driver used. +{% configuration %} +names: + description: ID and friendly name of your sensors. + required: false + type: string +mount_dir: + description: Location of device tree if owfs driver used. + required: false + type: string +{% endconfiguration %} diff --git a/source/_components/sensor.pilight.markdown b/source/_components/sensor.pilight.markdown index a78f5a1d391..78e5b61abf4 100644 --- a/source/_components/sensor.pilight.markdown +++ b/source/_components/sensor.pilight.markdown @@ -42,7 +42,7 @@ This section shows a real life example how to use values of a weather station. ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: pilight name: 'Temperature' diff --git a/source/_components/sensor.radarr.markdown b/source/_components/sensor.radarr.markdown index 8795896f9e7..0ec88883e51 100644 --- a/source/_components/sensor.radarr.markdown +++ b/source/_components/sensor.radarr.markdown @@ -50,7 +50,7 @@ In this section you find some real life examples of how to use this sensor. ### {% linkable_title Get Episodes airing in next 2 days %} ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: radarr api_key: YOUR_API_KEY @@ -65,7 +65,7 @@ sensor: SSL may run on a different port than the default (7878). The SSL port can be bound to any port in Radarr, so it should be set in the config here (unless it is changed to 7878). ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: radarr api_key: YOUR_API_KEY @@ -80,7 +80,7 @@ sensor: ### {% linkable_title Get disk space for all storage locations %} ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: radarr api_key: YOUR_API_KEY @@ -94,7 +94,7 @@ sensor: The storage locations Radarr returns are in the system page and in some cases this can list duplicates if sub paths are mounted separately. By listing paths to include, you can choose what data is reported by the sensor. ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: radarr api_key: YOUR_API_KEY @@ -112,7 +112,7 @@ The Radarr API returns available space in bytes, but this sensor will default to *This calculation is done using base 2 math, and may differ from systems calculating using base 10 math.* ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: radarr api_key: YOUR_API_KEY diff --git a/source/_components/sensor.snmp.markdown b/source/_components/sensor.snmp.markdown index f492d5ef3a7..9c78766582b 100644 --- a/source/_components/sensor.snmp.markdown +++ b/source/_components/sensor.snmp.markdown @@ -13,7 +13,6 @@ ha_iot_class: "Local Polling" ha_release: "0.22" --- - The `snmp` sensor platform displays information available through the [Simple Network Management Protocol (SNMP)](https://en.wikipedia.org/wiki/Simple_Network_Management_Protocol). SNMP uses a tree-like hierarchy where each node is an object, and is mainly supported by network-oriented devices such as routers, modems, and printers. To enable this sensor in your installation, add the following to your `configuration.yaml` file: @@ -26,28 +25,107 @@ sensor: baseoid: 1.3.6.1.4.1.2021.10.1.3.1 ``` -Configuration variables: +{% configuration %} +host: + description: The IP address of your host, eg. `192.168.1.32`. + required: true + type: string + default: 'localhost' +baseoid: + description: The OID where the information is located. It's advised to use the numerical notation. + required: true + type: string +port: + description: The SNMP port of your host. + required: Option + type: string + default: '161' +community: + description: "The SNMP community which is set for the device for SNMP v1 and v2c. Most devices have a default community set to `public` with read-only permission (which is sufficient)." + required: false + type: string + default: 'public' +username: + description: Username to use for authentication. + required: false + type: string + default: '' +auth_key: + description: Authentication key to use for SNMP v3. + required: false + type: string + default: no key +auth_protocol: + description: Authentication protocol to use for SNMP v3. + required: false + type: string + default: 'none' +priv_key: + description: Privacy key to use for SNMP v3. + required: false + type: string + default: no key +priv_protocol: + description: Privacy protocol to use for SNMP v3. + required: false + type: string + default: 'none' +version: + description: "Version of SNMP protocol, `1`, `2c` or `3`. Version `2c` or higher is needed to read data from 64-bit counters." + required: false + type: string + default: '1' +name: + description: Name of the SNMP sensor. + required: false + type: string +unit_of_measurement: + description: Defines the unit of measurement of the sensor, if any. + required: false + type: string +value_template: + description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to parse the value." + required: false + type: template +accept_errors: + description: "Determines whether the sensor should start and keep working even if the SNMP host is unreachable or not responding. This allows the sensor to be initialized properly even if, for example, your printer is not on when you start Home Assistant." + required: false + type: string + default: false +default_value: + description: "Determines what value the sensor should take if `accept_errors` is set and the host is unreachable or not responding. If not set, the sensor will have value `unknown` in case of errors." + required: false + type: string +{% endconfiguration %} -- **host** (*Required*): The IP address of your host, eg. `192.168.1.32`. -- **baseoid** (*Required*): The OID where the information is located. It's advised to use the numerical notation. -- **port** (*Option*): The SNMP port of your host. Defaults to `161`. -- **community** (*Optional*): The SNMP community which is set for the device. Most devices have a default community set to `public` with read-only permission (which is sufficient). -- **version** (*Optional*) version of SNMP protocol, `1` or `2c`. Defaults to `1`. Version `2c` is needed to read data from 64-bit counters. -- **name** (*Optional*): Name of the SNMP sensor. -- **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any. -- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to parse the value. -- **accept_errors** (*Optional*): Determines whether the sensor should start and keep working even if the SNMP host is unreachable or not responding. This allows the sensor to be initialized properly even if, for example, your printer is not on when you start Home Assistant. Defaults to `false`. -- **default_value** (*Optional*): Determines what value the sensor should take if `accept_errors` is set and the host is unreachable or not responding. If not set, the sensor will have value `unknown` in case of errors. +Valid values for auth_protocol: + +- **none** +- **hmac-md5** +- **hmac-sha** +- **hmac128-sha224** +- **hmac192-sha256** +- **hmac256-sha384** +- **hmac384-sha512** + +Valid values for priv_protocol: + +- **none** +- **des** +- **3des-ede** +- **aes-cfb-128** +- **aes-cfb-192** +- **aes-cfb-256** ## {% linkable_title Finding OIDs %} -OIDs may vary on different systems because they are vendor-specific. Beside the device's manual, the [OID Repository](http://www.oid-info.com/) is a good place to start if you are looking for OIDs. As an example, the following OIDs are for the load of a Linux systems. +OIDs may vary on different systems because they are vendor-specific. Besides the device's manual, the [OID Repository](http://www.oid-info.com/) is a good place to start if you are looking for OIDs. As an example, the following OIDs are for the load of a Linux system. - 1 minute Load: `1.3.6.1.4.1.2021.10.1.3.1` - 5 minute Load: `1.3.6.1.4.1.2021.10.1.3.2` - 15 minute Load: `1.3.6.1.4.1.2021.10.1.3.3` -There is a large amount of tools available to work with SNMP. `snmpwalk` let you easily retrieve the value of a OID. +There is a large amount of tools available to work with SNMP. `snmpwalk` let you easily retrieve the value of an OID. ```bash $ snmpwalk -Os -c public -v 2c 192.168.1.32 1.3.6.1.4.1.2021.10.1.3.1 @@ -58,10 +136,11 @@ laLoad.1 = STRING: 0.19 ### {% linkable_title Printer uptime minutes %} -According to the most common SNMP standard, the uptime of a device is accessible under OID `1.3.6.1.2.1.1.3.0`. The value represented using a format called `TimeTicks`, in units of hundredth of a second. +According to the most common SNMP standard, the uptime of a device is accessible under OID `1.3.6.1.2.1.1.3.0`. The value represented using a format called `TimeTicks`, in units of hundredths of a second. To create a sensor that displays the uptime for your printer in minutes, you can use this configuration: +{% raw %} ```yaml # Example configuration.yaml entry sensor: @@ -71,8 +150,9 @@ sensor: baseoid: 1.3.6.1.2.1.1.3.0 accept_errors: true unit_of_measurement: 'minutes' - value_template: {% raw %}'{{((value | int) / 6000) | int}}'{% endraw %} + value_template: '{{((value | int) / 6000) | int}}' ``` +{% endraw %} The `accept_errors` option will allow the sensor to work even if the printer is not on when Home Assistant is first started: the sensor will just display a `-` instead of a minute count. diff --git a/source/_components/sensor.sonarr.markdown b/source/_components/sensor.sonarr.markdown index 93b070adcee..837dde42b1d 100644 --- a/source/_components/sensor.sonarr.markdown +++ b/source/_components/sensor.sonarr.markdown @@ -53,7 +53,7 @@ In this section you find some real life examples of how to use this sensor. ### {% linkable_title Get Episodes airing in next 2 days %} ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: sonarr api_key: YOUR_API_KEY @@ -68,7 +68,7 @@ sensor: SSL may run on a different port than the default (8989). The SSL port can be bound to any port in Sonarr, so it should be set in the config here (unless it is changed to 8989). See the [Sonarr site](https://github.com/Sonarr/Sonarr/wiki/SSL) for details on SSL in Sonarr. ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: sonarr api_key: YOUR_API_KEY @@ -83,7 +83,7 @@ sensor: ### {% linkable_title Get disk space for all storage locations %} ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: sonarr api_key: YOUR_API_KEY @@ -97,7 +97,7 @@ sensor: The storage locations Sonarr returns are in the system page and in some cases this can list duplicates if sub paths are mounted separately. By listing paths to include, you can choose what data is reported by the sensor. ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: sonarr api_key: YOUR_API_KEY @@ -115,7 +115,7 @@ The Sonarr API returns available space in bytes, but this sensor will default to *This calculation is done using base 2 math, and may differ from systems calculating using base 10 math.* ```yaml -# Example configuration.yml entry +# Example configuration.yaml entry sensor: - platform: sonarr api_key: YOUR_API_KEY diff --git a/source/_components/sensor.sql.markdown b/source/_components/sensor.sql.markdown index 201861f2620..248b3caa8c0 100644 --- a/source/_components/sensor.sql.markdown +++ b/source/_components/sensor.sql.markdown @@ -132,9 +132,9 @@ SELECT * FROM states WHERE entity_id='binary_sensor.xyz789' GROUP BY state ORDER ```yaml sensor: - platform: sql + db_url: mysql://user:password@localhost/hass queries: - name: DB size - db_url: mysql://user:password@localhost/hass query: 'SELECT table_schema "database", Round(Sum(data_length + index_length) / 1024, 1) "value" FROM information_schema.tables WHERE table_schema="hass" GROUP BY table_schema;' column: 'value' unit_of_measurement: kB diff --git a/source/_components/sensor.starlingbank.markdown b/source/_components/sensor.starlingbank.markdown new file mode 100644 index 00000000000..e997e0da2a3 --- /dev/null +++ b/source/_components/sensor.starlingbank.markdown @@ -0,0 +1,80 @@ +--- +layout: page +title: "Starling Bank" +description: "How to integrate your Starling Bank account within Home Assistant." +date: 2018-09-07 08:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: starlingbank.png +ha_category: Finance +featured: false +ha_release: "0.79" +ha_iot_class: "Cloud Polling" +--- + +The Starling Bank sensor platform allows you to monitor your account balance data as sensors in Home Assistant. + +* Turn off the lights when money's tight? +* Play a song when you reach a savings goal? +* Sound an alarm if you go into your overdraft? + +You can find more information about Starling Bank at [their website](https://www.starlingbank.com/). Information on their API can be found on their [developers site](https://developer.starlingbank.com/). + +## {% linkable_title Access Token %} + +Once you have your own Starling bank account you will need to sign up for a Staring developer account [here](https://developer.starlingbank.com/signup). You won't need to do any development but you will need to get a "Personal Access Token" that will allow the integration to access your account balance. + +

+ You control what access is granted using this token. This integration only needs very basic access (see below). +

+ +Once you've signed up: +1. Head to the [Personal Access Section](https://developer.starlingbank.com/personal/token) of your developer account. +2. Click "Create Token". +3. Give your token a name e.g. "Home Assistant". +4. Tick the permissions "account:read" and "balance:read". The others you can leave un-ticked. +5. Click "Create" and make a note of the newly created token, you will need this for your Home Assistant configuration. + +## {% linkable_title Configuration %} + +To add Starling account balance sensors to your installation, add the following to your `configuration.yaml` file: +```yaml +# Example configuration.yaml entry +sensor: + - platform: starlingbank + accounts: + - access_token: YOUR_PERSONAL_ACCESS_TOKEN +``` + +{% configuration %} +accounts: + description: A list of Starling accounts. Allows you to monitor multiple Starling accounts. + required: true + type: list +name: + description: A friendly name for your account. + required: false + type: string + default: Starling +sandbox: + description: For test purposes. Set to true if you are using an access token for a sandbox Starling account. + required: false + default: false + type: boolean +access_token: + description: Your personal access token. + required: true + type: string +balance_types: + description: Choose to monitor your cleared or effective balance (or both). + required: false + type: list + default: Both balance types will be monitored. + keys: + cleared_balance: + description: Excludes outstanding transactions. + effective_balance: + description: Includes outstanding transactions. +{% endconfiguration %} diff --git a/source/_components/sensor.statistics.markdown b/source/_components/sensor.statistics.markdown index a169c2cc71d..d28f73eabee 100644 --- a/source/_components/sensor.statistics.markdown +++ b/source/_components/sensor.statistics.markdown @@ -14,7 +14,7 @@ ha_release: "0.30" --- -The `statistics` sensor platform consumes the state from other sensors. Besides the maximum and the minimum values, the total, mean, median, variance and the standard deviation are also available as attributes. If it's a binary sensor then only state changes are counted. +The `statistics` sensor platform consumes the state from other sensors. It exports the `mean` value as state and the following values as attributes: `count`, `mean`, `median`, `stdev`, `variance`, `total`, `min`, `max`, `min_age`, `max_age`, `change`, `average_change` and `change_rate`. If it's a binary sensor then only state changes are counted. If you are running the [recorder](/components/recorder/) component, on startup the data is read from the database. So after a restart of the platform, you will immediately have data available. If you're using the [history](/components/history/) component, this will automatically also start the `recorder` component on startup. If you are *not* running the `recorder` component, it can take time till the sensor starts to work because a couple of attributes need more than one value to do the calculation. @@ -43,6 +43,7 @@ Configuration variables: - **name** (*Optional*): Name of the sensor to use in the frontend. Defaults to `Stats`. - **sampling_size** (*Optional*): Size of the sampling. If the limit is reached then the values are rotated. Defaults to `20`. - **max_age** (*Optional*): Maximum age of measurements. Setting this to a time interval will cause older values to be discarded. +- **precision** (*Optional*): Defines the precision of the calculated values, through the argument of round(). Defaults to `2`.

diff --git a/source/_components/sensor.swiss_hydrological_data.markdown b/source/_components/sensor.swiss_hydrological_data.markdown index 44f4d6100bd..c6110b8f7c5 100644 --- a/source/_components/sensor.swiss_hydrological_data.markdown +++ b/source/_components/sensor.swiss_hydrological_data.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: swiss-hydrological-data.png -ha_category: Weather +ha_category: Environment ha_iot_class: "Cloud Polling" ha_release: 0.22 --- @@ -19,33 +19,49 @@ ha_release: 0.22 The `swiss_hydrological_data` sensor will show you details (temperature, level, and discharge) of rivers and lakes in Switzerland. +## {% linkable_title Setup %} + The [station overview](http://www.hydrodaten.admin.ch/en/danger-levels-table.html) contains a list of all available measuring points and will help to determine the ID of station which is needed for the configuration. +## {% linkable_title Configuration %} + To enable this sensor, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry sensor: - platform: swiss_hydrological_data - station: STATION_ID + - platform: swiss_hydrological_data + station: STATION_ID ``` -Configuration variables: - -- **name** (*Optional*): Name to use in the frontend. -- **station** (*Required*): The ID of the measurement point. +{% configuration %} +station: + description: The ID of the measurement point. + required: true + type: string +name: + description: Name to use in the frontend. + required: false + type: string + default: +{% endconfiguration %} The hydrological measurings are coming from the [Swiss Federal Office for the Environment (Bundesamt für Umwelt - Abt. Hydrologie)](http://www.hydrodaten.admin.ch) and are updated almost in real-time. +## {% linkable_title Example %} + This sensor contains additional information which an easily accessed by a [template sensor](/components/sensor.template/). +{% raw %} ```yaml # Example configuration.yaml entry sensor: platform: template sensors: discharge: - value_template: '{% raw %}{{ states.sensor.aare.attributes.Discharge }}{% endraw %}' + value_template: '{{ states.sensor.aare.attributes.Discharge }}' friendly_name: 'Discharge' ``` +{% endraw %} + diff --git a/source/_components/sensor.syncthru.markdown b/source/_components/sensor.syncthru.markdown index 19b2e5d1399..f2238dda257 100644 --- a/source/_components/sensor.syncthru.markdown +++ b/source/_components/sensor.syncthru.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: samsung.png -ha_category: Sensor +ha_category: System Monitor ha_iot_class: "Local Polling" ha_release: 0.66 --- diff --git a/source/_components/sensor.template.markdown b/source/_components/sensor.template.markdown index 7d612f01607..e22d329efb0 100644 --- a/source/_components/sensor.template.markdown +++ b/source/_components/sensor.template.markdown @@ -54,7 +54,7 @@ sensor: required: false type: string, list unit_of_measurement: - description: Defines the units of measurement of the sensor, if any. + description: "Defines the units of measurement of the sensor, if any. This will also influence the graphical presentation in the history visualisation as continuous value. Sensors with missing `unit_of_measurement` are showing as discrete values." required: false type: string value_template: diff --git a/source/_components/sensor.tradfri.markdown b/source/_components/sensor.tradfri.markdown index 98d673d16a6..91827191509 100644 --- a/source/_components/sensor.tradfri.markdown +++ b/source/_components/sensor.tradfri.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "IKEA Trådfri sensor" +title: "IKEA Trådfri Sensor" description: "Access and control your ZigBee-based IKEA Trådfri (Tradfri) Sensors." date: 2017-04-12 22.04 sidebar: true diff --git a/source/_components/sensor.trafikverket_weatherstation.markdown b/source/_components/sensor.trafikverket_weatherstation.markdown index 152d95316ac..d6635769511 100644 --- a/source/_components/sensor.trafikverket_weatherstation.markdown +++ b/source/_components/sensor.trafikverket_weatherstation.markdown @@ -28,7 +28,7 @@ To enable this sensor, add the following lines to your `configuration.yaml`. ```yaml sensor: - platform: trafikverket_weatherstation - name: Trafikverket Road WeatherStation Kungälv + name: Trafikverket Kungälv api_key: eXXcbXXXacXXXXc39XX3aXXX4aXX46XX station: Kungälv monitored_conditions: @@ -92,7 +92,7 @@ Click [here](https://www.trafikverket.se/trafikinformation/vag/?TrafficType=pers ```yaml sensor: - platform: trafikverket_weatherstation - name: Trafikverket Road WeatherStation Kungälv + name: Trafikverket Kungälv api_key: eXXcbXXXacXXXXc39XX3aXXX4aXX46XX station: Kungälv monitored_conditions: @@ -104,16 +104,15 @@ sensor: - wind_direction_text - wind_speed - platform: trafikverket_weatherstation - name: Trafikverket Air WeatherStation Lanna + name: Trafikverket Lanna api_key: eXXcbXXXacXXXXc39XX3aXXX4aXX46XX station: Lanna monitored_conditions: - air_temp - road_temp - humidity - scan_interval: 600 - platform: trafikverket_weatherstation - name: Trafikverket Precipitation WeatherStation Nöbbele + name: Trafikverket Nöbbele api_key: eXXcbXXXacXXXXc39XX3aXXX4aXX46XX station: Nöbbele monitored_conditions: @@ -121,5 +120,4 @@ sensor: - road_temp - humidity - precipitation - scan_interval: 600 ``` diff --git a/source/_components/sensor.twitch.markdown b/source/_components/sensor.twitch.markdown index d1265c1b1d5..660488a7675 100644 --- a/source/_components/sensor.twitch.markdown +++ b/source/_components/sensor.twitch.markdown @@ -16,6 +16,10 @@ ha_iot_class: "Cloud Polling" The `twitch` platform will allow you to monitor [Twitch](http://www.twitch.tv/) channel status from within Home Assistant and setup automation based on the information. +## {% linkable_title Setup %} + +Create a new app at "Register Your Application" in the [Twitch developer portal](https://glass.twitch.tv/console/apps). Then get the **Client ID** for the new app. + ## {% linkable_title Configuration %} To use Twitch with your installation, add the following to your `configuration.yaml` file: @@ -24,12 +28,17 @@ To use Twitch with your installation, add the following to your `configuration.y # Example configuration.yaml entry sensor: platform: twitch + client_id: YOUR_TWITCH_CLIENT_ID channels: - channel1 - channel2 ``` {% configuration %} +clientid: + description: Your Twitch client ID. + required: true + type: string channels: description: List of channels. required: true diff --git a/source/_components/sensor.upnp.markdown b/source/_components/sensor.upnp.markdown index c9d31bcca21..027d76d9ede 100644 --- a/source/_components/sensor.upnp.markdown +++ b/source/_components/sensor.upnp.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: upnp.png -ha_category: "Other" +ha_category: Network ha_release: 0.48 ha_iot_class: "Local Polling" --- diff --git a/source/_components/sensor.velbus.markdown b/source/_components/sensor.velbus.markdown index 7ec537b6e57..56233e50c8a 100644 --- a/source/_components/sensor.velbus.markdown +++ b/source/_components/sensor.velbus.markdown @@ -13,6 +13,6 @@ ha_iot_class: "Local Push" ha_release: 0.78 --- -The `velbus` sensor allows you to control [Velbus](http://www.velbus.eu) connected temperature sensors. +The `velbus` sensor allows you to control [Velbus](http://www.velbus.eu) connected sensors. For hub configuration, see [the Velbus component](/components/velbus/). diff --git a/source/_components/sensor.wunderground.markdown b/source/_components/sensor.wunderground.markdown index d82062c5ffa..0ce56092b59 100644 --- a/source/_components/sensor.wunderground.markdown +++ b/source/_components/sensor.wunderground.markdown @@ -16,7 +16,9 @@ ha_iot_class: "Cloud Polling" The `wunderground` platform uses [Weather Underground](http://www.wunderground.com) as a source for current weather information.

-Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). They no longer offer free API keys, and all keys must be paid for, at this time existing free keys will continue to work, but may be disabled in the future. +Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). They no longer offer free API keys, and all keys must be paid for. At this time existing free keys will continue to work, but will be disabled Dec 31, 2018. As of Sept 6, 2018 Weather Underground states they are declaring the [End of Service for the Weather Underground API](https://apicommunity.wunderground.com/weatherapi/topics/end-of-service-for-the-weather-underground-api). They say they will develop new plans for non-commercial users. No timeline for this has been announced. + +Please consider this when using the following information.

To add Wunderground to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.acer_projector.markdown b/source/_components/switch.acer_projector.markdown index 70e1ae5499f..7599cd6d96e 100644 --- a/source/_components/switch.acer_projector.markdown +++ b/source/_components/switch.acer_projector.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: acer.png -ha_category: Switch +ha_category: Multimedia ha_iot_class: "Local Polling" ha_release: 0.19 --- @@ -16,6 +16,8 @@ ha_release: 0.19 The `acer_projector` switch platform allows you to control the state of RS232 connected projectors from [Acer](http://www.acer.com). +## {% linkable_title Configuration %} + To use your Acer Projector in your installation, add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/switch.digitalloggers.markdown b/source/_components/switch.digitalloggers.markdown old mode 100755 new mode 100644 diff --git a/source/_components/switch.edp_redy.markdown b/source/_components/switch.edp_redy.markdown new file mode 100644 index 00000000000..9f8e7984164 --- /dev/null +++ b/source/_components/switch.edp_redy.markdown @@ -0,0 +1,18 @@ +--- +layout: page +title: "EDP re:dy Switch" +description: "Instructions on how to integrate the EDP re:dy switches into Home Assistant." +date: 2018-09-04 16:30 +sidebar: true +comments: false +sharing: true +footer: true +logo: edp_redy.png +ha_category: Switch +ha_release: "0.79" +ha_iot_class: "Cloud Polling" +--- + +See the [EDP re:dy main component](/components/edp_redy/) for configuration instructions. + +This switch platform will provide a switch per toggleable EDP re:dy device (switch, plug, etc). diff --git a/source/_components/switch.knx.markdown b/source/_components/switch.knx.markdown index dbddf761518..92c04b6e4c2 100644 --- a/source/_components/switch.knx.markdown +++ b/source/_components/switch.knx.markdown @@ -18,6 +18,8 @@ The `knx` switch component is used as in interface to switching actuators. The `knx` component must be configured correctly, see [KNX Component](/components/knx). +## {% linkable_title Configuration %} + To use your KNX switch in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -26,12 +28,13 @@ switch: name: Kitchen.Coffee address: '1/1/6' ``` + +Configuration variables: + +* **address** (*Required*): KNX group address for switching the switch on/off. * **name** (*Optional*): A name for this device used within Home Assistant. -* **address**: KNX group address for switching the switch on/off -* **state_address**: (*Optional*) separate KNX group address for retrieving the switch state. +* **state_address** (*Optional*): separate KNX group address for retrieving the switch state. Some KNX devices can change their state internally without any messages on the KNX bus, e.g., if you configure a timer on a channel. The optional `state_address` can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object. For switching actuators that are only controlled by a single group address and can't change their state internally, you don't have to configure the state address. - - diff --git a/source/_components/switch.mystrom.markdown b/source/_components/switch.mystrom.markdown index 924087adcdd..8d2f93dc439 100644 --- a/source/_components/switch.mystrom.markdown +++ b/source/_components/switch.mystrom.markdown @@ -16,6 +16,17 @@ ha_iot_class: "Local Polling" The `mystrom` switch platform allows you to control the state of your [myStrom](https://mystrom.ch/en/) switches. The built-in sensor is measuring the power consumption while the switch is on. +## {% linkable_title Setup %} + +Make sure that you have enabled the REST API under **Advanced** in the web frontend of the switch. + +

+ +

+ + +## {% linkable_title Configuration %} + To use your myStrom switch in your installation, add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/switch.snmp.markdown b/source/_components/switch.snmp.markdown index 59d9b239044..0d2cb6fd0fa 100644 --- a/source/_components/switch.snmp.markdown +++ b/source/_components/switch.snmp.markdown @@ -15,7 +15,7 @@ ha_release: 0.57 The `snmp` switch platform allows you to control SNMP-enabled equipment. -Currently, only SNMP OIDs that accept integer values are supported. SNMP v1 and v2c are supported. SNMP v3 is **not** supported. +Currently, only SNMP OIDs that accept integer values are supported. SNMP v1, v2c and v3 are supported. To use an SNMP switch in your installation: @@ -27,30 +27,123 @@ switch: baseoid: 1.3.6.1.4.1.19865.1.2.1.4.0 ``` -Configuration variables: - -- **baseoid** (*Required*): The SNMP BaseOID which to poll for the state of the switch. -- **command_oid** (*Optional*): The SNMP OID which to set in order to turn the switch on and off, if different from `baseoid`. -- **host** (*Optional*): The IP/host which to control. Defaults to `localhost`. -- **port** (*Optional*): The port on which to communicate. Defaults to `161`. -- **community** (*Optional*): community string to use for authentication. Defaults to `private`. -- **version** (*Optional*): SNMP version to use - either `1` or `2c`. Defaults to `1`. -- **payload_on** (*Optional*): What return value represents an `On` state for the switch. The same value is used in writes to turn on the switch if `command_payload_on` is not set. Defaults to `1`. -- **payload_off** (*Optional*): What return value represents an `Off` state for the switch. The same value is used in writes to turn off the switch if `command_payload_off` is not set. Defaults to `0`. -- **command_payload_on** (*Optional*): The value to write to turn on the switch, if different from `payload_on`. -- **command_payload_off** (*Optional*): The value to write to turn off the switch, if different from `payload_off`. +{% configuration %} +baseoid: + description: The SNMP BaseOID which to poll for the state of the switch. + required: true + type: string +command_oid: + description: The SNMP OID which to set in order to turn the switch on and off, if different from `baseoid`. + required: false + type: string +host: + description: The IP/host which to control. + required: false + type: string + default: 'localhost' +port: + description: The port on which to communicate. + required: false + type: string + default: '161' +community: + description: community string to use for authentication (SNMP v1 and v2c). + required: false + type: string + default: 'private' +username: + description: Username to use for authentication. + required: false + type: string + default: '' +auth_key: + description: Authentication key to use for SNMP v3. + required: false + type: string + default: no key +auth_protocol: + description: Authentication protocol to use for SNMP v3. + required: false + type: string + default: 'none' +priv_key: + description: Privacy key to use for SNMP v3. + required: false + type: string + default: no key +priv_protocol: + description: Privacy protocol to use for SNMP v3. + required: false + type: string + default: 'none' +version: + description: SNMP version to use - either `1`, `2c` or `3`. + required: false + type: string + default: '1' +payload_on: + description: What return value represents an `On` state for the switch. The same value is used in writes to turn on the switch if `command_payload_on` is not set. + required: false + type: string + default: '1' +payload_off: + description: What return value represents an `Off` state for the switch. The same value is used in writes to turn off the switch if `command_payload_off` is not set. + required: false + type: string + default: '0' +command_payload_on: + description: The value to write to turn on the switch, if different from `payload_on`. + required: false + type: string +command_payload_off: + description: The value to write to turn off the switch, if different from `payload_off`. + required: false + type: string +{% endconfiguration %} You should check with your device's vendor to find out the correct BaseOID and what values turn the switch on and off. -A complete example: +Valid values for auth_protocol: + +- **none** +- **hmac-md5** +- **hmac-sha** +- **hmac128-sha224** +- **hmac192-sha256** +- **hmac256-sha384** +- **hmac384-sha512** + +Valid values for priv_protocol: + +- **none** +- **des** +- **3des-ede** +- **aes-cfb-128** +- **aes-cfb-192** +- **aes-cfb-256** + +Complete examples: ```yaml switch: - platform: snmp - name: SNMP switch + name: SNMP v1 switch host: 192.168.0.2 community: private baseoid: 1.3.6.1.4.1.19865.1.2.1.4.0 payload_on: 1 payload_off: 0 + + - platform: snmp + name: SNMP v3 switch + host: 192.168.0.3 + version: '3' + username: 'myusername' + auth_key: 'myauthkey' + auth_protocol: 'hmac-sha' + priv_key: 'myprivkey' + priv_protocol: 'aes-cfb-128' + baseoid: 1.3.6.1.4.1.19865.1.2.1.4.0 + payload_on: 1 + payload_off: 0 ``` diff --git a/source/_components/switch.switchbot.markdown b/source/_components/switch.switchbot.markdown new file mode 100644 index 00000000000..ff7e8911b50 --- /dev/null +++ b/source/_components/switch.switchbot.markdown @@ -0,0 +1,35 @@ +--- +layout: page +title: "Switchbot" +description: "Instructions on how to set up Switchbot switches." +date: 2018-09-03 22:41 +sidebar: true +comments: false +sharing: true +footer: true +logo: switchbot.png +ha_category: Switch +ha_release: 0.78 +ha_iot_class: "Local Polling" +--- + +This `Switchbot` switch platform allow you to control Switchbot [devices]( https://www.switch-bot.com/). + +To enable it, add the following lines to your `configuration.yaml`: + +```yaml +switch: + - platform: switchbot + mac: 'cb:25:0b......' +``` + +{% configuration %} +mac: + description: Device MAC address. + required: true + type: string +name: + description: The name used to display the switch in the frontend. + required: false + type: string +{% endconfiguration %} diff --git a/source/_components/switch.switchmate.markdown b/source/_components/switch.switchmate.markdown new file mode 100644 index 00000000000..bfc26d496c9 --- /dev/null +++ b/source/_components/switch.switchmate.markdown @@ -0,0 +1,43 @@ +--- +layout: page +title: "Switchmate" +description: "Instructions on how to set up Switchmate switches." +date: 2018-08-17 22:41 +sidebar: true +comments: false +sharing: true +footer: true +logo: switchmate-logo-rgb.png +ha_category: Switch +ha_release: 0.78 +ha_iot_class: "Local Polling" +--- + +This `Switchmate` switch platform allows you to control Switchmate [devices]( https://www.mysimplysmarthome.com/products/switchmate-switches/). + +To enable it, add the following lines to your `configuration.yaml`: + +```yaml +switch: + - platform: switchmate + mac: 'cb:25:0b......' +``` + +{% configuration %} +mac: + description: Device MAC address. + required: true + type: string +name: + description: The name used to display the switch in the frontend. + required: false + type: string +flip_on_off: + description: Option to flip the on/off state. + required: false + type: boolean + default: false +{% endconfiguration %} + + +The component is tested with SwitchMate Lighting Control Rocker and SwitchMate Lighting Control Toggle. diff --git a/source/_components/switch.upcloud.markdown b/source/_components/switch.upcloud.markdown index 98f45d0e68d..bdd03f6af5e 100644 --- a/source/_components/switch.upcloud.markdown +++ b/source/_components/switch.upcloud.markdown @@ -8,13 +8,15 @@ comments: false sharing: true footer: true logo: upcloud.png -ha_category: Switch +ha_category: System Monitor ha_release: 0.65 ha_iot_class: Cloud Polling --- The `upcloud` switch platform allows you to control (start/stop) your UpCloud servers. +## {% linkable_title Configuration %} + To use your UpCloud servers, you first have to set up your [UpCloud hub](/components/upcloud/) and then add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/switch.wake_on_lan.markdown b/source/_components/switch.wake_on_lan.markdown index 161cfcd1b50..c487c602dac 100644 --- a/source/_components/switch.wake_on_lan.markdown +++ b/source/_components/switch.wake_on_lan.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: ethernet.png -ha_category: Switch +ha_category: Network ha_release: 0.16 ha_iot_class: "Local Polling" --- diff --git a/source/_components/tradfri.markdown b/source/_components/tradfri.markdown index 5eb66113cba..8c16a9a17e2 100644 --- a/source/_components/tradfri.markdown +++ b/source/_components/tradfri.markdown @@ -55,7 +55,7 @@ After updating the firmware of your Trådfri gateway it might be necessary to re Please make sure you have `autoconf` installed (`$ sudo apt-get install autoconf`) if you want to use this component. Also, installing some dependencies might take considerable time (>1 h) on slow devices. -### {% linkable_title Seeting the `api_key` %} +### {% linkable_title Setting the `api_key` %} Do not use the `api_key` variable in `configuration.yaml`. The API key is only needed once at initial setup and will be stored. diff --git a/source/_components/tts.google.markdown b/source/_components/tts.google.markdown index 3056b50d94e..75160c41c21 100644 --- a/source/_components/tts.google.markdown +++ b/source/_components/tts.google.markdown @@ -25,7 +25,7 @@ tts: Configuration variables: - **language** (*Optional*): The language to use. Defaults to `en`. - - [Complete list of supported languages](https://cloud.google.com/speech-to-text/docs/languages). + - [Complete list of supported languages (Languages where "Talk" feature is enabled in Google Translate)](https://translate.google.com/intl/en_ALL/about/languages/), use 2 digit language code which you can find at the end of url when you click on Language name. A full configuration sample: diff --git a/source/_components/tts.markdown b/source/_components/tts.markdown index 5fc0d8de47b..0b333959348 100644 --- a/source/_components/tts.markdown +++ b/source/_components/tts.markdown @@ -10,11 +10,11 @@ footer: true ha_release: 0.35 --- -Text-to-speech (TTS) enables Home Assistant to speak to you. +Text-to-Speech (TTS) enables Home Assistant to speak to you. ## {% linkable_title Configuring a `tts` platform %} -To get started, add the following lines to your `configuration.yaml` (example for google): +To get started, add the following lines to your `configuration.yaml` (example for Google): ```yaml # Example configuration.yaml entry for google tts service @@ -23,28 +23,66 @@ tts: ```

-Depending on your setup, you might need to set a base URL (`base_url`) inside the [http component](/components/http/). +Depending on your setup, you might need to set a base URL (`base_url`) inside the [http component](/components/http/) or in the parameters of this component.

The following optional parameters can be used with any platform. However, the TTS component will only look for global settings under the configuration of the first configured platform: -| Parameter | Default | Description | -|---------------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `cache` | True | Allow TTS to cache voice file to local storage. | -| `cache_dir` | tts | Folder name or path to a folder for caching files. | -| `time_memory` | 300 | Time to hold the voice data inside memory for fast play on a media player. Minimum is 60 s and the maximum 57600 s (16 hours). | +{% configuration %} +cache: + description: Allow TTS to cache voice file to local storage. + required: false + type: boolean + default: True +cache_dir: + description: Folder name or path to a folder for caching files. + required: false + type: string + default: tts +time_memory: + description: Time to hold the voice data inside memory for fast play on a media player. Minimum is 60 s and the maximum 57600 s (16 hours). + required: false + type: int + default: 300 +base_url: + description: A base URL to use *instead* of the one set in the [http component](/components/http/). It is used as-is by the `tts` component. In particular, you need to include the protocol scheme `http://` or `https://` and the correct port number. They will not be automatically added for you. + required: false + type: string + default: value of ``http.base_url`` +{% endconfiguration %} The extended example from above would look like the following sample: ```yaml -# Example configuration.yaml entry for google tts service +# Example configuration.yaml entry for Google TTS service tts: - platform: google cache: true cache_dir: /tmp/tts time_memory: 300 + base_url: http://192.168.0.10:8123 ``` +## {% linkable_title When do you need to set `base_url` here? %} + +The general answer is "whenever the global `base_url` set in [http component](/components/http/) is not adequate to allow the `say` service to run". The `say` service operates by generating a media file that contains the speech corresponding to the text passed to the service. Then the `say` service sends a message to the media device with a URL pointing to the file. The device fetches the media file at the URL and plays the media. Some combinations of a media device, network configuration and Home Assistant configuration can make it so that the device cannot fetch the media file. + +The following sections describe some of the problems encountered with media devices. + +### {% linkable_title Self-signed certificates %} + +This problem occurs when your Home Assistant instance is configured to be accessed through SSL, and you are using a self-signed certificate. + +The `tts` service will send an `https://` URL to the media device, which will check the certificate, and reject it. So it won't play your file. If you could make the device accept your certificate, it would play the file. However, many media devices do not allow changing settings to accept self-signed certificates. Ultimately, your option may be to serve files to the device as `http://` rather than `https://`. To do this, you *could* change the `base_url` setting in [http component](/components/http/), but that would turn off SSL for all services that use `base_url`. Instead, setting a `base_url` for the `tts` service allows turning off SSL only for this component. + +### {% linkable_title Google cast devices %} + +The Google cast devices (Google Home, Chromecast, etc.) present the following problems: + +* They [reject self-signed certificates](#self-signed-certificates). + +* They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). Setting a `base_url` that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname. + ## {% linkable_title Service say %} The `say` service support `language` and on some platforms also `options` for set, i.e., *voice, motion, speed, etc*. The text for speech is set with `message`. diff --git a/source/_components/upcloud.markdown b/source/_components/upcloud.markdown index dcb15e41fc4..abd6d945431 100644 --- a/source/_components/upcloud.markdown +++ b/source/_components/upcloud.markdown @@ -7,7 +7,7 @@ sidebar: true comments: false sharing: true footer: true -ha_category: Hub +ha_category: System Monitor ha_release: 0.65 logo: upcloud.png ha_iot_class: Cloud Polling @@ -16,8 +16,12 @@ ha_iot_class: Cloud Polling The `upcloud` component allows you to access the information about your [UpCloud](https://www.upcloud.com/) servers from Home Assistant. +## {% linkable_title Setup %} + Set up your API user credentials in your [UpCloud control panel](https://my.upcloud.com/). +## {% linkable_title Configuration %} + To integrate your UpCloud servers with Home Assistant, add the following section to your `configuration.yaml` file: ```yaml diff --git a/source/_components/upnp.markdown b/source/_components/upnp.markdown index 842e3b25ba4..02ba10a72fd 100644 --- a/source/_components/upnp.markdown +++ b/source/_components/upnp.markdown @@ -8,13 +8,13 @@ comments: false sharing: true footer: true logo: upnp.png -ha_category: "Other" +ha_category: Network ha_release: 0.18 --- The `upnp` component enables you to collect network statistics from your router such as bytes in/out and packets in/out. This information is provided by the Internet Gateway Device (IGD) Protocol if enabled on your router. -The IGD automatically creates port forwarding mappings on your router for Home Assistant, exposing your installation to the internet. The mapping will never automatically expire. Upon stopping Home Assistant, the mapping will be removed from your router. +The IGD automatically creates port forwarding mappings on your router for Home Assistant, exposing your installation to the internet. The mapping will never automatically expire. Upon stopping Home Assistant, the mapping will be removed from your router. Please note that UPnP or NAT-PMP needs to be enabled on your router for this component to work. diff --git a/source/_components/vacuum.markdown b/source/_components/vacuum.markdown index 3df2abbca45..5448d3d85f1 100644 --- a/source/_components/vacuum.markdown +++ b/source/_components/vacuum.markdown @@ -29,7 +29,7 @@ Before calling one of these services, make sure your vacuum platform supports it #### {% linkable_title Service `vacuum.turn_on` %} -Start a new cleaning task. +Start a new cleaning task. For the Xiaomi Vacuum and neato use `vacuum.start` instead. | Service data attribute | Optional | Description | |---------------------------|----------|-------------------------------------------------------| @@ -37,7 +37,7 @@ Start a new cleaning task. #### {% linkable_title Service `vacuum.turn_off` %} -Stop the current cleaning task and return to the dock. +Stop the current cleaning task and return to the dock. For the Xiaomi Vacuum and neato use `vacuum.stop` instead. | Service data attribute | Optional | Description | |---------------------------|----------|-------------------------------------------------------| @@ -106,7 +106,7 @@ Set the fan speed of the vacuum. The `fanspeed` can be a label, as `balanced` or | Service data attribute | Optional | Description | |---------------------------|----------|-------------------------------------------------------| | `entity_id` | yes | Only act on specific vacuum. Else targets all. | -| `fanspeed` | no | Platform dependent vacuum cleaner fan speed, with speed steps, like 'medium', or by percentage, between 0 and 100. | +| `fan_speed` | no | Platform dependent vacuum cleaner fan speed, with speed steps, like 'medium', or by percentage, between 0 and 100. | #### {% linkable_title Service `vacuum.send_command` %} diff --git a/source/_components/vacuum.neato.markdown b/source/_components/vacuum.neato.markdown index 51cf2cc1d81..bbdd37730b1 100644 --- a/source/_components/vacuum.neato.markdown +++ b/source/_components/vacuum.neato.markdown @@ -17,9 +17,13 @@ redirect_from: /components/sensor.neato/ The `neato` vacuum platform allows you to control your [Neato Botvac Connected](https://www.neatorobotics.com/robot-vacuum/botvac-connected-series/). The status will contain attributes on the robots last clean session. +

+If you notice the robot stops responding to commands check the status attribute to see if the robot is offline. If you see "Robot Offline" check the Neato app and make sure your robot is connected and working. If it is not then follow the steps in the app to reset your robot and give it the same name as before then restart Home Assistant. +

+ To add `neato` vacuum to your installation, please follow instructions in [Neato component](/components/neato/). -Currently supported features are: +Currently supported services are: - `start` - `pause` diff --git a/source/_components/vacuum.xiaomi_miio.markdown b/source/_components/vacuum.xiaomi_miio.markdown index 3adcbc43c45..cc93a36c8ab 100644 --- a/source/_components/vacuum.xiaomi_miio.markdown +++ b/source/_components/vacuum.xiaomi_miio.markdown @@ -15,7 +15,7 @@ ha_iot_class: "Local Polling" The `xiaomi miio` vacuum platform allows you to control the state of your [Xiaomi Mi Robot Vacuum](http://www.mi.com/roomrobot/). -Currently supported features are: +Currently supported services are: - `start` - `pause` @@ -48,7 +48,7 @@ Configuration variables: ## {% linkable_title Platform Services %} -In addition to all of the services provided by the `vacuum` component (`start`, `pause`, `stop`, `return_to_home`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are: +In addition to all of the services provided by the `vacuum` component (`start`, `pause`, `stop`, `return_to_base`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are: - `xiaomi_remote_control_start` - `xiaomi_remote_control_stop` diff --git a/source/_components/velbus.markdown b/source/_components/velbus.markdown index 329258ee28a..c5cb790ee99 100644 --- a/source/_components/velbus.markdown +++ b/source/_components/velbus.markdown @@ -13,21 +13,27 @@ ha_iot_class: "Local Push" ha_release: "0.50" --- -The `velbus` component supports the Velbus USB and serial gateways. +The `velbus` component supports the Velbus USB, Velbus serial and a TCP/IP gateway. ## {% linkable_title Configuration %} The gateway needs to be configured by adding the following lines to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yaml entry for a USB or serial interface velbus: port: '/dev/ttyUSB00' ``` +```yaml +# Example configuration.yaml entry for a TCP/IP interface +velbus: + port: '127.0.0.1:3678' +``` + {% configuration %} port: - description: The port where your board is connected to your Home Assistant host. The port will be most likely named `ttyUSB*`. + description: The port where your board is connected to your Home Assistant host. required: true type: string {% endconfiguration %} diff --git a/source/_components/wake_on_lan.markdown b/source/_components/wake_on_lan.markdown index 2f7b1d4532d..87603ad2338 100644 --- a/source/_components/wake_on_lan.markdown +++ b/source/_components/wake_on_lan.markdown @@ -8,13 +8,15 @@ comments: false sharing: true footer: true logo: ethernet.png -ha_category: Utility +ha_category: Network ha_release: "0.49" ha_iot_class: "Local Push" --- The `wake_on_lan` component enables the ability to send _magic packets_ to [Wake on LAN](https://en.wikipedia.org/wiki/Wake-on-LAN) capable devices, to turn them on. +## {% linkable_title Configuration %} + To use this component in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -34,3 +36,13 @@ Send a _magic packet_ to wake up a device with 'Wake-On-LAN' capabilities. |---------------------------|----------|-------------------------------------------------------| | `mac` | no | MAC address of the device to wake up. | | `broadcast_address` | yes | Optional broadcast IP where to send the magic packet. | + + +Sample service data: + +```json +{ + "mac":"00:40:13:ed:f1:32" +} +``` + diff --git a/source/_components/weather.darksky.markdown b/source/_components/weather.darksky.markdown index 6a3b1ad138f..96ef461a9ed 100644 --- a/source/_components/weather.darksky.markdown +++ b/source/_components/weather.darksky.markdown @@ -58,11 +58,15 @@ name: required: false type: string default: Open Sky +mode: + description: "The forecast type. Can be `hourly` or `daily`." + required: false + type: string + default: hourly {% endconfiguration %}

-This platform is an alternative to the [`darksky`](/components/sensor.darksky/) -sensor. +This platform is an alternative to the [`darksky`](/components/sensor.darksky/) sensor.

Details about the API are available in the [Dark Sky documentation](https://darksky.net/dev/docs). diff --git a/source/_components/weather.met.markdown b/source/_components/weather.met.markdown new file mode 100644 index 00000000000..1c31f4a0357 --- /dev/null +++ b/source/_components/weather.met.markdown @@ -0,0 +1,44 @@ +--- +layout: page +title: "Met.no" +description: "Instructions on how to integrate Met.no within Home Assistant." +date: 2018-09-17 09:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: metno.png +ha_category: Weather +ha_release: 0.79 +ha_iot_class: "Cloud Polling" +--- + +The `met` platform uses the [Met.no](https://met.no/) web service as a source for meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK. + +## {% linkable_title Configuration %} + +To add Met to your installation, add the following to your `configuration.yaml` file: + +```yaml +weather: + - platform: met +``` + + +{% configuration %} +latitude: + description: Manually specify latitude. By default the value will be taken from the Home Assistant configuration. + required: false + type: number + default: Provided by Home Assistant configuration +longitude: + description: Manually specify longitude. By default the value will be taken from the Home Assistant configuration. + required: false + type: number + default: Provided by Home Assistant configuration +altitude: + description: Manually specify altitude. By default the value will be taken from the Home Assistant configuration. + required: false + type: number + default: Provided by Home Assistant configuration +{% endconfiguration %} diff --git a/source/_components/wink.markdown b/source/_components/wink.markdown index cf62b8d380e..0d97c91d465 100644 --- a/source/_components/wink.markdown +++ b/source/_components/wink.markdown @@ -141,6 +141,7 @@ The Wink hub, by default, can only be accessed via the cloud. This means it requ - GoControl siren and strobe - Dome siren/chime/strobe +- Quirky Nimbus (Legacy device) These can no longer be officialy added to your Wink account ### {% linkable_title Service `set_siren_auto_shutoff` %} @@ -286,3 +287,55 @@ script: data: enabled: False ``` + +### {% linkable_title Service `set_nimbus_dial_state` %} + +You can use the service wink/set_nimbus_dial_state to update an individual dial's value/position and it's labels + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | no | String or list of strings that point at `entity_id`s of chime/chime. +| `value` | no | A number, should be between the dials min and max value (See set_nimbus_dial_configuration below) +| `labels` | yes | A list of strings the first being the value set on the dial's face and the second being the value on the dial face when the Nimbus is pressed + +Example: + +```yaml +script: + set_dial_1_value: + sequence: + - service: wink.set_nimbus_dial_state + data: + entity_id: wink.nimbus_dial_1 + value: 150 + labels: + - "Dial 1" + - "150" +``` + +### {% linkable_title Service `set_nimbus_dial_configuration` %} + +You can use the service wink/set_nimbus_dial_configuration to update an individual dial's configuration. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | no | String or list of strings that point at `entity_id`s of chime/chime. +| `rotation` | yes | One of "cw" or "ccw" the direction the dial hand should rotate. +| `ticks` | yes | A positive number, the number of times the hand should move. +| `scale` | yes | One of "linear" or "log" How the dial should move in response to higher values. +| `min_value` | yes | A number, the minimum value that the dial can have. +| `max_value` | yes | A number, the maximum value that the dial can have. +| `min_position` | yes | A number generally [0-360], the minimum position for the dial's hand. +| `max_value` | yes | A number generally [0-360], the maximum position for the dial's hand. + +Example: + +```yaml +script: + set_dial_1_value: + sequence: + - service: wink.set_nimbus_dial_state + data: + entity_id: wink.nimbus_dial_1 + rotation: 'ccw' +``` diff --git a/source/_components/zeroconf.markdown b/source/_components/zeroconf.markdown index 3d054ea4d59..d1459fdd1b1 100644 --- a/source/_components/zeroconf.markdown +++ b/source/_components/zeroconf.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: avahi.png -ha_category: "Other" +ha_category: Network ha_release: 0.18 --- diff --git a/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown b/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown index 65f5cb6b590..27320af7a8f 100644 --- a/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown +++ b/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown @@ -36,3 +36,40 @@ automation: service: homeassistant.turn_off entity_id: light.kitchen_light ``` + +Or in the case of multiple sensors/triggers: + +```yaml +automation: +- alias: Turn on hallway lights when the doorbell rings, the front door opens or if there is movement + trigger: + - platform: state + entity_id: sensor.motion_sensor, binary_sensor.front_door, binary_sensor.doorbell + to: 'on' + action: + - service: homeassistant.turn_on + data: + entity_id: + - light.hallway_0 + - light.hallway_1 + - service: timer.start + data: + entity_id: timer.hallway + +- alias: Turn off hallway lights 10 minutes after trigger + trigger: + platform: event + event_type: timer.finished + event_data: + entity_id: timer.hallway + action: + service: homeassistant.turn_off + data: + entity_id: + - light.hallway_0 + - light.hallway_1 + +timer: + hallway: + duration: '00:10:00' +``` diff --git a/source/_docs/asterisk_mbox.markdown b/source/_docs/asterisk_mbox.markdown index 438ed0fd422..45bc4071a80 100644 --- a/source/_docs/asterisk_mbox.markdown +++ b/source/_docs/asterisk_mbox.markdown @@ -56,6 +56,8 @@ Before beginning make sure that you have the following: mbox_path = PATH_TO_VOICEMAIL_FILES cache_file = PATH_TO_CACHE_FILE google_key = GOOGLE_API_KEY + cdr = mysql+pymysql://:@localhost/asterisk/cdr + ``` - **host** (*Optional*): The IP address to listen on for client requests. This defaults to all IP addresses on the server. To listen only locally, choose `127.0.0.1` @@ -64,6 +66,7 @@ Before beginning make sure that you have the following: - **mbox\_path** (*Required*): The path to the storage location of mailbox files. This is typically `/var/spool/asterisk/voicemail/default//` - **cache\_file** (*Required*): A fully-qualified path to a file thht can be written by the server containing transcriptions of voicemails. Example: `/var/spool/asterisk/transcription.cache` - **google\_key** (*Required*): Your 40 characters Google API key. + - **cdr** (*Optional*): Where to find CDR data. Supports various SQL databases as well as a file log. Configuring the CDR will enable the `asterisk_cdr` platfom. Once complete, ensure this file is only accessible by the Asterisk user: diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown index 7bae172053b..f2e984cf30a 100644 --- a/source/_docs/authentication.markdown +++ b/source/_docs/authentication.markdown @@ -40,6 +40,24 @@ As a user, you can setup multi-factor authentication with time-based one-time pa ## {% linkable_title Troubleshooting %} +### {% linkable_title Bearer token warnings %} + +Under the new authentication system you'll see the following warning logged when the [legacy API password](/docs/authentication/providers/#legacy-api-password) is supplied, but not configured in Home Assistant: + +```txt +WARNING (MainThread) [homeassistant.components.http.auth] You need to use a bearer token to access /blah/blah from 192.0.2.4 +``` + +If you see this, you need to add an [`api_password`](/components/http/#api_password) to your `http:` configuration. + +### {% linkable_title Bearer token informational messages %} + +If instead, you see the following, then this is a message for component developers, to tell them that they need to update how they authenticate to Home Assistant. As an end user you don't need to do anything: + +```txt +INFO (MainThread) [homeassistant.components.http.auth] You need to use a bearer token to access /blah/blah from 192.0.2.4 +``` + ### {% linkable_title Lost owner password %} While you should hopefully be storing your passwords in a password manager, if you lose the password associated with the owner account the only way to resolve this is to delete *all* the authentication data. You do this by shutting down Home Assistant and deleting the following files from the `.storage/` folder in your [configuration folder](https://www.home-assistant.io/docs/configuration/): @@ -49,3 +67,29 @@ While you should hopefully be storing your passwords in a password manager, if y * `onboarding` When you start Home Assistant next you'll be required to set up authentication again. + +### {% linkable_title Error: invalid client id or redirect url%} + +Screenshot of Error: invalid client id or redirect url + +You have to use a domain name, not IP address to remote access Home Assistant; otherwise you will get **Error: invalid client id or redirect url** error on the login form. However, you can use the IP address to access Home Assistant in your home network. + +It because we only allow using IP address as client ID when your IP address is one of internal network address (e.g., 192.168.0.1) or loopback address (e.g., 127.0.0.1). + +If you don't have a valid domain name for your Home Assistant instance, you can modify the `hosts` file on your computer to fake one. For example, if you are on Windows, edit `C:\Windows\System32\Drivers\etc\hosts` file with administrator privilege, add following entry. + +```text +12.34.56.78 hassbian.home +``` + +(Please replace `12.34.56.78` with your Home Assistant's public IP address) + +It will allow you to open Home Assistant instance by access `http://hassbian.home:8123/` + +### {% linkable_title Stuck on Loading data %} + +Some advert blocking software, such as Wipr, also blocks web sockets. If you're stuck on the Loading data screen, try disabling your ad blocker. + +### {% linkable_title Migrating from pre 0.77 %} + +If you were using the authentication system before 0.77, you'll likely have `auth:` and `auth_providers:` defined. You'll need to remove these and let Home Assistant [handle it automatically](https://www.home-assistant.io/docs/authentication/providers/#configuring-auth-providers). diff --git a/source/_docs/authentication/multi-factor-auth.markdown b/source/_docs/authentication/multi-factor-auth.markdown index 90d51fe8f78..19fc53d8d98 100644 --- a/source/_docs/authentication/multi-factor-auth.markdown +++ b/source/_docs/authentication/multi-factor-auth.markdown @@ -42,7 +42,7 @@ Below is a list of the currently available auth providers. [Time-based One-Time Password](https://en.wikipedia.org/wiki/Time-based_One-time_Password_algorithm) is widely adopted in modern authencation system, it combines a secret key with the current timestamp using a cryptographic hash function to generate a one-time password. Whoever possessed the secret key will get same one-time password in certain time period. By verifying that password, Home Assistant knows the user have the right secrt key. -When trying to set up TOTP module, a QR code will show up. The user can scan it by an authenticator app, or set it up manually using the code showed in the UI. After setup, the user needs to input a six digit number generated in the autendicator app to verify the setup is good. If the verification keeps failing, you need to check whether the clock on Home Assistant is accurate. +When trying to set up TOTP module, a QR code will show up. The user can scan it by an authenticator app, or set it up manually using the code showed in the UI. After setup, the user needs to input a six digit number generated in the authenticator app to verify the setup is good. If the verification keeps failing, you need to check whether the clock on Home Assistant is accurate. There are several authenticator apps on the market, we recommend either [Google Authenticator](https://support.google.com/accounts/answer/1066447) or [Authy](https://authy.com/). @@ -52,6 +52,8 @@ Please treat the secret key like a password, never expose it to others. By default, one TOTP multi-factor named "Authenticator app" will be auto loaded if no `auth_mfa_modules` configuration section defined in the `configuration.yaml` file. +By default one TOTP multi-factor auth module named "Authenticator app" will be auto loaded if no `auth_mfa_modules` config section defined in `configuration.yaml`. + Example of configuration: ```yaml @@ -59,3 +61,39 @@ homeassistant: auth_mfa_modules: - type: totp ``` + +### {% linkable_title Notify mutli-factor authentication module %} + +Notify MFA module using [notify component](https://www.home-assistant.io/components/notify/) to delivery a [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm) to user configured target. + +User need first set up the MFA module by select one of the aviliable notify service. A 8 digit one-time password will be sent by this notify service, user need to input it to verify the setup. + +During the login process, an 8 digit one-time password will be sent again, user need to input it to verify his/her identity. If the validation failed, a new one-time password will be sent again. + +

+Notify MFA module would not verify the one-time password deliveried success, so that if user cannot received the message due any reason, he/she may not be login again. Edit or remove `[your_config_dir]/.storage/auth_module.notify` can disable nofiy MFA module to resolve the issue. +

+ +Example of configuration + +```yaml +homeassistant: + auth_mfa_modules: + - type: notify +``` + +Optional configuration variables: + +- **exclude** (*Optional*): The list of notify services you do not want to include in. +- **include** (*Optional*): The list of notify services you want to include in. +- **message** (*Optional*): The message template + +```yaml +# Example configure with message template +homeassistant: + auth_mfa_modules: + - type: totp + name: Authenticator app + - type: notify + message: 'I almost forget, to get into my clubhouse, you need to say {}' +``` diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown index b672beb0967..8da14db4aaa 100644 --- a/source/_docs/authentication/providers.markdown +++ b/source/_docs/authentication/providers.markdown @@ -27,7 +27,11 @@ To make the transition from API password to authentication system easier, we've ## {% linkable_title Configuring auth providers %}

-By configuring your own instead of using the default configuration, you take full responsibility for the authentication of the system. +Home Assistant automatically configures the standard auth providers and you **do not** need to specify `auth_providers` in your `configuration.yaml` file. Specifying `auth_providers` in your configuration will disable all auth providers that are not listed and can reduce your security or create difficulties logging in. +

+ +

+[Issue 16441](https://github.com/home-assistant/home-assistant/issues/16441): the legacy API password auth provider won't be automatically configured if your API password is located in a package. This is because Home Assistant processes the `auth_provider` during the `core` section loading, which is earlier than the `packages` processing.

Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block: diff --git a/source/_docs/automation.markdown b/source/_docs/automation.markdown index e50db5d9bfe..6729aa4fcb4 100644 --- a/source/_docs/automation.markdown +++ b/source/_docs/automation.markdown @@ -47,6 +47,8 @@ State changes can be used as the source of triggers and the current state can be Actions are all about calling services. To explore the available services open the Services developer tool. Services allow to change anything. For example turn on a light, run a script or enable a scene. Each service has a domain and a name. For example the service `light.turn_on` is capable of turning on any light in your system. Services can be passed parameters to for example tell which device to turn on or what color to use. +### {% linkable_title Automation initial state %} + You have to set an initial state in your automations in order for Home Assistant to enable them upon restart. ```text diff --git a/source/_docs/autostart/systemd.markdown b/source/_docs/autostart/systemd.markdown index 17211e5ed9d..6b43b19c2e1 100644 --- a/source/_docs/autostart/systemd.markdown +++ b/source/_docs/autostart/systemd.markdown @@ -78,7 +78,7 @@ ExecStopPost=/usr/bin/docker rm -f home-assistant-%i WantedBy=multi-user.target ``` -### Next Steps +### {% linkable_title Next Steps %} You need to reload `systemd` to make the daemon aware of the new configuration. diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown index 150eef1b46f..fb4193f7265 100644 --- a/source/_docs/configuration.markdown +++ b/source/_docs/configuration.markdown @@ -2,14 +2,14 @@ layout: page title: "Configuring Home Assistant" description: "Configuring Home Assistant." -date: 2015-03-23 12:50 +date: 2018-09-08 16:15 sidebar: true comments: false sharing: true footer: true --- -When launched for the first time, Home Assistant will write a default configuration file enabling the web interface and device discovery. It can take up to a minute for your devices to be discovered and appear in the user interface. +When launched for the first time, Home Assistant will create a default configuration file enabling the web interface and device discovery. It can take up to a minute after startup for your devices to be discovered and appear in the user interface. The web interface can be found at `http://ip.ad.dre.ss:8123/` - for example if your Home Assistant system has the IP address `192.168.0.40` then you'll find the web interface as `http://192.168.0.40:8123/`. @@ -26,13 +26,20 @@ If you want to use a different folder for configuration, use the config command Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains components to be loaded with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable functionality. -

- You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect. You can load changes to [automations](/docs/automation/), [customize](/docs/configuration/customizing-devices/), [groups](/components/group/), and [scripts](/components/script/) without restarting. -

- If you run into trouble while configuring Home Assistant, have a look at the [configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [configuration.yaml examples](/cookbook/#example-configurationyaml).

Test any changes to your configuration files from the command line with `hass --script check_config`. This script allows you to test changes without the need to restart Home Assistant. Remember to run this as the user you run Home Assistant as.

+## {% linkable_title Reloading changes %} + +You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect. You can load changes to [automations](/docs/automation/), [customize](/docs/configuration/customizing-devices/), [groups](/components/group/), and [scripts](/components/script/) without restarting if you're not using [packages](/docs/configuration/packages/). + +

+If you've made any changes, remember to [check your configuration](https://www.home-assistant.io/docs/configuration/troubleshooting/#problems-with-the-configuration) before trying to reload or restart. +

+ +## {% linkable_title Migrating to a new system %} + +If you want to migrate your configuration to a new system then you can copy the contents of your configuration folder from the current system to the new system. Be aware that some of the files you need start with `.`, which is hidden by default from both `ls` (in SSH), in Windows Explorer, and macOS Finder. You'll need to ensure that you're viewing all files before you copy them. diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index a3dc6cc91a3..8de3aa169e0 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -10,8 +10,86 @@ footer: true redirect_from: /getting-started/customizing-devices/ --- +## {% linkable_title Changing the entity_id %} + +You can use the UI to change the `entity_id` and friendly name of supported entities. To do this: + +1. Select the entity, either from or from the frontend, or by clicking next to the entity in the dev-states menu +2. Click on the cog in the right corner of the entity's dialog +3. Enter the new name or the new entity ID (remember not to change the domain of the entity - the part before the `.`) +4. Select *Save* + +## {% linkable_title Customizing entities %} + By default, all of your devices will be visible and have a default icon determined by their domain. You can customize the look and feel of your front page by altering some of these parameters. This can be done by overriding attributes of specific entities. +### {% linkable_title Customization using the UI %} + +Under the *Configuration* menu you'll find the *Customization* menu. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those, or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)). + +#### {% linkable_title Possible values %} + +{% configuration customize %} +friendly_name: + description: Name of the entity as displayed in the UI. + required: false + type: string +homebridge_name: + description: Name of the entity in `HomeBridge`. + required: false + type: string +hidden: + description: Set to `true` to hide the entity. + required: false + type: boolean + default: False +homebridge_hidden: + description: Set to `true` to hide the entity from `HomeBridge`. + required: false + type: boolean + default: False +emulated_hue_hidden: + description: Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/components/emulated_hue)). + required: false + type: boolean + default: False +entity_picture: + description: URL to use as picture for entity. + required: false + type: string +icon: + description: Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://materialdesignicons.com/cheatsheet)). Prefix name with `mdi:`, ie `mdi:home`. + required: false + type: string +assumed_state: + description: For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon. + required: false + type: boolean + default: True +device_class: + description: Sets the class of the device, changing the device state and icon that is displayed on the UI (see below). + required: false + type: boolean +initial_state: + description: Sets the initial state for automations, `on` or `off`. + required: false + type: string +unit_of_measurement: + description: Defines the units of measurement, if any. + required: false + type: string +{% endconfiguration %} + +#### {% linkable_title Device Class %} + +Device class is currently supported by the following components: + +* [Binary Sensor](/components/binary_sensor/) +* [Sensor](/components/sensor/) +* [Cover](/components/cover/) + +### {% linkable_title Manual customization %} +

If you implement `customize`, `customize_domain`, or `customize_glob` you must make sure it is done inside of `homeassistant:` or it will fail.

@@ -53,30 +131,6 @@ homeassistant: homebridge_hidden: true ``` -### {% linkable_title Possible values %} - -| Attribute | Description | -| --------- | ----------- | -| `friendly_name` | Name of the entity. -| `homebridge_name` | Name of the entity in `HomeBridge`. -| `hidden` | Set to `true` to hide the entity. -| `homebridge_hidden` | Set to `true` to hide the entity from `HomeBridge`. -| `emulated_hue_hidden` | Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/components/emulated_hue)). -| `entity_picture` | Url to use as picture for entity. -| `icon` | Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://materialdesignicons.com/cheatsheet)). Prefix name with `mdi:`, ie `mdi:home`. -| `assumed_state` | For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon. -| `device_class` | Sets the class of the device, changing the device state and icon that is displayed on the UI (see below). -| `initial_state` | Sets the initial state for automations. `on` or `off`. -| `unit_of_measurement` | Defines the units of measurement, if any. - -### {% linkable_title Device Class %} - -Device class is currently supported by the following components: - -* [Binary Sensor](/components/binary_sensor/) -* [Sensor](/components/sensor/) -* [Cover](/components/cover/) - ### {% linkable_title Reloading customize %} Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant.reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the service developer tool icon service developer tools, select the service `homeassistant.reload_core_config` and click "CALL SERVICE". @@ -84,4 +138,3 @@ Home Assistant offers a service to reload the core configuration while Home Assi

New customize information will be applied the next time the state of the entity gets updated.

- diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index b8caf5394cb..9bcd0e2822c 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -63,9 +63,8 @@ light: There are some rules for packages that will be merged: -1. Component names may only use the basic form (e.g., `switch`, but not `switch 1` or `switch aa`). -2. Platform based components (`light`, `switch`, etc) can always be merged. -3. Components where entities are identified by a key that will represent the entity_id (`{key: config}`) need to have unique 'keys' between packages and the main configuration file. +1. Platform based components (`light`, `switch`, etc) can always be merged. +2. Components where entities are identified by a key that will represent the entity_id (`{key: config}`) need to have unique 'keys' between packages and the main configuration file. For example if we have the following in the main config. You are not allowed to re-use "my_input" again for `input_boolean` in a package: @@ -73,7 +72,7 @@ There are some rules for packages that will be merged: input_boolean: my_input: ``` -4. Any component that is not a platform [2], or dictionaries with Entity ID keys [3] can only be merged if its keys, except those for lists, are solely defined once. +3. Any component that is not a platform [2], or dictionaries with Entity ID keys [3] can only be merged if its keys, except those for lists, are solely defined once.

Components inside packages can only specify platform entries using configuration style 1, where all the platforms are grouped under the component name. diff --git a/source/_docs/configuration/remote.markdown b/source/_docs/configuration/remote.markdown index f0d981b116e..00f9e276b35 100644 --- a/source/_docs/configuration/remote.markdown +++ b/source/_docs/configuration/remote.markdown @@ -15,6 +15,10 @@ If you're interested in logging in to Home Assistant while away, you'll have to Remember to follow the [securing checklist](/docs/configuration/securing/) before doing this.

+

+Home Assistant no longer support remote access via IP address since release 0.77, you have to use domain name. +

+ The most common approach is to set up port forwarding (for any port) from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching ` port forwarding instructions`. You can use any free port on your router and forward that to port 8123. A problem with making a port accessible is that some Internet Service Providers only offer dynamic IPs. This can cause you to lose access to Home Assistant while away. You can solve this by using a free Dynamic DNS service like [DuckDNS](https://www.duckdns.org/). diff --git a/source/_docs/configuration/securing.markdown b/source/_docs/configuration/securing.markdown index 4ed3e20243e..664acbe217b 100644 --- a/source/_docs/configuration/securing.markdown +++ b/source/_docs/configuration/securing.markdown @@ -14,7 +14,7 @@ One major advantage of Home Assistant is that it's not dependent on cloud servic ### {% linkable_title Checklist %} -- [Protect your web interface with a password](/getting-started/basic/#password-protecting-the-web-interface) +- [Choose a strong password](/docs/authentication/). - Secure your host. Sources could be [Red Hat Enterprise Linux 7 Security Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Security_Guide/Red_Hat_Enterprise_Linux-7-Security_Guide-en-US.pdf), [CIS Red Hat Enterprise Linux 7 Benchmark](https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.0.0.pdf), or the [Securing Debian Manual](https://www.debian.org/doc/manuals/securing-debian-howto/index.en.html). - Restrict network access to your devices. Set `PermitRootLogin no` in your sshd config (usually `/etc/ssh/sshd_config`) and to use SSH keys for authentication instead of passwords. - Don't run Home Assistant as root – consider the Principle of Least Privilege. diff --git a/source/_docs/configuration/troubleshooting.markdown b/source/_docs/configuration/troubleshooting.markdown index 0d867a2622c..f76ca7086a0 100644 --- a/source/_docs/configuration/troubleshooting.markdown +++ b/source/_docs/configuration/troubleshooting.markdown @@ -26,7 +26,7 @@ If you have incorrect entries in your configuration files you can use the [`chec One of the most common problems with Home Assistant is an invalid `configuration.yaml` file. - - You can test your configuration using the command line with: `hass --script check_config` + - You can test your configuration using the command line with: `hass --script check_config`. On Hass.io you can use the [hassio command](https://www.home-assistant.io/hassio/commandline/#home-assistant): `hassio homeassistant check`. - You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/). - To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well). diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown index d8c82f80d42..0b62214a923 100644 --- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown +++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown @@ -14,7 +14,7 @@ If you are using Hass.io or Hassbian, do not use this guide. Instead, use the [D

-Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](/docs/configuration/basic/) page. +Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](/components/http/) page.

diff --git a/source/_docs/installation/hassbian/customization.markdown b/source/_docs/installation/hassbian/customization.markdown index e1c968a0c41..cb52818895b 100644 --- a/source/_docs/installation/hassbian/customization.markdown +++ b/source/_docs/installation/hassbian/customization.markdown @@ -35,7 +35,7 @@ These are some of the available suites: - [AppDaemon](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/appdaemon.md) - [Hassbian](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/hassbian.md) - [Home Assistant](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/homeassistant.md) -- [hassbian-config (hassbian-sctipts)](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/hassbian_config.md) +- [hassbian-config (hassbian-scripts)](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/hassbian_config.md) To upgrade any of them simply run `sudo hassbian-config upgrade SUITE`. diff --git a/source/_docs/installation/hassbian/upgrading.markdown b/source/_docs/installation/hassbian/upgrading.markdown index 1a6b37d4968..c9eb4af4d81 100644 --- a/source/_docs/installation/hassbian/upgrading.markdown +++ b/source/_docs/installation/hassbian/upgrading.markdown @@ -20,7 +20,7 @@ $ sudo apt-get -y upgrade #### {% linkable_title Updating Home Assistant %}

-You can use `hassbian-config` to automate the process by running `sudo hassbian-config upgrade homeassistant` +You can use `hassbian-config` to automate the process by running `sudo hassbian-config upgrade home-assistant`

To update the Home Assistant installation execute the following command as the `pi` user. diff --git a/source/_docs/installation/python.markdown b/source/_docs/installation/python.markdown index a7dda882e25..7f8c01ad421 100644 --- a/source/_docs/installation/python.markdown +++ b/source/_docs/installation/python.markdown @@ -10,6 +10,10 @@ footer: true redirect_from: /getting-started/installation-python/ --- +

+If you're running a Linux-based platform, we strongly recommend you follow the instructions for a [virtual environment](/docs/installation/virtualenv/) instead. If you're running on Windows then [see here](/docs/installation/windows/#installing-in-a-python-virtual-environment) instead. +

+ Once Python is installed, execute the following code in a console: ```bash @@ -22,12 +26,10 @@ Running these commands will: - Install Home Assistant - Launch Home Assistant and serve the web interface on [http://localhost:8123](http://localhost:8123) -If you're running a Linux-based platform, we suggest you follow the instructions for a [virtual environment](/docs/installation/virtualenv/) to avoid using `root`. - Video tutorials of this process for various operating systems are available here: - [Windows 10](https://www.youtube.com/watch?v=X27eVvuqwnY) - [macOS](https://www.youtube.com/watch?v=hej6ipN86ls) - [Ubuntu 14.04](https://www.youtube.com/watch?v=SXaAG1lGNH0) -Keep in mind that the used operating systems and the shown software releases may be outdated. +Keep in mind that the operating systems used and the software releases shown may be outdated. diff --git a/source/_docs/installation/raspberry-pi.markdown b/source/_docs/installation/raspberry-pi.markdown index 2ae0bc857b5..31af033f9d6 100644 --- a/source/_docs/installation/raspberry-pi.markdown +++ b/source/_docs/installation/raspberry-pi.markdown @@ -83,7 +83,7 @@ Once you have installed the required python package it is now time to install Ho (homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ pip3 install homeassistant ``` -Start Home Assistant for the first time. This will complete the installation, create the `.homeassistant` configuration directory in the `/home/homeassistant` directory and install any basic dependencies. +Start Home Assistant for the first time. This will complete the installation for you, automatically creating the `.homeassistant` configuration directory in the `/home/homeassistant` directory, and installing any basic dependencies. ```bash (homeassistant) $ hass @@ -114,4 +114,5 @@ When instructions tell you to activate the virtual environment, the following co ```bash $ sudo -u homeassistant -H -s -$ source /srv/homeassistant/bin/activate``` +$ source /srv/homeassistant/bin/activate +``` diff --git a/source/_docs/installation/virtualenv.markdown b/source/_docs/installation/virtualenv.markdown index 7c56772af73..336ced4598e 100644 --- a/source/_docs/installation/virtualenv.markdown +++ b/source/_docs/installation/virtualenv.markdown @@ -72,7 +72,7 @@ It is recommended to use the [advanced guide](/docs/installation/raspberry-pi/) - It's recommended to run Home Assistant as a dedicated user.

-Looking for more advanced guides? Check our [Rasbian guide](/docs/installation/raspberry-pi/) or the [other installation guides](/docs/installation/). +Looking for more advanced guides? Check our [Raspbian guide](/docs/installation/raspberry-pi/) or the [other installation guides](/docs/installation/).

### {% linkable_title After upgrading Python %} diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index 75a56503e8a..af0f99c2c1e 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -14,15 +14,17 @@ The discovery of MQTT devices will enable one to use MQTT devices with only mini Supported by MQTT discovery: +- [Alarm control panels](/components/alarm_control_panel.mqtt/) - [Binary sensors](/components/binary_sensor.mqtt/) - [Cameras](/components/camera.mqtt/) - [Covers](/components/cover.mqtt/) - [Fans](/components/fan.mqtt/) +- [HVACs](/components/climate.mqtt/) - [Lights](/components/light.mqtt/) +- [Locks](/components/lock.mqtt/) - [Sensors](/components/sensor.mqtt/) - [Switches](/components/switch.mqtt/) - To enable MQTT discovery, add the following to your `configuration.yaml` file: ```yaml @@ -49,6 +51,8 @@ The discovery topic need to follow a specific format: The payload will be checked like an entry in your `configuration.yaml` file if a new device is added. This means that missing variables will be filled with the platform's default values. All configuration variables which are *required* must be present in the initial payload send to `/config`. +An empty payload will cause a previously discovered device to be deleted. + The `` level can be used by clients to only subscribe to their own (command) topics by using one wildcard topic like `/+//+/set`. ### {% linkable_title Support by third-party tools %} @@ -79,6 +83,12 @@ Update the state. $ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/state" -m ON ``` +Delete the sensor by sending an empty message. + + ```bash +$ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/state" -m '' +``` + Setting up a switch is similar but requires a `command_topic` as mentioned in the [MQTT switch documentation](/components/switch.mqtt/). - Configuration topic: `homeassistant/switch/irrigation/config` diff --git a/source/_docs/mqtt/service.markdown b/source/_docs/mqtt/service.markdown index 941d79e7b78..d4a7aad206d 100644 --- a/source/_docs/mqtt/service.markdown +++ b/source/_docs/mqtt/service.markdown @@ -10,7 +10,7 @@ footer: true logo: mqtt.png --- -The MQTT component will register the service `publish` which allows publishing messages to MQTT topics. There are two ways of specifying your payload. You can either use `payload` to hard-code a payload or use `payload_template` to specify a [template](/topics/templating/) that will be rendered to generate the payload. +The MQTT component will register the service `mqtt.publish` which allows publishing messages to MQTT topics. There are two ways of specifying your payload. You can either use `payload` to hard-code a payload or use `payload_template` to specify a [template](/topics/templating/) that will be rendered to generate the payload. ```json { @@ -19,10 +19,20 @@ The MQTT component will register the service `publish` which allows publishing m } ``` +{% raw %} ```json { "topic": "home-assistant/light/1/state", - "payload_template": "{% raw %}{{ states('device_tracker.paulus') }}{% endraw %}" + "payload_template": "{{ states('device_tracker.paulus') }}" } ``` +{% endraw %} +`payload` must be a string. If you want to send JSON then you need to format/escape it properly. Like: + +```json +{ + "topic": "home-assistant/light/1/state", + "payload":"{\"Status\":\"off\", \"Data\":\"something\"}" +} +``` diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index 7534ae05787..9d8b8a218b6 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -67,10 +67,19 @@ Delays are useful for temporarily suspending your script and start it at a later ```yaml # Waits 1 minute - delay: - # supports milliseconds, seconds, minutes, hours, days + # Supports milliseconds, seconds, minutes, hours, days minutes: 1 ``` +{% raw %} +```yaml +# Waits however many seconds input_number.second_delay is set to +- delay: + # Supports milliseconds, seconds, minutes, hours, days + seconds: "{{ states('input_number.second_delay') }}" +``` +{% endraw %} + {% raw %} ```yaml # Waits however many minutes input_number.minute_delay is set to @@ -85,14 +94,14 @@ Wait until some things are complete. We support at the moment `wait_template` fo {% raw %} ```yaml -# wait until media player have stop the playing +# Wait until media player have stop the playing - wait_template: "{{ is_state('media_player.floor', 'stop') }}" ``` {% endraw %} {% raw %} ```yaml -# wait for sensor to trigger or 1 minute before continuing to execute. +# Wait for sensor to trigger or 1 minute before continuing to execute. - wait_template: "{{ is_state('binary_sensor.entrance', 'on') }}" timeout: '00:01:00' continue_on_timeout: 'true' @@ -125,7 +134,7 @@ You can also get the script to abort after the timeout by using `continue_on_tim {% raw %} ```yaml -# wait until a valve is < 10 or continue after 1 minute. +# Wait until a valve is < 10 or continue after 1 minute. - wait_template: "{{ states.climate.kitchen.attributes.valve|int < 10 }}" timeout: '00:01:00' continue_on_timeout: 'false' diff --git a/source/_docs/scripts/editor.markdown b/source/_docs/scripts/editor.markdown index a69ae296923..9ccc8252d42 100644 --- a/source/_docs/scripts/editor.markdown +++ b/source/_docs/scripts/editor.markdown @@ -10,7 +10,7 @@ footer: true redirect_from: /docs/script/editor/ --- -In Home Assistant 0.52 we introduced the first version of our automation editor. If you just created a new configuration with Home Assistant then you're all set! Go to the UI and enjoy. +In Home Assistant 0.52 we introduced the first version of our script editor. If you just created a new configuration with Home Assistant then you're all set! Go to the UI and enjoy.
diff --git a/source/_docs/z-wave.markdown b/source/_docs/z-wave.markdown index 6ee6a284fa1..6df8aca7acf 100644 --- a/source/_docs/z-wave.markdown +++ b/source/_docs/z-wave.markdown @@ -18,7 +18,7 @@ Before configuring the Z-Wave setup, please take a moment and read [this article ## {% linkable_title What is Z-Wave %} -Z-Wave is a wireless communication protocol designed for home automation. It uses a low power, and low bandwidth, mesh network that allows devices that aren't within direct range of each other to communicate indirectly, via other nodes. Any device that's permanently powered (not battery powered) will help build the mesh, if you don't have enough powered devices, or you locate these poorly, your mesh will be unreliable. +Z-Wave is a wireless communication protocol designed for home automation. It uses a low power, and low bandwidth, mesh network that allows devices that aren't within direct range of each other to communicate indirectly, via other nodes. Any device that's permanently powered (not battery powered) will help build the mesh, if you don't have enough powered devices, or you locate these poorly, your mesh will be unreliable. You can [view the state](https://community.home-assistant.io/t/graph-your-z-wave-mesh-python-auto-update/40549) of your mesh [by graphing it](https://community.home-assistant.io/t/z-wave-graph-without-the-python/64275). There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) components. There is also a limit of 4 hops for Z-Wave, so placing the controller as centrally as you can is important. diff --git a/source/_docs/z-wave/adding.markdown b/source/_docs/z-wave/adding.markdown index c52661c0c1c..3bfb7ad66d7 100644 --- a/source/_docs/z-wave/adding.markdown +++ b/source/_docs/z-wave/adding.markdown @@ -32,10 +32,10 @@ Security Z-Wave devices require a network key. Some devices only expose their fu A valid network key will be a 16 byte value, defined in the zwave section of your configuration, such as the following example: -``` +```yaml zwave: - usb_path: /dev/ttyACM0 - network_key: "0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10" + usb_path: /dev/ttyACM0 + network_key: "0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10" ``` Each individual value in the defined key can be anywhere from 0x00 to 0xFF. Define your own key by making changes to the above example key or for additional security try one of the two scripts mentioned below. @@ -43,13 +43,21 @@ Each individual value in the defined key can be anywhere from 0x00 to 0xFF. Defi ### {% linkable_title Network Key %} An easy script to generate a random key: + ```bash -cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' +$ cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' ``` On macOS, this script will generate a random key: + ```bash -cat /dev/urandom | LC_CTYPE=C tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' +$ cat /dev/urandom | LC_CTYPE=C tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' +``` + +If the above command doesn't work then replace `LC_CTYPE=C` with `LC_ALL=C`: + +```bash +$ cat /dev/urandom | LC_ALL=C tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' ```

diff --git a/source/_docs/z-wave/control-panel.markdown b/source/_docs/z-wave/control-panel.markdown index dc3f19c5cc5..8d2493c6e37 100644 --- a/source/_docs/z-wave/control-panel.markdown +++ b/source/_docs/z-wave/control-panel.markdown @@ -41,6 +41,36 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro * **Test Node** sends no_op test messages to the node. This could in theory bring back a dead node. +* **Node Information** this will display the Z-Wave entity card with information about the node: + +* **averageRequestRTT** The average Round Trip Time (RTT) of requests sent to the node, in milliseconds. A value of 250, for example, is a quarter of a second. +* **averageResponseRTT** The average Round Trip Time of responses to requests +* **battery_level** *Battery powered devices only* - the battery level, which may be rounded to the nearest 10 +* **capabilities** A comma separated list of the capabilities of the device +* **friendly_name** The name you specified to be displayed +* **is_awake** Whether the device is awake or not +* **is_failed** Whether the device has been marked as failed. The controller won't try to contact failed devices. +* **is_info_received** True once the controller has received the node information from the node. +* **is_ready** When you start the network (or Home Assistant) it will take a short while before all devices are ready, this shows which aren't yet ready. +* **is_zwave_plus** True for any Z-Wave Plus devices (note that controllers always report *false*, regardless of whether they are Plus devices or not) +* **lastRequestRTT** The Round Trip Time of the last request +* **lastResponseRTT** The Round Trip Time of the response to the last request +* **manufacturer_name** The name of the manufacturer, as supplied by OpenZWave +* **max_baud_rate** The maximum bandwidth the device supports, most modern devices will support 40,000 or higher +* **node_id** The unique node ID of this node +* **node_name** The base name of this node, this is used to build the entity ID of all entities of this node +* **product_name** The product name of the device, as supplied by OpenZWave +* **query_stage** The query stage for this device (see [here](/docs/z-wave/query-stage/) for details) +* **receivedCnt** The number of messages received from the device +* **receivedDups** The number of duplicate messages received from the device +* **receivedTS** The date and time the last message was received from the devices +* **receivedUnsolicited** How many unsolicited messages were received +* **retries** How many retries have been made to send messages to this node +* **sentCnt** How many messages have been sent to the node +* **sentFailed** How many messages that were sent weren't acknowledged +* **sentTS** The date and time the last message was sent to the ndoe +* **wake_up_interval** *Battery powered devices only* - the wakeup interval of the device, in seconds +

Battery powered devices need to be awake before you can use the Z-Wave control panel to update their settings. How to wake your device is device specific, and some devices will stay awake for only a couple of seconds. Please refer to the manual of your device for more details.

@@ -58,38 +88,6 @@ The **Polling intensity** says how many poll intervals does is this device polle You can also exclude a Z-Wave devices from Home Assistant. You can do that if you have a device that you need to have on the Z-Wave network, but you don't want it to appear in Home Assistant, or if you've got a device that's failed and you're unable to exclude it. -### {% linkable_title Node Information %} - -This will display the Z-Wave related information about the node: - -* **averageRequestRTT** The average Round Trip Time (RTT) of requests sent to the node, in milliseconds. A value of 250, for example, is a quarter of a second. -* **averageResponseRTT** The average Round Trip Time of responses to requests -* **battery_level** *Battery powered devices only* - the battery level, which may be rounded to the nearest 10 -* **capabilities** A comma separated list of the capabilities of the device -* **friendly_name** The name you specified to be displayed -* **is_awake** Whether the device is awake or not -* **is_failed** Whether the device has been marked as failed. The controller won't try to contact failed devices. -* **is_info_received** True once the controller has received the node information from the node. -* **is_ready** When you start the network (or Home Assistant) it will take a short while before all devices are ready, this shows which aren't yet ready. -* **is_zwave_plus** True for any Z-Wave Plus devices (note that controllers always report *false*, regardless of whether they are Plus devices or not) -* **lastRequestRTT** The Round Trip Time of the last request -* **lastResponseRTT** The Round Trip Time of the response to the last request -* **manufacturer_name** The name of the manufacturer, as supplied by OpenZWave -* **max_baud_rate** The maximum bandwidth the device supports, most modern devices will support 40,000 or higher -* **node_id** The unique node ID of this node -* **node_name** The base name of this node, this is used to build the entity ID of all entities of this node -* **product_name** The product name of the device, as supplied by OpenZWave -* **query_stage** The query stage for this device (see [here](/docs/z-wave/query-stage/) for details) -* **receivedCnt** The number of messages received from the device -* **receivedDups** The number of duplicate messages received from the device -* **receivedTS** The date and time the last message was received from the devices -* **receivedUnsolicited** How many unsolicited messages were received -* **retries** How many retries have been made to send messages to this node -* **sentCnt** How many messages have been sent to the node -* **sentFailed** How many messages that were sent weren't acknowledged -* **sentTS** The date and time the last message was sent to the ndoe -* **wake_up_interval** *Battery powered devices only* - the wakeup interval of the device, in seconds - ### {% linkable_title Node Values %} Contains a list of available values of the selected node, and it's instances. @@ -116,6 +114,10 @@ That would remove the broadcast group from association group 1 of the device wit You can set the *wakeup* interval (in seconds) of the device, this is shown for all devices that can be battery powered, even if they are currently mains powered. The wakeup interval only applies when those devices are battery powered. +

+The wakeup interval has no impact on the device's ability to report sensor changes. This is purely for how often the Z-Wave chip will check in with the controller. That activity consumes a lot of battery power compared to reporting sensor changes and if you reduce it you'll be reducing the battery life of your device. +

+ Underneath that you can select any supported configuration parameter to see the current setting. You can then change this and select **Set Config Parameter** to updated it. Battery powered devices will be updated the next time they wake. ### {% linkable_title Node protection %} @@ -160,4 +162,5 @@ for c in sys.argv[1]: ## {% linkable_title OZW Log %} If you want to only retrieve some lines at the end of the log, you can specify that with the selection field. Max is the last 1000 lines and minimum is 0 which equals the whole log. If this is not specified, you will retrieve the whole log. -Select **Refresh** to display the log if you need it to check activities. +Select **Load** to open a new window with the static log. +Select **Tail** to open a new window with a tailing log with the last specified lines of the log. This is a self updating window. diff --git a/source/_docs/z-wave/controllers.markdown b/source/_docs/z-wave/controllers.markdown index fdaac560c3c..128b122649b 100644 --- a/source/_docs/z-wave/controllers.markdown +++ b/source/_docs/z-wave/controllers.markdown @@ -24,6 +24,7 @@ You need to have a [supported Z-Wave USB stick or module](https://github.com/Ope | Sigma Designs UZB Stick | | | | | Tricklestar | | | | | Vision USB Stick | | | | +| ZWave.me Razberry Board | ✓ | | | | ZWave.me UZB1 | ✓ | | |

diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index a118d2c97ce..a734e976e51 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -24,7 +24,7 @@ On Linux platforms (other than Hass.io) there is one dependency you will need to $ sudo apt-get install libudev-dev ``` -On Python 3.6 you may also have to install libpython3.6-dev, and possibly python3.6-dev. +On Python 3.6 you may also have to install `libpython3.6-dev`, and possibly `python3.6-dev`. ### {% linkable_title macOS %} @@ -44,6 +44,7 @@ On Raspberry Pi you will need to enable the serial interface in the `raspi-confi # Example configuration.yaml entry zwave: usb_path: /dev/ttyACM0 + device_config: !include zwave_device_config.yaml ``` {% configuration zwave %} @@ -78,7 +79,7 @@ debug: type: boolean default: False device_config / device_config_domain / device_config_glob: - description: This attribute contains node-specific override values. (For releases prior to 0.39 this variable is called **customize**) See [Customizing devices and services](/docs/configuration/customizing-devices/) for the format. + description: "This attribute contains node-specific override values. NOTE: This needs to be specified if you are going to use any of the following options. See [Customizing devices and services](/docs/configuration/customizing-devices/) for the format." required: false type: string, list keys: @@ -160,14 +161,20 @@ $ ls /dev/cu.usbmodem* ### {% linkable_title Hass.io %} -To enable Z-Wave, plug your Z-Wave USB stick into your Raspberry Pi 3 and add the following to your `configuration.yaml`: +To enable Z-Wave, plug your Z-Wave USB stick into your system and add the following to your `configuration.yaml`: ```yaml zwave: usb_path: /dev/ttyACM0 ``` -Depending on your Z-Wave device it may instead be `/dev/ttyAMA0` (eg Razberry board) or `/dev/ttyUSB0` (eg HUBUZB-1). +If the above defaults don't work, you can check what hardware has been found using the [hassio command](/hassio/commandline/#hardware): + +```bash +$ hassio hardware info +``` + +Or you can use the UI and look in the *System* section of the *Hass.io* menu. There you'll find a *Hardware* button which will list all the hardware found. ### {% linkable_title RancherOS %} diff --git a/source/_lovelace/conditional.markdown b/source/_lovelace/conditional.markdown index 4bf17345887..d2f7f881315 100644 --- a/source/_lovelace/conditional.markdown +++ b/source/_lovelace/conditional.markdown @@ -42,6 +42,8 @@ card: *one is required (`state` or `state_not`) +Note: Conditions with more than one entity are treated as an 'and' condition. This means that for the card to show, *all* entities must meet the state requirements set. + ### {% linkable_title Examples %} ```yaml diff --git a/source/_lovelace/picture-entity.markdown b/source/_lovelace/picture-entity.markdown index 39ad6002f19..de390f82299 100644 --- a/source/_lovelace/picture-entity.markdown +++ b/source/_lovelace/picture-entity.markdown @@ -38,6 +38,10 @@ state_image: required: false description: "Map entity states to images (`state: image URL`, check the example below)." type: object +aspect_ratio: + required: false + description: "Forces the height of the image to be a ratio of the width. You may enter a value such as: `16x9`, `16:9`, `1.78`." + type: string name: required: false description: Overwrite entity name. diff --git a/source/_lovelace/picture-glance.markdown b/source/_lovelace/picture-glance.markdown index 62a6c258c82..e4f4162cbf6 100644 --- a/source/_lovelace/picture-glance.markdown +++ b/source/_lovelace/picture-glance.markdown @@ -51,6 +51,10 @@ state_image: type: string required: false description: "`state: image-url`, check the example below." +aspect_ratio: + required: false + description: "Forces the height of the image to be a ratio of the width. You may enter a value such as: `16x9`, `16:9`, `1.78`." + type: string entity: required: false description: Entity to use for `state_image`. diff --git a/source/_lovelace/weather-forecast.markdown b/source/_lovelace/weather-forecast.markdown index b92588bd2c2..c636319db9a 100644 --- a/source/_lovelace/weather-forecast.markdown +++ b/source/_lovelace/weather-forecast.markdown @@ -34,3 +34,9 @@ entity: - type: weather-forecast entity: weather.demo_weather_north ``` + +

+ This card works only with platforms that define a `weather` entity. + + E.g., it works with [Dark Sky](https://www.home-assistant.io/components/weather.darksky/) but not [Dark Sky Sensor](https://www.home-assistant.io/components/sensor.darksky/) +

diff --git a/source/_posts/2018-08-29-release-77.markdown b/source/_posts/2018-08-29-release-77.markdown index 84b3c8906d6..d57d9910198 100644 --- a/source/_posts/2018-08-29-release-77.markdown +++ b/source/_posts/2018-08-29-release-77.markdown @@ -81,6 +81,18 @@ You didn't think we would forget about Lovelace, did you? This release include a [light.lifx docs]: /components/light.lifx/ [wemo docs]: /components/wemo/ +## {% linkable_title Release 0.77.3 - September 3 %} + +Frontend changes only: + +- Ask "save login" after hass connected [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1631) [@awarecan] +- Show an error when invalid client id or redirect uri [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1620) [@balloob] +- Disable autocapitalization of username field [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1627) [@timmo001] +- Upgrade MDI icons [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1630) [@balloob] +- Update translations + +[@timmo001]: https://github.com/timmo001 + ## {% 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/_posts/2018-09-15-release-78.markdown b/source/_posts/2018-09-15-release-78.markdown new file mode 100644 index 00000000000..a8e712f1bc4 --- /dev/null +++ b/source/_posts/2018-09-15-release-78.markdown @@ -0,0 +1,492 @@ +--- +layout: post +title: "0.78: More auth, Switchmate, Yale Smart Alarm, OpenTherm" +description: "We're 5! We got some great new auth stuff in this release and support for Switchmate, Yale Smart Alarm and OpenTherm." +date: 2018-09-17 00:01:00 +date_formatted: "September 17, 2018" +author: Paulus Schoutsen +author_twitter: balloob +comments: true +categories: Release-Notes +og_image: /images/blog/2018-09-release-0.78/components.png +--- + + + +It's time for a new release and oh boy, what a time to be alive! Today marks our 5th (!!!) anniversary. That's 5 years we've been bringing privacy focused and locally controlled home automation to your home. Happy birthday to us. + +This release includes two new features for the auth system. The first one is long-lived access tokens. These are tokens that don't expire and can be used in your scripts instead of API password. Instructions on how to create and use them can be found on your profile. + +Also on your profile page is a new list of existing refresh tokens. These are all the tokens that are currently active for your account. If you ran into issues that the remember login dialog didn't show, you might have a lot. Don't worry, you can delete them all. + +## {% linkable_title New Platforms %} + +- Add temperature sensors to the velbus component ([@Cereal2nd] - [#16203]) ([velbus docs]) ([sensor.velbus docs]) (new-platform) +- Add Volkszaehler sensor ([@fabaff] - [#16188]) ([sensor.volkszaehler docs]) (new-platform) +- Switchmate ([@Danielhiversen] - [#15535]) ([switch.switchmate docs]) (new-platform) +- Add support for Habitica ([@ASMfreaK] - [#15744]) ([habitica docs]) ([sensor.habitica docs]) (new-platform) +- Geo Location component ([@exxamalte] - [#15953]) ([feedreader docs]) ([geo_location docs]) (new-platform) +- Add Cover to the Insteon component ([@teharris1] - [#16215]) ([insteon docs]) ([cover.insteon docs]) (new-platform) +- switchbot ([@Danielhiversen] - [#16396]) ([switch.switchbot docs]) (new-platform) +- Add Yale Smart Alarm component ([@domwillcode] - [#16377]) ([alarm_control_panel.yale_smart_alarm docs]) (new-platform) +- Add OpenTherm Gateway climate platform ([@mvn23] - [#16299]) ([climate.opentherm_gw docs]) (new-platform) + +## {% linkable_title Release 0.78.1 - September 20 %} + +- Updates documentation repo URL in PR template ([@frenck] - [#16537]) +- SnmpSensor: Fix async_update (#16679) ([@mtdcr] - [#16716]) ([sensor.snmp docs]) +- Handle chromecast CONNECTION_STATUS_DISCONNECTED event ([@awarecan] - [#16732]) ([media_player.cast docs]) +- Upgrade netdisco to 2.1.0 ([@awarecan] - [#16735]) + +[#16537]: https://github.com/home-assistant/home-assistant/pull/16537 +[#16716]: https://github.com/home-assistant/home-assistant/pull/16716 +[#16732]: https://github.com/home-assistant/home-assistant/pull/16732 +[#16735]: https://github.com/home-assistant/home-assistant/pull/16735 +[@awarecan]: https://github.com/awarecan +[@frenck]: https://github.com/frenck +[@mtdcr]: https://github.com/mtdcr +[media_player.cast docs]: /components/media_player.cast/ +[sensor.snmp docs]: /components/sensor.snmp/ + +## {% linkable_title Release 0.78.2 - September 21 %} + +- Fix discovery + +## {% linkable_title Release 0.78.3 - September 22 %} + +- Bump gtts-token to 1.1.2 ([@edif30] - [#16775]) ([tts docs]) + +[#16537]: https://github.com/home-assistant/home-assistant/pull/16537 +[#16775]: https://github.com/home-assistant/home-assistant/pull/16775 +[@edif30]: https://github.com/edif30 +[@frenck]: https://github.com/frenck +[tts docs]: /components/tts/ + +## {% 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. + +## {% linkable_title Reporting Issues %} + +Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template. + + + +## {% linkable_title Breaking Changes %} + +- Trafikverket weather: Instead of having multiple sensor configurations per station, add only one configuration per station and select the type of measurement data to subscribe to using monitored_conditions. +The configuration value type should no longer be used. ([@endor-force] - [#15935]) ([sensor.trafikverket_weatherstation docs]) (breaking change) +- Geizhals: config has changed. Remove domain and regex, specify locale instead: `AT`, `EU`, `DE`, `UK` or `PL`. ([@JulianKahnert] - [#15990]) ([sensor.geizhals docs]) (breaking change) +- Update to EnvoyReader 0.2, support for more hardware. Change keys in monitored_conditions from `7_days_production` and `7_days_consumption` to `seven_days_production` and `seven_days_consumption` ([@jesserizzo] - [#16212]) ([sensor.enphase_envoy docs]) (breaking change) +- Fix Mi Flora median calculation. Removed `retries` and `timeout` config parameters, they were not used for several months. Replaced `cache_value` config with `scan_interval` to fix a bug in the PR. ([@PaulAnnekov] - [#16085]) ([sensor.miflora docs]) (breaking change) +- Twitch now requires a `client_id` and so the platform got updated. ([@ioangogo] - [#16428]) ([sensor.twitch docs]) (breaking change) +- The radiotherm `fan` and `mode` state attributes were updated to reflect the real-time fan and mode states of the thermostat, rather than the overall selected state (automatic, mostly). The mode attributes still contain the selected modes (fan on/auto, heat/cool/auto). ([@cpw] - [#15031]) ([climate.radiotherm docs]) (breaking change) + +## {% linkable_title Beta Fixes %} + +- Replace api_password in Camera.Push ([@dgomes] - [#16339]) ([camera.push docs]) (beta fix) +- Fail fetch auth providers if onboarding required ([@balloob] - [#16454]) ([auth docs]) (beta fix) +- Fix insteon Hub v1 support ([@teharris1] - [#16472]) ([insteon docs]) (beta fix) +- bugfix - incorrect camera type and missing sensors when multiple netatmo cameras ([@vikramgorla] - [#16490]) ([netatmo docs]) (beta fix) +- Fix arlo intilization when no base station available ([@zellux] - [#16529]) ([arlo docs]) (beta fix) +- Long-lived access token ([@awarecan] - [#16453]) ([auth docs]) (beta fix) +- Fix typo ([@balloob] - [#16556]) (beta fix) +- Fix invalid state ([@balloob] - [#16558]) (beta fix) +- Add websocket commands for refresh tokens ([@balloob] - [#16559]) ([auth docs]) (beta fix) +- Return if refresh token is current used one in WS API ([@awarecan] - [#16575]) ([auth docs]) ([websocket_api docs]) (beta fix) +- Track refresh token last usage information ([@awarecan] - [#16408]) ([auth docs]) (beta fix) +- Increasing python-websockets' version number ([@zoe1337] - [#16578]) ([media_player.webostv docs]) (beta fix) +- Add retry limit for chromecast connection ([@awarecan] - [#16471]) ([media_player.cast docs]) (beta fix) +- Fix broken bluetooth tracker ([@awarecan] - [#16589]) ([device_tracker docs]) (beta fix) +- Rewrite bluetooth le ([@pvizeli] - [#16592]) ([device_tracker docs]) (beta fix) + +## {% linkable_title All changes %} + +- Add 'moon_phase' to Dark Sky sensor ([@fabaff] - [#16179]) ([sensor.darksky docs]) +- Zoneminder SSL fix ([@djm300] - [#16157]) ([zoneminder docs]) +- update python-velbus library version ([@thomasdelaet] - [#16194]) ([velbus docs]) +- MQTT: Log transmitted as well as received messages ([@smurfix] - [#16195]) ([mqtt docs]) +- Upgrade sqlalchemy to 1.2.11 ([@fabaff] - [#16192]) ([sensor.sql docs]) +- Add battery warning, rssi level and check for availability ([@fucm] - [#16193]) ([sensor.tahoma docs]) +- Inconsistent entity_id when multiple sensors ([@grea09] - [#16205]) ([sensor.dnsip docs]) +- Add temperature sensors to the velbus component ([@Cereal2nd] - [#16203]) ([velbus docs]) ([sensor.velbus docs]) (new-platform) +- Rewrite of Trafikverket weather - Multiple sensor types supported ([@endor-force] - [#15935]) ([sensor.trafikverket_weatherstation docs]) (breaking change) +- Add device_tracker.bluetooth_update service ([@kariudo] - [#15252]) ([device_tracker docs]) +- Fix geizhals price parsing ([@JulianKahnert] - [#15990]) ([sensor.geizhals docs]) (breaking change) +- Add Volkszaehler sensor ([@fabaff] - [#16188]) ([sensor.volkszaehler docs]) (new-platform) +- openalpr flag `WITH_TEST` should be `WITH_TESTS` ([@vrih] - [#16218]) +- Upgrade alpha_vantage to 2.1.0 ([@fabaff] - [#16217]) ([sensor.alpha_vantage docs]) +- Store devices as dict instead of list ([@Kane610] - [#16229]) +- Improve package loadable ([@balloob] - [#16237]) +- Switchmate ([@Danielhiversen] - [#15535]) ([switch.switchmate docs]) (new-platform) +- Add support for discrete states to MyQ cover ([@schmittx] - [#16251]) ([cover.myq docs]) +- bump version ([@dgomes] - [#16262]) ([upnp docs]) +- Replace Authorization by Authentication ([@cgtobi] - [#16259]) ([hangouts docs]) +- Add device info to Chromecast ([@balloob] - [#16261]) ([media_player.cast docs]) +- Add device info for sonos ([@balloob] - [#16263]) ([media_player.sonos docs]) +- Add device info Nest ([@balloob] - [#16265]) ([climate.nest docs]) +- Add Hue device info ([@balloob] - [#16267]) ([hue docs]) ([light.hue docs]) +- Nest Thermostat has software version ([@awarecan] - [#16275]) ([climate.nest docs]) +- Add support for Habitica ([@ASMfreaK] - [#15744]) ([habitica docs]) ([sensor.habitica docs]) (new-platform) +- Fix so that entities are properly unloaded with config entry ([@Kane610] - [#16281]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([scene.deconz docs]) ([sensor.deconz docs]) ([switch.deconz docs]) +- Geo Location component ([@exxamalte] - [#15953]) ([feedreader docs]) ([geo_location docs]) (new-platform) +- Bump songpal dependency ([@rytilahti] - [#16297]) ([media_player.songpal docs]) +- Use asterisk_mbox 0.5.0 client ([@PhracturedBlue] - [#16296]) ([asterisk_mbox docs]) +- Upgrade Adafruit-DHT to 1.3.4 ([@thomaslian] - [#16327]) ([sensor.dht docs]) +- Add unique ID ([@schmittx] - [#16323]) ([cover.myq docs]) +- Add Cover to the Insteon component ([@teharris1] - [#16215]) ([insteon docs]) ([cover.insteon docs]) (new-platform) +- Fix missing humidity sensor ([@danielperna84] - [#16337]) ([homematic docs]) +- Support Sonos Beam HDMI input ([@phil65] - [#16340]) ([media_player.sonos docs]) +- Make last_seen attribute a timezone aware datetime in UTC ([@pnbruckner] - [#16348]) ([device_tracker docs]) +- Handle netatmo exception ([@Danielhiversen] - [#16344]) ([sensor.netatmo docs]) +- Add support for sound_mode for Yamaha rxv media_player ([@Joshi425] - [#16352]) ([media_player.yamaha docs]) +- Add unique_id to MQTT Light ([@bieniu] - [#16303]) ([light.mqtt docs]) +- Update to EnvoyReader 0.2, support for more hardware ([@jesserizzo] - [#16212]) ([sensor.enphase_envoy docs]) (breaking change) +- Snips: Added special slot values, session_id and slotname_raw ([@tschmidty69] - [#16185]) ([snips docs]) +- Upgrade hbmqtt to 0.9.4 ([@awarecan] - [#16356]) ([mqtt docs]) +- Upgrade Sphinx to 1.7.7 ([@fabaff] - [#16359]) +- Upgrade qnapstats to 0.2.7 ([@fabaff] - [#16360]) ([sensor.qnap docs]) +- Upgrade mutagen to 1.41.1 ([@fabaff] - [#16361]) ([tts docs]) +- Upgrade shodan to 1.10.0 ([@fabaff] - [#16363]) ([sensor.shodan docs]) +- Upgrade to youtube_dl to 2018.09.01 ([@fabaff] - [#16365]) ([media_extractor docs]) +- Added 'nomapnt', 'outcurnt', 'loadapnt' fields ([@MarcSN311] - [#16176]) ([sensor.apcupsd docs]) +- Generic Thermostat: add support for climate.turn_on/climate.turn_off ([@aronsky] - [#16080]) ([climate.generic_thermostat docs]) +- Add support for Tahoma Lighting Receiver on/off io ([@fucm] - [#15925]) ([tahoma docs]) ([switch.tahoma docs]) +- Update discord.py ([@htotoo] - [#16248]) ([notify docs]) +- Upgrade python-telegram-bot to 11.0.0 ([@fabaff] - [#16373]) ([telegram_bot docs]) +- Upgrade attrs to 18.2.0 ([@fabaff] - [#16372]) +- Update server.py ([@awarecan] - [#16375]) ([mqtt docs]) +- add_entities for switchmate ([@Danielhiversen] - [#16368]) ([switch.switchmate docs]) +- Support for playing radio preset by Onkyo media_player ([@pszafer] - [#16258]) ([cover.mqtt docs]) ([media_player.onkyo docs]) +- Bug fix for Tibber ([@Danielhiversen] - [#16397]) ([sensor.tibber docs]) +- zha: Bump to zigpy 0.2.0/bellows 0.7.0 ([@rcloran] - [#16404]) ([zha docs]) +- Fix SystemMonitor IP address sensor ([@ReneNulschDE] - [#16394]) ([sensor.systemmonitor docs]) +- add ExpressBus icon key to sensor.mvg ([@9R] - [#16387]) ([sensor.mvglive docs]) +- Device and entity registry remove config entry on unload ([@Kane610] - [#16247]) +- Add config flow for OpenUV ([@bachya] - [#16159]) ([openuv docs]) ([binary_sensor.openuv docs]) ([sensor.openuv docs]) +- Service to load new deCONZ devices without restart ([@Kane610] - [#16308]) ([deconz docs]) +- Delegate mqtt topic match validation to the paho mqtt client ([@rohankapoorcom] - [#16403]) ([mqtt docs]) +- Clean up dlink and some bug fix ([@Danielhiversen] - [#16346]) ([switch.dlink docs]) +- Implement correct state for RFlink cover ([@nudded] - [#16304]) ([cover.rflink docs]) +- Fix Mi Flora median calculation ([@PaulAnnekov] - [#16085]) ([sensor.miflora docs]) (breaking change) +- Add context to scripts and automations ([@balloob] - [#16415]) ([automation docs]) ([script docs]) ([automation.event docs]) ([automation.homeassistant docs]) ([automation.numeric_state docs]) ([automation.state docs]) ([automation.template docs]) ([automation.zone docs]) +- Fix openuv.config_flow unit test ([@awarecan] - [#16419]) +- Upgrade sense library to 0.4.2 ([@kbickar] - [#16429]) ([sensor.sense docs]) +- switchbot ([@Danielhiversen] - [#16396]) ([switch.switchbot docs]) (new-platform) +- Fix camera proxy to not require api_password to function ([@PhracturedBlue] - [#16450]) ([camera docs]) ([camera.proxy docs]) +- Upgrade shodan to 1.10.1 ([@fabaff] - [#16460]) ([sensor.shodan docs]) +- Upgrade Sphinx to 1.7.8 ([@fabaff] - [#16459]) +- update rfxtrx lib ([@Danielhiversen] - [#16463]) ([rfxtrx docs]) +- Added Twitch v5 support to the twitch platform ([@ioangogo] - [#16428]) ([sensor.twitch docs]) (breaking change) +- Fix waze_travel_time component startup ([@tsvi] - [#16465]) ([sensor.waze_travel_time docs]) +- Update license to official GitHub template ([@OverloadUT] - [#16470]) +- Add Yale Smart Alarm component ([@domwillcode] - [#16377]) ([alarm_control_panel.yale_smart_alarm docs]) (new-platform) +- Update radiotherm ([@cpw] - [#15031]) ([climate.radiotherm docs]) (breaking change) +- Support SNMPv3 and asyncio in snmp switch ([@mtdcr] - [#14754]) ([switch.snmp docs]) +- Fix GitHub change to resolve conflicts ([@fabaff] - [#16477]) ([switch.snmp docs]) +- Add OpenTherm Gateway climate platform ([@mvn23] - [#16299]) ([climate.opentherm_gw docs]) (new-platform) +- Support SNMPv3 and asyncio in snmp sensor ([@mtdcr] - [#14753]) ([sensor.snmp docs]) +- Add rate of change to statistics sensor ([@flo-wer] - [#15632]) ([sensor.statistics docs]) +- Restore status attribute for xiaomi_vacuum ([@tamasv] - [#16366]) ([vacuum docs]) ([vacuum.xiaomi_miio docs]) +- Check if API key is valid and users available ([@fabaff] - [#16494]) ([sensor.lastfm docs]) +- Update name legacy api password ([@balloob] - [#16455]) +- Fix Netgear LTESensor docstring ([@scop] - [#16501]) ([sensor.netgear_lte docs]) +- Update pyHS100 to 0.3.3 ([@amelchio] - [#16502]) ([light.tplink docs]) ([switch.tplink docs]) +- Move voluptuous-serialize to core requirement ([@awarecan] - [#16507]) ([config docs]) +- adds listener for OnAVStart and OnAVChange ([@tadly] - [#16495]) ([media_player.kodi docs]) +- Order imports ([@fabaff] - [#16515]) +- Upgrade aiohttp to 3.4.4 ([@awarecan] - [#16486]) +- Add a base_url configuration setting to tts. ([@lddubeau] - [#16478]) ([tts docs]) +- Upgrade youtube_dl to 2018.09.10 ([@fabaff] - [#16534]) ([media_extractor docs]) +- Upgrade keyring to 15.0.0 ([@fabaff] - [#16536]) +- Updates documentation repo URL in PR template ([@frenck] - [#16537]) +- Replace api_password in Camera.Push ([@dgomes] - [#16339]) ([camera.push docs]) (beta fix) +- Fail fetch auth providers if onboarding required ([@balloob] - [#16454]) ([auth docs]) (beta fix) +- Fix insteon Hub v1 support ([@teharris1] - [#16472]) ([insteon docs]) (beta fix) +- bugfix - incorrect camera type and missing sensors when multiple netatmo cameras ([@vikramgorla] - [#16490]) ([netatmo docs]) (beta fix) +- Fix arlo intilization when no base station available ([@zellux] - [#16529]) ([arlo docs]) (beta fix) +- Long-lived access token ([@awarecan] - [#16453]) ([auth docs]) (beta fix) +- Fix typo ([@balloob] - [#16556]) (beta fix) +- Fix invalid state ([@balloob] - [#16558]) (beta fix) +- Add websocket commands for refresh tokens ([@balloob] - [#16559]) ([auth docs]) (beta fix) +- Return if refresh token is current used one in WS API ([@awarecan] - [#16575]) ([auth docs]) ([websocket_api docs]) (beta fix) +- Track refresh token last usage information ([@awarecan] - [#16408]) ([auth docs]) (beta fix) +- Increasing python-websockets' version number ([@zoe1337] - [#16578]) ([media_player.webostv docs]) (beta fix) +- Add retry limit for chromecast connection ([@awarecan] - [#16471]) ([media_player.cast docs]) (beta fix) +- Fix broken bluetooth tracker ([@awarecan] - [#16589]) ([device_tracker docs]) (beta fix) +- Rewrite bluetooth le ([@pvizeli] - [#16592]) ([device_tracker docs]) (beta fix) + +[#14753]: https://github.com/home-assistant/home-assistant/pull/14753 +[#14754]: https://github.com/home-assistant/home-assistant/pull/14754 +[#15031]: https://github.com/home-assistant/home-assistant/pull/15031 +[#15252]: https://github.com/home-assistant/home-assistant/pull/15252 +[#15535]: https://github.com/home-assistant/home-assistant/pull/15535 +[#15632]: https://github.com/home-assistant/home-assistant/pull/15632 +[#15744]: https://github.com/home-assistant/home-assistant/pull/15744 +[#15925]: https://github.com/home-assistant/home-assistant/pull/15925 +[#15935]: https://github.com/home-assistant/home-assistant/pull/15935 +[#15953]: https://github.com/home-assistant/home-assistant/pull/15953 +[#15990]: https://github.com/home-assistant/home-assistant/pull/15990 +[#16080]: https://github.com/home-assistant/home-assistant/pull/16080 +[#16085]: https://github.com/home-assistant/home-assistant/pull/16085 +[#16157]: https://github.com/home-assistant/home-assistant/pull/16157 +[#16159]: https://github.com/home-assistant/home-assistant/pull/16159 +[#16176]: https://github.com/home-assistant/home-assistant/pull/16176 +[#16179]: https://github.com/home-assistant/home-assistant/pull/16179 +[#16185]: https://github.com/home-assistant/home-assistant/pull/16185 +[#16188]: https://github.com/home-assistant/home-assistant/pull/16188 +[#16192]: https://github.com/home-assistant/home-assistant/pull/16192 +[#16193]: https://github.com/home-assistant/home-assistant/pull/16193 +[#16194]: https://github.com/home-assistant/home-assistant/pull/16194 +[#16195]: https://github.com/home-assistant/home-assistant/pull/16195 +[#16203]: https://github.com/home-assistant/home-assistant/pull/16203 +[#16205]: https://github.com/home-assistant/home-assistant/pull/16205 +[#16212]: https://github.com/home-assistant/home-assistant/pull/16212 +[#16215]: https://github.com/home-assistant/home-assistant/pull/16215 +[#16217]: https://github.com/home-assistant/home-assistant/pull/16217 +[#16218]: https://github.com/home-assistant/home-assistant/pull/16218 +[#16229]: https://github.com/home-assistant/home-assistant/pull/16229 +[#16237]: https://github.com/home-assistant/home-assistant/pull/16237 +[#16247]: https://github.com/home-assistant/home-assistant/pull/16247 +[#16248]: https://github.com/home-assistant/home-assistant/pull/16248 +[#16251]: https://github.com/home-assistant/home-assistant/pull/16251 +[#16258]: https://github.com/home-assistant/home-assistant/pull/16258 +[#16259]: https://github.com/home-assistant/home-assistant/pull/16259 +[#16261]: https://github.com/home-assistant/home-assistant/pull/16261 +[#16262]: https://github.com/home-assistant/home-assistant/pull/16262 +[#16263]: https://github.com/home-assistant/home-assistant/pull/16263 +[#16265]: https://github.com/home-assistant/home-assistant/pull/16265 +[#16267]: https://github.com/home-assistant/home-assistant/pull/16267 +[#16275]: https://github.com/home-assistant/home-assistant/pull/16275 +[#16281]: https://github.com/home-assistant/home-assistant/pull/16281 +[#16296]: https://github.com/home-assistant/home-assistant/pull/16296 +[#16297]: https://github.com/home-assistant/home-assistant/pull/16297 +[#16299]: https://github.com/home-assistant/home-assistant/pull/16299 +[#16303]: https://github.com/home-assistant/home-assistant/pull/16303 +[#16304]: https://github.com/home-assistant/home-assistant/pull/16304 +[#16308]: https://github.com/home-assistant/home-assistant/pull/16308 +[#16323]: https://github.com/home-assistant/home-assistant/pull/16323 +[#16327]: https://github.com/home-assistant/home-assistant/pull/16327 +[#16337]: https://github.com/home-assistant/home-assistant/pull/16337 +[#16339]: https://github.com/home-assistant/home-assistant/pull/16339 +[#16340]: https://github.com/home-assistant/home-assistant/pull/16340 +[#16344]: https://github.com/home-assistant/home-assistant/pull/16344 +[#16346]: https://github.com/home-assistant/home-assistant/pull/16346 +[#16348]: https://github.com/home-assistant/home-assistant/pull/16348 +[#16352]: https://github.com/home-assistant/home-assistant/pull/16352 +[#16356]: https://github.com/home-assistant/home-assistant/pull/16356 +[#16359]: https://github.com/home-assistant/home-assistant/pull/16359 +[#16360]: https://github.com/home-assistant/home-assistant/pull/16360 +[#16361]: https://github.com/home-assistant/home-assistant/pull/16361 +[#16363]: https://github.com/home-assistant/home-assistant/pull/16363 +[#16365]: https://github.com/home-assistant/home-assistant/pull/16365 +[#16366]: https://github.com/home-assistant/home-assistant/pull/16366 +[#16368]: https://github.com/home-assistant/home-assistant/pull/16368 +[#16372]: https://github.com/home-assistant/home-assistant/pull/16372 +[#16373]: https://github.com/home-assistant/home-assistant/pull/16373 +[#16375]: https://github.com/home-assistant/home-assistant/pull/16375 +[#16377]: https://github.com/home-assistant/home-assistant/pull/16377 +[#16387]: https://github.com/home-assistant/home-assistant/pull/16387 +[#16394]: https://github.com/home-assistant/home-assistant/pull/16394 +[#16396]: https://github.com/home-assistant/home-assistant/pull/16396 +[#16397]: https://github.com/home-assistant/home-assistant/pull/16397 +[#16403]: https://github.com/home-assistant/home-assistant/pull/16403 +[#16404]: https://github.com/home-assistant/home-assistant/pull/16404 +[#16408]: https://github.com/home-assistant/home-assistant/pull/16408 +[#16415]: https://github.com/home-assistant/home-assistant/pull/16415 +[#16419]: https://github.com/home-assistant/home-assistant/pull/16419 +[#16428]: https://github.com/home-assistant/home-assistant/pull/16428 +[#16429]: https://github.com/home-assistant/home-assistant/pull/16429 +[#16450]: https://github.com/home-assistant/home-assistant/pull/16450 +[#16453]: https://github.com/home-assistant/home-assistant/pull/16453 +[#16454]: https://github.com/home-assistant/home-assistant/pull/16454 +[#16455]: https://github.com/home-assistant/home-assistant/pull/16455 +[#16459]: https://github.com/home-assistant/home-assistant/pull/16459 +[#16460]: https://github.com/home-assistant/home-assistant/pull/16460 +[#16463]: https://github.com/home-assistant/home-assistant/pull/16463 +[#16465]: https://github.com/home-assistant/home-assistant/pull/16465 +[#16470]: https://github.com/home-assistant/home-assistant/pull/16470 +[#16471]: https://github.com/home-assistant/home-assistant/pull/16471 +[#16472]: https://github.com/home-assistant/home-assistant/pull/16472 +[#16477]: https://github.com/home-assistant/home-assistant/pull/16477 +[#16478]: https://github.com/home-assistant/home-assistant/pull/16478 +[#16486]: https://github.com/home-assistant/home-assistant/pull/16486 +[#16490]: https://github.com/home-assistant/home-assistant/pull/16490 +[#16494]: https://github.com/home-assistant/home-assistant/pull/16494 +[#16495]: https://github.com/home-assistant/home-assistant/pull/16495 +[#16501]: https://github.com/home-assistant/home-assistant/pull/16501 +[#16502]: https://github.com/home-assistant/home-assistant/pull/16502 +[#16507]: https://github.com/home-assistant/home-assistant/pull/16507 +[#16515]: https://github.com/home-assistant/home-assistant/pull/16515 +[#16529]: https://github.com/home-assistant/home-assistant/pull/16529 +[#16534]: https://github.com/home-assistant/home-assistant/pull/16534 +[#16536]: https://github.com/home-assistant/home-assistant/pull/16536 +[#16537]: https://github.com/home-assistant/home-assistant/pull/16537 +[#16556]: https://github.com/home-assistant/home-assistant/pull/16556 +[#16558]: https://github.com/home-assistant/home-assistant/pull/16558 +[#16559]: https://github.com/home-assistant/home-assistant/pull/16559 +[#16575]: https://github.com/home-assistant/home-assistant/pull/16575 +[#16578]: https://github.com/home-assistant/home-assistant/pull/16578 +[#16589]: https://github.com/home-assistant/home-assistant/pull/16589 +[#16592]: https://github.com/home-assistant/home-assistant/pull/16592 +[@9R]: https://github.com/9R +[@ASMfreaK]: https://github.com/ASMfreaK +[@Cereal2nd]: https://github.com/Cereal2nd +[@Danielhiversen]: https://github.com/Danielhiversen +[@Joshi425]: https://github.com/Joshi425 +[@JulianKahnert]: https://github.com/JulianKahnert +[@Kane610]: https://github.com/Kane610 +[@MarcSN311]: https://github.com/MarcSN311 +[@OverloadUT]: https://github.com/OverloadUT +[@PaulAnnekov]: https://github.com/PaulAnnekov +[@PhracturedBlue]: https://github.com/PhracturedBlue +[@ReneNulschDE]: https://github.com/ReneNulschDE +[@amelchio]: https://github.com/amelchio +[@aronsky]: https://github.com/aronsky +[@awarecan]: https://github.com/awarecan +[@bachya]: https://github.com/bachya +[@balloob]: https://github.com/balloob +[@bieniu]: https://github.com/bieniu +[@cgtobi]: https://github.com/cgtobi +[@cpw]: https://github.com/cpw +[@danielperna84]: https://github.com/danielperna84 +[@dgomes]: https://github.com/dgomes +[@djm300]: https://github.com/djm300 +[@domwillcode]: https://github.com/domwillcode +[@endor-force]: https://github.com/endor-force +[@exxamalte]: https://github.com/exxamalte +[@fabaff]: https://github.com/fabaff +[@flo-wer]: https://github.com/flo-wer +[@frenck]: https://github.com/frenck +[@fucm]: https://github.com/fucm +[@grea09]: https://github.com/grea09 +[@htotoo]: https://github.com/htotoo +[@ioangogo]: https://github.com/ioangogo +[@jesserizzo]: https://github.com/jesserizzo +[@kariudo]: https://github.com/kariudo +[@kbickar]: https://github.com/kbickar +[@lddubeau]: https://github.com/lddubeau +[@mtdcr]: https://github.com/mtdcr +[@mvn23]: https://github.com/mvn23 +[@nudded]: https://github.com/nudded +[@phil65]: https://github.com/phil65 +[@pnbruckner]: https://github.com/pnbruckner +[@pszafer]: https://github.com/pszafer +[@pvizeli]: https://github.com/pvizeli +[@rcloran]: https://github.com/rcloran +[@rohankapoorcom]: https://github.com/rohankapoorcom +[@rytilahti]: https://github.com/rytilahti +[@schmittx]: https://github.com/schmittx +[@scop]: https://github.com/scop +[@smurfix]: https://github.com/smurfix +[@tadly]: https://github.com/tadly +[@tamasv]: https://github.com/tamasv +[@teharris1]: https://github.com/teharris1 +[@thomasdelaet]: https://github.com/thomasdelaet +[@thomaslian]: https://github.com/thomaslian +[@tschmidty69]: https://github.com/tschmidty69 +[@tsvi]: https://github.com/tsvi +[@vikramgorla]: https://github.com/vikramgorla +[@vrih]: https://github.com/vrih +[@zellux]: https://github.com/zellux +[@zoe1337]: https://github.com/zoe1337 +[alarm_control_panel.yale_smart_alarm docs]: /components/alarm_control_panel.yale_smart_alarm/ +[arlo docs]: /components/arlo/ +[asterisk_mbox docs]: /components/asterisk_mbox/ +[auth docs]: /components/auth/ +[automation docs]: /components/automation/ +[automation.event docs]: /docs/automation/trigger/#event-trigger +[automation.homeassistant docs]: /docs/automation/trigger/#home-assistant-trigger +[automation.numeric_state docs]: /docs/automation/trigger/#numeric-state-trigger +[automation.state docs]: /docs/automation/trigger/#state-trigger +[automation.template docs]: /docs/automation/trigger/#template-trigger +[automation.zone docs]: /docs/automation/trigger/#zone-trigger +[binary_sensor.deconz docs]: /components/binary_sensor.deconz/ +[binary_sensor.openuv docs]: /components/binary_sensor.openuv/ +[camera docs]: /components/camera/ +[camera.proxy docs]: /components/camera.proxy/ +[camera.push docs]: /components/camera.push/ +[climate.generic_thermostat docs]: /components/climate.generic_thermostat/ +[climate.nest docs]: /components/climate.nest/ +[climate.opentherm_gw docs]: /components/climate.opentherm_gw/ +[climate.radiotherm docs]: /components/climate.radiotherm/ +[config docs]: /components/config/ +[cover.insteon docs]: /components/cover.insteon/ +[cover.mqtt docs]: /components/cover.mqtt/ +[cover.myq docs]: /components/cover.myq/ +[cover.rflink docs]: /components/cover.rflink/ +[deconz docs]: /components/deconz/ +[device_tracker docs]: /components/device_tracker/ +[feedreader docs]: /components/feedreader/ +[geo_location docs]: /components/geo_location/ +[habitica docs]: /components/habitica/ +[hangouts docs]: /components/hangouts/ +[homematic docs]: /components/homematic/ +[hue docs]: /components/hue/ +[insteon docs]: /components/insteon/ +[light.deconz docs]: /components/light.deconz/ +[light.hue docs]: /components/light.hue/ +[light.mqtt docs]: /components/light.mqtt/ +[light.tplink docs]: /components/light.tplink/ +[media_extractor docs]: /components/media_extractor/ +[media_player.cast docs]: /components/media_player.cast/ +[media_player.kodi docs]: /components/media_player.kodi/ +[media_player.onkyo docs]: /components/media_player.onkyo/ +[media_player.songpal docs]: /components/media_player.songpal/ +[media_player.sonos docs]: /components/media_player.sonos/ +[media_player.webostv docs]: /components/media_player.webostv/ +[media_player.yamaha docs]: /components/media_player.yamaha/ +[mqtt docs]: /components/mqtt/ +[netatmo docs]: /components/netatmo/ +[notify docs]: /components/notify/ +[openuv docs]: /components/openuv/ +[rfxtrx docs]: /components/rfxtrx/ +[scene.deconz docs]: /components/scene.deconz/ +[script docs]: /components/script/ +[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/ +[sensor.apcupsd docs]: /components/sensor.apcupsd/ +[sensor.darksky docs]: /components/sensor.darksky/ +[sensor.deconz docs]: /components/sensor.deconz/ +[sensor.dht docs]: /components/sensor.dht/ +[sensor.dnsip docs]: /components/sensor.dnsip/ +[sensor.enphase_envoy docs]: /components/sensor.enphase_envoy/ +[sensor.geizhals docs]: /components/sensor.geizhals/ +[sensor.habitica docs]: /components/sensor.habitica/ +[sensor.lastfm docs]: /components/sensor.lastfm/ +[sensor.miflora docs]: /components/sensor.miflora/ +[sensor.mvglive docs]: /components/sensor.mvglive/ +[sensor.netatmo docs]: /components/sensor.netatmo/ +[sensor.netgear_lte docs]: /components/sensor.netgear_lte/ +[sensor.openuv docs]: /components/sensor.openuv/ +[sensor.qnap docs]: /components/sensor.qnap/ +[sensor.sense docs]: /components/sensor.sense/ +[sensor.shodan docs]: /components/sensor.shodan/ +[sensor.snmp docs]: /components/sensor.snmp/ +[sensor.sql docs]: /components/sensor.sql/ +[sensor.statistics docs]: /components/sensor.statistics/ +[sensor.systemmonitor docs]: /components/sensor.systemmonitor/ +[sensor.tahoma docs]: /components/sensor.tahoma/ +[sensor.tibber docs]: /components/sensor.tibber/ +[sensor.trafikverket_weatherstation docs]: /components/sensor.trafikverket_weatherstation/ +[sensor.twitch docs]: /components/sensor.twitch/ +[sensor.velbus docs]: /components/sensor.velbus/ +[sensor.volkszaehler docs]: /components/sensor.volkszaehler/ +[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/ +[snips docs]: /components/snips/ +[switch.deconz docs]: /components/switch.deconz/ +[switch.dlink docs]: /components/switch.dlink/ +[switch.snmp docs]: /components/switch.snmp/ +[switch.switchbot docs]: /components/switch.switchbot/ +[switch.switchmate docs]: /components/switch.switchmate/ +[switch.tahoma docs]: /components/switch.tahoma/ +[switch.tplink docs]: /components/switch.tplink/ +[tahoma docs]: /components/tahoma/ +[telegram_bot docs]: /components/telegram_bot/ +[tts docs]: /components/tts/ +[upnp docs]: /components/upnp/ +[vacuum docs]: /components/vacuum/ +[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/ +[velbus docs]: /components/velbus/ +[websocket_api docs]: /components/websocket_api/ +[zha docs]: /components/zha/ +[zoneminder docs]: /components/zoneminder/ diff --git a/source/_posts/2018-09-17-thinking-big.markdown b/source/_posts/2018-09-17-thinking-big.markdown new file mode 100644 index 00000000000..d1b482d223b --- /dev/null +++ b/source/_posts/2018-09-17-thinking-big.markdown @@ -0,0 +1,97 @@ +--- +layout: post +title: "Thinking Big" +description: "Today we're turning 5 years old. It's time to set some goals." +date: 2018-09-17 01:01:00 +date_formatted: "September 17, 2018" +author: Paulus Schoutsen +author_twitter: balloob +comments: true +categories: Announcements +og_image: /images/blog/2018-09-thinking-big/social.png +--- + +Today marks the 5th anniversary of Home Assistant. I want to spend this post not only reflecting on the last 5 years, but also look at what is ahead of us, where we want to go, what we want Home Assistant to be. + +Home Assistant wasn’t born out of ideology. I built it because I got some smart lights and wanted to script them. I made that script open source and it went from there. As Home Assistant has grown, so has the world around us, and so have I. + +A lot of IoT products have been introduced since Home Assistant started. Sadly, the trend in these products is to send all data to the cloud and manage your house from there. I’ve come to realize that it’s not in the big corporations interest to make a product that focuses on privacy and local control. Our data is too useful for them. + +I don’t like this trend. I don’t like seeing more and more of our data being hoarded by a few giant companies, centralizing it in a few systems and using it to influence how we’ll be treated online. It’s our lives, our data, and we should be in control. Not some algorithm optimized for engagement. + +And so I want to introduce a goal for Home Assistant. A goal that will shape how the platform will evolve in the upcoming years. + + +## {% linkable_title The goal %} + +It’s our goal to create a people focused home automation platform. A platform that is open source and which prioritizes privacy and local control. + + - **Privacy.** All your data will be stored locally. + - **Local control.** All logic will run locally. The cloud will only be invoked as needed. + - **Open source.** The platform is freely available for users and companies alike. The more people that choose a privacy focused platform over a cloud-based one is a win for us. + - **Interoperability.** The platform implements APIs to easily share the data. We want your data to be available to any other application that you wish. + +## {% linkable_title What we’re going to build to achieve this goal %} + +Many things! However, here is a list of things that I am most enthusiastic about: + + - Remote connection to your instance to control Home Assistant while being away. We will use end-to-end encryption to ensure that the cloud can’t read your data. Powered by Home Assistant Cloud so you just have to log in and it will work. This is the next feature to be worked on for the cloud. + - Attribution. We’ve recently added both users and context. Next up is making it visible in the logbook which user was responsible for what change. + - Permissions. Using the same user and context features, we will also be able to limit access to entities to users. + - Improved device management. We’ve recently added devices to Home Assistant. As a user, you will be able to place devices in areas, see which entities are part of a device and make sure your entities are up to date. + - Accessibility. We want to make Hass.io run on as many devices as possible, making it very easy for people to get started with a private home. + - Integrate Mozilla's [Web Things API] to make it easier to interact with other home automation platforms. The introduced device management makes it perfectly aligned with the Web Things data model. + - Cloud Transparency. We want to make it visible what data is being shared with Amazon Alexa and Google Home clouds. + - Better Z-Wave. Our current integration has room for improvement. The owner of Z-Wave has announced a [public SDK](http://zwavepublic.com/), which we should explore to integrate with Home Assistant. + +## {% linkable_title What we need to achieve this goal %} + +Home Assistant has grown beyond what we can expect from people to handle in their spare time. We want to keep the community friendly, our code quality high, our upgrades smooth, our documentation up to date and our platform secure. + +In Ubiquiti we’ve found a great partner with aligned goals. They hired me in April to work full-time on Home Assistant which has already resulted in great progress – including some of the enhancements listed above. But one full-time employee is not enough. + +So I have started a new company to raise money and help Home Assistant achieve its goals: [Nabu Casa, Inc][nabu-home]. The company will run Home Assistant Cloud for a $5/month subscription. The revenue will be used to extend the cloud functionality, finance the infrastructure of the Home Assistant website and community, and pay full-time employees to contribute to Home Assistant to reach its goals. + +
Logo of Nabu Casa, Inc +
+ +Nabu Casa, Inc. will only be funded by its subscribers. That way it is guaranteed that we will do what is best for our users, the ones that provide the money. We will not raise any money from investors. Big money tends to care more about making more money than humans and privacy. We need to stay in control to ensure our goals are met. + +If you have been a user of Home Assistant Cloud for the last 9 months, we want to thank you for being part of our open beta. All members of the open beta will be automatically enrolled in the free trial and will be able to use Home Assistant Cloud for one more month till October 17, no changes in Home Assistant necessary. If you haven’t entered any payment information by the end of the trial, you will lose access to Home Assistant Cloud. + +More information: + + - [Nabu Casa, Inc homepage][nabu-home] + - [Manage your Home Assistant Cloud account][nabu-account] + +## {% linkable_title FAQ %} + +### {% linkable_title Do I have to pay to use Home Assistant and Hass.io? %} + +No. Home Assistant is open source and free to install and this will not change. Only the cloud service will be part of a paid subscription. + +### {% linkable_title Will Home Assistant and Hass.io remain open source? %} + +Yes. Nabu Casa will only be responsible for Home Assistant Cloud and it will contribute resources to help Home Assistant achieve its goals and pay for its infrastructure. + +### {% linkable_title Why not take donations? %} + +Relying on donations makes budgeting for employees impossible without exposing them and their families to the risk of not getting a paycheck at the end of the month. + +### {% linkable_title Is Home Assistant Cloud open source? %} + +The majority of Home Assistant Cloud is open source. The Alexa skill source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/alexa/smart_home.py) (with manual setup instructions [here](https://github.com/mike-grant/haaska/)) and the Google Assistant source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/google_assistant/smart_home.py) (with manual setup instructions [here](https://www.home-assistant.io/components/google_assistant/)). Our account page and relayer are not open source. + +### {% linkable_title Will you offer a lifetime plan for a one time fee? %} + +No. A lifetime plan to a cloud service is a pyramid scheme. It means new subscribers pay for the costs of the lifetime customers. + +### {% linkable_title I think the price is too high for what I get %} + +New features will be added in the future without a price increase. The next feature we’re planning to release is encrypted remote access to your instance. + +The subscription fee does not only cover the cost of running Home Assistant Cloud. The revenue will also be used to pay for the infrastructure of running Home Assistant and the community forums. + +[nabu-home]: https://www.nabucasa.com +[nabu-account]: https://account.nabucasa.com +[Web Things API]: https://iot.mozilla.org/wot/ diff --git a/source/cloud/alexa.markdown b/source/cloud/alexa.markdown index 7e140825afd..58cbefee6a8 100644 --- a/source/cloud/alexa.markdown +++ b/source/cloud/alexa.markdown @@ -3,112 +3,14 @@ layout: page title: "Alexa via Home Assistant Cloud" description: "Enable the Alexa integration via Home Assistant Cloud integration." date: 2017-11-17 20:00 -sidebar: true +sidebar: false comments: false sharing: true footer: true redirect_from: /components/cloud.alexa/ --- -The Alexa integration allows users to control the entities via the [Home Assistant Smart Home skill for Alexa][alexa skill]. This means that you can say things like "Alexa, turn on the kitchen light" to control your local Home Assistant. +Home Assistant Cloud is a subscription service provided by our partner Nabu Casa, Inc. Check out [their website](https://www.nabucasa.com/config/amazon_alexa/) for help with the Amazon Alexa integration via Home Assistant Cloud. -To use this integration, you need to have: - - - The cloud component set up. [Learn more](/components/cloud/) - - An Alexa enabled device like the Amazon Echo - - Activated the [Home Assistant Smart Home skill for Alexa][alexa skill] - -You can use `configuration.yaml` to configure the entities that are being shown to Alexa and how they are exposed. - -```yaml -# Example configuration.yaml entry configuring Alexa -cloud: - alexa: - filter: - include_entities: - - light.kitchen - - light.kitchen_left - include_domains: - - switch - exclude_entities: - - switch.outside - entity_config: - light.kitchen: - name: Custom Name for Alexa - description: The light in the kitchen - switch.stairs: - display_categories: LIGHT -``` - -{% configuration cloud %} -alexa: - description: Configuration options for the Amazon Alexa integration. - required: false - type: map - keys: - filter: - description: Filters for entities to include/exclude from Alexa. - required: false - type: map - keys: - include_entities: - description: Entity IDs to include. - required: false - type: list - include_domains: - description: Domains to include. - required: false - type: list - exclude_entities: - description: Entity IDs to exclude. - required: false - type: list - exclude_domains: - description: Domains to exclude. - required: false - type: list - entity_config: - description: Entity specific configuration for Alexa - required: false - type: map - keys: - '``': - description: Entity to configure - required: false - type: map - keys: - name: - description: Name of entity to show in Alexa - required: false - type: string - description: - description: Description of entity to show in Alexa - required: false - type: string - display_categories: - description: The display category to use in Alexa. [Available categories](https://developer.amazon.com/docs/device-apis/alexa-discovery.html#display-categories) - required: false - type: string -{% endconfiguration %} - -### {% linkable_title Possible values for customizing %} - -_Configuration via `customize:` is no longer available. Use the entity config as described above._ - -### {% linkable_title Available domains %} -Currently, the following domains are available to be used with Alexa: - -- alert -- automation (enables/disables) -- cover -- fan (supports on/off and set speed) -- group -- input_boolean -- light -- lock (lock and unlock, but unlock is untested as Amazon has disabled unlock for now) -- media_player (play, pause, stop, set volume, adjust volume, next track, and previous track) -- scene -- script (enables/disables) -- switch - -[alexa skill]: https://alexa.amazon.com/spa/index.html#skills/dp/B0772J1QKB/?ref=skill_dsk_skb_sr_2 +
Logo of Nabu Casa, Inc +
diff --git a/source/cloud/google_assistant.markdown b/source/cloud/google_assistant.markdown index 7868c9387bb..4d17dfb7fe5 100644 --- a/source/cloud/google_assistant.markdown +++ b/source/cloud/google_assistant.markdown @@ -3,100 +3,13 @@ layout: page title: "Google Assistant via Home Assistant Cloud" description: "Enable the Google Assistant via Home Assistant Cloud integration." date: 2017-11-17 20:00 -sidebar: true +sidebar: false comments: false sharing: true footer: true --- -

-The minimum supported version of Home Assistant is 0.65.6. -

+Home Assistant Cloud is a subscription service provided by our partner Nabu Casa, Inc. Check out [their website](https://www.nabucasa.com/config/google_assistant/) for help with the Google Assistant integration via Home Assistant Cloud. -The Google Assistant integration allows users to control the entities via the Home Assistant Smart Home skill for Google Assistant. This means that you can say things like "Ok Google, turn on the kitchen light" to control your local Home Assistant. - -To use this integration, you need to have: - - - The cloud component set up. [Learn more](/components/cloud/) - - A Google Assistant enabled device like the Google Home or a mobile phone running Google Assistant. - - Activated the Home Assistant Smart Home skill for Google Assistant. - - If you have a Google Home device, use the Google Home app, select *Home control*, and then add *hass.io* using the *Add devices* option. - - If you only have a mobile phone, launch Google Assistant, select the three dots menu. Under *Settings* you'll find *Home Control*. There you can add *hass.io* using the *Add devices* option. - -You can use `configuration.yaml` to configure the entities that are being shown to Google Assistant and how they are exposed. - -```yaml -# Example configuration.yaml entry configuring Google Assistant -cloud: - google_actions: - filter: - include_entities: - - light.kitchen - - light.kitchen_left - include_domains: - - switch - exclude_entities: - - switch.outside - entity_config: - switch.kitchen: - name: Custom Name for Google Assistant - aliases: - - bright lights - - entry lights - room: living room -``` - -{% configuration cloud %} -google_actions: - description: Configuration options for the Google Assistant integration. - required: false - type: map - keys: - filter: - description: Filters for entities to include/exclude from Google Assistant. - required: false - type: map - keys: - include_entities: - description: Entity IDs to include. - required: false - type: list - include_domains: - description: Domains to include. - required: false - type: list - exclude_entities: - description: Entity IDs to exclude. - required: false - type: list - exclude_domains: - description: Domains to exclude. - required: false - type: list - entity_config: - description: Entity specific configuration for Google Assistant. - required: false - type: map - keys: - '``': - description: Entity to configure - required: false - type: map - keys: - name: - description: Name of entity to show in Google Assistant. - required: false - type: string - aliases: - description: Aliases that can also be used to refer to this entity. - required: false - type: list - room: - description: Hint for Google Assistant in which room this entity is. - required: false - type: string -{% endconfiguration %} - -

-After setting up the cloud, if you make any device changes such as changing the name or adding a new device simply say "Ok Google, sync my devices" to get the changes to show up. -

+
Logo of Nabu Casa, Inc +
diff --git a/source/cloud/index.markdown b/source/cloud/index.markdown index 24f5cf76aa4..92749a82231 100644 --- a/source/cloud/index.markdown +++ b/source/cloud/index.markdown @@ -3,7 +3,7 @@ layout: page title: "Home Assistant Cloud" description: "Enable the Home Assistant Cloud integration." date: 2017-11-17 20:00 -sidebar: true +sidebar: false comments: false sharing: true footer: true @@ -13,32 +13,7 @@ ha_category: Voice ha_iot_class: "Cloud Push" --- -

The Home Assistant Cloud is currently free and will become part of the upcoming Community Support Package. [Learn more](/blog/2017/12/17/introducing-home-assistant-cloud/)

+Home Assistant Cloud is a subscription service provided by our partner Nabu Casa, Inc. Check out [their website](https://www.nabucasa.com) For more information on features, pricing and how to configure Home Assistant. -The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services. The following integrations are currently available: - - - [Amazon Alexa (Amazon Echo)](/cloud/alexa/) - - [Google Assistant (Google Home)](/cloud/google_assistant/) - -### {% linkable_title How does it work? %} - -The Home Assistant Cloud has been designed with security in mind. When you activate the Cloud component, your instance will create a secure connection to the Home Assistant Cloud. There is no need for any further configuration or to expose your instance to the internet. - -Integrations like Alexa or Google will deliver messages to our cloud which we will forward to your local instance for processing. We just forward the response back. This means that we do not have to store the state of your house in our cloud, we’re just the messenger! - -You can find a list of frequently asked questions (and their answers) in [this blog post](/blog/2017/12/17/introducing-home-assistant-cloud/#faq). - -### {% linkable_title Enabling the cloud %} - -The Home Assistant Cloud is enabled by default. If not, add this to your configuration: - -```yaml -# Example configuration.yaml entry to enable the cloud component -cloud: -``` - -Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your configuration.yaml` file. - -```yaml -config: -``` +
Logo of Nabu Casa, Inc +
diff --git a/source/cloud/troubleshooting.markdown b/source/cloud/troubleshooting.markdown index c9868e882f1..4e8c2a88d79 100644 --- a/source/cloud/troubleshooting.markdown +++ b/source/cloud/troubleshooting.markdown @@ -3,36 +3,13 @@ layout: page title: "Troubleshooting Home Assistant Cloud" description: "Pointers to help troubleshooting issues with Home Assistant Cloud." date: 2018-07-17 20:00 -sidebar: true +sidebar: false comments: false sharing: true footer: true --- -Alright, so you got all excited, tried to setup cloud and it failed? Not to worry, here are some common issues and how to resolve them. +Home Assistant Cloud is a subscription service provided by our partner Nabu Casa, Inc. Check out [their website](https://www.nabucasa.com/config/troubleshooting/) for help with troubleshooting. -## {% linkable_title Error fetching the cognito keyset %} - -This issue can occur by Docker being misconfigured. This issue is especially common for people using the GENERIC installation of Hass.io on top of Ubuntu Bionic or another Linux installation. It is related to IPv6 being incorrectly marked as available. - -The solution is to make sure that Docker uses a public available DNS server, like the Google ones. As root, run: - -``` -mkdir -p /etc/docker -echo '{"dns": ["8.8.8.8", "8.8.4.4"]}' > /etc/docker/daemon.json -``` - -## {% linkable_title Alexa: We were unable to link Home Assistant at this time. Please try again later %} - -Some users are experiencing an issue when they are setting up the Home Assistant skill inside the Alexa app. We are still researching what is going on. Some users have reported that the issue went away if they configured Alexa to not expose all entities. You can try this by changing your cloud configuration like this: - -```yaml -# Example configuration.yaml entry configuring Alexa -cloud: - alexa: - filter: - include_entities: - - light.kitchen -``` - -If this resolves the issue, please report it in the #cloud channel on Discord as it can help us find the entities that are causing this issue. +
Logo of Nabu Casa, Inc +
diff --git a/source/developers/credits.markdown b/source/developers/credits.markdown index 6eacda0733f..5de3f71a6d2 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: 2018-08-28 07:39:11 +0000 +date: 2018-09-21 19:49:45 +0000 sidebar: true comments: false sharing: true @@ -13,7 +13,7 @@ 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 "7458 total commits to the home-assistant organization, 4212 commits to home-assistant, 1565 commits to home-assistant.io, 1011 commits to home-assistant-polymer, 237 commits to home-assistant-js, 126 commits to netdisco, 110 commits to developers.home-assistant, 66 commits to home-assistant-js-websocket, 38 commits to hass-release, 17 commits to LabelBot, 15 commits to home-assistant-assets, 10 commits to hassio, 9 commits to hbmqtt-auth-home-assistant, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 6 commits to custom-panel-starter-kit-react, 4 commits to ui-schema, 3 commits to hassio-addons, 3 commits to hassio-build, 2 commits to home-assistant-iOS, 2 commits to issue-bot, 2 commits to lambda-home-assistant-github, 2 commits to hassio-addons-example, 1 commit to warrant, 1 commit to home-assistant-notebooks, 1 commit to architecture") +- [Paulus Schoutsen (@balloob)](https://github.com/balloob "7690 total commits to the home-assistant organization, 4314 commits to home-assistant, 1588 commits to home-assistant.io, 1067 commits to home-assistant-polymer, 237 commits to home-assistant-js, 129 commits to developers.home-assistant, 127 commits to netdisco, 94 commits to home-assistant-js-websocket, 40 commits to hass-release, 17 commits to LabelBot, 15 commits to home-assistant-assets, 11 commits to hassio, 9 commits to hbmqtt-auth-home-assistant, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 6 commits to custom-panel-starter-kit-react, 4 commits to ui-schema, 3 commits to hassio-addons, 3 commits to hassio-build, 2 commits to issue-bot, 2 commits to home-assistant-iOS, 2 commits to hassio-addons-example, 2 commits to lambda-home-assistant-github, 1 commit to home-assistant-notebooks, 1 commit to warrant, 1 commit to architecture") ### {% linkable_title Contributors %} @@ -21,9 +21,9 @@ This page contains a list of people who have contributed in one way or another t - [7even (@hwikene)](https://github.com/hwikene "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [a-andre (@a-andre)](https://github.com/a-andre "3 total commits to the home-assistant organization, 3 commits to home-assistant") -- [Aaron Bach (@bachya)](https://github.com/bachya "81 total commits to the home-assistant organization, 56 commits to home-assistant, 25 commits to home-assistant.io") +- [Aaron Bach (@bachya)](https://github.com/bachya "84 total commits to the home-assistant organization, 59 commits to home-assistant, 25 commits to home-assistant.io") - [Aaron Linville (@linville)](https://github.com/linville "2 total commits to the home-assistant organization, 2 commits to appdaemon") -- [Abílio Costa (@abmantis)](https://github.com/abmantis "24 total commits to the home-assistant organization, 14 commits to home-assistant, 6 commits to home-assistant.io, 2 commits to home-assistant-polymer, 1 commit to home-assistant-js-websocket, 1 commit to netdisco") +- [Abílio Costa (@abmantis)](https://github.com/abmantis "26 total commits to the home-assistant organization, 15 commits to home-assistant, 7 commits to home-assistant.io, 2 commits to home-assistant-polymer, 1 commit to home-assistant-js-websocket, 1 commit to netdisco") - [Adam Baxter (@voltagex)](https://github.com/voltagex "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Adam Cooper (@GenericStudent)](https://github.com/GenericStudent "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.io") - [Adam Dullage (@Dullage)](https://github.com/Dullage "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") @@ -41,37 +41,32 @@ This page contains a list of people who have contributed in one way or another t - [Albatross (@DyingAlbatross)](https://github.com/DyingAlbatross "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") - [Albert Lee (@trisk)](https://github.com/trisk "20 total commits to the home-assistant organization, 12 commits to home-assistant, 8 commits to home-assistant.io") - [Alberto Arias Maestro (@albertoarias)](https://github.com/albertoarias "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Alec Rust (@AlecRust)](https://github.com/AlecRust "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") - [Alessandro Mogavero (@alexmogavero)](https://github.com/alexmogavero "3 total commits to the home-assistant organization, 3 commits to home-assistant") +- [Alessandro Staniscia (@Odyno)](https://github.com/Odyno "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Alex Barcelo (@alexbarcelo)](https://github.com/alexbarcelo "7 total commits to the home-assistant organization, 4 commits to home-assistant.io, 3 commits to hassio-addons") - [Alex Harvey (@infamy)](https://github.com/infamy "29 total commits to the home-assistant organization, 14 commits to home-assistant, 11 commits to home-assistant.io, 4 commits to hassos") -- [Alex Mekkering (@AlexMekkering)](https://github.com/AlexMekkering "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") - [Alex MF (@adsmf)](https://github.com/adsmf "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [Alex Osadchyy (@aosadchyy)](https://github.com/aosadchyy "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Alex Tzonkov (@attzonko)](https://github.com/attzonko "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") -- [Alexander Bachmeier (@asbach)](https://github.com/asbach "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") - [Alexander Kratzer (@hexxter)](https://github.com/hexxter "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [Alexandre Perrin (@kAworu)](https://github.com/kAworu "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Alexei Chetroi (@Adminiuga)](https://github.com/Adminiuga "4 total commits to the home-assistant organization, 3 commits to home-assistant, 1 commit to home-assistant-polymer") +- [Alexei Chetroi (@Adminiuga)](https://github.com/Adminiuga "12 total commits to the home-assistant organization, 11 commits to home-assistant, 1 commit to home-assistant-polymer") - [Alexis Iglauer (@ax42)](https://github.com/ax42 "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Alfie Day (@Azelphur)](https://github.com/Azelphur "12 total commits to the home-assistant organization, 12 commits to home-assistant") - [Aliaksandr (@minchik)](https://github.com/minchik "7 total commits to the home-assistant organization, 3 commits to home-assistant.io, 2 commits to appdaemon, 2 commits to home-assistant") -- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "148 total commits to the home-assistant organization, 83 commits to home-assistant.io, 53 commits to home-assistant, 7 commits to home-assistant-polymer, 3 commits to developers.home-assistant, 1 commit to hassio-addons, 1 commit to pi-gen") +- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "148 total commits to the home-assistant organization, 83 commits to home-assistant.io, 53 commits to home-assistant, 7 commits to home-assistant-polymer, 3 commits to developers.home-assistant, 1 commit to pi-gen, 1 commit to hassio-addons") - [amorsillo (@AndrewMorsillo)](https://github.com/AndrewMorsillo "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Anders Fogh Eriksen (@Fogh)](https://github.com/Fogh "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") -- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "245 total commits to the home-assistant organization, 199 commits to home-assistant, 44 commits to home-assistant.io, 2 commits to home-assistant-polymer") +- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "252 total commits to the home-assistant organization, 206 commits to home-assistant, 44 commits to home-assistant.io, 2 commits to home-assistant-polymer") - [andig (@andig)](https://github.com/andig "2 total commits to the home-assistant organization, 2 commits to pi-gen") -- [Andrea Campi (@andreacampi)](https://github.com/andreacampi "8 total commits to the home-assistant organization, 6 commits to home-assistant, 2 commits to home-assistant.io") +- [Andrea Campi (@andreacampi)](https://github.com/andreacampi "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Andreas Björshammar (@abjorshammar)](https://github.com/abjorshammar "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Andreas Jacobsen (@andreasjacobsen93)](https://github.com/andreasjacobsen93 "8 total commits to the home-assistant organization, 6 commits to home-assistant.io, 2 commits to hassio-addons") +- [Andreas Oberritter (@mtdcr)](https://github.com/mtdcr "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") - [Andreas Rammhold (@andir)](https://github.com/andir "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Andreas Renberg (@IQAndreas)](https://github.com/IQAndreas "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") - [Andreea\-Daniela Ene (@AndreeaEne)](https://github.com/AndreeaEne "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Andrei Pop (@andreipop2005)](https://github.com/andreipop2005 "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Andrej Friesen (@ajfriesen)](https://github.com/ajfriesen "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Andrew (@aneisch)](https://github.com/aneisch "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") -- [Andrew (@aoakeson)](https://github.com/aoakeson "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") -- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "821 total commits to the home-assistant organization, 686 commits to appdaemon, 88 commits to hadashboard, 25 commits to scenegen, 22 commits to home-assistant.io") +- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "836 total commits to the home-assistant organization, 701 commits to appdaemon, 88 commits to hadashboard, 25 commits to scenegen, 22 commits to home-assistant.io") - [Andrew Smith (@andrewmichaelsmith)](https://github.com/andrewmichaelsmith "2 total commits to the home-assistant organization, 2 commits to pi-gen") - [Andrew Stock (@watchforstock)](https://github.com/watchforstock "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Andrew Thigpen (@andythigpen)](https://github.com/andythigpen "33 total commits to the home-assistant organization, 32 commits to home-assistant, 1 commit to home-assistant-js") @@ -80,7 +75,6 @@ This page contains a list of people who have contributed in one way or another t - [Andrey (@andrey-git)](https://github.com/andrey-git "323 total commits to the home-assistant organization, 147 commits to home-assistant, 138 commits to home-assistant-polymer, 37 commits to home-assistant.io, 1 commit to home-assistant-js-websocket") - [Andrey Kupreychik (@foxel)](https://github.com/foxel "13 total commits to the home-assistant organization, 8 commits to home-assistant, 5 commits to home-assistant.io") - [Andrzej (@andriej)](https://github.com/andriej "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Andréas Lundgren (@adevade)](https://github.com/adevade "2 total commits to the home-assistant organization, 2 commits to home-assistant.io") - [Andy Castille (@Klikini)](https://github.com/Klikini "18 total commits to the home-assistant organization, 11 commits to home-assistant, 7 commits to home-assistant.io") - [anotherthomas (@anotherthomas)](https://github.com/anotherthomas "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [Anthony Arnaud (@aarnaud)](https://github.com/aarnaud "2 total commits to the home-assistant organization, 2 commits to home-assistant") @@ -117,7 +111,7 @@ This page contains a list of people who have contributed in one way or another t - [bcl1713 (@bcl1713)](https://github.com/bcl1713 "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Beat (@bdurrer)](https://github.com/bdurrer "14 total commits to the home-assistant organization, 10 commits to home-assistant.io, 3 commits to home-assistant, 1 commit to home-assistant-polymer") - [Ben Bangert (@bbangert)](https://github.com/bbangert "4 total commits to the home-assistant organization, 4 commits to home-assistant") -- [Ben Lebherz (@benleb)](https://github.com/benleb "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") +- [Ben Lebherz (@benleb)](https://github.com/benleb "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Ben Nuttall (@bennuttall)](https://github.com/bennuttall "1 total commits to the home-assistant organization, 1 commit to pi-gen") - [Ben Origas (@borigas)](https://github.com/borigas "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Ben Pirt (@bjpirt)](https://github.com/bjpirt "2 total commits to the home-assistant organization, 2 commits to pi-gen") @@ -136,7 +130,8 @@ This page contains a list of people who have contributed in one way or another t - [Boced66 (@boced66)](https://github.com/boced66 "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [bonanitech (@bonanitech)](https://github.com/bonanitech "9 total commits to the home-assistant organization, 9 commits to home-assistant.io") - [boojew (@boojew)](https://github.com/boojew "7 total commits to the home-assistant organization, 7 commits to home-assistant.io") -- [Boris K (@bokub)](https://github.com/bokub "12 total commits to the home-assistant organization, 6 commits to home-assistant.io, 6 commits to home-assistant") +- [Boris K (@bokub)](https://github.com/bokub "12 total commits to the home-assistant organization, 6 commits to home-assistant, 6 commits to home-assistant.io") +- [borpin (@borpin)](https://github.com/borpin "1 total commits to the home-assistant organization, 1 commit to hassos") - [bottomquark (@bottomquark)](https://github.com/bottomquark "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Boyi C (@fanthos)](https://github.com/fanthos "23 total commits to the home-assistant organization, 17 commits to home-assistant-polymer, 6 commits to home-assistant") - [Brad Dixon (@rbdixon)](https://github.com/rbdixon "2 total commits to the home-assistant organization, 2 commits to home-assistant") @@ -154,7 +149,7 @@ This page contains a list of people who have contributed in one way or another t - [Brent Saltzman (@brent20)](https://github.com/brent20 "9 total commits to the home-assistant organization, 9 commits to home-assistant.io") - [Brian Cribbs (@cribbstechnologies)](https://github.com/cribbstechnologies "43 total commits to the home-assistant organization, 26 commits to home-assistant, 15 commits to home-assistant.io, 2 commits to home-assistant-polymer") - [Brian Hopkins (@btotharye)](https://github.com/btotharye "6 total commits to the home-assistant organization, 4 commits to home-assistant.io, 2 commits to home-assistant") -- [Brian J King (@brianjking)](https://github.com/brianjking "12 total commits to the home-assistant organization, 12 commits to home-assistant.io") +- [Brian J King (@brianjking)](https://github.com/brianjking "14 total commits to the home-assistant organization, 14 commits to home-assistant.io") - [Brian Jinwright (@bjinwright)](https://github.com/bjinwright "159 total commits to the home-assistant organization, 159 commits to warrant") - [BRUH Automation (@bruhautomation)](https://github.com/bruhautomation "3 total commits to the home-assistant organization, 3 commits to hassbian-scripts") - [Bruno Adele (@badele)](https://github.com/badele "22 total commits to the home-assistant organization, 22 commits to home-assistant") @@ -168,15 +163,16 @@ This page contains a list of people who have contributed in one way or another t - [Cameron Bulock (@cbulock)](https://github.com/cbulock "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to netdisco") - [Carlo Costanzo (@CCOSTAN)](https://github.com/CCOSTAN "99 total commits to the home-assistant organization, 91 commits to home-assistant.io, 5 commits to home-assistant, 1 commit to fabric-home-assistant, 1 commit to hassbian-scripts, 1 commit to homebridge-homeassistant") - [carlosmgr (@carlosmgr)](https://github.com/carlosmgr "6 total commits to the home-assistant organization, 6 commits to home-assistant") -- [cdce8p (@cdce8p)](https://github.com/cdce8p "143 total commits to the home-assistant organization, 84 commits to home-assistant, 41 commits to home-assistant.io, 11 commits to home-assistant-polymer, 5 commits to hass-release, 2 commits to developers.home-assistant") +- [cdce8p (@cdce8p)](https://github.com/cdce8p "147 total commits to the home-assistant organization, 85 commits to home-assistant, 42 commits to home-assistant.io, 13 commits to home-assistant-polymer, 5 commits to hass-release, 2 commits to developers.home-assistant") - [Cecron (@Cecron)](https://github.com/Cecron "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Cedric Van Goethem (@Zepheus)](https://github.com/Zepheus "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [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 "2 total commits to the home-assistant organization, 2 commits to hassio-addons") - [Cezar Sá Espinola (@cezarsa)](https://github.com/cezarsa "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [cgtobi (@cgtobi)](https://github.com/cgtobi "32 total commits to the home-assistant organization, 19 commits to home-assistant, 13 commits to home-assistant.io") +- [cgtobi (@cgtobi)](https://github.com/cgtobi "34 total commits to the home-assistant organization, 21 commits to home-assistant, 13 commits to home-assistant.io") - [chanders (@chanders)](https://github.com/chanders "2 total commits to the home-assistant organization, 2 commits to hadashboard") - [Charles Blonde (@CharlesBlonde)](https://github.com/CharlesBlonde "19 total commits to the home-assistant organization, 12 commits to home-assistant, 7 commits to home-assistant.io") -- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "26 total commits to the home-assistant organization, 14 commits to home-assistant.io, 9 commits to home-assistant, 3 commits to home-assistant-polymer") +- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "33 total commits to the home-assistant organization, 16 commits to home-assistant.io, 10 commits to home-assistant, 7 commits to home-assistant-polymer") - [Charles Spirakis (@srcLurker)](https://github.com/srcLurker "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.io") - [Chayoung You (@yous)](https://github.com/yous "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Check your git settings\! (@invalid-email-address)](https://github.com/invalid-email-address "1 total commits to the home-assistant organization, 1 commit to libcoap") @@ -203,37 +199,34 @@ This page contains a list of people who have contributed in one way or another t - [Claus F\. Strasburger (@cfstras)](https://github.com/cfstras "5 total commits to the home-assistant organization, 5 commits to pi-gen") - [cogneato (@cogneato)](https://github.com/cogneato "20 total commits to the home-assistant organization, 15 commits to home-assistant.io, 3 commits to developers.home-assistant, 2 commits to hassos") - [Colin Dunn (@colindunn)](https://github.com/colindunn "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Colin Frei (@colinfrei)](https://github.com/colinfrei "5 total commits to the home-assistant organization, 3 commits to home-assistant.io, 2 commits to home-assistant") +- [Colin Frei (@colinfrei)](https://github.com/colinfrei "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Colin O'Dell (@colinodell)](https://github.com/colinodell "33 total commits to the home-assistant organization, 18 commits to home-assistant, 15 commits to home-assistant.io") - [Colin Teubner (@netopiax)](https://github.com/netopiax "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Conrad Juhl Andersen (@cnrd)](https://github.com/cnrd "15 total commits to the home-assistant organization, 7 commits to home-assistant, 5 commits to home-assistant.io, 2 commits to home-assistant-polymer, 1 commit to developers.home-assistant") +- [Conrad Juhl Andersen (@cnrd)](https://github.com/cnrd "17 total commits to the home-assistant organization, 9 commits to home-assistant, 5 commits to home-assistant.io, 2 commits to home-assistant-polymer, 1 commit to developers.home-assistant") - [Constantine Grantcharov (@conz27)](https://github.com/conz27 "1 total commits to the home-assistant organization, 1 commit to libcoap") - [Constantine Poltyrev (@shprota)](https://github.com/shprota "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Corban Mailloux (@corbanmailloux)](https://github.com/corbanmailloux "18 total commits to the home-assistant organization, 18 commits to home-assistant.io") -- [Corey Pauley (@devspacenine)](https://github.com/devspacenine "5 total commits to the home-assistant organization, 3 commits to home-assistant.io, 2 commits to home-assistant") +- [Corey Pauley (@devspacenine)](https://github.com/devspacenine "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [corneyl (@corneyl)](https://github.com/corneyl "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Craig J\. Midwinter (@craigjmidwinter)](https://github.com/craigjmidwinter "27 total commits to the home-assistant organization, 20 commits to home-assistant, 7 commits to home-assistant.io") - [CTLS (@CTLS)](https://github.com/CTLS "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [CV (@dagobert)](https://github.com/dagobert "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [cxlwill (@cxlwill)](https://github.com/cxlwill "4 total commits to the home-assistant organization, 2 commits to hassbian-scripts, 2 commits to home-assistant-polymer") - [Dale Higgs (@dale3h)](https://github.com/dale3h "45 total commits to the home-assistant organization, 32 commits to home-assistant.io, 11 commits to home-assistant, 1 commit to hassbot, 1 commit to homebridge-homeassistant") -- [damarco (@damarco)](https://github.com/damarco "6 total commits to the home-assistant organization, 6 commits to home-assistant") +- [damarco (@damarco)](https://github.com/damarco "7 total commits to the home-assistant organization, 7 commits to home-assistant") - [Dan (@danieljkemp)](https://github.com/danieljkemp "23 total commits to the home-assistant organization, 16 commits to home-assistant, 7 commits to home-assistant.io") -- [Dan Chen (@djchen)](https://github.com/djchen "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Dan Cinnamon (@Cinntax)](https://github.com/Cinntax "19 total commits to the home-assistant organization, 16 commits to home-assistant, 3 commits to home-assistant.io") -- [Dan Klaffenbach (@klada)](https://github.com/klada "4 total commits to the home-assistant organization, 4 commits to home-assistant") +- [Dan Cinnamon (@Cinntax)](https://github.com/Cinntax "17 total commits to the home-assistant organization, 14 commits to home-assistant, 3 commits to home-assistant.io") +- [Dan Klaffenbach (@klada)](https://github.com/klada "5 total commits to the home-assistant organization, 5 commits to home-assistant") - [Dan Nixon (@DanNixon)](https://github.com/DanNixon "25 total commits to the home-assistant organization, 19 commits to home-assistant, 6 commits to home-assistant.io") - [Dan Ports (@drkp)](https://github.com/drkp "4 total commits to the home-assistant organization, 4 commits to home-assistant") -- [Dan Sarginson (@dansarginson)](https://github.com/dansarginson "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Dan Smith (@kk7ds)](https://github.com/kk7ds "84 total commits to the home-assistant organization, 68 commits to home-assistant, 14 commits to home-assistant.io, 2 commits to home-assistant-polymer") - [Dani (@danichispa)](https://github.com/danichispa "9 total commits to the home-assistant organization, 9 commits to home-assistant.io") - [Daniel Bowman (@vrih)](https://github.com/vrih "5 total commits to the home-assistant organization, 4 commits to home-assistant, 1 commit to netdisco") - [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 "310 total commits to the home-assistant organization, 196 commits to home-assistant, 111 commits to home-assistant.io, 3 commits to home-assistant-polymer") -- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "102 total commits to the home-assistant organization, 50 commits to home-assistant, 41 commits to home-assistant.io, 11 commits to hassio-addons") +- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "330 total commits to the home-assistant organization, 210 commits to home-assistant, 117 commits to home-assistant.io, 3 commits to home-assistant-polymer") +- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "107 total commits to the home-assistant organization, 54 commits to home-assistant, 42 commits to home-assistant.io, 11 commits to hassio-addons") - [Daniel Peukert (@dpeukert)](https://github.com/dpeukert "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Daniel Schaal (@schaal)](https://github.com/schaal "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Daniel Shokouhi (@dshokouhi)](https://github.com/dshokouhi "26 total commits to the home-assistant organization, 19 commits to home-assistant.io, 7 commits to home-assistant") +- [Daniel Shokouhi (@dshokouhi)](https://github.com/dshokouhi "27 total commits to the home-assistant organization, 20 commits to home-assistant.io, 7 commits to home-assistant") - [Daniel Trnka (@trnila)](https://github.com/trnila "2 total commits to the home-assistant organization, 2 commits to appdaemon") - [Daniel Watkins (@OddBloke)](https://github.com/OddBloke "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Daniel Welch (@danielwelch)](https://github.com/danielwelch "6 total commits to the home-assistant organization, 3 commits to home-assistant.io, 2 commits to homebridge-homeassistant, 1 commit to hassio-addons") @@ -243,14 +236,12 @@ This page contains a list of people who have contributed in one way or another t - [datafx (@datafx)](https://github.com/datafx "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Dave Banks (@djbanks)](https://github.com/djbanks "2 total commits to the home-assistant organization, 2 commits to appdaemon") - [Dave J (@kxtcd950)](https://github.com/kxtcd950 "3 total commits to the home-assistant organization, 3 commits to hassbian-scripts") -- [DaveSergeant (@dethpickle)](https://github.com/dethpickle "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [David (@fanaticDavid)](https://github.com/fanaticDavid "16 total commits to the home-assistant organization, 12 commits to home-assistant.io, 3 commits to home-assistant, 1 commit to home-assistant-polymer") - [David Broadfoot (@dlbroadfoot)](https://github.com/dlbroadfoot "5 total commits to the home-assistant organization, 5 commits to home-assistant") - [David De Sloovere (@DavidDeSloovere)](https://github.com/DavidDeSloovere "16 total commits to the home-assistant organization, 16 commits to home-assistant.io") - [David F\. Mulcahey (@dmulcahey)](https://github.com/dmulcahey "5 total commits to the home-assistant organization, 5 commits to home-assistant") -- [David Fiel (@dfiel)](https://github.com/dfiel "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [David Grant (@davegravy)](https://github.com/davegravy "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") -- [David McNett (@nugget)](https://github.com/nugget "10 total commits to the home-assistant organization, 5 commits to home-assistant.io, 5 commits to home-assistant") +- [David McNett (@nugget)](https://github.com/nugget "10 total commits to the home-assistant organization, 5 commits to home-assistant, 5 commits to home-assistant.io") - [David Ohayon (@ohayon)](https://github.com/ohayon "3 total commits to the home-assistant organization, 3 commits to issue-bot") - [David Steele (@davesteele)](https://github.com/davesteele "4 total commits to the home-assistant organization, 4 commits to pi-gen") - [David Straub (@DavidMStraub)](https://github.com/DavidMStraub "10 total commits to the home-assistant organization, 6 commits to home-assistant, 4 commits to home-assistant.io") @@ -262,6 +253,7 @@ This page contains a list of people who have contributed in one way or another t - [deisi (@deisi)](https://github.com/deisi "10 total commits to the home-assistant organization, 10 commits to home-assistant") - [Delio Castillo (@jangeador)](https://github.com/jangeador "2 total commits to the home-assistant organization, 2 commits to hassio-addons") - [Demid Lupin (@lupin-de-mid)](https://github.com/lupin-de-mid "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") +- [Denix (@denics)](https://github.com/denics "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Dennis Karpienski (@TheRealLink)](https://github.com/TheRealLink "22 total commits to the home-assistant organization, 15 commits to home-assistant-polymer, 6 commits to home-assistant, 1 commit to netdisco") - [Derek (@itchaboy)](https://github.com/itchaboy "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [Derek Brooks (@broox)](https://github.com/broox "39 total commits to the home-assistant organization, 30 commits to home-assistant, 9 commits to home-assistant.io") @@ -269,13 +261,13 @@ This page contains a list of people who have contributed in one way or another t - [DetroitEE (@DetroitEE)](https://github.com/DetroitEE "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [devdelay (@devdelay)](https://github.com/devdelay "16 total commits to the home-assistant organization, 7 commits to home-assistant.io, 5 commits to home-assistant, 4 commits to homebridge-homeassistant") - [Devon Peet (@dpeet)](https://github.com/dpeet "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") -- [Diogo Gomes (@dgomes)](https://github.com/dgomes "70 total commits to the home-assistant organization, 46 commits to home-assistant, 23 commits to home-assistant.io, 1 commit to developers.home-assistant") +- [Diogo Gomes (@dgomes)](https://github.com/dgomes "74 total commits to the home-assistant organization, 49 commits to home-assistant, 24 commits to home-assistant.io, 1 commit to developers.home-assistant") - [Dmitri Pribysh (@dmand)](https://github.com/dmand "1 total commits to the home-assistant organization, 1 commit to hassos") - [Domantas (@Dohxis)](https://github.com/Dohxis "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Dougal Matthews (@d0ugal)](https://github.com/d0ugal "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [dramamoose (@dramamoose)](https://github.com/dramamoose "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") - [DrewSK (@dzsquared)](https://github.com/dzsquared "8 total commits to the home-assistant organization, 8 commits to home-assistant.io") -- [DubhAd (@DubhAd)](https://github.com/DubhAd "395 total commits to the home-assistant organization, 392 commits to home-assistant.io, 2 commits to hassos, 1 commit to developers.home-assistant") +- [DubhAd (@DubhAd)](https://github.com/DubhAd "419 total commits to the home-assistant organization, 415 commits to home-assistant.io, 2 commits to hassos, 2 commits to developers.home-assistant") - [Duoxilian (@Duoxilian)](https://github.com/Duoxilian "11 total commits to the home-assistant organization, 6 commits to home-assistant.io, 5 commits to home-assistant") - [ebpetway (@ebpetway)](https://github.com/ebpetway "55 total commits to the home-assistant organization, 55 commits to warrant") - [Egor Tsinko (@etsinko)](https://github.com/etsinko "12 total commits to the home-assistant organization, 9 commits to home-assistant, 3 commits to home-assistant.io") @@ -293,10 +285,10 @@ This page contains a list of people who have contributed in one way or another t - [Eu (@covrig)](https://github.com/covrig "2 total commits to the home-assistant organization, 2 commits to home-assistant-polymer") - [Eugenio Panadero (@azogue)](https://github.com/azogue "77 total commits to the home-assistant organization, 46 commits to home-assistant, 25 commits to home-assistant.io, 3 commits to homebridge-homeassistant, 3 commits to home-assistant-polymer") - [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 "4889 total commits to the home-assistant organization, 3055 commits to home-assistant.io, 1697 commits to home-assistant, 33 commits to home-assistant-assets, 32 commits to home-assistant-notebooks, 15 commits to developers.home-assistant, 11 commits to home-assistant-polymer, 11 commits to hassio-build, 10 commits to netdisco, 7 commits to hassos, 6 commits to hassio-addons, 4 commits to hassio, 3 commits to hass-release, 2 commits to home-assistant-iOS, 1 commit to example-custom-config, 1 commit to ui-schema, 1 commit to home-assistant-js-websocket") +- [Fabian Affolter (@fabaff)](https://github.com/fabaff "4972 total commits to the home-assistant organization, 3110 commits to home-assistant.io, 1723 commits to home-assistant, 33 commits to home-assistant-assets, 32 commits to home-assistant-notebooks, 15 commits to developers.home-assistant, 11 commits to home-assistant-polymer, 11 commits to hassio-build, 10 commits to netdisco, 7 commits to hassos, 6 commits to hassio, 6 commits to hassio-addons, 3 commits to hass-release, 2 commits to home-assistant-iOS, 1 commit to home-assistant-js-websocket, 1 commit to example-custom-config, 1 commit to ui-schema") - [Fabian Fischer (@nodomain)](https://github.com/nodomain "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [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 "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") +- [Fabien Piuzzi (@reefab)](https://github.com/reefab "4 total commits to the home-assistant organization, 3 commits to home-assistant, 1 commit to home-assistant-polymer") - [Fabrizio Furnari (@fabfurnari)](https://github.com/fabfurnari "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [fakezeta (@fakezeta)](https://github.com/fakezeta "7 total commits to the home-assistant organization, 7 commits to home-assistant") - [Felix Krause (@KrauseFx)](https://github.com/KrauseFx "27 total commits to the home-assistant organization, 27 commits to issue-bot") @@ -308,22 +300,23 @@ This page contains a list of people who have contributed in one way or another t - [florianj1 (@florianj1)](https://github.com/florianj1 "1 total commits to the home-assistant organization, 1 commit to hassio") - [florincosta (@florincosta)](https://github.com/florincosta "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.io") - [Fonta (@f0nt4)](https://github.com/f0nt4 "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") -- [Franck Nijhof (@frenck)](https://github.com/frenck "44 total commits to the home-assistant organization, 31 commits to home-assistant.io, 6 commits to hassio, 2 commits to hassio-cli, 2 commits to hassio-addons, 2 commits to home-assistant-polymer, 1 commit to appdaemon") +- [Franck Nijhof (@frenck)](https://github.com/frenck "52 total commits to the home-assistant organization, 31 commits to home-assistant.io, 10 commits to hassio, 3 commits to hassio-addons, 3 commits to home-assistant, 2 commits to hassio-cli, 2 commits to home-assistant-polymer, 1 commit to appdaemon") - [Frank (@syphernl)](https://github.com/syphernl "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Frantz (@rofrantz)](https://github.com/rofrantz "17 total commits to the home-assistant organization, 9 commits to home-assistant, 4 commits to home-assistant.io, 3 commits to netdisco, 1 commit to home-assistant-js-websocket") - [Frederic Hemberger (@fhemberger)](https://github.com/fhemberger "93 total commits to the home-assistant organization, 93 commits to home-assistant.io") - [Frederik Bolding (@FrederikBolding)](https://github.com/FrederikBolding "4 total commits to the home-assistant organization, 4 commits to home-assistant") -- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "224 total commits to the home-assistant organization, 110 commits to hassbian-scripts, 73 commits to home-assistant.io, 36 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer") +- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "226 total commits to the home-assistant organization, 112 commits to hassbian-scripts, 73 commits to home-assistant.io, 36 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer") - [freol35241 (@freol35241)](https://github.com/freol35241 "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [fuga2136 (@fuga2136)](https://github.com/fuga2136 "13 total commits to the home-assistant organization, 13 commits to home-assistant.io") - [Gabor SZOLLOSI (@szogi)](https://github.com/szogi "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Gabriel Oliveira (@gabrielboliveira)](https://github.com/gabrielboliveira "2 total commits to the home-assistant organization, 1 commit to hassos, 1 commit to hassio-addons") +- [geekofweek (@geekofweek)](https://github.com/geekofweek "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Geoff Norton (@kangaroo)](https://github.com/kangaroo "14 total commits to the home-assistant organization, 14 commits to home-assistant") - [George\.M (@nodinosaur)](https://github.com/nodinosaur "6 total commits to the home-assistant organization, 6 commits to home-assistant.io") - [Georgi Kirichkov (@kirichkov)](https://github.com/kirichkov "17 total commits to the home-assistant organization, 11 commits to home-assistant.io, 5 commits to home-assistant, 1 commit to appdaemon") - [Georgi Yanev (@jumpalottahigh)](https://github.com/jumpalottahigh "6 total commits to the home-assistant organization, 4 commits to home-assistant.io, 2 commits to home-assistant-polymer") - [Georgii Staroselskii (@staroselskii)](https://github.com/staroselskii "1 total commits to the home-assistant organization, 1 commit to pi-gen") -- [Gerard (@gerard33)](https://github.com/gerard33 "12 total commits to the home-assistant organization, 6 commits to home-assistant.io, 6 commits to home-assistant") +- [Gerard (@gerard33)](https://github.com/gerard33 "12 total commits to the home-assistant organization, 6 commits to home-assistant, 6 commits to home-assistant.io") - [Gergely Imreh (@imrehg)](https://github.com/imrehg "16 total commits to the home-assistant organization, 11 commits to home-assistant, 5 commits to home-assistant.io") - [Gianluca Barbaro (@MrMep)](https://github.com/MrMep "24 total commits to the home-assistant organization, 16 commits to home-assistant, 8 commits to home-assistant.io") - [Giel Janssens (@gieljnssns)](https://github.com/gieljnssns "5 total commits to the home-assistant organization, 5 commits to home-assistant") @@ -331,14 +324,14 @@ This page contains a list of people who have contributed in one way or another t - [GitBook Bot (@gitbook-bot)](https://github.com/gitbook-bot "1 total commits to the home-assistant organization, 1 commit to developers.home-assistant") - [githubbuh (@githubbuh)](https://github.com/githubbuh "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [gitmopp (@gitmopp)](https://github.com/gitmopp "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Giuseppe (@glpatcern)](https://github.com/glpatcern "4 total commits to the home-assistant organization, 4 commits to home-assistant") +- [Giuseppe (@glpatcern)](https://github.com/glpatcern "5 total commits to the home-assistant organization, 5 commits to home-assistant") - [Glenn Waters (@gwww)](https://github.com/gwww "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [GMFalka (@GMFalka)](https://github.com/GMFalka "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Gopal Kildoliya (@gopalkildoliya)](https://github.com/gopalkildoliya "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Grant McConnaughey (@grantmcconnaughey)](https://github.com/grantmcconnaughey "8 total commits to the home-assistant organization, 8 commits to warrant") - [GreenTurtwig (@GreenTurtwig)](https://github.com/GreenTurtwig "80 total commits to the home-assistant organization, 75 commits to home-assistant.io, 5 commits to home-assistant") - [Greg Dowling (@pavoni)](https://github.com/pavoni "209 total commits to the home-assistant organization, 183 commits to home-assistant, 25 commits to home-assistant.io, 1 commit to netdisco") -- [Greg Laabs (@OverloadUT)](https://github.com/OverloadUT "20 total commits to the home-assistant organization, 16 commits to home-assistant, 4 commits to home-assistant.io") +- [Greg Laabs (@OverloadUT)](https://github.com/OverloadUT "22 total commits to the home-assistant organization, 18 commits to home-assistant, 4 commits to home-assistant.io") - [Greg MacLellan (@gregmac)](https://github.com/gregmac "1 total commits to the home-assistant organization, 1 commit to pi-gen") - [Greg Stevenson (@gstevenson)](https://github.com/gstevenson "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Gregory Benner (@Klathmon)](https://github.com/Klathmon "3 total commits to the home-assistant organization, 3 commits to home-assistant") @@ -364,7 +357,7 @@ This page contains a list of people who have contributed in one way or another t - [Hillary Fraley (@hillaryfraley)](https://github.com/hillaryfraley "12 total commits to the home-assistant organization, 12 commits to home-assistant.io") - [Hmmbob (@hmmbob)](https://github.com/hmmbob "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [honcheng (@honcheng)](https://github.com/honcheng "2 total commits to the home-assistant organization, 2 commits to homebridge-homeassistant") -- [huangyupeng (@huangyupeng)](https://github.com/huangyupeng "14 total commits to the home-assistant organization, 7 commits to home-assistant.io, 7 commits to home-assistant") +- [huangyupeng (@huangyupeng)](https://github.com/huangyupeng "14 total commits to the home-assistant organization, 7 commits to home-assistant, 7 commits to home-assistant.io") - [Hugo Dupras (@jabesq)](https://github.com/jabesq "29 total commits to the home-assistant organization, 21 commits to home-assistant, 8 commits to home-assistant.io") - [Hugo Gresse (@HugoGresse)](https://github.com/HugoGresse "8 total commits to the home-assistant organization, 8 commits to home-assistant.io") - [Hugo Hromic (@hhromic)](https://github.com/hhromic "4 total commits to the home-assistant organization, 4 commits to pi-gen") @@ -375,7 +368,8 @@ This page contains a list of people who have contributed in one way or another t - [ianj001 (@ianj001)](https://github.com/ianj001 "7 total commits to the home-assistant organization, 7 commits to home-assistant.io") - [icovada (@icovada)](https://github.com/icovada "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.io") - [Igor Shults (@ishults)](https://github.com/ishults "12 total commits to the home-assistant organization, 6 commits to home-assistant, 5 commits to home-assistant.io, 1 commit to home-assistant-polymer") -- [Ioan Loosley (@ioangogo)](https://github.com/ioangogo "11 total commits to the home-assistant organization, 11 commits to home-assistant.io") +- [Ioan Loosley (@ioangogo)](https://github.com/ioangogo "15 total commits to the home-assistant organization, 12 commits to home-assistant.io, 3 commits to home-assistant") +- [Isabella Gross Alström (@isabellaalstrom)](https://github.com/isabellaalstrom "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Issac Kelly (@issackelly)](https://github.com/issackelly "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Jaak Laineste (@jaakla)](https://github.com/jaakla "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Jacen (@jacen92)](https://github.com/jacen92 "2 total commits to the home-assistant organization, 2 commits to pi-gen") @@ -384,7 +378,7 @@ This page contains a list of people who have contributed in one way or another t - [Jack Minardi (@jminardi)](https://github.com/jminardi "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [Jacob Mansfield (@cyberjacob)](https://github.com/cyberjacob "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Jacob Siverskog (@jsiverskog)](https://github.com/jsiverskog "1 total commits to the home-assistant organization, 1 commit to pi-gen") -- [Jacob Tomlinson (@jacobtomlinson)](https://github.com/jacobtomlinson "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") +- [Jacob Tomlinson (@jacobtomlinson)](https://github.com/jacobtomlinson "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [Jaimyn Mayer (@jabelone)](https://github.com/jabelone "1 total commits to the home-assistant organization, 1 commit to hassbian-scripts") - [Jakub Bittner (@rexcze)](https://github.com/rexcze "2 total commits to the home-assistant organization, 2 commits to home-assistant-polymer") - [James Cole (@jamespcole)](https://github.com/jamespcole "94 total commits to the home-assistant organization, 93 commits to home-assistant, 1 commit to home-assistant-js") @@ -399,7 +393,7 @@ This page contains a list of people who have contributed in one way or another t - [Janne Grunau (@jannau)](https://github.com/jannau "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Jason Carter (@JasonCarter80)](https://github.com/JasonCarter80 "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") - [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 "92 total commits to the home-assistant organization, 62 commits to home-assistant, 12 commits to home-assistant-polymer, 11 commits to home-assistant.io, 6 commits to developers.home-assistant, 1 commit to home-assistant-js-websocket") +- [Jason Hu (@awarecan)](https://github.com/awarecan "136 total commits to the home-assistant organization, 93 commits to home-assistant, 17 commits to home-assistant-polymer, 15 commits to home-assistant.io, 9 commits to developers.home-assistant, 1 commit to home-assistant-js-websocket, 1 commit to netdisco") - [Jason Hunter (@hunterjm)](https://github.com/hunterjm "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Jay Stevens (@Jay2645)](https://github.com/Jay2645 "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [JAYMAN-ATX (@JAYMAN-ATX)](https://github.com/JAYMAN-ATX "2 total commits to the home-assistant organization, 2 commits to homebridge-homeassistant") @@ -409,8 +403,8 @@ This page contains a list of people who have contributed in one way or another t - [Jeff Schroeder (@SEJeff)](https://github.com/SEJeff "17 total commits to the home-assistant organization, 17 commits to home-assistant") - [Jeff Wilson (@jawilson)](https://github.com/jawilson "25 total commits to the home-assistant organization, 19 commits to home-assistant, 6 commits to home-assistant.io") - [Jens (@jhoepken)](https://github.com/jhoepken "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Jens Østergaard Nielsen (@dingusdk)](https://github.com/dingusdk "8 total commits to the home-assistant organization, 4 commits to home-assistant.io, 4 commits to home-assistant") -- [Jerad Meisner (@jeradM)](https://github.com/jeradM "52 total commits to the home-assistant organization, 30 commits to home-assistant-polymer, 11 commits to home-assistant.io, 11 commits to home-assistant") +- [Jens Østergaard Nielsen (@dingusdk)](https://github.com/dingusdk "8 total commits to the home-assistant organization, 4 commits to home-assistant, 4 commits to home-assistant.io") +- [Jerad Meisner (@jeradM)](https://github.com/jeradM "57 total commits to the home-assistant organization, 33 commits to home-assistant-polymer, 12 commits to home-assistant.io, 12 commits to home-assistant") - [Jeremiah Wuenschel (@jer)](https://github.com/jer "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Jeremy Williams (@jwillaz)](https://github.com/jwillaz "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [jeremysv (@jeremysv)](https://github.com/jeremysv "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") @@ -419,12 +413,12 @@ This page contains a list of people who have contributed in one way or another t - [Jerry Workman (@JerryWorkman)](https://github.com/JerryWorkman "9 total commits to the home-assistant organization, 9 commits to home-assistant.io") - [Jesse Hills (@jesserockz)](https://github.com/jesserockz "9 total commits to the home-assistant organization, 9 commits to home-assistant") - [Jesse Newland (@jnewland)](https://github.com/jnewland "16 total commits to the home-assistant organization, 13 commits to home-assistant, 3 commits to hubot-home-assistant") -- [JesseWebDotCom (@JesseWebDotCom)](https://github.com/JesseWebDotCom "16 total commits to the home-assistant organization, 8 commits to home-assistant.io, 8 commits to home-assistant") +- [JesseWebDotCom (@JesseWebDotCom)](https://github.com/JesseWebDotCom "16 total commits to the home-assistant organization, 8 commits to home-assistant, 8 commits to home-assistant.io") - [jgrieger1 (@jgrieger1)](https://github.com/jgrieger1 "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [jiafengwang (@jiafengwang)](https://github.com/jiafengwang "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [jimbob1001 (@jimbob1001)](https://github.com/jimbob1001 "4 total commits to the home-assistant organization, 4 commits 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 Sørensen (@ludeeus)](https://github.com/ludeeus "123 total commits to the home-assistant organization, 98 commits to hassbian-scripts, 22 commits to home-assistant.io, 3 commits to home-assistant") +- [Joakim Sørensen (@ludeeus)](https://github.com/ludeeus "129 total commits to the home-assistant organization, 104 commits to hassbian-scripts, 22 commits to home-assistant.io, 3 commits to home-assistant") - [jodur (@jodur)](https://github.com/jodur "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Joe Lu (@snjoetw)](https://github.com/snjoetw "25 total commits to the home-assistant organization, 19 commits to home-assistant, 5 commits to home-assistant.io, 1 commit to appdaemon") - [Joe McMonagle (@joemcmonagle)](https://github.com/joemcmonagle "13 total commits to the home-assistant organization, 13 commits to home-assistant.io") @@ -435,8 +429,9 @@ This page contains a list of people who have contributed in one way or another t - [Johan van der Kuijl (@Rubyan)](https://github.com/Rubyan "4 total commits to the home-assistant organization, 3 commits to home-assistant.io, 1 commit to appdaemon") - [Johann Kellerman (@kellerza)](https://github.com/kellerza "181 total commits to the home-assistant organization, 148 commits to home-assistant, 33 commits to home-assistant.io") - [Johannes K\. (@roadrash2108)](https://github.com/roadrash2108 "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") +- [Johannes Truschnigg (@jtru)](https://github.com/jtru "1 total commits to the home-assistant organization, 1 commit to hassos") - [John (@J-C-B)](https://github.com/J-C-B "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") -- [John Arild Berentsen (@turbokongen)](https://github.com/turbokongen "218 total commits to the home-assistant organization, 156 commits to home-assistant, 40 commits to home-assistant.io, 22 commits to home-assistant-polymer") +- [John Arild Berentsen (@turbokongen)](https://github.com/turbokongen "221 total commits to the home-assistant organization, 156 commits to home-assistant, 42 commits to home-assistant.io, 23 commits to home-assistant-polymer") - [John Lindley (@jwl17330536)](https://github.com/jwl17330536 "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [John Mihalic (@mezz64)](https://github.com/mezz64 "51 total commits to the home-assistant organization, 37 commits to home-assistant, 12 commits to home-assistant.io, 1 commit to hadashboard, 1 commit to home-assistant-polymer") - [Johnny Chadda (@joch)](https://github.com/joch "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") @@ -461,7 +456,7 @@ This page contains a list of people who have contributed in one way or another t - [JudgeDredd (@JudgeDreddKLC)](https://github.com/JudgeDreddKLC "10 total commits to the home-assistant organization, 10 commits to home-assistant.io") - [Juggels (@Juggels)](https://github.com/Juggels "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.io") - [Julian Kaffke (@jaykay)](https://github.com/jaykay "1 total commits to the home-assistant organization, 1 commit to hassio-addons") -- [Julian Kahnert (@JulianKahnert)](https://github.com/JulianKahnert "6 total commits to the home-assistant organization, 3 commits to home-assistant.io, 3 commits to home-assistant") +- [Julian Kahnert (@JulianKahnert)](https://github.com/JulianKahnert "7 total commits to the home-assistant organization, 4 commits to home-assistant.io, 3 commits to home-assistant") - [Julius Mittenzwei (@Julius2342)](https://github.com/Julius2342 "31 total commits to the home-assistant organization, 24 commits to home-assistant, 7 commits to home-assistant.io") - [jumpkick (@jumpkick)](https://github.com/jumpkick "15 total commits to the home-assistant organization, 12 commits to home-assistant, 3 commits to home-assistant.io") - [Junian Triajianto (@junian)](https://github.com/junian "1 total commits to the home-assistant organization, 1 commit to pi-gen") @@ -469,21 +464,23 @@ This page contains a list of people who have contributed in one way or another t - [Justin Hayes (@GussyH)](https://github.com/GussyH "8 total commits to the home-assistant organization, 7 commits to hadashboard, 1 commit to appdaemon") - [Justin Weberg (@justweb1)](https://github.com/justweb1 "26 total commits to the home-assistant organization, 13 commits to home-assistant-polymer, 7 commits to hassbot, 4 commits to home-assistant, 1 commit to home-assistant-js, 1 commit to hassio") - [Justyn Shull (@justyns)](https://github.com/justyns "5 total commits to the home-assistant organization, 5 commits to home-assistant") +- [Jérémie Klein (@grm)](https://github.com/grm "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Karen Goode (@kfgoode)](https://github.com/kfgoode "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [karlkar (@karlkar)](https://github.com/karlkar "15 total commits to the home-assistant organization, 10 commits to home-assistant, 5 commits to home-assistant.io") -- [kbickar (@kbickar)](https://github.com/kbickar "3 total commits to the home-assistant organization, 3 commits to home-assistant") +- [kbickar (@kbickar)](https://github.com/kbickar "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Keaton Taylor (@keatontaylor)](https://github.com/keatontaylor "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") - [Ken Bannister (@kb2ma)](https://github.com/kb2ma "1 total commits to the home-assistant organization, 1 commit to libcoap") -- [Ken Davidson (@kwdavidson)](https://github.com/kwdavidson "14 total commits to the home-assistant organization, 12 commits to home-assistant.io, 2 commits to appdaemon") +- [Ken Davidson (@kwdavidson)](https://github.com/kwdavidson "15 total commits to the home-assistant organization, 13 commits to home-assistant.io, 2 commits to appdaemon") - [kennedyshead (@kennedyshead)](https://github.com/kennedyshead "10 total commits to the home-assistant organization, 10 commits to home-assistant") +- [Kevin Eifinger (@eifinger)](https://github.com/eifinger "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "19 total commits to the home-assistant organization, 11 commits to home-assistant, 8 commits to home-assistant.io") - [Kevin Gisi (@gisikw)](https://github.com/gisikw "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [Kevin Gottsman (@gottsman)](https://github.com/gottsman "8 total commits to the home-assistant organization, 8 commits to home-assistant.io") -- [Kevin Siml (@appzer)](https://github.com/appzer "4 total commits to the home-assistant organization, 4 commits to home-assistant") +- [Kevin Siml (@appzer)](https://github.com/appzer "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") - [Keyasha Brothern (@KMBrothern)](https://github.com/KMBrothern "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [kfcook (@kfcook)](https://github.com/kfcook "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [kireyeu (@kireyeu)](https://github.com/kireyeu "4 total commits to the home-assistant organization, 4 commits to home-assistant-notebooks") -- [Klaas Hoekema (@KlaasH)](https://github.com/KlaasH "12 total commits to the home-assistant organization, 5 commits to home-assistant.io, 5 commits to home-assistant, 2 commits to home-assistant-polymer") +- [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, 2 commits to home-assistant-polymer") - [Klaus (@k-laus)](https://github.com/k-laus "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [koolsb (@koolsb)](https://github.com/koolsb "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Kory Prince (@korylprince)](https://github.com/korylprince "4 total commits to the home-assistant organization, 4 commits to home-assistant-polymer") @@ -497,7 +494,7 @@ This page contains a list of people who have contributed in one way or another t - [Lennart Bernhardt (@LennyPenny)](https://github.com/LennyPenny "1 total commits to the home-assistant organization, 1 commit to hassio-build") - [Leon99 (@Leon99)](https://github.com/Leon99 "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Leonardo Saraiva (@vyper)](https://github.com/vyper "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Lev Aronsky (@aronsky)](https://github.com/aronsky "15 total commits to the home-assistant organization, 12 commits to home-assistant, 3 commits to home-assistant.io") +- [Lev Aronsky (@aronsky)](https://github.com/aronsky "16 total commits to the home-assistant organization, 13 commits to home-assistant, 3 commits to home-assistant.io") - [Lewis Juggins (@lwis)](https://github.com/lwis "66 total commits to the home-assistant organization, 53 commits to home-assistant, 12 commits to home-assistant.io, 1 commit to home-assistant-polymer") - [lichtteil (@lichtteil)](https://github.com/lichtteil "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Lindsay Ward (@lindsaymarkward)](https://github.com/lindsaymarkward "18 total commits to the home-assistant organization, 13 commits to home-assistant.io, 5 commits to home-assistant") @@ -517,20 +514,20 @@ This page contains a list of people who have contributed in one way or another t - [Luke Armstrong (@lukearmstrong)](https://github.com/lukearmstrong "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [LvivEchoes (@LvivEchoes)](https://github.com/LvivEchoes "8 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io, 1 commit to home-assistant-polymer") - [Maarten Groeneweg (@lazytesting)](https://github.com/lazytesting "1 total commits to the home-assistant organization, 1 commit to hassio-addons") -- [Maciej Bieniek (@bieniu)](https://github.com/bieniu "5 total commits to the home-assistant organization, 4 commits to home-assistant, 1 commit to home-assistant-polymer") +- [Maciej Bieniek (@bieniu)](https://github.com/bieniu "7 total commits to the home-assistant organization, 6 commits to home-assistant, 1 commit to home-assistant-polymer") - [Maciej Sokołowski (@matemaciek)](https://github.com/matemaciek "5 total commits to the home-assistant organization, 4 commits to home-assistant, 1 commit to hassio-build") - [Maciej Wasilak (@mwasilak)](https://github.com/mwasilak "1 total commits to the home-assistant organization, 1 commit to libcoap") - [Magnus Ihse Bursie (@magicus)](https://github.com/magicus "16 total commits to the home-assistant organization, 9 commits to home-assistant, 4 commits to netdisco, 3 commits to home-assistant.io") - [Magnus Lyckå (@magnus-lycka)](https://github.com/magnus-lycka "1 total commits to the home-assistant organization, 1 commit to netdisco") - [MagnusKnutas (@MagnusKnutas)](https://github.com/MagnusKnutas "29 total commits to the home-assistant organization, 29 commits to home-assistant") - [Mal Curtis (@snikch)](https://github.com/snikch "3 total commits to the home-assistant organization, 3 commits to home-assistant") -- [Malte Franken (@exxamalte)](https://github.com/exxamalte "11 total commits to the home-assistant organization, 6 commits to home-assistant, 3 commits to home-assistant.io, 1 commit to developers.home-assistant, 1 commit to home-assistant-polymer") +- [Malte Franken (@exxamalte)](https://github.com/exxamalte "16 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.io, 1 commit to developers.home-assistant, 1 commit to home-assistant-polymer") - [Marc Egli (@frog32)](https://github.com/frog32 "12 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.io, 1 commit to hassio-addons-example") -- [Marc Forth (@mf-social)](https://github.com/mf-social "27 total commits to the home-assistant organization, 26 commits to home-assistant.io, 1 commit to fabric-home-assistant") -- [Marc Khouri (@ubnt-marc-khouri)](https://github.com/ubnt-marc-khouri "4 total commits to the home-assistant organization, 2 commits to home-assistant-polymer, 1 commit to developers.home-assistant, 1 commit to hassio-build") +- [Marc Forth (@mf-social)](https://github.com/mf-social "28 total commits to the home-assistant organization, 27 commits to home-assistant.io, 1 commit to fabric-home-assistant") +- [Marc Khouri (@ubnt-marc-khouri)](https://github.com/ubnt-marc-khouri "4 total commits to the home-assistant organization, 2 commits to home-assistant-polymer, 1 commit to hassio-build, 1 commit to developers.home-assistant") - [Marc Pabst (@marcpabst)](https://github.com/marcpabst "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Marc Plano\-Lesay (@Kernald)](https://github.com/Kernald "10 total commits to the home-assistant organization, 10 commits to home-assistant.io") -- [Marcel Hoppe (@hobbypunk90)](https://github.com/hobbypunk90 "3 total commits to the home-assistant organization, 3 commits to home-assistant") +- [Marcel Hoppe (@hobbypunk90)](https://github.com/hobbypunk90 "12 total commits to the home-assistant organization, 6 commits to home-assistant.io, 6 commits to home-assistant") - [Marcel030nl (@Marcel030nl)](https://github.com/Marcel030nl "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "159 total commits to the home-assistant organization, 89 commits to home-assistant, 67 commits to home-assistant.io, 1 commit to home-assistant-assets, 1 commit to hassio-build, 1 commit to home-assistant-polymer") - [Marcin Domański (@kabturek)](https://github.com/kabturek "2 total commits to the home-assistant organization, 2 commits to appdaemon") @@ -553,24 +550,24 @@ This page contains a list of people who have contributed in one way or another t - [Martin Berg (@mbrrg)](https://github.com/mbrrg "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") - [Martin Eberhardt (@DarkFox)](https://github.com/DarkFox "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [Martin Hjelmare (@MartinHjelmare)](https://github.com/MartinHjelmare "179 total commits to the home-assistant organization, 144 commits to home-assistant, 30 commits to home-assistant.io, 5 commits to developers.home-assistant") -- [Martin Rowan (@shortbloke)](https://github.com/shortbloke "6 total commits to the home-assistant organization, 3 commits to home-assistant.io, 3 commits to home-assistant") +- [Martin Rowan (@shortbloke)](https://github.com/shortbloke "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.io") - [Martin Weinelt (@mweinelt)](https://github.com/mweinelt "17 total commits to the home-assistant organization, 9 commits to home-assistant, 7 commits to home-assistant.io, 1 commit to home-assistant-polymer") - [Martokk (@martokk)](https://github.com/martokk "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Mathew Peterson (@mathewpeterson)](https://github.com/mathewpeterson "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant") - [Matt N\. (@mnoorenberghe)](https://github.com/mnoorenberghe "54 total commits to the home-assistant organization, 25 commits to home-assistant-iOS, 17 commits to home-assistant.io, 9 commits to home-assistant, 2 commits to home-assistant-polymer, 1 commit to homebridge-homeassistant") - [Matt Rogers (@rogersmj)](https://github.com/rogersmj "20 total commits to the home-assistant organization, 20 commits to hadashboard") -- [Matt Schmitt (@schmittx)](https://github.com/schmittx "88 total commits to the home-assistant organization, 52 commits to homebridge-homeassistant, 19 commits to home-assistant, 12 commits to home-assistant.io, 3 commits to home-assistant-polymer, 2 commits to developers.home-assistant") +- [Matt Schmitt (@schmittx)](https://github.com/schmittx "90 total commits to the home-assistant organization, 52 commits to homebridge-homeassistant, 21 commits to home-assistant, 12 commits to home-assistant.io, 3 commits to home-assistant-polymer, 2 commits to developers.home-assistant") - [Matt Snyder (@oblogic7)](https://github.com/oblogic7 "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") +- [Matt White (@mw-white)](https://github.com/mw-white "10 total commits to the home-assistant organization, 5 commits to home-assistant, 5 commits to home-assistant.io") - [Matt White (@matt-FFFFFF)](https://github.com/matt-FFFFFF "1 total commits to the home-assistant organization, 1 commit to hassio-addons") -- [Matt White (@mw-white)](https://github.com/mw-white "10 total commits to the home-assistant organization, 5 commits to home-assistant.io, 5 commits to home-assistant") - [Matteo Lampugnani (@t30)](https://github.com/t30 "7 total commits to the home-assistant organization, 7 commits to home-assistant.io") - [Matthew Donoughe (@mdonoughe)](https://github.com/mdonoughe "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Matthew Garrett (@mjg59)](https://github.com/mjg59 "30 total commits to the home-assistant organization, 22 commits to home-assistant, 7 commits to home-assistant.io, 1 commit to netdisco") - [Matthew Rollings (@stealthcopter)](https://github.com/stealthcopter "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [Matthew Treinish (@mtreinish)](https://github.com/mtreinish "24 total commits to the home-assistant organization, 15 commits to home-assistant, 9 commits to home-assistant.io") - [Matthias Dötsch (@brainexe)](https://github.com/brainexe "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Matthias Urlichs (@smurfix)](https://github.com/smurfix "3 total commits to the home-assistant organization, 3 commits to appdaemon") -- [Mattias Welponer (@mxworm)](https://github.com/mxworm "22 total commits to the home-assistant organization, 13 commits to home-assistant, 8 commits to home-assistant.io, 1 commit to home-assistant-polymer") +- [Matthias Urlichs (@smurfix)](https://github.com/smurfix "6 total commits to the home-assistant organization, 3 commits to appdaemon, 3 commits to home-assistant") +- [Mattias Welponer (@mxworm)](https://github.com/mxworm "24 total commits to the home-assistant organization, 14 commits to home-assistant, 9 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, 3 commits to home-assistant.io") - [Max Mudde (@makzdot)](https://github.com/makzdot "1 total commits to the home-assistant organization, 1 commit to developers.home-assistant") - [Max Prokhorov (@mcspr)](https://github.com/mcspr "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") @@ -619,9 +616,10 @@ This page contains a list of people who have contributed in one way or another t - [mountainsandcode (@mountainsandcode)](https://github.com/mountainsandcode "9 total commits to the home-assistant organization, 6 commits to home-assistant.io, 3 commits to home-assistant") - [mueslo (@mueslo)](https://github.com/mueslo "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") - [mukundv (@mukundv)](https://github.com/mukundv "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") +- [Myles Eftos (@madpilot)](https://github.com/madpilot "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Mārtiņš Grunskis (@grunskis)](https://github.com/grunskis "1 total commits to the home-assistant organization, 1 commit to netdisco") - [Nash Kaminski (@nkaminski)](https://github.com/nkaminski "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Nate Clark (@heythisisnate)](https://github.com/heythisisnate "9 total commits to the home-assistant organization, 6 commits to home-assistant, 3 commits to home-assistant.io") +- [Nate Clark (@heythisisnate)](https://github.com/heythisisnate "15 total commits to the home-assistant organization, 10 commits to home-assistant, 5 commits to home-assistant.io") - [Nathan Flynn (@eperdeme)](https://github.com/eperdeme "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [Nathan Henrie (@n8henrie)](https://github.com/n8henrie "22 total commits to the home-assistant organization, 10 commits to home-assistant, 8 commits to home-assistant.io, 2 commits to homebridge-homeassistant, 1 commit to appdaemon, 1 commit to home-assistant-polymer") - [Nathan Knotts (@nknotts)](https://github.com/nknotts "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") @@ -655,16 +653,17 @@ This page contains a list of people who have contributed in one way or another t - [Oliver van Porten (@mcdeck)](https://github.com/mcdeck "10 total commits to the home-assistant organization, 10 commits to home-assistant") - [Oncleben31 (@oncleben31)](https://github.com/oncleben31 "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Open Home Automation (@open-homeautomation)](https://github.com/open-homeautomation "41 total commits to the home-assistant organization, 29 commits to home-assistant, 12 commits to home-assistant.io") +- [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 "70 total commits to the home-assistant organization, 54 commits to home-assistant, 13 commits to home-assistant.io, 3 commits to home-assistant-polymer") - [oznu (@oznu)](https://github.com/oznu "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant") - [Parker Moore (@parkr)](https://github.com/parkr "60 total commits to the home-assistant organization, 60 commits to home-assistant.io") - [pascal (@passie)](https://github.com/passie "4 total commits to the home-assistant organization, 3 commits to home-assistant, 1 commit to home-assistant-polymer") - [Pascal Bach (@bachp)](https://github.com/bachp "10 total commits to the home-assistant organization, 9 commits to home-assistant, 1 commit to netdisco") -- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "3696 total commits to the home-assistant organization, 1303 commits to hassio, 675 commits to hassos, 475 commits to home-assistant, 465 commits to hassio-build, 369 commits to hassio-addons, 328 commits to home-assistant.io, 29 commits to hassio-homeassistant, 17 commits to hassio-addons-example, 13 commits to developers.home-assistant, 12 commits to hassio-cli, 7 commits to hassio-base, 1 commit to netdisco, 1 commit to home-assistant-polymer, 1 commit to home-assistant-js-websocket") +- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "3731 total commits to the home-assistant organization, 1314 commits to hassio, 676 commits to hassos, 479 commits to home-assistant, 465 commits to hassio-build, 371 commits to hassio-addons, 332 commits to home-assistant.io, 34 commits to hassio-homeassistant, 20 commits to developers.home-assistant, 17 commits to hassio-addons-example, 12 commits to hassio-cli, 7 commits to hassio-base, 2 commits to home-assistant-polymer, 1 commit to netdisco, 1 commit to home-assistant-js-websocket") - [Pat Thoyts (@patthoyts)](https://github.com/patthoyts "2 total commits to the home-assistant organization, 2 commits to netdisco") - [Patrick Aikens (@duckpuppy)](https://github.com/duckpuppy "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Patrick Easters (@patrickeasters)](https://github.com/patrickeasters "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") -- [Paul Annekov (@PaulAnnekov)](https://github.com/PaulAnnekov "4 total commits to the home-assistant organization, 4 commits to home-assistant") +- [Paul Annekov (@PaulAnnekov)](https://github.com/PaulAnnekov "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.io") - [Paul Hendry (@pshendry)](https://github.com/pshendry "1 total commits to the home-assistant organization, 1 commit to warrant") - [Paul Jimenez (@pjz)](https://github.com/pjz "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Paul Nicholls (@pauln)](https://github.com/pauln "2 total commits to the home-assistant organization, 2 commits to netdisco") @@ -694,21 +693,22 @@ This page contains a list of people who have contributed in one way or another t - [Philip Rosenberg\-Watt (@PhilRW)](https://github.com/PhilRW "19 total commits to the home-assistant organization, 12 commits to home-assistant, 7 commits to home-assistant.io") - [Philipp Hellmich (@runningman84)](https://github.com/runningman84 "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Philipp Schmitt (@pschmitt)](https://github.com/pschmitt "40 total commits to the home-assistant organization, 27 commits to home-assistant, 11 commits to home-assistant.io, 1 commit to hassio-build, 1 commit to appdaemon") -- [Phill Price (@phillprice)](https://github.com/phillprice "11 total commits to the home-assistant organization, 11 commits to home-assistant.io") -- [PhracturedBlue (@PhracturedBlue)](https://github.com/PhracturedBlue "34 total commits to the home-assistant organization, 21 commits to home-assistant, 12 commits to home-assistant.io, 1 commit to home-assistant-polymer") +- [Phill Price (@phillprice)](https://github.com/phillprice "12 total commits to the home-assistant organization, 12 commits to home-assistant.io") +- [PhracturedBlue (@PhracturedBlue)](https://github.com/PhracturedBlue "42 total commits to the home-assistant organization, 25 commits to home-assistant, 13 commits to home-assistant.io, 4 commits to home-assistant-polymer") - [PhyberApex (@PhyberApex)](https://github.com/PhyberApex "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Pierre Ståhl (@postlund)](https://github.com/postlund "50 total commits to the home-assistant organization, 33 commits to home-assistant, 11 commits to home-assistant.io, 4 commits to netdisco, 2 commits to home-assistant-polymer") - [pkonnekermetametrics (@pkonnekermetametrics)](https://github.com/pkonnekermetametrics "5 total commits to the home-assistant organization, 5 commits to warrant") +- [plyblu (@plyblu)](https://github.com/plyblu "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [PuckStar (@PuckStar)](https://github.com/PuckStar "7 total commits to the home-assistant organization, 7 commits to home-assistant.io") - [quthla (@quthla)](https://github.com/quthla "13 total commits to the home-assistant organization, 5 commits to home-assistant-polymer, 4 commits to home-assistant-iOS, 4 commits to home-assistant") -- [R Huish (@Genestealer)](https://github.com/Genestealer "23 total commits to the home-assistant organization, 23 commits to home-assistant.io") - [rafale77 (@rafale77)](https://github.com/rafale77 "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Raiford (@raiford)](https://github.com/raiford "1 total commits to the home-assistant organization, 1 commit to hassio-addons") +- [randellhodges (@randellhodges)](https://github.com/randellhodges "3 total commits to the home-assistant organization, 3 commits to home-assistant-polymer") - [rbflurry (@rbflurry)](https://github.com/rbflurry "17 total commits to the home-assistant organization, 14 commits to home-assistant.io, 3 commits to home-assistant") - [Reed Riley (@reedriley)](https://github.com/reedriley "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Rendili (@Rendili)](https://github.com/Rendili "3 total commits to the home-assistant organization, 3 commits to home-assistant") -- [Rene Nulsch (@ReneNulschDE)](https://github.com/ReneNulschDE "21 total commits to the home-assistant organization, 14 commits to home-assistant, 7 commits to home-assistant.io") -- [Rene Tode (@ReneTode)](https://github.com/ReneTode "38 total commits to the home-assistant organization, 38 commits to appdaemon") +- [Rene Nulsch (@ReneNulschDE)](https://github.com/ReneNulschDE "22 total commits to the home-assistant organization, 15 commits to home-assistant, 7 commits to home-assistant.io") +- [Rene Tode (@ReneTode)](https://github.com/ReneTode "39 total commits to the home-assistant organization, 39 commits to appdaemon") - [Reza Moallemi (@moallemi)](https://github.com/moallemi "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [rhooper (@rhooper)](https://github.com/rhooper "27 total commits to the home-assistant organization, 25 commits to home-assistant, 2 commits to hadashboard") - [Riccardo Canta (@commento)](https://github.com/commento "3 total commits to the home-assistant organization, 3 commits to home-assistant") @@ -719,19 +719,22 @@ This page contains a list of people who have contributed in one way or another t - [Rick (@rcuddy)](https://github.com/rcuddy "1 total commits to the home-assistant organization, 1 commit to pi-gen") - [Rick Rubino (@rrubin0)](https://github.com/rrubin0 "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [rkabadi (@rkabadi)](https://github.com/rkabadi "17 total commits to the home-assistant organization, 17 commits to home-assistant") +- [rnizametdinov (@rnizametdinov)](https://github.com/rnizametdinov "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [Rob Capellini (@capellini)](https://github.com/capellini "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Rob Cranfill (@RobCranfill)](https://github.com/RobCranfill "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Rob Slifka (@rslifka)](https://github.com/rslifka "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") -- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1411 total commits to the home-assistant organization, 735 commits to home-assistant-iOS, 259 commits to home-assistant, 249 commits to home-assistant.io, 92 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 14 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to home-assistant-js, 3 commits to scenegen, 3 commits to appdaemon, 3 commits to hassbot, 3 commits to organization, 3 commits to hadashboard, 3 commits to home-assistant-js-websocket, 2 commits to LabelBot, 2 commits to lambda-home-assistant-github, 2 commits to fabric-home-assistant, 2 commits to micropython-home-assistant, 2 commits to home-assistant-assets, 2 commits to home-assistant-notebooks") +- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1430 total commits to the home-assistant organization, 752 commits to home-assistant-iOS, 260 commits to home-assistant, 249 commits to home-assistant.io, 93 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 14 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to organization, 3 commits to scenegen, 3 commits to appdaemon, 3 commits to home-assistant-js-websocket, 3 commits to hassbot, 3 commits to home-assistant-js, 3 commits to hadashboard, 2 commits to fabric-home-assistant, 2 commits to LabelBot, 2 commits to home-assistant-assets, 2 commits to micropython-home-assistant, 2 commits to lambda-home-assistant-github, 2 commits to home-assistant-notebooks") - [Robert (@metbril)](https://github.com/metbril "8 total commits to the home-assistant organization, 8 commits to home-assistant.io") - [Robert Accettura (@raccettura)](https://github.com/raccettura "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Robert Schütz (@dotlambda)](https://github.com/dotlambda "2 total commits to the home-assistant organization, 1 commit to netdisco, 1 commit to appdaemon") -- [Robert Svensson (@Kane610)](https://github.com/Kane610 "64 total commits to the home-assistant organization, 43 commits to home-assistant, 19 commits to home-assistant.io, 1 commit to netdisco, 1 commit to home-assistant-polymer") +- [Robert Schütz (@dotlambda)](https://github.com/dotlambda "3 total commits to the home-assistant organization, 2 commits to netdisco, 1 commit to appdaemon") +- [Robert Svensson (@Kane610)](https://github.com/Kane610 "78 total commits to the home-assistant organization, 53 commits to home-assistant, 22 commits to home-assistant.io, 1 commit to netdisco, 1 commit to developers.home-assistant, 1 commit to home-assistant-polymer") - [Robin (@robmarkcole)](https://github.com/robmarkcole "57 total commits to the home-assistant organization, 35 commits to home-assistant.io, 19 commits to home-assistant, 2 commits to home-assistant-assets, 1 commit to hassos") - [Robin Laurén (@llauren)](https://github.com/llauren "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Roddie Hasan (@eiddor)](https://github.com/eiddor "6 total commits to the home-assistant organization, 6 commits to home-assistant.io") +- [Rohan Kapoor (@rohankapoorcom)](https://github.com/rohankapoorcom "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Roi Dayan (@roidayan)](https://github.com/roidayan "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [roiff (@roiff)](https://github.com/roiff "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant") +- [Rolf Schäuble (@rschaeuble)](https://github.com/rschaeuble "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Ron Klinkien (@cyberjunky)](https://github.com/cyberjunky "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Ron Miller (@brainyron)](https://github.com/brainyron "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [roqeer (@roqeer)](https://github.com/roqeer "3 total commits to the home-assistant organization, 3 commits to home-assistant") @@ -742,11 +745,12 @@ This page contains a list of people who have contributed in one way or another t - [ruohan\.chen (@crhan)](https://github.com/crhan "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Ruslan Sayfutdinov (@KapJI)](https://github.com/KapJI "1 total commits to the home-assistant organization, 1 commit to developers.home-assistant") - [Russ K (@rkubes)](https://github.com/rkubes "2 total commits to the home-assistant organization, 2 commits to pi-gen") -- [Russell Cloran (@rcloran)](https://github.com/rcloran "36 total commits to the home-assistant organization, 32 commits to home-assistant, 4 commits to homebridge-homeassistant") +- [Russell Cloran (@rcloran)](https://github.com/rcloran "37 total commits to the home-assistant organization, 33 commits to home-assistant, 4 commits to homebridge-homeassistant") - [Ryan Bahm (@rdbahm)](https://github.com/rdbahm "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Ryan Bray (@rbray89)](https://github.com/rbray89 "13 total commits to the home-assistant organization, 12 commits to hassos, 1 commit to hassio-build") - [Ryan Daigle (@rwdaigle)](https://github.com/rwdaigle "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Ryan Jarvis (@Cabalist)](https://github.com/Cabalist "1 total commits to the home-assistant organization, 1 commit to hassbian-scripts") +- [Ryan Kladar (@Kladar)](https://github.com/Kladar "1 total commits to the home-assistant organization, 1 commit to hassos") - [Ryan Kraus (@rmkraus)](https://github.com/rmkraus "193 total commits to the home-assistant organization, 163 commits to home-assistant, 15 commits to home-assistant.io, 14 commits to home-assistant-polymer, 1 commit to home-assistant-notebooks") - [Ryan McLean (@ryanm101)](https://github.com/ryanm101 "97 total commits to the home-assistant organization, 75 commits to hassio-cli, 16 commits to home-assistant, 6 commits to home-assistant.io") - [Ryan Turner (@turnrye)](https://github.com/turnrye "6 total commits to the home-assistant organization, 6 commits to home-assistant") @@ -766,7 +770,7 @@ This page contains a list of people who have contributed in one way or another t - [Sean Wilson (@swilson)](https://github.com/swilson "5 total commits to the home-assistant organization, 4 commits to home-assistant, 1 commit to home-assistant-polymer") - [Sebastian (@sebk-666)](https://github.com/sebk-666 "6 total commits to the home-assistant organization, 5 commits to home-assistant.io, 1 commit to netdisco") - [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 "136 total commits to the home-assistant organization, 86 commits to home-assistant, 45 commits to home-assistant.io, 3 commits to netdisco, 2 commits to home-assistant-polymer") +- [Sebastian Muszynski (@syssi)](https://github.com/syssi "138 total commits to the home-assistant organization, 88 commits to home-assistant, 45 commits to home-assistant.io, 3 commits to netdisco, 2 commits to home-assistant-polymer") - [Sebastian von Minckwitz (@teodoc)](https://github.com/teodoc "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Semir Patel (@analogue)](https://github.com/analogue "2 total commits to the home-assistant organization, 2 commits to appdaemon") - [Sergey Isachenko (@zabuldon)](https://github.com/zabuldon "9 total commits to the home-assistant organization, 9 commits to home-assistant") @@ -782,8 +786,7 @@ This page contains a list of people who have contributed in one way or another t - [Sjors Spoorendonk (@sjorsjes)](https://github.com/sjorsjes "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [sjoshi10 (@sjoshi10)](https://github.com/sjoshi10 "1 total commits to the home-assistant organization, 1 commit to warrant") - [snizzleorg (@snizzleorg)](https://github.com/snizzleorg "5 total commits to the home-assistant organization, 5 commits to hadashboard") -- [squidwardy (@squidwardy)](https://github.com/squidwardy "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Sriram Vaidyanathan (@vaidyasr)](https://github.com/vaidyasr "6 total commits to the home-assistant organization, 3 commits to home-assistant.io, 3 commits to home-assistant") +- [Sriram Vaidyanathan (@vaidyasr)](https://github.com/vaidyasr "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.io") - [St\. John Johnson (@stjohnjohnson)](https://github.com/stjohnjohnson "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.io") - [starkillerOG (@starkillerOG)](https://github.com/starkillerOG "12 total commits to the home-assistant organization, 6 commits to home-assistant, 4 commits to home-assistant.io, 1 commit to developers.home-assistant, 1 commit to home-assistant-polymer") - [Stefan Jonasson (@stefan-jonasson)](https://github.com/stefan-jonasson "12 total commits to the home-assistant organization, 8 commits to home-assistant, 4 commits to home-assistant.io") @@ -792,27 +795,27 @@ This page contains a list of people who have contributed in one way or another t - [stephanerosi (@stephanerosi)](https://github.com/stephanerosi "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.io") - [Stephen Edgar (@ntwb)](https://github.com/ntwb "1 total commits to the home-assistant organization, 1 commit to fabric-home-assistant") - [Stephen Tomkinson (@neonbunny)](https://github.com/neonbunny "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Stephen Vanterpool (@blackgold9)](https://github.com/blackgold9 "38 total commits to the home-assistant organization, 37 commits to home-assistant-iOS, 1 commit to developers.home-assistant") +- [Stephen Vanterpool (@blackgold9)](https://github.com/blackgold9 "75 total commits to the home-assistant organization, 73 commits to home-assistant-iOS, 1 commit to developers.home-assistant, 1 commit to home-assistant-polymer") - [Stephen Yeargin (@stephenyeargin)](https://github.com/stephenyeargin "25 total commits to the home-assistant organization, 24 commits to hubot-home-assistant, 1 commit to home-assistant-polymer") - [Steve Easley (@SteveEasley)](https://github.com/SteveEasley "3 total commits to the home-assistant organization, 3 commits to home-assistant") -- [Steven Looman (@StevenLooman)](https://github.com/StevenLooman "9 total commits to the home-assistant organization, 7 commits to home-assistant, 2 commits to netdisco") +- [Steven Looman (@StevenLooman)](https://github.com/StevenLooman "10 total commits to the home-assistant organization, 7 commits to home-assistant, 3 commits to netdisco") - [Stu Gott (@stu-gott)](https://github.com/stu-gott "9 total commits to the home-assistant organization, 5 commits to home-assistant.io, 4 commits to home-assistant") - [Stuart Williams (@stuwil)](https://github.com/stuwil "1 total commits to the home-assistant organization, 1 commit to netdisco") - [Suresh Kalavala (@skalavala)](https://github.com/skalavala "32 total commits to the home-assistant organization, 32 commits to home-assistant.io") - [Sven\-Hendrik Haase (@svenstaro)](https://github.com/svenstaro "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [swanwila (@swanwila)](https://github.com/swanwila "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [System Tester (@systemtester)](https://github.com/systemtester "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") -- [Sytone (@sytone)](https://github.com/sytone "8 total commits to the home-assistant organization, 6 commits to home-assistant.io, 1 commit to developers.home-assistant, 1 commit to hassio-build") -- [Sören Oldag (@soldag)](https://github.com/soldag "15 total commits to the home-assistant organization, 8 commits to home-assistant.io, 7 commits to home-assistant") +- [Sytone (@sytone)](https://github.com/sytone "8 total commits to the home-assistant organization, 6 commits to home-assistant.io, 1 commit to hassio-build, 1 commit to developers.home-assistant") +- [Sören Oldag (@soldag)](https://github.com/soldag "16 total commits to the home-assistant organization, 8 commits to home-assistant, 8 commits to home-assistant.io") - [Tabakhase (@tabakhase)](https://github.com/tabakhase "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [tadly (@tadly)](https://github.com/tadly "4 total commits to the home-assistant organization, 4 commits to home-assistant") +- [tadly (@tadly)](https://github.com/tadly "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [tango-foxtrot (@tango-foxtrot)](https://github.com/tango-foxtrot "1 total commits to the home-assistant organization, 1 commit to netdisco") - [Taylor Peet (@RePeet13)](https://github.com/RePeet13 "9 total commits to the home-assistant organization, 9 commits to home-assistant.io") - [Teagan Glenn (@Teagan42)](https://github.com/Teagan42 "59 total commits to the home-assistant organization, 49 commits to home-assistant, 9 commits to home-assistant.io, 1 commit to home-assistant-js") - [Ted Drain (@TD22057)](https://github.com/TD22057 "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [tedstriker (@tedstriker)](https://github.com/tedstriker "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Teemu Mikkonen (@T3m3z)](https://github.com/T3m3z "3 total commits to the home-assistant organization, 3 commits to home-assistant") -- [Teemu R\. (@rytilahti)](https://github.com/rytilahti "59 total commits to the home-assistant organization, 46 commits to home-assistant, 9 commits to home-assistant.io, 4 commits to netdisco") +- [Teemu R\. (@rytilahti)](https://github.com/rytilahti "60 total commits to the home-assistant organization, 47 commits to home-assistant, 9 commits to home-assistant.io, 4 commits to netdisco") - [Teguh Sobirin (@tjstyle)](https://github.com/tjstyle "2 total commits to the home-assistant organization, 2 commits to pi-gen") - [Tentoe (@Tentoe)](https://github.com/Tentoe "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Theb-1 (@Theb-1)](https://github.com/Theb-1 "5 total commits to the home-assistant organization, 5 commits to home-assistant") @@ -835,6 +838,7 @@ This page contains a list of people who have contributed in one way or another t - [ThUnD3r\|Gr33n (@thundergreen)](https://github.com/thundergreen "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [tijuca (@tijuca)](https://github.com/tijuca "106 total commits to the home-assistant organization, 106 commits to libcoap") - [Tim Wilbrink (@TWilb)](https://github.com/TWilb "15 total commits to the home-assistant organization, 15 commits to home-assistant-iOS") +- [Timmo (@timmo001)](https://github.com/timmo001 "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Timo (@timotk)](https://github.com/timotk "1 total commits to the home-assistant organization, 1 commit to netdisco") - [timstanley1985 (@timstanley1985)](https://github.com/timstanley1985 "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [TJ Rana (@tjrana)](https://github.com/tjrana "1 total commits to the home-assistant organization, 1 commit to pi-gen") @@ -843,12 +847,12 @@ This page contains a list of people who have contributed in one way or another t - [Tobias Hoff (@ToSa27)](https://github.com/ToSa27 "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [Tobie Booth (@tobiebooth)](https://github.com/tobiebooth "4 total commits to the home-assistant organization, 3 commits to home-assistant, 1 commit to home-assistant-polymer") - [Toby Gray (@tobygray)](https://github.com/tobygray "4 total commits to the home-assistant organization, 4 commits to home-assistant") -- [Tod Schmidt (@tschmidty69)](https://github.com/tschmidty69 "37 total commits to the home-assistant organization, 21 commits to home-assistant, 10 commits to home-assistant.io, 5 commits to hassio-addons, 1 commit to hassio") +- [Tod Schmidt (@tschmidty69)](https://github.com/tschmidty69 "38 total commits to the home-assistant organization, 22 commits to home-assistant, 10 commits to home-assistant.io, 5 commits to hassio-addons, 1 commit to hassio") - [toddeye (@toddeye)](https://github.com/toddeye "20 total commits to the home-assistant organization, 20 commits to home-assistant") - [Tom (@Qu3uk)](https://github.com/Qu3uk "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Tom Dickman (@tdickman)](https://github.com/tdickman "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Tom Duijf (@tomduijf)](https://github.com/tomduijf "70 total commits to the home-assistant organization, 53 commits to home-assistant, 9 commits to home-assistant.io, 6 commits to home-assistant-polymer, 2 commits to netdisco") -- [Tom Harris (@teharris1)](https://github.com/teharris1 "22 total commits to the home-assistant organization, 15 commits to home-assistant, 7 commits to home-assistant.io") +- [Tom Harris (@teharris1)](https://github.com/teharris1 "27 total commits to the home-assistant organization, 18 commits to home-assistant, 9 commits to home-assistant.io") - [Tom Hoover (@tomhoover)](https://github.com/tomhoover "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Tom Matheussen (@Tommatheussen)](https://github.com/Tommatheussen "13 total commits to the home-assistant organization, 6 commits to home-assistant, 4 commits to home-assistant-polymer, 3 commits to home-assistant.io") - [Tom Usher (@tomusher)](https://github.com/tomusher "1 total commits to the home-assistant organization, 1 commit to netdisco") @@ -864,7 +868,7 @@ This page contains a list of people who have contributed in one way or another t - [Trevor (@tboyce021)](https://github.com/tboyce021 "15 total commits to the home-assistant organization, 10 commits to home-assistant, 5 commits to home-assistant.io") - [Trey Hunner (@treyhunner)](https://github.com/treyhunner "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [trollkarlen (@trollkarlen)](https://github.com/trollkarlen "5 total commits to the home-assistant organization, 5 commits to home-assistant") -- [Tsvi Mostovicz (@tsvi)](https://github.com/tsvi "9 total commits to the home-assistant organization, 5 commits to home-assistant.io, 4 commits to home-assistant") +- [Tsvi Mostovicz (@tsvi)](https://github.com/tsvi "12 total commits to the home-assistant organization, 6 commits to home-assistant.io, 6 commits to home-assistant") - [Tyler Page (@iamtpage)](https://github.com/iamtpage "3 total commits to the home-assistant organization, 3 commits to home-assistant.io") - [Tõnis Tobre (@tobre6)](https://github.com/tobre6 "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant") - [uchagani (@uchagani)](https://github.com/uchagani "8 total commits to the home-assistant organization, 7 commits to home-assistant, 1 commit to home-assistant-polymer") @@ -877,7 +881,8 @@ This page contains a list of people who have contributed in one way or another t - [Victor Cerutti (@victorcerutti)](https://github.com/victorcerutti "3 total commits to the home-assistant organization, 3 commits to home-assistant-polymer") - [Viet Dzung (@dzungpv)](https://github.com/dzungpv "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Vignesh Venkat (@vickyg3)](https://github.com/vickyg3 "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.io") -- [Ville Skyttä (@scop)](https://github.com/scop "91 total commits to the home-assistant organization, 59 commits to home-assistant, 11 commits to home-assistant.io, 9 commits to netdisco, 4 commits to hassio-addons, 3 commits to hassio-cli, 2 commits to hassio-build, 2 commits to home-assistant-polymer, 1 commit to hassio") +- [Ville Skyttä (@scop)](https://github.com/scop "106 total commits to the home-assistant organization, 70 commits to home-assistant, 11 commits to netdisco, 11 commits to home-assistant.io, 4 commits to hassio-addons, 3 commits to hassio-cli, 2 commits to hassio-build, 2 commits to developers.home-assistant, 2 commits to home-assistant-polymer, 1 commit to hassio") +- [Villányi Bálint (@villanyibalint)](https://github.com/villanyibalint "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Vincent Van Den Berghe (@vandenberghev)](https://github.com/vandenberghev "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [viswa-swami (@viswa-swami)](https://github.com/viswa-swami "9 total commits to the home-assistant organization, 9 commits to home-assistant") - [Vlad Korniev (@vkorn)](https://github.com/vkorn "1 total commits to the home-assistant organization, 1 commit to hassio-build") @@ -890,25 +895,27 @@ This page contains a list of people who have contributed in one way or another t - [Will W\. (@tiktok7)](https://github.com/tiktok7 "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Willems Davy (@joyrider3774)](https://github.com/joyrider3774 "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [William Johansson (@radhus)](https://github.com/radhus "1 total commits to the home-assistant organization, 1 commit to hassio") -- [William Scanlon (@w1ll1am23)](https://github.com/w1ll1am23 "119 total commits to the home-assistant organization, 81 commits to home-assistant, 36 commits to home-assistant.io, 2 commits to netdisco") +- [William Scanlon (@w1ll1am23)](https://github.com/w1ll1am23 "123 total commits to the home-assistant organization, 83 commits to home-assistant, 37 commits to home-assistant.io, 2 commits to netdisco, 1 commit to developers.home-assistant") - [williamlehman (@williamlehman)](https://github.com/williamlehman "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Wim Haanstra (@depl0y)](https://github.com/depl0y "3 total commits to the home-assistant organization, 3 commits to home-assistant") +- [Wim Haanstra (@depl0y)](https://github.com/depl0y "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.io") - [wokar (@wokar)](https://github.com/wokar "12 total commits to the home-assistant organization, 8 commits to home-assistant, 4 commits to home-assistant.io") - [Wolf\-Bastian Pöttner (@BastianPoe)](https://github.com/BastianPoe "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.io") - [Wolfgang Malgadey (@wmalgadey)](https://github.com/wmalgadey "5 total commits to the home-assistant organization, 5 commits to home-assistant") - [XECDesign (@XECDesign)](https://github.com/XECDesign "145 total commits to the home-assistant organization, 145 commits to pi-gen") - [Xorso (@Xorso)](https://github.com/Xorso "22 total commits to the home-assistant organization, 21 commits to home-assistant, 1 commit to hassio-addons") -- [Yannick POLLART (@ypollart)](https://github.com/ypollart "8 total commits to the home-assistant organization, 4 commits to home-assistant.io, 4 commits to home-assistant") +- [Yannick POLLART (@ypollart)](https://github.com/ypollart "8 total commits to the home-assistant organization, 4 commits to home-assistant, 4 commits to home-assistant.io") - [yasinS (@yasinS)](https://github.com/yasinS "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Yevgeniy (@sgttrs)](https://github.com/sgttrs "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [yingzong (@yingzong)](https://github.com/yingzong "1 total commits to the home-assistant organization, 1 commit to warrant") +- [yulongying (@yulongying)](https://github.com/yulongying "1 total commits to the home-assistant organization, 1 commit to home-assistant-js-websocket") - [Zen Tormey (@xehn)](https://github.com/xehn "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Zhao Lu (@zlu)](https://github.com/zlu "4 total commits to the home-assistant organization, 4 commits to home-assistant.io") - [Zio Tibia (@ziotibia81)](https://github.com/ziotibia81 "12 total commits to the home-assistant organization, 7 commits to home-assistant.io, 5 commits to home-assistant") - [Zorks (@Zorks)](https://github.com/Zorks "5 total commits to the home-assistant organization, 5 commits to home-assistant.io") +- [Zoé Bőle (@zoe1337)](https://github.com/zoe1337 "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Åskar Andersson (@olskar)](https://github.com/olskar "10 total commits to the home-assistant organization, 6 commits to home-assistant.io, 3 commits to home-assistant, 1 commit to hassbian-scripts") This page is irregularly updated using the [`credits_generator` tool](https://github.com/home-assistant/home-assistant.github.io/tree/next/credits_generator). If you think that you are missing, please let us know. -This page was last updated Tuesday, August 28th 2018, 7:39:11 am UTC. +This page was last updated Friday, September 21st 2018, 7:49:45 pm UTC. diff --git a/source/hassio/commandline.markdown b/source/hassio/commandline.markdown index a37177f832f..858bfda8fdf 100644 --- a/source/hassio/commandline.markdown +++ b/source/hassio/commandline.markdown @@ -16,7 +16,7 @@ Hass.io upgrade process from the SSH command line On the SSH command line, you can use the `hassio` command to retrieve logs, check the details of connected hardware, and more. -Home Assistant: +## {% linkable_title Home Assistant %} ```bash $ hassio homeassistant info @@ -28,7 +28,7 @@ $ hassio homeassistant stop $ hassio homeassistant update ``` -Supervisor: +## {% linkable_title Supervisor %} ```bash $ hassio supervisor info @@ -37,7 +37,7 @@ $ hassio supervisor reload $ hassio supervisor update ``` -Host: +## {% linkable_title Host %} ```bash $ hassio host reboot @@ -45,13 +45,15 @@ $ hassio host shutdown $ hassio host update ``` -Hardware: +## {% linkable_title Hardware %} ```bash $ hassio hardware info $ hassio hardware audio ``` +## {% linkable_title Usage examples %} + To update Home Assistant to a specific version, use the command: ```bash hassio homeassistant update --options version=x.y.z diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index 88aac017cc6..2c4db4c8e76 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -77,14 +77,14 @@ A detailed guide about running Hass.io as a virtual machine is available in the [etcher]: https://etcher.io/ [Virtual Appliance]: https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/ova.md [hassos-network]: https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md -[pi0-w]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi0-w-2.2.img.gz -[pi1]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi-2.2.img.gz -[pi2]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi2-2.2.img.gz -[pi3-32]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi3-2.2.img.gz -[pi3-64]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi3-64-2.2.img.gz +[pi0-w]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi0-w-1.10.img.gz +[pi1]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi-1.10.img.gz +[pi2]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi2-1.10.img.gz +[pi3-32]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi3-1.10.img.gz +[pi3-64]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi3-64-1.10.img.gz [tinker]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_tinker-2.2.img.gz [odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_odroid-c2-2.2.img.gz -[vmdk]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_ova-2.2.vmdk.gz +[vmdk]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_ova-1.10.vmdk [linux]: https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio [local]: http://hassio.local:8123 [samba]: /addons/samba/ diff --git a/source/images/blog/2018-09-release-0.78/components.png b/source/images/blog/2018-09-release-0.78/components.png new file mode 100644 index 00000000000..c02f11a8c8a Binary files /dev/null and b/source/images/blog/2018-09-release-0.78/components.png differ diff --git a/source/images/blog/2018-09-thinking-big/logo-text.svg b/source/images/blog/2018-09-thinking-big/logo-text.svg new file mode 100644 index 00000000000..784ed048c85 --- /dev/null +++ b/source/images/blog/2018-09-thinking-big/logo-text.svg @@ -0,0 +1 @@ +logo-text \ No newline at end of file diff --git a/source/images/blog/2018-09-thinking-big/social.png b/source/images/blog/2018-09-thinking-big/social.png new file mode 100644 index 00000000000..4e0a5032ead Binary files /dev/null and b/source/images/blog/2018-09-thinking-big/social.png differ diff --git a/source/images/components/mystrom/switch-advanced.png b/source/images/components/mystrom/switch-advanced.png new file mode 100644 index 00000000000..58edc028a70 Binary files /dev/null and b/source/images/components/mystrom/switch-advanced.png differ diff --git a/source/images/docs/authentication/error-invalid-client-id.png b/source/images/docs/authentication/error-invalid-client-id.png new file mode 100644 index 00000000000..9f543b92395 Binary files /dev/null and b/source/images/docs/authentication/error-invalid-client-id.png differ diff --git a/source/images/frontend/entity_box.png b/source/images/frontend/entity_box.png new file mode 100644 index 00000000000..8336a978d98 Binary files /dev/null and b/source/images/frontend/entity_box.png differ diff --git a/source/images/screenshots/habitica_new_task.png b/source/images/screenshots/habitica_new_task.png new file mode 100644 index 00000000000..dd21d3a3b6c Binary files /dev/null and b/source/images/screenshots/habitica_new_task.png differ diff --git a/source/images/supported_brands/edp_redy.png b/source/images/supported_brands/edp_redy.png new file mode 100644 index 00000000000..81959baffb9 Binary files /dev/null and b/source/images/supported_brands/edp_redy.png differ diff --git a/source/images/supported_brands/enedis.png b/source/images/supported_brands/enedis.png new file mode 100644 index 00000000000..df4e95c4c74 Binary files /dev/null and b/source/images/supported_brands/enedis.png differ diff --git a/source/images/supported_brands/geo_location.png b/source/images/supported_brands/geo_location.png new file mode 100644 index 00000000000..a8fab0f9133 Binary files /dev/null and b/source/images/supported_brands/geo_location.png differ diff --git a/source/images/supported_brands/habitica.png b/source/images/supported_brands/habitica.png new file mode 100644 index 00000000000..a90f684be21 Binary files /dev/null and b/source/images/supported_brands/habitica.png differ diff --git a/source/images/supported_brands/logi_circle.png b/source/images/supported_brands/logi_circle.png new file mode 100644 index 00000000000..61a8c72dc50 Binary files /dev/null and b/source/images/supported_brands/logi_circle.png differ diff --git a/source/images/supported_brands/metno.png b/source/images/supported_brands/metno.png new file mode 100644 index 00000000000..79a82c559ce Binary files /dev/null and b/source/images/supported_brands/metno.png differ diff --git a/source/images/supported_brands/nabu-casa.svg b/source/images/supported_brands/nabu-casa.svg new file mode 100644 index 00000000000..a038f7e6890 --- /dev/null +++ b/source/images/supported_brands/nabu-casa.svg @@ -0,0 +1 @@ +logo \ No newline at end of file diff --git a/source/images/supported_brands/opentherm.png b/source/images/supported_brands/opentherm.png new file mode 100644 index 00000000000..459f60e6736 Binary files /dev/null and b/source/images/supported_brands/opentherm.png differ diff --git a/source/images/supported_brands/starlingbank.png b/source/images/supported_brands/starlingbank.png new file mode 100644 index 00000000000..dd1c5eff703 Binary files /dev/null and b/source/images/supported_brands/starlingbank.png differ diff --git a/source/images/supported_brands/switchbot.png b/source/images/supported_brands/switchbot.png new file mode 100644 index 00000000000..da31c5feb00 Binary files /dev/null and b/source/images/supported_brands/switchbot.png differ diff --git a/source/images/supported_brands/switchmate-logo-rgb.png b/source/images/supported_brands/switchmate-logo-rgb.png new file mode 100644 index 00000000000..97030d5c6a5 Binary files /dev/null and b/source/images/supported_brands/switchmate-logo-rgb.png differ