-There are [known compatability issues](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030) with older hardware versions of the Aeotec stick not working on the Raspberry Pi 4. Aeotec has released a 2020 hardware revision ZW090-A/B/C Gen5+ with Pi 4 compatibility. Both hardware revisions are still being sold, make informed purchasing decisions if using paired with a Pi 4.
+There are [known compatibility issues](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030) with older hardware versions of the Aeotec stick not working on the Raspberry Pi 4. Aeotec has released a 2020 hardware revision ZW090-A/B/C Gen5+ with Pi 4 compatibility. Both hardware revisions are still being sold, make informed purchasing decisions if using paired with a Pi 4.
diff --git a/source/_integrations/default_config.markdown b/source/_integrations/default_config.markdown
index 38eeb67a6a9..23b7f34fb25 100644
--- a/source/_integrations/default_config.markdown
+++ b/source/_integrations/default_config.markdown
@@ -32,6 +32,7 @@ This integration is a meta-component and configures a default set of integration
- [Scene](/integrations/scene/) (`scene`)
- [Scripts](/integrations/script/) (`script`)
- [Simple Service Discovery Protocol (SSDP)](/integrations/ssdp/) (`ssdp`)
+- [Stream](/integrations/stream/) (`stream`)
- [Sun](/integrations/sun/) (`sun`)
- [System Health](/integrations/system_health/) (`system_health`)
- [Tag](/integrations/tag/) (`tag`)
diff --git a/source/_integrations/devolo_home_control.markdown b/source/_integrations/devolo_home_control.markdown
index e1f6ddd8ea4..7f6cb103b96 100755
--- a/source/_integrations/devolo_home_control.markdown
+++ b/source/_integrations/devolo_home_control.markdown
@@ -30,6 +30,8 @@ devolo Home Control is a Z-Wave ecosystem with a Z-Wave to IP gateway in the cen
{% include integrations/config_flow.md %}
+Please do not change the URL provided in the advanced mode unless you know what you are doing.
+
## Switches
The integration provides support for the following Z-Wave devices:
diff --git a/source/_integrations/dht.markdown b/source/_integrations/dht.markdown
index 232bde6b3a3..264aa3e3212 100644
--- a/source/_integrations/dht.markdown
+++ b/source/_integrations/dht.markdown
@@ -30,7 +30,7 @@ Add the following to your `configuration.yaml` file:
sensor:
platform: dht
sensor: DHT22
- pin: D23
+ pin: 23
monitored_conditions:
- temperature
- humidity
@@ -71,7 +71,7 @@ humidity_offset:
type: [integer, float]
{% endconfiguration %}
-The name of the pin to which the sensor is connected has different names on different platforms. 'P8_11' for Beaglebone, 'D23' for Raspberry Pi.
+The name of the pin to which the sensor is connected has different names on different platforms. 'P8_11' for Beaglebone, '23' for Raspberry Pi.
### Example
@@ -81,7 +81,7 @@ An example for a Raspberry Pi 3 with a DHT22 sensor connected to GPIO4 (pin 7):
sensor:
- platform: dht
sensor: DHT22
- pin: D4
+ pin: 4
temperature_offset: 2.1
humidity_offset: -3.2
monitored_conditions:
diff --git a/source/_integrations/fritzbox.markdown b/source/_integrations/fritzbox.markdown
index f5bd289502b..b8036ee9455 100644
--- a/source/_integrations/fritzbox.markdown
+++ b/source/_integrations/fritzbox.markdown
@@ -42,6 +42,10 @@ There is currently support for the following device types within Home Assistant:
{% include integrations/config_flow.md %}
+
+The configuration in the UI asks for a username. Starting from FRITZ!OS 7.24 the FRITZ!Box creates a random username for the admin user if you didn't set one yourself. This can be found after logging into the FRITZ!Box and visiting System -> FRITZ!Box Users -> Users. The username starts with "fritz" followed by four random numbers. Under properties on the right it says "created automatically". Prior to FRITZ!OS 7.24 the default username was "admin".
+
+
## Switches & Thermostats
To get AVM FRITZ!DECT switches (e.g. FRITZ!DECT 400/440) or thermostats (e.g. FRITZ!DECT 301) follow the [configuration instructions](#configuration) above.
diff --git a/source/_integrations/google_maps.markdown b/source/_integrations/google_maps.markdown
index b4a7a5f7010..0eb334ff596 100644
--- a/source/_integrations/google_maps.markdown
+++ b/source/_integrations/google_maps.markdown
@@ -23,7 +23,22 @@ You need two Google accounts. Account A is the account that has to be set up to
### Note for existing location sharing users
-If you already have other people sharing their location to your existing Account A and do not wish to ask them to also share their location with a new Account B. Create the new Google account (account B) and share the location of Account B back to Account A. Follow the steps listed, substituting the instructions stating “Account B” for “Account A” (i.e., a cookie file is from Account A, slugified username of Account A), then ensure both Account A and Account B are logged in on your mobile device.
+If you already have other people sharing their location with your existing Account A and do not wish to ask them to also share their location with a new Account B. Simply repeat the steps above to obtain a valid cookie from Google for Account A. Then add both accounts to the device tracker configuration (don’t forget to include the multiple cookie files, one for each account being added to the integration).
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+ - platform: google_maps
+ username: "ACCOUNT_A_EMAIL"
+ - platform: google_maps
+ username: "ACCOUNT_B_EMAIL"
+```
+
+
+If using more than one account, your own device may show twice, however, the parameters returned from Account A will not include a value for battery_level or entity_picture. These parameters will be present in your device tracker entity from Account B. Therefore, disregard the device tracker entity with is missing those parameters.
+
+
+
## Configuration
diff --git a/source/_integrations/google_translate.markdown b/source/_integrations/google_translate.markdown
index f054f740d45..c04252b5278 100644
--- a/source/_integrations/google_translate.markdown
+++ b/source/_integrations/google_translate.markdown
@@ -10,7 +10,7 @@ ha_platforms:
- tts
---
-The `google_translate` text-to-speech platform uses the unofficial [Google Translate Text-to-Speech engine](https://translate.google.com/) to read a text with natural sounding voices.
+The `google_translate` text-to-speech platform uses the unofficial [Google Translate Text-to-Speech engine](https://translate.google.com/) to read a text with natural sounding voices. Contrary to what the name suggests, the integration only does text-to-speech and does not translate messages sent to it.
## Configuration
@@ -24,7 +24,7 @@ tts:
{% configuration %}
language:
- description: "The language to use."
+ description: "The default speech language to use."
required: false
type: string
default: "`en`"
@@ -33,6 +33,8 @@ language:
Check the [complete list of supported languages](https://translate.google.com/intl/en_ALL/about/languages/) (languages where "Talk" feature is enabled in Google Translate) for allowed values.
Use the 2 digit language code which you can find at the end of URL when you click on Language name.
+For more information about using text-to-speech with Home Assistant and more details on all the options it provides, see the [TTS documentation](/integrations/tts/).
+
## Full configuration example
A full configuration sample including optional variables:
diff --git a/source/_integrations/ialarm.markdown b/source/_integrations/ialarm.markdown
index e5529d4cb91..54055ac32ce 100644
--- a/source/_integrations/ialarm.markdown
+++ b/source/_integrations/ialarm.markdown
@@ -15,6 +15,7 @@ ha_platforms:
---
The iAlarm integration provides connectivity with the [Antifurto365](https://www.antifurtocasa365.it/) iAlarm alarm systems and has also been confirmed to work with the alarm system brands Meian and Emooluxr.
+Please note that the latest iAlarm-XR alarm system is not supported.
This platform supports the following services:
diff --git a/source/_integrations/icloud.markdown b/source/_integrations/icloud.markdown
index 7defeffa5c6..1d571a5ae67 100644
--- a/source/_integrations/icloud.markdown
+++ b/source/_integrations/icloud.markdown
@@ -27,10 +27,6 @@ It does require that your devices are registered with the [Find My](https://www.
{% include integrations/config_flow.md %}
-
-Low `max_interval` may cause battery drainage as it wakes up your device to get the current location.
-
-
You may receive an email and a notification from Apple saying that someone has logged into your account.
@@ -61,7 +57,7 @@ The iCloud integration will add a battery sensor for each iCloud devices availab
### Service `icloud.update`
-This service can be used to ask an update of a certain iDevice or all devices linked to an iCloud account. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iPhone location. It can be used in automations when a manual location update is needed, e.g., to check if anyone is home when a door been opened.
+This service can be used to ask an update of a certain iDevice or all devices linked to an iCloud account. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iPhone location. It can be used in automations when a manual location update is needed, e.g., to check if anyone is home when a door has been opened.
### Service `icloud.play_sound`
diff --git a/source/_integrations/integration.markdown b/source/_integrations/integration.markdown
index 29e73ce2b55..f45780e295b 100644
--- a/source/_integrations/integration.markdown
+++ b/source/_integrations/integration.markdown
@@ -64,7 +64,9 @@ method:
default: trapezoidal
{% endconfiguration %}
-In case you have an appliance which produces spikey consumption (like an on/off electrical boiler) you should opt for the `left` method to get accurate readings. If `unit` is set then `unit_prefix` and `unit_time` are ignored.
+In case you have an appliance which produces spikey consumption (like an on/off electrical boiler) you should opt for the `left` method to get accurate readings.
+
+The unit of `source` together with `unit_prefix` and `unit_time` is used to generate a unit for the integral product (e.g. a source in `W` with prefix `k` and time `h` would result in `kWh`). You can override this behavior by providing a custom value for `unit`. Note that `unit_prefix` and `unit_time` are _also_ relevant to the Riemann sum calculation. Even if you provide a custom value for `unit`, ensure prefix and time accurately reflect the properties of your source data.
## Energy
diff --git a/source/_integrations/manual.markdown b/source/_integrations/manual.markdown
index 8143552c69c..0eb5ec5aff6 100644
--- a/source/_integrations/manual.markdown
+++ b/source/_integrations/manual.markdown
@@ -171,12 +171,12 @@ automation:
to: "open"
condition:
- condition: state
- entity_id: alarm_control_panel.ha_alarm
+ entity_id: alarm_control_panel.home_alarm
state: armed_away
action:
service: alarm_control_panel.alarm_trigger
target:
- entity_id: alarm_control_panel.ha_alarm
+ entity_id: alarm_control_panel.home_alarm
```
Sending a notification when the alarm is triggered.
@@ -186,7 +186,7 @@ automation:
- alias: 'Send notification when alarm triggered'
trigger:
- platform: state
- entity_id: alarm_control_panel.ha_alarm
+ entity_id: alarm_control_panel.home_alarm
to: "triggered"
action:
- service: notify.notify
@@ -207,7 +207,7 @@ automation:
action:
- service: alarm_control_panel.alarm_disarm
target:
- entity_id: alarm_control_panel.house_alarm
+ entity_id: alarm_control_panel.home_alarm
```
Sending a Notification when the Alarm is Armed (Away/Home), Disarmed and in Pending Status
diff --git a/source/_integrations/motion_blinds.markdown b/source/_integrations/motion_blinds.markdown
index 865b71f185f..fefba158ed2 100644
--- a/source/_integrations/motion_blinds.markdown
+++ b/source/_integrations/motion_blinds.markdown
@@ -16,6 +16,12 @@ ha_platforms:
The integration allows you to control [Motion Blinds](https://motion-blinds.com) from [Coulisse B.V.](https://coulisse.com/products/motion).
+Additionally the following brands have been reported to also work with this integration:
+
+- [Motion Blinds](https://motion-blinds.com)
+- [Dooya](http://www.dooya.com/)
+- [Bloc Blinds](https://www.blocblinds.com/)
+
{% include integrations/config_flow.md %}
## Retrieving the API Key
diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown
index 19301a7b6ac..66dbdfae500 100644
--- a/source/_integrations/plex.markdown
+++ b/source/_integrations/plex.markdown
@@ -29,6 +29,10 @@ If a Plex server has been claimed by a Plex account via the [claim interface](ht
{% include integrations/config_flow.md %}
+During setup, the integration will check all possible ways to connect to your Plex server(s) - i.e., local or public addresses, HTTP or HTTPS, by IP or using a subdomain of `plex.direct`, or by using a Plex relay if all other methods fail. The integration will prefer local over public and secure over insecure, in that order. The selected address is shown on the Plex card on the Integrations page.
+
+If your router enforces DNS rebind protection, connections to the local `plex.direct` hostname may fail (see [Plex documentation](https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/#dnsrebinding)). To avoid this, configure your router to allow DNS rebinding for `plex.direct` by following the instructions in the documentation link.
+
### Integration Options
Several options are provided to adjust the behavior of `media_player` entities. These can be changed at **Plex** -> **Options** on the Integrations page.
diff --git a/source/_integrations/shelly.markdown b/source/_integrations/shelly.markdown
index a6557623683..df956246e49 100644
--- a/source/_integrations/shelly.markdown
+++ b/source/_integrations/shelly.markdown
@@ -70,9 +70,44 @@ Shelly device relays are added to the Home Assistant by default as `switch` enti
## Events
-If the **BUTTON TYPE** of the switch connected to the device is set to `momentary` or `detached switch`, integration fires events when the switch is used. You can use these events in your automations.
+If the **BUTTON TYPE** of the switch connected to the device is set to `momentary` or `detached switch`, integration fires events under the type `shelly.click` when the switch is used. You can use these events in your automations.
-### Automation examples
+Also, some devices do not add an entity for the button/switch. For example, the Shelly Button1 has only one entity for the battery level. It does not have an entity for the button itself. To trigger automations based on button presses, use the `shelly.click` event.
+
+### Listening for events
+
+You can subscribe to the `shelly.click` event type in [Developer Tools/Events](/docs/tools/dev-tools/) in order to examine the event data JSON for the correct parameters to use in your automations. For example, `shelly.click` returns event data JSON similar to the following when you press the Shelly Button1.
+
+```json
+Event 0 fired 9:53 AM:
+{
+ "event_type": "shelly.click",
+ "data": {
+ "device_id": "e09c64a22553484d804353ef97f6fcd6",
+ "device": "shellybutton1-A4C12A45174",
+ "channel": 1,
+ "click_type": "single"
+ },
+ "origin": "LOCAL",
+ "time_fired": "2021-04-28T08:53:12.755729+00:00",
+ "context": {
+ "id": "e0f379706563aaa0c2c1fda5174b5a0e",
+ "parent_id": null,
+ "user_id": null
+ }
+}
+```
+
+### Automations
+
+The simplest way to create automations is to use the Home Assistant automation editor. For example, to set an automation triggered by a double press of a particular Shelly Button1:
+
+1. In the Triggers section of the automation, set Trigger Type to `Device`.
+2. In the Device dropdown menu. find the Shelly Button1.
+3. In the Trigger dropdown menu, select `Button double clicked`.
+4. Set any conditions and actions to complete your automation.
+
+You can also create automations using YAML, for example:
```yaml
- alias: "Toggle living room light"
diff --git a/source/_integrations/statistics.markdown b/source/_integrations/statistics.markdown
index f94d313a778..3d006cae8d9 100644
--- a/source/_integrations/statistics.markdown
+++ b/source/_integrations/statistics.markdown
@@ -32,8 +32,6 @@ sensor:
entity_id: sensor.cpu
- platform: statistics
entity_id: binary_sensor.movement
- max_age:
- minutes: 30
```
{% configuration %}
diff --git a/source/_integrations/synology_dsm.markdown b/source/_integrations/synology_dsm.markdown
index c3d6e83a9be..ee9bcff7a68 100644
--- a/source/_integrations/synology_dsm.markdown
+++ b/source/_integrations/synology_dsm.markdown
@@ -85,6 +85,12 @@ Entities reporting status, total size (TB), used size (TB), % of volume used, av
Entities reporting the update and security status of the NAS.
+
+
+The security status corresponds with the analysis of the DSM Security Advisor, e.g., an `outOfDate` state for the `Update` attribute not only reflects the update status of the installed DSM version but also the status of the installed DSM packages.
+
+
+
### Disk sensors
Similar to the [normal disk sensors](#disk-sensors), there are binary sensors reporting each drive's status. These sensors report if a drive has exceeded the maximum threshold for detected bad sectors and if a drive has dropped below the threshold for its remaining life.
diff --git a/source/_integrations/systemmonitor.markdown b/source/_integrations/systemmonitor.markdown
index 165332d2eb1..2282562a667 100644
--- a/source/_integrations/systemmonitor.markdown
+++ b/source/_integrations/systemmonitor.markdown
@@ -40,6 +40,9 @@ resources:
required: false
{% endconfiguration %}
+After restarting Home Assistant, these sensors will show up and update their
+information every 15 seconds.
+
The table contains types and their argument to use in your `configuration.yaml`
file.
diff --git a/source/_integrations/vultr.markdown b/source/_integrations/vultr.markdown
index 5ace94fea8c..ae3aa17a6d9 100644
--- a/source/_integrations/vultr.markdown
+++ b/source/_integrations/vultr.markdown
@@ -128,13 +128,13 @@ monitored_conditions:
detault: All conditions
type: list
keys:
- current_bandwidth_used:
+ current_bandwidth_gb:
description: The current (invoice period) bandwidth usage in Gigabytes (GB).
pending_charges:
description: The current (invoice period) charges that have built up for this subscription. Value is in US Dollars (US$).
{% endconfiguration %}
-Full `configuration.yaml` using `{}` to format condition name (produces `sensor.server_current_bandwidth_used` and `sensor.server_pending_charges`):
+Full `configuration.yaml` using `{}` to format condition name (produces `sensor.server_current_bandwidth_gb` and `sensor.server_pending_charges`):
```yaml
sensor:
@@ -142,7 +142,7 @@ sensor:
name: Server {}
subscription: 123456
monitored_conditions:
- - current_bandwidth_used
+ - current_bandwidth_gb
- pending_charges
```
diff --git a/source/_integrations/yeelight.markdown b/source/_integrations/yeelight.markdown
index a0634d5462c..dfec10e1104 100644
--- a/source/_integrations/yeelight.markdown
+++ b/source/_integrations/yeelight.markdown
@@ -191,6 +191,7 @@ This integration is tested to work with the following models. If you have a diff
| `mono` | YLTD03YL | Yeelight Serene Eye-Friendly Desk Lamp |
| `ceiling10` | YLDL01YL | Yeelight Meteorite Pendant Light |
| `ceiling13` | YLXD01YL | Yeelight LED Ceiling Light |
+| `ceil26` | YLXD76YL | Yeelight Ceiling Light - Updated HomeKit 23w |
| `lamp` | MJTD02YL | Xiaomi Mijia Desk Lamp Pro |
## Services
diff --git a/source/_posts/2021-05-21-community-highlights.markdown b/source/_posts/2021-05-21-community-highlights.markdown
new file mode 100644
index 00000000000..011e4122cc1
--- /dev/null
+++ b/source/_posts/2021-05-21-community-highlights.markdown
@@ -0,0 +1,102 @@
+---
+title: "Community Highlights: 22nd edition"
+description: "A new highlight with 2 new cards that you can use, blueprint for those who always leave the door open and give your TV an upgrade with Hyperion project."
+date: 2021-05-21 00:00:00
+date_formatted: "May 21, 2021"
+author: Klaas Schoute
+author_twitter: klaasnicolaas
+categories: Community
+og_image: /images/blog/2021-05-21-community-highlights/social.png
+---
+
+The 22nd edition of the Home Assistant Community Highlights! Some interesting
+things popped up around our community, we thought was worth sharing.
+
+Do you want to share something for the next edition?
+Information on [how to share](#got-a-tip-for-the-next-edition).
+
+./Klaas
+*Intern on Home Assistant Energy*
+
+## Blueprint of the week
+------
+
+Are you one of those who always leave the doors open?
+
+Then this week we have a nice blueprint for you! [BasTijs](https://community.home-assistant.io/u/bastijs )
+has made a blueprint that announces through text to speech in the house,
+that a door is open and only stops when the door is closed again.
+
+{% my blueprint_import badge blueprint_url="https://community.home-assistant.io/t/door-open-tts-announcer/266252" %}
+
+Try it out! Read more about it on the [community forum][week_blueprint] or
+install this automation in your instance with a click on the My button!
+
+## Sun card
+------
+
+
+
+On our [Home Assistant reddit][reddit] page we also encountered another nice
+project, namely that of [AitorDB](https://github.com/AitorDB). Who made a
+[Lovelace card](https://github.com/AitorDB/home-assistant-sun-card) that shows
+the position of the sun when it rises, is at its highest point and sets again.
+
+
+
+## Collapsed card
+------
+
+Is your Lovelace dashboard overflowing with cards and do you want to
+make some free space? Then try the card made by [RossMcMillan92](https://github.com/RossMcMillan92),
+which makes it possible to collapse entire cards and reappear as a dropdown.
+
+
+
+## Hyperion - HA bridge
+------
+
+
+
+You have those TVs where LEDs are mounted on the back so that the colors of
+the TV continue over the wall behind it, this is also called ambilight. If
+your TV is not equipped with this, you can also make this yourself through
+the [Hyperion project](https://hyperion-project.org). [pimw](https://community.home-assistant.io/u/pimw)
+has also written an [instruction post](https://community.home-assistant.io/t/instruction-hyperion-ha-bridge-home-assistant/307708)
+about this on our [community forum][community] on how to connect the bridge
+to Home Assistant.
+
+## Got a tip for the next edition?
+------
+
+Have you seen (or made) something awesome, interesting, unique, amazing,
+inspirational, unusual or funny, using Home Assistant?
+
+[Click here to send us your Community Highlight suggestion](/suggest-community-highlight).
+
+Also, don't forget to share your creations with us via Social Media:
+
+- Tweet it! Be sure to mention [@home_assistant][twitter]
+- Share it on our [Facebook group][facebook-group]
+- Post it to our [subreddit][reddit]
+- Tag [@homeasssistant][instagram] on Instagram
+- Or via chat, drop us a line in the [#lounge at Discord][chat]
+
+See you next edition!
+
+[chat]: https://www.home-assistant.io/join-chat
+[facebook-group]: https://www.facebook.com/groups/HomeAssistant
+[instagram]: https://www.instagram.com/homeassistant
+[reddit]: https://www.reddit.com/r/homeassistant
+[twitter]: https://www.twitter.com/home_assistant
+[blueprints]: https://community.home-assistant.io/c/blueprints-exchange
+[community]: https://community.home-assistant.io
+[week_blueprint]: https://community.home-assistant.io/t/door-open-tts-announcer/266252
\ No newline at end of file
diff --git a/source/images/blog/2021-05-21-community-highlights/social.png b/source/images/blog/2021-05-21-community-highlights/social.png
new file mode 100644
index 00000000000..f941ce24dfb
Binary files /dev/null and b/source/images/blog/2021-05-21-community-highlights/social.png differ
diff --git a/source/images/blog/2021-05-21-community-highlights/sun-card.png b/source/images/blog/2021-05-21-community-highlights/sun-card.png
new file mode 100644
index 00000000000..7d5d2ad2600
Binary files /dev/null and b/source/images/blog/2021-05-21-community-highlights/sun-card.png differ
-Select all the devices (and/or entities when in advanced mode) you want to include in your scene.
+Select all the devices (or entities when advanced mode is enabled on your user profile) you want to include in your scene.
The state of your devices will be saved, so it can be restored when you are finished creating your scene.
Set the state of the devices to how you want them to be in your scene, this can be done by clicking on it and edit the state from the popup, or any other method that changes the state.
On the moment you save the scene, all the states of your devices are stored in the scene.
diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown
index 7c5813f1dfb..98dd5df48ee 100644
--- a/source/_docs/scripts.markdown
+++ b/source/_docs/scripts.markdown
@@ -96,8 +96,8 @@ While executing a script you can add a condition to stop further execution. When
```yaml
# If paulus is home, continue to execute the script below these lines
- alias: "Check if Paulus is home"
-- condition: state
+- alias: "Check if Paulus is home"
+ condition: state
entity_id: device_tracker.paulus
state: "home"
```
diff --git a/source/_docs/z-wave/controllers.markdown b/source/_docs/z-wave/controllers.markdown
index b9fd52a7b4e..c572273803a 100644
--- a/source/_docs/z-wave/controllers.markdown
+++ b/source/_docs/z-wave/controllers.markdown
@@ -15,7 +15,7 @@ You need to have a compatible Z-Wave stick or module installed. This needs to be
+
+