mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-27 03:07:14 +00:00
Merge branch 'next' into rc
This commit is contained in:
Franck Nijhof
commit
246aa3dd9b
9
.vscode/cSpell.json
vendored
9
.vscode/cSpell.json
vendored
@ -4,6 +4,7 @@
|
||||
"version": "0.2",
|
||||
"language": "en",
|
||||
"words": [
|
||||
"Accu",
|
||||
"aeotec",
|
||||
"Alexa",
|
||||
"arest",
|
||||
@ -16,6 +17,7 @@
|
||||
"BTLE",
|
||||
"CEST",
|
||||
"Chromecast",
|
||||
"codeowners",
|
||||
"deCONZ",
|
||||
"Denon",
|
||||
"DSMR",
|
||||
@ -44,9 +46,11 @@
|
||||
"HomeKit",
|
||||
"Homematic",
|
||||
"HVAC",
|
||||
"Hygro",
|
||||
"IBAN",
|
||||
"icloud",
|
||||
"IFTTT",
|
||||
"Jeelink",
|
||||
"kardon",
|
||||
"laundrify",
|
||||
"Lutron",
|
||||
@ -54,6 +58,7 @@
|
||||
"Meteobridge",
|
||||
"Modbus",
|
||||
"Mosquitto",
|
||||
"Multiday",
|
||||
"Nabu Casa",
|
||||
"nginx",
|
||||
"Nijhof",
|
||||
@ -65,6 +70,7 @@
|
||||
"OwnTracks",
|
||||
"Paulus",
|
||||
"PECO",
|
||||
"POOLV",
|
||||
"Powerwall",
|
||||
"Pushbullet",
|
||||
"Schoutsen",
|
||||
@ -80,6 +86,9 @@
|
||||
"waqi",
|
||||
"WLED",
|
||||
"worldclock",
|
||||
"WRTHV",
|
||||
"WSDTH",
|
||||
"WTHV",
|
||||
"Xiaomi",
|
||||
"Zigbee"
|
||||
],
|
||||
|
||||
@ -108,7 +108,7 @@ GEM
|
||||
tilt (2.0.11)
|
||||
tzinfo (2.0.5)
|
||||
concurrent-ruby (~> 1.0)
|
||||
tzinfo-data (1.2022.1)
|
||||
tzinfo-data (1.2022.3)
|
||||
tzinfo (>= 1.0.0)
|
||||
unicode-display_width (1.8.0)
|
||||
|
||||
|
||||
@ -107,8 +107,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 2022
|
||||
current_minor_version: 8
|
||||
current_patch_version: 0
|
||||
date_released: 2022-08-03
|
||||
current_patch_version: 6
|
||||
date_released: 2022-08-18
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
14
package-lock.json
generated
14
package-lock.json
generated
@ -17,7 +17,7 @@
|
||||
"textlint": "^12.2.1",
|
||||
"textlint-filter-rule-comments": "^1.2.2",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^3.0.2"
|
||||
"textlint-rule-terminology": "^3.0.3"
|
||||
}
|
||||
},
|
||||
"node_modules/@azu/format-text": {
|
||||
@ -5384,9 +5384,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/textlint-rule-terminology": {
|
||||
"version": "3.0.2",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.2.tgz",
|
||||
"integrity": "sha512-PgHg7wkf0gWbihSL+GZF+rG8GJX01azQXIUtWZ4UniDs5GwcwXpb98Dts8jrFQ+c9UeLb1u2HtBgjTmlWkWlQw==",
|
||||
"version": "3.0.3",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.3.tgz",
|
||||
"integrity": "sha512-c1AzZ7ztXZfLySI8j7CnUGj8leNsfTCs+OPwJQV0ZWpKIZ7FsuRULCof1wLxsOZM+9MpVkmJWGfi6/qR6kRGIg==",
|
||||
"dev": true,
|
||||
"dependencies": {
|
||||
"lodash": "^4.17.15",
|
||||
@ -10077,9 +10077,9 @@
|
||||
}
|
||||
},
|
||||
"textlint-rule-terminology": {
|
||||
"version": "3.0.2",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.2.tgz",
|
||||
"integrity": "sha512-PgHg7wkf0gWbihSL+GZF+rG8GJX01azQXIUtWZ4UniDs5GwcwXpb98Dts8jrFQ+c9UeLb1u2HtBgjTmlWkWlQw==",
|
||||
"version": "3.0.3",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.3.tgz",
|
||||
"integrity": "sha512-c1AzZ7ztXZfLySI8j7CnUGj8leNsfTCs+OPwJQV0ZWpKIZ7FsuRULCof1wLxsOZM+9MpVkmJWGfi6/qR6kRGIg==",
|
||||
"dev": true,
|
||||
"requires": {
|
||||
"lodash": "^4.17.15",
|
||||
|
||||
@ -12,7 +12,7 @@
|
||||
"textlint": "^12.2.1",
|
||||
"textlint-filter-rule-comments": "^1.2.2",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^3.0.2"
|
||||
"textlint-rule-terminology": "^3.0.3"
|
||||
},
|
||||
"resolutions": {
|
||||
"minimist": ">=1.2.5"
|
||||
|
||||
@ -60,6 +60,8 @@
|
||||
description: "[Scripts](/docs/scripts/) are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on."
|
||||
- topic: Sensor
|
||||
description: "[Sensors](/integrations/sensor) return information about a thing, for instance the level of water in a tank."
|
||||
- topic: Selectors
|
||||
description: "[Selectors](/docs/blueprint/selectors/) are components for the user interface. Some selectors can, for example, show a toggle button to turn something on or off, while another select can filter a list of devices to show only devices that have motion-sensing capabilities."
|
||||
- topic: Service
|
||||
description: "[Services](/docs/scripts/service-calls/) are called to perform actions."
|
||||
- topic: Switch
|
||||
@ -70,5 +72,7 @@
|
||||
description: "A [trigger](/docs/automation/trigger/) is a set of values or conditions of a platform that are defined to cause an automation to run."
|
||||
- topic: TTS
|
||||
description: "TTS ([text to speech](/integrations/tts)) allows Home Assistant to talk to you."
|
||||
- topic: Variables
|
||||
description: "[Variables](/docs/scripts/#variables) are used to store values in memory that can be processed e.g. in a script."
|
||||
- topic: Zone
|
||||
description: "[Zones](/integrations/zone/) are areas that can be used for presence detection."
|
||||
|
||||
@ -33,6 +33,7 @@ The following selectors are currently available:
|
||||
- [Object selector](#object-selector)
|
||||
- [RGB color selector](#rgb-color-selector)
|
||||
- [Select selector](#select-selector)
|
||||
- [State selector](#state-selector)
|
||||
- [Target selector](#target-selector)
|
||||
- [Template selector](#template-selector)
|
||||
- [Text selector](#text-selector)
|
||||
@ -820,6 +821,29 @@ When `multiple` is `true`, the output of this selector is the list of selected
|
||||
option values. In this case, if `Green` was selected, in the first example it
|
||||
would return ["Green"] and in the last example it returns ["g"].
|
||||
|
||||
## State selector
|
||||
|
||||
The state selector shows a list of states for a provided entity of which
|
||||
one can be selected.
|
||||
|
||||
|
||||
|
||||
{% configuration state %}
|
||||
entity_id:
|
||||
description: The entity ID of which an state can be selected from.
|
||||
type: string
|
||||
required: true
|
||||
attribute:
|
||||
description: The attribute of which an attribute state can be selected from.
|
||||
type: string
|
||||
required: false
|
||||
{% endconfiguration %}
|
||||
|
||||
The output of this selector is the select state (not the translated or
|
||||
prettified name shown in the frontend).
|
||||
|
||||
For example: `heat_cool`.
|
||||
|
||||
## Target selector
|
||||
|
||||
The target selector is a rather special selector, allowing the user to select
|
||||
|
||||
@ -13,12 +13,12 @@ The easiest option to edit `configuration.yaml` is to use the {% my supervisor_a
|
||||
|
||||
If you prefer to use a file editor on your computer, use the {% my supervisor_addon title="Samba add-on" addon="core_samba" %} to access the files as a network share.
|
||||
|
||||
The path to your configuration directory can be found in the Home Assistant frontend by going to {% my system_health title="Settings > System > System Health" %}
|
||||
The path to your configuration directory can be found in the Home Assistant frontend by going to {% my system_health title="Settings > System > Repairs > System information from the top right menu" %}
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/system_health_config_dir.png' alt='Screenshot showing the top of the system health panel'>
|
||||
Right under the version you are running, you will find what path Home Assistant has loaded the configuration from.
|
||||
</div>
|
||||
|
||||
|
||||
Right under the version you are running, you will find what path Home Assistant has loaded the configuration from.
|
||||
|
||||
|
||||
_If you use Home Assistant Container, you can find `configuration.yaml` in the config folder that you mounted in your container._
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ longitude:
|
||||
required: false
|
||||
type: float
|
||||
elevation:
|
||||
description: Altitude above sea level in meters. Impacts weather/sunrise data.
|
||||
description: Altitude above sea level in meters. Impacts sunrise data.
|
||||
required: false
|
||||
type: integer
|
||||
unit_system:
|
||||
|
||||
@ -24,7 +24,7 @@ There is [an issue](https://github.com/rabbitmq/rabbitmq-server/issues/154) with
|
||||
|
||||
## Connect to a public broker
|
||||
|
||||
The Mosquitto project runs a [public broker](https://test.mosquitto.org). This is the easiest to set up, but there is no privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices or controlling your home. To use the public mosquitto broker, confiure the MQTT integration to connect to broker `test.mosquitto.org` on port 1183 or 8883.
|
||||
The Mosquitto project runs a [public broker](https://test.mosquitto.org). This is the easiest to set up, but there is no privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices or controlling your home. To use the public mosquitto broker, configure the MQTT integration to connect to broker `test.mosquitto.org` on port 1183 or 8883.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -440,10 +440,10 @@ The entity id is automatically generated from the entity's name. All MQTT entity
|
||||
```json
|
||||
{
|
||||
"name":"My Super Device",
|
||||
"object_id":"device1",
|
||||
"object_id":"my_super_device",
|
||||
"state_topic": "homeassistant/sensor/device1/state"
|
||||
}
|
||||
```
|
||||
|
||||
In the example above, the entity_id will be `sensor.device1` instead of `sensor.my_super_device`.
|
||||
In the example above, the entity_id will be `sensor.my_super_device` instead of `sensor.device1`.
|
||||
|
||||
|
||||
@ -0,0 +1,6 @@
|
||||
---
|
||||
title: "Configuration.yaml by omerome83"
|
||||
description: ""
|
||||
ha_category: Example configuration.yaml
|
||||
ha_external_link: https://github.com/omerome83/homeassistant
|
||||
---
|
||||
@ -6,4 +6,7 @@ ha_category: Common
|
||||
|
||||
New versions of Home Assistant are released on the first Wednesday of every month. The exact dates can be seen in the upcoming events calendar on the [Home Assistant Developers](https://developers.home-assistant.io/) website.
|
||||
|
||||
A list of all releases in our history and their announcement blog posts
|
||||
can be found [here](/blog/categories/core/).
|
||||
|
||||
The last week of our release schedule is primarily focused on beta testing. Users who participate in the beta can view the changelog under [beta release notes](https://rc.home-assistant.io/latest-release-notes/) and get help in the `#beta` channel of [Home Assistant's Discord server](/join-chat). Testers are also encouraged to [report issues on GitHub](/help/#bugs-feature-requests-and-alike).
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
## Backups
|
||||
|
||||
Backup of your Home Assistant and add-on data and configuration. They are stored in a compressed archive file (.tar). Backups are made from the Supervisor Backups panel. There is also a service available that allows you to trigger the creation of a backup from an automation. Backups are stored in the /backup directory.
|
||||
Backup of your Home Assistant and add-on data and configuration. They are stored in a compressed archive file (.tar). Backups are made from the Supervisor Backups panel. There is also a service available that allows you to trigger the creation of a backup from an automation. Backups are stored in the `/backup` directory.
|
||||
|
||||
A full backup includes the following directories:
|
||||
|
||||
@ -58,3 +58,4 @@ You often need a backup in case your system has crashed. If you only store them
|
||||
- [Nextcloud Backup](https://github.com/Sebclem/hassio-nextcloud-backup)
|
||||
- [Samba backup](https://github.com/thomasmauerer/hassio-addons/tree/master/samba-backup)
|
||||
- [Remote Backup (scp/rsync/rclone)](https://github.com/ikifar2012/remote-backup-addon)
|
||||
- [Syncthing](https://github.com/Poeschl/Hassio-Addons/tree/main/syncthing)
|
||||
|
||||
@ -165,7 +165,7 @@ This can be accomplished either by using a live operating system (e.g. Ubuntu) a
|
||||
|
||||
```text
|
||||
efibootmgr --create --disk /dev/<drivename> --part 1 --label "HAOS" \
|
||||
--loader "\EFI\BOOT\bootx64.efi"
|
||||
--loader '\EFI\BOOT\bootx64.efi'
|
||||
```
|
||||
|
||||
Or else, the BIOS might provide you with a tool to add boot options, there you can specify the path to the EFI file:
|
||||
|
||||
@ -25,7 +25,7 @@ The Advantage Air integration allows you to control [Advantage Air](https://www.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
The wall-mounted Android table running the [MyPlace](https://play.google.com/store/apps/details?id=com.air.advantage.myair5), [e-zone](https://play.google.com/store/apps/details?id=com.air.advantage.ezone), or [zone10e](https://play.google.com/store/apps/details?id=com.air.advantage.zone10) must have a static IP, which you will enter on the integrations page in Home Assistant.
|
||||
The wall-mounted Android tablet running the [MyPlace](https://play.google.com/store/apps/details?id=com.air.advantage.myair5), [e-zone](https://play.google.com/store/apps/details?id=com.air.advantage.ezone), or [zone10e](https://play.google.com/store/apps/details?id=com.air.advantage.zone10) must have a static IP, which you will enter on the integrations page in Home Assistant.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -70,11 +70,3 @@ Set the On/Off Timer using the relevant sensor entity.
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | yes | `sensor.[name]_time_to_on` or `sensor.[name]_time_to_off`
|
||||
| `minutes` | no | Number of minutes between `0` and `720`.
|
||||
|
||||
### Service `advantage_air.set_myzone`
|
||||
|
||||
Change the MyZone setting to the provided zone climate entity.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | yes | `climate.[zone name]`
|
||||
|
||||
@ -9,6 +9,7 @@ ha_category:
|
||||
- Switch
|
||||
ha_release: '0.40'
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_domain: android_ip_webcam
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
@ -16,9 +17,11 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@engrbm87'
|
||||
---
|
||||
|
||||
The `android_ip_webcam` integration connects with Android IP Webcam to turn any Android phone or tablet into a network camera with multiple viewing options.
|
||||
The Android IP Webcam integration connects with Android IP Webcam to turn any Android phone or tablet into a network camera with multiple viewing options.
|
||||
|
||||
The integration is setup as an MJPEG camera with all settings as switches inside Home Assistant. You can also integrate the sensors exposed by the app. If you have multiple phones, you can use all options inside a list.
|
||||
|
||||
@ -33,177 +36,10 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
Download [Android IP Webcam app](https://play.google.com/store/apps/details?id=com.pas.webcam) and launch the app. When you press 'Start Server', it will start streaming video from your phone and the IP address of the device will be shown on screen.
|
||||
|
||||
## Configuration
|
||||
|
||||
To set up the component, add the following information to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
android_ip_webcam:
|
||||
- host: 192.168.1.10
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP address of the phone on the network.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The port the IP Webcam listens on.
|
||||
required: false
|
||||
default: 8080
|
||||
type: integer
|
||||
name:
|
||||
description: Override the name of the phone.
|
||||
required: false
|
||||
default: IP Webcam
|
||||
type: string
|
||||
username:
|
||||
description: The username to access the phone. If username is specified then password must be also.
|
||||
required: inclusive
|
||||
type: string
|
||||
password:
|
||||
description: The password to access the phone. If password is specified then username must be also.
|
||||
required: inclusive
|
||||
type: string
|
||||
scan_interval:
|
||||
description: The update interval to use (in seconds).
|
||||
required: false
|
||||
default: 10
|
||||
type: integer
|
||||
sensors:
|
||||
description: List of sensor entities to be created by this component (if supported by the phone and app).
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
audio_connections:
|
||||
description: The audio connections
|
||||
battery_level:
|
||||
description: The battery level
|
||||
battery_temp:
|
||||
description: The battery temperature
|
||||
battery_voltage:
|
||||
description: The battery voltage
|
||||
light:
|
||||
description: The light level
|
||||
motion:
|
||||
description: Analog (not binary) amount of motion detected
|
||||
pressure:
|
||||
description: The current pressure
|
||||
proximity:
|
||||
description: The proximity
|
||||
sound:
|
||||
description: The sound level
|
||||
video_connections:
|
||||
description: The video connections
|
||||
switches:
|
||||
description: List of switch entities to be created by this component.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
exposure_lock:
|
||||
description: Control the exposure lock
|
||||
ffc:
|
||||
description: Control the front-facing camera
|
||||
focus:
|
||||
description: Control the focus
|
||||
gps_active:
|
||||
description: Control the GPS
|
||||
motion_detect:
|
||||
description: Control the motion detector
|
||||
night_vision:
|
||||
description: Control the night vision
|
||||
overlay:
|
||||
description: Control the overlay
|
||||
torch:
|
||||
description: Control the torch
|
||||
whitebalance_lock:
|
||||
description: Control the white balance lock
|
||||
video_recording:
|
||||
description: Control the video recording
|
||||
motion_sensor:
|
||||
description: Create a binary_sensor.<name>_motion_active entity. Note that `auto_discovery` may also create this sensor.
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
{% endconfiguration %}
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
<div class='note'>
|
||||
|
||||
You need to enable logging in the Android app (`Data logging` > `Enable data logging`) if you wish to see the sensor states in Home Assistant. The sensor states stay as `unknown`, until this is enabled.
|
||||
|
||||
</div>
|
||||
|
||||
## Full example
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
android_ip_webcam:
|
||||
- host: 192.168.1.202
|
||||
port: 8000
|
||||
sensors:
|
||||
- audio_connections
|
||||
- battery_level
|
||||
- battery_temp
|
||||
- battery_voltage
|
||||
- light
|
||||
- motion
|
||||
- pressure
|
||||
- proximity
|
||||
- sound
|
||||
- video_connections
|
||||
switches:
|
||||
- exposure_lock
|
||||
- ffc
|
||||
- focus
|
||||
- gps_active
|
||||
- motion_detect
|
||||
- night_vision
|
||||
- overlay
|
||||
- torch
|
||||
- whitebalance_lock
|
||||
- video_recording
|
||||
- host: 192.168.1.203
|
||||
port: 8000
|
||||
sensors:
|
||||
- light
|
||||
switches:
|
||||
- torch
|
||||
```
|
||||
|
||||
## Alternate Configuration Method
|
||||
|
||||
The configuration described above will cause the `android_ip_webcam` binary sensor platform to automatically create and configure the devices. Alternatively you can omit the `android_ip_webcam` component from your `configuration.yaml` file and add individual devices instead.
|
||||
|
||||
### Binary Sensor
|
||||
|
||||
You can setup the binary motion sensor with the following in your `configuration.yaml` file:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: rest
|
||||
name: Kitchen Motion
|
||||
device_class: motion
|
||||
resource: http://IP_ADDRESS:PORT/sensors.json?sense=motion_active
|
||||
value_template: "{{ value_json.motion_active.data[0][1][0] | round(0) }}"
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
### Camera
|
||||
|
||||
To enable only the camera in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
camera:
|
||||
- platform: mjpeg
|
||||
mjpeg_url: http://IP_ADDRESS:PORT/video
|
||||
```
|
||||
|
||||
### Other Sensors
|
||||
|
||||
You can setup your own sensors by examining the JSON file from the webcam server: `http://IP:8080/sensors.json`
|
||||
|
||||
@ -68,6 +68,7 @@ Also, with **power_on_enabled** as True, the Aquos logo on your TV will stay on
|
||||
## Currently known supported models
|
||||
|
||||
- LC-40LE830U
|
||||
- LC-40CFE6242E (no volume control, not fully tested but able to poll state)
|
||||
- LC-46LE830U
|
||||
- LC-52LE830U
|
||||
- LC-60LE830U
|
||||
|
||||
@ -103,6 +103,25 @@ If you have an August Keypad, once you have enabled the August component, you sh
|
||||
|
||||
- Keypad Battery
|
||||
|
||||
## Integration with Yale Access Bluetooth
|
||||
|
||||
Following Assa Abloy, Yale's parent company, purchasing August in 2017, most newer devices use the Yale Access branding.
|
||||
|
||||
The [Yale Access Bluetooth](/integrations/yalexe_ble) provides local control over Bluetooth of many Yale Access locks and some August locks that use the same system.
|
||||
|
||||
For locks that support the Yale Access system, the August integration can keep your offline access keys up to date to ensure you can operate your lock over Bluetooth. The following requirements must be met for the offline key updates to work:
|
||||
|
||||
- The August integration must support the lock.
|
||||
- The [Yale Access Bluetooth integration](/integrations/yalexe_ble) must support the lock.
|
||||
- The Bluetooth integration must be active and functional.
|
||||
- The lock must be discoverable by the [Yale Access Bluetooth integration](/integrations/yalexe_ble).
|
||||
- The account logged in with the August integration must have the offline keys.
|
||||
|
||||
### Troubleshooting offline keys updates
|
||||
|
||||
- If you do not know which account has the offline keys, configure August integration with each different Owner account until you find the one that holds the keys. You may need to make a new owner account and grant the account access to your lock to force the keys to synchronize with the cloud service.
|
||||
- Ensure the lock is in range and discoverable by the [Yale Access Bluetooth integration](/integrations/yalexe_ble).
|
||||
|
||||
## Presence Detection with Lock Operation
|
||||
|
||||
Using the lock operation sensors, you can detect when a user operates a lock and is physically present (not remote). The below automation example (added to `automations.yaml`) will trigger when the user named “John Doe” in August locks or unlocks the door from the keypad (if present), via Bluetooth from their phone, or by auto-unlock. The state of the sensor will be the name of the party operating the lock as returned by August.
|
||||
|
||||
28
source/_integrations/august_ble.markdown
Normal file
28
source/_integrations/august_ble.markdown
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
title: August Bluetooth
|
||||
description: Instructions on how to integrate August Bluetooth locks into Home Assistant.
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Lock
|
||||
- Sensor
|
||||
ha_bluetooth: true
|
||||
ha_release: 2022.9
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@bdraco'
|
||||
ha_domain: august_ble
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- lock
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_supporting_domain: yalexs_ble
|
||||
ha_supporting_integration: Yale Access Bluetooth
|
||||
---
|
||||
|
||||
Integrates [August](https://august.com/) locks over Bluetooth into Home Assistant.
|
||||
|
||||
Following Assa Abloy, Yale's parent company, purchasing August in 2017, most newer devices use the Yale Access branding.
|
||||
|
||||
{% include integrations/supported_brand.md %}
|
||||
@ -5,7 +5,7 @@ ha_category:
|
||||
- Health
|
||||
ha_config_flow: true
|
||||
ha_release: 0.84
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@ahayworth'
|
||||
- '@danielsjf'
|
||||
@ -17,13 +17,23 @@ ha_integration_type: integration
|
||||
|
||||
The Awair integration will fetch data from your [Awair devices](https://getawair.com).
|
||||
|
||||
You will need to request access to the Awair API and obtain an access token from the Awair [Developer Console](https://developer.getawair.com/). It is free, but getting a token can take up to 24 hours.
|
||||
## Prerequisites
|
||||
|
||||
### Connect locally (preferred)
|
||||
|
||||
When connecting locally, the integration will poll the device every 30 seconds. Awair provides a [list of devices](https://support.getawair.com/hc/en-us/articles/360049221014-Awair-Element-Local-API-Feature#h_01F40FB3ETMR4TZKPVXJNE86HQ) that support the Local API. This API must be enabled via the Awair app via [these steps](https://support.getawair.com/hc/en-us/articles/360049221014-Awair-Element-Local-API-Feature#h_01F40FBBW5323GBPV7D6XMG4J8). If you add new Awair devices to your home, you must follow these steps again.
|
||||
|
||||
### Connect via the cloud
|
||||
|
||||
When connecting via the cloud, data is summarized over 5-minute intervals. All devices are supported. You will need to request access to the Awair API and obtain an access token from the Awair [Developer Console](https://developer.getawair.com/). It is free, but getting a token can take up to 24 hours.
|
||||
|
||||
This integration refreshes once every 5 minutes, based on the [default per-device quota](https://docs.developer.getawair.com/?version=latest#tiers--quotas) of 300 API calls per day.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Available Sensors
|
||||
|
||||
The integration will fetch data from each device linked to your Awair developer account. The following sensors are supported:
|
||||
The integration will fetch data from each device. The following sensors are supported:
|
||||
|
||||
* Temperature
|
||||
* Humidity
|
||||
@ -35,5 +45,3 @@ The integration will fetch data from each device linked to your Awair developer
|
||||
* Luminescence
|
||||
|
||||
Not all devices support all sensors; consult Awair's documentation to find out what sensors are present on your device. For first-generation Awair devices with a "dust" sensor, the integration will create identical PM2.5 and PM10 sensors (which reflects the capabilities of the sensor - it can detect dust between PM2.5 and PM10 but cannot differentiate between them).
|
||||
|
||||
This integration refreshes once every 5 minutes, based on the [default per-device quota](https://docs.developer.getawair.com/?version=latest#tiers--quotas) of 300 API calls per day.
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.81
|
||||
ha_domain: rflink
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/en/21-rflink-). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First, you have to set up your [RFLink hub](/integrations/rflink/).
|
||||
|
||||
|
||||
@ -35,17 +35,34 @@ For Bluetooth to function on Linux systems, the [D-Bus](https://en.wikipedia.org
|
||||
- Home Assistant Supervised: The host system must run BlueZ, and the D-Bus socket must be accessible to Home Assistant **inside** the container.
|
||||
- Home Assistant Core: The system must run BlueZ, and the D-Bus socket must be accessible to Home Assistant.
|
||||
|
||||
### Additional details for Container installs
|
||||
|
||||
{% details Making the DBus socket available in the Docker container %}
|
||||
|
||||
For most systems, the Dbus socket is in `/run/dbus`. The socket must be available in the container for Home Assistant to be able to connect to Dbus and access the Bluetooth adapter. When starting with `docker run`, this can be accomplished by adding `-v /run/dbus:/run/dbus:ro` to the command. If the Dbus socket is in `/var/run/dbus` on the host system, use `-v /var/run/dbus:/run/dbus:ro` instead.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
### Additional details for Container and Supervised installs
|
||||
|
||||
{% details Installing BlueZ %}
|
||||
|
||||
On Debian based host systems, the `sudo apt-get -y install bluez` command will install BlueZ.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
## Installing a USB Bluetooth Adapter
|
||||
|
||||
Some systems may not come with Bluetooth and require a USB adapter. Installing an adapter for the first time may require multiple restarts for the device to be fully recognized.
|
||||
|
||||
If you experience an unreliable Bluetooth connection, installing a [USB extension cable with a Ferrite Bead](https://a.co/d/fRnFIwy) may improve reliability.
|
||||
If you experience an unreliable Bluetooth connection, installing a short USB extension cable between your Bluetooth adapter and your Home Assistant server may improve reliability.
|
||||
|
||||
### Known working adapters
|
||||
|
||||
- ASUS USB-BT400
|
||||
- ASUS USB-BT500
|
||||
- Avantree DG45
|
||||
- Kinivo BTD-400
|
||||
- Maxuni BT-501
|
||||
- SUMEE BT501
|
||||
- UGREEN CM390
|
||||
@ -58,19 +75,27 @@ If you experience an unreliable Bluetooth connection, installing a [USB extensio
|
||||
- tp-link UB400 - Frequent connection failures
|
||||
- tp-link UB500 - Frequent connection failures
|
||||
|
||||
{% include integrations/option_flow.md %}
|
||||
## Multiple adapters
|
||||
|
||||
### Multiple adapters
|
||||
Support for multiple local Bluetooth adapters is available on Linux systems only. Place adapters far enough away from each other to reduce interference.
|
||||
|
||||
Support for multiple Bluetooth adapters is available on Linux systems only. Select the adapter you wish to use via the options flow on the integrations page. The adapter selection only affects integrations that use the Bluetooth integration interfaces.
|
||||
The following methods are known to work to add multiple adapters:
|
||||
|
||||
## Integrations that require exclusive use of the Bluetooth Adapter
|
||||
- Long USB Extension cables
|
||||
- USB-Ethernet extenders
|
||||
- [USB/IP](http://usbip.sourceforge.net/)
|
||||
|
||||
Integrations that have followed the [Best practices for library authors](https://developers.home-assistant.io/docs/network_discovery?_highlight=bluetooth#best-practices-for-library-authors) will automatically connect via the adapter with the best signal and failover to an active adapter if one becomes unavailable.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Integrations that require exclusive use of the Bluetooth Adapter
|
||||
|
||||
While newer integrations can share the Bluetooth Adapter, some legacy integrations require exclusive use of the adapter. Enabling this integration may prevent an integration that has not been updated to use newer methods from functioning.
|
||||
|
||||
Deleting the config entry for this integration will release control of the adapter and allow another integration to gain exclusive use of the Bluetooth adapter. If you have manually added `bluetooth:` to your `configuration.yaml`, you must also remove it to prevent the configuration from being recreated. Consider adding a second Bluetooth adapter on Linux systems if you need to continue using legacy integrations, as more integrations will move to use the Bluetooth integration in the future.
|
||||
|
||||
## Bluetooth interference with other devices
|
||||
### Bluetooth interference with other devices
|
||||
|
||||
Devices that are using the 2.4 GHz band, like Wi-Fi, Zigbee, and USB3 devices (and their cable connections) are known to affect Bluetooth reception. Especially external SSD drives with USB3 cables are known to block the Bluetooth signal. Also, metal casings can decrease the Bluetooth performance of internal Bluetooth Adapters.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ Devices discovered are stored with 'BLE_' as the prefix for device mac addresses
|
||||
|
||||
## Setup
|
||||
|
||||
This platform requires pybluez to be installed, which is already the case if you're using Home Assistant OS, Supervised or Container. For Home Assistant Core installs see below on the required steps.
|
||||
This integration requires the [Bluetooth](/integrations/bluetooth) integration to be enabled and functional.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -58,30 +58,3 @@ Some BTLE devices (e.g., fitness trackers) are only visible to the devices that
|
||||
Enabling the battery tracking might slightly decrease the duration of the battery, but since this is only done at most once a day, this shouldn't be noticeable. Not all devices offer battery status information; if the information is not available, the integration will only try once at startup.
|
||||
|
||||
For additional configuration variables check the [Device tracker page](/integrations/device_tracker/).
|
||||
|
||||
{% details "Notes for Home Assistant Core Installations" %}
|
||||
|
||||
On Debian based Home Assistant Core installations, run:
|
||||
|
||||
```bash
|
||||
sudo apt install bluetooth
|
||||
```
|
||||
|
||||
Before you get started with this platform, please note that:
|
||||
|
||||
- This platform is incompatible with Windows
|
||||
- This platform requires access to the Bluetooth stack, see [Rootless Setup section](#rootless-setup) for further information
|
||||
|
||||
### Rootless Setup on Core installs
|
||||
|
||||
Normally accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 and hcitool the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see [Stack Exchange](https://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root) for more information).
|
||||
|
||||
```bash
|
||||
sudo apt-get install libcap2-bin
|
||||
sudo setcap 'cap_net_raw,cap_net_admin+eip' $(readlink -f $(which python3))
|
||||
sudo setcap 'cap_net_raw+ep' $(readlink -f $(which hcitool))
|
||||
```
|
||||
|
||||
A restart of Home Assistant is required.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
@ -132,10 +132,10 @@ enabled_by_default:
|
||||
type: boolean
|
||||
default: true
|
||||
encoding:
|
||||
description: The encoding of the image payloads received. Set to `"b64"` to enable base64 decoding of image payload. If not set, or if set to `null`, the image payload must be raw binary data.
|
||||
description: The encoding of the payloads received. Set to `""` to disable decoding of incoming payload. Use `image_encoding` to enable `Base64` decoding on `topic`.
|
||||
required: false
|
||||
type: string
|
||||
default: null
|
||||
default: "utf-8"
|
||||
entity_category:
|
||||
description: The [category](https://developers.home-assistant.io/docs/core/entity#generic-properties) of the entity.
|
||||
required: false
|
||||
@ -145,6 +145,11 @@ icon:
|
||||
description: "[Icon](/docs/configuration/customizing-devices/#icon) for the entity."
|
||||
required: false
|
||||
type: icon
|
||||
image_encoding:
|
||||
description: The encoding of the image payloads received. Set to `"b64"` to enable base64 decoding of image payload. If not set, the image payload must be raw binary data.
|
||||
required: false
|
||||
type: string
|
||||
default: None
|
||||
json_attributes_template:
|
||||
description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the JSON dictionary from messages received on the `json_attributes_topic`."
|
||||
required: false
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.55
|
||||
ha_domain: rflink
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/en/21-rflink-). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First, you have to set up your [RFLink hub](/integrations/rflink/).
|
||||
|
||||
|
||||
@ -78,6 +78,7 @@ Known supported devices:
|
||||
- Marantz SR5011
|
||||
- Marantz SR6007 - SR6012
|
||||
- Marantz SR7007
|
||||
- Marantz SR7012
|
||||
- Marantz SR8015
|
||||
- Marantz NR1504
|
||||
- Marantz NR1506
|
||||
|
||||
@ -11,6 +11,10 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
<div class='note warning'>
|
||||
This integration is pending removal from Home Assistant and will be no longer available as of Home Assistant 2022.11.
|
||||
</div>
|
||||
|
||||
The `deutsche_bahn` sensor will give you the departure time of the next train for the given connection. In case of a delay, the delay is also shown. Additional details are used to inform about, e.g., the type of the train, price, and if it is on time.
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
@ -27,3 +27,8 @@ ha_release: pre 0.7
|
||||
---
|
||||
|
||||
{% include integrations/supported_brand.md %}
|
||||
|
||||
The only tested working model is the Pro Switch.
|
||||
|
||||
Supported Digital Loggers models emulate the WeMo protocol but this is not automatically enabled.
|
||||
To enable this, find the IP address of your device and log in. Click on External APIs, check the box to allow CoAP, and then click submit.
|
||||
|
||||
@ -67,6 +67,7 @@ Tested devices:
|
||||
- Epson WF3540
|
||||
- Epson WF3620
|
||||
- Epson WF3640
|
||||
- Epson WF4820
|
||||
- Epson EcoTank ET-77x0
|
||||
- Epson ET-2650
|
||||
- Epson ET-4750
|
||||
|
||||
47
source/_integrations/escea.markdown
Normal file
47
source/_integrations/escea.markdown
Normal file
@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Escea
|
||||
description: Instructions on how to integrate Escea fireplaces with Home Assistant.
|
||||
ha_category:
|
||||
- Climate
|
||||
ha_release: 2022.9
|
||||
ha_iot_class: Local Push
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@lazdavila'
|
||||
ha_domain: escea
|
||||
ha_homekit: true
|
||||
ha_platforms:
|
||||
- climate
|
||||
---
|
||||
|
||||
The Escea integration allows monitoring and control of local [Escea](https://escea.com/) fireplaces. These fireplaces are manufactured in New Zealand and sold throughout Australia and New Zealand.
|
||||
|
||||
## Supported hardware
|
||||
|
||||
Support all current Escea fireplaces with the Smart Heat feature, including the DF, DL, DS, and DX series.
|
||||
Though these fireplaces are supported, they can only be integrated if they were connected via Ethernet when installed (i.e., these fireplaces do not support Wi-Fi).
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Network settings
|
||||
|
||||
The Escea system uses UDP over the local network to find and communicate with Escea devices. For this to work properly, UDP port 3300 must be available for broadcasting and messaging fireplaces, and similarly, UDP port 3300 must be available to listen for responses. The integration currently listens on `0.0.0.0` and broadcasts to all broadcast IPv4 local addresses, which is not configurable.
|
||||
|
||||
## Master controller
|
||||
|
||||
Fireplace on / off, fan settings, and desired temperature settings are supported. The current room temperature, as measured by the fireplace, is also supported.
|
||||
|
||||
## Debugging
|
||||
|
||||
If you're trying to track down issues with the component, set up logging for it:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml with logging for Escea
|
||||
logger:
|
||||
default: warning
|
||||
logs:
|
||||
homeassistant.components.escea: debug
|
||||
pescea: debug
|
||||
```
|
||||
|
||||
This will help you to find network connection issues etc.
|
||||
@ -10,14 +10,13 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `ffmpeg` integration allows other Home Assistant integrations to process video and audio streams. This integration supports all FFmpeg versions since 3.0.0; if you have an older version, please update.
|
||||
The FFmpeg integration allows other Home Assistant integrations to process
|
||||
video and audio streams.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
If you are running Home Assistant Core in a Python environment, you'll need have the `ffmpeg` binary in your system path.
|
||||
On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself.
|
||||
|
||||
</div>
|
||||
This integration supports all FFmpeg versions since 3.0.0. If you run
|
||||
the Home Assistant Operating System or use the Home Assistant Container,
|
||||
this is already pre-installed for you. In all other cases, make sure
|
||||
you have FFmpeg installed on your system.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -35,27 +34,14 @@ ffmpeg_bin:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### Raspbian Debian Jessie Lite Installations
|
||||
To get the binary on Raspbian Debian Jessie Lite on a Raspberry Pi you need to perform the following:
|
||||
|
||||
```bash
|
||||
sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
|
||||
sudo apt-get update
|
||||
sudo apt-get -t jessie-backports install ffmpeg
|
||||
```
|
||||
|
||||
We can use now following in the configuration:
|
||||
|
||||
```yaml
|
||||
ffmpeg:
|
||||
ffmpeg_bin: /usr/bin/ffmpeg
|
||||
```
|
||||
|
||||
### Troubleshooting
|
||||
|
||||
In most cases, `ffmpeg` automatically detects all needed options to read a video or audio stream or file. But it is possible in rare cases that you will need to set options to help `ffmpeg` out.
|
||||
In most cases, `ffmpeg` automatically detects all needed options to read
|
||||
a video or audio stream or file. But it is possible in rare cases that you
|
||||
will need to set options to help `ffmpeg` out.
|
||||
|
||||
First, check that your stream is playable by `ffmpeg` outside of Home Assistant with (use option `-an` or `-vn` to disable video or audio stream):
|
||||
First, check that your stream is playable by `ffmpeg` outside of Home Assistant
|
||||
with (use option `-an` or `-vn` to disable video or audio stream):
|
||||
|
||||
```bash
|
||||
ffmpeg -i INPUT -an -f null -
|
||||
|
||||
@ -78,16 +78,16 @@ filters:
|
||||
description: Algorithm to be used to filter data. Available filters are `lowpass`, `outlier`, `range`, `throttle`, `time_throttle` and `time_simple_moving_average`.
|
||||
required: true
|
||||
type: string
|
||||
precision:
|
||||
description: Defines the precision of the filtered state, through the argument of round().
|
||||
required: false
|
||||
type: integer
|
||||
default: 2
|
||||
window_size:
|
||||
description: Size of the window of previous states. Time based filters such as `time_simple_moving_average` will require a time period (size in time), while other filters such as `outlier` will require an integer (size in number of states). Time periods are in _hh:mm_ format and must be quoted.
|
||||
required: false
|
||||
type: [integer, time]
|
||||
default: 1
|
||||
precision:
|
||||
description: See [_lowpass_](#low-pass) filter. Defines the precision of the filtered state, through the argument of round().
|
||||
required: false
|
||||
type: integer
|
||||
default: None
|
||||
time_constant:
|
||||
description: See [_lowpass_](#low-pass) filter. Loosely relates to the amount of time it takes for a state to influence the output.
|
||||
required: false
|
||||
@ -129,8 +129,6 @@ A = 1.0 - B
|
||||
LowPass(state) = A * previous_state + B * state
|
||||
```
|
||||
|
||||
The returned value is rounded to the number of decimals defined in (`precision`).
|
||||
|
||||
### Outlier
|
||||
|
||||
The Outlier filter (`outlier`) is a basic Band-pass filter, as it cuts out any value outside a specific range.
|
||||
|
||||
@ -15,6 +15,10 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
<div class='note warning'>
|
||||
This integration is pending removal from Home Assistant and will be no longer available as of Home Assistant 2022.10.
|
||||
</div>
|
||||
|
||||
The `flunearyou` sensor platform allows users in the United States and its
|
||||
territories to get information regarding reported flu symptoms from [Flu Near
|
||||
You](https://flunearyou.org/). The platform can return user-reported information as well reports from the
|
||||
|
||||
@ -31,6 +31,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Binary Sensor
|
||||
- Climate
|
||||
- Cover
|
||||
- Light
|
||||
- Sensor
|
||||
- Switch
|
||||
@ -47,6 +48,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [FRITZ!DECT 500](https://en.avm.de/products/fritzdect/fritzdect-500/)
|
||||
- [Eurotronic Comet DECT](https://eurotronic.org/produkte/dect-ule-heizkoerperthermostat/comet-dect/)
|
||||
- [Magenta SmartHome LED E27](https://www.smarthome.de/geraete/smarthome-led-lampe-e27-farbig-weiss)
|
||||
- [Rademacher RolloTron DECT 1213](https://www.rademacher.de/shop/rollladen-sonnenschutz/elektrischer-gurtwickler/rollotron-dect-1213)
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -108,3 +110,7 @@ To get AVM FRITZ!DECT lightbulbs (e.g., FRITZ!DECT 500) follow the [configuratio
|
||||
<div class='note'>
|
||||
The FRITZ!DECT 500 lightbulb supports only 36 colors. When a color is picked in home assistant that is not supported by the device, a color that comes close will be activated.
|
||||
</div>
|
||||
|
||||
## Cover
|
||||
|
||||
To get AVM FRITZ!DECT compatible covers (e.g., Rademacher RolloTron DECT 1213) follow the [configuration instructions](#configuration) above.
|
||||
|
||||
@ -103,7 +103,7 @@ Theme `sad`: By using the new `modes` key plus the subkey `dark` this theme will
|
||||
|
||||
Note: Since this example theme only has a `dark` mode defined, this mode will automatically be used.
|
||||
|
||||
Theme `day_and_night`: This theme has both a `light` and a `dark` mode section. That tells the frontend to allow the user to choose which mode to use from the user profile (default selection is based on the system settings). Independent of the selection, the primary color will be set to green, but based on the chosen mode either the default light or dark theme will be used as the basis for rendering, plus the secondary text color will be either olive or slategray.
|
||||
Theme `day_and_night`: This theme has both a `light` and a `dark` mode section. That tells the frontend to allow the user to choose which mode to use from the user profile (default selection is based on the system settings). Independent of the selection, the primary color will be set to coral, but based on the chosen mode either the default light or dark theme will be used as the basis for rendering, plus the secondary text color will be either olive or slategray.
|
||||
|
||||
### Theme configuration splitting
|
||||
|
||||
|
||||
59
source/_integrations/fully_kiosk.markdown
Normal file
59
source/_integrations/fully_kiosk.markdown
Normal file
@ -0,0 +1,59 @@
|
||||
---
|
||||
title: Fully Kiosk Browser
|
||||
description: Instructions on how to integrate Fully Kiosk Browser with Home Assistant
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: 2022.9
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@cgarwood'
|
||||
ha_domain: fully_kiosk
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
[Fully Kiosk Browser](https://www.fully-kiosk.com) is a powerful kiosk browser for Android devices. It provides a number of features for monitoring and controlling your Android device. This integration gives you access to control your device and view the status in Home Assistant.
|
||||
|
||||
## Requirements
|
||||
|
||||
This integration requires the Fully Remote Admin feature to be enabled in the Fully Kiosk Browser app. This feature requires the paid Fully Plus license. You can test it out for free, but Fully Kiosk Browser will display a watermark on your device.
|
||||
|
||||
You will need the IP address of your device, and the Fully Remote Admin password you set in the Fully Kiosk Browser app.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Capabilities
|
||||
|
||||
The following is available as sensors:
|
||||
|
||||
- Device plugged in
|
||||
- Kiosk mode enabled/disabled
|
||||
- Battery level
|
||||
- Current page
|
||||
- Current foreground app
|
||||
- Device storage space available
|
||||
- Device RAM available
|
||||
|
||||
The following controls are available:
|
||||
|
||||
- Bring Fully Kiosk to the foreground
|
||||
- Send Fully Kiosk to the background
|
||||
- Load the start URL
|
||||
- Restart the Fully Kiosk Browser app
|
||||
- Reboot your device (requires root)
|
||||
- Maintenance mode on/off
|
||||
- Lock/unlock kiosk mode
|
||||
- Motion detection on/off
|
||||
- Screensaver on/off
|
||||
- Screensaver timer
|
||||
- Screensaver brightness
|
||||
- Screen on/off
|
||||
- Screen off timer
|
||||
- Screen brightness
|
||||
@ -60,7 +60,7 @@ ac_mode:
|
||||
type: boolean
|
||||
default: false
|
||||
min_cycle_duration:
|
||||
description: Set a minimum amount of time that the switch specified in the *heater* option must be in its current state prior to being switched either off or on.
|
||||
description: Set a minimum amount of time that the switch specified in the *heater* option must be in its current state prior to being switched either off or on. This option will be ignored if the `keep_alive` option is set.
|
||||
required: false
|
||||
type: [time, integer]
|
||||
cold_tolerance:
|
||||
@ -74,7 +74,7 @@ hot_tolerance:
|
||||
default: 0.3
|
||||
type: float
|
||||
keep_alive:
|
||||
description: Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate integration state (either on or off).
|
||||
description: Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate integration state (either on or off). When `keep_alive` is set the `min_cycle_duration` option will be ignored.
|
||||
required: false
|
||||
type: [time, integer]
|
||||
initial_hvac_mode:
|
||||
|
||||
@ -29,7 +29,7 @@ This section explains how to generate a Client ID and Client Secret on
|
||||
1. The wizard will ask you to choose a project to manage your application. Select a project and click continue.
|
||||
1. Verify that your calendar API was enabled and click 'Go to credentials'
|
||||
1. Navigate to APIs & Services (left sidebar) > [Credentials](https://console.cloud.google.com/apis/credentials)
|
||||
1. Click on the field on the right of the screen, **OAuth Consent Screen**.
|
||||
1. Click on the field on the left of the screen, **OAuth Consent Screen**.
|
||||
1. Select **External** and **Create**.
|
||||
1. Set the *App Name* (the name of the application asking for consent) to anything you want e.g. *Home Assistant*.
|
||||
1. You then need to select a *Support email*. To do this, simply click the drop down box and select your email address.
|
||||
|
||||
@ -23,8 +23,15 @@ The Govee BLE integration will automatically discover devices once the [Bluetoot
|
||||
|
||||
## Supported devices
|
||||
|
||||
- [H5177/5178 Bluetooth Thermo-Hygrometer](https://us.govee.com/collections/thermo-hydrometer/products/bluetooth-thermo-hygrometer)
|
||||
- H5071 Hygrometer Thermometer
|
||||
- H5072 Hygrometer Thermometer
|
||||
- H5074 Hygrometer Thermometer
|
||||
- [H5075 Bluetooth Hygrometer Thermometer](https://us.govee.com/collections/thermo-hydrometer/products/govee-bluetooth-hygrometer-thermometer-h5075)
|
||||
- H5100 Hygrometer Thermometer
|
||||
- H5101 Hygrometer Thermometer
|
||||
- [H5177/5178 Bluetooth Thermo-Hygrometer](https://us.govee.com/collections/thermo-hydrometer/products/bluetooth-thermo-hygrometer)
|
||||
- H5179 Hygrometer Thermometer
|
||||
- 5181 Meat Thermometer
|
||||
- 5183 Meat Thermometer
|
||||
- 5184 Meat Thermometer
|
||||
- 5185 Meat Thermometer
|
||||
|
||||
@ -27,7 +27,7 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The [HomematicIP](https://www.homematic-ip.com/) integration platform is used as an interface to the cloud server. Since there is no official documentation about this API, everything was done via reverse engineering. The [homematicip-rest-api](https://github.com/coreGreenberet/homematicip-rest-api) is used for communicating. Use at your own risk.
|
||||
The [HomematicIP](https://www.homematic-ip.com/) integration platform is used as an interface to the cloud server. Since there is no official documentation about this API, everything was done via reverse engineering. Use at your own risk.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -168,7 +168,7 @@ tags_attributes:
|
||||
default: 0
|
||||
ignore_attributes:
|
||||
type: [string, list]
|
||||
description: The list of attribute names to ignore when reporting to InfluxDB. This can be used to filter out attributes that either don't change or don't matter to you in order to reduce the amount of data stored in InfluxDB.
|
||||
description: The list of attribute names to ignore when reporting to InfluxDB. This can be used to filter out attributes that either don't change or don't matter to you in order to reduce the amount of data stored in InfluxDB. Please be aware of the underlying InfluxDB mechanism that converts non-string attributes to strings and adds a `_str` suffix to the attribute name in this case. It means that when you want to ignore, for example, the `icon_str` attribute that shows in your InfluxDB instance, you need to provide `icon` to `ignore_attributes`.
|
||||
required: false
|
||||
component_config:
|
||||
type: string
|
||||
|
||||
@ -27,7 +27,7 @@ ha_integration_type: integration
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
<p class='note warning'>The Insteon company has shut down and turned off their cloud as of April 2022.</p>
|
||||
<p class='note warning'>The Insteon company has shut down and turned off its cloud as of April 2022. Recently the service has been restarted but as a paid offering. Time will tell how successful this new model will be.</p>
|
||||
|
||||
This integration adds support for integrating your INSTEON network with Home Assistant. It is known to work with the [2413U] USB and [2412S] RS242 flavors of PLM and the [2448A7] USB stick. It has also been tested to work with the [2242] and [2245] Hubs. Device support is provided by the underlying [pyinsteon] package.
|
||||
|
||||
|
||||
@ -22,6 +22,7 @@ This platform calculates prayer times using the following calculation methods:
|
||||
- Islamic Society of North America
|
||||
- Muslim World League
|
||||
- Umm Al-Qura University in Makkah
|
||||
- Moonsighting
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -93,6 +93,8 @@ Time sensor states are represented as ISO8601 formatted *UTC time*.
|
||||
### Binary sensors
|
||||
|
||||
- `issur_melacha_in_effect`: A boolean sensor indicating if melacha is currently not permitted. The value is _on_ when it is currently Shabbat or Yom Tov and _off_ otherwise.
|
||||
- `erev_shabbat_hag`: A boolean sensor indicating that there is an upcoming Shabbat or Hag.
|
||||
- `motzei_shabbat_hag`: A boolean sensor indicating that Shabbat or Hag has ended.
|
||||
|
||||
### Holiday sensor
|
||||
|
||||
|
||||
43
source/_integrations/justnimbus.markdown
Normal file
43
source/_integrations/justnimbus.markdown
Normal file
@ -0,0 +1,43 @@
|
||||
---
|
||||
title: JustNimbus
|
||||
description: Instructions on how to configure the JustNimbus integration within Home Assistant
|
||||
ha_category:
|
||||
- Environment
|
||||
ha_release: 2022.9
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: justnimbus
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_config_flow: true
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The JustNimbus integration queries the JustNumbus API used by the JustNimbus web dashboard.
|
||||
This integration allows you to collect and save data to get an historic overview of your water bag
|
||||
usage.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
To configure and use this integration, you need to have a
|
||||
[JustNimbus water bag](https://justnimbus.com/regenwatersysteem/) (Dutch), and
|
||||
you need to be subscribed for the web dashboard functionality. For this configuration, you need the
|
||||
client ID from the URL. For example: `https://dashboard.justnimbus.com/api/installation/<client_id>/data`.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Sensor Types
|
||||
|
||||
When configured, the integration will create twelve sensors for each configured client ID:
|
||||
|
||||
- Pump flow, in `L/min` (Liters/minute)
|
||||
- Drink flow, in `L/min` (Liters/minute)
|
||||
- Pump pressure, in `bar`
|
||||
- Pump starts, a number counting the number of times the pump has started
|
||||
- Pump hours, a number counting the number of hours the pump has been used
|
||||
- Reservoir temperature, in `°C`
|
||||
- Reservoir content, in `L` (Liters)
|
||||
- Total saved, in `L` (Liters)
|
||||
- Total replenished, in `L` (Liters)
|
||||
- Error code
|
||||
- Total use, in `L` (Liters)
|
||||
- Max reservoir content, in `L` (Liters)
|
||||
29
source/_integrations/lacrosse_view.markdown
Normal file
29
source/_integrations/lacrosse_view.markdown
Normal file
@ -0,0 +1,29 @@
|
||||
---
|
||||
title: "LaCrosse View"
|
||||
description: "Get data for LaCrosse View-connected sensors"
|
||||
ha_release: "2022.6"
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_quality_scale: platinum
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@IceBotYT'
|
||||
ha_domain: lacrosse_view
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
[**LaCrosse View**](https://www.lacrossetechnology.com/pages/la-crosse-view) is the service provided by LaCrosse Technology that allows access to LaCrosse sensors.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
If you are looking for an integration for [**Jeelink LaCrosse sensors**](/integrations/lacrosse), you can find that integration [**here**](/integrations/lacrosse).
|
||||
|
||||
</div>
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Supported sensors
|
||||
|
||||
All of the sensors on [**this page**](https://www.lacrossetechnology.com/collections/lacrosse-view-connected) are supported by this integration.
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: LaMetric
|
||||
description: Instructions on how to integrate LaMetric with Home Assistant.
|
||||
description: Instructions on how to integrate LaMetric TIME with Home Assistant.
|
||||
ha_category:
|
||||
- Hub
|
||||
- Notifications
|
||||
ha_iot_class: Cloud Push
|
||||
- Number
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.49
|
||||
ha_codeowners:
|
||||
- '@robbiet480'
|
||||
@ -12,139 +12,168 @@ ha_codeowners:
|
||||
ha_domain: lametric
|
||||
ha_platforms:
|
||||
- notify
|
||||
- number
|
||||
ha_integration_type: integration
|
||||
ha_config_flow: true
|
||||
ha_ssdp: true
|
||||
---
|
||||
|
||||
[LaMetric Time](https://lametric.com/) is a smart clock that can be used to access applications, listen to web radio and display notifications.
|
||||
[LaMetric TIME](https://lametric.com/) is a smart clock that can be used to access applications, listen to web radio and display notifications.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- [Notify](#notifications)
|
||||
|
||||
The LaMetric Time can only be accessed by authorized applications. Therefore, each application that wants to access the LaMetric time needs to be registered at the LaMetric Developer web page. Sign Up and login to the developer web page. Click the Create button in the upper right corner, then select Notification App and click Create again. Enter an app name, a description and a redirect URL. Finally, click Save to create the application. For the newly created app you will obtain a client id and a client secret that is required in the following configuration.
|
||||
|
||||
```yaml
|
||||
# configuration.yaml example
|
||||
lametric:
|
||||
client_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
|
||||
client_secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
||||
```
|
||||
|
||||
## Setup Steps
|
||||
|
||||
LaMetric needs an OAuth2 `client_id` and `client_secret` from the LaMetric developer portal to use it with Home Assistant.
|
||||
These are the steps to take:
|
||||
|
||||
1. Log in with your LaMetric device account to [developer.lametric.com](https://developer.lametric.com).
|
||||
2. Hit the Create button and choose [Notification](https://developer.lametric.com/applications/createsource).
|
||||
3. Fill in the form. You can put almost anything in the fields, they just need to be populated:
|
||||
* App Name: Home Assistant
|
||||
* Description: Home Assistant
|
||||
* Privacy Policy: `http://localhost/`
|
||||
* Check all permission boxes
|
||||
* Hit Save
|
||||
4. You should be directed to your [Notification Apps list](https://developer.lametric.com/applications/sources), click on "Home Assistant", copy your client ID and client Secret and paste into the Home Assistant configuration block in the previous section.
|
||||
5. Set up some notifications in Home Assistant by following the instructions on the [Lametric Notify](/integrations/lametric) page.
|
||||
6. Save all configuration files and restart Home Assistant.
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Notifications
|
||||
|
||||
The `lametric` notification platform allows to send notification to a LaMetric device. It needs the LaMetric platform to be configured first.
|
||||
You can send notifications to your LaMetric device using
|
||||
the [Notifications](/integrations/notify) integration.
|
||||
|
||||
To enable LaMetric notifications in your installation, add the following to your `configuration.yaml` file:
|
||||
Each LaMetric device added to your Home Assistant will have its own
|
||||
`notify.` service. The service name matches the name of your device
|
||||
as shown in your LaMetric account. For example, if you have a device
|
||||
called "My LaMetric", the service would become `notify.my_lametric`.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
name: NOTIFIER_NAME
|
||||
platform: lametric
|
||||
```
|
||||
The notification service call against an LaMetric device can take the
|
||||
following, additional, optional parameters:
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: "The optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`."
|
||||
required: false
|
||||
type: string
|
||||
default: notify
|
||||
lifetime:
|
||||
description: Defines how long the message remains in LaMetric notification queue (in seconds).
|
||||
required: false
|
||||
type: integer
|
||||
default: 10
|
||||
icon:
|
||||
description: An icon or animation. List of all icons available at [https://developer.lametric.com/icons](https://developer.lametric.com/icons). Note that icons always begin with "i" while animations begin with "a". This is part of the name, you can't just use the number!
|
||||
description: "An icon or animation. List of all icons available at [https://developer.lametric.com/icons](https://developer.lametric.com/icons)."
|
||||
required: false
|
||||
type: string
|
||||
cycles:
|
||||
description: Defines how long the notification will be displayed. Set to 0 to require manual dismissal
|
||||
description: "Defines how long the notification will be displayed. Set to `0` to require manual dismissal."
|
||||
required: false
|
||||
type: integer
|
||||
default: 1
|
||||
priority:
|
||||
description: Defines the priority of the notification. Allowed values are info, warning, and critical
|
||||
description: "Defines the priority of the notification. Allowed values are `info`, `warning`, and `critical`."
|
||||
required: false
|
||||
type: string
|
||||
default: warning
|
||||
icon_type:
|
||||
description: Defines the nature of notification. Allowed values are none, info, and alert
|
||||
description: "Defines the nature of notification. Allowed values are `none`, `info`, and `alert`."
|
||||
required: false
|
||||
type: string
|
||||
default: info
|
||||
default: none
|
||||
sound:
|
||||
description: "Defines the sound of the notification. Allowed are listed [below](#list-of-notification-sounds)."
|
||||
required: false
|
||||
type: string
|
||||
default: none
|
||||
{% endconfiguration %}
|
||||
|
||||
## Example
|
||||
|
||||
## Examples
|
||||
|
||||
### Full configuration example
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
name: NOTIFIER_NAME
|
||||
platform: lametric
|
||||
lifetime: 20
|
||||
icon: a7956
|
||||
cycles: 3
|
||||
priority: info
|
||||
icon_type: none
|
||||
```
|
||||
|
||||
### Changing sounds and icons
|
||||
|
||||
To add a notification sound, icon, cycles, or priority override, it has to be done via service data.
|
||||
To add a notification sound, icon, cycles, or priority override,
|
||||
|
||||
```yaml
|
||||
- alias: "Send notification on arrival at school"
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: device_tracker.son_mobile
|
||||
entity_id: device_tracker.tom_mobile
|
||||
from: "not_home"
|
||||
to: "school"
|
||||
action:
|
||||
service: notify.lametric
|
||||
service: notify.my_lametric
|
||||
data:
|
||||
message: "Son has arrived at school!"
|
||||
message: "Tom has arrived at school!"
|
||||
data:
|
||||
sound: "notification"
|
||||
icon: "i51"
|
||||
icon: "51"
|
||||
cycles: 0
|
||||
priority: "critical"
|
||||
icon_type: "none"
|
||||
icon_type: "info"
|
||||
```
|
||||
|
||||
### Only notify specific device
|
||||
## List of notification sounds
|
||||
|
||||
If you have more than one La Metric device, you can specify which will receive the message by adding `target:` to the service data:
|
||||
The following notification sounds can be used with the `sound` parameter on
|
||||
notify service calls:
|
||||
|
||||
```yaml
|
||||
action:
|
||||
service: notify.lametric
|
||||
data:
|
||||
message: "Son has arrived at school!"
|
||||
target: "Office LaMetric"
|
||||
data:
|
||||
sound: "notification"
|
||||
icon: "i51"
|
||||
```
|
||||
- `alarm1`
|
||||
- `alarm10`
|
||||
- `alarm11`
|
||||
- `alarm12`
|
||||
- `alarm13`
|
||||
- `alarm2`
|
||||
- `alarm3`
|
||||
- `alarm4`
|
||||
- `alarm5`
|
||||
- `alarm6`
|
||||
- `alarm7`
|
||||
- `alarm8`
|
||||
- `alarm9`
|
||||
- `bicycle`
|
||||
- `car`
|
||||
- `cash`
|
||||
- `cat`
|
||||
- `dog`
|
||||
- `dog2`
|
||||
- `energy`
|
||||
- `knock-knock`
|
||||
- `letter_email`
|
||||
- `lose1`
|
||||
- `lose2`
|
||||
- `negative1`
|
||||
- `negative2`
|
||||
- `negative3`
|
||||
- `negative4`
|
||||
- `negative5`
|
||||
- `notification`
|
||||
- `notification2`
|
||||
- `notification3`
|
||||
- `notification4`
|
||||
- `open_door`
|
||||
- `positive1`
|
||||
- `positive2`
|
||||
- `positive3`
|
||||
- `positive4`
|
||||
- `positive5`
|
||||
- `positive6`
|
||||
- `statistic`
|
||||
- `thunder`
|
||||
- `water1`
|
||||
- `water2`
|
||||
- `win`
|
||||
- `win2`
|
||||
- `wind_short`
|
||||
- `wind`
|
||||
|
||||
If target is not specified, all LaMetric devices will be notified.
|
||||
## Manual automatic import configuration
|
||||
|
||||
If you prefer not to use the Home Assistant account linking service, you
|
||||
can set up the LaMetric application manually.
|
||||
|
||||
However, please note! At this point, it is easier to choose the "Enter manually"
|
||||
option during the integration setup; this also avoids the use of the account
|
||||
linking service and doesn't need all the steps below either.
|
||||
|
||||
If you still want to set up your own LaMetric application for importing
|
||||
your LaMetric devices, use the following steps:
|
||||
|
||||
1. Log in with your LaMetric device account to [developer.lametric.com](https://developer.lametric.com).
|
||||
2. Click the Create button and choose [Notification](https://developer.lametric.com/applications/createsource) app.
|
||||
3. Fill in the form. You can put almost anything in the fields, they just need to be populated:
|
||||
* App Name: Home Assistant
|
||||
* Description: Home Assistant
|
||||
* Redirect URI: `https://my.home-assistant.io/redirect/oauth`
|
||||
* Privacy Policy: `http://localhost/`
|
||||
* Check the "basic" and "read_devices" permission boxes
|
||||
* Click Save
|
||||
4. You should be directed to your [Notification Apps list](https://developer.lametric.com/applications/sources),
|
||||
click on "Home Assistant", copy your client ID and Client Secret.
|
||||
|
||||
You may then add the credentials to [Application Credentials](/integrations/application_credentials/) and then setup the integration.
|
||||
|
||||
{% details "I have manually disabled My Home Assistant" %}
|
||||
|
||||
If you don't have [My Home Assistant](/integrations/my) on your installation,
|
||||
you can use `<HOME_ASSISTANT_URL>/auth/external/callback` as the redirect URI
|
||||
instead.
|
||||
|
||||
The `<HOME_ASSISTANT_URL>` must be the same as used during the configuration/
|
||||
authentication process.
|
||||
|
||||
Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://homeassistant.local:8123/auth/external/callback`."
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
87
source/_integrations/landisgyr_heat_meter.markdown
Normal file
87
source/_integrations/landisgyr_heat_meter.markdown
Normal file
@ -0,0 +1,87 @@
|
||||
---
|
||||
title: Landis+Gyr Heat Meter
|
||||
description: Instructions on how to integrate your Landis+Gyr Heat Meter device into Home Assistant.
|
||||
ha_category:
|
||||
- Energy
|
||||
- Sensor
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_release: 2022.9
|
||||
ha_domain: landisgyr_heat_meter
|
||||
ha_codeowners:
|
||||
- '@vpathuis'
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The Landis+Gyr Heat Meter integration for Home Assistant allows you to read the meter values from Ultraheat devices by Landis & Gyr. These devices are commonly used for district heating. The integration has been tested with the Landis & Gyr Ultraheat 50 (UH50), type LUGCUH50. Other models are likely to work as well.
|
||||
|
||||
The device is read through the optical interface. An (USB) IR reader is needed and connected to Home Assistant.
|
||||
|
||||
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Sensors
|
||||
|
||||
The integration will create the following sensors:
|
||||
|
||||
- Heat usage (MWh)
|
||||
- Volume usage (m3)
|
||||
|
||||
To be compatible with the Home Assistant energy units of measurement, heat usage is converted to MWh, from usage in GJ, which is supplied by the device, using a conversion factor: 1 GJ = 0.277778 MWh.
|
||||
|
||||
Further data that is read from the device is added as diagnostic entities:
|
||||
|
||||
- Heat usage measured in GJ, as is read from the device before conversion
|
||||
- Ownership number
|
||||
- Volume previous year (m3)
|
||||
- Heat previous year (MWh)
|
||||
- Error number
|
||||
- Device number
|
||||
- Measurement period minutes
|
||||
- Power max (kW)
|
||||
- Power max previous year (kW)
|
||||
- Flow rate max (m3ph)
|
||||
- Flow rate max previous year (m3ph)
|
||||
- Flow temperature max (°C)
|
||||
- Return temperature max (°C)
|
||||
- Flow temperature max previous year (°C)
|
||||
- Return temperature max previous year (°C)
|
||||
- Operating hours
|
||||
- Fault hours
|
||||
- Fault hours previous year
|
||||
- Yearly set day
|
||||
- Monthly set day
|
||||
- Meter date time
|
||||
- Measuring range (m3ph)
|
||||
- Settings and firmware
|
||||
- Flow hours
|
||||
|
||||
## Energy Dashboard
|
||||
|
||||
Either heat usage or volume usage can be used as "Gas" on the energy dashboard. If you want to supply a price per MWh, make sure to apply the conversion factor first.
|
||||
|
||||
## Polling the device
|
||||
|
||||
Polling is by default done only once per day (and once right after adding the integration). Every time the Heat Meter values are read, battery time of the device will (supposedly) go down by about 30 minutes.
|
||||
|
||||
For detailed control on polling and time of polling, consider disabling polling in the integration panel and poll manually. For instructions, see below.
|
||||
|
||||
### Polling manually (optional)
|
||||
|
||||
For detailed control on when the device is polled, disable the default polling for this integration and create an automation that will update one of the entities (the other entities will be updated as well)
|
||||
|
||||
If you're comfortable with YAML, this game could be used:
|
||||
|
||||
```yaml
|
||||
alias: "Heat Meter manual update"
|
||||
trigger:
|
||||
- platform: time
|
||||
at: "23:30:00"
|
||||
action:
|
||||
- service: homeassistant.update_entity
|
||||
target:
|
||||
entity_id: sensor.heat_meter_heat_usage_gj
|
||||
```
|
||||
@ -2,6 +2,7 @@
|
||||
title: LIFX
|
||||
description: Instructions on how to integrate LIFX into Home Assistant.
|
||||
ha_category:
|
||||
- Button
|
||||
- Light
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.81
|
||||
@ -9,6 +10,7 @@ ha_config_flow: true
|
||||
ha_domain: lifx
|
||||
ha_homekit: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- light
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
@ -114,6 +116,18 @@ Run an effect that does nothing, thereby stopping any other effect that might be
|
||||
| ---------------------- | ----------- |
|
||||
| `entity_id` | String or list of strings that point at `entity_id`s of lights. Use `entity_id: all` to target all.
|
||||
|
||||
## Buttons
|
||||
|
||||
The LIFX button platform creates two buttons for each LIFX device.
|
||||
|
||||
### Identify Button
|
||||
|
||||
The Identify button will flash the bulb three times at maximum brightness then return the bulb to the state it was in prior. Successful identification requires the bulb to be powered on and already configured in Home Assistant.
|
||||
|
||||
### Restart Button
|
||||
|
||||
The Restart button triggers the bulb to restart in exactly the same way as a physical power cycle, which makes it ideal for triggering a new DHCP request from the bulb.
|
||||
|
||||
## HomeKit Accessory Protocol
|
||||
|
||||
Most LIFX devices support Apple HomeKit via the HomeKit Accessory Protocol (HAP). If a LIFX device has not already been added to HomeKit natively using an Apple iOS or macOS device, it can be paired with Home Assistant using via the [HomeKit Controller](/integrations/homekit_controller) integration which uses HAP.
|
||||
|
||||
@ -720,13 +720,18 @@ state_topic:
|
||||
required: false
|
||||
type: string
|
||||
supported_color_modes:
|
||||
description: A list of color modes supported by the list. This is required if `color_mode` is `True`. Possible color modes are `onoff`, `brightness`, `color_temp`, `hs`, `xy`, `rgb`, `rgbw`, `rgbww`.
|
||||
description: A list of color modes supported by the list. This is required if `color_mode` is `True`. Possible color modes are `onoff`, `brightness`, `color_temp`, `hs`, `xy`, `rgb`, `rgbw`, `rgbww`, `white`.
|
||||
required: false
|
||||
type: list
|
||||
unique_id:
|
||||
description: An ID that uniquely identifies this light. If two lights have the same unique ID, Home Assistant will raise an exception.
|
||||
required: false
|
||||
type: string
|
||||
white_scale:
|
||||
description: "Defines the maximum white level (i.e., 100%) of the MQTT device. This is used when setting the light to white mode."
|
||||
required: false
|
||||
type: integer
|
||||
default: 255
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.38
|
||||
ha_domain: rflink
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/en/21-rflink-). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First, you have to set up your [RFLink hub](/integrations/rflink/).
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: OpenWRT (luci)
|
||||
description: Instructions on how to integrate OpenWRT routers into Home Assistant.
|
||||
title: OpenWrt (luci)
|
||||
description: Instructions on how to integrate OpenWrt routers into Home Assistant.
|
||||
ha_category:
|
||||
- Presence Detection
|
||||
ha_iot_class: Local Polling
|
||||
@ -15,7 +15,7 @@ ha_integration_type: integration
|
||||
|
||||
This is a presence detection scanner for OpenWrt using [luci](https://openwrt.org/docs/techref/luci).
|
||||
|
||||
Before this scanner can be used you have to install the luci RPC package on OpenWRT:
|
||||
Before this scanner can be used you have to install the luci RPC package on OpenWrt:
|
||||
|
||||
```bash
|
||||
# opkg install luci-mod-rpc
|
||||
|
||||
@ -35,6 +35,7 @@ Additionally the following brands have been reported to also work with this inte
|
||||
- [Martec](https://www.martec.co.nz/)
|
||||
- [Motion Blinds](https://motionblinds.com/)
|
||||
- [Raven Rock MFG](https://www.ravenrockmfg.com/)
|
||||
- [ScreenAway](https://www.screenaway.com.au/)
|
||||
- [Smart Blinds](https://www.smartblinds.nl/)
|
||||
- [Smart Home](https://www.smart-home.hu)
|
||||
- [Uprise Smart Shades](http://uprisesmartshades.com)
|
||||
|
||||
@ -43,7 +43,7 @@ Button entity to restart the router.
|
||||
|
||||
### Update entity
|
||||
|
||||
Update entity to vieuw current and latest firmware version, and install the latest firmware of the router.
|
||||
Update entity to view current and latest firmware version, and install the latest firmware of the router.
|
||||
|
||||
### Traffic meter data
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ ha_codeowners:
|
||||
- '@bieniu'
|
||||
ha_domain: nextdns
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- diagnostics
|
||||
- sensor
|
||||
|
||||
@ -4,6 +4,7 @@ description: Instructions on how to integrate exchange rates from https://openex
|
||||
ha_category:
|
||||
- Finance
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_release: 0.23
|
||||
ha_domain: openexchangerates
|
||||
ha_platforms:
|
||||
@ -11,37 +12,8 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `openexchangerates` sensor will show you the current exchange rate from [Open Exchange Rates](https://openexchangerates.org) that provides realtime exchange rates for [170 currencies](https://openexchangerates.org/currencies). The free account is limited to only USD as a base currency, allows 1000 requests per month, and updates every hour.
|
||||
The Open Exchange Rates integration will show you the current exchange rate from [Open Exchange Rates](https://openexchangerates.org) that provides real-time exchange rates for [170 currencies](https://openexchangerates.org/currencies). The free account is limited to only USD as a base currency, allows 1000 requests per month, and updates every hour.
|
||||
|
||||
Obtain your API key [here](https://openexchangerates.org/signup)
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: openexchangerates
|
||||
api_key: YOUR_API_KEY
|
||||
quote: EUR
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: The name of the sensor.
|
||||
required: false
|
||||
type: string
|
||||
default: Exchange Rate Sensor
|
||||
api_key:
|
||||
description: "The API Key for [Open Exchange Rates](https://openexchangerates.org)."
|
||||
required: true
|
||||
type: string
|
||||
quote:
|
||||
description: The symbol of the quote or target currency.
|
||||
required: true
|
||||
type: string
|
||||
base:
|
||||
description: The symbol of the base currency. Note that, changing the API `base` currency is not part of the freemium API plan.
|
||||
required: false
|
||||
type: string
|
||||
default: USD
|
||||
{% endconfiguration %}
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -31,20 +31,6 @@ trained medical professional.
|
||||
To generate an API key,
|
||||
[simply log in to the OpenUV website](https://www.openuv.io/auth/google).
|
||||
|
||||
<div class='note warning'>
|
||||
Beginning February 1, 2019, the "Limited" plan (which is what new users are
|
||||
given by default) is limited to 50 API requests per day. Because different
|
||||
API plans and locations will have different requirements, the `openuv`
|
||||
component does not automatically query the API for new data after it initially
|
||||
loads. To request new data, the `update_data` service may be used.
|
||||
</div>
|
||||
|
||||
<div class='note warning'>
|
||||
Each use of the `update_data` service will consume 2 API calls from the daily quota
|
||||
(since it performs the same tasks as back-to-back calls of the `update_uv_index_data` and
|
||||
the `update_protection_data` services).
|
||||
</div>
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Sensors
|
||||
@ -56,6 +42,44 @@ the `update_protection_data` services).
|
||||
| Current UV Level | Sensor | UV Level (as literal) |
|
||||
| Max UV Index | Sensor | max UV Index for the day (at solar noon) |
|
||||
| Protection Window | Binary Sensor | whether sunblock protection should be used |
|
||||
| Skin Type 1 Safe Exposure Time | Sensor | the amount of time [Fitzpatrick skin type 1](https://en.wikipedia.org/wiki/Fitzpatrick_scale) can be in the sun unprotected |
|
||||
| Skin Type 2 Safe Exposure Time | Sensor | the amount of time [Fitzpatrick skin type 2](https://en.wikipedia.org/wiki/Fitzpatrick_scale) can be in the sun unprotected |
|
||||
| Skin Type 3 Safe Exposure Time | Sensor | the amount of time [Fitzpatrick skin type 3](https://en.wikipedia.org/wiki/Fitzpatrick_scale) can be in the sun unprotected |
|
||||
| Skin Type 4 Safe Exposure Time | Sensor | the amount of time [Fitzpatrick skin type 4](https://en.wikipedia.org/wiki/Fitzpatrick_scale) can be in the sun unprotected |
|
||||
| Skin Type 5 Safe Exposure Time | Sensor | the amount of time [Fitzpatrick skin type 5](https://en.wikipedia.org/wiki/Fitzpatrick_scale) can be in the sun unprotected |
|
||||
| Skin Type 6 Safe Exposure Time | Sensor | the amount of time [Fitzpatrick skin type 6](https://en.wikipedia.org/wiki/Fitzpatrick_scale) can be in the sun unprotected |
|
||||
|
||||
## Updating Data
|
||||
|
||||
<div class='note warning'>
|
||||
OpenUV does _not_ automatically update data for its entities! Users must manually
|
||||
update data via the `homeassistant.update_entity` service.
|
||||
</div>
|
||||
|
||||
Beginning February 1, 2019, the "Limited" plan (which is what new users are given by
|
||||
default) is limited to 50 API requests per day. Because different API plans and
|
||||
locations will have different requirements, the `openuv` component does not automatically
|
||||
query the API for new data after it initially loads. To request new data, the
|
||||
`homeassistant.update_entity` service should be used.
|
||||
|
||||
Note that in the case of UV and ozone data, selecting any one of:
|
||||
|
||||
* Current Ozone Level
|
||||
* Current UV Index
|
||||
* Current UV Level
|
||||
* Max UV Index
|
||||
* Skin Type 1 Safe Exposure Time
|
||||
* Skin Type 2 Safe Exposure Time
|
||||
* Skin Type 3 Safe Exposure Time
|
||||
* Skin Type 4 Safe Exposure Time
|
||||
* Skin Type 5 Safe Exposure Time
|
||||
* Skin Type 6 Safe Exposure Time
|
||||
|
||||
...as the target for the `homeassistant.update_entity` service will update the data for
|
||||
_all_ of these entities.
|
||||
|
||||
To protect against possible API call waste, all calls to `homeassistant.update_entity`
|
||||
that reference an OpenUV entity are throttled to a minimum of 15 minutes between calls.
|
||||
|
||||
### Protection Window
|
||||
|
||||
@ -64,81 +88,20 @@ The Protection Window binary sensor will be `on` when sunblock protection should
|
||||
By default, this occurs anytime the UV index is above 3.5. This behavior can be
|
||||
configured via the config entry options within the UI. Two parameters are given:
|
||||
|
||||
* `Starting UV index for the protection window`: the UV index that, when passed, indicates protection should be utilized
|
||||
* `Ending UV index for the protection window`: the UV index that, when passed, indicates protection is no longer required
|
||||
|
||||
### The Fitzpatrick Scale
|
||||
|
||||
The approximate number of minutes of a particular skin type can be exposed to
|
||||
the sun before burning/tanning starts is based on the
|
||||
[Fitzpatrick scale](https://en.wikipedia.org/wiki/Fitzpatrick_scale).
|
||||
|
||||
OpenUV integration provide sensors for safe exposure time (in minutes) based on skin type:
|
||||
|
||||
- Skin Type 1 Safe Exposure Time
|
||||
- Skin Type 2 Safe Exposure Time
|
||||
- Skin Type 3 Safe Exposure Time
|
||||
- Skin Type 4 Safe Exposure Time
|
||||
- Skin Type 5 Safe Exposure Time
|
||||
- Skin Type 6 Safe Exposure Time
|
||||
|
||||
## Services
|
||||
|
||||
### `openuv.update_data`
|
||||
|
||||
Perform an on-demand update of OpenUV data.
|
||||
|
||||
### `openuv.update_uv_index_data`
|
||||
|
||||
Perform an on-demand update of OpenUV sensor data including current UV index, but not the `uv_protection_window`, saving an API call over `update_data`.
|
||||
|
||||
### `openuv.update_protection_data`
|
||||
|
||||
Perform an on-demand update of OpenUV `uv_protection_window` data, but not the sensors, saving an API call.
|
||||
* `Starting UV index for the protection window`: the UV index that, when passed, indicates
|
||||
protection should be utilized
|
||||
* `Ending UV index for the protection window`: the UV index that, when passed, indicates
|
||||
protection is no longer required
|
||||
|
||||
## Examples of Updating Data
|
||||
|
||||
To perform an optimal amount of API calls you need to know the hours of daylight on the longest day of the year. If for example this is 17 hours, you can perform 2 calls around every 45 minutes without running into the 50 API call limit per day:
|
||||
Update the UV index data every 20 minutes while the sun is at least 10 degrees above the
|
||||
horizon:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: "Update OpenUV"
|
||||
trigger:
|
||||
# Time pattern of /45 will not work as expected, it will trigger on the whole hour and on the whole hour + 45 minutes.
|
||||
# Using more frequent time pattern and a condition to get the intended behavior.
|
||||
- platform: time_pattern
|
||||
minutes: "/15"
|
||||
condition:
|
||||
- condition: sun
|
||||
after: sunrise
|
||||
before: sunset
|
||||
# The last call will most likely fall before the sunset, thus leaving an UV index value not at 0 for the remaining night.
|
||||
# To fix this, we allow one more service call after the sun has set.
|
||||
before_offset: "+00:45:00"
|
||||
# We check if the last trigger has been 40 minutes or more ago so we don't run into timing issues.
|
||||
# By checking for 40 minutes or greater we ensure this is only true at the 45 minute mark.
|
||||
- condition: template
|
||||
value_template: >-
|
||||
{{
|
||||
state_attr('automation.openuv_update', 'last_triggered') == None or
|
||||
(now() - state_attr('automation.openuv_update', 'last_triggered')) >= timedelta(hours = 0, minutes = 40)
|
||||
}}
|
||||
action:
|
||||
- service: openuv.update_data
|
||||
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Update the UV index data every 20 minutes while the sun is at least 10 degrees above the horizon:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: "Update OpenUV every 20 minutes while the sun is at least 10 degrees above the horizon"
|
||||
trigger:
|
||||
platform: time_pattern
|
||||
minutes: "/20"
|
||||
@ -148,33 +111,66 @@ automation:
|
||||
value_template: "{{ state.attributes.elevation }}"
|
||||
above: 10
|
||||
action:
|
||||
service: openuv.update_uv_index_data
|
||||
service: homeassistant.update_entity
|
||||
target:
|
||||
entity_id: sensor.LATITUDE_LONGITUDE_current_uv_index
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Update the protection window once a day:
|
||||
Update the protection window once a day at 12:00pm:
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: "Update OpenUV protection window once a day"
|
||||
- alias: "Update OpenUV"
|
||||
trigger:
|
||||
platform: time
|
||||
at: "02:12:00"
|
||||
at: "12:00:00"
|
||||
action:
|
||||
service: openuv.update_protection_data
|
||||
service: homeassistant.update_entity
|
||||
target:
|
||||
entity_id: binary_sensor.LATITUDE_LONGITUDE_protection_window
|
||||
```
|
||||
|
||||
Another method (useful when monitoring locations other than the Home Assistant latitude
|
||||
and longitude, in locations where there is a large amount of sunlight per day,
|
||||
etc.) might be to simply query the API less often:
|
||||
To perform an optimal amount of API calls in locations where the amount of daylight
|
||||
varies, you need to know the total hours of daylight on the longest day of the year. If,
|
||||
for example, this is 17 hours, you can perform 2 calls around every 45 minutes without
|
||||
running into the 50 API call limit per day:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
automation:
|
||||
- alias: "Update OpenUV every hour (48 of 50 calls per day)"
|
||||
- alias: "Update OpenUV"
|
||||
trigger:
|
||||
platform: time_pattern
|
||||
hours: "*"
|
||||
# Time pattern of /45 will not work as expected, as it will sometimes be true
|
||||
# twice per hour (on the whole hour and on the whole hour + 45 minutes); use a
|
||||
# more frequent time pattern and a condition to get the intended behavior:
|
||||
- platform: time_pattern
|
||||
minutes: "/15"
|
||||
condition:
|
||||
- condition: sun
|
||||
after: sunrise
|
||||
before: sunset
|
||||
# The last call will most likely fall before the sunset, leaving the UV index at
|
||||
# something other than 0 for the remainder of the night; to fix this, we allow
|
||||
# one more service call after the sun has set:
|
||||
before_offset: "+00:45:00"
|
||||
- condition: template
|
||||
# We check if the last trigger has been 40 minutes or more ago so we don't run
|
||||
# into timing issues; by checking for 40 minutes or greater, we ensure this is
|
||||
# only true at the 45 minute mark:
|
||||
value_template: >-
|
||||
{{
|
||||
state_attr('automation.update_openuv', 'last_triggered') == None
|
||||
or (
|
||||
now() - state_attr('automation.update_openuv', 'last_triggered')
|
||||
) >= timedelta(hours = 0, minutes = 40)
|
||||
}}
|
||||
action:
|
||||
service: openuv.update_data
|
||||
service: homeassistant.update_entity
|
||||
target:
|
||||
entity_id:
|
||||
# Update both UV and protection window data:
|
||||
- binary_sensor.LATITUDE_LONGITUDE_protection_window
|
||||
- sensor.LATITUDE_LONGITUDE_current_uv_index
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@ -49,6 +49,14 @@ See per phase what your voltage, current and power consumption/production is.
|
||||
- Power consumed phases L1/2/3 (W)
|
||||
- Power Produced phases L1/2/3 (W)
|
||||
|
||||
### WaterMeter
|
||||
|
||||
See how much water you consume per day, in total and the number of counted pulses.
|
||||
|
||||
- Water Consumption - day (liters)
|
||||
- Water Consumption - total (m3)
|
||||
- Pulse Count
|
||||
|
||||
### Settings
|
||||
|
||||
You can use the rates set in P1 Monitor for your calculations in Home Assistant.
|
||||
|
||||
@ -4,11 +4,14 @@ description: Instructions on how to add Pushover notifications to Home Assistant
|
||||
ha_category:
|
||||
- Notifications
|
||||
ha_release: pre 0.7
|
||||
ha_config_flow: true
|
||||
ha_iot_class: Cloud Push
|
||||
ha_domain: pushover
|
||||
ha_platforms:
|
||||
- notify
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@engrbm87'
|
||||
---
|
||||
|
||||
The [Pushover service](https://pushover.net/) is a platform for the notify component. This allows integrations to send messages to the user using Pushover.
|
||||
@ -17,32 +20,7 @@ The [Pushover service](https://pushover.net/) is a platform for the notify compo
|
||||
|
||||
In order to get an API key you need to [register an application](https://pushover.net/apps/clone/home_assistant) on the Pushover website. Your Pushover user key can be found on the [Pushover dashboard](https://pushover.net/dashboard).
|
||||
|
||||
To use Pushover notifications, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- name: NOTIFIER_NAME
|
||||
platform: pushover
|
||||
api_key: YOUR_API_KEY
|
||||
user_key: YOUR_USER_KEY
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`.
|
||||
required: false
|
||||
default: notify
|
||||
type: string
|
||||
api_key:
|
||||
description: Your API key.
|
||||
required: true
|
||||
type: string
|
||||
user_key:
|
||||
description: Your user key for Pushover.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
Example Automation:
|
||||
|
||||
|
||||
31
source/_integrations/qingping.markdown
Normal file
31
source/_integrations/qingping.markdown
Normal file
@ -0,0 +1,31 @@
|
||||
---
|
||||
title: Qingping
|
||||
description: Instructions on how to integrate Qingping devices into Home Assistant.
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
ha_bluetooth: true
|
||||
ha_release: 2022.9
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@bdraco'
|
||||
ha_domain: qingping
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
Integrates [Qingping](https://qingping.co/) devices into Home Assistant.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
The Qingping integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional.
|
||||
|
||||
## Supported devices
|
||||
|
||||
- [Air Monitor Lite](https://www.qingping.co/air-monitor-lite/overview) (CGDN1)
|
||||
- [Alarm Clock](https://www.qingping.co/bluetooth-alarm-clock/overview) (CGD1)
|
||||
- [BT Clock Lite](https://www.qingping.co/bluetooth-clock/overview) (CGC1)
|
||||
- [Motion & Ambient Light Sensor](https://www.qingping.co/motion-light-sensor/overview) (CGPR1)
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Irrigation
|
||||
- Sensor
|
||||
- Switch
|
||||
- Update
|
||||
ha_release: 0.69
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
@ -14,9 +15,11 @@ ha_codeowners:
|
||||
ha_domain: rainmachine
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- diagnostics
|
||||
- sensor
|
||||
- switch
|
||||
- update
|
||||
ha_zeroconf: true
|
||||
ha_homekit: true
|
||||
ha_integration_type: integration
|
||||
@ -27,6 +30,7 @@ The RainMachine integration is the main integration to integrate all platforms r
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Binary Sensor
|
||||
- Button
|
||||
- Sensor
|
||||
- [Switch](#switch)
|
||||
|
||||
@ -125,11 +129,7 @@ Unpause all paused watering activities.
|
||||
|
||||
Remove all watering restrictions enforced by `rainmachine.restrict_watering`.
|
||||
|
||||
## Switch
|
||||
|
||||
The `rainmachine` switch platform allows you to control programs and zones within a [RainMachine smart Wi-Fi sprinkler controller](https://www.rainmachine.com/).
|
||||
|
||||
### Controlling Your Device
|
||||
## Controlling Your Device
|
||||
|
||||
After Home Assistant loads, new switches will be added for every enabled program and zone. These work as expected:
|
||||
|
||||
@ -138,4 +138,13 @@ After Home Assistant loads, new switches will be added for every enabled program
|
||||
|
||||
Programs and zones are linked. While a program is running, you will see both the program and zone switches turned on; turning either one off will turn the other one off (just like in the web app).
|
||||
|
||||
## Entity Availability
|
||||
|
||||
Many RainMachine entities are enabled by default. Others, like those related to flow sensors, are disabled by default if they only apply to some controllers. You can view all entities for a controller and enable/disable them as appropriate in the Device screen for your RainMachine controller.
|
||||
|
||||
[wnum reference]: https://github.com/sprinkler/rainmachine-developer-resources/blob/d47e1ad59dee59e34094ad41636ae289275eb973/sdk-parsers/RMDataFramework/rmWeatherData.py#L13
|
||||
|
||||
## Firmware Updates
|
||||
|
||||
The integration has an [update entity](/integrations/update/) that provides information on the latest available RainMachine firmware version. The firmware update can be triggered and installed onto your RainMachine controller
|
||||
directly from Home Assistant.
|
||||
|
||||
@ -34,7 +34,7 @@ in the repairs dashboard is shown in the sidebar on the "Settings" menu item.
|
||||
|
||||
<p class='img'>
|
||||
<img class="no-shadow" src='/images/integrations/repairs/number-of-repairs.png' alt='Screenshot showing the number of updates and repairs pending on the settings menu item in the sidebar'>
|
||||
The settings menu item shows the number of updatesd and repairable issues pending.
|
||||
The settings menu item shows the number of pending updates and repairable issues.
|
||||
</p>
|
||||
|
||||
Navigate to {% my repairs title="**Settings** -> **System** -> **Repairs**" %}
|
||||
|
||||
@ -17,7 +17,7 @@ ha_codeowners:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink Gateway is an Arduino Mega firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/en/21-rflink-). RFLink Gateway is an Arduino Mega firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
The 433 MHz spectrum is used by many manufacturers mostly using their own protocol/standard and includes devices like: light switches, blinds, weather stations, alarms and various other sensors.
|
||||
|
||||
|
||||
@ -63,3 +63,18 @@ docker exec -it CONTAINER_NAME_OR_ID python -c 'import roombapy.entry_points; ro
|
||||
The command to retrieve the credentials does not need any additional software to be installed because it uses the built-in [roombapy](https://github.com/pschmitt/roombapy) package and [password](https://github.com/pschmitt/roombapy/blob/1.6.1/roomba/entry_points.py#L20) function deployed with Home Assistant.
|
||||
|
||||
</div>
|
||||
|
||||
#### Retrieving credentials from the cloud with dorita980
|
||||
|
||||
The underlying Python library is currently unable to retrieve the credentials from some newer models (e.g. J7). See [this issue](https://github.com/pschmitt/roombapy/issues/97) for details. Luckily, the password can be retrieved from the cloud using a tool provided by the [dorita980](https://github.com/koalazak/dorita980) library. Follow [these instructions](https://github.com/koalazak/dorita980#how-to-get-your-usernameblid-and-password) to do this, you should receive output of the form:
|
||||
|
||||
```shell
|
||||
Found 1 robot(s)!
|
||||
Robot "RoombaJ7" (sku: j715800 SoftwareVer: sapphire+22.21.1+2022-06-02-570490a425b+Firmware-Production+70):
|
||||
BLID=> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|
||||
Password=> XXXXXXXXXXXXXXXXXXXXXXXXXXXXX <= Yes, all this string.
|
||||
|
||||
Use this credentials in dorita980 lib :)
|
||||
```
|
||||
|
||||
Copy the password (everything between `=>` and `<=`, not including leading and trailing whitespace) into the Home Assistant password dialog.
|
||||
|
||||
110
source/_integrations/schedule.markdown
Normal file
110
source/_integrations/schedule.markdown
Normal file
@ -0,0 +1,110 @@
|
||||
---
|
||||
title: Schedule
|
||||
description: Instructions on how use make weekly schedule in Home Assistant.
|
||||
ha_category:
|
||||
- Automation
|
||||
- Helper
|
||||
ha_release: 2022.9
|
||||
ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: schedule
|
||||
ha_integration_type: helper
|
||||
---
|
||||
|
||||
The schedule integration provides a way to create a weekly schedule in
|
||||
Home Assistant that can be used to trigger or make decisions in your
|
||||
automations and scripts.
|
||||
|
||||
The preferred way to configure a schedule is via the user interface at
|
||||
**Settings** -> **Devices & Services** -> **Helpers**. Click the add button
|
||||
and then choose the **Schedule** option, or click the My button below.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
To be able to add **Helpers** via the user interface you should
|
||||
have `default_config:` in your `configuration.yaml`, it should already
|
||||
be there by default unless you removed it.
|
||||
|
||||
If you removed `default_config:` from your configuration,
|
||||
you must add it back or, alternatively, `schedule:` to your
|
||||
`configuration.yaml` first, before you can create them via the UI.
|
||||
|
||||
Alternatively, a schedule can also be created and configured via YAML
|
||||
configuration. For example:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
schedule:
|
||||
thermostat_schedule:
|
||||
name: "Thermostat schedule"
|
||||
monday:
|
||||
- from: "17:00:00"
|
||||
to: "21:00:00"
|
||||
tuesday:
|
||||
- from: "17:00:00"
|
||||
to: "21:00:00"
|
||||
wednesday:
|
||||
- from: "17:00:00"
|
||||
to: "21:00:00"
|
||||
thursday:
|
||||
- from: "17:00:00"
|
||||
to: "21:00:00"
|
||||
friday:
|
||||
- from: "17:00:00"
|
||||
to: "23:00:00"
|
||||
saturday:
|
||||
- from: "07:00:00"
|
||||
to: "10:00:00"
|
||||
- from: "16:00:00"
|
||||
to: "23:00:00"
|
||||
sunday:
|
||||
- from: "07:00:00"
|
||||
to: "21:00:00"
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
schedule:
|
||||
description: Alias for the schedule. Multiple entries are allowed.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: Friendly name of the schedule.
|
||||
required: true
|
||||
type: string
|
||||
icon:
|
||||
description: Icon to display in the frontend for this schedule.
|
||||
required: false
|
||||
type: icon
|
||||
"monday|tuesday|wednesday|thursday|friday|saturday|sunday":
|
||||
description: A schedule for each day of the week.
|
||||
required: false
|
||||
required: true
|
||||
type: list
|
||||
keys:
|
||||
from:
|
||||
description: The start time to mark the schedule as active/on.
|
||||
required: true
|
||||
type: time
|
||||
to:
|
||||
description: The end time to mark as inactive/off again.
|
||||
required: true
|
||||
type: time
|
||||
{% endconfiguration %}
|
||||
|
||||
### Attributes
|
||||
|
||||
A schedule entity's state exports attributes that can be useful in
|
||||
automations and templates.
|
||||
|
||||
| Attribute | Description |
|
||||
| ----- | ----- |
|
||||
| `next_event` | A datetime object containing the next time the schedule is going to change state. |
|
||||
### Services
|
||||
|
||||
Available service: `schedule.reload`.
|
||||
|
||||
#### schedule.reload
|
||||
|
||||
`schedule.reload` service allows one to reload the schedule's configuration without restarting Home Assistant itself.
|
||||
@ -9,7 +9,7 @@ ha_release: 0.38
|
||||
ha_domain: rflink
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/en/21-rflink-). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -17,6 +17,10 @@ ha_integration_type: integration
|
||||
|
||||
Integrates [SensorPush](https://www.sensorpush.com/) devices into Home Assistant.
|
||||
|
||||
## Activation is required
|
||||
|
||||
Sensor entities (temperature, humidity, barometric pressure) will not be available to Home Assistant until you have activated the device with the SensorPush app on iOS or Android.
|
||||
|
||||
## Supported devices
|
||||
|
||||
- [HT.w Water-Resistant Temperature / Humidity Smart Sensor](https://www.sensorpush.com/products/p/ht-w)
|
||||
|
||||
@ -62,7 +62,7 @@ The following characteristics are supported for `sensor` source sensors:
|
||||
| `total` | The sum of all source sensor measurements within the given time and sampling size limits.
|
||||
| `value_max` | The biggest value among the number of measurements.
|
||||
| `value_min` | The smallest value among the number of measurements.
|
||||
| `variance` | The [variance](https://en.wikipedia.org/wiki/Standard_deviation) of an assumed normal distribution from all measurements.
|
||||
| `variance` | The [variance](https://en.wikipedia.org/wiki/Variance) of an assumed normal distribution from all measurements.
|
||||
|
||||
### Binary Source Sensor
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.38
|
||||
ha_domain: rflink
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/en/21-rflink-). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First, you have to set up your [RFLink hub](/integrations/rflink/).
|
||||
|
||||
|
||||
@ -36,10 +36,16 @@ things like locks or garage doors.
|
||||
Using the Switch as X integration, you can convert those switches into the
|
||||
entity types that best matches your use case.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
{% include integrations/config_flow.md name="Change device type of a switch" %}
|
||||
{% configuration_basic %}
|
||||
Switch entity:
|
||||
description: The switch entity you want to convert into something else.
|
||||
Type:
|
||||
description: The type of entity you want the switch to become.
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Switch as X from the existing entity
|
||||
|
||||
Where compatible, Switch as X will appear on entity properties. A list of entities can be found in {% my entities title="Settings -> Devices & Services -> Entities" %}.
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ ha_zeroconf: true
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
[System Bridge](https://system-bridge.timmo.dev) is an application that runs on your local machine to share system information via its API/WebSocket. You can also send commands to be to the device such as opening a URL or sending keyboard keypresses.
|
||||
[System Bridge](https://system-bridge.timmo.dev) is an application that runs on your local machine to share system information via its API/WebSocket. You can also send commands to the device such as opening a URL or sending keyboard keypresses.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -80,6 +80,10 @@ These sensors are also available, but are not enabled by default:
|
||||
| GPU Power Usage | GPU power usage |
|
||||
| GPU Temperature | The current temperature of the GPU |
|
||||
|
||||
## Media Source
|
||||
|
||||
This integration is available as a media source to use with the media browser integration. You can browse and view media from your system to media players such as your web browser and other supported media players.
|
||||
|
||||
## Services
|
||||
|
||||
### Service `system_bridge.open_path`
|
||||
|
||||
@ -387,10 +387,14 @@ action:
|
||||
service: notify.NOTIFIER_NAME
|
||||
data:
|
||||
title: "*Send a message*"
|
||||
message: "That's an example that sends a message with message_tag and disable_notification."
|
||||
message: |-
|
||||
That's an example that sends a message with message_tag, disable_notification and disable_web_page_preview.
|
||||
<a href="https://www.home-assistant.io/">HA site</a>
|
||||
data:
|
||||
parse_mode: html
|
||||
message_tag: "example_tag"
|
||||
disable_notification: True
|
||||
disable_web_page_preview: True
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -403,6 +407,10 @@ disable_notification:
|
||||
required: false
|
||||
default: false
|
||||
type: boolean
|
||||
disable_web_page_preview:
|
||||
description: True/false to display a webpage preview.
|
||||
default: false
|
||||
type: boolean
|
||||
message_tag:
|
||||
description: Tag for sent message.
|
||||
required: false
|
||||
|
||||
@ -253,7 +253,7 @@ Remove the bot from the chat group where it was added.
|
||||
|
||||
## Telegram notification platform
|
||||
|
||||
The [`telegram` notification platform](/integrations/telegram) requires the `telegram_bot` integration to work with, and it's designed to generate a customized shortcut (`notify.USERNAME`) to send notifications (messages, photos, documents and locations) to a particular `chat_id` with the old syntax, allowing backward compatibility. The data attributes `parse_mode`, `disable_notification` and `message_tag` are also supported.
|
||||
The [`telegram` notification platform](/integrations/telegram) requires the `telegram_bot` integration to work with, and it's designed to generate a customized shortcut (`notify.USERNAME`) to send notifications (messages, photos, documents and locations) to a particular `chat_id` with the old syntax, allowing backward compatibility. The data attributes `parse_mode`, `disable_notification`, `message_tag` and `disable_web_page_preview` are also supported.
|
||||
|
||||
The required YAML configuration now reduces to:
|
||||
|
||||
@ -556,3 +556,16 @@ action:
|
||||
data:
|
||||
message_tag: "example_tag"
|
||||
```
|
||||
|
||||
## Example: send_message with disabled webpage preview:
|
||||
|
||||
```yaml
|
||||
action:
|
||||
- service: notify.telegram
|
||||
data:
|
||||
message: >-
|
||||
<a href="https://www.home-assistant.io/">HA site</a>
|
||||
data:
|
||||
parse_mode: html
|
||||
disable_web_page_preview: true
|
||||
```
|
||||
|
||||
@ -11,11 +11,11 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](https://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier](https://www.transportapi.com/benefits/) allows 30,000 requests a month, which is sufficient for a single sensor refreshing every 87 seconds.
|
||||
The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](https://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier]([https://www.transportapi.com/benefits/](https://www.transportapi.com/blog/2022/08/introducing-the-home-use-plan-for-transportapi/)) allows 30 requests a day, which is sufficient for a single sensor refreshing every 48 minutes.
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Additional sensors can be added but at the expense of a reduced refresh rate. 2 sensors can be updated every 2*87 = 174 seconds, and so on. Calculating and setting this rate is automatically handles by the integration.
|
||||
Additional sensors can be added but at the expense of a reduced refresh rate. 2 sensors can be updated every 2*48 = 96 minutes, and so on. Calculating and setting this rate is automatically handles by the integration.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -14,10 +14,12 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The Ukraine Alarm integration uses the siren.pp.ua API - public wrapper for [Ukraine Alarm](https://www.ukrainealarm.com/) web service to offer air-raid siren notifications. The integration will create 4 binary sensors for your selected region in Ukraine:
|
||||
The Ukraine Alarm integration uses the siren.pp.ua API - public wrapper for [Ukraine Alarm](https://www.ukrainealarm.com/) web service to offer air-raid siren notifications. The integration will create 6 binary sensors for your selected region in Ukraine:
|
||||
|
||||
- Air
|
||||
- Artillery
|
||||
- Chemical
|
||||
- Nuclear
|
||||
- Urban Fights
|
||||
- Unknown
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ ha_category:
|
||||
- Light
|
||||
- Lock
|
||||
- Media Player
|
||||
- Media Source
|
||||
- Number
|
||||
- Select
|
||||
- Sensor
|
||||
@ -116,7 +117,7 @@ check that this is done. To check and enable the feature:
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Features
|
||||
## Device Support
|
||||
|
||||
All known UniFi Protect devices should be supported. Each UniFi Protect device will get a variety of entities added for
|
||||
each of the different entity platforms.
|
||||
@ -212,6 +213,35 @@ Your main UniFi Protect NVR device also gets a number of diagnostics sensors tha
|
||||
* **Disk Health**: Each disk installed in your NVR will have a disk health sensor. These are simple good/bad sensors and the order is not promised to match the order in UniFi OS. Disk model number is provided as a state attribute though to help map sensor to disk.
|
||||
* **Utilization and Storage Sensors**: Several other sensors are also added for uptime, hardware utilization, and distribution details of the video on disk.
|
||||
|
||||
## Media Source
|
||||
|
||||
A media source is provided for your UniFi Protect cameras so you can fetch video clips and event thumbnails.
|
||||
|
||||
### Media Browser
|
||||
|
||||
The media source is split into 5 folders/levels:
|
||||
|
||||
1. NVR Console Selector - only appears if you have more then one Protect NVR Console. Allows you to select your NVR Console you want to view events for.
|
||||
2. Camera Selector - either lets you select all cameras or a specific camera to view events for.
|
||||
3. Event Selector - either lets you select all events or a specific event type to view events for.
|
||||
4. Time Selector - filters events for a given time range:
|
||||
* Last 24 Hours
|
||||
* Last 7 Days
|
||||
* Last 30 Days
|
||||
* By Month since start of recording - selecting a month lets you either view the whole month or a specific date
|
||||
5. Event Selector - lets you select the specific event for playback
|
||||
|
||||
Since the media browser does not have any pagination or filtering, all of the events must be loaded into memory. As a result, the number of events loaded at once is truncated to 10,000 by default. The number of events will be listed at "10000 (TRUNCATED)" if the event count was truncated. You can raise or lower the limit of the number of events that can be loaded using the Config Entry Options.
|
||||
|
||||
### Media Identifiers
|
||||
|
||||
Below are the accepted identifiers to resolve media. Since events do not necessarily map to any Home Assistant entity, all IDs are in reference to the UniFi Protect IDs, not Home Assistant ones.
|
||||
|
||||
| Identifier Format | Description |
|
||||
| -------------------------------- | ---------------------------------- |
|
||||
| `{nvr_id}:event:{event_id}` | MP4 video clip for specific event. |
|
||||
| `{nvr_id}:eventthumb:{event_id}` | JPEG thumbnail for specific event. |
|
||||
|
||||
## Services
|
||||
|
||||
### Service unifiprotect.set_default_doorbell_text
|
||||
@ -260,6 +290,17 @@ Use to set the paired doorbell(s) with a smart chime.
|
||||
| `device_id` | No | The device ID of the Chime you want to pair or unpair doorbells to. |
|
||||
| `doorbells` | Yes | A target selector for any number of doorbells you want to pair to the chime. No value means unpair all. |
|
||||
|
||||
## Views
|
||||
|
||||
The integration provides two proxy views to proxy media content from your Home Assistant instance so you can access thumbnails and video clips from within the context of Home Assistant without having to expose your UniFi Protect NVR Console. As with the media identifiers, all IDs are UniFi Protect IDs as they may not map to specific Home Assistant entities depending on how you have configured your integration.
|
||||
|
||||
These URLs work great when trying to send notifications. Home Assistant will automatically sign the URLs and make them safe for external consumption if used in an automation or [notify service](/integrations/notify/).
|
||||
|
||||
| View URL | Description |
|
||||
| ------------------------------------------------------------ | -------------------------------------------------- |
|
||||
| `/api/unifiprotect/thumbnail/{nvr_id}/{event_id}` | Proxies a JPEG event thumbnail from UniFi Protect. |
|
||||
| `/api/unifiprotect/video/{nvr_id}/{camera_id}/{start}/{end}` | Proxies a MP4 video clip from UniFi Protect for a specific camera. Start and end must be in [ISO 8601 format](https://www.iso.org/iso-8601-date-and-time-format.html). |
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Enabling Debug Logging
|
||||
|
||||
@ -73,14 +73,6 @@ mutable:
|
||||
required: false
|
||||
default: true
|
||||
type: boolean
|
||||
name:
|
||||
description: "Make it possible to provide a name for the vehicles. Note: Use all lower case letters when inputting your VIN number."
|
||||
required: false
|
||||
type: string
|
||||
resources:
|
||||
description: A list of resources to display (defaults to all available).
|
||||
required: false
|
||||
type: list
|
||||
scandinavian_miles:
|
||||
description: If set to true, Scandinavian miles ("mil") are used for distances and fuel range.
|
||||
required: false
|
||||
@ -130,20 +122,3 @@ The list of currently available resources:
|
||||
- `tyre_pressure_rear_right_tyre_pressure`
|
||||
- `any_door_open`
|
||||
- `any_window_open`
|
||||
|
||||
## Advanced Examples
|
||||
|
||||
A more advanced example for setting the vehicle name and selecting what resources to display:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
volvooncall:
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
name:
|
||||
YOUR_VIN_NUMBER: "NEW_NAME"
|
||||
resources:
|
||||
- odometer
|
||||
- lock
|
||||
- heater
|
||||
```
|
||||
|
||||
@ -4,7 +4,9 @@ description: Instructions on how to integrate WiLight devices into Home Assistan
|
||||
ha_category:
|
||||
- Cover
|
||||
- Fan
|
||||
- Irrigation
|
||||
- Light
|
||||
- Switch
|
||||
ha_release: 0.115
|
||||
ha_config_flow: true
|
||||
ha_iot_class: Local Polling
|
||||
@ -17,6 +19,7 @@ ha_platforms:
|
||||
- cover
|
||||
- fan
|
||||
- light
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -25,8 +28,9 @@ The `wilight` integration is to integrate [WiLight](http://www.wilight.com.br) d
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Cover (WiLight model C-103).
|
||||
- Fan (WiLight model V-104).
|
||||
- Light (WiLight model I-100, I-102 and I-107).
|
||||
- [Fan](#fan) (WiLight model V-104).
|
||||
- Light (WiLight model I-100, I-102, I-107, I-110 and I-112).
|
||||
- [Irrigation](#irrigation) / Switch (WiLight model R-105).
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -34,14 +38,49 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
The `wilight` integration allows you to control your Fans from within Home Assistant.
|
||||
|
||||
### Services
|
||||
### Fan Services
|
||||
|
||||
There are several services which can be used for automations and control of the fan:
|
||||
|
||||
| Service | Description |
|
||||
| --------- | ----------- |
|
||||
| `set_percentage` | Calling this service sets the fan speed (entity_id and percentage are required parameters). Percentage must be in the range 0-100, percentage = 0 turns off the fan. There are three speed levels 33%, 66% and 100%. Adjusting to intermediate levels goes to the next higher level.
|
||||
| `set_direction` | Calling this service will set the fan direction (entity_id and direction are required parameters, and direction must be one of the following: forward or reverse). Calling this service will turn the fan on.
|
||||
| `toggle` | Calling this service will toggle the fan between on and off states (entity_id is required).
|
||||
| `turn_off` | Calling this service will turn the fan off (entity_id is required).
|
||||
| `turn_on` | Calling this service will turn the fan on and set the speed and direction to the last used ones (defaults to high and forward, entity_id is required).
|
||||
| `set_percentage` | Calling this service sets the fan speed (`entity_id` and `percentage` are required parameters). Percentage must be in the range 0-100, percentage = 0 turns off the fan. There are three speed levels 33%, 66% and 100%. Adjusting to intermediate levels goes to the next higher level.
|
||||
| `set_direction` | Calling this service will set the fan direction (`entity_id` and `direction` are required parameters, and direction must be one of the following: forward or reverse). Calling this service will turn the fan on.
|
||||
| `toggle` | Calling this service will toggle the fan between on and off states (`entity_id` is required).
|
||||
| `turn_off` | Calling this service will turn the fan off (`entity_id` is required).
|
||||
| `turn_on` | Calling this service will turn the fan on and set the speed and direction to the last used ones (defaults to high and forward, `entity_id` is required).
|
||||
|
||||
## Irrigation
|
||||
|
||||
The `wilight` integration allows you to control your Irrigation from within Home Assistant. This is exposed via switches in Home Assistant.
|
||||
There are two switch types for Irrigation: `watering switch` and `pause switch`.
|
||||
A `watering switch` can turn on and off the irrigation valve, while the `pause switch` can disable / enable the action of a `watering switch`.
|
||||
`Triggers` activate (turn on) the `watering switch` (irrigation valve) at the programmed time. The trigger can be set to run on a day of the week or only once (today).
|
||||
|
||||
### Irrigation Services
|
||||
|
||||
There are several services which can be used for automations and control of the Irrigation:
|
||||
|
||||
- For `watering switch`:
|
||||
|
||||
| Service | Description |
|
||||
| --------- | ----------- |
|
||||
| `turn_off` | Calling this service will turn the irrigation valve off (`entity_id` is required).
|
||||
| `turn_on` | Calling this service will turn the irrigation valve on (`entity_id` is required).
|
||||
| `set_watering_time` | Calling this service sets the watering time (`entity_id` and `watering_time` are required parameters), `watering_time` must be in the range 1-1800 seconds.
|
||||
| `set_trigger` | Calling this service sets the trigger_1, trigger_2, trigger_3 or trigger_4 (`entity_id`, `trigger_index` and `trigger` are required parameters), `trigger_index` must be between 1 and 4 and `trigger` must be according Trigger rules (see below).
|
||||
|
||||
- For `pause switch`:
|
||||
|
||||
| Service | Description |
|
||||
| --------- | ----------- |
|
||||
| `turn_off` | Calling this service will turn the pause switch off, enabling watering switch (`entity_id` is required).
|
||||
| `turn_on` | Calling this service will turn the pause switch on, disabling watering switch (`entity_id` is required).
|
||||
| `set_pause_time` | Calling this service sets the pause time (`entity_id` and `pause_time` are required parameters), `pause_time` must be in the range 1-24 hours.
|
||||
|
||||
Trigger rules:
|
||||
- String with 8 decimal characters ("0" to "9").
|
||||
- The first three characters (String[0,3]) represent an integer from 0 to 127, which corresponds to Bitfield of: 1 - Sunday, 2 - Monday, 4 - Tuesday, 8 - Wednesday, 16 - Thursday, 32 - Friday and 64 - Saturday. Setting zero, trigger is only valid for today.
|
||||
- String[3,5] represents the hour of trigger, from 0 to 23.
|
||||
- String[5,7] represents the minute of trigger, from 0 to 59.
|
||||
- String[7,8] represents the enable trigger, 0 - disabled, 1- enabled.
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Xiaomi BLE
|
||||
description: Instructions on how to integrate Xiaomi BLE devices into Home Assistant.
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
ha_bluetooth: true
|
||||
ha_release: 2022.8
|
||||
@ -12,6 +13,7 @@ ha_codeowners:
|
||||
ha_domain: xiaomi_ble
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
@ -36,6 +38,12 @@ It is possible that we detect your device because it uses the MiBeacon protocol
|
||||
- Voltage
|
||||
- Battery
|
||||
|
||||
It also supports the following classes of binary sensors:
|
||||
|
||||
- Light
|
||||
- Smoke
|
||||
- Moisture
|
||||
|
||||
## Encryption
|
||||
|
||||
Some devices use AES encryption to protect the sensor values they are broadcasting.
|
||||
@ -49,3 +57,21 @@ There are a few ways to obtain a bindkey for your device:
|
||||
|
||||
* Set your own. The [Telink Flasher](https://atc1441.github.io/TelinkFlasher.html) allows you to generate new bindkeys for devices it supports. The new bind key will work with Home Assistant, but the Mi Home app will not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app.
|
||||
* Extract the keys from Xiaomi Cloud using a [token extractor](https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor) tool.
|
||||
|
||||
## Devices
|
||||
|
||||
### Plant sensor: Flower Care / MiFlora (HHCCJCY01)
|
||||
|
||||
HHCCJCY01, also known as MiFlora or "Flower Care", should be automatically discovered. However, if the firmware is too old, it won't send the right BLE beacons and an update via the app is required. The lowest confirmed working firmware version is 3.2.1 (a lower 3.x version could also be alright).
|
||||
|
||||
Flower Care firmware update steps:
|
||||
|
||||
* Install the official "Flower Care" app by HHCC:
|
||||
* [Google Play](https://play.google.com/store/apps/details?id=com.huahuacaocao.flowercare) (requires location and storage permission)
|
||||
* [Apple App Store](https://apps.apple.com/us/app/flower-care/id1095274672)
|
||||
* Place the device with the app within 10cm of the plant sensor
|
||||
* Press the "+" button on the top right in the devices tab of the app
|
||||
* Add the plant sensor to the app and select an arbitrary plant
|
||||
* Wait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes)
|
||||
* The installed and latest firmware version can be verified by selecting the plant -> three-dot menu -> Hardware settings -> Hardware update
|
||||
* The Flower Care account and app are not required any further for this integration to work
|
||||
|
||||
@ -216,6 +216,8 @@ Supported devices:
|
||||
| Air Purifier 3 (2019) | zhimi.airpurifier.ma4 | |
|
||||
| Air Purifier 3H (2019) | zhimi.airpurifier.mb3 | |
|
||||
| Air Purifier 3C | zhimi.airpurifier.mb4 | |
|
||||
| Air Purifier 4 | zhimi.airp.mb5 | |
|
||||
| Air Purifier 4 PRO | zhimi.airp.vb4 | |
|
||||
| Air Fresh A1 | dmaker.airfresh.a1 | MJXFJ-150-A1 |
|
||||
| Air Fresh VA2 | zhimi.airfresh.va2 | |
|
||||
| Air Fresh T2017 | dmaker.airfresh.t2017 | MJXFJ-300-G1 |
|
||||
@ -496,6 +498,49 @@ Buzzer | Turn on/off the buzzer
|
||||
Child Lock | Turn on/off the child lock
|
||||
LED | Turn on/off the LED
|
||||
|
||||
### Air Purifier 4/4 PRO (zhimi.airp.mb5/zhimi.airp.vb4)
|
||||
|
||||
These models use newer MiOT communication protocol.
|
||||
|
||||
- Power (on, off)
|
||||
- Operation modes (Auto, Silent, Favorite, Fan)
|
||||
- Attributes (fan platform)
|
||||
- Number entities
|
||||
|
||||
Number | Description
|
||||
----------------------- | -----------------------
|
||||
Fan Level | Set the fan level
|
||||
Favorite Level | Set the favorite level
|
||||
|
||||
- Select entities
|
||||
|
||||
Select | Description
|
||||
----------------------- | -----------------------
|
||||
LED Brightness | Controls the brightness of the Display (bright, dim, off)
|
||||
|
||||
- Sensor entities
|
||||
|
||||
Sensor | Description | Enabled by default
|
||||
----------------------- | ----------------------- | -----------------------
|
||||
Filter Life Remaining | The remaining life of the filter in % | True
|
||||
Filter Time Left | The remaining life of the filter in days | True
|
||||
Filter Use | Filter usage time in hours | True
|
||||
Humidity | The current humidity measured | True
|
||||
Motor Speed | The current motor speed measured in rpm | True
|
||||
PM2.5 | The current particulate matter 2.5 measured | True
|
||||
PM10 | The current particulate matter 10 measured(4 PRO only) | True
|
||||
Purify Volume | The volume of purified air in qubic meter | False
|
||||
Temperature | The current temperature measured | True
|
||||
|
||||
- Switch entities
|
||||
|
||||
Switch | Description
|
||||
----------------------- | -----------------------
|
||||
Buzzer | Turn on/off the buzzer
|
||||
Child Lock | Turn on/off the child lock
|
||||
Ionizer | Turn on/off the negative ion generator
|
||||
|
||||
|
||||
### Air Fresh A1 (dmaker.airfresh.a1)
|
||||
|
||||
- Power (on, off)
|
||||
@ -584,6 +629,13 @@ Button | Description
|
||||
Reset Dust Filter | Resets filter lifetime and usage of the dust filter
|
||||
Reset Upper Filter | Resets filter lifetime and usage of the upper filter
|
||||
|
||||
- Select entities
|
||||
|
||||
Select | Description
|
||||
----------------------- | -----------------------
|
||||
Auxiliary Heat Level | Controls the level of the heater (Low, Medium, High)
|
||||
Display Orientation | Controls the orientation of the display (Forward, Left, Right)
|
||||
|
||||
- Sensor entities
|
||||
|
||||
Sensor | Description
|
||||
|
||||
80
source/_integrations/yalexs_ble.markdown
Normal file
80
source/_integrations/yalexs_ble.markdown
Normal file
@ -0,0 +1,80 @@
|
||||
---
|
||||
title: Yale Access Bluetooth
|
||||
description: Instructions on how to integrate Yale Access Bluetooth devices into Home Assistant.
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Lock
|
||||
- Sensor
|
||||
ha_bluetooth: true
|
||||
ha_release: 2022.9
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@bdraco'
|
||||
ha_domain: yalexs_ble
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- lock
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
Integrates [Yale Access](https://www.yalehome.com/us/en/products/smart-technology/yale-access) Bluetooth devices into Home Assistant.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
The Yale Access Bluetooth integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional.
|
||||
|
||||
Devices must have a Yale Access module installed to function with this integration if one is not already built-in.
|
||||
|
||||
## Supported devices
|
||||
|
||||
- YRD216 (Yale Assure Lock Keypad with Physical Key)
|
||||
- YRL216 (Yale Assure Door Lever Lock with Push Button Keypad)
|
||||
- YRD226 (Yale Assure Lock Touchscreen Deadbolt with Physical Key)
|
||||
- YRL226 (Yale Assure Door Lever Lock Keypad)
|
||||
- YRD256 (Yale Assure Lock Keypad)
|
||||
- ASL-05 (August WiFi Smart Lock - Gen 4)
|
||||
- ASL-03 (August Smart Lock Pro - Gen 3)
|
||||
- ASL-02 (August Smart Lock Pro - Gen 2)
|
||||
|
||||
## Limited support devices
|
||||
|
||||
These devices do not send updates, but can be locked and unlocked.
|
||||
|
||||
- MD-04I (Yale Conexis L1)
|
||||
- YRCB-490 (Yale Smart Cabinet Lock)
|
||||
|
||||
## Push updates
|
||||
|
||||
Some locks only send push updates when they have an active HomeKit pairing. If your lock is not sending push updates, ensure it's paired with a HomeKit using an iOS device or the HomeKit controller integration. The lock cannot be paired via HomeKit Controller and the Yale Access Bluetooth integration on the same Home Assistant instance as they will both try to access the lock simultaneously and fail.
|
||||
|
||||
Alternatively, call the `homeassistant.update_entity` service to force the integration to update the lock state.
|
||||
|
||||
## Door Sensors
|
||||
|
||||
The lock must be calibrated in the Yale Access App for the door sensors to function correctly. If the door sensor has an unknown state or is not updating, try recalibrating the lock in the app.
|
||||
|
||||
|
||||
## Obtaining the offline key
|
||||
|
||||
The offline key and slot number are required to operate the lock. These credentials can be found in multiple places depending on the lock brand and model.
|
||||
|
||||
### Yale Access or August Cloud
|
||||
|
||||
The [August](/integrations/august) integration will automatically provision the offline key if the configured account has the key loaded. You may need to create or use a non-primary existing account with owner-level access to the lock, as not all accounts will have the key loaded.
|
||||
|
||||
Most Yale branded locks can use the August cloud to obtain the keys. Accessing the August cloud to receive the key may not work unless the lock was purchased in a market that sells under both brands.
|
||||
|
||||
### iOS - Yale Access App or August App
|
||||
|
||||
The iOS app will only save the offline key to your device's filesystem if Auto-Unlock has been enabled and used at least once. Auto-Unlock can be disabled once the key has been loaded.
|
||||
|
||||
- Using [iMazing](https://imazing.com/) or [iPhone Backup Extractor](https://www.iphonebackupextractor.com/), find the backup files for the Yale Access app.
|
||||
- Look in the `Library/Preferences` `.plist` files for the Yale Access app and find the one with the value of `key` and `slot` using `Xcode` or any binary `plist` viewer.
|
||||
|
||||
### Android - Yale Access App or August App
|
||||
|
||||
The Android app will only save the offline key to your device's filesystem if Auto-Unlock has been enabled and used at least once. Auto-Unlock can be disabled once the key has been loaded.
|
||||
|
||||
Root access is required to read the `key` and `slot` stored in `/data/data/com.august.luna/shared_prefs/PeripheralInfoCache.xml`
|
||||
@ -83,7 +83,7 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
|
||||
- [RaspBee II (a.k.a. RaspBee 2) Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee2)
|
||||
- [RaspBee Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee)
|
||||
- Silicon Labs EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
|
||||
- [ITead Zigbee 3.0 USB Dongle (EFR32MG21) Model 9888010100045](https://itead.cc/product/zigbee-3-0-usb-dongle/)
|
||||
- [ITead SONOFF Zigbee 3.0 USB Dongle Plus Model "ZBDongle-E" (EFR32MG21 variant)](https://itead.cc/product/zigbee-3-0-usb-dongle/)
|
||||
- [ITead Sonoff ZBBridge](https://itead.cc/product/sonoff-zbbridge/) (Note! [WiFi-based bridges are not recommended for ZHA with EZSP radios](https://github.com/home-assistant/home-assistant.io/issues/17170). Also, this first have to be flashed with [Tasmota firmware and Silabs EmberZNet NCP EZSP UART Host firmware to use as Serial-to-IP adapter](https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html))
|
||||
- [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee Ember 3581 USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/walthowd/husbzb-firmware))
|
||||
- [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs-usb-adapter.html)/[POPP ZB-Stick](https://shop.zwave.eu/detail/index/sArticle/2496) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
|
||||
@ -172,7 +172,7 @@ Some devices can be auto-discovered, which can simplify the ZHA setup process. T
|
||||
|
||||
| Device | Discovery Method | Identifier |
|
||||
| -------| ---------------- | ---------- |
|
||||
| [ITead SONOFF Zigbee 3.0 USB Dongle Plus](https://itead.cc/product/sonoff-zigbee-3-0-usb-dongle-plus/) | USB | 10C4:EA60 |
|
||||
| [ITead SONOFF Zigbee 3.0 USB Dongle Plus Model "ZBDongle-P" (CC2652P variant)](https://itead.cc/product/sonoff-zigbee-3-0-usb-dongle-plus/) | USB | 10C4:EA60 |
|
||||
| [Bitron Video/SMaBiT BV AV2010/10](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) | USB | 10C4:8B34 |
|
||||
| [ConBee II](https://phoscon.de/conbee2) | USB | 1CF1:0030 |
|
||||
| [Nortek HUSBZB-1](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) | USB | 10C4:8A2A |
|
||||
|
||||
@ -370,6 +370,7 @@ These are notification events fired by devices using the Multilevel Switch comma
|
||||
"command_class": 38,
|
||||
"command_class_name": "Multilevel Switch",
|
||||
"event_type": 4,
|
||||
"event_type_label": "label 1",
|
||||
"direction": "up"
|
||||
},
|
||||
```
|
||||
@ -384,6 +385,7 @@ These are notification events fired by devices using the Multilevel Switch comma
|
||||
"command_class": 38,
|
||||
"command_class_name": "Multilevel Switch",
|
||||
"event_type": 5,
|
||||
"event_type_label": "label 2",
|
||||
"direction": null
|
||||
},
|
||||
```
|
||||
@ -401,7 +403,9 @@ These are notification events fired by devices using the Entry Control command c
|
||||
"command_class": 111,
|
||||
"command_class_name": "Entry Control",
|
||||
"event_type": 6,
|
||||
"event_type_label": "label 1",
|
||||
"data_type": 5,
|
||||
"data_type_label": "label 2",
|
||||
"event_data": "555"
|
||||
}
|
||||
```
|
||||
@ -870,6 +874,6 @@ Many users have reported issues with interference when the USB stick was directl
|
||||
|
||||
Z-Wave JS writes details to its logs. To access these logs go to the following.
|
||||
|
||||
**Configuraton** -> **Devices & Services** -> **Integrations(tab)** -> **Z-Wave (CONFIGURE)** -> **Logs(tab)**
|
||||
**Settings** -> **Devices & Services** -> **Integrations(tab)** -> **Z-Wave (CONFIGURE)** -> **Logs(tab)**
|
||||
|
||||
You need to keep this browser tab open for logging to be active.
|
||||
|
||||
@ -43,27 +43,23 @@ Enjoy the release!
|
||||
- [Other noteworthy changes](#other-noteworthy-changes)
|
||||
- [New Integrations](#new-integrations)
|
||||
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
|
||||
- [Release 2022.8.1 - August 4](#release-202281---august-4)
|
||||
- [Release 2022.8.2 - August 7](#release-202282---august-7)
|
||||
- [Release 2022.8.3 - August 9](#release-202283---august-9)
|
||||
- [Release 2022.8.4 - August 12](#release-202284---august-12)
|
||||
- [Release 2022.8.5 - August 15](#release-202285---august-15)
|
||||
- [Release 2022.8.6 - August 17](#release-202286---august-17)
|
||||
- [Need help? Join the community!](#need-help-join-the-community)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [Farewell to the following](#farewell-to-the-following)
|
||||
- [All changes](#all-changes)
|
||||
|
||||
|
||||
Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=m9gKFH8WlzY) today at 12:00 PDT / 21:00 CET!
|
||||
|
||||
<lite-youtube videoid="m9gKFH8WlzY" videotitle="Home Assistant 2022.8 Release Party"></lite-youtube>
|
||||
|
||||
{% comment %}
|
||||
|
||||
<!-- Replace the wrapper above with the following after the livestream...-->
|
||||
|
||||
Missed our release party live stream on YouTube? Don't worry! You can watch
|
||||
the recording of it right here!
|
||||
|
||||
<lite-youtube videoid="m9gKFH8WlzY" videotitle="Home Assistant 2022.8 Release Party"></lite-youtube>
|
||||
|
||||
{% endcomment %}
|
||||
|
||||
## Introducing Repairs: You can fix it!
|
||||
|
||||
A completely new feature we hope you are going to love: **Repairs**! 👷♂️
|
||||
@ -100,7 +96,7 @@ it to be extended a lot, with more issue detections, in the near future.
|
||||
## First-class Bluetooth support
|
||||
|
||||
Today, we proudly announce that Home Assistant now has **first-class**
|
||||
Bluetooth support! 🥇
|
||||
Bluetooth support! 🥇
|
||||
|
||||
A brand new [Bluetooth integration] has been added, which provides absolutely
|
||||
amazing Bluetooth support to Home Assistant, including automatic discovery of
|
||||
@ -227,7 +223,7 @@ noteworthy changes this release:
|
||||
- [@frenck] updated the events developer tools to use YAML instead of JSON
|
||||
and added syntax highlighting.
|
||||
- The [LIFX] integration got a significant overhaul, making it much more
|
||||
reliable. Thanks for the work on this in the past releases
|
||||
reliable. Thanks for the work on this in the past releases
|
||||
[@bdraco] and [@Djelibeybi]!
|
||||
- The [UniFi Network] now has update entities, allowing you to update the
|
||||
firmware of UniFi devices directly from Home Assistant. Great addition [@J3173]!
|
||||
@ -319,6 +315,297 @@ The following integrations are now available via the Home Assistant UI:
|
||||
[Anthem A/V Receivers]: /integrations/anthemav
|
||||
[Bose SoundTouch]: /integrations/soundtouch
|
||||
|
||||
## Release 2022.8.1 - August 4
|
||||
|
||||
- Fix zwave_js addon info ([@MartinHjelmare] - [#76044]) ([hassio docs]) ([zwave_js docs])
|
||||
- Bump bleak to 0.15.1 ([@bdraco] - [#76136]) ([bluetooth docs])
|
||||
- Allow climate operation mode fan_only as custom mode in Alexa ([@jbouwh] - [#76148]) ([alexa docs])
|
||||
- Remove icon attribute if device class is set ([@dgomes] - [#76161]) ([integration docs])
|
||||
- Fix flux_led ignored entries not being respected ([@bdraco] - [#76173]) ([flux_led docs])
|
||||
- Fix race in bluetooth async_process_advertisements ([@bdraco] - [#76176]) ([bluetooth docs])
|
||||
- Add repair item to remove no-longer-functioning Flu Near You integration ([@bachya] - [#76177]) ([flunearyou docs]) (deprecation)
|
||||
- Fix arm away in Risco ([@OnFreund] - [#76188]) ([risco docs])
|
||||
- Fix nullable ip_address in mikrotik ([@engrbm87] - [#76197]) ([mikrotik docs])
|
||||
- Mark RPI Power binary sensor as diagnostic ([@frenck] - [#76198]) ([rpi_power docs])
|
||||
- BLE pairing reliablity fixes for HomeKit Controller ([@bdraco] - [#76199]) ([homekit_controller docs]) (dependency)
|
||||
- Bump NextDNS library ([@bieniu] - [#76207]) ([nextdns docs])
|
||||
- Bump AIOAladdin Connect to 0.1.41 ([@mkmer] - [#76217]) ([aladdin_connect docs]) (dependency)
|
||||
- Fix spelling of OpenWrt in luci integration manifest ([@frenck] - [#76219]) ([luci docs])
|
||||
- Fix Life360 recovery from server errors ([@pnbruckner] - [#76231]) ([life360 docs])
|
||||
- More explicitly call out special cases with SimpliSafe authorization code ([@bachya] - [#76232]) ([simplisafe docs])
|
||||
- Enable strict typing for HomeKit Controller config flow module ([@Jc2k] - [#76233]) ([homekit_controller docs])
|
||||
- Fix some homekit_controller pylint warnings and (local only) test failures ([@Jc2k] - [#76122]) ([homekit_controller docs])
|
||||
|
||||
[#76044]: https://github.com/home-assistant/core/pull/76044
|
||||
[#76122]: https://github.com/home-assistant/core/pull/76122
|
||||
[#76136]: https://github.com/home-assistant/core/pull/76136
|
||||
[#76148]: https://github.com/home-assistant/core/pull/76148
|
||||
[#76161]: https://github.com/home-assistant/core/pull/76161
|
||||
[#76173]: https://github.com/home-assistant/core/pull/76173
|
||||
[#76176]: https://github.com/home-assistant/core/pull/76176
|
||||
[#76177]: https://github.com/home-assistant/core/pull/76177
|
||||
[#76188]: https://github.com/home-assistant/core/pull/76188
|
||||
[#76197]: https://github.com/home-assistant/core/pull/76197
|
||||
[#76198]: https://github.com/home-assistant/core/pull/76198
|
||||
[#76199]: https://github.com/home-assistant/core/pull/76199
|
||||
[#76207]: https://github.com/home-assistant/core/pull/76207
|
||||
[#76217]: https://github.com/home-assistant/core/pull/76217
|
||||
[#76219]: https://github.com/home-assistant/core/pull/76219
|
||||
[#76231]: https://github.com/home-assistant/core/pull/76231
|
||||
[#76232]: https://github.com/home-assistant/core/pull/76232
|
||||
[#76233]: https://github.com/home-assistant/core/pull/76233
|
||||
[@Jc2k]: https://github.com/Jc2k
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@OnFreund]: https://github.com/OnFreund
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@dgomes]: https://github.com/dgomes
|
||||
[@engrbm87]: https://github.com/engrbm87
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[@mkmer]: https://github.com/mkmer
|
||||
[@pnbruckner]: https://github.com/pnbruckner
|
||||
[aladdin_connect docs]: /integrations/aladdin_connect/
|
||||
[alexa docs]: /integrations/alexa/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[flunearyou docs]: /integrations/flunearyou/
|
||||
[flux_led docs]: /integrations/flux_led/
|
||||
[hassio docs]: /integrations/hassio/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[integration docs]: /integrations/integration/
|
||||
[life360 docs]: /integrations/life360/
|
||||
[luci docs]: /integrations/luci/
|
||||
[mikrotik docs]: /integrations/mikrotik/
|
||||
[nextdns docs]: /integrations/nextdns/
|
||||
[risco docs]: /integrations/risco/
|
||||
[rpi_power docs]: /integrations/rpi_power/
|
||||
[simplisafe docs]: /integrations/simplisafe/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2022.8.2 - August 7
|
||||
|
||||
- Update gree to use the network component to set discovery interfaces ([@Jc2k] - [#75812]) ([gree docs])
|
||||
- Use stored philips_js system data on start ([@elupus] - [#75981]) ([philips_js docs])
|
||||
- Ensure bluetooth recovers if Dbus gets restarted ([@bdraco] - [#76249]) ([bluetooth docs])
|
||||
- Fix default sensor names in NextDNS integration ([@bieniu] - [#76264]) ([nextdns docs])
|
||||
- Bump ZHA dependencies ([@puddly] - [#76275]) ([zha docs])
|
||||
- Bump pydeconz to v102 ([@Kane610] - [#76287]) ([deconz docs])
|
||||
- Fix ZHA light color temp support ([@dmulcahey] - [#76305]) ([zha docs])
|
||||
- Bump pySwitchbot to 0.18.4 ([@bdraco] - [#76322]) ([switchbot docs])
|
||||
- Bump aiobafi6 to 0.7.2 to unblock #76328 ([@jfroy] - [#76330]) ([baf docs])
|
||||
- Postpone broadlink platform switch until config entry is ready ([@elupus] - [#76371]) ([broadlink docs])
|
||||
|
||||
[#75812]: https://github.com/home-assistant/core/pull/75812
|
||||
[#75981]: https://github.com/home-assistant/core/pull/75981
|
||||
[#76249]: https://github.com/home-assistant/core/pull/76249
|
||||
[#76264]: https://github.com/home-assistant/core/pull/76264
|
||||
[#76275]: https://github.com/home-assistant/core/pull/76275
|
||||
[#76287]: https://github.com/home-assistant/core/pull/76287
|
||||
[#76305]: https://github.com/home-assistant/core/pull/76305
|
||||
[#76322]: https://github.com/home-assistant/core/pull/76322
|
||||
[#76330]: https://github.com/home-assistant/core/pull/76330
|
||||
[#76371]: https://github.com/home-assistant/core/pull/76371
|
||||
[@Jc2k]: https://github.com/Jc2k
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@dmulcahey]: https://github.com/dmulcahey
|
||||
[@elupus]: https://github.com/elupus
|
||||
[@jfroy]: https://github.com/jfroy
|
||||
[@puddly]: https://github.com/puddly
|
||||
[baf docs]: /integrations/baf/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[broadlink docs]: /integrations/broadlink/
|
||||
[deconz docs]: /integrations/deconz/
|
||||
[gree docs]: /integrations/gree/
|
||||
[nextdns docs]: /integrations/nextdns/
|
||||
[philips_js docs]: /integrations/philips_js/
|
||||
[switchbot docs]: /integrations/switchbot/
|
||||
[zha docs]: /integrations/zha/
|
||||
|
||||
## Release 2022.8.3 - August 9
|
||||
|
||||
- Add debug logging for unknown Notion errors ([@bachya] - [#76395]) ([notion docs])
|
||||
- Automatically enable common RainMachine restriction entities ([@bachya] - [#76405]) ([rainmachine docs])
|
||||
- Fix bug where RainMachine entity states don't populate on startup ([@bachya] - [#76412]) ([rainmachine docs])
|
||||
- Fix Govee 5185 Meat Thermometers with older firmware not being discovered ([@bdraco] - [#76414]) ([govee_ble docs])
|
||||
- Fix iCloud listeners ([@epenet] - [#76437]) ([icloud docs])
|
||||
- Bump version of pyunifiprotect to 4.0.12 ([@AngellusMortis] - [#76465]) ([unifiprotect docs])
|
||||
- Bump aiohomekit to 1.2.6 ([@bdraco] - [#76488]) ([homekit_controller docs])
|
||||
- Fix inkbird ibbq2s that identify with xbbq ([@bdraco] - [#76492]) ([inkbird docs])
|
||||
- Bump govee-ble to 0.14.0 to fix H5052 sensors ([@bdraco] - [#76497]) ([govee_ble docs])
|
||||
- Fix pairing with HK accessories that do not provide format for vendor chars ([@bdraco] - [#76502]) ([homekit_controller docs])
|
||||
- Fix #76283 ([@ocalvo] - [#76531]) ([sms docs])
|
||||
- Bump aiohomekit to 1.2.8 ([@bdraco] - [#76532]) ([homekit_controller docs])
|
||||
|
||||
[#76395]: https://github.com/home-assistant/core/pull/76395
|
||||
[#76405]: https://github.com/home-assistant/core/pull/76405
|
||||
[#76412]: https://github.com/home-assistant/core/pull/76412
|
||||
[#76414]: https://github.com/home-assistant/core/pull/76414
|
||||
[#76437]: https://github.com/home-assistant/core/pull/76437
|
||||
[#76465]: https://github.com/home-assistant/core/pull/76465
|
||||
[#76488]: https://github.com/home-assistant/core/pull/76488
|
||||
[#76492]: https://github.com/home-assistant/core/pull/76492
|
||||
[#76497]: https://github.com/home-assistant/core/pull/76497
|
||||
[#76502]: https://github.com/home-assistant/core/pull/76502
|
||||
[#76531]: https://github.com/home-assistant/core/pull/76531
|
||||
[#76532]: https://github.com/home-assistant/core/pull/76532
|
||||
[@AngellusMortis]: https://github.com/AngellusMortis
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@epenet]: https://github.com/epenet
|
||||
[@ocalvo]: https://github.com/ocalvo
|
||||
[govee_ble docs]: /integrations/govee_ble/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[icloud docs]: /integrations/icloud/
|
||||
[inkbird docs]: /integrations/inkbird/
|
||||
[notion docs]: /integrations/notion/
|
||||
[rainmachine docs]: /integrations/rainmachine/
|
||||
[sms docs]: /integrations/sms/
|
||||
[unifiprotect docs]: /integrations/unifiprotect/
|
||||
|
||||
## Release 2022.8.4 - August 12
|
||||
|
||||
- Bump ZHA dependencies ([@puddly] - [#76565]) ([zha docs])
|
||||
- Replaces aiohttp.hdrs CONTENT_TYPE with plain string for the Swisscom integration ([@DeeVeX] - [#76568]) ([swisscom docs])
|
||||
- Fix homekit_controller not noticing ip and port changes that zeroconf has found ([@Jc2k] - [#76570]) ([homekit_controller docs])
|
||||
- Fix Spotify deviding None value in current progress ([@frenck] - [#76581]) ([spotify docs])
|
||||
- Improve code quality in huawei_lte ([@a-p-z] - [#76583]) ([huawei_lte docs])
|
||||
- Fix Govee 5181 with old firmware ([@bdraco] - [#76600]) ([govee_ble docs])
|
||||
- Fix evohome preset modes ([@MartinHjelmare] - [#76606]) ([evohome docs])
|
||||
- Add missing _abort_if_unique_id_configured to ble integrations ([@bdraco] - [#76624]) ([govee_ble docs]) ([sensorpush docs]) ([inkbird docs]) ([xiaomi_ble docs]) ([moat docs])
|
||||
- Fix non-awaited coroutine in BMW notify ([@rikroe] - [#76664]) ([bmw_connected_drive docs])
|
||||
|
||||
[#76565]: https://github.com/home-assistant/core/pull/76565
|
||||
[#76568]: https://github.com/home-assistant/core/pull/76568
|
||||
[#76570]: https://github.com/home-assistant/core/pull/76570
|
||||
[#76581]: https://github.com/home-assistant/core/pull/76581
|
||||
[#76583]: https://github.com/home-assistant/core/pull/76583
|
||||
[#76600]: https://github.com/home-assistant/core/pull/76600
|
||||
[#76606]: https://github.com/home-assistant/core/pull/76606
|
||||
[#76624]: https://github.com/home-assistant/core/pull/76624
|
||||
[#76664]: https://github.com/home-assistant/core/pull/76664
|
||||
[@DeeVeX]: https://github.com/DeeVeX
|
||||
[@Jc2k]: https://github.com/Jc2k
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@a-p-z]: https://github.com/a-p-z
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@puddly]: https://github.com/puddly
|
||||
[@rikroe]: https://github.com/rikroe
|
||||
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
|
||||
[evohome docs]: /integrations/evohome/
|
||||
[govee_ble docs]: /integrations/govee_ble/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[huawei_lte docs]: /integrations/huawei_lte/
|
||||
[inkbird docs]: /integrations/inkbird/
|
||||
[moat docs]: /integrations/moat/
|
||||
[sensorpush docs]: /integrations/sensorpush/
|
||||
[spotify docs]: /integrations/spotify/
|
||||
[swisscom docs]: /integrations/swisscom/
|
||||
[xiaomi_ble docs]: /integrations/xiaomi_ble/
|
||||
[zha docs]: /integrations/zha/
|
||||
|
||||
## Release 2022.8.5 - August 15
|
||||
|
||||
- Update systembridgeconnector to 3.4.4 ([@timmo001] - [#75362]) ([system_bridge docs])
|
||||
- 🐛 Fix "The request content was malformed" error in home_connect ([@hansgoed] - [#76411]) ([home_connect docs])
|
||||
- Bump pySwitchbot to 0.18.5 ([@bdraco] - [#76640]) ([switchbot docs])
|
||||
- Bump pySwitchbot to 0.18.6 to fix disconnect race ([@bdraco] - [#76656]) ([switchbot docs])
|
||||
- Bump pySwitchbot to 0.18.10 to handle empty data and disconnects ([@bdraco] - [#76684]) ([switchbot docs])
|
||||
- Fix google calendar disabled entity handling ([@allenporter] - [#76699]) ([google docs])
|
||||
- Motion Blinds fix OperationNotAllowed ([@starkillerOG] - [#76712]) ([motion_blinds docs])
|
||||
- Update xknx to 1.0.0 🎉 ([@marvin-w] - [#76734]) ([knx docs])
|
||||
- Bump aiohomekit to 1.2.10 ([@bdraco] - [#76738]) ([homekit_controller docs])
|
||||
- Fix bad data with inkbird bbq sensors ([@bdraco] - [#76739]) ([inkbird docs])
|
||||
- Bump bimmer_connected to 0.10.2 ([@rikroe] - [#76751]) ([bmw_connected_drive docs])
|
||||
- Bump aiohue to 4.5.0 ([@marcelveldt] - [#76757]) ([hue docs])
|
||||
- Fix stale data with SensorPush sensors ([@bdraco] - [#76771]) ([sensorpush docs])
|
||||
- Bump homeconnect to 0.7.2 ([@BraveChicken1] - [#76773]) ([home_connect docs])
|
||||
- Bump aiohomekit to 1.2.11 ([@bdraco] - [#76784]) ([homekit_controller docs])
|
||||
- Fix bluetooth callback registration not surviving a reload ([@bdraco] - [#76817]) ([bluetooth docs])
|
||||
- Correct referenced entities and devices for event triggers ([@emontnemery] - [#76818]) ([automation docs])
|
||||
- Fix lifx homekit discoveries not being ignorable or updating the IP ([@bdraco] - [#76825]) ([lifx docs])
|
||||
|
||||
[#75362]: https://github.com/home-assistant/core/pull/75362
|
||||
[#76411]: https://github.com/home-assistant/core/pull/76411
|
||||
[#76640]: https://github.com/home-assistant/core/pull/76640
|
||||
[#76656]: https://github.com/home-assistant/core/pull/76656
|
||||
[#76684]: https://github.com/home-assistant/core/pull/76684
|
||||
[#76699]: https://github.com/home-assistant/core/pull/76699
|
||||
[#76712]: https://github.com/home-assistant/core/pull/76712
|
||||
[#76734]: https://github.com/home-assistant/core/pull/76734
|
||||
[#76738]: https://github.com/home-assistant/core/pull/76738
|
||||
[#76739]: https://github.com/home-assistant/core/pull/76739
|
||||
[#76751]: https://github.com/home-assistant/core/pull/76751
|
||||
[#76757]: https://github.com/home-assistant/core/pull/76757
|
||||
[#76771]: https://github.com/home-assistant/core/pull/76771
|
||||
[#76773]: https://github.com/home-assistant/core/pull/76773
|
||||
[#76784]: https://github.com/home-assistant/core/pull/76784
|
||||
[#76817]: https://github.com/home-assistant/core/pull/76817
|
||||
[#76818]: https://github.com/home-assistant/core/pull/76818
|
||||
[#76825]: https://github.com/home-assistant/core/pull/76825
|
||||
[@BraveChicken1]: https://github.com/BraveChicken1
|
||||
[@allenporter]: https://github.com/allenporter
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@hansgoed]: https://github.com/hansgoed
|
||||
[@marcelveldt]: https://github.com/marcelveldt
|
||||
[@marvin-w]: https://github.com/marvin-w
|
||||
[@rikroe]: https://github.com/rikroe
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@timmo001]: https://github.com/timmo001
|
||||
[automation docs]: /integrations/automation/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
|
||||
[google docs]: /integrations/google/
|
||||
[home_connect docs]: /integrations/home_connect/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[hue docs]: /integrations/hue/
|
||||
[inkbird docs]: /integrations/inkbird/
|
||||
[knx docs]: /integrations/knx/
|
||||
[lifx docs]: /integrations/lifx/
|
||||
[motion_blinds docs]: /integrations/motion_blinds/
|
||||
[sensorpush docs]: /integrations/sensorpush/
|
||||
[switchbot docs]: /integrations/switchbot/
|
||||
[system_bridge docs]: /integrations/system_bridge/
|
||||
|
||||
## Release 2022.8.6 - August 17
|
||||
|
||||
- Fix displayed units for BMW Connected Drive ([@rikroe] - [#76613]) ([bmw_connected_drive docs])
|
||||
- Fix Overkiz startup order to prevent unnamed device showing up ([@iMicknl] - [#76695]) ([overkiz docs])
|
||||
- Bump pynetgear to 0.10.7 ([@starkillerOG] - [#76754]) ([netgear docs])
|
||||
- Correct restoring of mobile_app sensors ([@emontnemery] - [#76886]) ([mobile_app docs])
|
||||
- Fix acmeda set cover tilt position ([@epenet] - [#76927]) ([acmeda docs])
|
||||
- Fix race in notify setup ([@bdraco] - [#76954]) ([notify docs])
|
||||
- Pass the real config for Discord ([@tkdrob] - [#76959]) ([discord docs])
|
||||
- Pass the real config for Slack ([@tkdrob] - [#76960]) ([slack docs])
|
||||
|
||||
[#76613]: https://github.com/home-assistant/core/pull/76613
|
||||
[#76695]: https://github.com/home-assistant/core/pull/76695
|
||||
[#76754]: https://github.com/home-assistant/core/pull/76754
|
||||
[#76886]: https://github.com/home-assistant/core/pull/76886
|
||||
[#76927]: https://github.com/home-assistant/core/pull/76927
|
||||
[#76954]: https://github.com/home-assistant/core/pull/76954
|
||||
[#76959]: https://github.com/home-assistant/core/pull/76959
|
||||
[#76960]: https://github.com/home-assistant/core/pull/76960
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@epenet]: https://github.com/epenet
|
||||
[@iMicknl]: https://github.com/iMicknl
|
||||
[@rikroe]: https://github.com/rikroe
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@tkdrob]: https://github.com/tkdrob
|
||||
[acmeda docs]: /integrations/acmeda/
|
||||
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
|
||||
[discord docs]: /integrations/discord/
|
||||
[mobile_app docs]: /integrations/mobile_app/
|
||||
[netgear docs]: /integrations/netgear/
|
||||
[notify docs]: /integrations/notify/
|
||||
[overkiz docs]: /integrations/overkiz/
|
||||
[slack docs]: /integrations/slack/
|
||||
|
||||
## Need help? Join the community!
|
||||
|
||||
Home Assistant has a great community of users who are all more than willing
|
||||
@ -460,7 +747,7 @@ Removed:
|
||||
- `mdi:discord`
|
||||
- `mdi:google-home`
|
||||
- `tablet-android` - Use `mdi:tablet` instead.
|
||||
|
||||
|
||||
Renamed:
|
||||
|
||||
- `mdi:diving-scuba` to `mdi:diving-scuba-mask`
|
||||
|
||||
@ -41,8 +41,8 @@ Now let's make a change using the file editor: we are going to change the name,
|
||||
</div>
|
||||
|
||||
- Click the save icon in the top right to commit changes.
|
||||
- Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a configuration check. Do this by clicking on Configuration in the sidebar, click on `Developer-Tools -> YAML` and click on the **Check configuration** button. When it's valid, it will show the text "Configuration valid!". In order for the **Check Configuration**" button to be visible, you must enable "Advanced Mode" on your user profile.
|
||||
- Now Restart Home Assistant using the **Restart** button in the Server management section on the same page.
|
||||
- Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a configuration check. Do this by navigating to {% my server_controls title="Developer Tools -> YAML" %} and and then clicking on the **Check configuration** button. When it's valid, it will show the text "Configuration valid!". In order for the **Check Configuration**" button to be visible, you must enable "Advanced Mode" on your user profile.
|
||||
- Now Restart Home Assistant. You can do so by either using the **Restart** option in the ⚙ menu of the File Editor UI or by navigating to {% my system_dashboard title="Settings -> System" %} and then clicking on the **Restart** button on the top right of the page.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,10 +8,7 @@ Presence detection detects if people are home, which is the most valuable input
|
||||
- Send me a notification when my child arrives at school
|
||||
- Turn on the AC when I leave work
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/map.png' />
|
||||
Screenshot of Home Assistant showing a school, work and home zone and two people.
|
||||
</p>
|
||||
|
||||
|
||||
### Adding presence detection
|
||||
|
||||
@ -23,10 +20,9 @@ During the setup of Home Assistant Companion on your mobile device, the app will
|
||||
|
||||
|
||||
### Zones
|
||||
|
||||
|
||||
<img src='/images/screenshots/badges-zone.png' style='float: right; margin-left: 8px; height: 100px;'>
|
||||
|
||||
Zones allow you to name areas on a map. These areas can then be used to name the location a tracked user is, or use entering/leaving a zone as an automation [trigger] or [condition]. Zones can be set up from configuration screen.
|
||||
Zones allow you to name areas on a map. These areas can then be used to name the location a tracked user is, or use entering/leaving a zone as an automation [trigger] or [condition]. See [Zones integration](/integrations/zone/) page for more details like creating zones.
|
||||
|
||||
<div class='note'>
|
||||
The map view will hide all devices that are home.
|
||||
|
||||
BIN
source/images/blueprints/selector-state.png
Normal file
BIN
source/images/blueprints/selector-state.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.1 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 88 KiB |
BIN
source/images/integrations/switch_as_x/Entities_Properties.png
Normal file
BIN
source/images/integrations/switch_as_x/Entities_Properties.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
BIN
source/images/screenshots/System_information.png
Normal file
BIN
source/images/screenshots/System_information.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
source/images/screenshots/System_information_menu.png
Normal file
BIN
source/images/screenshots/System_information_menu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 56 KiB |
@ -24,7 +24,7 @@ the database, and even change how long it stores the data
|
||||
|
||||
## Delete old backups
|
||||
|
||||
Open the Home Assistant UI and go to {% my backups title="Settings > System > Backups" %}, here you will see all your backups,
|
||||
Open the Home Assistant UI and go to {% my backup title="Settings > System > Backups" %}, here you will see all your backups,
|
||||
these can be downloaded and placed somewhere safe. When you have done that, you can delete
|
||||
them in the UI and it will free up some space for you.
|
||||
|
||||
@ -32,8 +32,7 @@ them in the UI and it will free up some space for you.
|
||||
|
||||
Add-ons can take a lot of space, not just the add-on itself but also their data.
|
||||
|
||||
Open the Home Assistant UI and go to {% my supervisor title="Settings > Add-ons" %} in the sidebar, you will be
|
||||
on the "Dashboard" tab when you click on {% my supervisor title="Settings > Add-ons" %}, here you will see
|
||||
Open the Home Assistant UI and go to {% my supervisor title="Settings > Add-ons" %} in the sidebar. Here you will see
|
||||
all your installed add-ons, maybe you have some that you no longer use, if
|
||||
you do those can be uninstalled to free up some space.
|
||||
|
||||
@ -46,5 +45,5 @@ documentation for your hypervisor on how to expand disks for virtual machines.
|
||||
Home Assistant will auto-expand to use the newly added space.
|
||||
|
||||
If you are not running a VM, you need to replace your storage medium
|
||||
(typically, this will be an SD card). You can use [backups](/hassio/haos_common_tasks/#home-assistant-os-backups) to quickly restore your Home Assistant
|
||||
(typically, this will be an SD card). You can use [backups](/common-tasks/os#home-assistant-os-backups) to quickly restore your Home Assistant
|
||||
installation on a new storage medium.
|
||||
|
||||
21
source/more-info/unsupported/supervisor_version.markdown
Normal file
21
source/more-info/unsupported/supervisor_version.markdown
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Supervisor Version"
|
||||
description: "More information on why supervisor_version marks the installation as unsupported."
|
||||
---
|
||||
|
||||
## The issue
|
||||
|
||||
Only the latest version of the supervisor is supported. Users may control when Supervisor
|
||||
updates by disabling its default auto-update behavior and updating it manually.
|
||||
But using any version of Supervisor besides the latest is not supported.
|
||||
|
||||
## The solution
|
||||
|
||||
Update Supervisor to the latest version by running the following command:
|
||||
```bash
|
||||
ha supervisor update
|
||||
```
|
||||
Or re-enable auto update with this command:
|
||||
```bash
|
||||
ha supervisor options --auto-update
|
||||
```
|
||||
Loading…
x
Reference in New Issue
Block a user