jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2019-12-03 11:56:32 +01:00
commit 954f00e5df
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
77 changed files with 444 additions and 937 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Gemfile
View File

@ -13,7 +13,7 @@ end
group :jekyll_plugins do
gem 'jekyll-paginate', '1.1.0'
gem 'jekyll-redirect-from', '0.15.0'
gem 'jekyll-sitemap', '1.3.1'
gem 'jekyll-sitemap', '1.4.0'
gem 'jekyll-time-to-read', '0.1.2'
gem 'jekyll-commonmark', '1.3.1'
end

10
Gemfile.lock
View File

@ -25,8 +25,8 @@ GEM
http_parser.rb (~> 0.6.0)
eventmachine (1.2.7)
eventmachine (1.2.7-x64-mingw32)
ffi (1.11.1)
ffi (1.11.1-x64-mingw32)
ffi (1.11.2)
ffi (1.11.2-x64-mingw32)
forwardable-extended (2.6.0)
http_parser.rb (0.6.0)
i18n (1.7.0)
@ -54,7 +54,7 @@ GEM
jekyll (>= 3.3, < 5.0)
jekyll-sass-converter (2.0.1)
sassc (> 2.0.1, < 3.0)
jekyll-sitemap (1.3.1)
jekyll-sitemap (1.4.0)
jekyll (>= 3.7, < 5.0)
jekyll-time-to-read (0.1.2)
jekyll
@ -85,7 +85,7 @@ GEM
rb-fsevent (0.10.3)
rb-inotify (0.10.0)
ffi (~> 1.0)
rouge (3.12.0)
rouge (3.13.0)
ruby-enum (0.7.2)
i18n
safe_yaml (1.0.5)
@ -121,7 +121,7 @@ DEPENDENCIES
jekyll-commonmark (= 1.3.1)
jekyll-paginate (= 1.1.0)
jekyll-redirect-from (= 0.15.0)
jekyll-sitemap (= 1.3.1)
jekyll-sitemap (= 1.4.0)
jekyll-time-to-read (= 0.1.2)
nokogiri (= 1.10.5)
rake (= 13.0.1)

4
_config.yml
View File

@ -101,8 +101,8 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 102
current_patch_version: 0
date_released: 2019-11-20
current_patch_version: 3
date_released: 2019-11-29
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

10
source/_addons/mosquitto.markdown
View File

@ -77,6 +77,16 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the int
Password: MQTT_PASSWORD
```
If you are using the ACL, remember to enter the newly created user and homeassistant in `/share/mosquitto/accesscontrollist` as follows:
```text
user [YOUR_MQTT_USER]
topic readwrite #
user homeassistant
topic readwrite #
```
Note: .yaml modifications are not required.
See [testing your setup](/docs/mqtt/testing/) to verify the steps above.

2
source/_docs/automation/editor.markdown
View File

@ -79,7 +79,7 @@ For example, the below automation will be triggered when the sun goes from below
```yaml
# Example automations.yaml entry
- id: my_unique_id # <-- Required for editor to work.
- id: my_unique_id # <-- Required for editor to work, for automations created with the editor the id will be automatically generated.
alias: Hello world
trigger:
- platform: state

44
source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
View File

@ -1,13 +1,16 @@
---
title: "Self-signed certificate for SSL/TLS"
description: "Configure a self-signed certificate to use with Home Assistant"
title: "Certificate Authority and self-signed certificate for SSL/TLS"
description: "Configure a Certificate Authority and self-signed certificate to use with Home Assistant"
redirect_from: /cookbook/tls_self_signed_certificate/
---
If your Home Assistant instance is only accessible from your local network you can still protect the communication between your browsers and the frontend with SSL/TLS.
[Let's encrypt]({{site_root}}/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/) will only work if you have a DNS entry and remote access is allowed.
[Let's encrypt]({{site_root}}/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/) will only work if you have a DNS entry and remote access is allowed.
The solution is to use a self-signed certificate. As you most likely don't have a certification authority (CA) your browser will complain about the security. If you have a CA then this will not be an issue.
If you use Chrome browser version 58 or above and/or **don't want to have issues regarding a non-trusted CA or CN (Common Name)**, follow this full tutorial: [Create Root Certificate Authority and self-signed certificate for your Home Assistant. Compatible with Chrome browser > version 58](https://gist.github.com/tiagofreire-pt/4920be8d03a3dfa8201c6afedd00305e). Otherwise, follow this:
To create a certificate locally, you need the [OpenSSL](https://www.openssl.org/) command-line tool.
Change to your Home Assistant [configuration directory](/getting-started/configuration/) like `~/.homeassistant`. This will make it easier to backup your certificate and the key. Run the command shown below.
@ -15,28 +18,47 @@ Change to your Home Assistant [configuration directory](/getting-started/configu
The certificate **must** be `.pem` extension.
```bash
openssl req -sha256 -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out certificate.pem
openssl req -sha256 -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out fullchain.pem
```
For details about the parameters, please check the OpenSSL documentation. Provide the requested information during the generation process.
At the end you will have two files called `privkey.pem` and `certificate.pem`. The key and the certificate.
At the end you will have two files called `privkey.pem` and `fullchain.pem`. The key and the certificate.
Update the `http:` entry in your `configuration.yaml` file and let it point to your created files.
Hass.io:
```yaml
http:
ssl_certificate: /home/your_user/.homeassistant/certificate.pem
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
```
Non-hass.io:
```yaml
http:
ssl_certificate: /home/your_user/.homeassistant/fullchain.pem
ssl_key: /home/your_user/.homeassistant/privkey.pem
```
A restart of Home Assistant is required for the changes to take effect.
A restart of Home Assistant is required for the new certificate to take effect.
If you get any log error about *ssl_key* or *ssl_certificate* that is **not a file for dictionary value** when run Home Assistant, you need to change owner or access permission of the `.pem` files as following:
Hass.io (through Console or SSH plug-in):
```bash
sudo chown homeassistant:homeassistant certificate.pem privkey.pem
sudo chmod 755 certificate.pem privkey.pem
chown root:root fullchain.pem privkey.pem
chmod 600 fullchain.pem privkey.pem
```
Non-hass-io:
```bash
sudo chown homeassistant:homeassistant fullchain.pem privkey.pem
sudo chmod 600 fullchain.pem privkey.pem
```
A tutorial "[Working with SSL Certificates, Private Keys and CSRs](https://www.digitalocean.com/community/tutorials/openssl-essentials-working-with-ssl-certificates-private-keys-and-csrs)" could give you some insight about special cases.
@ -46,7 +68,7 @@ A tutorial "[Working with SSL Certificates, Private Keys and CSRs](https://www.d
#### iOS
If you are going to use this certificate with the iOS app, you need to ensure you complete **all** fields during the certificate creation process, then:
* Send **only** the `certificate.pem` file to the iOS device, using airdrop or other transfer method.
* Send **only** the `fullchain.pem` file to the iOS device, using airdrop or other transfer method.
* Open the `.pem` file on the iOS device, follow the prompts to trust and install it.
* If you are using iOS 10.3 or newer then [additional steps](https://support.apple.com/en-us/HT204477) are needed.

58
source/_docs/ecosystem/ios.markdown
View File

@ -1,58 +0,0 @@
---
title: "iOS"
description: "Documentation about the Home Assistant iOS app."
redirect_from: /ecosystem/ios/
---
The Home Assistant for iOS app offers a companion app for iOS which is deeply integrated into both Home Assistant and iOS. Its basic features include:
* Advanced push notifications
* Location tracking
* Basic control of all Home Assistant entities
* Integration with third party apps
The app is available on the iOS App Store in every country that Apple supports.
<p style="text-align: center;"><a target="_blank" href="https://itunes.apple.com/us/app/home-assistant-open-source-home-automation/id1099568401?mt=8" style="display:inline-block;overflow:hidden;background:url(//linkmaker.itunes.apple.com/assets/shared/badges/en-us/appstore-lrg.svg) no-repeat;width:135px;height:40px;background-size:contain;"></a></p>
## Basic requirements
* iOS device running at least iOS 9, but iOS 10 is greatly preferred.
* Home Assistant 0.42.4 or higher for push notification support.
* SSL is strongly recommended. Self-signed SSL certificates will not work due to Apple's limitations.
The `ios` integration is the companion integration for the Home Assistant iOS app. While not required, adding the `ios` integration to your setup will greatly enhance the iOS app with new notification, location and sensor functions not possible with a standalone app.
Loading the `ios` integration will also load the [`device_tracker`](/integrations/device_tracker), [`zeroconf`](/integrations/zeroconf) and [`notify`](/integrations/notify) platforms.
The Home Assistant for iOS app supports the new authentication system introduced in Home Assistant 0.77.
## Setup
### Automated Setup
The `ios` integration will automatically be loaded under the following circumstances:
1. The [`discovery`](/integrations/discovery) integration is enabled.
2. You have just installed the app and are at the getting started screen.
Automated discovery and integration loading only happens at first install of the app. You may need to wait a few minutes for the iOS integration to load as the `discovery` integration only scans the network every 5 minutes.
After the first automated setup you need to add `ios:` to your configuration so that the integration loads by default even after restarting Home Assistant.
### Manual Setup
You may also manually load the `ios` integration by adding the following to your configuration:
```yaml
# Example configuration.yaml entry
ios:
```
{% configuration %}
push:
description: Actionable push notifications configuration. See the [actionable notifications documentation](/docs/ecosystem/ios/notifications/actions/) for more information.
required: false
type: list
{% endconfiguration %}

6
source/_docs/ecosystem/ios/devices_file.markdown
View File

@ -1,6 +0,0 @@
---
title: "ios.conf"
description: "Describes the contents and purpose of ios.conf"
---
The `ios.conf` file contains the most recent state of all registered iOS devices. Deleting this file will not disable the devices and the file will be recreated the next time a new device is connected or an existing one reconnects.

20
source/_docs/ecosystem/ios/integration.markdown
View File

@ -1,20 +0,0 @@
---
title: "Integration"
description: "Examples of how Home Assistant for iOS can be integrated with other apps"
redirect_from: /ecosystem/ios/integration/
---
Home Assistant for iOS supports opening from other apps via URL.
Query parameters are passed as a dictionary in the call.
## Call service
Example: `homeassistant://call_service/device_tracker.see?entity_id=device_tracker.entity`
## Fire event
You can create an [event trigger](/docs/automation/trigger/#event-trigger) and fire the event.
Example: `homeassistant://fire_event/custom_event?entity_id=MY_CUSTOM_EVENT`
## Send one shot location
Example: `homeassistant://send_location/`

49
source/_docs/ecosystem/ios/location.markdown
View File

@ -1,49 +0,0 @@
---
title: "Location"
description: "Documentation about the location tracking abilities in Home Assistant for iOS"
redirect_from: /ecosystem/ios/location/
---
## Location tracking when outside a Home Assistant zone
Home Assistant for iOS receives _significant location updates_ from iOS. Whenever an update is received, it is sent to Home Assistant. Roughly, an update is received every time that your device transfers to a new cellular tower, a significant amount of time has passed (usually a couple hours) or a connection state changes and the system notices your location recently changed.
Apple [defines][apple-location-programming-guide] significant significant-change location updates as:
> The significant-change location service delivers updates only when there has been a significant change in the device’s location, such as 500 meters or more.
They also say in the [Energy Efficiency Guide][apple-energy-guide]:
> Significant-change location updates wake the system and your app once every 15 minutes, at minimum, even if no location changes have occurred.
Finally, I think this answer from [Stack Overflow][stackoverflow] says it best:
> The significant location change is the least accurate of all the location monitoring types. It only gets its updates when there is a cell tower transition or change. This can mean a varying level of accuracy and updates based on where the user is. City area, more updates with more towers. Out of town, interstate, fewer towers and changes.
What's the real story on significant-change location updates? Who knows, because Apple keeps it private.
## Location tracking in Home Assistant zones
At launch, Home Assistant for iOS sets up geofences for all zones in your Home Assistant configuration. Enter and exit notifications are sent to Home Assistant.
### Configuration
Add `track_ios: false` to your zone configurations to disable zone location tracking for all connected iOS apps.
### iBeacons
As of 1.0.3 the app has basic support for using iBeacons to trigger enter/exit updates. To configure them, add your iBeacon details to your zone like this:
```yaml
zone.home:
beacon:
uuid: B9407F30-F5F8-466E-AFF9-25556B57FE6D
major: 60042
minor: 43814
```
Restart Home Assistant and then the iOS app. It will then begin using iBeacons _instead of your location_ for enter and exit triggers around your zones. To add an iBeacon to `zone.home` add the above under your `customize`.
[apple-energy-guide]: https://developer.apple.com/library/content/documentation/Performance/Conceptual/EnergyGuide-iOS/LocationBestPractices.html#//apple_ref/doc/uid/TP40015243-CH24-SW4
[apple-location-programming-guide]: https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html#//apple_ref/doc/uid/TP40009497-CH2-SW9
[stackoverflow]: http://stackoverflow.com/a/13331625/486182

18
source/_docs/ecosystem/ios/notifications.markdown
View File

@ -1,18 +0,0 @@
---
title: "Notifications Introduction"
description: "Getting started with iOS notifications"
redirect_from: /ecosystem/ios/notifications/
---
The `ios` notify platform enables sending push notifications to the Home Assistant iOS app.
The 'ios' integration will automatically load the notify service.
The service integration can be called using `service: notify.ios_<your_device_ID>`.
Your device ID can be found in the `ios.conf` file in your configuration folder. The file is compressed JSON. You can view it easier by copying the file contents and pasting them into [JSONLint](http://jsonlint.com).
In this example, the device ID is `robbiet480_7plus`, so the notify service to use is `notify.ios_robbiet480_7plus`:
```json
{"devices":{"robbiet480_7plus":{"app":{"bundleIdentifer":"io.robbie.HomeAssistant","versionNumber":1,"buildNumber":53},"pushSounds":[],"permissions":["location"],"deviceId":"robbiet480_7plus","device":{"type":"iPhone 7 Plus","systemName":"iOS","systemVersion":"10.3","permanentID":"AB9F02FE-6AC6-47B8-ADEB-5DD87B489156","localizedModel":"iPhone","name":"Robbie's iPhone 7 Plus","model":"iPhone"},"battery":{"state":"Full","level":100},"pushToken":"SECRET","pushId":"SECRET"}}}
```
You can find more information in the [Basic Notifications](/docs/ecosystem/ios/notifications/basic/) documentation and the [Actionable Notifications](/docs/ecosystem/ios/notifications/actions/) documentation.

144
source/_docs/ecosystem/ios/notifications/actions.markdown
View File

@ -1,144 +0,0 @@
---
title: "Actionable notifications"
description: "Making push notifications a two way system"
redirect_from: /ecosystem/ios/notifications/actions/
---
Actionable notifications allow you to attach 1-4 custom buttons to a notification. When one of the actions is selected Home Assistant will be notified which action was chosen. This allows you to build complex automations.
Examples of actionable notifications:
- A notification is sent whenever motion is detected in your home while you are away or asleep. You can add an action to Sound Alarm. When tapped, Home Assistant is notified that the `sound_alarm` action was selected. You can add an automation to sound the burglar alarm whenever this event is seen.
- Someone rings your front door bell. You can send an action to lock or unlock your front door. When tapped, a notification is sent back to Home Assistant upon which you can build automations.
- Send a notification whenever your garage door opens with actions to open and close the garage.
<p class='img'>
<img src='/images/ios/actions.png' />
Actionable notifications allow the user to send a command back to Home Assistant.
</p>
## Overview of how actionable notifications work
In advance of sending a notification:
1. Define a notification category in your Home Assistant configuration which contain 1-4 actions.
2. At launch iOS app requests notification categories from Home Assistant (can also be done manually in notification settings).
When sending a notification:
1. Send a notification with `data.push.category` set to a pre-defined notification category identifier.
2. Push notification delivered to device
3. User opens notification.
3. Action tapped
4. Identifier of action sent back to HA as the `actionName` property of the event `ios.notification_action_fired`, along with other metadata such as the device and category name.
<p class='img'>
<img src='/images/ios/NotificationActionFlow.png' />
How the iOS device and Home Assistant work together to enable actionable notifications.
</p>
## Definitions
- Category - A category represents a type of notification that the app might receive. Think of it as a unique group of actions.
- Actions - An action consists of a button title and the information that iOS needs to notify the app when the action is selected. You create separate action objects for distinct action your app supports.
## Category parameters
- **name** (*Required*): A friendly name for this category.
- **identifier** (*Required*): A unique identifier for the category. Must be lowercase and have no special characters or spaces.
- **actions** (*Required*): A list of actions.
## Actions parameters
- **identifier** (*Required*): A unique identifier for this action. Must be uppercase and have no special characters or spaces. Only needs to be unique to the category, not unique globally.
- **title** (*Required*): The text to display on the button. Keep it short.
- **activationMode** (*Optional*): The mode in which to run the app when the action is performed. Setting this to `foreground` will make the app open after selecting. Default value is `background`.
- **authenticationRequired** (*Optional*): If `true`, the user must unlock the device before the action is performed.
- **destructive** (*Optional*): When the value of this property is a truthy value, the system displays the corresponding button differently to indicate that the action is destructive (text color is red).
- **behavior** (*Optional*): When `textInput` the system provides a way for the user to enter a text response to be included with the notification. The entered text will be sent back to Home Assistant. Default value is `default`.
- **textInputButtonTitle** (*Optional*): The button label. *Required* if `behavior` is `textInput`.
- **textInputPlaceholder** (*Optional*): The placeholder text to show in the text input field. Only used if `behavior` is `textInput` and the device runs iOS 10.
Here's a fully built example configuration:
```yaml
ios:
push:
categories:
- name: Alarm
identifier: 'alarm'
actions:
- identifier: 'SOUND_ALARM'
title: 'Sound Alarm'
activationMode: 'background'
authenticationRequired: true
destructive: true
behavior: 'default'
- identifier: 'SILENCE_ALARM'
title: 'Silence Alarm'
activationMode: 'background'
authenticationRequired: true
destructive: false
behavior: 'textInput'
textInputButtonTitle: 'Silencio!'
textInputPlaceholder: 'Placeholder'
```
## Building automations for notification actions
Here is an example automation to send a notification with a category in the payload:
```yaml
automation:
- alias: Notify iOS app
trigger:
...
action:
service: notify.ios_robbies_iphone_7_plus
data:
message: "Something happened at home!"
data:
push:
badge: 5
sound: <SOUND FILE HERE>
category: "alarm" # Needs to match the top level identifier you used in the ios configuration
action_data: # Anything passed in action_data will get echoed back to Home Assistant.
entity_id: light.test
my_custom_data: foo_bar
```
When an action is selected an event named `ios.notification_action_fired` will be emitted on the Home Assistant event bus. Below is an example payload.
```json
{
"sourceDeviceName": "Robbie's iPhone 7 Plus",
"sourceDeviceID": "robbies_iphone_7_plus",
"actionName": "SOUND_ALARM",
"sourceDevicePushId": "ab9f02fe-6ac6-47b8-adeb-5dd87b489156",
"textInput": "",
"actionData": {}
}
```
Here's an example automation for the given payload:
```yaml
automation:
- alias: Sound the alarm
trigger:
platform: event
event_type: ios.notification_action_fired
event_data:
actionName: SOUND_ALARM
action:
...
```
Notes:
* `textInput` will only exist if `behavior` was set to `textInput`.
* `actionData` is a dictionary with parameters passed in the `action_data` dictionary of the `push` dictionary in the original notification.
* When adding or updating push categories be sure to update push settings within the Home Assistant iOS app. This can be found within the app at **Settings** (gear icon) > **Notification Settings**.
## Compatibility with different devices
* For devices that support "Force Touch" / "3D Touch" - a long press on the notification will cause the actions to appear. Devices such as iPhone 6S, iPhone 6S Plus, iPhone 7, iPhone 7 Plus, iPhone 8, iPhone 8 Plus, iPhone X, iPhone XS, iPhone XS Max as well as some iPad and Apple Watch models.
* For device that do not support this feature - a left to right swipe on the notification + tap on 'View' button, will cause the relevant actions to appear. Devices such as iPhone 6 and below, iPhone SE, iPhone XR as some iPad models.

10
source/_docs/ecosystem/ios/notifications/architecture.markdown
View File

@ -1,10 +0,0 @@
---
title: "Architecture"
description: "The push notification system layout"
redirect_from: /ecosystem/ios/notifications/architecture/
---
<p class='img'>
<img src='/images/ios/PushNotificationLayout.png' />
The push notification infrastructure layout
</p>

71
source/_docs/ecosystem/ios/notifications/attachments.markdown
View File

@ -1,71 +0,0 @@
---
title: "Notification attachments"
description: "Adding attachments to iOS push notifications"
redirect_from: /ecosystem/ios/notifications/attachments/
---
iOS 10 adds _attachments_ to notifications. An attachment is an image, video, or audio file which is downloaded to the device when a notification is received and shown alongside the notification. A thumbnail is shown when the notification is not expanded. The full size attachment is shown when the notification is expanded.
<div class="note">
To expand a notification on 3D Touch devices simply force touch any notification. On non-3D Touch devices swipe and tap the "View" button.
</div>
```yaml
- alias: Notify iOS app
trigger:
...
action:
service: notify.ios_robbies_iphone_7_plus
data:
message: "Something happened at home!"
data:
attachment:
url: "https://github.com/home-assistant/home-assistant-assets/blob/master/logo-round-192x192.png?raw=true"
content-type: png
hide-thumbnail: false
```
Notes:
* The thumbnail of the notification will be the media at the `url`.
* The notification content is the media at the `url`.
* Attachment can be used with custom push notification categories.
## Example
<p class='img'>
<img src='/images/ios/attachment.png' />
An unexpanded push notification with an attachment.
</p>
<p class='img'>
<img src='/images/ios/expanded_attachment.png' />
The same notification but expanded to show the full size attachment
</p>
## Supported media types
If the attachment does not appear please ensure it is in one of the following formats:
### Audio attachments
Maximum file size: 5 MB
Allowed Formats: AIFF, WAV, MP3, MPEG4 Audio
### Image attachments
Maximum file size: 10 MB
Allowed Formats: JPEG, GIF, PNG
### Video attachments
Maximum file size: 50 MB
Allowed Formats: MPEG, MPEG2, MPEG4, AVI
## Configuration
- **url** (*Required*): The URL of content to use as the attachment. This URL _must_ be accessible from the Internet, or the receiving device must be on the same network as the hosted content.
- **content-type** (*Optional*): By default, the extension of the URL will be checked to determine the filetype. If there is no extension/it can't be determined you can manually provide a file extension.
- **hide-thumbnail** (*Optional*): If set to `true` the thumbnail will not show on the notification. The content will only be viewable by expanding.

99
source/_docs/ecosystem/ios/notifications/basic.markdown
View File

@ -1,99 +0,0 @@
---
title: "Basic Notifications"
description: "Basic notes about iOS notifications"
redirect_from: /ecosystem/ios/notifications/basic/
---
The iOS notify platform accepts the standard `title`, `message` and `target` parameters. The iOS notify platform supports targets as services. Assuming that you did not set a `name` when configuring the platform you should find all your registered and notification-enabled iOS devices available as notify targets as services with names prefixed "notify.ios_" and then the device name you entered at setup.
Notes:
* `title` only displays on Apple Watch and devices with iOS 10 or above.
* `target` can be used to specific a single device using its PushID, found in `ios.conf`. The preferred way of providing a target is through a target specific notify service.
<p class='img'>
<img src='/images/ios/example.png' />
A push notification showing all of the basic options `title` and `message` as well as `subtitle` and [actions](/ecosystem/ios/notifications/actions/).
</p>
### Enhancing basic notifications
#### Badge
You can set the icon badge in the payload:
```yaml
automation:
- alias: Notify iOS app
trigger:
...
action:
service: notify.ios_<your_device_id_here>
data:
title: "Smart Home Alerts"
message: "Something happened at home!"
data:
push:
badge: 5
```
#### Subtitle
Starting with iOS 10, a subtitle is supported in addition to the title:
```yaml
automation
- alias: Notify iOS app
trigger:
...
action:
service: notify.ios_<your_device_id_here>
data:
title: "Smart Home Alerts"
message: "Something happened at home!"
data:
subtitle: "Subtitle goes here"
```
#### Thread-id (grouping notifications)
Starting with iOS 12, grouping of notifications is supported. All notifications with the same thread-id will be grouped together in the notification center. Without a thread-id, all notifications from the app will be placed in a single group.
```yaml
automation:
- alias: Notify iOS app
trigger:
...
action:
service: notify.ios_<your_device_id_here>
data:
title: "Smart Home Alerts"
message: "Something happened at home!"
data:
push:
thread-id: "example-notification-group"
```
### Sending notifications to multiple phones
To send notifications to multiple phones, create a [notification group](/integrations/notify.group/):
```yaml
notify:
- name: NOTIFIER_NAME
platform: group
services:
- service: ios_iphone_one
- service: ios_iphone_two
```
Now, you can send notifications to everyone in the group using:
```yaml
automation:
- alias: Notify iOS app
trigger:
...
action:
service: notify.NOTIFIER_NAME
data:
message: "Something happened at home!"
data:
push:
badge: 5
```

103
source/_docs/ecosystem/ios/notifications/content_extensions.markdown
View File

@ -1,103 +0,0 @@
---
title: "Dynamic content"
description: "Extend your notifications with dynamic content"
redirect_from: /ecosystem/ios/notifications/content_extensions/
---
With the new Content Extension feature found in iOS 10, dynamic content can now be displayed as part of a notification without opening an app.
# Map
Will show a map with a red tipped pin at the coordinates given.
The map will be centered at the coordinates given.
```yaml
service: notify.ios_<your_device_id_here>
data:
message: Something happened at home!
data:
push:
category: map
action_data:
latitude: "40.785091"
longitude: "-73.968285"
```
## Showing a second pin
You can use the following properties under `action_data` to display a second pin. If used, the first pin will be red and the second green.
- **second_latitude**: The latitude of the second pin. **Must be a string!**
- **second_longitude**: The longitude of the second pin. **Must be a string!**
- **shows_line_between_points**: A Boolean value indicating whether a line should be drawn between the first and second pin.
## Extra configuration
You can also pass the following properties under `action_data` to modify the map in various ways. All are expected to be boolean values unless otherwise noted:
- **shows_compass**: A Boolean indicating whether the map displays a compass control.
- **shows_points_of_interest**: A Boolean indicating whether the map displays point-of-interest information.
- **shows_scale**: A Boolean indicating whether the map shows scale information.
- **shows_traffic**: A Boolean value indicating whether the map displays traffic information.
- **shows_user_location**: A Boolean value indicating whether the map should try to display the user’s location.
<p class='img'>
<img src='/images/ios/map.png' />
An example of the map dynamic content.
</p>
# Camera Stream
The notification thumbnail will be a still image from the camera.
The notification content is a real time MJPEG stream of a camera (assuming the camera supports it).
You can use the attachment parameters `content-type` and `hide-thumbnail` with camera to control the thumbnail.
You can view an example [here](https://www.youtube.com/watch?v=LmYwpxPKW0g).
Note: This functionality is only available from iOS 11 onwards.
```yaml
service: notify.ios_<your_device_id_here>
data:
message: Motion detected in the Living Room
data:
attachment:
content-type: jpeg
push:
category: camera
entity_id: camera.demo_camera
```
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube.com/embed/LmYwpxPKW0g" frameborder="0" allowfullscreen></iframe>
</div>
# Combining with actionable notifications
As you can see the `category` key is used to tell the device what kind of content extension to use. You can use the same category identifiers in your own custom [actions](/ecosystem/ios/notifications/actions/) to add actions to the content extension.
For example this configuration adds actions to a camera content message.
```yaml
ios:
push:
categories:
- name: Camera With Actions
identifier: 'camera'
actions:
- identifier: 'OPEN_COVER'
title: 'Open Cover'
activationMode: 'background'
authenticationRequired: true
destructive: no
- identifier: 'CLOSE_COVER'
title: 'Close Cover'
activationMode: 'background'
authenticationRequired: true
destructive: true
```
# Troubleshooting
If you are having problems with receiving these special notifications try restarting your phone first. The extensions somewhat often fail to register properly until a restart.

17
source/_docs/ecosystem/ios/notifications/privacy_security_rate_limits.markdown
View File

@ -1,17 +0,0 @@
---
title: "Privacy, rate limiting and security"
description: "Notes about important topics relating to push notifications"
redirect_from: /ecosystem/ios/notifications/privacy_security_rate_limits/
---
## Privacy
No notification content is stored on remote servers. Only the required push registration data and a simple counter of the total number of push notifications sent per day per device (for rate limiting purposes) is kept.
## Rate limiting
Currently, you are allowed to send a maximum of 150 push notifications per day per device. This is to ensure that the service remains cheap to maintain. In the future we may add support for upgrading to allow more notifications. The rate limit resets at midnight UTC daily. When a notification is sent your current rate limits (including sent notifications and notifications remaining for the day) will be output to your Home Assistant logs. If an error occurs while sending a notification your rate limit will not be affected.
## Security
All traffic between your Home Assistant instance, the push infrastructure, and Apple, is encrypted with SSL.

25
source/_docs/ecosystem/ios/notifications/requesting_location_updates.markdown
View File

@ -1,25 +0,0 @@
---
title: "Requesting location updates"
description: "Ask the device to send a location update remotely"
redirect_from: /ecosystem/ios/notifications/requesting_location_updates/
---
<div class="note warning">
Do not rely on this functionality due to the time limits mentioned below.
</div>
You can force a device to attempt to report its location by sending a special notification.
```yaml
automation
- alias: Notify iOS app
trigger:
...
action:
service: notify.ios_<your_device_id_here>
data:
message: "request_location_update"
```
Assuming the device receives the notification, it will attempt to get a location update within 5 seconds and report it to Home Assistant. This is a little bit hit or miss since Apple imposes a maximum time allowed for the app to work with the notification and location updates sometimes take longer than usual due to factors such as waiting for GPS acquisition.

180
source/_docs/ecosystem/ios/notifications/sounds.markdown
View File

@ -1,180 +0,0 @@
---
title: "Notification Sounds"
description: "Adding sounds to notifications"
redirect_from: /ecosystem/ios/notifications/sounds/
---
Adding a custom sound to a notification allows you to easily identify the notification without even looking at your device. Home Assistant for iOS comes with some notification sounds pre-installed but you can also upload your own.
Here is an example notification that uses one of the pre-installed sounds.
```yaml
- alias: Notify iOS app
trigger:
...
action:
service: notify.ios_<your_device_id_here>
data:
message: “Something happened at home!”
data:
push:
sound: "US-EN-Morgan-Freeman-Roommate-Is-Arriving.wav"
```
Notes:
* You must use the full filename in the payload (including extension).
## Custom push notification sounds
The app allows you to use your own custom sounds in push notifications. The sounds must be formatted as 32bit float 48000Hz wav files. You set the filename of the sound in the notification payload. To add sounds:
1. Connect the device to a PC or Mac running the latest version of iTunes.
2. Go to the device in iTunes.
3. Select "File Sharing" in the left-hand menu.
4. Select Home Assistant.
5. Drag and drop properly formatted sounds (32bit float 48000Hz wav files).
6. Click Sync in the lower right.
7. Once the sync is complete, disconnect the device from the computer.
8. On your iOS device, open the Home Assistant app.
9. Go to Settings -> Notification Settings.
10. Select "Import sounds from iTunes".
Assuming that you correctly formatted the sounds they are now available to use in push notifications.
Notes:
* **Please note that due to a bug in iOS 10 you may need to restart your entire device before notification sounds can be played. This should hopefully be fixed by Apple soon.**
* Uploading a file with the same name as an existing one will overwrite the original.
* You can view what sounds are installed on each device by inspecting the `ios.conf` file in your configuration directory. They are listed in the `pushSounds` array.
### Preinstalled notification sounds
```txt
US-EN-Alexa-Back-Door-Opened.wav
US-EN-Alexa-Back-Door-Unlocked.wav
US-EN-Alexa-Basement-Door-Opened.wav
US-EN-Alexa-Basement-Door-Unlocked.wav
US-EN-Alexa-Boyfriend-Is-Arriving.wav
US-EN-Alexa-Daughter-Is-Arriving.wav
US-EN-Alexa-Front-Door-Opened.wav
US-EN-Alexa-Front-Door-Unlocked.wav
US-EN-Alexa-Garage-Door-Opened.wav
US-EN-Alexa-Girlfriend-Is-Arriving.wav
US-EN-Alexa-Good-Morning.wav
US-EN-Alexa-Good-Night.wav
US-EN-Alexa-Husband-Is-Arriving.wav
US-EN-Alexa-Mail-Has-Arrived.wav
US-EN-Alexa-Motion-At-Back-Door.wav
US-EN-Alexa-Motion-At-Front-Door.wav
US-EN-Alexa-Motion-Detected-Generic.wav
US-EN-Alexa-Motion-In-Back-Yard.wav
US-EN-Alexa-Motion-In-Basement.wav
US-EN-Alexa-Motion-In-Front-Yard.wav
US-EN-Alexa-Motion-In-Garage.wav
US-EN-Alexa-Patio-Door-Opened.wav
US-EN-Alexa-Patio-Door-Unlocked.wav
US-EN-Alexa-Smoke-Detected-Generic.wav
US-EN-Alexa-Smoke-Detected-In-Basement.wav
US-EN-Alexa-Smoke-Detected-In-Garage.wav
US-EN-Alexa-Smoke-Detected-In-Kitchen.wav
US-EN-Alexa-Son-Is-Arriving.wav
US-EN-Alexa-Water-Detected-Generic.wav
US-EN-Alexa-Water-Detected-In-Basement.wav
US-EN-Alexa-Water-Detected-In-Garage.wav
US-EN-Alexa-Water-Detected-In-Kitchen.wav
US-EN-Alexa-Welcome-Home.wav
US-EN-Alexa-Wife-Is-Arriving.wav
US-EN-Daisy-Back-Door-Motion.wav
US-EN-Daisy-Back-Door-Open.wav
US-EN-Daisy-Front-Door-Motion.wav
US-EN-Daisy-Front-Door-Open.wav
US-EN-Daisy-Front-Window-Open.wav
US-EN-Daisy-Garage-Door-Open.wav
US-EN-Daisy-Guest-Bath-Leak.wav
US-EN-Daisy-Kitchen-Sink-Leak.wav
US-EN-Daisy-Kitchen-Window-Open.wav
US-EN-Daisy-Laundry-Room-Leak.wav
US-EN-Daisy-Master-Bath-Leak.wav
US-EN-Daisy-Master-Bedroom-Window-Open.wav
US-EN-Daisy-Office-Window-Open.wav
US-EN-Daisy-Refrigerator-Leak.wav
US-EN-Daisy-Water-Heater-Leak.wav
US-EN-Morgan-Freeman-Back-Door-Closed.wav
US-EN-Morgan-Freeman-Back-Door-Locked.wav
US-EN-Morgan-Freeman-Back-Door-Opened.wav
US-EN-Morgan-Freeman-Back-Door-Unlocked.wav
US-EN-Morgan-Freeman-Basement-Door-Closed.wav
US-EN-Morgan-Freeman-Basement-Door-Locked.wav
US-EN-Morgan-Freeman-Basement-Door-Opened.wav
US-EN-Morgan-Freeman-Basement-Door-Unlocked.wav
US-EN-Morgan-Freeman-Boss-Is-Arriving.wav
US-EN-Morgan-Freeman-Boyfriend-Is-Arriving.wav
US-EN-Morgan-Freeman-Cleaning-Supplies-Closet-Opened.wav
US-EN-Morgan-Freeman-Coworker-Is-Arriving.wav
US-EN-Morgan-Freeman-Daughter-Is-Arriving.wav
US-EN-Morgan-Freeman-Friend-Is-Arriving.wav
US-EN-Morgan-Freeman-Front-Door-Closed.wav
US-EN-Morgan-Freeman-Front-Door-Locked.wav
US-EN-Morgan-Freeman-Front-Door-Opened.wav
US-EN-Morgan-Freeman-Front-Door-Unlocked.wav
US-EN-Morgan-Freeman-Garage-Door-Closed.wav
US-EN-Morgan-Freeman-Garage-Door-Opened.wav
US-EN-Morgan-Freeman-Girlfriend-Is-Arriving.wav
US-EN-Morgan-Freeman-Good-Morning.wav
US-EN-Morgan-Freeman-Good-Night.wav
US-EN-Morgan-Freeman-Liquor-Cabinet-Opened.wav
US-EN-Morgan-Freeman-Motion-Detected.wav
US-EN-Morgan-Freeman-Motion-In-Basement.wav
US-EN-Morgan-Freeman-Motion-In-Bedroom.wav
US-EN-Morgan-Freeman-Motion-In-Game-Room.wav
US-EN-Morgan-Freeman-Motion-In-Garage.wav
US-EN-Morgan-Freeman-Motion-In-Kitchen.wav
US-EN-Morgan-Freeman-Motion-In-Living-Room.wav
US-EN-Morgan-Freeman-Motion-In-Theater.wav
US-EN-Morgan-Freeman-Motion-In-Wine-Cellar.wav
US-EN-Morgan-Freeman-Patio-Door-Closed.wav
US-EN-Morgan-Freeman-Patio-Door-Locked.wav
US-EN-Morgan-Freeman-Patio-Door-Opened.wav
US-EN-Morgan-Freeman-Patio-Door-Unlocked.wav
US-EN-Morgan-Freeman-Roommate-Is-Arriving.wav
US-EN-Morgan-Freeman-Searching-For-Car-Keys.wav
US-EN-Morgan-Freeman-Setting-The-Mood.wav
US-EN-Morgan-Freeman-Smartthings-Detected-A-Flood.wav
US-EN-Morgan-Freeman-Smartthings-Detected-Carbon-Monoxide.wav
US-EN-Morgan-Freeman-Smartthings-Detected-Smoke.wav
US-EN-Morgan-Freeman-Smoke-Detected-In-Basement.wav
US-EN-Morgan-Freeman-Smoke-Detected-In-Garage.wav
US-EN-Morgan-Freeman-Smoke-Detected-In-Kitchen.wav
US-EN-Morgan-Freeman-Someone-Is-Arriving.wav
US-EN-Morgan-Freeman-Son-Is-Arriving.wav
US-EN-Morgan-Freeman-Starting-Movie-Mode.wav
US-EN-Morgan-Freeman-Starting-Party-Mode.wav
US-EN-Morgan-Freeman-Starting-Romance-Mode.wav
US-EN-Morgan-Freeman-Turning-Off-All-The-Lights.wav
US-EN-Morgan-Freeman-Turning-Off-The-Air-Conditioner.wav
US-EN-Morgan-Freeman-Turning-Off-The-Bar-Lights.wav
US-EN-Morgan-Freeman-Turning-Off-The-Chandelier.wav
US-EN-Morgan-Freeman-Turning-Off-The-Family-Room-Lights.wav
US-EN-Morgan-Freeman-Turning-Off-The-Hallway-Lights.wav
US-EN-Morgan-Freeman-Turning-Off-The-Kitchen-Light.wav
US-EN-Morgan-Freeman-Turning-Off-The-Light.wav
US-EN-Morgan-Freeman-Turning-Off-The-Lights.wav
US-EN-Morgan-Freeman-Turning-Off-The-Mood-Lights.wav
US-EN-Morgan-Freeman-Turning-Off-The-TV.wav
US-EN-Morgan-Freeman-Turning-On-The-Air-Conditioner.wav
US-EN-Morgan-Freeman-Turning-On-The-Bar-Lights.wav
US-EN-Morgan-Freeman-Turning-On-The-Chandelier.wav
US-EN-Morgan-Freeman-Turning-On-The-Family-Room-Lights.wav
US-EN-Morgan-Freeman-Turning-On-The-Hallway-Lights.wav
US-EN-Morgan-Freeman-Turning-On-The-Kitchen-Light.wav
US-EN-Morgan-Freeman-Turning-On-The-Light.wav
US-EN-Morgan-Freeman-Turning-On-The-Lights.wav
US-EN-Morgan-Freeman-Turning-On-The-Mood-Lights.wav
US-EN-Morgan-Freeman-Turning-On-The-TV.wav
US-EN-Morgan-Freeman-Vacate-The-Premises.wav
US-EN-Morgan-Freeman-Water-Detected-In-Basement.wav
US-EN-Morgan-Freeman-Water-Detected-In-Garage.wav
US-EN-Morgan-Freeman-Water-Detected-In-Kitchen.wav
US-EN-Morgan-Freeman-Welcome-Home.wav
US-EN-Morgan-Freeman-Wife-Is-Arriving.wav
```

2
source/_docs/scene/editor.markdown
View File

@ -73,5 +73,5 @@ For example:
```
<div class='note'>
Any comments in the YAML file will be lost and templates will be reformatted when you update an automation via the editor.
Any comments in the YAML file will be lost and templates will be reformatted when you update a scene via the editor.
</div>

2
source/_integrations/aftership.markdown
View File

@ -14,7 +14,7 @@ The sensor value shows the number of packages that are not in `Delivered` state.
## Setup
To use this sensor, you need an [AfterShip Account](https://accounts.aftership.com/register) and set up an API Key. To set up an API Key go to [AfterShip API](https://secure.aftership.com/#/settings/api) page, and copy existing key or generate a new one.
To use this sensor, you need an [AfterShip Account](https://accounts.aftership.com/register) and set up an API Key. To set up an API Key go to [AfterShip API](https://admin.aftership.com/settings/api-keys) page, and copy existing key or generate a new one.
<div class='note info'>
AfterShip recently started requiring having a credit card on file even if you are only using the free plan. That does not change the functionality of the platform, just something to be aware of.

2
source/_integrations/almond.markdown
View File

@ -45,6 +45,8 @@ The Almond integration does not update config entries yet. If you make a change
Stanford offers a hosted version of Almond Server called Almond Web. To use this, go to the integrations page and add Almond using the add integration flow.
Your Home Assistant installation needs to be externally accessible if you want Almond Web to be able to control Home Assistant.
### Almond Web - Manual installation
It is possible to set up Almond Web manually. You will need to create your own client ID and secret in the web interface.

4
source/_integrations/androidtv.markdown
View File

@ -249,7 +249,9 @@ A list of various intents can be found [here](https://gist.github.com/mcfrojd/9e
## Custom State Detection
The `state_detection_rules` configuration parameter allows you to provide your own rules for state detection. The keys are app IDs, and the values are lists of rules that are evaluated in order. Valid rules are:
The Android TV integration works by polling the Android TV / Fire TV device at a regular interval and collecting a handful of properties. Unfortunately, there is no standard API for determining the state of the device to which all apps adhere. Instead, the backend `androidtv` package uses three of the properties that it collects to determine the state: `audio_state`, `media_session_state`, and `wake_lock_size`. The correct logic for determining the state differs depending on the current app, and the backend `androidtv` package implements app-specific state detection logic for a handful of apps. Of course, it is not feasible to implement custom logic for each and every app in the `androidtv` package. Moreover, the correct state detection logic may differ across devices and device configurations.
The solution to this problem is the `state_detection_rules` configuration parameter, which allows you to provide your own rules for state detection. The keys are app IDs, and the values are lists of rules that are evaluated in order. Valid rules are:
* `'standby'`, `'playing'`, `'paused'`, `'idle'`, or `'off'`
* If this is not a map, then this state will always be reported when this app is the current app

2
source/_integrations/azure_service_bus.markdown
View File

@ -3,7 +3,7 @@ title: "Azure Service Bus"
description: "Setup for Azure Service Bus integration"
logo: azure_service_bus.svg
ha_category:
- Notification
- Notifications
ha_release: 0.102
---

1
source/_integrations/comfoconnect.markdown
View File

@ -6,6 +6,7 @@ ha_category:
- Fan
- Sensor
ha_release: 0.48
ha_iot_class: "Local Push"
---
The `comfoconnect` integration lets you control Zehnder ComfoAir [Q350](https://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q350-tr)/[Q450](https://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q450-tr)/[Q600](https://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q600-st)

2
source/_integrations/envisalink.markdown
View File

@ -137,5 +137,5 @@ The following services are supported by Envisalink and can be used to script or
- **alarm_arm_away**: Arms the alarm in standard away mode.
- **alarm_arm_night**: Arms the alarm in night mode.
- **alarm_trigger**: Trigger an alarm on the Envisalink connected alarm system. For example, a newer zwave/zigbee sensor can now be integrated into a legacy alarm system using a Home Assistant automation.
- **alarm_keypress**: Sends a string of up to 6 characters to the alarm. *DSC alarms only*
- **alarm_keypress**: Sends a string of up to 6 characters to the alarm. *Works with DSC panels, and confirmed to work with Honeywell Vista-20P (aka First Alert FA-168)*
- **invoke_custom_function**: Invokes a custom PGM function. *DSC alarms only*

5
source/_integrations/fan.mqtt.markdown
View File

@ -180,11 +180,11 @@ device:
type: string
{% endconfiguration %}
<dkv class='note warning'>
<div class='note warning'>
Make sure that your topics match exactly. `some-topic/` and `some-topic` are different topics.
</dkv>
</div>
## Examples
@ -214,6 +214,7 @@ fan:
payload_medium_speed: "medium"
payload_high_speed: "high"
speeds:
- "off"
- low
- medium
- high

32
source/_integrations/fan.xiaomi_miio.markdown
View File

@ -29,6 +29,7 @@ Air Purifier Super | zhimi.airpurifier.sa1 | |
Air Purifier Super 2 | zhimi.airpurifier.sa2 | |
Air Humidifier | zhimi.humidifier.v1 | |
Air Humidifier CA1 | zhimi.humidifier.ca1 | |
Air Humidifier CB1 | zhimi.humidifier.cb1 | |
Air Fresh VA2 | zhimi.airfresh.va2 | |
@ -246,6 +247,33 @@ Air Fresh VA2 | zhimi.airfresh.va2 | |
- depth
- dry
### Air Humidifier CB (zhimi.humidifier.cb1)
- On, Off
- Operation modes (silent, medium, high, auto)
- Buzzer (on, off)
- Child lock (on, off)
- LED (on, off), LED brightness (bright, dim, off)
- Target humidity (30, 40, 50, 60, 70, 80)
- Dry mode (on, off)
- Attributes
- speed
- speed_list
- model
- temperature
- humidity
- mode
- buzzer
- child_lock
- target_humidity
- led_brightness
- use_time
- hardware_version
- motor_speed
- depth
- dry
- supported_features
### Air Fresh VA2
* Power (on, off)
@ -447,7 +475,7 @@ Set the target humidity.
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `humidity` | no | Target humidity. Allowed values are 30, 40, 50, 60, 70 and 80 |
### Service `xiaomi_miio.fan_set_dry_on` (Air Humidifier CA only)
### Service `fan.xiaomi_miio_set_dry_on` (Air Humidifier CA and CB)
Turn the dry mode on.
@ -455,7 +483,7 @@ Turn the dry mode on.
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_dry_off` (Air Humidifier CA only)
### Service `fan.xiaomi_miio_set_dry_off` (Air Humidifier CA and CB)
Turn the dry mode off.

1
source/_integrations/gc100.markdown
View File

@ -7,6 +7,7 @@ ha_category:
- Switch
ha_release: 0.57
ha_iot_class: Local Polling
logo: global-cache.png
---
The Global Caché [GC-100](https://www.globalcache.com/products/gc-100/) can be integrated into Home Assistant. GC-100 is a TCP-controllable

4
source/_integrations/group.markdown
View File

@ -10,7 +10,7 @@ ha_release: pre 0.7
Groups allow the user to combine multiple entities into one.
Check the **Set State** <img src='/images/screenshots/developer-tool-states-icon.png' class='no-shadow' height='38' /> page from the **Developer Tools** and browse the **Current entities:** listing for all available entities.
Check the **States** <img src='/images/screenshots/developer-tool-states-icon.png' class='no-shadow' height='38' /> page from the **Developer Tools** and browse the **Current entities:** listing for all available entities.
```yaml
# Example configuration.yaml entry
@ -70,7 +70,7 @@ Some integrations automatically create special groups containing integration ent
- `group.all_scripts`
- `group.all_automations`
You can see list of these groups in **State** <img src='/images/screenshots/developer-tool-states-icon.png' class='no-shadow' height='38' /> page of the **Developer Tools**.
You can see list of these groups in **States** <img src='/images/screenshots/developer-tool-states-icon.png' class='no-shadow' height='38' /> page of the **Developer Tools**.
## Group behavior

6
source/_integrations/homematic.markdown
View File

@ -32,6 +32,12 @@ There is currently support for the following device types within Home Assistant:
Device support is available for most of the wired and wireless devices, as well as a lot of IP devices. If you have a setup with mixed protocols, you have to configure additional [interfaces](/integrations/homematic#interfaces) with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 **and** require you to set the `path` setting to `/groups`. When using SSL on a CCU3, by default the same ports as usual with a prepended 4 are available. So 2001 becomes 42001, 2010 becomes 42010 etc..
<div class='note info'>
Since CCU Version 3, the internal firewalls are enabled by default. You have to grant full access for the `XML-RPC API` or specify the IP-address of the Home-Assistant server and whitelist it, inside the CCU's security settings.
</div>
If you want to see if a specific device you have is supported, head over to the [pyhomematic](https://github.com/danielperna84/pyhomematic/tree/master/pyhomematic/devicetypes) repository and browse through the source code. A dictionary with the device identifiers (e.g., HM-Sec-SC-2) can be found within the relevant modules near the bottom. If your device is not supported, feel free to contribute.
We automatically detect all devices we currently support and try to generate useful names. If you enable name-resolving, we try to fetch names from Metadata (Homegear), via JSON-RPC or the XML-API you may have installed on your CCU. Since this may fail this is disabled by default.

2
source/_integrations/honeywell.markdown
View File

@ -8,7 +8,7 @@ ha_release: pre 0.7
ha_iot_class: Cloud Polling
---
The `honeywell` climate platform integrates Home Assistant with _US-based_ [Honeywell Total Connect Comfort (TCC)](https://mytotalconnectcomfort.com/portal/]) climate systems.
The `honeywell` climate platform integrates Home Assistant with _US-based_ [Honeywell Total Connect Comfort (TCC)](https://mytotalconnectcomfort.com/portal/) climate systems.
It does not support the home security functionality of TCC.

6
source/_integrations/life360.markdown
View File

@ -19,6 +19,12 @@ Then in the Home Assistant user interface (UI), click on Configuration in the le
If you would like to set any advanced options, see the following section. You may want to do this before entering your Life360 account information in the UI, or you can change it at any time. Any of the advanced options you want to set from the section below will need to be set manually in your configuration.yaml file. They are not able to be set from the UI. You can also enter your account information in the configuration file (in addition to, or instead of, the UI) if you prefer.
After configuring, you should see a new Life360 device tracker entity showing up on the States page. If it does not:
- Check the [device tracker documentation](/integrations/device_tracker), especially the `new_device_defaults` setting.
- Check your `known_devices.yaml`; `tracking` should be `true` for your Life360 device.
- In the Life360 app, Location Sharing should be enabled.
{% configuration %}
accounts:
description: Your Life360 account information.

6
source/_integrations/luci.markdown
View File

@ -11,12 +11,6 @@ _This is one of multiple ways we support OpenWRT. For an overview, see [openwrt]
This is a presence detection scanner for OpenWRT using [luci](https://openwrt.org/docs/techref/luci).
<div class='note'>
This integration requires a [workaround](https://github.com/home-assistant/home-assistant/issues/1258#issuecomment-252469880) when using luci with HTTPS and a self-signed certificate.
</div>
Before this scanner can be used you have to install the luci RPC package on OpenWRT:
```bash

2
source/_integrations/media_player.markdown
View File

@ -13,7 +13,7 @@ Interacts with media players on your network.
## Services
### Media control services
Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, `volume_set`, `volume_mute`, `media_play_pause`, `media_play`, `media_pause`, `media_stop`, `media_next_track`, `media_previous_track`, `clear_playlist`, `shuffle_set`
Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, `volume_set`, `volume_mute`, `media_play_pause`, `media_play`, `media_pause`, `media_stop`, `media_next_track`, `media_previous_track`, `clear_playlist`, `shuffle_set`, `play_media`, `select_source`, `select_sound_mode`
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ------------------------------------------------ |

2
source/_integrations/miflora.markdown
View File

@ -80,7 +80,7 @@ monitored_conditions:
conductivity:
description: Conductivity in the soil.
battery:
description: Battery details.
description: Battery details. Cached and only updated once a day.
name:
description: The name displayed in the frontend.
required: false

5
source/_integrations/mobile_app.markdown
View File

@ -22,3 +22,8 @@ This integration is by default enabled, unless you've disabled or removed the [`
# Example configuration.yaml entry
mobile_app:
```
## Apps that use Mobile App
- [Home Assistant for iOS](https://apps.apple.com/us/app/home-assistant/id1099568401?ls=1) (official)
- [Home Assistant for Android](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android) (official)

2
source/_integrations/nmbs.markdown
View File

@ -58,5 +58,5 @@ show_on_map:
<p class='img'>
<img src='{{site_root}}/images/screenshots/nmbs-card-example.png' />
<p>Example using the Lovelace Attributes card</p>
<p>Example using the <a href="https://github.com/custom-cards/entity-attributes-card">Lovelace Attributes custom card</a> </p>
</p>

4
source/_integrations/notify.markdown
View File

@ -8,7 +8,7 @@ ha_qa_scale: internal
ha_release: 0.7
---
The `notify` integration makes it possible to send notifications to a wide variety of platforms. Please check the sidebar for a full list of platforms that are supported.
The `notify` integration makes it possible to send notifications to a wide variety of platforms. To use it you have to setup at least one notification target (notifier), check the [integrations list](/integrations/#notifications) for one that fits your use case.
If you want to send notifications to the Home Assistant web interface, you may use the [Persistent Notification integration](/integrations/persistent_notification/).
@ -37,7 +37,7 @@ action:
### Test if it works
A simple way to test if you have set up your notify platform correctly, is to open **Developer Tools** from the sidebar and then select the **Services** tab. Choose your service from the **Service** dropdown menu, enter the sample below into the **Service Data** field, and press the **CALL SERVICE** button.
After you setup a [notifier](/integrations/#notifications) a simple way to test if you have set up your notify platform correctly, is to open **Developer Tools** from the sidebar and then select the **Services** tab. Choose your service from the **Service** dropdown menu, enter the sample below into the **Service Data** field, and press the **CALL SERVICE** button.
```json
{

8
source/_integrations/nuki.markdown
View File

@ -48,11 +48,3 @@ See the [Nuki Website](https://nuki.io/en/support/smart-lock/sl-features/locking
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that point at `entity_id`s Nuki Locks.
| `unlatch` | yes | Boolean - Whether to unlatch the door when first opening it.
### Service `check_connection`
This will force the communication between the bridge and the lock, updating the available attribute.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that point at `entity_id`s Nuki Locks.

1
source/_integrations/orangepi_gpio.markdown
View File

@ -6,6 +6,7 @@ ha_category:
- Binary Sensor
ha_release: 0.93
ha_iot_class: Local Push
logo: orange-pi.png
---
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.

8
source/_integrations/picotts.markdown
View File

@ -11,6 +11,14 @@ The `picotts` text-to-speech platform uses offline pico Text-to-Speech engine to
This requires to install the pico tts library on the system, typically on debian just do `sudo apt-get install libttspico-utils`
On some Raspbian release, this package is missing but you can just copy the arm deb package from debian.
On Debian Buster, the package is missing, use the following commands to install it:
```
wget http://ftp.us.debian.org/debian/pool/non-free/s/svox/libttspico0_1.0+git20130326-9_armhf.deb
wget http://ftp.us.debian.org/debian/pool/non-free/s/svox/libttspico-utils_1.0+git20130326-9_armhf.deb
sudo apt-get install -f ./libttspico0_1.0+git20130326-9_armhf.deb ./libttspico-utils_1.0+git20130326-9_armhf.deb
```
## Configuration
To enable text-to-speech with Pico, add the following lines to your `configuration.yaml`:

1
source/_integrations/samsungtv.markdown
View File

@ -118,6 +118,7 @@ Currently tested but not working models:
- JU7500 - Unable to see state and unable to control
- MU6125 - Unable to see state and unable to control (Tested on UE58MU6125 on port 8001 and 8801)
- MU6300 - Port set to 8001, turning on works, status not working reliably, turning off is not permanent (it comes back on)
- MU6400 - Unable to see state and unable to control (using latest 1270 firmware. Had limited functionality on previous firmware)
- Q60 – turning on works, turning off does not work, State is always "off".
- Q6F – Port set to 8001, turning on works, turning off does not work, status not working reliably.
- Q7F - State is always "off" and unable to control via port 8001.

4
source/_integrations/satel_integra.markdown
View File

@ -52,6 +52,10 @@ port:
required: false
default: 7094
type: integer
code:
description: The INTEGRA ID (found in DLOADX under "Communication configuration" or in polish "Komunikacja Konfiguracji" section), it's needed for making use of the switchable_outputs.
required: false
type: string
partitions:
description: List of the partitions to operate on.
required: false

2
source/_integrations/smartthings.markdown
View File

@ -46,7 +46,7 @@ If you are using Home Assistant Cloud (Nabu Casa) the integration will create a
1. A [personal access token](https://account.smartthings.com/tokens) tied to a Samsung or SmartThings account (see below for instructions).
2. Home Assistant setup for [remote access](/docs/configuration/remote/) via a domain name secured with SSL. *Self-signed SSL certificates are not supported by the SmartThings Cloud API.*
3. [`base_url` of the http component](/integrations/http#base_url) set the URL that Home Assistant is available on the internet.
3. [`base_url` of the http integration](/integrations/http#base_url) set the URL that Home Assistant is available on the internet. SmartThings requires the `base_url` and Home Assistant to use the standard HTTPS port (443).
## Setup instructions

2
source/_integrations/snips.markdown
View File

@ -27,7 +27,7 @@ The Snips platform can be installed via the Snips APT/Debian repository.
sudo apt-get update
sudo apt-get install -y dirmngr
sudo bash -c 'echo "deb https://raspbian.snips.ai/$(lsb_release -cs) stable main" > /etc/apt/sources.list.d/snips.list'
sudo apt-key adv --keyserver pgp.mit.edu --recv-keys D4F50CDCA10A2849
sudo apt-key adv --fetch-keys https://raspbian.snips.ai/531DD1A7B702B14D.pub
sudo apt-get update
sudo apt-get install -y snips-platform-voice
```

2
source/_integrations/spotify.markdown
View File

@ -81,7 +81,7 @@ name:
## Setup
After the prerequisites and configuration are complete, restart Home Assistant.
A **Spotify** configurator element will be available. Follow the instructions to
Under notifications a **Spotify** configurator element will be available. Click on "Link Spotify account" and follow the instructions to
authorize Home Assistant to access your Spotify account. A Spotify media player
will then appear. If you are prompted to download a file after completing
authorization, discard the download. It is not needed.

1
source/_integrations/ssdp.markdown
View File

@ -4,6 +4,7 @@ description: "Discover integrations on the network using the SSDP protocol."
ha_category:
- Network
ha_release: 0.94
logo: home-assistant.png
---
The `ssdp` "Simple Service Discovery Protocol" integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the config panel.

2
source/_integrations/switch.template.markdown
View File

@ -151,7 +151,7 @@ switch:
switches:
skylight:
friendly_name: "Skylight"
value_template: "{{ is_state('sensor.skylight.state', 'on') }}"
value_template: "{{ is_state('sensor.skylight', 'on') }}"
turn_on:
service: switch.turn_on
data:

1
source/_integrations/switcher_kis.markdown
View File

@ -27,6 +27,7 @@ To retrieve your device's details, please follow the instructions [here](https:/
Please note, on the original script repository, users recently reported difficulties controlling the device after upgrading the firmware to the new 3.0 version.As this integration is based on that script, please do not upgrade to version 3.0 until this issue is resolved. You can follow the issue [here](https://github.com/NightRang3r/Switcher-V2-Python/issues/3).
</div>
```yaml
switcher_kis:
phone_id: 'REPLACE_WITH_PHONE_ID'

2
source/_integrations/tibber.markdown
View File

@ -21,7 +21,7 @@ There is currently support for the following device types within Home Assistant:
## Setup
Go to [developer.tibber.com/](https://developer.tibber.com/) to get your API token.
Go to [developer.tibber.com/settings/accesstoken](https://developer.tibber.com/settings/accesstoken) to get your API token.
## Configuration

5
source/_integrations/time_date.markdown
View File

@ -9,9 +9,8 @@ ha_release: pre 0.7
ha_qa_scale: internal
---
The time and date (`time_date`) sensor platform simple displays the time in various formats, the date, or both.
To enable this sensor in your installation, add the following to your `configuration.yaml` file:
The time and date (`time_date`) sensor platform adds one or more sensors to your Home Assistant state machine.
To have these sensors available in your installation, add the following to your `configuration.yaml` file (each option creates a separate sensor that contains appropriate data):
```yaml
# Example configuration.yaml entry

2
source/_integrations/tplink.markdown
View File

@ -36,7 +36,7 @@ The following devices are known to work with this component.
- HS107 (indoor 2-outlet)
- HS300 (powerstrip 6-outlet)
- KP400 (outdoot 2-outlet)
- KP400 (outdoor 2-outlet)
### Wall Switches

2
source/_integrations/unifiled.markdown
View File

@ -8,7 +8,7 @@ ha_release: 0.102
ha_iot_class: Local Polling
---
[UniFi LED](https://unifi-led.ui.com/) by [Ubiquiti Networks, inc.](https://www.ubnt.com/) is a system off controller managed led light panels and dimmers.
[UniFi LED](https://unifi-led.ui.com/) by [Ubiquiti Networks, inc.](https://www.ubnt.com/) is a system of controller managed led light panels and dimmers.
There is currently support for the following device type within Home Assistant:

1
source/_integrations/upc_connect.markdown
View File

@ -37,4 +37,5 @@ Also known to be working with the following devices:
- Irish Virgin Media Super Hub 3.0
- Unitymedia Connect Box (DE)
- Ziggo Connectbox (NL)
- Compal CH7465LG ED 3.0 - Connect box (UPC / Vodafone CZ)

4
source/_integrations/uptimerobot.markdown
View File

@ -8,7 +8,7 @@ ha_release: 0.72
ha_iot_class: Cloud Polling
---
The `uptimerobot` binary sensor platform allows you get the status for all of your monitors from your account on [Uptime Robot.]( https://uptimerobot.com).
The `uptimerobot` binary sensor platform allows you get the status for all of your monitors from your account on [Uptime Robot]( https://uptimerobot.com).
## Configuration
@ -28,6 +28,6 @@ api_key:
type: string
{% endconfiguration %}
All the data will be fetch from [Uptime Robot](https://uptimerobot.com).
All the data will be fetched from [Uptime Robot](https://uptimerobot.com).
To get your API key, go to [My Settings](https://uptimerobot.com/dashboard#mySettings) on the Uptime Robot website, at the bottom you will find your "Main API Key".

11
source/_integrations/venstar.markdown
View File

@ -10,17 +10,18 @@ ha_iot_class: Local Polling
The `venstar` climate platform allows you to control [Venstar](https://www.venstar.com/) thermostats from Home Assistant.
Venstar thermostats feature a local API that allows for automation without the need for a cloud service.
Venstar thermostats feature a local API that allows for automation without the need for their Skyport cloud service.
Currently supported and tested thermostats:
- Color Touch T7900
- ColorTouch T7900
- ColorTouch T7850 (No Humidity control)
Currently supported functionality:
- Setting heat/cool temperature when the thermostat is in the appropriate mode.
- Changing the operation mode of the thermostat (heat/cool/off/auto)
- Turning the fan on/off
- Reading and setting the humidity level and limits
- Reading and setting the humidity level and limits (T7900 only)
- Turning on away preset
- Turning on hold mode preset
@ -28,7 +29,9 @@ The following values are supported for the hold_mode state attribute:
- `off`: *Enables* the scheduling functionality.
- `temperature`: *Disables* the schedule and holds the set temperature indefinitely.
Note - Please ensure you update your thermostat to the latest firmware. Currently tested on firmware 5.10.
Note - Please ensure that you update your thermostat to the latest firmware. Initially tested on firmware 5.10 and currently VH6.79.
Local API mode needs to be enabled via the thermostat's *Menu > WiFi > Local API Options > Local API - ON*
To set it up, add the following information to your `configuration.yaml` file:

10
source/_integrations/watson_iot.markdown
View File

@ -16,7 +16,7 @@ To use this component, you first need to register a gateway device type and then
a gateway device in your IoT platform instance. For instructions on how to do
this check the [official documentation](https://cloud.ibm.com/docs/services/IoT?topic=iot-platform-getting-started#IoT_connectGateway)
which provides the details on doing this. After you register the gateway device
for your home-assistant you'll need 4 pieces of information:
for your Home Assistant instance you'll need four pieces of information:
- Organization ID
- Gateway device Type
@ -36,19 +36,19 @@ watson_iot:
{% configuration %}
organization:
description: The Organization ID for your Watson IoT Platform instance
description: The Organization ID for your Watson IoT Platform instance.
required: true
type: string
type:
description: The device type for the gateway device to use
description: The device type for the gateway device to use.
required: true
type: string
id:
description: The device id for the gateway device to use
description: The device id for the gateway device to use.
required: true
type: string
token:
description: The authentication token for the gateway device
description: The authentication token for the gateway device.
required: true
type: string
exclude:

2
source/_integrations/weblink.markdown
View File

@ -11,7 +11,9 @@ ha_qa_scale: internal
The `weblink` integration allows you to display links in the Home Assistant frontend.
<div class='note'>
The below documentation applies to the classic "States" user interface. Starting with Home Assistant 0.86, Lovelace is the new default interface. For information on configuring weblinks in Lovelace please follow [these instructions](/lovelace/entities/#weblink) instead.
</div>
## Configuration

2
source/_integrations/yi.markdown
View File

@ -21,7 +21,7 @@ To successfully implement this platform, the Home Assistant host should be capab
### Installing Alternative Firmware
In order to integrate the camera with Home Assistant, it is necessary to install a custom firmware on the device. Instructions for doing so can be found via the [yi-hack-v3 GitHub project](https://github.com/shadow-1/yi-hack-v3).
In order to integrate the camera with Home Assistant, it is necessary to install a custom firmware on the device. Instructions for doing so can be found via the [yi-hack-v3 GitHub project](https://github.com/shadow-1/yi-hack-v3) or if you have a 2019 version camera [yi-hack-6FUS_4.5.0 GitHub project](https://github.com/roleoroleo/yi-hack-6FUS_4.5.0).
Once installed, please ensure that you have enabled FTP and Telnet on your device.

1
source/_integrations/zeroconf.markdown
View File

@ -5,6 +5,7 @@ ha_category:
- Network
ha_qa_scale: internal
ha_release: 0.18
logo: home-assistant.png
---
The `zeroconf` integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the config panel. It will also make Home Assistant discoverable for other services in the network. Zeroconf is also sometimes known as Bonjour, Rendezvous, and Avahi.

18
source/_posts/2019-10-25-rip-hassbian.markdown
View File

@ -7,38 +7,42 @@ date_formatted: "October 26, 2019"
author: Fredrik Lindqvist
author_twitter: Landrash
comments: true
categories: community
categories: Announcements
---
It's time for what was once the simplest way to install Home Assistant to retire.
## R.I.P Hassbian
Some of you will probably wonder why Hassbian is being retired and I'll try to give a proper motivation.
Some of you will probably wonder why Hassbian is being retired and I'll try to give a proper motivation.
First of is the age-old factor of **time**. I as the lead developer of Hassbian haven't been able to give it the time and attention it requires, and there have been few others that have pushed the project further. The one exception being [@ludeeus] who's done most of the heavy lifting when the image was retooled to use a proper apt package and repository.
Second is that it's no longer the best option for most to use as an installation method. Hass.io has surpassed Hassbian in almost all ways I can imagine.
## Next Step for Hassbian
Since Hassbian has been around for quite a while, there are quite a few users that don't want Hassbian to go away. To make this as easy as possible for those users, here's the plan.
- The repositories [pi-gen] and [hassbian-scripts] hosting the Hassbian projects files will be moved to a new organization.
- A last release will be done by me mid Q4 2019. This image will be hosted under the [pi-gen] repository.
- The [pi-gen] repository will be reworked to work with a standard [raspbian] image with minor modifications for anyone wanting to create their own "Hassbian like" image. This has always been possible, but the current repository is a bit out of date with the current layout of the Raspbian image.
- The [hassbian-scripts] package will get a final release and will continue to be hosted on Gitlab. Some minor changes will be made to reflect the changes to the project.
- The repositories [pi-gen] and [hassbian-scripts] hosting the Hassbian projects files will be moved to a new organization.
- A last release will be done by me mid Q4 2019. This image will be hosted under the [pi-gen] repository.
- The [pi-gen] repository will be reworked to work with a standard [raspbian] image with minor modifications for anyone wanting to create their own "Hassbian like" image. This has always been possible, but the current repository is a bit out of date with the current layout of the Raspbian image.
- The [hassbian-scripts] package will get a final release and will continue to be hosted on Gitlab. Some minor changes will be made to reflect the changes to the project.
## Next step for Hassbian users
The Hassbian image has always aimed to be the same as a manual Raspbian Lite installation with some packages added.
There won't really be any big changes for all of the users of Hassbian and for documentation, please refer to the [Manual installation on a Raspberry PI] method.
## Alternatives
If you want to continue using something similar, have a look at the [manual installation on a Raspberry Pi] since it is the base Hassbian was created from.
For everyone else, I would wholeheartedly recommend Hass.io since it is what I personally use now (It's what I had hoped Hassbian could have been but better).
## Last but not least
Last but not least, thank you to all of those who contributed, in any way, to the Hassbian project and image.
[@ludeeus]: https://github.com/ludeeus
[pi-gen]: https://github.com/Hassbian/pi-gen
[hassbian-scripts]: https://github.com/Hassbian/hassbian-scripts
[Manual installation on a Raspberry Pi]: /docs/installation/raspberry-pi/
[manual installation on a raspberry pi]: /docs/installation/raspberry-pi/
[raspbian]: https://www.raspberrypi.org/downloads/raspbian/

55
source/_posts/2019-11-20-release-102.markdown
View File

@ -8,7 +8,7 @@ author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Release-Notes
og_image: /images/blog/2019-10-0.102/components.png
og_image: /images/blog/2019-11-0.102/components.png
---
Home Assistant 0.102 is here ! It's been quite the trip as we hosted our annual State of the Union last week, which took a lot of energy away from our release. This doesn't mean that we don't have anything to share, just that the notes might be a little less polished.
@ -21,13 +21,13 @@ Alright, so what's new? A lot.
At the State of the Union we announced that we have released the initial version of the official [Home Assistant Android app](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android). It's still a work in progress, but the basic version already works.
It's been developed by [@CedrickFlocon](https://github.com/CedrickFlocon) and the source is [available on GitHub](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android). We've already seen some other developers step in, so that's great! Keep it coming.
It's been developed by [@CedrickFlocon](https://github.com/CedrickFlocon) and the source is [available on GitHub](https://github.com/home-assistant/home-assistant-android/). We've already seen some other developers step in, so that's great! Keep it coming.
<!--more-->
## Private Voice Assistant
We teamed up with Stanford to tightly integrate their open, privacy-preserving virtual assistant Almond into Home Assistant. For more information, see the [separate blog post](/blog/2019/11/14/privacy-focused-voice-assistant/).
We teamed up with Stanford to tightly integrate their open, privacy-preserving virtual assistant Almond into Home Assistant. For more information, see the [separate blog post](/blog/2019/11/20/privacy-focused-voice-assistant/).
## Account Linking
@ -211,6 +211,55 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Updated frontend to 20191119.2 ([@bramkragten] - [#28896]) ([frontend docs]) (beta fix)
- Fix Almond onboarding url when using cloud ([@bramkragten] - [#28908]) ([almond docs]) (beta fix)
## Release 0.102.1 - November 21
- Fix missing Netatmo sensors ([@cgtobi] - [#28899]) ([netatmo docs])
- Updated frontend to 20191119.5 ([@bramkragten] - [#28925]) ([frontend docs])
- Fix Plex startup race condition #28934 [@jjlawren]
[#28899]: https://github.com/home-assistant/home-assistant/pull/28899
[#28925]: https://github.com/home-assistant/home-assistant/pull/28925
[@bramkragten]: https://github.com/bramkragten
[@cgtobi]: https://github.com/cgtobi
[frontend docs]: /integrations/frontend/
[netatmo docs]: /integrations/netatmo/
## Release 0.102.2 - November 24
- Fix Plex setup race condition v2 ([@jjlawren] - [#28943]) ([plex docs])
- Fix ikea lights on deconz ([@pvizeli] - [#28949]) ([deconz docs])
- Fix manual config ([@cgtobi] - [#28956]) ([netatmo docs])
- Fix temp not being reported properly ([@shred86] - [#28973]) ([abode docs])
- Updated frontend to 20191119.6 ([@bramkragten] - [#28996]) ([frontend docs])
- Alexa gracefully handle climate devices without presets ([@frenck] - [#29010]) ([alexa docs])
## Release 0.102.3 - November 29
- Fix smartthings cloud webhook ([@bramkragten] - [#29219]) ([smartthings docs])
[#29219]: https://github.com/home-assistant/home-assistant/pull/29219
[@bramkragten]: https://github.com/bramkragten
[smartthings docs]: /components/smartthings/
[#28943]: https://github.com/home-assistant/home-assistant/pull/28943
[#28949]: https://github.com/home-assistant/home-assistant/pull/28949
[#28956]: https://github.com/home-assistant/home-assistant/pull/28956
[#28973]: https://github.com/home-assistant/home-assistant/pull/28973
[#28996]: https://github.com/home-assistant/home-assistant/pull/28996
[#29010]: https://github.com/home-assistant/home-assistant/pull/29010
[@bramkragten]: https://github.com/bramkragten
[@cgtobi]: https://github.com/cgtobi
[@frenck]: https://github.com/frenck
[@jjlawren]: https://github.com/jjlawren
[@pvizeli]: https://github.com/pvizeli
[@shred86]: https://github.com/shred86
[abode docs]: /integrations/abode/
[alexa docs]: /integrations/alexa/
[deconz docs]: /integrations/deconz/
[frontend docs]: /integrations/frontend/
[netatmo docs]: /integrations/netatmo/
[plex docs]: /integrations/plex/
## All changes
- Cover all possible values for venstar operation_mode ([@iamtpage] - [#27949]) ([venstar docs])

136
source/_posts/2019-11-22-state-of-the-union.markdown Normal file
View File

@ -0,0 +1,136 @@
---
layout: post
title: "State of the Union 2019: Recap"
description: "ING hosted 150 Home Assistant community members to hear about the what and why of Home Assistant."
date: 2019-11-22 0:41:02
date_formatted: "November 22, 2019"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Announcements
redirect_from:
- /state-of-the-union/
og_image: /images/blog/2019-11-state-of-the-union/social.jpeg
---
On November 13, 2019, 150 Home Assistant community members gathered at [ING](https://www.ing.com) in Amsterdam for the Home Assistant State of the Union 2019.
That evening, Paulus Schoutsen (founder Home Assistant) and Pascal Vizeli (founder hass.io) presented what Home Assistant is up to, why we're doing what we're doing and what we got planned.
Video of the event is embedded below (it starts at 7:12):
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/tc17q1Zn0Xs?start=437" frameborder="0" allowfullscreen></iframe>
</div>
## Thanks
The State of the Union could not have been possible without the time and energy of the following people:
- [ING](https://www.ing.com) for hosting us once again ❤️
- Erik-Jan Riemers for organizing – Rockstar ⭐️
- Frenck for managing the livestream
- Arjan Vroege for assisting the team
## Announcements
### We're #10 open-source project in the world
GitHub posted their [State of the Octoverse](https://octoverse.github.com/#top-and-trending-projects), listing Home Assistant as the tenth biggest project in the last year based on the number of contributors.
This is especially impressive because all the other things on the list are related to, or maintained by billion dollar companies.
<p class='img'><img src='/images/blog/2019-11-state-of-the-union/octoverse.png' alt='Top 10 biggest open-source projects.'>Top 10 biggest open-source projects.</p>
### Home Assistant around the world ❤️
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/AsPqrAxSMbU" frameborder="0" allowfullscreen></iframe>
</div>
### Improved Scenes
In Home Assistant 0.102 we're launching a new scene editor. We're also adding two scene services `scene.apply` and `scene.create`. First one allows you to apply a scene without prior defining it, the second one allows you to create a scene on the fly.
### iOS app
[@robbiet480](https://github.com/robbiet480) has submitted the new and updated iOS app to the app store and it will be available soon.
[Source code](https://github.com/home-assistant/home-assistant-ios)
### Android app
We have released a new Android app! [Download it here.](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android) It's being developed by [@CedrickFlocon](https://github.com/CedrickFlocon) and we're already seeing a ton of other contributors jump in. Awesome!
[Source code](https://github.com/home-assistant/home-assistant-android/)
### OAuth2 Account Linking
We've made it easier in Home Assistant for integrations to use OAuth2 account linking. This is available starting Home Assistant 0.102. Somfy is the first partner to use it.
It works using a small cloud service provided by Home Assistant Cloud. It is available to all users for free, no cloud account necessary.
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/y0SECWUVR-M" frameborder="0" allowfullscreen></iframe>
</div>
Check the [updated developer documentation](https://developers.home-assistant.io/docs/en/config_entries_config_flow_handler.html#configuration-via-oauth2) if you want to add OAuth2 account linking to an integration.
### Teamed up with Almond: privacy-preserving virtual assistant
We've teamed up with the Stanford Open Virtual Assistant Lab to bring [Almond](https://almond.stanford.edu/) to Home Assistant users. Almond has been upgraded with Home Assistant integration and users can now talk to Almond via the Lovelace UI.
You can run this standalone, as a hass.io add-on or via a version hosted in the cloud by Stanford.
<p class='img'><img src='/images/blog/2019-11-state-of-the-union/almond.png' alt='Short description of what Almond is.'>Short description of what Almond is.</p>
For more information, check [the announcement blog](/blog/2019/11/20/privacy-focused-voice-assistant/).
### Ada, voice assistant powered by Home Assistant
We have introduced a new project called Ada. Ada is a voice assistant that outsources all processing to the speech-to-text (new!), conversation and text-to-speech integrations in Home Assistant. You can pick your own providers for each integration.
You can run this standalone or as a hass.io add-on.
For more information, check [the announcement blog](/blog/2019/11/20/privacy-focused-voice-assistant/).
[Source code](https://github.com/home-assistant/ada).
<p class='img'><img src='/images/blog/2019-11-state-of-the-union/ada.png' alt='Architectural overview of Ada.'>Architectural overview of Ada.</p>
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/8VFZiHcjp78" frameborder="0" allowfullscreen></iframe>
</div>
### Voice for Home Assistant Cloud
Nabu Casa has introduced a new beta service providing speech-to-text and text-to-speech services to Home Assistant Cloud subscribers powered by Azure Cognitive Services. This will make it easy to get started with Ada or use it to send spoken notifications to speakers in your house.
### Z-Wave
We've been working with the Open Z-Wave developers on a new solution that will allow us to migrate to the new Open Z-Wave 1.6 relase and make it easier to stay up to date in the future.
We're expecting to launch an MVP soon. This effort is driven by [@cgarwood](https://github.com/cgarwood).
[Source code](https://github.com/cgarwood/python-openzwave-mqtt)
### Frenck is joining Nabu Casa
Frenck will be joining Nabu Casa as the fourth employee working full-time on Home Assistant.
_"If I could describe my dream job, it would be being a full-time open source developer; Helping the world to become a better place by dedicating my time & knowledge to create & innovate open source software solutions. Allowing everybody on this earth the privilege to enjoy those things for free."_ &nbsp;&nbsp;&nbsp;–&nbsp;Franck&nbsp;Nijhof&nbsp;(Frenck)&nbsp;on&nbsp;[frenck.dev](https://frenck.dev/donate/)
### Create automations using your voice
We have been able to leverage Almond's neural network to **allow users to generate automations using natural language**. This means that you can now create an automation by telling Home Assitant to "turn on the lights when I get home" and we'll convert it to the appropriate automation in Home Assistant.
[Source code](https://github.com/NabuCasa/thingtalk-hass-generator/).
<p class='img'>
<img src='/images/blog/2019-11-0.102/thingtalk-automation.png' alt='Screenshot of the create automation dialog.'></a>
Screenshot of the create automation dialog.
</p>
### Share the love ❤️
Home Assistant is the community and the community is Home Asssitant. Help us spread the Home Assitant love, help others and share your knowledge on YouTube, blogs and other media.

48
source/_posts/2019-12-01-home-assistant-for-everyone.markdown Normal file
View File

@ -0,0 +1,48 @@
---
title: "Home Assistant for everyone"
description: "Make it easier. We're making Home Assistant easier to use, configure and contribute to."
date: 2019-12-01 00:01:00
date_formatted: "December 1, 2019"
author: Paulus Schoutsen
author_twitter: balloob
categories: Community
og_image: /images/blog/2019-12-home-assistant-for-everyone/social.png
---
With Home Assistant, we want to help people live their life, while helping out in the background. I wrote about this in 2016 when I detailed my view on the [perfect home automation](https://www.home-assistant.io/blog/2016/01/19/perfect-home-automation/). We've been working towards this ever since.
In 2019 we focused on "Make It Easier" ([see State of the Union for details](https://youtu.be/tc17q1Zn0Xs?t=1271)). We made Home Assistant easier to use, configure and to contribute to. Every time we make it easier, we become accessible to more people. There is still a ton we can make easier, and that's great because 2020 is around the corner and we need things to do :-)
During Thanksgiving, Home Assistant made it to #1 on [Hacker News](https://news.ycombinator.com/item?id=21665125), a social news website focusing on computer science and entrepreneurship. The comments had lots of users chiming in with their positive experiences. One comment stood out to me and I wanted to share it:
<blockquote style='font-size:1em'>
Just wanted to say that my life as a quadriplegic would be 13.4 million percent more crap without Home Assistant. Being quadriplegic and having something as open as Home Assistant is absolutely amazing, I have automated absolutely everything in the house and home assistant has not choked once.
<br><br>
Couple that with one of the friendliest communities for newbies I have come across in a long time and you have something really awesome.
<br><br>
I've been using it for a couple of years, I have tried all the other open source alternatives but nothing really comes close for me. I'm actually fiddling with my installation right now as it were.
<br><br>
I cannot plug my phone in to charge it up myself obviously, so I am writing a little automation that will check who is in the house and announce through the speakers my phone needs charging up or send them a text message if I have their phone number when my mobile phone charge gets below 20%.
<br><br>
Totally cool beanz and I am totally serious about how much easier this makes my life as a quadriplegic.
<br><br>
– <a href="https://news.ycombinator.com/item?id=21666909">escapologybb on Hacker News</a>
</blockquote>
This is just great. I love how this user can live a more comfortable life. It's really motivating.
I also really like the first reply to the above comment. It highlights how we tend to judge things from our perspective and that our perspective might not paint the whole picture.
<blockquote style='font-size:1em'>
Thanks for your comment. I came to this discussion with my blinkers on, so to speak, pre -judging how I need less automation in my world, and you give concrete evidence how someone's "meh" can be balanced by untold advantages (13.4 million, in fact) of such a system.
<br><br>
Thanks for making me eat humble pie and broadening my views. Sometimes more tech is helpful indeed.
<br><br>
Ps: The way you're applying it is creative and awesome too!
<br><br>
– <a href="https://news.ycombinator.com/item?id=21667056">cmroanirgo on Hacker News</a>
</blockquote>
As Home Assistant grows and evolves, let's make sure we don't judge the additions and changes based on just our own perspective and needs. Think about how it can help other (potential) Home Assistant users. It's our goal that a privacy-focused home automation platform is within everyone's reach, regardless of background, location or income.
Paulus

17
source/_redirects
View File

@ -2054,3 +2054,20 @@
# Breaking changes
/integrations/switch.pca /integrations/elv
# App documentation
/ios/whats-new https://companion.home-assistant.io/getting_started/index.html
/docs/ecosystem/ios/ https://companion.home-assistant.io/
/docs/ecosystem/ios/devices_file https://companion.home-assistant.io/
/docs/ecosystem/ios/integration https://companion.home-assistant.io/integrations/
/docs/ecosystem/ios/location https://companion.home-assistant.io/core/location
/docs/ecosystem/ios/notifications https://companion.home-assistant.io/notifications/basic
/docs/ecosystem/ios/notifications/actions https://companion.home-assistant.io/notifications/actionable
/docs/ecosystem/ios/notifications/architecture https://companion.home-assistant.io/notifications/details
/docs/ecosystem/ios/notifications/attachments https://companion.home-assistant.io/notifications/attachments
/docs/ecosystem/ios/notifications/basic https://companion.home-assistant.io/notifications/basic
/docs/ecosystem/ios/notifications/content_extensions https://companion.home-assistant.io/notifications/dynamic-content
/docs/ecosystem/ios/notifications/privacy_security_rate_limits https://companion.home-assistant.io/notifications/details
/docs/ecosystem/ios/notifications/requesting_location_updates https://companion.home-assistant.io/notifications/location
/docs/ecosystem/ios/notifications/sounds https://companion.home-assistant.io/notifications/sounds
/ecosystem/ios/notifications https://companion.home-assistant.io/en/getting_started/migration#5---known-issues

2
source/getting-started/index.markdown
View File

@ -35,7 +35,7 @@ Follow this guide if you want to get started with Home Assistant easily or if yo
We will need a few things to get started with installing Home Assistant. The Raspberry Pi 3 Model B+ is a good, affordable starting point for your home automation journey. Links below lead to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country.
- [Raspberry Pi 3 Model B+](https://amzn.to/2IAyNl0) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 2.5A)
- [Raspberry Pi 4 Model B (2GB)](https://amzn.to/2XULT2z) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 2.5A)
- [Micro SD Card](https://amzn.to/2X0Z2di). Ideally get one that is [Application Class 2](https://www.sdcard.org/developers/overview/application/index.html) as they handle small I/O much more consistently than cards not optimized to host applications. A 32 GB or bigger card is recommended.
- SD Card reader. This is already part of most laptops, but you can purchase a [standalone USB adapter](https://amzn.to/2WWxntY) if you don't have one. The brand doesn't matter, just pick the cheapest.
- Ethernet cable. Home Assistant can work with Wi-Fi, but an Ethernet connection would be more reliable.

BIN
source/images/blog/2019-11-state-of-the-union/ada.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
source/images/blog/2019-11-state-of-the-union/almond.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

BIN
source/images/blog/2019-11-state-of-the-union/octoverse.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 64 KiB

BIN
source/images/blog/2019-11-state-of-the-union/social.jpeg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 MiB

BIN
source/images/blog/2019-12-home-assistant-for-everyone/social.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 304 KiB

BIN
source/images/frontpage/sotu2019-paulus.jpeg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 53 KiB

BIN
source/images/supported_brands/global-cache.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 30 KiB

BIN
source/images/supported_brands/orange-pi.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 95 KiB

21
source/index.html
View File

@ -14,13 +14,12 @@ description: Open source home automation that puts local control and privacy fir
<div class="current-version material-card text">
<h1>
Current Version: {{ site.current_major_version }}.{{
site.current_minor_version
}}.{{ site.current_patch_version }}
site.current_minor_version }}.{{ site.current_patch_version }}
</h1>
Released:
<span class="release-date">{{
site.date_released | date: "%B %d, %Y"
}}</span>
<span class="release-date"
>{{ site.date_released | date: "%B %d, %Y" }}</span
>
<div class="links">
<a href="/latest-release-notes/">Release notes</a>
@ -88,9 +87,17 @@ description: Open source home automation that puts local control and privacy fir
<a
class="material-card picture-promo"
href="/state-of-the-union/"
style="background-image: url(/images/frontpage/sotu2019.png);background-size: contain;background-repeat: no-repeat;background-color: #41bdf5;background-position: top left;"
href="/blog/2019/11/22/state-of-the-union/"
style="background-image: url(/images/frontpage/sotu2019-paulus.jpeg);background-size: cover;background-color: #41bdf5;"
>
<div class="caption">
<div class="title">
State of the Union 2019
</div>
<div class="subtitle">
Learn why we do what we do and what is next.
</div>
</div>
</a>
<a

46
source/state-of-the-union/index.markdown
View File

@ -1,46 +0,0 @@
---
show_title: true
sidebar: false
title: State of the Union
hide_github_edit: true
description: Join us on November 13, 2019 for the Home Assistant State of the Union.
og_image: /images/frontpage/sotu2019.png
---
Home Assistant is proud to present the State of the Union 2019. We're going to discuss all things Home Assistant: the platform, our goals, our achievements and a sneak peek at what we have planned for the home automation ecosystem.
It will take place on November 13, 2019 in Amsterdam. Tickets have already been sold out (in 24h!) but we're having a live stream (see below).
This years presenters are:
- Paulus Schoutsen (founder Home Assistant)
- Pascal Vizeli (founder Hass.io)
[See last year's edition.](/blog/2018/11/16/state-of-the-union/)
## Livestream
This year, the Home Assistant State of the Union will be live streamed to YouTube!
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube.com/embed/tc17q1Zn0Xs" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
Direct YouTube URL: <https://www.youtube.com/watch?v=tc17q1Zn0Xs>
🔔 Don't forget to go to the above URL to hit the "Set reminder" bell!
Doing that, ensures you'll get a notification from YouTube, when the stream starts.
The presentation is going to start on 13 November at:
- 9.30 AM in PST
- 12.30 PM in EST
- 18:30 in CET
- [Other time zones](https://www.timeanddate.com/worldclock/converter.html?iso=20191113T173000&p1=137&p2=179&p3=16)
## Local Meetups
If you would like to meet other Home Assistant users and watch the livestream together, check out the following local meetups:
- [Berlin](https://www.meetup.com/Berlin-Home-Assistant/events/265634883/)
- [Rhein-Main Area](https://www.meetup.com/de-DE/Home-Assistant-Meetup-Rhein-Main-Neckar/events/265920456/)