diff --git a/_config.yml b/_config.yml index aba8631a696..c5f0d7c8236 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 108 -current_patch_version: 0 -date_released: 2020-04-08 +current_patch_version: 3 +date_released: 2020-04-10 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_cookbook/configuration_yaml_by_DrJohnT.markdown b/source/_cookbook/configuration_yaml_by_DrJohnT.markdown new file mode 100644 index 00000000000..124a444f5d5 --- /dev/null +++ b/source/_cookbook/configuration_yaml_by_DrJohnT.markdown @@ -0,0 +1,6 @@ +--- +title: "Configuration.yaml by DrJohnT" +description: "Velux windows, Drayton Wiser heating, Audio / Visual, lighting and humidity controlled fans" +ha_category: Example configuration.yaml +ha_external_link: https://github.com/DrJohnT/HomeAssistantPublicConfig +--- diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown index d5ff1b98553..4743ec8ea57 100644 --- a/source/_docs/automation/templating.markdown +++ b/source/_docs/automation/templating.markdown @@ -76,7 +76,15 @@ Knowing how to access the [state object](/docs/configuration/state_object/) of a
- Be aware that if you reference a trigger state object in an automation action, attempting to test that automation by calling the `automation.trigger` service or by clicking EXECUTE in the More Info box for the automation will not work. This is because the trigger state object doesn't exist in those contexts. One way to test automations like these is to manually change the state of the trigger entity at Developer Tools > States. + Be aware that if you reference a `trigger` state object in templates of automation `action`, attempting to test that automation by calling the `automation.trigger` service or by clicking EXECUTE in the More Info box for the automation will not work. This is because the trigger state object doesn't exist in those contexts. One way to test automations like these is to manually check that the templates work as expected by pasting them in Developer Tools > Template together with your trigger's definition like: + +{%raw%} +```yaml +{% set trigger={'to_state':{'state': 'heat'}} %} +{% set option = trigger.to_state.state %} +{{ 'on' if option == 'heat' else 'off' }} +``` +{%endraw%}
diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 47f359d96ea..e946477df98 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -352,6 +352,8 @@ automation: You could run the above automation by sending a POST HTTP request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. An example with no data sent to a SSL/TLS secured installation and using the command-line curl program is `curl -d "" https://your-home-assistant:8123/api/webhook/some_hook_id`. +Note that each webhook can only be used in one automation at a time. + ### Zone trigger Zone trigger fires when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/gpslogger/), the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/). diff --git a/source/_docs/ecosystem/appdaemon.markdown b/source/_docs/ecosystem/appdaemon.markdown index 59a6d36d097..e9b7263cc45 100644 --- a/source/_docs/ecosystem/appdaemon.markdown +++ b/source/_docs/ecosystem/appdaemon.markdown @@ -8,7 +8,7 @@ AppDaemon is a loosely coupled, multithreaded, sandboxed Python execution enviro # Another Take on Automation -AppDaemon is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and appdeamon then comes into its own. It brings quite a few things to the table: +AppDaemon is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and AppDaemon then comes into its own. It brings quite a few things to the table: - New paradigm - Some problems require a procedural and/or iterative approach, and `AppDaemon` Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that automations can't. - Ease of use - AppDaemon's API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as "Pythonic" as possible; experienced Python programmers should feel right at home. diff --git a/source/_docs/installation/docker.markdown b/source/_docs/installation/docker.markdown index 194fbac0c27..30f4f48d781 100644 --- a/source/_docs/installation/docker.markdown +++ b/source/_docs/installation/docker.markdown @@ -175,7 +175,10 @@ If you want to use a USB Bluetooth adapter or Z-Wave USB stick with Home Assista The above command should show you any USB devices plugged into your NAS. If you have more than one, you may get multiple items returned. Like : `ttyACM0` - Run Docker command: - `docker run --init --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e variable=TZ -e value=Europe/London --device /dev/ttyACM0 homeassistant/home-assistant:stable` + + ```bash + docker run --init --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e TZ=Europe/London --device /dev/ttyACM0 homeassistant/home-assistant:stable + ``` `-v` is your configuration path `-e` is set timezone @@ -193,7 +196,10 @@ That will tell Home Assistant where to look for our Z-Wave radio. - Connect to your NAS over SSH - Run Docker command: - `docker run --init --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e variable=TZ -e value=Europe/London -v /dev/bus/usb:/dev/bus/usb -v /var/run/dbus:/var/run/dbus homeassistant/home-assistant:stable` + + ```bash + docker run --init --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e TZ=Europe/London -v /dev/bus/usb:/dev/bus/usb -v /var/run/dbus:/var/run/dbus homeassistant/home-assistant:stable + ``` First `-v` is your configuration path `-e` is set timezone diff --git a/source/_integrations/actiontec.markdown b/source/_integrations/actiontec.markdown index 1cf78c72d1a..be399fa49b5 100644 --- a/source/_integrations/actiontec.markdown +++ b/source/_integrations/actiontec.markdown @@ -1,7 +1,6 @@ --- title: Actiontec description: Instructions on how to integrate Actiontec routers into Home Assistant. -logo: actiontec.png ha_category: - Presence Detection ha_release: 0.7 diff --git a/source/_integrations/aladdin_connect.markdown b/source/_integrations/aladdin_connect.markdown index 71735d6b6dc..e0ee71d4a8c 100644 --- a/source/_integrations/aladdin_connect.markdown +++ b/source/_integrations/aladdin_connect.markdown @@ -1,7 +1,6 @@ --- title: Aladdin Connect description: Instructions how to integrate Genie Aladdin Connect garage door covers into Home Assistant. -logo: aladdin_connect.png ha_category: - Cover ha_release: 0.75 diff --git a/source/_integrations/alarmdecoder.markdown b/source/_integrations/alarmdecoder.markdown index bf883ca99b5..975b2193a88 100644 --- a/source/_integrations/alarmdecoder.markdown +++ b/source/_integrations/alarmdecoder.markdown @@ -1,7 +1,6 @@ --- title: AlarmDecoder description: Instructions on how to integrate a DSC/Honeywell alarm panel with Home Assistant using an AlarmDecoder device. -logo: alarmdecoder.png ha_category: - Alarm - Binary Sensor diff --git a/source/_integrations/alpha_vantage.markdown b/source/_integrations/alpha_vantage.markdown index 758786c2752..595ca5a2e1a 100644 --- a/source/_integrations/alpha_vantage.markdown +++ b/source/_integrations/alpha_vantage.markdown @@ -1,7 +1,6 @@ --- title: Alpha Vantage description: Instructions on how to setup Alpha Vantage within Home Assistant. -logo: alpha_vantage.png ha_category: - Finance ha_iot_class: Cloud Polling diff --git a/source/_integrations/ambiclimate.markdown b/source/_integrations/ambiclimate.markdown index e83cfe321d4..ea561125809 100644 --- a/source/_integrations/ambiclimate.markdown +++ b/source/_integrations/ambiclimate.markdown @@ -1,7 +1,6 @@ --- title: Ambiclimate description: Instructions on how to integrate Ambiclimate A/C controller into Home Assistant. -logo: ambiclimate.png ha_category: Climate ha_release: 0.93 ha_iot_class: Cloud Polling diff --git a/source/_integrations/amcrest.markdown b/source/_integrations/amcrest.markdown index b74cc6a8cfb..78b5297a6c0 100644 --- a/source/_integrations/amcrest.markdown +++ b/source/_integrations/amcrest.markdown @@ -1,7 +1,6 @@ --- title: Amcrest description: Instructions on how to integrate Amcrest (or Dahua) IP cameras within Home Assistant. -logo: amcrest.png ha_category: - Hub - Binary Sensor diff --git a/source/_integrations/ampio.markdown b/source/_integrations/ampio.markdown index b0400fa639f..5655a7ca3f6 100644 --- a/source/_integrations/ampio.markdown +++ b/source/_integrations/ampio.markdown @@ -1,7 +1,6 @@ --- title: Ampio Smart Smog System description: Instructions on how to setup Ampio Smog sensors in Home Assistant. -logo: ampio_smog.png ha_category: - Health - Sensor diff --git a/source/_integrations/anel_pwrctrl.markdown b/source/_integrations/anel_pwrctrl.markdown index 91d2022aa86..e5aa7678ccc 100644 --- a/source/_integrations/anel_pwrctrl.markdown +++ b/source/_integrations/anel_pwrctrl.markdown @@ -1,7 +1,6 @@ --- title: Anel NET-PwrCtrl description: Instructions on how to integrate ANEL PwrCtrl switches within Home Assistant. -logo: anel.png ha_category: - Switch ha_iot_class: Local Polling diff --git a/source/_integrations/aquostv.markdown b/source/_integrations/aquostv.markdown index 32cbba65f33..1765dc0bce2 100644 --- a/source/_integrations/aquostv.markdown +++ b/source/_integrations/aquostv.markdown @@ -1,7 +1,6 @@ --- title: Sharp Aquos TV description: Instructions on how to integrate a Sharp Aquos TV into Home Assistant. -logo: sharp_aquos.png ha_category: - Media Player ha_release: 0.35 diff --git a/source/_integrations/arlo.markdown b/source/_integrations/arlo.markdown index 2cbc1cf9206..7fb64c95596 100644 --- a/source/_integrations/arlo.markdown +++ b/source/_integrations/arlo.markdown @@ -1,7 +1,6 @@ --- title: Arlo description: Instructions on how to integrate your Netgear Arlo cameras within Home Assistant. -logo: arlo.png ha_category: - Hub - Alarm diff --git a/source/_integrations/aruba.markdown b/source/_integrations/aruba.markdown index 2a8c20e3fbf..27fb1a46eba 100644 --- a/source/_integrations/aruba.markdown +++ b/source/_integrations/aruba.markdown @@ -1,7 +1,6 @@ --- title: Aruba description: Instructions on how to integrate Aruba routers into Home Assistant. -logo: aruba.png ha_category: - Presence Detection ha_release: 0.7 diff --git a/source/_integrations/asterisk_cdr.markdown b/source/_integrations/asterisk_cdr.markdown index 38a946896d0..185561d2c2c 100644 --- a/source/_integrations/asterisk_cdr.markdown +++ b/source/_integrations/asterisk_cdr.markdown @@ -1,7 +1,6 @@ --- title: Asterisk Call Detail Records description: Instructions on how to integrate an Asterisk CDR within Home Assistant. -logo: asterisk.png ha_category: - Mailbox ha_release: 0.79 diff --git a/source/_integrations/asterisk_mbox.markdown b/source/_integrations/asterisk_mbox.markdown index 4bed55d8d02..734323fe1ca 100644 --- a/source/_integrations/asterisk_mbox.markdown +++ b/source/_integrations/asterisk_mbox.markdown @@ -1,7 +1,6 @@ --- title: Asterisk Voicemail description: Instructions on how to integrate your existing Asterisk voicemail within Home Assistant. -logo: asterisk.png ha_category: - Mailbox ha_iot_class: Local Push diff --git a/source/_integrations/avri.markdown b/source/_integrations/avri.markdown index b91e2b06725..7145a19196a 100644 --- a/source/_integrations/avri.markdown +++ b/source/_integrations/avri.markdown @@ -1,7 +1,6 @@ --- title: Avri description: Instructions on how to set up Avri Waste sensor within Home Assistant. -logo: avri.jpeg ha_category: - Sensor ha_iot_class: Cloud Polling diff --git a/source/_integrations/axis.markdown b/source/_integrations/axis.markdown index 4e296522c15..c9a2625ee50 100644 --- a/source/_integrations/axis.markdown +++ b/source/_integrations/axis.markdown @@ -1,7 +1,6 @@ --- title: Axis description: Integration between network devices from Axis Communications with Home Assistant. -logo: axis.png ha_category: - Camera - Binary Sensor diff --git a/source/_integrations/baidu.markdown b/source/_integrations/baidu.markdown index cfec3e92b2e..765c71d47c1 100644 --- a/source/_integrations/baidu.markdown +++ b/source/_integrations/baidu.markdown @@ -1,7 +1,6 @@ --- title: Baidu description: Instructions on how to setup Baidu TTS with Home Assistant. -logo: baiducloud.png ha_category: - Text-to-speech ha_release: 0.59 diff --git a/source/_integrations/bitcoin.markdown b/source/_integrations/bitcoin.markdown index d07edfaf613..6bdefec6706 100644 --- a/source/_integrations/bitcoin.markdown +++ b/source/_integrations/bitcoin.markdown @@ -1,7 +1,6 @@ --- title: Bitcoin description: Instructions on how to integrate Bitcoin data within Home Assistant. -logo: bitcoin.png ha_category: - Finance ha_release: pre 0.7 diff --git a/source/_integrations/blockchain.markdown b/source/_integrations/blockchain.markdown index 55d3638d342..cca407b6555 100644 --- a/source/_integrations/blockchain.markdown +++ b/source/_integrations/blockchain.markdown @@ -1,7 +1,6 @@ --- title: Blockchain.com description: Instructions on how to integrate Blockchain.com data within Home Assistant. -logo: blockchain.png ha_category: - Finance ha_release: 0.47 diff --git a/source/_integrations/bloomsky.markdown b/source/_integrations/bloomsky.markdown index 871d50b0ff2..c0c2c9280cb 100644 --- a/source/_integrations/bloomsky.markdown +++ b/source/_integrations/bloomsky.markdown @@ -1,7 +1,6 @@ --- title: BloomSky description: Instructions on how to integrate the BloomSky within Home Assistant. -logo: bloomsky.png ha_category: - Environment - Binary Sensor diff --git a/source/_integrations/bluetooth_le_tracker.markdown b/source/_integrations/bluetooth_le_tracker.markdown index 32745562156..e1f73a2ed9e 100644 --- a/source/_integrations/bluetooth_le_tracker.markdown +++ b/source/_integrations/bluetooth_le_tracker.markdown @@ -1,7 +1,6 @@ --- title: Bluetooth LE Tracker description: Instructions for integrating bluetooth low-energy tracking within Home Assistant. -logo: bluetooth.png ha_category: - Presence Detection ha_iot_class: Local Polling diff --git a/source/_integrations/bluetooth_tracker.markdown b/source/_integrations/bluetooth_tracker.markdown index 6294fa732d5..9cbd37e593e 100644 --- a/source/_integrations/bluetooth_tracker.markdown +++ b/source/_integrations/bluetooth_tracker.markdown @@ -1,7 +1,6 @@ --- title: Bluetooth Tracker description: Instructions for integrating Bluetooth tracking within Home Assistant. -logo: bluetooth.png ha_category: - Presence Detection ha_iot_class: Local Polling diff --git a/source/_integrations/bom.markdown b/source/_integrations/bom.markdown index 12cc48d91dc..df4b3f431d7 100644 --- a/source/_integrations/bom.markdown +++ b/source/_integrations/bom.markdown @@ -1,7 +1,6 @@ --- title: Australian Bureau of Meteorology (BOM) description: Instructions on how to integrate Bureau of Meteorology Australia weather conditions into Home Assistant. -logo: bom.png ha_category: - Weather - Sensor diff --git a/source/_integrations/braviatv.markdown b/source/_integrations/braviatv.markdown index 5a5de181d0a..9ba6ccc7abf 100644 --- a/source/_integrations/braviatv.markdown +++ b/source/_integrations/braviatv.markdown @@ -1,7 +1,6 @@ --- title: Sony Bravia TV description: Instructions on how to integrate a Sony Bravia TV into Home Assistant. -logo: bravia.png ha_category: - Media Player ha_release: 0.23 diff --git a/source/_integrations/caldav.markdown b/source/_integrations/caldav.markdown index e15962d2029..e5d2bdc6009 100644 --- a/source/_integrations/caldav.markdown +++ b/source/_integrations/caldav.markdown @@ -106,7 +106,7 @@ custom_calendars: ### Sensor attributes - - **offset_reached**: If set in the event title and parsed out will be on/off once the offset in the title in minutes is reached. So the title Very important meeting !!-10 would trigger this attribute to be on 10 minutes before the event starts. + - **offset_reached**: If set in the event title and parsed out will be on/off once the offset in the title in minutes is reached. So the title Very important meeting !!-10 would trigger this attribute to be on 10 minutes before the event starts. This should be in the format of `HH:MM` or `MM`. - **all_day**: `True/False` if this is an all day event. Will be `False` if there is no event found. - **message**: The event title with the `search` values extracted. So in the above example for `offset_reached` the message would be set to Very important meeting - **description**: The event description. diff --git a/source/_integrations/camera.markdown b/source/_integrations/camera.markdown index 2a6ea0b9884..c62ded05185 100644 --- a/source/_integrations/camera.markdown +++ b/source/_integrations/camera.markdown @@ -85,7 +85,7 @@ For example, the following action in an automation would take a recording from " ```yaml action: service: camera.record - data: + data_template: entity_id: camera.yourcamera filename: '/tmp/{{ entity_id }}_{{ now().strftime("%Y%m%d-%H%M%S") }}.mp4' ``` diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index 8a326f576ac..7c5abfd6bbb 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -27,7 +27,8 @@ Note that Home Assistant Cast requires your Home Assistant installation to be ac ## Advanced use -Cast devices can only be discovered if they are on the same subnet as Home Assistant. If this is not the case, you need to configure the IP address of the Cast device directly: +### Manual configuration +By default, any discovered Cast device is added to Home Assistant. This can be restricted by supplying a white list of wanted chrome casts. ```yaml # Example configuration.yaml entry @@ -43,7 +44,7 @@ media_player: type: list keys: host: - description: Use only if you don't want to scan for devices. + description: IP-address of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS. required: false type: string ignore_cec: @@ -53,3 +54,12 @@ media_player: required: false type: list {% endconfiguration %} + +### Cast devices and Home Assistant on different subnets + +Cast devices can only be discovered and connected to if they are on the same subnet as Home Assistant. If this is not the case, it's necessary to: + +- Enable mDNS forwarding between the subnets. +- Enable source NAT to make requests from Home Assistant to the Chromecast appear to come from the same subnet as the Chromecast. + +Setups with cast devices on a different subnet than Home Assistant are not recommended and not supported. diff --git a/source/_integrations/cisco_ios.markdown b/source/_integrations/cisco_ios.markdown index 8e5f8d80259..b8e435ab9e3 100644 --- a/source/_integrations/cisco_ios.markdown +++ b/source/_integrations/cisco_ios.markdown @@ -1,7 +1,6 @@ --- title: Cisco IOS description: Instructions on how to integrate Cisco IOS routers into Home Assistant. -logo: cisco.png ha_category: - Presence Detection ha_release: 0.33 diff --git a/source/_integrations/cisco_mobility_express.markdown b/source/_integrations/cisco_mobility_express.markdown index 13047b645a5..44233d12831 100644 --- a/source/_integrations/cisco_mobility_express.markdown +++ b/source/_integrations/cisco_mobility_express.markdown @@ -1,7 +1,6 @@ --- title: Cisco Mobility Express description: Instructions on how to integrate Cisco Mobility Express wireless controllers into Home Assistant. -logo: cisco.png ha_category: - Presence Detection ha_release: '0.90' diff --git a/source/_integrations/coinbase.markdown b/source/_integrations/coinbase.markdown index 7a9400b074b..eeeab10884b 100644 --- a/source/_integrations/coinbase.markdown +++ b/source/_integrations/coinbase.markdown @@ -1,7 +1,6 @@ --- title: Coinbase description: Instructions for how to add Coinbase sensors to Home Assistant. -logo: coinbase.png ha_category: - Finance - Sensor diff --git a/source/_integrations/comfoconnect.markdown b/source/_integrations/comfoconnect.markdown index db447944fe9..85d74f8016b 100644 --- a/source/_integrations/comfoconnect.markdown +++ b/source/_integrations/comfoconnect.markdown @@ -1,7 +1,6 @@ --- title: Zehnder ComfoAir Q description: Instructions on how to integrate Zehnder ComfoAir Q350/450/600 ventilation systems into Home Assistant. -logo: zehnder.png ha_category: - Fan - Sensor diff --git a/source/_integrations/cppm_tracker.markdown b/source/_integrations/cppm_tracker.markdown index 0acc267dc77..1bb25d16601 100644 --- a/source/_integrations/cppm_tracker.markdown +++ b/source/_integrations/cppm_tracker.markdown @@ -1,7 +1,6 @@ --- title: Aruba ClearPass description: Instructions on how to integrate Aruba ClearPass into Home Assistant. -logo: aruba.png ha_category: - Presence Detection ha_release: '0.90' diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index 2f09ea2cd60..e8d7876c2e4 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -33,8 +33,9 @@ Known supported devices: - Marantz M-RC610 - Marantz SR5008 - Marantz SR6007 - SR6010 -- Marantz NR1506 +- Marantz NR1504 - Marantz NR1604 +- Marantz NR1506 - Other Denon AVR receivers (untested) - Marantz receivers (experimental) diff --git a/source/_integrations/dialogflow.markdown b/source/_integrations/dialogflow.markdown index 2e7b45ec041..7e18ea766f9 100644 --- a/source/_integrations/dialogflow.markdown +++ b/source/_integrations/dialogflow.markdown @@ -1,7 +1,6 @@ --- title: Dialogflow description: Instructions on how integrate Dialogflow with Home Assistant. -logo: dialogflow.png ha_category: - Voice ha_release: 0.56 diff --git a/source/_integrations/doods.markdown b/source/_integrations/doods.markdown index 178acf3c7f7..665139507a2 100644 --- a/source/_integrations/doods.markdown +++ b/source/_integrations/doods.markdown @@ -8,16 +8,15 @@ ha_release: '0.100' ha_domain: doods --- -The `doods` image processing platform allows you to detect and recognize objects in a camera image using [DOODS](https://github.com/snowzach/doods/). The state of the entity is the number of objects detected, and recognized objects are listed in the `summary` attribute along with quantity. The `matches` attribute provides the confidence `score` for recognition and the bounding `box` of the object for each detection category. +The `doods` image processing integration allows you to detect and recognize objects in a camera image using [DOODS](https://github.com/snowzach/doods/). The state of the entity is the number of objects detected and recognized objects are listed in the `summary` attribute along with quantity. The `matches` attribute provides the confidence `score` for recognition and the bounding `box` of the object for each detection category. ## Setup -You need to have DOODS running somewhere. It's easiest to run as a Docker container and deployment is described on Docker Hub -[DOODS - Docker](https://hub.docker.com/r/snowzach/doods) +You need to have DOODS running somewhere. It's easiest to run as a [Docker](https://hub.docker.com/r/snowzach/doods) container. ## Configuration -The configuration loosely follows the TensorFlow configuration. To enable this platform in your installation, add the following to your `configuration.yaml` file: +To enable this integration in your installation, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -44,20 +43,20 @@ source: required: false type: string url: - description: The URL of the DOODS server + description: The URL of the DOODS server. required: true type: string timeout: - description: Timeout for requests (in seconds) + description: Timeout for requests (in seconds). required: false type: integer default: 90 detector: - description: The DOODS detector to use + description: The DOODS detector to use. required: true type: string confidence: - description: The default confidence for any detected objects where not explicitly set + description: The default confidence for any detected objects where not explicitly set. required: false type: float area: @@ -104,7 +103,7 @@ labels: required: true type: string confidence: - description: The minimum confidence for the selected label + description: The minimum confidence for the selected label. required: false type: float area: @@ -140,9 +139,12 @@ labels: {% endconfiguration %} +## Sample configuration + +{% raw %} + ```yaml # Example advanced configuration.yaml entry -# Example configuration.yaml entry image_processing: - platform: doods scan_interval: 1000 @@ -152,8 +154,8 @@ image_processing: source: - entity_id: camera.front_yard file_out: - - "/tmp/{% raw %}{{ camera_entity.split('.')[1] }}{% endraw %}_latest.jpg" - - "/tmp/{% raw %}{{ camera_entity.split('.')[1] }}_{{ now().strftime('%Y%m%d_%H%M%S') }}{% endraw %}.jpg" + - "/tmp/{{ camera_entity.split('.')[1] }}_latest.jpg" + - "/tmp/{{ camera_entity.split('.')[1] }}_{{ now().strftime('%Y%m%d_%H%M%S') }}.jpg" confidence: 50 # This global detection area is required for all labels area: @@ -177,9 +179,11 @@ image_processing: - truck ``` +{% endraw %} + ## Optimizing resources -[Image processing components](/components/image_processing/) process the image from a camera at a fixed period given by the `scan_interval`. This leads to excessive processing if the image on the camera hasn't changed, as the default `scan_interval` is 10 seconds. You can override this by adding to your configuration `scan_interval: 10000` (setting the interval to 10,000 seconds), and then call the `image_processing.scan` service when you actually want to perform processing. +The [Image processing integration](/components/image_processing/) process the image from a camera at a fixed period given by the `scan_interval`. This leads to excessive processing if the image on the camera hasn't changed, as the default `scan_interval` is 10 seconds. You can override this by adding to your configuration `scan_interval: 10000` (setting the interval to 10,000 seconds) and then call the `image_processing.scan` service when you actually want to perform processing. ```yaml # Example advanced configuration.yaml entry diff --git a/source/_integrations/doorbird.markdown b/source/_integrations/doorbird.markdown index c2f39708de3..ed85a46fcc8 100644 --- a/source/_integrations/doorbird.markdown +++ b/source/_integrations/doorbird.markdown @@ -32,7 +32,7 @@ It is recommended to set up a new account on your Doorbird App for use with Home ## Configuration -To add `DoorBird` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **DoorBird**. +To add `DoorBird` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **DoorBird**. After filling out UI prompts, click the gear icon to edit device settings. Enter device event names here to associate with a schedule in DoorBird app. See [Schedules](#schedules) Alternatively, add the following to your `configuration.yaml` file: @@ -129,7 +129,8 @@ Simply open a new browser window and navigate to `{Home Assistant URL}/api/doorb localhost:8123`. Replace `{DEVICE_TOKEN}` with the token specified in your configuration for the device you would like to clear.

Please note that clearing device events will require configuration steps above to be taken again. It could also affect other third-party applications you may use with your DoorBird device. It will not break the official mobile app in any way, so mobile push notifications will still work. - +

+If DoorBird was setup using UI prompts, a token can be discovered through DoorBird App by clicking settings (cog icon) -> Administration-> LOGIN (using your App Administration details). Under the "FAVORITES" section, choose "HTTP(S) Calls". This displays all events and the associated HTTP URL. In that URL field, you will be able to see the token that was auto-generated by Home Assistant. #### Event Data diff --git a/source/_integrations/efergy.markdown b/source/_integrations/efergy.markdown index 6012d6dea90..eee769abebc 100644 --- a/source/_integrations/efergy.markdown +++ b/source/_integrations/efergy.markdown @@ -1,7 +1,6 @@ --- title: Efergy description: Instructions on how to integrate Efergy devices within Home Assistant. -logo: efergy.png ha_category: - Energy ha_release: pre 0.7 diff --git a/source/_integrations/envisalink.markdown b/source/_integrations/envisalink.markdown index 26e348a4a35..0fd9f0b09d0 100644 --- a/source/_integrations/envisalink.markdown +++ b/source/_integrations/envisalink.markdown @@ -1,7 +1,6 @@ --- title: Envisalink description: Instructions on how to integrate a DSC/Honeywell alarm panel with Home Assistant using an envisalink evl3/evl4 board. -logo: eyezon.png ha_category: - Alarm - Binary Sensor diff --git a/source/_integrations/epson.markdown b/source/_integrations/epson.markdown index ff8459ff08b..13007710fc6 100644 --- a/source/_integrations/epson.markdown +++ b/source/_integrations/epson.markdown @@ -1,7 +1,6 @@ --- title: Epson description: Instructions on how to integrate Epson projector into Home Assistant. -logo: epson.png ha_category: - Media Player ha_release: 0.72 diff --git a/source/_integrations/epsonworkforce.markdown b/source/_integrations/epsonworkforce.markdown index 5a8ab2f6159..f26bc88f2d5 100644 --- a/source/_integrations/epsonworkforce.markdown +++ b/source/_integrations/epsonworkforce.markdown @@ -1,7 +1,6 @@ --- title: Epson Workforce description: Instructions on how to integrate Epson Workforce Printer into Home Assistant. -logo: epson.png ha_category: - Sensor ha_release: 0.92 diff --git a/source/_integrations/fido.markdown b/source/_integrations/fido.markdown index b88742852ef..42d4df2012d 100644 --- a/source/_integrations/fido.markdown +++ b/source/_integrations/fido.markdown @@ -1,7 +1,6 @@ --- title: Fido description: Instructions on how to integrate Fido data usage within Home Assistant. -logo: fido.png ha_category: - Network ha_release: 0.39 diff --git a/source/_integrations/gearbest.markdown b/source/_integrations/gearbest.markdown index 2cf6ab80b06..17b1c61402a 100644 --- a/source/_integrations/gearbest.markdown +++ b/source/_integrations/gearbest.markdown @@ -1,7 +1,6 @@ --- title: Gearbest description: Instructions on how to integrate a Gearbest sensor into Home Assistant. -logo: gearbest.png ha_category: - Sensor ha_iot_class: Cloud Polling diff --git a/source/_integrations/here_travel_time.markdown b/source/_integrations/here_travel_time.markdown index fc28c2f3785..5661b7e333b 100644 --- a/source/_integrations/here_travel_time.markdown +++ b/source/_integrations/here_travel_time.markdown @@ -94,10 +94,9 @@ arrival: required: false type: time departure: - description: "Time when travel is expected to end. A 24 hour time string like `08:00:00`. On a sensor update it will be combined with the current date to get travel time for that moment. Cannot be used in combination with `arrival`. The default is now (the current date and time)" + description: "Time when travel is expected to end. A 24 hour time string like `08:00:00`. On a sensor update it will be combined with the current date to get travel time for that moment. Cannot be used in combination with `arrival`. If departure is not provided each update of the sensor uses the current date and time." required: false type: time - default: "now" unit_system: description: "You can choose between `metric` or `imperial`." required: false diff --git a/source/_integrations/hikvisioncam.markdown b/source/_integrations/hikvisioncam.markdown index c2f26809332..178a21c9683 100644 --- a/source/_integrations/hikvisioncam.markdown +++ b/source/_integrations/hikvisioncam.markdown @@ -1,7 +1,6 @@ --- title: Hikvision description: Instructions on how to integrate Hikvision camera switches into Home Assistant. -logo: hikvision.png ha_category: - Switch ha_release: pre 0.7 diff --git a/source/_integrations/hisense_aehw4a1.markdown b/source/_integrations/hisense_aehw4a1.markdown index 637870c4f48..8009ab8391e 100644 --- a/source/_integrations/hisense_aehw4a1.markdown +++ b/source/_integrations/hisense_aehw4a1.markdown @@ -1,7 +1,6 @@ --- title: Hisense AEH-W4A1 description: Instructions to setup the Hisense AEH W4A1 WiFi module for ACs. -logo: hisense.png ha_release: 0.103 ha_category: - Climate diff --git a/source/_integrations/hunterdouglas_powerview.markdown b/source/_integrations/hunterdouglas_powerview.markdown index a02ca235614..d804ab73781 100644 --- a/source/_integrations/hunterdouglas_powerview.markdown +++ b/source/_integrations/hunterdouglas_powerview.markdown @@ -1,7 +1,6 @@ --- title: Hunter Douglas PowerView description: Instructions on how to setup Hunter Douglas PowerView scenes within Home Assistant. -logo: hunter-douglas-powerview.png ha_category: - Scene ha_release: 0.15 diff --git a/source/_integrations/hydrawise.markdown b/source/_integrations/hydrawise.markdown index 6f82a482181..a30dfbc5895 100644 --- a/source/_integrations/hydrawise.markdown +++ b/source/_integrations/hydrawise.markdown @@ -1,7 +1,6 @@ --- title: Hunter Hydrawise description: Instructions on how to integrate your Hunter Hydrawise Wi-Fi irrigation control system within Home Assistant. -logo: hydrawise_logo.png ha_category: - Irrigation - Binary Sensor diff --git a/source/_integrations/input_boolean.markdown b/source/_integrations/input_boolean.markdown index 6aeecdc9503..e2568f4742d 100644 --- a/source/_integrations/input_boolean.markdown +++ b/source/_integrations/input_boolean.markdown @@ -19,7 +19,6 @@ To enable input booleans in your installation, add the following lines to your ` input_boolean: notify_home: name: Notify when someone arrives home - initial: off icon: mdi:car ``` diff --git a/source/_integrations/kira.markdown b/source/_integrations/kira.markdown index b469a682be4..f5c38667649 100644 --- a/source/_integrations/kira.markdown +++ b/source/_integrations/kira.markdown @@ -10,21 +10,25 @@ ha_release: 0.45 ha_domain: kira --- -The `kira` integration is the main integration to integrate Keene Electronics IR over IP [Kira](https://www.keene.co.uk/keene-ir-anywhere-single-worldwide.html) modules with Home Assistant. +The `kira` integration is the main integration to integrate Keene Electronics IR over IP [Kira](https://k2audio.co.uk/collections/ip-and-internet-control) modules with Home Assistant. There is currently support for the following device types within Home Assistant: -- Remote -- Sensor +- Remote (emit an IR code when instructed by Home Assistant) +- Sensor (trigger Home Assistant to do something when a particular IR signal is received) -### Example Configuration +Some models (original Kira and Kira128) can be configured to act as either a sensor or as a remote. They are also able act as both when set to Standalone mode. The wireless models are hardware specific so the receiver can only be integrated as a sensor and the transmitter can only be integrated as a remote. + +If you are using two or more Kira devices for point to point IR transfer across your network they can continue to perform this function whilst also acting as a sensor or remote for Home Assistant. + +## Configuration ```yaml # Example configuration.yaml entry kira: ``` -Kira modules have no built-in mechanism for auto-discovery, so will need to be configured to send packets to Home Assistant. Documentation for this can be found on the manufacturer's website [Here](https://www.keene.co.uk/pages/iranywhere/index.html). +Kira modules have no built-in mechanism for auto-discovery, so will need to be configured to send packets to Home Assistant. The process varies according to the module type. The documentation for each can be found on the [manufacturer's website](https://www.info.keene-electronics.co.uk). ### Configuration Options @@ -83,7 +87,15 @@ remotes: If no sensors or remotes are specified, a sensor with default values will be added. -### Code Configuration +### Entities + +Restart Home Assistant and you should now have an entity called `kira_remote` (or whatever you called it). To check go to Developer Tools > States and start to type “kira” within the entity list. + +

+ +

+ +### IR Codes The first time the Kira integration is loaded, `kira_codes.yaml` will be created in the Home Assistant configuration directory. @@ -129,11 +141,102 @@ repeat: Some manufacturers (e.g., Samsung) require an IR code to be sent a number of times in a row in rapid succession (usually 3). This doesn't apply to the vast majority of devices, but it can be helpful if needed. +You now need to edit `kira_codes.yaml` to make sure it contains the codes you want the Kira to blast out as a remote or respond to as a sensor. Note that each time you edit and save the `kira_codes.yaml` file you need to restart Home Assistant for the changes to take effect, reloading the automations alone is not sufficient. + +### Example remote + +Using the number 1 button from a Panasonic DVD player: + +```yaml +# Example kira_codes.yaml entry +- name: PanaOne +code: "K 2432 0D31 06EB 0196 01F3 0194 0538 01B4 01D3 01B4 01D1 01B4 01D3 01B4 01D3 01B3 01D3 01B3 01D3 01B4 01D3 01B3 01D3 01B3 01D3 01B4 01D3 01B3 01D3 01B4 0518 01B4 01D3 01B3 01D3 01B4 01D1 01B7 01D1 01B7 01D1 01B4 01D3 01B4 0518 01B4 01D3 01B4 01D1 01B7 0518 01B4 01D3 01B3 01D3 01B4 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B4 01D3 01B4 0518 01B4 01D3 01B4 01D1 01B7 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B4 0518 01B7 2000" +device: DVD +type: kira +``` + +Go to "Configuration" and select "Scripts" and click to add a new script. This is an example using the Panasonic code above. + +

+ +

+ +When you have filled in the data to match your YAML entry save the script and test it by clicking the play button next to the name you assigned. If all has gone well your Kira module should now blast this IR code and operate your equipment. + +

+ +

+ +Once you know the code is working and procedure is correct you can use the facility in any number of ways, perhaps triggering the output based on sensor readings or by adding a number of buttons as a virtual remote in the Home Assistant front end. + +### Example sensor + +Using the number 1 and 2 buttons from a Panasonic DVD player: + +```yaml +# Example kira_codes.yaml entry +- name: PanaOne + code: "K 2432 0D31 06EB 0196 01F3 0194 0538 01B4 01D3 01B4 01D1 01B4 01D3 01B4 01D3 01B3 01D3 01B3 01D3 01B4 01D3 01B3 01D3 01B3 01D3 01B4 01D3 01B3 01D3 01B4 0518 01B4 01D3 01B3 01D3 01B4 01D1 01B7 01D1 01B7 01D1 01B4 01D3 01B4 0518 01B4 01D3 01B4 01D1 01B7 0518 01B4 01D3 01B3 01D3 01B4 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B4 01D3 01B4 0518 01B4 01D3 01B4 01D1 01B7 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B4 01D3 01B4 01D1 01B7 01D1 01B4 0518 01B7 2000" + device: DVD + type: kira + +- name: PanaTwo + code: "K 2432 0D30 06EE 0192 01F6 0192 053A 0192 01F3 0194 01F3 0194 01F3 0192 01F6 0192 01F3 0194 01F3 0192 01F6 0192 01F3 0194 01F3 0192 01F6 0192 01F3 0194 053A 0192 01F3 0194 01F3 0194 01F3 0194 01F3 0192 01F3 0194 01F3 0194 053A 0192 01F6 0192 01F3 0194 053A 0192 01F3 0194 01F3 0194 01F3 0194 01F3 0192 01F6 0192 01F3 0194 01F3 0192 01F3 0194 053A 0194 01F3 0194 01F3 0192 01F6 0192 053A 0192 01F3 0194 01F3 0194 01F3 0194 053A 0192 01F3 0194 01F3 0194 01F3 0194 01F3 0192 01F6 0192 01F3 0194 053A 0192 2000" + device: DVD + type: kira +``` + +Visit the Kira module configuration page and be sure to make the following changes according to your module use: + +If this is to be the only use of the Kira module then set the TARGET IP address to be that of your Home Assistant installation. Uncheck the “auto find” option box if present. Click on save and reboot the module. + +If the Kira module is to used in conjunction with another module be for IR over IP then leave (or set) the TARGET IP address to that of the other Kira module and in this instance set the COMPUTER IP address to the IP address of your Home Assistant installation. Check the option box to "send to alternative device" if present. Click on save and reboot to make the changes effective. + +Note that once you changed the COMPUTER IP you will longer be able to use the Kira utiltiy on your PC to capture IR codes. + +Next within Home Assistant go to Developer tools -> States and scroll down the list until you see `sensor.kira_(whatever you called it)`. Aim your remote at the Kira device and press the buttons you stored the code for. If all is well you should see the state change to match the name you gave to the code. + +

+ +

+ +Example automation using these IR codes to toggle a Sonoff plug. + +```yaml +# Example kira_sensor +- id: '1583339338363' + alias: Panasonic On + description: Turn on sonoff s20 relay + trigger: + - entity_id: sensor.kira_wireless + platform: state + to: PanaOne + condition: [] + action: + - device_id: 3628b4f34df943b3b721ead954cf3ca7 + domain: switch + entity_id: switch.plug2_relay + type: turn_on +- id: '1584035716024' + alias: 'Panaxonic Off ' + description: Turn off sonoff s20 relay + trigger: + - entity_id: sensor.kira_wireless + platform: state + to: PanaTwo + condition: [] + action: + - device_id: 3628b4f34df943b3b721ead954cf3ca7 + domain: switch + entity_id: switch.plug2_relay + type: turn_off +``` + ### Code Types When creating an entry in `kira_codes.yaml`, a few different kinds of codes can be used. -- **kira**: This is the native wire protocol used by Kira modules. These can be captured using netcat. +- **kira**: This is the native wire protocol used by Kira modules. These can be captured using the free Kira utility available from the manufacturers website. - **pronto**: Pronto codes are supported. - **nec**: If the device uses NEC IR codes and the manufacturer has published them, they can be used here. diff --git a/source/_integrations/lg_netcast.markdown b/source/_integrations/lg_netcast.markdown index 891a963883a..1c695637f44 100644 --- a/source/_integrations/lg_netcast.markdown +++ b/source/_integrations/lg_netcast.markdown @@ -1,7 +1,6 @@ --- title: LG Netcast description: Instructions on how to integrate a LG TV (Netcast 3.0 & 4.0) within Home Assistant. -logo: lg.png ha_category: - Media Player ha_iot_class: Local Polling diff --git a/source/_integrations/lg_soundbar.markdown b/source/_integrations/lg_soundbar.markdown index fe38a9c748e..037685436e0 100644 --- a/source/_integrations/lg_soundbar.markdown +++ b/source/_integrations/lg_soundbar.markdown @@ -1,7 +1,6 @@ --- title: LG Soundbars description: Instructions on how to integrate LG Soundbars into Home Assistant. -logo: lg.png ha_category: - Media Player ha_iot_class: Local Polling diff --git a/source/_integrations/lock.mqtt.markdown b/source/_integrations/lock.mqtt.markdown index 5a9baf5a6cc..312714b401d 100644 --- a/source/_integrations/lock.mqtt.markdown +++ b/source/_integrations/lock.mqtt.markdown @@ -165,6 +165,8 @@ lock: command_topic: "home-assistant/frontdoor/set" payload_lock: "LOCK" payload_unlock: "UNLOCK" + state_locked: "LOCK" + state_unlocked: "UNLOCK" optimistic: false qos: 1 retain: true diff --git a/source/_integrations/luci.markdown b/source/_integrations/luci.markdown index f5b25501e19..fdcf6f2f5c4 100644 --- a/source/_integrations/luci.markdown +++ b/source/_integrations/luci.markdown @@ -1,7 +1,6 @@ --- title: OpenWRT (luci) description: Instructions on how to integrate OpenWRT routers into Home Assistant. -logo: openwrt.png ha_category: - Presence Detection ha_release: pre 0.7 diff --git a/source/_integrations/lupusec.markdown b/source/_integrations/lupusec.markdown index 86f9b84d3d8..df4d2ac387c 100644 --- a/source/_integrations/lupusec.markdown +++ b/source/_integrations/lupusec.markdown @@ -1,7 +1,6 @@ --- title: Lupus Electronics LUPUSEC description: Instructions on integrating Lupusec home security with Home Assistant. -logo: lupusec.png ha_category: - Hub - Alarm diff --git a/source/_integrations/mailgun.markdown b/source/_integrations/mailgun.markdown index e4414ce9370..730817b4986 100644 --- a/source/_integrations/mailgun.markdown +++ b/source/_integrations/mailgun.markdown @@ -1,7 +1,6 @@ --- title: Mailgun description: Instructions on how to add Mailgun mail notifications to Home Assistant. -logo: mailgun.png ha_category: - Notifications ha_release: 0.38 diff --git a/source/_integrations/matrix.markdown b/source/_integrations/matrix.markdown index dea7dbda403..898bed89e03 100644 --- a/source/_integrations/matrix.markdown +++ b/source/_integrations/matrix.markdown @@ -1,7 +1,6 @@ --- title: Matrix description: Matrix chatbot support -logo: matrix.png ha_category: - Hub - Notifications diff --git a/source/_integrations/meraki.markdown b/source/_integrations/meraki.markdown index 0c25fd67ca1..2659c91a794 100644 --- a/source/_integrations/meraki.markdown +++ b/source/_integrations/meraki.markdown @@ -1,7 +1,6 @@ --- title: Meraki description: Instructions on how to integrate Meraki-based presence detection into Home Assistant. -logo: meraki.png ha_category: - Presence Detection ha_release: '0.60' diff --git a/source/_integrations/mfi.markdown b/source/_integrations/mfi.markdown index ad369ac77b0..f8d6c4951ed 100644 --- a/source/_integrations/mfi.markdown +++ b/source/_integrations/mfi.markdown @@ -1,7 +1,6 @@ --- title: Ubiquiti mFi mPort description: Instructions on how to integrate mFi within Home Assistant. -logo: ubiquiti.png ha_category: - Network - Sensor diff --git a/source/_integrations/miflora.markdown b/source/_integrations/miflora.markdown index e1037cca244..e23bc0048ca 100644 --- a/source/_integrations/miflora.markdown +++ b/source/_integrations/miflora.markdown @@ -1,7 +1,6 @@ --- title: Mi Flora description: Instructions on how to integrate MiFlora BLE plant sensor with Home Assistant. -logo: miflora.png ha_category: - Environment ha_release: 0.29 diff --git a/source/_integrations/mqtt.markdown b/source/_integrations/mqtt.markdown index 290d2d79b53..e71be99f986 100644 --- a/source/_integrations/mqtt.markdown +++ b/source/_integrations/mqtt.markdown @@ -16,7 +16,9 @@ MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things 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. +The preferred way to setup MQTT for your installation is via **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **MQTT**. + +Alternatively, if you want to manually configure MQTT, you will need to add the following to your `configuration.yaml` file. To connect to your [own MQTT broker](/docs/mqtt/broker#run-your-own): diff --git a/source/_integrations/mqtt_eventstream.markdown b/source/_integrations/mqtt_eventstream.markdown index ce6eab477bb..e24cbc36ae4 100644 --- a/source/_integrations/mqtt_eventstream.markdown +++ b/source/_integrations/mqtt_eventstream.markdown @@ -1,7 +1,6 @@ --- title: MQTT Eventstream description: Instructions on how to setup MQTT eventstream within Home Assistant. -logo: mqtt.png ha_category: - Other ha_release: 0.11 diff --git a/source/_integrations/mqtt_json.markdown b/source/_integrations/mqtt_json.markdown index 0ab8730c6c6..5be1cc5ad48 100644 --- a/source/_integrations/mqtt_json.markdown +++ b/source/_integrations/mqtt_json.markdown @@ -1,7 +1,6 @@ --- title: MQTT JSON description: Instructions on how to use JSON MQTT to track devices in Home Assistant. -logo: mqtt.png ha_category: - Presence Detection ha_iot_class: Configurable diff --git a/source/_integrations/mqtt_room.markdown b/source/_integrations/mqtt_room.markdown index 93e7f3d563e..43ed9ecad9e 100644 --- a/source/_integrations/mqtt_room.markdown +++ b/source/_integrations/mqtt_room.markdown @@ -1,7 +1,6 @@ --- title: MQTT Room Presence description: Instructions on how to track room presence within Home Assistant. -logo: mqtt.png ha_category: - Presence Detection ha_release: 0.27 diff --git a/source/_integrations/mqtt_statestream.markdown b/source/_integrations/mqtt_statestream.markdown index 2e1453a6038..15c27e6ce97 100644 --- a/source/_integrations/mqtt_statestream.markdown +++ b/source/_integrations/mqtt_statestream.markdown @@ -1,7 +1,6 @@ --- title: MQTT Statestream description: Instructions on how to setup MQTT Statestream within Home Assistant. -logo: mqtt.png ha_category: - Other ha_release: 0.54 diff --git a/source/_integrations/mycroft.markdown b/source/_integrations/mycroft.markdown index 23934118d83..833a013367b 100644 --- a/source/_integrations/mycroft.markdown +++ b/source/_integrations/mycroft.markdown @@ -1,7 +1,6 @@ --- title: Mycroft description: Instructions on how to setup Mycroft AI within Home Assistant. -logo: mycroft.png ha_category: - Voice - Notifications diff --git a/source/_integrations/nanoleaf.markdown b/source/_integrations/nanoleaf.markdown index 2fd39e57b03..c8707f4e5fa 100644 --- a/source/_integrations/nanoleaf.markdown +++ b/source/_integrations/nanoleaf.markdown @@ -1,7 +1,6 @@ --- title: Nanoleaf description: Instructions how to integrate Nanoleaf Light Panels into Home Assistant. -logo: nanoleaf_light.png ha_category: - Light ha_iot_class: Local Polling diff --git a/source/_integrations/netgear.markdown b/source/_integrations/netgear.markdown index 46ec42f856a..fb52ccfaab9 100644 --- a/source/_integrations/netgear.markdown +++ b/source/_integrations/netgear.markdown @@ -1,7 +1,6 @@ --- title: NETGEAR description: Instructions on how to integrate NETGEAR routers into Home Assistant. -logo: netgear.png ha_category: - Presence Detection ha_iot_class: Local Polling diff --git a/source/_integrations/netgear_lte.markdown b/source/_integrations/netgear_lte.markdown index bfb0e56f9b9..b7c9379a319 100644 --- a/source/_integrations/netgear_lte.markdown +++ b/source/_integrations/netgear_lte.markdown @@ -1,7 +1,6 @@ --- title: NETGEAR LTE description: Instructions on how to integrate your NETGEAR LTE modem within Home Assistant. -logo: netgear.png ha_release: 0.72 ha_category: - Network diff --git a/source/_integrations/nexia.markdown b/source/_integrations/nexia.markdown index a0d99ab0e87..cadb3bdbe09 100644 --- a/source/_integrations/nexia.markdown +++ b/source/_integrations/nexia.markdown @@ -77,6 +77,12 @@ The following binary sensors are added for each thermostat zone: The `nexia` climate platform lets you control a thermostat. +The following thermostats are supported: `XL1050`, `XL850`, `XL824` + +The following thermostats are not supported: `XL624` + +Other thermostats may work, but they have not been tested. + ### Scene The `nexia` scene platform lets you activate a nexia automation. diff --git a/source/_integrations/nextcloud.markdown b/source/_integrations/nextcloud.markdown index 87be2c0b906..100a959f141 100644 --- a/source/_integrations/nextcloud.markdown +++ b/source/_integrations/nextcloud.markdown @@ -12,7 +12,7 @@ ha_codeowners: The `nextcloud` integration pulls summary [Nextcloud](https://nextcloud.com/) information into Home Assistant. -![Nextcloud Example Sensor]('/images/screenshots/nextcloud-sample-sensor.png') +![Nextcloud Example Sensor](/images/screenshots/nextcloud-sample-sensor.png) ## Configuration diff --git a/source/_integrations/niko_home_control.markdown b/source/_integrations/niko_home_control.markdown index f2a1ef75d67..aa7533260ba 100644 --- a/source/_integrations/niko_home_control.markdown +++ b/source/_integrations/niko_home_control.markdown @@ -1,7 +1,6 @@ --- title: Niko Home Control description: Instructions on how to integrate Niko Home Control lights into Home Assistant. -logo: niko.png ha_category: - Light ha_iot_class: Local Polling diff --git a/source/_integrations/notion.markdown b/source/_integrations/notion.markdown index 9a3ca95e265..561446e4745 100644 --- a/source/_integrations/notion.markdown +++ b/source/_integrations/notion.markdown @@ -1,7 +1,6 @@ --- title: Notion description: How to integrate Notion kits within Home Assistant. -logo: notion.png ha_category: - Hub - Binary Sensor diff --git a/source/_integrations/onvif.markdown b/source/_integrations/onvif.markdown index cfafe9eeafd..918ac0d02dc 100644 --- a/source/_integrations/onvif.markdown +++ b/source/_integrations/onvif.markdown @@ -1,7 +1,6 @@ --- title: ONVIF description: Instructions on how to integrate a ONVIF camera within Home Assistant. -logo: onvif.png ha_category: - Camera ha_release: 0.47 diff --git a/source/_integrations/opensky.markdown b/source/_integrations/opensky.markdown index 833cca573ff..e20a4689b34 100644 --- a/source/_integrations/opensky.markdown +++ b/source/_integrations/opensky.markdown @@ -1,7 +1,6 @@ --- title: OpenSky Network description: Instructions on how to integrate OpenSky Network into Home Assistant. -logo: opensky.png ha_category: - Transport ha_release: 0.43 diff --git a/source/_integrations/openweathermap.markdown b/source/_integrations/openweathermap.markdown index c72d30c3e39..e319b7875a7 100644 --- a/source/_integrations/openweathermap.markdown +++ b/source/_integrations/openweathermap.markdown @@ -93,7 +93,7 @@ forecast: description: Enables the forecast. The default is to display the current conditions. required: false default: false - type: string + type: boolean language: description: The language in which you want text results to be returned. It's a two-characters string, e.g., `en`, `es`, `ru`, `it`, etc. required: false diff --git a/source/_integrations/opnsense.markdown b/source/_integrations/opnsense.markdown index 8a59c1c6080..991bb74d550 100644 --- a/source/_integrations/opnsense.markdown +++ b/source/_integrations/opnsense.markdown @@ -23,7 +23,7 @@ to your configuration.yaml: ```yaml opnsense: - url: http://router/api + url: https://router/api api_secret: API_SECRET api_key: API_KEY ``` diff --git a/source/_integrations/orangepi_gpio.markdown b/source/_integrations/orangepi_gpio.markdown index 4ec19164383..b0e4fb930de 100644 --- a/source/_integrations/orangepi_gpio.markdown +++ b/source/_integrations/orangepi_gpio.markdown @@ -1,5 +1,5 @@ --- -title: Orangepi GPIO +title: Orange Pi GPIO description: Instructions on how to integrate the GPIO capability of a Orange Pi into Home Assistant. ha_category: - DIY @@ -13,11 +13,11 @@ ha_domain: orangepi_gpio The `orangepi_gpio` integration is the base for all related GPIO platforms in Home Assistant. There is no setup needed for the integration itself, for the platforms please check their corresponding pages. -## Binary Sensor +This integration provides the following platforms: -The `orangepi_gpio` binary sensor platform allows you to read sensor values of the GPIOs of your Orange Pi or NanoPi. +- Binary sensor: The `orangepi_gpio` binary sensor platform allows you to read sensor values of the GPIOs of your Orange Pi or NanoPi. -## Configuration +### Configuration To use your Orange Pi's GPIO in your installation, add the following to your `configuration.yaml` file: @@ -79,6 +79,7 @@ As this platform supports different types of GPIO pinouts for difference Orange | `neocore2` | Supports the NanoPi Neocore 2 | ## Additional steps + This integration uses the `SYSFS` filesystem to get control of the GPIOs. Therefore an operating system with `CONFIG_GPIO_SYSFS` is required. As far as I know, most out-of-the-box distributions still enable this by default. As of Linux 4.8 sysfs-gpio is marked as obsolete. However as of today, the alternative GPIO character device is not widely used. Therefore we will use this until the new character device is more widely supported. @@ -92,3 +93,31 @@ SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'find -L /sys/class/gpio/ -maxdepth 2 -e ``` Home Assistant will now be able to control your GPIO pins. + +## Limitations + +This integration uses interrupts to catch changes on your pins. However, it depends on the Allwinner chipset which pin banks support external interrupts. There is also a great difference between Orange Pi models which pins are routed to the GPIO connector. Therefore it greatly differs between devices which pins you can use for your sensors. + +You can find the pinouts of all the supported Orange Pi devices [here](https://pascalroeleven.nl/2020/04/13/orange-pi-gpio-pinouts/). The pinouts for the [NanoPi Duo](http://wiki.friendlyarm.com/wiki/index.php/NanoPi_Duo) and [NanoPi NEO Core2](http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Core2) can be found on the [FriendlyARM wiki](http://wiki.friendlyarm.com/). For example: If a pin is named PA01, the pin bank is PA. If this pin bank is in the following table after your chipset, this particular pin is supported. + +| Chipset | Pin banks which support external interrupts | +| ------- | ------------------------------------------- | +| H2+ | PA, PG, PL | +| H3 | PA, PG, PL | +| H5 | PA, PF, PG, PL | +| H6 | PF, PG, PH, PL, PM | +| A64 | PB, PG, PH, PL | + +In the table below you can see the number of usable pins for sensors per device. + +| Device | Usable pins | +| ----- | ----------- | +| H2+ (R1, Zero) | 17/17 | +| H3 (Lite, One, PC, PC Plus, Plus 2E) | 21/28 | +| H5 (Zero Plus) | 17/17 | +| H5 (Zero Plus 2) | 15/17 | +| H5 (PC 2) | 22/28 | +| H5 (Prime) | 17/28 | +| H6 (Lite 2, One Plus) | 3/17 | +| H6 (PI 3) | 8/17 | +| A64 (Win Plus) | 18/28 | diff --git a/source/_integrations/orvibo.markdown b/source/_integrations/orvibo.markdown index 61a8d7e0985..ebf9b0cd1e5 100644 --- a/source/_integrations/orvibo.markdown +++ b/source/_integrations/orvibo.markdown @@ -1,7 +1,6 @@ --- title: Orvibo description: Instructions on how to integrate Orvibo sockets within Home Assistant. -logo: orvibo.png ha_category: - Switch ha_release: 0.8 diff --git a/source/_integrations/panasonic_bluray.markdown b/source/_integrations/panasonic_bluray.markdown index 75531dc0bad..89dda0c7c06 100644 --- a/source/_integrations/panasonic_bluray.markdown +++ b/source/_integrations/panasonic_bluray.markdown @@ -1,7 +1,6 @@ --- title: Panasonic Blu-Ray Player description: Instructions on how to integrate a Panasonic Blu-Ray player into Home Assistant. -logo: panasonic.png ha_category: - Media Player ha_iot_class: Local Polling diff --git a/source/_integrations/panasonic_viera.markdown b/source/_integrations/panasonic_viera.markdown index d8185528e23..6761443451e 100644 --- a/source/_integrations/panasonic_viera.markdown +++ b/source/_integrations/panasonic_viera.markdown @@ -1,7 +1,6 @@ --- title: Panasonic Viera TV description: Instructions on how to integrate a Panasonic Viera TV into Home Assistant. -logo: panasonic.png ha_category: - Media Player ha_release: 0.17 diff --git a/source/_integrations/pandora.markdown b/source/_integrations/pandora.markdown index bf7a7532fd1..fe1e5ba944b 100644 --- a/source/_integrations/pandora.markdown +++ b/source/_integrations/pandora.markdown @@ -1,7 +1,6 @@ --- title: Pandora description: Instructions on how to integrate Pandora radio into Home Assistant. -logo: pandora.png ha_category: - Media Player ha_release: 0.22 diff --git a/source/_integrations/philips_js.markdown b/source/_integrations/philips_js.markdown index 3c31b13d14a..64cca223de2 100644 --- a/source/_integrations/philips_js.markdown +++ b/source/_integrations/philips_js.markdown @@ -1,7 +1,6 @@ --- title: Philips TV description: Instructions on how to add Philips TVs to Home Assistant. -logo: philips.png ha_category: - Media Player ha_iot_class: Local Polling diff --git a/source/_integrations/pilight.markdown b/source/_integrations/pilight.markdown index 0ecc2b2397f..6218a4b0a1f 100644 --- a/source/_integrations/pilight.markdown +++ b/source/_integrations/pilight.markdown @@ -1,7 +1,6 @@ --- title: Pilight description: Instructions on how to setup Pilight within Home Assistant. -logo: pilight.png ha_category: - DIY - Binary Sensor diff --git a/source/_integrations/proxmoxve.markdown b/source/_integrations/proxmoxve.markdown index f65b274ec56..c190434bf84 100644 --- a/source/_integrations/proxmoxve.markdown +++ b/source/_integrations/proxmoxve.markdown @@ -138,7 +138,7 @@ To apply the user and role just created, we need to give it permissions * Click `Datacenter` * Click `Permissions` * Open `Add` and click `User Permission` -* Select "\" for the path +* Select "/" for the path * Select your Home Assistant user (`hass`) * Select the Home Assistant role (`home-assistant`) * Make sure `Propigate` is checked diff --git a/source/_integrations/pulseaudio_loopback.markdown b/source/_integrations/pulseaudio_loopback.markdown index e701ae2f19b..0d7b4a6bcd0 100644 --- a/source/_integrations/pulseaudio_loopback.markdown +++ b/source/_integrations/pulseaudio_loopback.markdown @@ -1,7 +1,6 @@ --- title: PulseAudio Loopback description: Instructions on how to use Pulseaudio loopback modules to build a flexible whole-home audio system. -logo: pulseaudio.png ha_category: - Switch ha_release: 0.16 diff --git a/source/_integrations/pushover.markdown b/source/_integrations/pushover.markdown index 4581aeca170..709632a9cfd 100644 --- a/source/_integrations/pushover.markdown +++ b/source/_integrations/pushover.markdown @@ -58,9 +58,25 @@ Component specific values in the nested `data` section are optional. Image attachments can be added using the `attachment` parameter, which can either be a valid URL for an image (ex: `http://example.com/image.png`) or a local file reference (ex: `/tmp/image.png`). +To use a specific Pushover device, set it using `target`. If one of the entered devices doesn't exist or is disabled in your Pushover account it will send a message to all you devices. To send to all devices, just skip the target attribute. + +```yaml +- service: notify.entity_id + data: + message: "This is the message" + title: "Title of message" + target: + - pixel3 + - pixel4a + data: + sound: pianobar + priority: 0 +``` + + To use notifications, please see the [getting started with automation page](/getting-started/automation/). -When sending a notification, optional parameters can also be set as per the pushover [API documentation](https://pushover.net/api). +When sending a notification, optional parameters can also be set as per the Pushover [API documentation](https://pushover.net/api). Example notification triggered from the Alexa integration for an intents is shown below which also uses [Automation Templating](/getting-started/automation-templating/) for the message: @@ -77,9 +93,9 @@ alexa: message: "The location of {{ User }} has been queried via Alexa." data: title: "Home Assistant" + target: pixel data: sound: falling - device: pixel url: "https://www.home-assistant.io/" attachment: "/tmp/image.png" ``` diff --git a/source/_integrations/rainbird.markdown b/source/_integrations/rainbird.markdown index 6ed3cbdf444..a87ac1922be 100644 --- a/source/_integrations/rainbird.markdown +++ b/source/_integrations/rainbird.markdown @@ -1,7 +1,6 @@ --- title: Rain Bird description: Instructions on how to integrate your Rain Bird LNK WiFi Module within Home Assistant. -logo: rainbird.png ha_category: - Irrigation - Sensor diff --git a/source/_integrations/raspihats.markdown b/source/_integrations/raspihats.markdown index 85f65646b80..e5962769610 100644 --- a/source/_integrations/raspihats.markdown +++ b/source/_integrations/raspihats.markdown @@ -1,7 +1,6 @@ --- title: Raspihats description: Instructions on how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant. -logo: raspihats.png ha_category: - DIY - Binary Sensor diff --git a/source/_integrations/rejseplanen.markdown b/source/_integrations/rejseplanen.markdown index a7ee68fe009..7c41be042f9 100644 --- a/source/_integrations/rejseplanen.markdown +++ b/source/_integrations/rejseplanen.markdown @@ -1,7 +1,6 @@ --- title: Rejseplanen description: Instructions on how to integrate timetable data for Danish Rejseplanen within Home Assistant. -logo: rejseplanen.png ha_category: - Transport ha_iot_class: Cloud Polling diff --git a/source/_integrations/remember_the_milk.markdown b/source/_integrations/remember_the_milk.markdown index 715a955ce0e..50adcc6f32a 100644 --- a/source/_integrations/remember_the_milk.markdown +++ b/source/_integrations/remember_the_milk.markdown @@ -1,14 +1,13 @@ --- title: Remember The Milk description: Instructions on how to use Remember The Milk with Home Assistant. -logo: rememberthemilk.png ha_category: - Calendar ha_release: 0.57 ha_domain: remember_the_milk --- -The `Remember The Milk` (RTM) integration allows you to create tasks in [remember_the_milk](https://www.rememberthemilk.com) from Home Assistant. You can use this if you want Home Assistant to send you a task that you should not forget, e.g., water the plants. The integration allows you to have several RTM accounts in parallel. +The `remember_the_milk` integration allows you to create tasks in [Remember The Milk (RTM)](https://www.rememberthemilk.com) from Home Assistant. You can use this if you want Home Assistant to send you a task that you should not forget, e.g., water the plants. The integration allows you to have several RTM accounts in parallel. ## Setup @@ -16,7 +15,7 @@ The setup consists of two steps: getting an API key and registering your account ### Step 1: API key -To be able to use this component, you need a Remember The Milk account and you need to apply for your own [API key](https://www.rememberthemilk.com/services/api/keys.rtm). With the API key you will also receive your personal `shared secret`. Both of them need to be stored in your Home Assistant configuration: +To be able to use this integration, you need a Remember The Milk account and you need to apply for your own [API key](https://www.rememberthemilk.com/services/api/keys.rtm). With the API key you will also receive your personal shared secret. Both of them need to be stored in your Home Assistant configuration: ```yaml # Example configuration.yaml entry @@ -43,7 +42,7 @@ remember_the_milk: type: string {% endconfiguration %} -### Step 2: registering your account +### Step 2: Registering your account After saving the configuration, you need to (re-)start Home Assistant. On the first start you will notice a new "Configuration" panel appearing on the Home Assistant page. After opening the configuration page, follow the link "Remember The Milk login". This will take you to a login page where you have to log in with your normal Remember The Milk credentials. This will authorize Home Assistant to access your Remember The Milk account. @@ -53,13 +52,13 @@ If the registration was successful, the Configuration panel will disappear from In the background Home Assistant downloaded a "token" from the Remember The Milk server which is stored in the `remember_the_milk.conf` file locally. So you only need to register once. After that the token is used to authenticate with the server. -## Creating/updating tasks with service ```create_task``` +## Creating/updating tasks with service `create_task` -This integration offers a new service domain ```remember_the_milk``` with the services ```_create_task```. You can call this service with the argument ```name``` and the optional parameter ```id``` to create a new task in your Remember The Milk account. You can call this service from your usual automations. +This integration offers a new service domain `remember_the_milk` with the services `_create_task`. You can call this service with the argument `name` and the optional parameter `id` to create a new task in your Remember The Milk account. You can call this service from your usual automations. -If you set an ```id``` and a task with that id exists already, the existing task is updated, rather than creating a new task. This way you can change the name of the task. If you do not set an ```id```, a new task is created with every call. If you're using this from an automation, you could use the name of your automation as id or the entity that triggered the task to be created. This way you can later on update or complete this task. +If you set an `id` and a task with that id exists already, the existing task is updated, rather than creating a new task. This way you can change the name of the task. If you do not set an `id`, a new task is created with every call. If you're using this from an automation, you could use the name of your automation as id or the entity that triggered the task to be created. This way you can later on update or complete this task. -The task creation supports the "smart syntax", so to create a task with the tag "from_hass" which is due today you can create a task with the name ```test task created in Home Assistant ^today #from_hass```. More info about the smart syntax is available on the [Remember The Milk documentation](https://www.rememberthemilk.com/help/answer/basics-smartadd-howdoiuse). +The task creation supports the "smart syntax", so to create a task with the tag "from_hass" which is due today you can create a task with the name `test task created in Home Assistant ^today #from_hass`. More info about the smart syntax is available on the [Remember The Milk documentation](https://www.rememberthemilk.com/help/answer/basics-smartadd-howdoiuse). **Note:** At the moment, smart syntax is *not* supported when updating tasks. All smart syntax commands are ignored during the update and will end up as normal text in the name of the task. @@ -69,11 +68,11 @@ At the moment, smart syntax is *not* supported when updating tasks. All smart sy | name | no | Name of the new task, you can use the smart syntax here. | "do this ^today #from_hass" | | id | yes | Identifier for the task you're creating, can be used to update or complete the task later on | "myid" | -## Completing tasks with service ```complete_task``` +## Completing tasks with service `complete_task` Complete a tasks that was privously created from Home Assistant. You can not complete tasks that were created outside of Home Assistant. -If you have created your task with an ```id```, calling ```_complete_task``` with the parameter ```id``` will then complete your task. +If you have created your task with an `id`, calling `_complete_task` with the parameter `id` will then complete your task. |Service data attribute | Optional | Description | Example | |-----------------------|----------|-------------|---------| @@ -81,7 +80,9 @@ If you have created your task with an ```id```, calling ```_complete_ta ## Automation example -Here's an example for an automation that creates a new task whenever ```sensor.mysensor``` is ```on``` and completes it when the sensor reports ```off```. This way it reminds you to switch it off. By using the ```entity_id``` as id for the task, you can use the same rule also for multiple sensors. +Here's an example for an automation that creates a new task whenever `sensor.mysensor` is `on` and completes it when the sensor reports `off`. This way it reminds you to switch it off. By using the `entity_id` as ID for the task, you can use the same rule also for multiple sensors. + +{% raw %} ```yaml - id: mysensor_on @@ -105,7 +106,8 @@ Here's an example for an automation that creates a new task whenever ```sensor.m id: "{{trigger.entity_id}}" ``` +{% endraw %} ## Disclaimer -This product uses the Remember The Milk API but is not endorsed or certified by Remember The Milk. +This integration uses the Remember The Milk API but is not endorsed or certified by Remember The Milk. diff --git a/source/_integrations/saj.markdown b/source/_integrations/saj.markdown index f1187fb95ca..ffc6737d7a7 100644 --- a/source/_integrations/saj.markdown +++ b/source/_integrations/saj.markdown @@ -3,7 +3,6 @@ title: SAJ Solar Inverter description: Instructions on how to connect your SAJ Solar Inverter to Home Assistant. ha_category: - Energy -logo: saj.png ha_iot_class: Local Polling ha_release: '0.100' ha_codeowners: diff --git a/source/_integrations/samsungtv.markdown b/source/_integrations/samsungtv.markdown index 25146d07c1e..0b56194558e 100644 --- a/source/_integrations/samsungtv.markdown +++ b/source/_integrations/samsungtv.markdown @@ -111,6 +111,7 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am - KU6290 - KU6400U - KU6470 +- KU6500 (on working with WOL) - KU7000 - M5620 - MU6170UXZG diff --git a/source/_integrations/satel_integra.markdown b/source/_integrations/satel_integra.markdown index b0bfaa4cf90..7a6ae977b30 100644 --- a/source/_integrations/satel_integra.markdown +++ b/source/_integrations/satel_integra.markdown @@ -1,7 +1,6 @@ --- title: Satel Integra description: Instructions on how to integrate a Satel Integra alarm panel with Home Assistant using an ETHM network extension from Satel. -logo: satel.jpg ha_category: - Hub - Alarm diff --git a/source/_integrations/slack.markdown b/source/_integrations/slack.markdown index 1d64eb376dc..23459d1d177 100644 --- a/source/_integrations/slack.markdown +++ b/source/_integrations/slack.markdown @@ -95,7 +95,7 @@ Example for using the block framework: message: Message that will be added as a comment to the file. title: Title of the file. data: - attachments: + blocks: - type: section text: type: mrkdwn diff --git a/source/_integrations/sleepiq.markdown b/source/_integrations/sleepiq.markdown index 9fcae8edbf4..6ca83f79130 100644 --- a/source/_integrations/sleepiq.markdown +++ b/source/_integrations/sleepiq.markdown @@ -1,7 +1,6 @@ --- title: SleepIQ description: Instructions for how to integrate SleepIQ beds within Home Assistant. -logo: sleepiq.png ha_category: - Health - Sensor diff --git a/source/_integrations/smarty.markdown b/source/_integrations/smarty.markdown index 6f8747d1f55..4cc73ca5691 100644 --- a/source/_integrations/smarty.markdown +++ b/source/_integrations/smarty.markdown @@ -1,7 +1,6 @@ --- title: Salda Smarty description: Instructions on how to integrate Salda Smarty 2X/3X/4X P/V ventilation systems into Home Assistant. -logo: salda.png ha_category: - Hub - Fan diff --git a/source/_integrations/smhi.markdown b/source/_integrations/smhi.markdown index 8195f15145e..f47effef8bd 100644 --- a/source/_integrations/smhi.markdown +++ b/source/_integrations/smhi.markdown @@ -1,7 +1,6 @@ --- title: SMHI description: Instructions on how to integrate SMHI forecasts within Home Assistant. -logo: smhi.png ha_category: - Hub - Weather diff --git a/source/_integrations/soundtouch.markdown b/source/_integrations/soundtouch.markdown index b7c107c9cc6..c4c8e416d5f 100644 --- a/source/_integrations/soundtouch.markdown +++ b/source/_integrations/soundtouch.markdown @@ -1,7 +1,6 @@ --- title: Bose Soundtouch description: Instructions on how to integrate Bose Soundtouch devices into Home Assistant. -logo: soundtouch.png ha_category: - Media Player ha_release: 0.34 diff --git a/source/_integrations/telegram.markdown b/source/_integrations/telegram.markdown index 67b0991aff0..363c1c9fde6 100644 --- a/source/_integrations/telegram.markdown +++ b/source/_integrations/telegram.markdown @@ -288,9 +288,9 @@ action: document: file: /tmp/whatever.odf caption: Document Title xy - keyboard: - - '/command1, /command2' - - '/command3, /command4' + keyboard: + - '/command1, /command2' + - '/command3, /command4' ``` {% configuration %} diff --git a/source/_integrations/tmb.markdown b/source/_integrations/tmb.markdown index 8d0c8533223..6a2c2bc1f98 100644 --- a/source/_integrations/tmb.markdown +++ b/source/_integrations/tmb.markdown @@ -1,7 +1,6 @@ --- title: Transports Metropolitans de Barcelona description: Instructions on how to integrate TMB iBus sensor within Home Assistant. -logo: tmb.png ha_category: - Transport ha_release: 0.104 diff --git a/source/_integrations/torque.markdown b/source/_integrations/torque.markdown index fb72efccf26..a07e96d2008 100644 --- a/source/_integrations/torque.markdown +++ b/source/_integrations/torque.markdown @@ -1,7 +1,6 @@ --- title: Torque description: Instructions on how to integrate Torque sensors into Home Assistant. -logo: torque.png ha_category: - Car ha_release: '0.10' diff --git a/source/_integrations/touchline.markdown b/source/_integrations/touchline.markdown index 32353bd9fe9..d488e6b5039 100644 --- a/source/_integrations/touchline.markdown +++ b/source/_integrations/touchline.markdown @@ -1,7 +1,6 @@ --- title: Roth Touchline description: Instructions on how to integrate Roth Touchline within Home Assistant. -logo: roth.png ha_category: - Climate ha_release: 0.61 diff --git a/source/_integrations/transport_nsw.markdown b/source/_integrations/transport_nsw.markdown index 8d2cbaf7d09..0b2f540dd3f 100644 --- a/source/_integrations/transport_nsw.markdown +++ b/source/_integrations/transport_nsw.markdown @@ -1,7 +1,6 @@ --- title: Transport NSW description: Instructions on how to integrate timetable data for Transport NSW (Australia) within Home Assistant. -logo: transport_nsw.png ha_category: - Transport ha_iot_class: Cloud Polling diff --git a/source/_integrations/tuya.markdown b/source/_integrations/tuya.markdown index bd95d59a855..2994a3ee577 100644 --- a/source/_integrations/tuya.markdown +++ b/source/_integrations/tuya.markdown @@ -1,7 +1,6 @@ --- title: Tuya description: Instructions on how to setup the Tuya hub within Home Assistant. -logo: tuya.png ha_category: - Hub - Climate diff --git a/source/_integrations/twentemilieu.markdown b/source/_integrations/twentemilieu.markdown index a9bcecc16d6..c439aad85ef 100644 --- a/source/_integrations/twentemilieu.markdown +++ b/source/_integrations/twentemilieu.markdown @@ -1,7 +1,6 @@ --- title: Twente Milieu description: Instructions on how to integrate Twente Milieu with Home Assistant. -logo: twentemilieu.png ha_category: - Sensor - Environment diff --git a/source/_integrations/ubee.markdown b/source/_integrations/ubee.markdown index 51683c4eeb3..d106181b596 100644 --- a/source/_integrations/ubee.markdown +++ b/source/_integrations/ubee.markdown @@ -1,7 +1,6 @@ --- title: Ubee Router description: Instructions on how to integrate Ubee routers into Home Assistant. -logo: ubee.png ha_category: - Presence Detection ha_release: 0.89 diff --git a/source/_integrations/ubus.markdown b/source/_integrations/ubus.markdown index 79ffd41b488..5c101c5cdcd 100644 --- a/source/_integrations/ubus.markdown +++ b/source/_integrations/ubus.markdown @@ -1,7 +1,6 @@ --- title: OpenWrt (ubus) description: Instructions on how to integrate OpenWRT routers into Home Assistant. -logo: openwrt.png ha_category: - Presence Detection ha_release: 0.7.6 diff --git a/source/_integrations/ue_smart_radio.markdown b/source/_integrations/ue_smart_radio.markdown index 3055b1ba32e..3760786949b 100644 --- a/source/_integrations/ue_smart_radio.markdown +++ b/source/_integrations/ue_smart_radio.markdown @@ -1,7 +1,6 @@ --- title: Logitech UE Smart Radio description: Instructions on how to integrate a Logitech UE Smart Radio player into Home Assistant. -logo: ueradio.png ha_category: - Media Player ha_release: '0.60' diff --git a/source/_integrations/unifiled.markdown b/source/_integrations/unifiled.markdown index c39a8cc575e..b57c78c1b88 100644 --- a/source/_integrations/unifiled.markdown +++ b/source/_integrations/unifiled.markdown @@ -1,7 +1,6 @@ --- title: Ubiquiti UniFi LED description: Instructions on how to configure the UniFi LED integration with UniFi LED Controller by Ubiquiti. -logo: ubiquiti.png ha_category: - Light ha_release: 0.102 diff --git a/source/_integrations/uptimerobot.markdown b/source/_integrations/uptimerobot.markdown index d18b4cf82ea..63efc7bb666 100644 --- a/source/_integrations/uptimerobot.markdown +++ b/source/_integrations/uptimerobot.markdown @@ -1,7 +1,6 @@ --- title: Uptime Robot description: Instructions on how to set up Uptime Robot within Home Assistant. -logo: uptimerobot.png ha_category: - System Monitor ha_release: 0.72 diff --git a/source/_integrations/usgs_earthquakes_feed.markdown b/source/_integrations/usgs_earthquakes_feed.markdown index 49f2ae9911e..3ce7e4b9dcf 100644 --- a/source/_integrations/usgs_earthquakes_feed.markdown +++ b/source/_integrations/usgs_earthquakes_feed.markdown @@ -1,7 +1,6 @@ --- title: U.S. Geological Survey Earthquake Hazards (USGS) description: Instructions on how to integrate the U.S. Geological Survey Earthquake Hazards Program Feed feed into Home Assistant. -logo: us-geological-survey.png ha_category: - Geolocation ha_iot_class: Cloud Polling diff --git a/source/_integrations/uvc.markdown b/source/_integrations/uvc.markdown index c076f7ee627..c4abba9f5f0 100644 --- a/source/_integrations/uvc.markdown +++ b/source/_integrations/uvc.markdown @@ -1,7 +1,6 @@ --- title: Ubiquiti UniFi Video description: Instructions on how to integrate UVC cameras within Home Assistant. -logo: ubiquiti.png ha_category: - Camera ha_release: 0.13 diff --git a/source/_integrations/vasttrafik.markdown b/source/_integrations/vasttrafik.markdown index 5a93e80ea4a..419a7b6d5fe 100644 --- a/source/_integrations/vasttrafik.markdown +++ b/source/_integrations/vasttrafik.markdown @@ -1,7 +1,6 @@ --- title: Västtrafik description: Instructions on how to integrate timetable data for traveling in Sweden within Home Assistant. -logo: vasttrafik.png ha_category: - Transport ha_iot_class: Cloud Polling diff --git a/source/_integrations/velux.markdown b/source/_integrations/velux.markdown index c25eaac9adf..6aeca027e3c 100644 --- a/source/_integrations/velux.markdown +++ b/source/_integrations/velux.markdown @@ -1,7 +1,6 @@ --- title: Velux description: Instructions on how to integrate Velux KLF 200 integration with Home Assistant. -logo: velux.png ha_category: - Scene - Cover diff --git a/source/_integrations/venstar.markdown b/source/_integrations/venstar.markdown index d1793746f85..a9c49b96b98 100644 --- a/source/_integrations/venstar.markdown +++ b/source/_integrations/venstar.markdown @@ -1,7 +1,6 @@ --- title: Venstar description: Instructions for how to integrate Venstar WiFi thermostats within Home Assistant. -logo: venstar.png ha_category: - Climate ha_release: 0.62 diff --git a/source/_integrations/vera.markdown b/source/_integrations/vera.markdown index ece203cbaa8..cfe372f6484 100644 --- a/source/_integrations/vera.markdown +++ b/source/_integrations/vera.markdown @@ -1,7 +1,6 @@ --- title: Vera description: Instructions on how to setup Vera Z-Wave hubs and configure devices within Home Assistant. -logo: vera.png ha_category: - Hub - Binary Sensor diff --git a/source/_integrations/verisure.markdown b/source/_integrations/verisure.markdown index d16d01e6af1..edc50407aa4 100644 --- a/source/_integrations/verisure.markdown +++ b/source/_integrations/verisure.markdown @@ -1,7 +1,6 @@ --- title: Verisure description: Instructions on how to setup Verisure devices within Home Assistant. -logo: verisure.png ha_category: - Hub - Alarm diff --git a/source/_integrations/vicare.markdown b/source/_integrations/vicare.markdown index 40a7ab4af25..4bf6157de59 100644 --- a/source/_integrations/vicare.markdown +++ b/source/_integrations/vicare.markdown @@ -1,7 +1,6 @@ --- title: Viessmann ViCare description: Instructions how to integrate Viessmann heating devices with Home Assistant -logo: viessmann.png ha_category: Climate ha_release: 0.99 ha_iot_class: Cloud Polling diff --git a/source/_integrations/voicerss.markdown b/source/_integrations/voicerss.markdown index 92e07b85c8a..013a93f4bf7 100644 --- a/source/_integrations/voicerss.markdown +++ b/source/_integrations/voicerss.markdown @@ -1,7 +1,6 @@ --- title: VoiceRSS description: Instructions on how to setup VoiceRSS TTS with Home Assistant. -logo: voicerss.png ha_category: - Text-to-speech ha_release: 0.35 diff --git a/source/_integrations/volkszaehler.markdown b/source/_integrations/volkszaehler.markdown index 7c194d7d48d..475c92a7d3c 100644 --- a/source/_integrations/volkszaehler.markdown +++ b/source/_integrations/volkszaehler.markdown @@ -1,7 +1,6 @@ --- title: Volkszaehler description: Instructions on how to integrate Volkszaehler sensors into Home Assistant. -logo: volkszaehler.png ha_category: - System Monitor ha_iot_class: Local Polling diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index 06319a62396..58eba00cba2 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -1,7 +1,6 @@ --- title: LG webOS Smart TV description: Instructions on how to integrate a LG webOS Smart TV within Home Assistant. -logo: webos.png ha_category: - Media Player - Notifications diff --git a/source/_integrations/yale_smart_alarm.markdown b/source/_integrations/yale_smart_alarm.markdown index 832633aed32..9f493012d93 100644 --- a/source/_integrations/yale_smart_alarm.markdown +++ b/source/_integrations/yale_smart_alarm.markdown @@ -1,7 +1,6 @@ --- title: Yale Smart Living description: Instructions on how to integrate Yale Smart Alarms into Home Assistant. -logo: yale.png ha_category: - Alarm ha_release: 0.78 diff --git a/source/_integrations/yamaha.markdown b/source/_integrations/yamaha.markdown index 4231c030500..3d4efcfa4d2 100644 --- a/source/_integrations/yamaha.markdown +++ b/source/_integrations/yamaha.markdown @@ -1,7 +1,6 @@ --- title: Yamaha Network Receivers description: Instructions on how to integrate Yamaha Network Receivers into Home Assistant. -logo: yamaha.png ha_category: - Media Player ha_release: 0.16 diff --git a/source/_integrations/yandex_transport.markdown b/source/_integrations/yandex_transport.markdown index 30b3ad55199..24c6c8e3dd9 100644 --- a/source/_integrations/yandex_transport.markdown +++ b/source/_integrations/yandex_transport.markdown @@ -1,7 +1,6 @@ --- title: Yandex Transport description: Instructions on how to set up Yandex transport with Home Assistant. -logo: yandex.png ha_category: - Sensor - Transport diff --git a/source/_integrations/yeelight.markdown b/source/_integrations/yeelight.markdown index 11f96266756..a2a5dbd0007 100644 --- a/source/_integrations/yeelight.markdown +++ b/source/_integrations/yeelight.markdown @@ -1,7 +1,6 @@ --- title: Yeelight description: Instructions on how to setup Yeelight Wifi devices within Home Assistant. -logo: yeelight.png ha_category: - Light ha_release: 0.32 diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index e62990d47cf..a44574bb9c5 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -33,6 +33,8 @@ There is currently support for the following device types within Home Assistant: - Sensor - Switch +There is also support for grouping of lights, switches, and fans (i.e. support for commanding device groups as entities). + ## ZHA exception and deviation handling Zigbee devices that deviate from or do not fully conform to the standard specifications set by the [Zigbee Alliance](https://zigbeealliance.org) may require the development of custom [ZHA Device Handlers](https://github.com/dmulcahey/zha-device-handlers) (ZHA custom quirks handler implementation) to for all their functions to work properly with the ZHA integration in Home Assistant. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. diff --git a/source/_integrations/zhong_hong.markdown b/source/_integrations/zhong_hong.markdown index ab023eeae9c..474927c8f6a 100644 --- a/source/_integrations/zhong_hong.markdown +++ b/source/_integrations/zhong_hong.markdown @@ -1,7 +1,6 @@ --- title: ZhongHong description: Instructions on how to integrate ZhongHong Support thermostats within Home Assistant. -logo: zhong_hong.png ha_category: - Climate ha_release: 0.72 diff --git a/source/_integrations/zigbee.markdown b/source/_integrations/zigbee.markdown index 9348dbd1157..e8b19ec0fcc 100644 --- a/source/_integrations/zigbee.markdown +++ b/source/_integrations/zigbee.markdown @@ -1,7 +1,6 @@ --- title: Zigbee description: Instructions on how to integrate a Zigbee network with Home Assistant. -logo: zigbee.png ha_category: - Binary Sensor - Light diff --git a/source/_integrations/zoneminder.markdown b/source/_integrations/zoneminder.markdown index 7c1c150afa6..5f4174e53f4 100644 --- a/source/_integrations/zoneminder.markdown +++ b/source/_integrations/zoneminder.markdown @@ -1,7 +1,6 @@ --- title: ZoneMinder description: How to integrate ZoneMinder into Home Assistant. -logo: zoneminder.png ha_category: - Hub - Binary Sensor diff --git a/source/_lovelace/entity-filter.markdown b/source/_lovelace/entity-filter.markdown index 3f6e6da06e5..34e932a96a3 100644 --- a/source/_lovelace/entity-filter.markdown +++ b/source/_lovelace/entity-filter.markdown @@ -94,7 +94,8 @@ attribute: ### Examples -Show only active switches or lights in the house +Show only active switches or lights in the house. + ```yaml type: entity-filter entities: @@ -121,7 +122,30 @@ card: title: People at home ``` -Specify filter for a single entity +

+ Entity filter combined with glance card + Entity filter combined with glance card. +

+ +You can also specify multiple `state_filter`s, in which case matching any condition will display the entity. This example will display everyone who isn't at home or at work. + +```yaml +type: entity-filter +entities: + - device_tracker.demo_paulus + - device_tracker.demo_anne_therese + - device_tracker.demo_home_boy +state_filter: + - operator: "!=" + value: home + - operator: "!=" + value: work +card: + type: glance + title: Who's Running Errands +``` + +Specify filter for a single entity. ```yaml type: entity-filter @@ -139,7 +163,22 @@ entities: attribute: humidity ``` -

- Entity filter combined with glance card - Entity filter combined with glance card. -

+Use a regex filter against entity attributes. This regex filter below looks for expressions that are 1 digit in length and where the number is between 0-7 (so show holidays today or in the next 7 days) and displays those holidays as entities in the entity-filter card. + +```yaml + - type: entity-filter + card: + title: "Upcoming Holidays In Next 7 Days" + show_header_toggle: false + state_filter: + - operator: regex + value: "^([0-7]{1})$" + attribute: eta + entities: + - entity: sensor.upcoming_ical_holidays_0 + - entity: sensor.upcoming_ical_holidays_1 + - entity: sensor.upcoming_ical_holidays_2 + - entity: sensor.upcoming_ical_holidays_3 + - entity: sensor.upcoming_ical_holidays_4 + show_empty: false +``` diff --git a/source/_posts/2020-04-08-release-108.markdown b/source/_posts/2020-04-08-release-108.markdown index 2daa0cdb0d1..ce2274a4596 100644 --- a/source/_posts/2020-04-08-release-108.markdown +++ b/source/_posts/2020-04-08-release-108.markdown @@ -82,7 +82,7 @@ to allow them to be configured via the Home Assistant frontend. Not all of them were ready in time for this release; nevertheless, the list is amazing already: - + - [Freebox][freebox docs], done by [@Quentame] - [Monoprice][monoprice docs], done by [@OnFreund] - [Roku][roku docs], done by [@ctalkington] @@ -141,7 +141,7 @@ Before and after screenshot for the Horizontal Stack improvements. ## Other noteworthy changes -- _**"Alexa, show the front door camera."**_ 😲 +- _**"Alexa, show the front door camera."**_ 😲 [Alexa][alexa docs] now has support for Cameras, thanks [@ochlocracy]! - Selecting your default Lovelace dashboard has been moved to the user @@ -157,7 +157,7 @@ Before and after screenshot for the Horizontal Stack improvements. - The Markdown card has a new `user` variable that can be used to display the currently logged in user. - + - With the ZHA Zigbee integration, Zigbee groups now dynamically create entities for lights, switches and fans that are grouped together. This enables near-simultaneous control over a large group of lights allowing @@ -295,6 +295,152 @@ Experiencing issues introduced by this release? Please report them in our [issue These integrations have been removed. The websites for both have changed, causing the integrations to break because they relied on web scraping, which is no longer allowed (ADR-0004). - ([@frenck] - [#33056] [#33066]) +## Release 0.108.1 - April 8 + +- Speed up TP-Link lights ([@balloob] - [#33606]) ([tplink docs]) +- Update sensor.py ([@danbishop] - [#33788]) ([octoprint docs]) +- Bump pylutron-caseta version to 0.6.1 ([@swails] - [#33815]) ([lutron_caseta docs]) +- Update to pyipp==0.9.1 ([@ctalkington] - [#33819]) ([ipp docs]) +- Fix unhandled exception in Recollect Waste ([@bachya] - [#33823]) ([recollect_waste docs]) +- Fix modbus transaction response ([@janiversen] - [#33824]) ([modbus docs]) +- Fix kef DSP_SCAN_INTERVAL timedelta ([@basnijholt] - [#33825]) ([kef docs]) +- Fix Doorbird yaml import aborted if discovery finds it first ([@bdraco] - [#33843]) ([doorbird docs]) +- Bump up ZHA dependencies ([@Adminiuga] - [#33856]) ([zha docs]) +- Fix vizio bug that occurs when CONF_APPS isn't in config entry… ([@raman325] - [#33857]) ([vizio docs]) +- TTS: Wait till files are created in tests ([@balloob] - [#33760]) ([tts docs]) +- Fix last flaky TTS test ([@balloob] - [#33849]) ([tts docs]) + +[#33606]: https://github.com/home-assistant/core/pull/33606 +[#33760]: https://github.com/home-assistant/core/pull/33760 +[#33788]: https://github.com/home-assistant/core/pull/33788 +[#33815]: https://github.com/home-assistant/core/pull/33815 +[#33819]: https://github.com/home-assistant/core/pull/33819 +[#33823]: https://github.com/home-assistant/core/pull/33823 +[#33824]: https://github.com/home-assistant/core/pull/33824 +[#33825]: https://github.com/home-assistant/core/pull/33825 +[#33843]: https://github.com/home-assistant/core/pull/33843 +[#33849]: https://github.com/home-assistant/core/pull/33849 +[#33856]: https://github.com/home-assistant/core/pull/33856 +[#33857]: https://github.com/home-assistant/core/pull/33857 +[@Adminiuga]: https://github.com/Adminiuga +[@bachya]: https://github.com/bachya +[@balloob]: https://github.com/balloob +[@basnijholt]: https://github.com/basnijholt +[@bdraco]: https://github.com/bdraco +[@ctalkington]: https://github.com/ctalkington +[@danbishop]: https://github.com/danbishop +[@janiversen]: https://github.com/janiversen +[@raman325]: https://github.com/raman325 +[@swails]: https://github.com/swails +[doorbird docs]: /integrations/doorbird/ +[ipp docs]: /integrations/ipp/ +[kef docs]: /integrations/kef/ +[lutron_caseta docs]: /integrations/lutron_caseta/ +[modbus docs]: /integrations/modbus/ +[octoprint docs]: /integrations/octoprint/ +[recollect_waste docs]: /integrations/recollect_waste/ +[tplink docs]: /integrations/tplink/ +[tts docs]: /integrations/tts/ +[vizio docs]: /integrations/vizio/ +[zha docs]: /integrations/zha/ + +## Release 0.108.2 - April 9 + +- Improve Plex debounce/throttle logic ([@jjlawren] - [#33805]) ([plex docs]) +- Update aioswitcher ([@balloob] - [#33821]) ([switcher_kis docs]) +- Fix nextcloud sensor mappings ([@L-Henke] - [#33840]) ([nextcloud docs]) +- Check status code on onvif snapshot ([@balloob] - [#33865]) ([onvif docs]) +- Fix Monoprice robustness ([@OnFreund] - [#33869]) ([monoprice docs]) +- Fix modbus default delay ([@janiversen] - [#33877]) ([modbus docs]) +- Updated frontend to 20200407.2 ([@bramkragten] - [#33891]) ([frontend docs]) +- Fix onvif consistent return ([@balloob] - [#33898]) ([onvif docs]) +- Modbus: isolate common test functions ([@janiversen] - [#33447]) +- Fix Modbus review comments ([@janiversen] - [#33755]) ([modbus docs]) +- Rename domain import in modbus ([@janiversen] - [#33906]) ([modbus docs]) +- Fix tplink HS220 dimmers ([@bdraco] - [#33909]) ([tplink docs]) +- Exclude access token from host info updates in Konnected config flow ([@kit-klein] - [#33912]) ([konnected docs]) +- Bump pyvizio version for vizio ([@raman325] - [#33924]) ([vizio docs]) +- Fix tplink HS220 dimmers (round 2) ([@bdraco] - [#33928]) ([tplink docs]) +- Guard IPP against negative ink levels ([@ctalkington] - [#33931]) ([ipp docs]) +- Remove print() from Bayesian Binary Sensor ([@carlos-sarmiento] - [#33916]) ([bayesian docs]) + +[#33447]: https://github.com/home-assistant/core/pull/33447 +[#33755]: https://github.com/home-assistant/core/pull/33755 +[#33805]: https://github.com/home-assistant/core/pull/33805 +[#33821]: https://github.com/home-assistant/core/pull/33821 +[#33840]: https://github.com/home-assistant/core/pull/33840 +[#33865]: https://github.com/home-assistant/core/pull/33865 +[#33869]: https://github.com/home-assistant/core/pull/33869 +[#33877]: https://github.com/home-assistant/core/pull/33877 +[#33891]: https://github.com/home-assistant/core/pull/33891 +[#33898]: https://github.com/home-assistant/core/pull/33898 +[#33906]: https://github.com/home-assistant/core/pull/33906 +[#33909]: https://github.com/home-assistant/core/pull/33909 +[#33912]: https://github.com/home-assistant/core/pull/33912 +[#33916]: https://github.com/home-assistant/core/pull/33916 +[#33924]: https://github.com/home-assistant/core/pull/33924 +[#33928]: https://github.com/home-assistant/core/pull/33928 +[#33931]: https://github.com/home-assistant/core/pull/33931 +[@L-Henke]: https://github.com/L-Henke +[@OnFreund]: https://github.com/OnFreund +[@balloob]: https://github.com/balloob +[@bdraco]: https://github.com/bdraco +[@bramkragten]: https://github.com/bramkragten +[@carlos-sarmiento]: https://github.com/carlos-sarmiento +[@ctalkington]: https://github.com/ctalkington +[@janiversen]: https://github.com/janiversen +[@jjlawren]: https://github.com/jjlawren +[@kit-klein]: https://github.com/kit-klein +[@raman325]: https://github.com/raman325 +[bayesian docs]: /integrations/bayesian/ +[frontend docs]: /integrations/frontend/ +[ipp docs]: /integrations/ipp/ +[konnected docs]: /integrations/konnected/ +[modbus docs]: /integrations/modbus/ +[monoprice docs]: /integrations/monoprice/ +[nextcloud docs]: /integrations/nextcloud/ +[onvif docs]: /integrations/onvif/ +[plex docs]: /integrations/plex/ +[switcher_kis docs]: /integrations/switcher_kis/ +[tplink docs]: /integrations/tplink/ +[vizio docs]: /integrations/vizio/ + +## Release 0.108.3 - April 10 + +- Fix Onvif Camera that does not have SnapshotUri such as Sricam ([@Minims] - [#33902]) ([onvif docs]) +- Make homekit aware of DEVICE_CLASS_GATE ([@bdraco] - [#33936]) ([homekit docs]) +- Fix powerwall units (kW) ([@bdraco] - [#33954]) ([powerwall docs]) +- Fix turning off/on light groups in homekit ([@Knapoc] - [#33965]) ([homekit docs]) +- Update pyipp to 0.9.2 ([@ctalkington] - [#33967]) ([ipp docs]) +- Handle 304 http responses in nexia ([@bdraco] - [#33972]) ([nexia docs]) +- Fix shutdown timeout and make it upstream with Supervisor ([@pvizeli] - [#33973]) +- Cleanup ZHA group entity lifecycle ([@dmulcahey] - [#33977]) ([zha docs]) +- Exclude non thermostats from being detected by nexia ([@bdraco] - [#33979]) ([nexia docs]) +- Use zeroconf UUID if not available via IPP properties ([@ctalkington] - [#33991]) ([ipp docs]) + +[#33902]: https://github.com/home-assistant/core/pull/33902 +[#33936]: https://github.com/home-assistant/core/pull/33936 +[#33954]: https://github.com/home-assistant/core/pull/33954 +[#33965]: https://github.com/home-assistant/core/pull/33965 +[#33967]: https://github.com/home-assistant/core/pull/33967 +[#33972]: https://github.com/home-assistant/core/pull/33972 +[#33973]: https://github.com/home-assistant/core/pull/33973 +[#33977]: https://github.com/home-assistant/core/pull/33977 +[#33979]: https://github.com/home-assistant/core/pull/33979 +[#33991]: https://github.com/home-assistant/core/pull/33991 +[@Knapoc]: https://github.com/Knapoc +[@Minims]: https://github.com/Minims +[@bdraco]: https://github.com/bdraco +[@ctalkington]: https://github.com/ctalkington +[@dmulcahey]: https://github.com/dmulcahey +[@pvizeli]: https://github.com/pvizeli +[homekit docs]: /integrations/homekit/ +[ipp docs]: /integrations/ipp/ +[nexia docs]: /integrations/nexia/ +[onvif docs]: /integrations/onvif/ +[powerwall docs]: /integrations/powerwall/ +[zha docs]: /integrations/zha/ + ## All changes
@@ -620,8 +766,8 @@ These integrations have been removed. The websites for both have changed, causin
- - + + [#29063]: https://github.com/home-assistant/core/pull/29063 [#29909]: https://github.com/home-assistant/core/pull/29909 diff --git a/source/images/integrations/kira/kira_remote_script.png b/source/images/integrations/kira/kira_remote_script.png new file mode 100644 index 00000000000..4d59731a053 Binary files /dev/null and b/source/images/integrations/kira/kira_remote_script.png differ diff --git a/source/images/integrations/kira/kira_sensor_states.png b/source/images/integrations/kira/kira_sensor_states.png new file mode 100644 index 00000000000..1856a5008c6 Binary files /dev/null and b/source/images/integrations/kira/kira_sensor_states.png differ diff --git a/source/images/integrations/kira/kira_states.png b/source/images/integrations/kira/kira_states.png new file mode 100644 index 00000000000..8d4de16a299 Binary files /dev/null and b/source/images/integrations/kira/kira_states.png differ diff --git a/source/images/integrations/kira/kira_test_script.png b/source/images/integrations/kira/kira_test_script.png new file mode 100644 index 00000000000..02aba485c58 Binary files /dev/null and b/source/images/integrations/kira/kira_test_script.png differ diff --git a/source/lovelace/dashboards-and-views.markdown b/source/lovelace/dashboards-and-views.markdown index 7555bee4454..f56b25a3063 100644 --- a/source/lovelace/dashboards-and-views.markdown +++ b/source/lovelace/dashboards-and-views.markdown @@ -55,7 +55,7 @@ mode: type: string resources: required: false - description: "List of resources that should be loaded when you use Lovelace. Only use this when mode is `yaml`." + description: "List of resources that should be loaded when you use Lovelace. Only use this when mode is `yaml`. If you change anything here, click the three dots menu (top-right) and click on `Reload resources` for Lovelace to pick up changes without restarting Home Assistant. You can also call `lovelace.reload_resources` service directly." type: list keys: url: diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown index c5fe345447b..623fcd687c1 100644 --- a/source/lovelace/index.markdown +++ b/source/lovelace/index.markdown @@ -5,7 +5,7 @@ redirect_from: - /integrations/lovelace/ --- -Lovelace is the name of the Home Assistant user interface. It is a fast, customizable and powerful way for users to manage their homes, working both on mobile and desktop. +Lovelace is the Home Assistant user interface. It's a fast, customizable and powerful way for users to manage their homes, working on mobile or desktop. - 24 different cards to place and configure as you like. - UI Editor. A configuration UI to manage your Lovelace UI including live preview when editing cards. @@ -16,6 +16,8 @@ Lovelace is the name of the Home Assistant user interface. It is a fast, customi - Ability to override names and icons of entities. - Custom Cards from our amazing community are fully supported. +To start, go to the Home Assistant Overview page, click the three dots at the top right of the screen and select 'Configure UI'. Then click the orange '+' icon at the bottom right and select a card to add. +