- Intruder alert
+
+
+
+
+
+
- 
-
-
-
- 
-
+burglar:
+ alias: "Burglar Alarm"
+ sequence:
+ - service: shell_command.snapshot
+ - delay:
+ seconds: 1
+ - service: notify.NOTIFIER_NAME
+ data:
+ message: "Intruder alert at apartment!!"
+ data:
+ images:
+ - /home/pi/snapshot1.jpg
+ - /home/pi/snapshot2.jpg
+ html: >
+
+
+
+
+
+
+
-
+
+
+
+ Intruder alert at apartment!!
+
+
+
+
+
+
+
```
This platform is fragile and not able to catch all exceptions in a smart way because of the large number of possible configuration combinations.
A combination that will work properly is port 587 and STARTTLS. It's recommended to enable STARTTLS, if possible.
-Keep in mind that if the password contains a colon, it needs to be wrapped in apostrophes in the `configuration.yaml` file.
-
For Google Mail (smtp.gmail.com) an additional step in the setup process is needed. Google has some extra layers of protection
which need special attention. By default, the usage by external applications, especially scripts, is limited. Visit the [Less secure apps](https://www.google.com/settings/security/lesssecureapps) page and enable it.
diff --git a/source/_integrations/tahoma.markdown b/source/_integrations/tahoma.markdown
index 4610ae5f666..f2dc6a3a5d9 100644
--- a/source/_integrations/tahoma.markdown
+++ b/source/_integrations/tahoma.markdown
@@ -22,7 +22,7 @@ ha_platforms:
- switch
---
-The `Tahoma` integration platform is used as an interface to the [tahomalink.com](https://www.tahomalink.com) website. It adds covers, scenes and a sun sensor from the Tahoma platform.
+The Tahoma integration is used as an interface to the [tahomalink.com](https://www.tahomalink.com) website. It adds covers, scenes and a sun sensor from the Tahoma platform.
There is currently support for the following device types within Home Assistant:
@@ -40,9 +40,12 @@ To use your Tahoma devices in your installation, add the following to your `conf
```yaml
# Example configuration.yaml entry
tahoma:
- username: YOUR_USERNAME
- password: YOUR_PASSWORD
- exclude: [BridgeHUEComponent, HueLampHUEComponent, PodComponent]
+ username: "YOUR_USERNAME"
+ password: "YOUR_PASSWORD"
+ exclude:
+ - "BridgeHUEComponent"
+ - "HueLampHUEComponent"
+ - "PodComponent"
```
{% configuration %}
@@ -60,4 +63,4 @@ exclude:
type: list
{% endconfiguration %}
-This also works with the Somfy Connexoon. Check [here](https://somfyhouse.freshdesk.com/nl/support/solutions/articles/14000058145-wat-is-het-verschil-tussen-de-tahoma-en-de-connexoon-) for the differences between the bridges.
+This also works with the Somfy Connexoon. Check [here](https://www.somfy.nl/keuzehulp/verschillen-tahoma-en-connexoon) for the differences between the bridges.
diff --git a/source/_integrations/tuya.markdown b/source/_integrations/tuya.markdown
index 595b08fdc20..75122bbb29f 100644
--- a/source/_integrations/tuya.markdown
+++ b/source/_integrations/tuya.markdown
@@ -38,7 +38,7 @@ There is currently support for the following device types within Home Assistant:
{% include integrations/config_flow.md %}
-During configuration, be careful to select the [country code](https://www.countrycode.org/) and the platform corresponding to those used by you in the app. Once configuration flow is completed, the devices configured in your app will be automatically discovered.
+During configuration, be careful to select the [country code](https://www.countrycode.org/) and the platform corresponding to those used by you in the app. Once configuration flow is completed, the devices configured in your app will be automatically discovered. Additionally, if your username or e-mail address isn't accepted, please try using your phone number (minus the country code) as your username.
## Integration Options
diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown
index 94cffadd918..a6dcbcf42cc 100644
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@@ -188,7 +188,23 @@ zha:
You can choose if the IKEA or LEDVANCE provider should be set to enabled (`true`) or disabled (`false`) individually. After the OTA firmware upgrades are finished, you can set these to `false` again if you do not want ZHA to automatically download and perform OTA firmware upgrades in the future.
-Note that the `otau_directory` setting is optional and can be used for any firmware files you have downloaded yourself.
+Note that the `otau_directory` setting is optional and can be used for any firmware files you have downloaded yourself, for any device type and manufacturer. For example, Philips Hue firmwares manually downloaded from [here](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/OTA-Image-Types---Firmware-versions) and/or [here](https://github.com/Koenkk/zigbee-OTA/blob/a02a4cb33f7c46b4d2916805bfcad582124ec975/index.json) added to the `otau_directory` can be flashed, although a manual `zha.issue_zigbee_cluster_command` command currently (as of 2021.3.3) must be issued against the IEEE of the Philips Hue device under Developer Tools->Services, e.g.:
+
+```yaml
+service: zha.issue_zigbee_cluster_command
+data:
+ ieee: "xx:xx:xx:xx:xx:xx:xx:xx"
+ endpoint_id: 11
+ cluster_id: 25
+ cluster_type: out
+ command: 0
+ command_type: client
+ args:
+ - 0
+ - 100
+```
+
+Note: `cluster_id: 25` may also be `cluster_id: 0x0019`. The two are synonymous.
### Defining Zigbee channel to use
diff --git a/source/more-info/unsupported/apparmor.markdown b/source/more-info/unsupported/apparmor.markdown
new file mode 100644
index 00000000000..bc74fae2120
--- /dev/null
+++ b/source/more-info/unsupported/apparmor.markdown
@@ -0,0 +1,16 @@
+---
+title: "AppArmor issues"
+description: "More information on why missing AppArmor marks the installation as unsupported."
+---
+
+## The issue
+
+AppArmor is how the Supervisor does handling all the security around add-ons,
+without this, the Supervisor is missing important security mechanics to protect your system and data within it.
+
+## The solution
+
+If the AppArmor is not enabled on your host, set this to the Linux boot cmd: `apparmor=1 security=apparmor` and reboot your operating system.
+
+As a last resort, you might need to reinstall the host running the Supervisor
+with one of the supported operating systems, [see instructions here](/more-info/unsupported/os).
+
-
-
-
-
+
+
+
+
+
+
-
+