mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-18 23:06:58 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
a5cd7fc19b
2
Gemfile
2
Gemfile
@ -21,7 +21,7 @@ group :jekyll_plugins do
|
||||
end
|
||||
|
||||
gem 'sinatra', '2.1.0'
|
||||
gem 'nokogiri', '1.12.5'
|
||||
gem 'nokogiri', '1.13.1'
|
||||
|
||||
# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
|
||||
# and associated library
|
||||
|
||||
16
Gemfile.lock
16
Gemfile.lock
@ -25,8 +25,8 @@ GEM
|
||||
http_parser.rb (~> 0)
|
||||
eventmachine (1.2.7)
|
||||
eventmachine (1.2.7-x64-mingw32)
|
||||
ffi (1.15.4)
|
||||
ffi (1.15.4-x64-mingw32)
|
||||
ffi (1.15.5)
|
||||
ffi (1.15.5-x64-mingw32)
|
||||
forwardable-extended (2.6.0)
|
||||
http_parser.rb (0.8.0)
|
||||
i18n (1.8.11)
|
||||
@ -66,18 +66,18 @@ GEM
|
||||
kramdown-parser-gfm (1.1.0)
|
||||
kramdown (~> 2.0)
|
||||
liquid (4.0.3)
|
||||
listen (3.7.0)
|
||||
listen (3.7.1)
|
||||
rb-fsevent (~> 0.10, >= 0.10.3)
|
||||
rb-inotify (~> 0.9, >= 0.9.10)
|
||||
mercenary (0.4.0)
|
||||
mini_portile2 (2.6.1)
|
||||
mini_portile2 (2.7.1)
|
||||
multi_json (1.15.0)
|
||||
mustermann (1.1.1)
|
||||
ruby2_keywords (~> 0.0.1)
|
||||
nokogiri (1.12.5)
|
||||
mini_portile2 (~> 2.6.1)
|
||||
nokogiri (1.13.1)
|
||||
mini_portile2 (~> 2.7.0)
|
||||
racc (~> 1.4)
|
||||
nokogiri (1.12.5-x64-mingw32)
|
||||
nokogiri (1.13.1-x64-mingw32)
|
||||
racc (~> 1.4)
|
||||
pathutil (0.16.2)
|
||||
forwardable-extended (~> 2.6)
|
||||
@ -130,7 +130,7 @@ DEPENDENCIES
|
||||
jekyll-sitemap (= 1.4.0)
|
||||
jekyll-time-to-read (= 0.1.2)
|
||||
jekyll-toc (= 0.17.1)
|
||||
nokogiri (= 1.12.5)
|
||||
nokogiri (= 1.13.1)
|
||||
rake (= 13.0.6)
|
||||
sass-globbing (= 1.1.5)
|
||||
sassc (= 2.1.0)
|
||||
|
||||
@ -108,8 +108,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 2021
|
||||
current_minor_version: 12
|
||||
current_patch_version: 7
|
||||
date_released: 2021-12-29
|
||||
current_patch_version: 10
|
||||
date_released: 2022-01-17
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -51,7 +51,7 @@ If you don't specify any `auth_providers` section in the `configuration.yaml` fi
|
||||
|
||||
### Trusted Networks
|
||||
|
||||
The Trusted Networks auth provider defines a range of IP addresses for which no authentication will be required (also known as "whitelisting"). For example, you can whitelist your local network so you won't be prompted for a password if you access Home Assistant from inside your home.
|
||||
The Trusted Networks auth provider defines a range of IP addresses for which no authentication will be required (also known as "allowlisting"). For example, you can allowlist your local network so you won't be prompted for a password if you access Home Assistant from inside your home.
|
||||
|
||||
When you log in from one of these networks, you will be asked which user account to use and won't need to enter a password.
|
||||
|
||||
@ -74,7 +74,7 @@ homeassistant:
|
||||
|
||||
{% configuration %}
|
||||
trusted_networks:
|
||||
description: A list of IP address or IP network you want to whitelisted. It accepts both IPv4 and IPv6 IP address or network
|
||||
description: A list of IP addresses or an IP network you want allowlisted. It accepts both IPv4 and IPv6 IP address or network
|
||||
required: true
|
||||
type: list
|
||||
trusted_users:
|
||||
|
||||
@ -3,16 +3,16 @@ title: "Customizing entities"
|
||||
description: "Simple customization for entities."
|
||||
---
|
||||
|
||||
## Changing the entity_id
|
||||
## Changing the entity ID
|
||||
|
||||
You can use the UI to change the `entity_id` and friendly name of supported entities. To do this:
|
||||
You can use the UI to change the entity ID and friendly name of supported entities. To do this:
|
||||
|
||||
1. Select the entity, either from the frontend or by clicking the info button next to the entity in the Developer Tools "States" tab.
|
||||
2. Click on the cog in the right corner of the entity's dialog
|
||||
2. Click on the cog icon in the right corner of the entity's dialog
|
||||
3. Enter the new name or the new entity ID (remember not to change the domain of the entity - the part before the `.`)
|
||||
4. Select *Save*
|
||||
|
||||
If your entity is not supported, or you cannot customize what you need via this method, please see below for more options:
|
||||
If your entity is not supported, or you cannot customize what you need via this method, please see below for more options.
|
||||
|
||||
## Customizing entities
|
||||
|
||||
|
||||
@ -59,25 +59,3 @@ switch 1:
|
||||
switch 2:
|
||||
platform: vera
|
||||
```
|
||||
|
||||
## Grouping entities
|
||||
|
||||
Once you have several entities set up, it is time to organize them into groups.
|
||||
Each group consists of a name and a list of entity IDs. Entity IDs can be
|
||||
retrieved from the web interface by using the
|
||||
{% my developer_states title="States page in the Developer Tools" %}.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
group:
|
||||
living_room:
|
||||
entities:
|
||||
- light.table_lamp
|
||||
- switch.ac
|
||||
bedroom:
|
||||
entities:
|
||||
- light.bedroom
|
||||
- media_player.nexus_player
|
||||
```
|
||||
|
||||
For more details please check the [Group](/integrations/group/) page.
|
||||
|
||||
@ -183,6 +183,9 @@ This (large) sensor configuration gives us another example:
|
||||
|
||||
You'll notice that this example includes a secondary parameter section (under the steam section) as well as a better example of the way comments can be used to break down files into sections.
|
||||
|
||||
All of the above can be applied when splitting up files using packages. To
|
||||
learn more about packages, see the [Packages](/docs/configuration/packages) page.
|
||||
|
||||
That about wraps it up.
|
||||
|
||||
If you have issues checkout `home-assistant.log` in the configuration directory as well as your indentations. If all else fails, head over to our [Discord chat server][discord] and ask away.
|
||||
|
||||
@ -397,8 +397,8 @@ Examples using `iif`:
|
||||
{% endraw %}
|
||||
|
||||
- `as_datetime()` converts a string containing a timestamp, or valid UNIX timestamp, to a datetime object.
|
||||
- `as_timestamp(value, default)` converts datetime object or string to UNIX timestamp. If that fails, returns the `default` value, or if omitted `None`. This function also be used as a filter.
|
||||
- `as_local()` converts datetime object to local time. This function also be used as a filter.
|
||||
- `as_timestamp(value, default)` converts datetime object or string to UNIX timestamp. If that fails, returns the `default` value, or if omitted `None`. This function can also be used as a filter.
|
||||
- `as_local()` converts datetime object to local time. This function can also be used as a filter.
|
||||
- `strptime(string, format)` parses a string based on a [format](https://docs.python.org/3.8/library/datetime.html#strftime-and-strptime-behavior) and returns a datetime object. If that fails, returns the `default` value, or if omitted the unprocessed input value.
|
||||
- `relative_time` converts datetime object to its human-friendly "age" string. The age can be in second, minute, hour, day, month or year (but only the biggest unit is considered, e.g., if it's 2 days and 3 hours, "2 days" will be returned). Note that it only works for dates _in the past_.
|
||||
- `timedelta` returns a timedelta object and accepts the same arguments as the Python `datetime.timedelta` function -- days, seconds, microseconds, milliseconds, minutes, hours, weeks.
|
||||
@ -414,7 +414,7 @@ Examples using `iif`:
|
||||
|
||||
- Filter `timestamp_local(default)` converts a UNIX timestamp to the ISO format string representation as date/time in your local timezone. If that fails, returns the `default` value, or if omitted the unprocessed input value. If a custom string format is needed in the string, use `timestamp_custom` instead.
|
||||
- Filter `timestamp_utc(default)` converts a UNIX timestamp to the ISO format string representation representation as date/time in UTC timezone. If that fails, returns the `default` value, or if omitted the unprocessed input value. If a custom string format is needed in the string, use `timestamp_custom` instead.
|
||||
- Filter `timestamp_custom(format_string, local_time=True, default)` converts an UNIX timestamp to its string representation based on a custom format, the use of a local timezone is default. If that fails, returns the `default` value, or if omitted the unprocessed input value. Supports the standard [Python time formatting options](https://docs.python.org/3/library/time.html#time.strftime).
|
||||
- Filter `timestamp_custom(format_string, local=True, default)` converts an UNIX timestamp to its string representation based on a custom format, the use of a local timezone is default. If that fails, returns the `default` value, or if omitted the unprocessed input value. Supports the standard [Python time formatting options](https://docs.python.org/3/library/time.html#time.strftime).
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -23,13 +23,13 @@ Connect a keyboard and monitor to your device.
|
||||
|
||||
#### To reset a user's password, via the container command line
|
||||
|
||||
If you are running Home Assistant in a container, you can use the command line in the container with the `hass` command to change your password. The steps below refer to a Home Assistant container in Docker named `ha`. Note that while working in the container, commands will take a few moments to execute.
|
||||
If you are running Home Assistant in a container, you can use the command line in the container with the `hass` command to change your password. The steps below refer to a Home Assistant container in Docker named `homeassistant`. Note that while working in the container, commands will take a few moments to execute.
|
||||
|
||||
1. `docker exec -it ha bash` to open to the container command line
|
||||
1. `docker exec -it homeassistant bash` to open to the container command line
|
||||
2. `hass` to create a default user, if this is your first time using the tool
|
||||
3. `hass --script auth --config /config change_password existing_user new_password` to change the password
|
||||
4. `exit` to exit the container command line
|
||||
5. `docker restart ha` to restart the container
|
||||
5. `docker restart homeassistant` to restart the container
|
||||
|
||||
#### To reset a user's password, as an administrator via the web interface
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: "Instructions on how to setup MQTT Discovery within Home Assistant.
|
||||
logo: mqtt.png
|
||||
---
|
||||
|
||||
The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the [HTTP binary sensor](/integrations/http/#binary-sensor) and the [HTTP sensor](/integrations/http/#sensor). To prevent multiple identical entries if a device reconnects a unique identifier is necessary. Two parts are required on the device side: The configuration topic which contains the necessary device type and unique identifier and the remaining device configuration without the device type.
|
||||
The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the [HTTP binary sensor](/integrations/http/#binary-sensor) and the [HTTP sensor](/integrations/http/#sensor). To prevent multiple identical entries if a device reconnects, a unique identifier is necessary. Two parts are required on the device side: The configuration topic which contains the necessary device type and unique identifier, and the remaining device configuration without the device type.
|
||||
|
||||
Supported by MQTT discovery:
|
||||
|
||||
@ -314,6 +314,7 @@ The following software has built-in support for MQTT discovery:
|
||||
- [ecowitt2mqtt](https://github.com/bachya/ecowitt2mqtt)
|
||||
- [ESPHome](https://esphome.io)
|
||||
- [ESPurna](https://github.com/xoseperez/espurna)
|
||||
- [HASS.Agent](https://github.com/LAB02-Research/HASS.Agent)
|
||||
- [IOTLink](https://iotlink.gitlab.io) (starting with 2.0.0)
|
||||
- [MiFlora MQTT Daemon](https://github.com/ThomDietrich/miflora-mqtt-daemon)
|
||||
- [OpenMQTTGateway](https://github.com/1technophile/OpenMQTTGateway)
|
||||
@ -501,7 +502,7 @@ The entity id is automatically generated from the entity's name. All MQTT entity
|
||||
{
|
||||
"name":"My Super Device",
|
||||
"object_id":"device1",
|
||||
"state_topic": "homeassistant/sensor/device1/state",
|
||||
"state_topic": "homeassistant/sensor/device1/state"
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
@ -61,7 +61,7 @@ The Template Editor provides a way to quickly test templates prior to placing th
|
||||
|
||||
By default, this will contain sample code that illustrates how templates can be written and tested. This sample code can be removed and replaced with your own. You can restore the default example by pressing the "Reset to Demo Template" button beneath the code editor.
|
||||
|
||||
For more information about Jinja2, visit [Jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/).
|
||||
For more information about Jinja2, visit [Jinja2 documentation](https://jinja.palletsprojects.com/en/latest/templates/), and also read templating document [here](/docs/configuration/templating).
|
||||
|
||||
## Events
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ You need to have a compatible Z-Wave stick or module installed. The following de
|
||||
- Aeotec Z-Pi 7 (700 series)
|
||||
- ZWave.me Razberry Board (500 series)
|
||||
|
||||
If you are just starting out, we recommend that you purchase a 700 series controller to take advantage of the latest improvements. At the very least, you should purchase a [Z-Wave Plus](https://z-wavealliance.org/z-wave_plus_certification/) controller.
|
||||
If you are just starting out, we recommend that you purchase a 500 series controller. At the very least, you should purchase a [Z-Wave Plus](https://z-wavealliance.org/z-wave_plus_certification/) controller.
|
||||
|
||||
<div class='note'>
|
||||
Not all of the above devices are supported by the deprecated Z-Wave integration.
|
||||
|
||||
@ -34,6 +34,6 @@ Typically, you'll see this when you create entities manually using YAML, but it
|
||||
- Entity with a unique ID: Entity ID can be adjusted freely (as long as it follows the format `<domain>.<id>` and does not result in duplicates in your Home Assistant). Keep in mind that if you change the entity ID, you also need to update the references, e.g., in automations and dashboards.<br>
|
||||
- Entity without a unique ID: Entity ID is considered a fixed, static identifier and cannot be changed.
|
||||
|
||||
If your user profile has the "Advanced Mode" activated, you will also see the second paragraph in the popup with a link to the [customization user interface](/docs/configuration/customizing-devices/#customization-using-the-ui) for this specific entity, which offers some customization options.
|
||||
In case your entity has no unique ID and therefore cannot be changed through the UI, there are some [manual customization options](/docs/configuration/customizing-devices) directly through YAML files.
|
||||
|
||||
In case you want to read more about unique IDs, head over to this [developer documentation page](https://developers.home-assistant.io/docs/entity_registry_index/).
|
||||
|
||||
@ -74,6 +74,10 @@ Start it by running:
|
||||
docker-compose up -d
|
||||
```
|
||||
|
||||
Once the Home Assistant Container is running Home Assistant should be accessible using `http://<host>:8123` (replace <host> with the hostname or IP of the system). You can continue with onboarding.
|
||||
|
||||
{% include getting-started/next_step.html step="Onboarding" link="/getting-started/onboarding/" %}
|
||||
|
||||
### Exposing Devices
|
||||
|
||||
In order to use Z-Wave, Zigbee or other integrations that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your container instructions:
|
||||
|
||||
@ -132,10 +132,14 @@ Using a combination of the available services and attributes, you can create swi
|
||||
value_template: "{{ is_state_attr('alarm_control_panel.alarm_panel', 'chime', true) }}"
|
||||
turn_on:
|
||||
service: alarmdecoder.alarm_toggle_chime
|
||||
target:
|
||||
entity_id: alarm_control_panel.alarm_panel
|
||||
data:
|
||||
code: !secret alarm_code
|
||||
turn_off:
|
||||
service: alarmdecoder.alarm_toggle_chime
|
||||
target:
|
||||
entity_id: alarm_control_panel.alarm_panel
|
||||
data:
|
||||
code: !secret alarm_code
|
||||
icon_template: >-
|
||||
|
||||
@ -29,14 +29,15 @@ The `august` integration allows you to integrate your [August](https://august.co
|
||||
|
||||
| Device | Requires [Connect Bridge](https://august.com/products/august-connect/) or Doorbell |
|
||||
| --------------------------------- | ------------------------------------|
|
||||
| August Wi-Fi Smart Lock (Gen 4) | yes |
|
||||
| August Wi-Fi Smart Lock (Gen 4) | no |
|
||||
| August Smart Lock Pro (Gen 3) | yes |
|
||||
| August Smart Lock (Gen 2) | yes |
|
||||
| August Smart Lock (Gen 1) | no |
|
||||
| August Doorbell Cam (Gen 1, Gen2) | no |
|
||||
| August View | no |
|
||||
| Yale Assure Locks with August/Yale Connect Module | yes |
|
||||
| Yale Conexis L1 with August/Yale Connect Module | yes |
|
||||
| Yale Assure Lock | yes |
|
||||
| Yale Conexis L1 | yes |
|
||||
| Yale Linus | yes |
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -14,6 +14,9 @@ The `Blockchain` sensor platform displays Bitcoin wallet balances from [blockcha
|
||||
|
||||
To add the Blockchain sensor to your installation, specify a list of bitcoin addresses to watch in the `configuration.yaml` file. The sensor state will be the sum of the balances of all addresses listed.
|
||||
|
||||
Currently, the original Bitcoin address format is supported.
|
||||
For example, the newer Segwit and Taproot format are not supported.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
|
||||
@ -79,7 +79,7 @@ Pick an icon that you can find on [materialdesignicons.com](https://materialdesi
|
||||
|
||||
This integration will automatically restore the state it had prior to Home Assistant stopping as long as your entity has `restore` set to `true`, which is the default. To disable this feature, set `restore` to `false`.
|
||||
|
||||
If `restore` is set to `false`, the `initial` value will only be used when no previous state is found or when the counter is reset.
|
||||
If `restore` is set to `true`, the `initial` value will only be used when no previous state is found or when the counter is reset.
|
||||
|
||||
## Services
|
||||
|
||||
|
||||
@ -28,6 +28,10 @@ The way these sensors are displayed in the frontend can be modified in the [cust
|
||||
- **shutter**: Control of shutters, which are linked slats that swing out/in to covering an opening or may be tilted to partially cover an opening, such as indoor or exterior window shutters.
|
||||
- **window**: Control of a physical window that opens and closes or may tilt.
|
||||
|
||||
Here are a few examples of this representation in the UI:
|
||||
|
||||
<p class='img'><img src='/images/screenshots/cover_classes_icons.png' />Example of various device classes icons in `open` and `closed` state. The open image in this example has `state_color: true` specified in the Entities card configuration to receive the icon coloring.</p>
|
||||
|
||||
## Services
|
||||
|
||||
### Cover control services
|
||||
|
||||
@ -5,6 +5,7 @@ ha_category:
|
||||
- Climate
|
||||
- Sensor
|
||||
- Switch
|
||||
- Energy
|
||||
ha_release: 0.59
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
|
||||
@ -32,6 +32,7 @@ Known supported devices:
|
||||
- Denon AVR-X2300W
|
||||
- Denon AVR-X2400H
|
||||
- Denon AVR-X2500H
|
||||
- Denon AVR-X2600H
|
||||
- Denon AVR-X2700H
|
||||
- Denon AVR-X3000
|
||||
- Denon AVR-X3200W
|
||||
|
||||
@ -84,6 +84,10 @@ device:
|
||||
description: 'Identifier of a device that routes messages between this device and Home Assistant. Examples of such devices are hubs, or parent devices of a sub-device. This is used to show device topology in Home Assistant.'
|
||||
required: false
|
||||
type: string
|
||||
value_template:
|
||||
description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the value."
|
||||
required: false
|
||||
type: template
|
||||
{% endconfiguration %}
|
||||
|
||||
### Example
|
||||
|
||||
@ -33,3 +33,19 @@ Event listener callback URL:
|
||||
Poll for device availability:
|
||||
description: "Periodically try to connect to the DLNA device, even if it is unavailable. Enable this if SSDP advertisements sent by the device are not received by Home Assistant, e.g. when IP multicast is broken on your network."
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Services
|
||||
|
||||
DLNA devices can support a range of features. Depending on the device itself, the following [media_player](/integrations/media_player/#services) services may be supported:
|
||||
|
||||
* `media_player.volume_up`, `media_player.volume_down`, and `media_player.volume_set`
|
||||
* `media_player.volume_mute`
|
||||
* `media_player.media_play`
|
||||
* `media_player.media_pause` and `media_player.media_play_pause`
|
||||
* `media_player.media_stop`
|
||||
* `media_player.media_next_track`
|
||||
* `media_player.media_previous_track`
|
||||
* `media_player.play_media`
|
||||
* `media_player.shuffle_set`
|
||||
* `media_player.repeat_set`
|
||||
* `media_player.select_sound_mode`
|
||||
|
||||
@ -20,12 +20,14 @@ Compatible transceivers:
|
||||
|
||||
- [DIY](https://wiki.volkszaehler.org/hardware/controllers/ir-schreib-lesekopf-rs232-ausgang)
|
||||
- [Weidmann Elektronik Schreib-/Lesekopf USB](https://shop.weidmann-elektronik.de/index.php?page=product&info=24)
|
||||
- [USB IR Lesekopf EHZ Lese-Schreib-Kopf Volkszähler Hichi Smartmeter](https://www.ebay.de/itm/313455434998)
|
||||
|
||||
Tested smart meters:
|
||||
|
||||
- APATOR Norax 3D (enable InF Mode as described in manual to retrieve full data)
|
||||
- DZG DWS76 (enable InF as described in manual to retrieve full data)
|
||||
- Iskraemeco MT175 (ISKRA MT175-D2A51-V22-K0t)
|
||||
- EMH metering eHZ Generation K (enable InF as described in manual to retrieve full data)
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -56,12 +56,47 @@ partner:
|
||||
|
||||
### Supported features
|
||||
|
||||
Sensors:
|
||||
Sensors and associated attributes:
|
||||
|
||||
- eight_left/right_bed_state
|
||||
- Attributes:
|
||||
- Target Heating Level
|
||||
- Heating Active
|
||||
- Heating Time Remaining
|
||||
- eight left/right_sleep_fitness
|
||||
- Attributes:
|
||||
- Fitness Date
|
||||
- Fitness Duration Score
|
||||
- Fitness Asleep Score
|
||||
- Fitness Out-of-Bed Score
|
||||
- Fitness Wakeup Score
|
||||
- eight_left/right_sleep_session
|
||||
- Attributes:
|
||||
- Session Start
|
||||
- Tosses & Turns
|
||||
- Processing (True/False)
|
||||
- Time Slept (s)
|
||||
- Light Sleep %
|
||||
- Deep Sleep %
|
||||
- REM Sleep %
|
||||
- Respiratory Rate
|
||||
- Heart Rate
|
||||
- Sleep Stage
|
||||
- Room Temperature
|
||||
- Bed Temperature
|
||||
- eight_left/right_previous_sleep_session
|
||||
- Attributes:
|
||||
- Session Start
|
||||
- Tosses & Turns
|
||||
- Processing (True/False)
|
||||
- Time Slept (s)
|
||||
- Light Sleep %
|
||||
- Deep Sleep %
|
||||
- REM Sleep %
|
||||
- Average Respiratory Rate
|
||||
- Average Heart Rate
|
||||
- Average Room Temperature
|
||||
- Average Bed Temperature
|
||||
- eight_left/right_bed_temperature
|
||||
- eight_left/right_sleep_stage
|
||||
- eight_room_temperature
|
||||
@ -93,3 +128,7 @@ script:
|
||||
target: 35
|
||||
duration: 3600
|
||||
```
|
||||
|
||||
### Notice
|
||||
|
||||
Please note this component relies on an undocumented API utilized by the Eight Sleep mobile app to communicate with the Eight Sleep servers. It is not supported by Eight Sleep and may malfunction if changes are made to either the mobile app operation or the API format.
|
||||
|
||||
@ -123,26 +123,6 @@ The following is an example implementation of an automation:
|
||||
entity_id: media_player.amplifier
|
||||
```
|
||||
|
||||
## Selecting apps, channels, or favorites
|
||||
|
||||
Apps, channels, and favorites are exposed as media content to the integration. You can see which ones are available by clicking the media button in the media player more info card for your TV. To capture the `content_id` for the one you want to use in an automation or script, turn your logging on to debug level and tail the log while choosing the media content in the media player more info card. You will find a log message that looks like this when you choose the media:
|
||||
|
||||
```txt
|
||||
2021-11-22 01:45:14 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=media_player, service=play_media, service_data=entity_id=media_player.philips936_tv, media_content_id=com.amazon.ignition.IgnitionActivity-com.amazon.amazonvideo.livingroom, media_content_type=app>
|
||||
```
|
||||
|
||||
Then you can turn that into a service call for the script or automation like the following, which can then open the app/channel/favorite automatically.
|
||||
|
||||
```yaml
|
||||
service: media_player.play_media
|
||||
data:
|
||||
media_content_id: com.amazon.ignition.IgnitionActivity-com.amazon.amazonvideo.livingroom
|
||||
media_content_type: app
|
||||
target:
|
||||
entity_id:
|
||||
- media_player.philips936_tv
|
||||
```
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
If you change your advertised IP or ports, you will have to re-add the emulated Roku in your app.
|
||||
|
||||
@ -15,4 +15,6 @@ ha_platforms:
|
||||
|
||||
This integration allows you to control and monitor the artworks by [Evil Genius Labs](https://www.evilgeniuslabs.org/). Tested with the Fibonacci256.
|
||||
|
||||
If the integration is unable to connect, make sure the firmware is up to date.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -142,7 +142,7 @@ binary_sensor:
|
||||
required: true
|
||||
type: string
|
||||
pin:
|
||||
description: The digital or analog pin number on the board.
|
||||
description: The digital or analog pin number on the board. For analog pins the corresponding digital number must be used. Please use the pinout that corresponds to your board. For example, on the Arduino Uno, pin A2 corresponds to the digital pin number 16.
|
||||
required: true
|
||||
type: [integer, string]
|
||||
pin_mode:
|
||||
@ -232,7 +232,7 @@ firmata:
|
||||
negate: true
|
||||
- name: my_other_door
|
||||
pin_mode: INPUT
|
||||
pin: A1
|
||||
pin: 16 # A2
|
||||
negate: true
|
||||
sensors:
|
||||
- name: my_sensor
|
||||
|
||||
@ -31,14 +31,25 @@ This integration will provide local control over your LED lights/strips and can
|
||||
|
||||
Example of bulbs:
|
||||
|
||||
- [Flux Smart Lighting](https://www.fluxsmartlighting.com/)
|
||||
- [Flux WiFi Smart LED Light Bulb4](https://amzn.to/2X0dVwu)
|
||||
- [WIFI smart LED light Bulb1](https://amzn.to/2J2fksr)
|
||||
- [MagicLight Smart Bulbs](https://www.magiclightbulbs.com/lightbulbs) or [Amazon](https://www.amazon.com/gp/product/B081YJHHB1/)
|
||||
- [RGBCW Downlights](https://www.amazon.com/gp/product/B093Q83G7S/)
|
||||
- [RGBCW Floodlights](https://www.amazon.com/gp/product/B09J38NKPN)
|
||||
|
||||
Examples of controllers with strips:
|
||||
|
||||
- [MagicLight Strip Lights](https://www.magiclightbulbs.com/strip-lights) or [Amazon](https://www.amazon.com/gp/product/B08LPSS4J3/)
|
||||
|
||||
Examples of controllers:
|
||||
|
||||
- [Ledenet WiFi RGBW Controller](https://amzn.to/2WZKXNa)
|
||||
- [SUPERNIGHT WiFi Wireless LED Smart Controller](https://amzn.to/2WURx7w)
|
||||
- [Single color](https://www.amazon.com/gp/product/B07J5B3R5L/)
|
||||
- [RGB](https://www.amazon.com/gp/product/B07C1LN7FZ/)
|
||||
- [RGBW](https://www.amazon.com/gp/product/B07J9QCQNN/)
|
||||
- [RGBCW](https://www.amazon.com/gp/product/B09BMC4JNJ/)
|
||||
- [RGB/W/CW](https://www.amazon.com/gp/product/B01DY56N8U/)
|
||||
|
||||
Examples of addressable controllers:
|
||||
|
||||
- [Addressable v3](https://www.amazon.com/gp/product/B09BMBSCRF/)
|
||||
|
||||
These devices have been sold under at least the following brands:
|
||||
|
||||
@ -112,7 +123,6 @@ These devices have been sold under at least the following brands:
|
||||
|
||||
After the devices have been added they can be configured with different effects listed below. These settings can be accessed by navigating to the integration settings in Configuration -> Integrations and selecting the "Magic Home" configuration for the bulb or controller.
|
||||
|
||||
|
||||
**Custom Effect**\
|
||||
A list of RGB colors can be entered to create an effect. The effect speed can be adjusted using the slider underneath.
|
||||
|
||||
|
||||
@ -80,8 +80,10 @@ Recommended energy dashboard configuration for meter location in feed in path (`
|
||||
|
||||
- For `Grid consumption` use the meters `Energy real consumed` entity.
|
||||
- For `Return to grid` use the meters `Energy real produced` entity.
|
||||
- For `Solar production` add each inverters `Energy total` entity.
|
||||
- `Battery systems` aren't supported directly. Use [Riemann sum](/integrations/integration/) with negative values of `Power battery` entity (from power_flow endpoint found in your `SolarNet` device) for charging and positive values for discharging.
|
||||
- For `Solar production`:
|
||||
- If no battery is connected to an inverter: Add each inverters `Energy total` entity.
|
||||
- If a battery is connected to an inverter: Use [Riemann sum](/integrations/integration/) over `Power photovoltaics` entity (from power_flow endpoint found in your `SolarNet` device)
|
||||
- `Battery systems` aren't supported directly. Use [Template](/integrations/template) to split and invert negative values of `Power battery` entity (from power_flow) for charging power (W) and positive values for discharging power (W). Then use [Riemann sum](/integrations/integration/) to integrate each into energy values (kWh).
|
||||
- For `Devices` use the Ohmpilots `Energy consumed` entity.
|
||||
|
||||
## Note
|
||||
|
||||
@ -21,12 +21,12 @@ about major droughts, earthquakes, floods, tropical cyclones, tsunamis and
|
||||
volcanic activities worldwide.
|
||||
It retrieves alerts from a feed and shows information of those alerts filtered
|
||||
by distance to Home Assistant's location.
|
||||
The filter is set in the configuration as categories, radius (kilometers or miles based on unit system set in Home Assistant), latitude and longatude.
|
||||
|
||||
Entities are generated, updated and removed automatically with each update
|
||||
from the feed. Each entity defines latitude and longitude and will be shown
|
||||
on the default map automatically, or on a map card by defining the source
|
||||
`gdacs`. The distance is available as the state of each entity, and
|
||||
converted to the unit (kilometers or miles) configured in Home Assistant.
|
||||
`gdacs`. The distance is available as the state of each entity converted to the configured unit system (kilometers or miles).
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/gdacs-alerts-feed-map.png' />
|
||||
|
||||
@ -47,6 +47,9 @@ If you are trying to switch to a new Google account then you would run into the
|
||||
|
||||
'oauth2client.client.HttpAccessTokenRefreshError: deleted_client: The OAuth client was deleted'
|
||||
|
||||
In case you get an `Authentication code expired, please restart Home-Assistant and try again` error message, switch your timezone to `Etc/GMT` and restart Home Assistant. This should fix the issue and the `google_calendars.yaml` configuration file will be created.
|
||||
You can then switch back the timezone to your original one and restart Home Assistant again.
|
||||
|
||||
## Configuration
|
||||
|
||||
To integrate Google Calendar in Home Assistant,
|
||||
|
||||
@ -65,6 +65,10 @@ icon:
|
||||
|
||||
By default when any member of a group is `on` then the group will also be `on`. Similarly with a device tracker, when any member of the group is `home` then the group is `home`. If you set the `all` option to `true` though, this behavior is inverted and all members of the group have to be `on` for the group to turn on as well.
|
||||
|
||||
## Group state update
|
||||
|
||||
The group's state is updated when any group member's state is updated. Calling `homeassistant.update_entity` with the target set to the group will not be forwarded to the group members, instead the `expand()` template function can be used to force all group members to update state.
|
||||
|
||||
## Group state calculation
|
||||
|
||||
The system can calculate group state with entities from the following domains:
|
||||
|
||||
@ -545,6 +545,10 @@ You can also try to use `avahi-daemon` in reflector mode together with the optio
|
||||
|
||||
Configure the network mode as `networkbridge`. Otherwise the Home Assistant Bridge won't be exposed to the network.
|
||||
|
||||
#### Accessory does not appear in the Home App (for pairing) - Libvirt QEMU/KVM virtual machine with macvtap adapter
|
||||
|
||||
Please see the [Zero-configuration networking](/integrations/zeroconf/#troubleshooting) integration for more details.
|
||||
|
||||
#### Pairing hangs - zeroconf error
|
||||
|
||||
Pairing eventually fails, you might see the error message, `NonUniqueNameException`, you likely need to enable `default_interface: true` in the `zeroconf` integration configuration and set a unique name such as `name: MyHASS42`.
|
||||
|
||||
@ -450,7 +450,7 @@ lock:
|
||||
- platform: template
|
||||
name: Basedoor
|
||||
unique_id: basedoor
|
||||
value_template: "{{ state_attr('homematic.ccu2', 'base_lock_status') }}"
|
||||
value_template: "{{ is_state('sensor.lock_status', 'locked') }}"
|
||||
lock:
|
||||
service: homematic.set_device_value
|
||||
data:
|
||||
@ -469,9 +469,6 @@ lock:
|
||||
|
||||
{% endraw %}
|
||||
|
||||
To get the current value of the current lock status, you have to create a system variable (in the example above it is `base_lock_status`) and create a program on CCU, which updates the variable with every change of the Lock level to `true` for locked and `false` for unlocked.
|
||||
|
||||
|
||||
#### Detecting lost connections
|
||||
|
||||
When the connection to your Homematic CCU or Homegear is lost, Home Assistant will stop getting updates from devices. This may happen after rebooting the CCU for example. Due to the nature of the communication protocol this cannot be handled automatically, so you must call *homematic.reconnect* in this case. That's why it is usually a good idea to check if your Homematic integrations are still updated properly, in order to detect connection losses. This can be done in several ways through an automation:
|
||||
|
||||
@ -45,7 +45,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- Sensor
|
||||
- Switch
|
||||
|
||||
Home Assistant is capable of communicating with any binary sensor, cover, fan, light, lock, sensor and switch that is configured on the controller. Using the programs on the controller, custom binary sensors, cover, fan, lock, and switches can also be created.
|
||||
Home Assistant is capable of communicating with any binary sensor, cover, fan, light, lock, sensor and switch that is configured on the controller. Using the programs on the controller, custom binary sensors, covers, fans, locks, and switches can also be created.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -67,20 +67,20 @@ host:
|
||||
required: true
|
||||
type: string
|
||||
username:
|
||||
description: The username that used to access the ISY interface.
|
||||
description: The username that is used to access the ISY interface.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password that used to access the ISY interface.
|
||||
description: The password that is used to access the ISY interface.
|
||||
required: true
|
||||
type: string
|
||||
sensor_string:
|
||||
description: This is the string that is used to identify which devices are to be assumed to be sensors instead of lights of switches. If this string is found in the device name or folder, Home Assistant will assume it is as a sensor or binary sensor (if the device has on/off or true/false states). This is only necessary for nodes that are not automatically detected as sensors by Home Assistant. Insteon door, window, motion and leak sensors should all be detected automatically.
|
||||
description: This is the string that is used to identify which devices are to be assumed to be sensors instead of lights or switches. If this string is found in the device name or folder, Home Assistant will assume it is a sensor or binary sensor (if the device has on/off or true/false states). This is only necessary for nodes that are not automatically detected as sensors by Home Assistant. Insteon door, window, motion and leak sensors should all be detected automatically.
|
||||
required: false
|
||||
type: string
|
||||
default: sensor
|
||||
variable_sensor_string:
|
||||
description: This is the string that is used to identify which Integer or State Variables are to be added as sensors. If this string is found in the device name, Home Assistant will assume it is as a sensor.
|
||||
description: This is the string that is used to identify which Integer or State Variables are to be added as sensors. If this string is found in the device name, Home Assistant will assume it is a sensor.
|
||||
required: false
|
||||
type: string
|
||||
default: sensor
|
||||
@ -149,7 +149,7 @@ All `isy994_control` events will have an `entity_id` and `control` parameter in
|
||||
|
||||
### Insteon Scenes & Keypad/Remote Buttons
|
||||
|
||||
All Insteon scenes configured in the ISY994 will show up as a `switch` in Home Assistant, as they do not support dimming or setting specific brightness settings as Home Assisstant's `light` component.
|
||||
All Insteon scenes configured in the ISY994 will show up as a `switch` in Home Assistant, as they do not support dimming or setting specific brightness settings as Home Assistant's `light` component.
|
||||
|
||||
Insteon Secondary Keypad buttons and Remote buttons are added to Home Assistant to allow support for using Control Events in Automations. These devices are added as `sensors` since they cannot be directly controlled (turned on/off); their state is the last ON level command they sent, in a range from `0` (Off) to `255` (On 100%). Note: these devices may report incorrect states before being used after a reboot of the ISY. Secondary Keypad buttons may be turned on or off using ISY Scenes (refer to ISY Documentation for more details).
|
||||
|
||||
@ -167,7 +167,7 @@ Send a command to an ISY Device using its Home Assistant entity ID. Valid comman
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | Name(s) of entities to send the command, e.g., `light.front_porch`. |
|
||||
| `entity_id` | no | Name(s) of target entities for the command, e.g., `light.front_porch`. |
|
||||
| `command` | no | The command to be sent to the device, e.g., `"fast_on"` |
|
||||
|
||||
#### Service `isy994.send_raw_node_command`
|
||||
@ -176,7 +176,7 @@ Send a "raw" (e.g., `DON`, `DOF`) ISY REST Device Command to a Node using its Ho
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | Name(s) of entities to send the command, e.g., `light.front_porch`. |
|
||||
| `entity_id` | no | Name(s) of target entities for the command, e.g., `light.front_porch`. |
|
||||
| `command` | no | The ISY REST Command to be sent to the device, e.g., `"DON"` |
|
||||
| `value` | yes | The integer value to be sent with the command, if required by the command, e.g., `255` |
|
||||
| `parameters` | yes | A `dict` of parameters to be sent in the query string for controlling colored bulbs or advanced parameters, e.g., `{ GV2: 0, GV3: 0, GV4: 255 }` |
|
||||
@ -188,7 +188,7 @@ Request a Z-Wave Device parameter via the ISY. The parameter value will be retur
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------------------------------------------------------------------------------------------- |
|
||||
| `entity_id` | no | Name of entity to send the command, e.g., `light.front_porch`. This must be an ISY Z-Wave Node. |
|
||||
| `entity_id` | no | Name of target entity for the command, e.g., `light.front_porch`. This must be an ISY Z-Wave Node. |
|
||||
| `parameter` | no | The parameter number to retrieve from the end device. |
|
||||
|
||||
#### Service `isy994.set_zwave_parameter`
|
||||
@ -197,7 +197,7 @@ Update a Z-Wave Device parameter via the ISY. The parameter value will also be r
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------------------------------------------------------------------------------------------- |
|
||||
| `entity_id` | no | Name of entity to send the command, e.g., `light.front_porch`. This must be an ISY Z-Wave Node. |
|
||||
| `entity_id` | no | Name of target entity for the command, e.g., `light.front_porch`. This must be an ISY Z-Wave Node. |
|
||||
| `parameter` | no | The parameter number to set on the end device. |
|
||||
| `value` | no | The value to set for the parameter. May be an integer or byte string (e.g. "0xFFFF"). |
|
||||
| `size` | no | The size of the parameter, either 1, 2, or 4 bytes. |
|
||||
@ -208,7 +208,7 @@ Rename a node or group (scene) on the ISY994. Note: this will not automatically
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | -------------------------------------------------------------- |
|
||||
| `entity_id` | no | Name of entity to send the command, e.g., `light.front_porch`. |
|
||||
| `entity_id` | no | Name of target entity for the command, e.g., `light.front_porch`. |
|
||||
| `name` | no | The new name to use within the ISY994. |
|
||||
|
||||
#### Service `isy994.set_on_level`
|
||||
@ -217,7 +217,7 @@ Send an ISY set_on_level command to a `light` Node to set the devices' local On
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | Name(s) of entities to send the command, e.g., `light.front_porch`. |
|
||||
| `entity_id` | no | Name(s) of target entities for the command, e.g., `light.front_porch`. |
|
||||
| `value` | no | The integer value to set the On Level to in a range of 0-255, e.g., `255` |
|
||||
|
||||
#### Service `isy994.set_ramp_rate`
|
||||
@ -226,7 +226,7 @@ Send an ISY set_ramp_rate command to a `light` Node to set the devices' ramp rat
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | Name(s) of entities to send the command, e.g., `light.front_porch`. |
|
||||
| `entity_id` | no | Name(s) of target entities for the command, e.g., `light.front_porch`. |
|
||||
| `value` | no | The integer index value to set the Ramp Rate to in a range of `0` (9.5 minutes) to `31` (0.1 Seconds), e.g., `28` |
|
||||
|
||||
#### Service `isy994.system_query`
|
||||
@ -330,13 +330,17 @@ A device is created by creating a directory, with the name for the device, under
|
||||
- *HA.lock* will create a lock.
|
||||
- *HA.switch* will create a switch.
|
||||
|
||||
A program, named *status*, is required under the program device directory. A program, named *actions*, is required for all program devices except for binary_sensor. Any other programs in these device directories will be ignored. The *status* program requires that you create a variable with the name of your choice. This variable will store the actual status of the new device and will be updated by the *action* program.
|
||||
A program, named *status*, is required under the program device directory. A program, named *actions*, is required for all program devices except for binary_sensor. Any other programs in these device directories will be ignored.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/isy994/isy994_CoverExample.png' />
|
||||
</p>
|
||||
|
||||
The *status* program in this directory is what indicates the state of the device:
|
||||
The *status* program requires that you create a state variable with the name of your choice. Note that you must use a state variable, not an integer variable. This variable will store the actual status of the new device and will be updated by the *action* program.
|
||||
|
||||
|
||||
|
||||
The IF clause of the *status* program in the device directory is what indicates the state of the device:
|
||||
|
||||
- *binary_sensor* on if the clause returns true, otherwise off.
|
||||
- *cover* closed if the clause returns true, otherwise open.
|
||||
|
||||
@ -9,7 +9,7 @@ ha_quality_scale: internal
|
||||
ha_domain: group
|
||||
---
|
||||
|
||||
The group light platform lets you combine multiple lights into one entity. All child lights of a light group can still be used as usual, but controlling the state of the grouped light will forward the command to each child light.
|
||||
The light group platform lets you combine multiple lights into one entity. All child lights of a light group can still be used as usual, but controlling the state of the grouped light will forward the command to each child light.
|
||||
|
||||
To enable this platform in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ Most lights do not support all attributes. You can check the integration documen
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all the lights use `all` as `entity_id`.
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all lights, set `entity_id` to `all`.
|
||||
| `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state.
|
||||
| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color, brightness and a transition value (if no transition is desired, set to 0 or leave out the column entirely). If a profile is given, and a brightness is set, then the profile brightness will be overwritten.
|
||||
| `hs_color` | yes | A list containing two floats representing the hue and saturation of the color you want the light to be. Hue is scaled 0-360, and saturation is scaled 0-100.
|
||||
@ -107,7 +107,7 @@ Turns one or multiple lights off.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all the lights use all as `entity_id`.
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all lights, set `entity_id` to `all`.
|
||||
| `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds.
|
||||
|
||||
### Service `light.toggle`
|
||||
|
||||
@ -40,6 +40,8 @@ Please note that "-" characters need to be included in the key when providing it
|
||||
<img src='/images/integrations/motion_blinds/Motion_App__get_key_2.jpg' />
|
||||
</p>
|
||||
|
||||
Note that it has been reported that the official Bloc Blinds app doesn't seem to hand out the API key on Android, it does seem to provide the API key on the iOS version of the official Bloc Blinds app.
|
||||
|
||||
## Top Down Bottom Up (TDBU) blinds
|
||||
|
||||
TDBU blinds consist of two bars controlled by two motors designated by Top and Bottom with fabric in between.
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Local Push
|
||||
ha_domain: mqtt_statestream
|
||||
---
|
||||
|
||||
The `mqtt_statestream` integration publishes state changes in Home Assistant to individual MQTT topics.
|
||||
The `mqtt_statestream` integration publishes state changes in Home Assistant to individual MQTT topics. [The MQTT integration](/integrations/mqtt/) is a prerequisite for MQTT Statestream to work.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -41,6 +41,12 @@ The Nest Smart Device Management (SDM) API **requires a US$5 fee**.
|
||||
|
||||
</div>
|
||||
|
||||
## Video Walkthrough
|
||||
|
||||
<div class='videoWrapper'>
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/wghcd9xDdMs" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
## Device Access Registration
|
||||
|
||||
For the first phase, you will turn on the API and create the necessary credentials to have Home Assistant talk to the Nest API.
|
||||
|
||||
@ -233,7 +233,7 @@ client_secret:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
**After the client_id and client_secret is added to your `configuration.yaml` you must enable Netatmo through the integrations page.**
|
||||
**After the `client_id` and `client_secret` are added to your `configuration.yaml` you must restart Home Assistant and then enable Netatmo through the integrations page.**
|
||||
|
||||
Menu: **Configuration** -> **Devices & Services**.
|
||||
|
||||
|
||||
@ -22,6 +22,7 @@ This platform allows you to detect presence by looking at connected devices to a
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
Most NETGEAR routers use port 5000 to communicate, however the following list of models are known to use port 80:
|
||||
- Nighthawk RAX50
|
||||
- Nighthawk X4S - AC2600 (R7800)
|
||||
- Orbi
|
||||
- XR500
|
||||
|
||||
@ -125,4 +125,24 @@ icon:
|
||||
auth: "digest"
|
||||
```
|
||||
|
||||
Example of an automation with an service call, full configuration:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
service: notify.living_room_tv
|
||||
data:
|
||||
title: "Thanks for the water!"
|
||||
message: "Nigel is {{ states('sensor.nigel_moisture') }}% moisture"
|
||||
data:
|
||||
duration: 4
|
||||
position: "bottom-left"
|
||||
fontsize: "medium"
|
||||
transparency: "80%"
|
||||
color: "teal"
|
||||
interrupt: 0
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Please note that `path` is validated against the `allowlist_external_dirs` in the `configuration.yaml`.
|
||||
|
||||
@ -54,6 +54,6 @@ port:
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
This integration relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with this component, `module-native-protocol` must be loaded on the PulseAudio server.
|
||||
This integration relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with this component, `module-native-protocol-tcp auth-ip-acl=<homeassistant ip>` must be loaded on the PulseAudio server.
|
||||
|
||||
</div>
|
||||
|
||||
@ -219,14 +219,16 @@ Note that purging will not immediately decrease disk space usage but it will sig
|
||||
|
||||
### Service `purge_entities`
|
||||
|
||||
Call the service `recorder.purge_entities` to start a task that purges events and states from the recorder database that match any of the specified `entity_id`, `domains` and `entity_globs` fields. Note: leaving all three parameters empty will result in all entities being selected for purging.
|
||||
Call the service `recorder.purge_entities` to start a task that purges events and states from the recorder database that match any of the specified `entity_id`, `domains` and `entity_globs` fields. Leaving all three parameters empty will result in all entities being selected for purging.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `entity_id` | yes | A list of entity_ids that should be purged from the recorder database. |
|
||||
| `entity_id` | yes<sup>*</sup> | A list of entity_ids that should be purged from the recorder database. |
|
||||
| `domains` | yes | A list of domains that should be purged from the recorder database. |
|
||||
| `entity_globs` | yes | A list of regular expressions that identify entities to purge from the recorder database. |
|
||||
|
||||
Note: The `entity_id` is only optional when used in `automations.yaml` or `scripts.yaml`. When using the UI to call this service then it is mandatory to specify at least one `entity_id` using the Target Picker or via YAML mode.
|
||||
|
||||
### Service `disable`
|
||||
|
||||
Call the service `recorder.disable` to stop saving events and states to the database.
|
||||
|
||||
@ -102,7 +102,9 @@ See [Generate codes](#generate-codes) how to generate event codes.
|
||||
|
||||
#### Somfy RTS
|
||||
|
||||
The [RFXtrx433e](http://www.rfxcom.com/RFXtrx433E-USB-43392MHz-Transceiver/en) or later versions like [RFXtrx433XL](http://www.rfxcom.com/epages/78165469.sf/en_GB/?ObjectPath=/Shops/78165469/Products/18103) is required for support, however, it does not support receive for the Somfy RTS protocol - as such devices cannot be automatically added. Instead, configure the device in the [rfxmngr](http://www.rfxcom.com/downloads.htm) tool. Make a note of the assigned ID and Unit Code and then add a device to the configuration with the following id `071a0000[id][unit_code]`. E.g., if the id was `0a` `00` `01`, and the unit code was `01` then the fully qualified id would be `071a00000a000101`, if you set your id/code to single digit in the rfxmngr, e.g., id: `1` `02` `04` and unit code: `1` you will need to add `0` before, so `102031` becomes `071a000001020301`.
|
||||
The [RFXtrx433e](http://www.rfxcom.com/RFXtrx433E-USB-43392MHz-Transceiver/en) or later versions like [RFXtrx433XL](http://www.rfxcom.com/epages/78165469.sf/en_GB/?ObjectPath=/Shops/78165469/Products/18103) is required for support, however, it does not support receive for the Somfy RTS protocol - as such devices cannot be automatically added. Instead, configure the device in the [rfxmngr](http://www.rfxcom.com/downloads.htm) tool. Make a note of the assigned ID and Unit Code and then add a device to the configuration with the following id `071a0000[id][unit_code]`. E.g., if the id was `0a` `00` `01`, and the unit code was `01` then the fully qualified id would be `071a00000a000101`, if you set your id/code to single digit in the rfxmngr, e.g., id: `1` `02` `03` and unit code: `1` you will need to add `0` before, so `102031` becomes `071a000001020301`.
|
||||
|
||||
To add the device, enter the value unaltered in the Event Code field, and click Submit.
|
||||
|
||||
#### Convert switch event to dimming event
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ The `roomba` integration allows you to control your [iRobot Roomba](https://www.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
This integration has been tested and confirmed to be working with the iRobot Roomba s9+, Roomba 980, Roomba 960, Roomba 890, and Braava jet m6 models, but should also work fine with any Wi-Fi enabled Roomba or Braava like the 690. For auto-discovery, you will need to initiate a Roomba reboot. For example, by holding the clean button for up to 20 seconds on an i7 or 980. [More information about rebooting your robot](https://homesupport.irobot.com/app/answers/detail/a_id/9087/~/rebooting-or-resetting-your-robot).
|
||||
This integration has been tested and confirmed to be working with the iRobot Roomba s9+, Roomba 980, Roomba 960, Roomba 890, and Braava jet m6 models, but should also work fine with any Wi-Fi enabled Roomba or Braava like the 690. For auto-discovery, you will need to initiate a Roomba reboot. For example, by holding the clean button for up to 20 seconds on an i7 or 980. [More information about rebooting your robot](https://homesupport.irobot.com/s/article/9087).
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -34,10 +34,10 @@ Sensors are added for both usage and production:
|
||||
- Usage: Current active power usage in Watts.
|
||||
- Production: Current active power production in Watts.
|
||||
- Trend sensors: Data provided for daily, weekly, monthly and yearly scales. Updated every 5 minutes.
|
||||
- Usage: Power usage in kWh.
|
||||
- Production: Power production in kWh.
|
||||
- To Grid: Power exported to the grid in kWh.
|
||||
- From Grid: Power imported from the grid in kWh.
|
||||
- Usage: Energy usage in kWh.
|
||||
- Production: Energy production in kWh.
|
||||
- To Grid: Energy exported to the grid in kWh.
|
||||
- From Grid: Energy imported from the grid in kWh.
|
||||
- Net Production: Measures total solar production against usage.
|
||||
- Net Production Percentage: Net production as a percentage value.
|
||||
- Solar Powered Percentage: Percentage of power used directly from solar.
|
||||
|
||||
@ -271,7 +271,7 @@ sensor:
|
||||
|
||||
{% endraw %}
|
||||
|
||||
### Fetch multiple JSON values and present them as attributes
|
||||
### Fetch multiple JSON attributes and present them as values
|
||||
|
||||
[JSON Test](https://www.jsontest.com/) returns the current time, date and milliseconds since epoch from [http://date.jsontest.com/](http://date.jsontest.com/).
|
||||
|
||||
|
||||
@ -44,10 +44,12 @@ Any service data passed into the service call to activate the shell command will
|
||||
The `command` is executed within the [configuration directory](/docs/configuration/).
|
||||
|
||||
<div class='note'>
|
||||
If you are using [Home Assistant operating system](https://github.com/home-assistant/operating-system), the commands are executed in the `homeassistant` container context. So if you test or debug your script, it might make sense to do this in the context of this container to get the same runtime environment.
|
||||
|
||||
If you are using [Home Assistant Operating System](https://github.com/home-assistant/operating-system), the commands are executed in the `homeassistant` container context. So if you test or debug your script, it might make sense to do this in the context of this container to get the same runtime environment.
|
||||
|
||||
</div>
|
||||
|
||||
With a `0` exit code, the output (stdout) of the command is used as `value`. In case a command results in a non `0` exit code or is terminated by the `command_timeout`, the result is only logged to Home Assistant log and the value of the sensor is not updated.
|
||||
With a `0` exit code, the output (stdout) of the command is used as `value`. In case a command results in a non `0` exit code or is terminated after a timeout of 60 seconds, the result is only logged to Home Assistant log and the value of the sensor is not updated.
|
||||
|
||||
## Examples
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: Integrate Shelly devices
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Cover
|
||||
- Energy
|
||||
- Light
|
||||
- Sensor
|
||||
- Switch
|
||||
@ -79,6 +80,16 @@ The integration uses the following strategy to name its entities:
|
||||
- If `Channel Name` is set in the device, the integration will use it to generate the entities' name, e.g. `Kitchen Light`
|
||||
- If `Channel Name` is set to the default value, the integration will use the `Device ID` and default channel name to generate the entities' name, e.g. `ShellyPro4PM-9808D1D8B912 switch_0`.
|
||||
|
||||
## Binary input sensors
|
||||
|
||||
### Binary input sensors (generation 1)
|
||||
|
||||
Depending on how a device's button type is configured, the integration will create binary sensors corresponding to those inputs. binary sensors are not created when the button type is `momentary` or `momentary_on_release`, for these types you need to use events for your automations.
|
||||
|
||||
### Binary input sensors (generation 2)
|
||||
|
||||
For generation 2 hardware it's possible to select if a device's input is connected to a button or a switch. Binary sensors are created only if the input mode is set to `switch`. When the input is of type `button` you need to use events for your automations.
|
||||
|
||||
## Events
|
||||
|
||||
If the **BUTTON TYPE** of the switch connected to the device is set to `momentary` or `detached switch`, integration fires events under the type `shelly.click` when the switch is used. You can use these events in your automations.
|
||||
|
||||
@ -108,7 +108,7 @@ Note that the SQL sensor state corresponds to the last row of the SQL result set
|
||||
|
||||
Based on previous example with temperature, the query to get the former state is :
|
||||
```sql
|
||||
SELECT * FROM (SELECT * FROM states WHERE entity_id = 'sensor.temperature_in' ORDER BY state_id DESC LIMIT 2) two_entity ORDER BY state_id ASC LIMIT 1;
|
||||
SELECT * FROM (SELECT * FROM states WHERE entity_id = 'sensor.temperature_in' ORDER BY state_id DESC LIMIT 2) two_entity ORDER BY state_id ASC LIMIT 1;
|
||||
```
|
||||
Thus in yaml
|
||||
```yaml
|
||||
@ -117,7 +117,7 @@ sensor:
|
||||
- platform: sql
|
||||
queries:
|
||||
- name: Former_Temperature_In
|
||||
query: "SELECT * FROM (SELECT state FROM states WHERE entity_id = 'sensor.temperature_in' ORDER BY state_id DESC LIMIT 2) two_entity ORDER BY state_id ASC LIMIT 1;"
|
||||
query: "SELECT * FROM (SELECT state, state_id FROM states WHERE entity_id = 'sensor.temperature_in' ORDER BY state_id DESC LIMIT 2) two_entity ORDER BY state_id ASC LIMIT 1;"
|
||||
column: "state"
|
||||
```
|
||||
|
||||
|
||||
@ -56,7 +56,7 @@ switches:
|
||||
description: The name used to display the switch in the frontend.
|
||||
required: false
|
||||
type: string
|
||||
icon:
|
||||
icon_template:
|
||||
description: Defines a template for the icon of the entity.
|
||||
required: false
|
||||
type: template
|
||||
|
||||
@ -33,4 +33,4 @@ In the frontend open the sidebar. At the bottom, under **Developer Tools**, clic
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | The entity ID of the switch to control. To target all switches, set the entity ID to `all`|
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`s of switches. To target all switches, set `entity_id` to `all`.
|
||||
|
||||
@ -15,11 +15,9 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The Samsung SyncThru Printer platform allows you to read current data from your local Samsung printer.
|
||||
The Samsung SyncThru Printer platform allows Home Asssitant to read current data from a local Samsung printer.
|
||||
|
||||
It usually provides information about the device's state, the left amount of ink or toner and the state of paper trays.
|
||||
|
||||
The following information is displayed in separate sensors, if it is available:
|
||||
Depending on device abilities, the following separate sensors are created if supported:
|
||||
|
||||
- Whether the printer is online
|
||||
- Whether the printer is in an error state
|
||||
@ -28,4 +26,6 @@ The following information is displayed in separate sensors, if it is available:
|
||||
- First to fifth paper input tray state
|
||||
- First to sixth paper output tray state
|
||||
|
||||
In order for a device to be discovered automatically, SSPD / UPnP (under Network settings) must be enabled.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -8,7 +8,7 @@ ha_quality_scale: internal
|
||||
ha_domain: system_log
|
||||
---
|
||||
|
||||
The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Configuration** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
|
||||
The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Configuration** -> **Settings** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -90,6 +90,17 @@ tmpfs 934M 0 934M 0% /dev/shm
|
||||
|
||||
Defining a `disk_use` sensor for `/` and `/home/pi` is redundant and will return the same values, since they both belong to the same "disk". However, defining separate sensors for `/dev` and `/dev/shm` is possible and provides different values, since those are treated as separate "disks" by the integration.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: systemmonitor
|
||||
resources:
|
||||
- type: disk_use
|
||||
arg: /dev
|
||||
- type: disk_use
|
||||
arg: /dev/shm
|
||||
```
|
||||
|
||||
## Processor temperature
|
||||
|
||||
- If no hardware sensor data is available (e.g., because the integration runs in a virtualized environment), the sensor entity will not be created.
|
||||
|
||||
@ -21,6 +21,10 @@ The Tailscale integration integrates the [Tailscale](https://www.tailscale.com)
|
||||
with Home Assistant; giving you the possibility to monitor and automate on
|
||||
the state of the devices in your Tailscale VPN network (Tailnet).
|
||||
|
||||
Please, note that this integration integrates with data from the Tailscale API,
|
||||
it is not a Tailscale client itself, and thus add Home Assistant to your
|
||||
Tailscale VPN network.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
To use the Tailscale integration, you will need to obtain an API key,
|
||||
|
||||
@ -17,7 +17,7 @@ When a timer finishes or gets canceled the corresponding events are fired. This
|
||||
</div>
|
||||
|
||||
## Configuration
|
||||
The preferred way to configure timer helpers is via the user interface. To add one, go to Configuration -> Helpers and click the add button; next choose the “Timer” option.
|
||||
The preferred way to configure timer helpers is via the user interface. To add one, go to Configuration -> Automations & Scenes, select the "Helpers" tab and click the add button; next choose the “Timer” option.
|
||||
|
||||
You can also click the following button to be redirected to the Helpers page of your Home Assistant instance.
|
||||
|
||||
|
||||
@ -77,7 +77,7 @@ This is a separate account from the one you made for the app. You cannot log in
|
||||
|
||||
4. Click `Confirm` in the app.
|
||||
5. To confirm that everything worked, navigate to the `All Devices` tab. Here you should be able to find the devices from the app.
|
||||
6. If zero devices are imported, try changing the DataCenter.
|
||||
6. If zero devices are imported. Try changing the DataCenter and check the account used is the "Home Owner".
|
||||
|
||||
|
||||
|
||||
@ -100,10 +100,10 @@ Click the created project to enter the `Project Overview` page and get the `Auth
|
||||
description: Go to your cloud project on [Tuya IoT Platform](https://iot.tuya.com/). Find the **Access Secret** under [Authorization Key](#get-authorization-key) on the **Project Overview** tab.
|
||||
|
||||
Account:
|
||||
description: Tuya Smart or Smart Life app account.
|
||||
description: Tuya Smart or Smart Life **app** account.
|
||||
|
||||
Password:
|
||||
description: The password of your app account.
|
||||
description: The password of your **app** account.
|
||||
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
|
||||
@ -143,3 +143,59 @@ data:
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
### Activating a preset
|
||||
|
||||
Activating a preset is an easy way to set a WLED light to a specific
|
||||
configuration. Here is an example service call to set a WLED light
|
||||
to a preset called My Preset:
|
||||
|
||||
```yaml
|
||||
- service: light.turn_on
|
||||
target:
|
||||
entity_id: light.wled
|
||||
- service: select.select_option
|
||||
target:
|
||||
entity_id: select.wled_preset
|
||||
data:
|
||||
option: "My Preset"
|
||||
```
|
||||
|
||||
### Automation Using Specific Palette Name
|
||||
|
||||
An automation to turn on a WLED light and select a specific palette and
|
||||
set intensity, and speed can be created by first calling the `light.turn_on`
|
||||
service, then calling the `select.select_option` service to select the
|
||||
palette, then call the `number.set_value` service to set the intensity
|
||||
and again to set the speed.
|
||||
|
||||
Here is an example of all of these put together into an automation:
|
||||
|
||||
```yaml
|
||||
- alias: "Turn on WLED rain effect when weather changes to rainy"
|
||||
trigger:
|
||||
- platform: state
|
||||
entity_id: sensor.weather_condition
|
||||
to: "rainy"
|
||||
action:
|
||||
- service: light.turn_on
|
||||
target:
|
||||
entity_id: light.wled
|
||||
data:
|
||||
effect: "Rain"
|
||||
- service: select.select_option
|
||||
target:
|
||||
entity_id: select.wled_color_palette
|
||||
data:
|
||||
option: "Breeze"
|
||||
- service: number.set_value
|
||||
target:
|
||||
entity_id: number.wled_intensity
|
||||
data:
|
||||
value: 200
|
||||
- service: number.set_value
|
||||
target:
|
||||
entity_id: number.wled_speed
|
||||
data:
|
||||
value: 255
|
||||
```
|
||||
|
||||
@ -29,3 +29,28 @@ zeroconf:
|
||||
Zeroconf chooses which interfaces to broadcast on based on the [Network](/integrations/network/) integration.
|
||||
|
||||
IPv6 will automatically be enabled if one of the selected interfaces has an IPv6 address that is enabled via the Network integration.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Integrations relying on Zeroconf traffic are unresponsive
|
||||
|
||||
Some integrations rely on Zeroconf traffic to work, for example, the [HomeKit](/integrations/homekit/) integration.
|
||||
These integrations will not respond to traffic from other devices if the host device is not configured correctly.
|
||||
|
||||
#### Libvirt virtual machine with macvtap adapter
|
||||
|
||||
By default, the macvtap adapter created by libvirt does not allow the guest to receive Zeroconf or multicast traffic.
|
||||
|
||||
Configure the virtual machine to accept this traffic by adding the `trustGuestRxFilters="yes"` setting in the adapter's XML. For example:
|
||||
|
||||
```xml
|
||||
<interface type="direct" trustGuestRxFilters="yes">
|
||||
<mac address="xx:xx:xx:xx:xx:xx"/>
|
||||
<source dev="eno1" mode="bridge"/>
|
||||
<model type="virtio"/>
|
||||
<link state="up"/>
|
||||
<address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
|
||||
</interface>
|
||||
```
|
||||
|
||||
This only works with the `virtio` network adapter type and it is disabled by default for security reasons. See [the libvirt documentation](https://libvirt.org/formatdomain.html#elementsNICS) for more details.
|
||||
@ -548,7 +548,7 @@ The Z-Wave network can be configured via the built-in Z-Wave JS control panel in
|
||||
|
||||
**Option 3: The Zwavejs2Mqtt Docker container**
|
||||
|
||||
This is the recommended approach if you're running Home Assistant Container. See the [Zwavejs2Mqtt documentation](https://zwave-js.github.io/Zwavejs2Mqtt/#/getting-started/quick-start) for instructions.
|
||||
This is the recommended approach if you're running Home Assistant Container. See the [Zwavejs2Mqtt documentation](https://zwave-js.github.io/zwavejs2mqtt/#/getting-started/quick-start) for instructions.
|
||||
|
||||
This method provides the same server application and UI as the Zwavejs2Mqtt add-on. After installing the Docker image, make sure you enable the WS Server in the Home Assistant section of Settings page.
|
||||
|
||||
@ -596,7 +596,7 @@ You can also keep track of the Roadmap for the Z-Wave JS integration [here](http
|
||||
|
||||
#### Which Z-Wave controller should I buy?
|
||||
|
||||
Z-Wave JS supports all known 500 and 700 series Z-Wave controllers. If you are just starting out, we recommend that you purchase a 700 series controller to take advantage of the latest improvements.
|
||||
Z-Wave JS supports all known 500 and 700 series Z-Wave controllers. If you are just starting out, we recommend that you purchase a 500 series controller.
|
||||
|
||||
For more information, see [Supported Z-Wave dongles](/docs/z-wave/controllers/#supported-z-wave-usb-sticks--hardware-modules)
|
||||
|
||||
@ -680,8 +680,8 @@ Names set in Home Assistant will not import into Zwavejs2Mqtt.
|
||||
#### How can I add (include) a new device to my Z-Wave network?
|
||||
|
||||
1. In Home Assistant: open Configuration -> Integrations -> Z-Wave JS -> Configure.
|
||||
2. Press `Add node`.
|
||||
3. Press `Start Inclusion`. The Z-Wave controller is now in inclusion mode and will not respond to other commands.
|
||||
2. Press `+ ADD DEVICE`.
|
||||
3. The Z-Wave controller is now in inclusion mode and will not respond to other commands.
|
||||
4. Put the device you want to add in inclusion mode. Refer to its manual how this is done.
|
||||
5. The UI should confirm that the node was added and it will be immediately visible in Home Assistant. After a short while (seconds to minutes) the entities should also be created.
|
||||
6. If the controller fails to add/find your device, cancel the inclusion process (to unblock your network again). In some cases it might help to first remove a node (exclusion) before you add it, even when the device has not been added to this Z-Wave network yet. Another approach would be to factory reset the device. Info about that is in the manual of your device.
|
||||
@ -704,8 +704,8 @@ S2 security does not impose additional network traffic and provides additional b
|
||||
#### How do I remove (exclude) a device from my Z-Wave network?
|
||||
|
||||
1. In Home Assistant: open Configuration -> Integrations -> Z-Wave JS -> Configure.
|
||||
2. Press `Remove node`.
|
||||
3. Press `Start Exclusion`. The Z-Wave controller is now in exclusion mode and will not respond to other commands.
|
||||
2. Press `REMOVE DEVICE`.
|
||||
3. Press `START EXCLUSION`. The Z-Wave controller is now in exclusion mode and will not respond to other commands.
|
||||
4. Put the device you want to remove in exclusion mode. Refer to its manual how this is done.
|
||||
5. The UI should confirm that the node was removed and the device and entities will be removed from Home Assistant.
|
||||
|
||||
@ -760,3 +760,11 @@ When trying to determine why something isn't working as you expect, or when repo
|
||||
### Interference issues
|
||||
|
||||
Many users have reported issues with interference when the USB stick was directly connected to the machine (proximity). If you are having issues try to use a short USB 2.0 A male to female extension cord.
|
||||
|
||||
#### How to access the Z-Wave JS logs
|
||||
|
||||
Z-Wave JS writes details to its logs. To access these logs go to the following.
|
||||
|
||||
**Configuraton** -> **Devices & Services** -> **Integrations(tab)** -> **Z-Wave JS (CONFIGURE)** -> **Logs(tab)**
|
||||
|
||||
You need to keep this browser tab open for logging to be active.
|
||||
|
||||
@ -17,7 +17,7 @@ To add the Area card to your user interface, click the Lovelace menu (three dots
|
||||
|
||||
Buttons will appear on the card for the entities in the area including fan, light and switch. A motion sensor icon will appear in the top left if a motion sensor is in the area and motion is detected by the motion sensor.
|
||||
|
||||
If a camera is added to the area you can show the camera feed instead of the area pictue.
|
||||
If a camera is added to the area you can show the camera feed instead of the area picture.
|
||||
|
||||
{% configuration %}
|
||||
type:
|
||||
@ -60,6 +60,6 @@ Complex example
|
||||
- type: area
|
||||
area: bedroom
|
||||
navigation_path: my_bedroom
|
||||
show_camera:true
|
||||
show_camera: true
|
||||
theme: green
|
||||
```
|
||||
|
||||
@ -8,7 +8,7 @@ author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories:
|
||||
- Announcement
|
||||
- Announcements
|
||||
og_image: /images/blog/2021-11-analytics/social.png
|
||||
---
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ date_formatted: "November 27, 2021"
|
||||
author: Frank Bakker
|
||||
comments: true
|
||||
categories:
|
||||
- Announcement
|
||||
- Release-Notes
|
||||
og_image: /images/blog/2021-11-NetDaemon/NetDaemonLogo.png
|
||||
---
|
||||
|
||||
|
||||
@ -57,6 +57,9 @@ holidays. So, the first release in 2022, will be Wednesday, 2 February 2022._
|
||||
- [Release 2021.12.5 - December 23](#release-2021125---december-23)
|
||||
- [Release 2021.12.6 - December 27](#release-2021126---december-27)
|
||||
- [Release 2021.12.7 - December 29](#release-2021127---december-29)
|
||||
- [Release 2021.12.8 - January 4](#release-2021128---january-4)
|
||||
- [Release 2021.12.9 - January 10](#release-2021129---january-10)
|
||||
- [Release 2021.12.10 - January 17](#release-20211210---january-17)
|
||||
- [If you need help...](#if-you-need-help)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [Updates for custom integration developers](#updates-for-custom-integration-developers)
|
||||
@ -812,6 +815,242 @@ like before. Done by [@marvin-w].
|
||||
[sonos docs]: /integrations/sonos/
|
||||
[tuya docs]: /integrations/tuya/
|
||||
|
||||
## Release 2021.12.8 - January 4
|
||||
|
||||
- Update version of iZone library to add some bug fixes ([@Swamp-Ig] - [#61548]) ([izone docs])
|
||||
- Fix Tuya vacuum display battery level ([@dougiteixeira] - [#61643]) ([tuya docs])
|
||||
- Update no_ip URL ([@fabaff] - [#62477]) ([no_ip docs])
|
||||
- Do not create a number LED brightness entity for Xiaomi Miio devices that do not support it ([@bieniu] - [#62819]) ([xiaomi_miio docs])
|
||||
- Fix local_ip handling in KNX options flow ([@marvin-w] - [#62969]) ([knx docs])
|
||||
- Fix reporting correct colormode for 3rd party Hue lights ([@marcelveldt] - [#63015]) ([hue docs])
|
||||
- Hue allow per-device availability override ([@marcelveldt] - [#63025]) ([hue docs])
|
||||
- Bump pyatmo to 6.2.1 ([@cgtobi] - [#62291]) ([netatmo docs])
|
||||
- Bump pyatmo to v6.2.2 ([@cgtobi] - [#63053]) ([netatmo docs])
|
||||
- Ignore serial number "blank" from NUT ([@ollo69] - [#63066]) ([nut docs])
|
||||
- Bump greeclimate to 1.0.1 ([@cmroche] - [#63092]) ([gree docs])
|
||||
- Fix Shelly error fetching device triggers for sleeping devices ([@thecode] - [#63103]) ([shelly docs])
|
||||
- Fix systemmonitor CPU temp for Armbian on PineA64 ([@ktaragorn] - [#63111]) ([systemmonitor docs])
|
||||
- Fix CO/CO2 sensors mixup in Google Assistant ([@ryborg] - [#63152]) ([google_assistant docs])
|
||||
- Bump flux_led to 0.27.28 to fix missing white channel on SK6812RGBW strips ([@bdraco] - [#63154]) ([flux_led docs])
|
||||
- Add default Fronius logger model for v0 API ([@trdischat] - [#63184]) ([fronius docs])
|
||||
- Prevent doorbird integration from overloading the device on startup ([@bdraco] - [#63253]) ([doorbird docs])
|
||||
- Bump flux_led to 0.27.32 to fix incorrect strip order on A2 devices ([@bdraco] - [#63262]) ([flux_led docs])
|
||||
- Sisyphus: Fix bad super call ([@balloob] - [#63327]) ([sisyphus docs])
|
||||
- Fix status type in Shelly climate platform ([@bieniu] - [#63347]) ([shelly docs])
|
||||
- Bump micloud to 0.5 ([@starkillerOG] - [#63348]) ([xiaomi_miio docs])
|
||||
- Work around ingress glitch with 304 responses ([@masto] - [#63355]) ([hassio docs])
|
||||
- Fix Hue grouped light color_mode calculation ([@marcelveldt] - [#63374]) ([hue docs])
|
||||
- Fix missing timezone in GTFS timestamp sensor ([@frenck] - [#63401]) ([gtfs docs])
|
||||
- Handle missing monitored users in Plex options ([#63411]) [@jjlawren]
|
||||
- Handle no enabled ipv4 addresses in the network integration ([#63416]) [@bdraco]
|
||||
|
||||
[#63411]: https://github.com/home-assistant/core/pull/63411
|
||||
[#63416]: https://github.com/home-assistant/core/pull/63416
|
||||
[#61548]: https://github.com/home-assistant/core/pull/61548
|
||||
[#61643]: https://github.com/home-assistant/core/pull/61643
|
||||
[#62291]: https://github.com/home-assistant/core/pull/62291
|
||||
[#62477]: https://github.com/home-assistant/core/pull/62477
|
||||
[#62819]: https://github.com/home-assistant/core/pull/62819
|
||||
[#62969]: https://github.com/home-assistant/core/pull/62969
|
||||
[#63015]: https://github.com/home-assistant/core/pull/63015
|
||||
[#63025]: https://github.com/home-assistant/core/pull/63025
|
||||
[#63053]: https://github.com/home-assistant/core/pull/63053
|
||||
[#63066]: https://github.com/home-assistant/core/pull/63066
|
||||
[#63092]: https://github.com/home-assistant/core/pull/63092
|
||||
[#63103]: https://github.com/home-assistant/core/pull/63103
|
||||
[#63111]: https://github.com/home-assistant/core/pull/63111
|
||||
[#63152]: https://github.com/home-assistant/core/pull/63152
|
||||
[#63154]: https://github.com/home-assistant/core/pull/63154
|
||||
[#63184]: https://github.com/home-assistant/core/pull/63184
|
||||
[#63253]: https://github.com/home-assistant/core/pull/63253
|
||||
[#63262]: https://github.com/home-assistant/core/pull/63262
|
||||
[#63327]: https://github.com/home-assistant/core/pull/63327
|
||||
[#63347]: https://github.com/home-assistant/core/pull/63347
|
||||
[#63348]: https://github.com/home-assistant/core/pull/63348
|
||||
[#63355]: https://github.com/home-assistant/core/pull/63355
|
||||
[#63374]: https://github.com/home-assistant/core/pull/63374
|
||||
[#63401]: https://github.com/home-assistant/core/pull/63401
|
||||
[@Swamp-Ig]: https://github.com/Swamp-Ig
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@cgtobi]: https://github.com/cgtobi
|
||||
[@cmroche]: https://github.com/cmroche
|
||||
[@dougiteixeira]: https://github.com/dougiteixeira
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@ktaragorn]: https://github.com/ktaragorn
|
||||
[@marcelveldt]: https://github.com/marcelveldt
|
||||
[@marvin-w]: https://github.com/marvin-w
|
||||
[@masto]: https://github.com/masto
|
||||
[@ollo69]: https://github.com/ollo69
|
||||
[@ryborg]: https://github.com/ryborg
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@thecode]: https://github.com/thecode
|
||||
[@trdischat]: https://github.com/trdischat
|
||||
[doorbird docs]: /integrations/doorbird/
|
||||
[flux_led docs]: /integrations/flux_led/
|
||||
[fronius docs]: /integrations/fronius/
|
||||
[google_assistant docs]: /integrations/google_assistant/
|
||||
[gree docs]: /integrations/gree/
|
||||
[gtfs docs]: /integrations/gtfs/
|
||||
[hassio docs]: /integrations/hassio/
|
||||
[hue docs]: /integrations/hue/
|
||||
[izone docs]: /integrations/izone/
|
||||
[knx docs]: /integrations/knx/
|
||||
[netatmo docs]: /integrations/netatmo/
|
||||
[no_ip docs]: /integrations/no_ip/
|
||||
[nut docs]: /integrations/nut/
|
||||
[shelly docs]: /integrations/shelly/
|
||||
[sisyphus docs]: /integrations/sisyphus/
|
||||
[systemmonitor docs]: /integrations/systemmonitor/
|
||||
[tuya docs]: /integrations/tuya/
|
||||
[xiaomi_miio docs]: /integrations/xiaomi_miio/
|
||||
|
||||
## Release 2021.12.9 - January 10
|
||||
|
||||
- Bump pychromecast to 10.2.3 ([@emontnemery] - [#63429]) ([cast docs])
|
||||
- Bump flux_led to 0.27.40 to fix SK6812RGBW white level reporting ([@bdraco] - [#63435]) ([flux_led docs])
|
||||
- Fix incorrect access to entity registry in Xiaomi Miio ([@frenck] - [#63446]) ([xiaomi_miio docs])
|
||||
- Pickup screenlogic codeowner ([@bdraco] - [#61477]) ([screenlogic docs])
|
||||
- Bump screenlogicpy ([@dieselrabbit] - [#63533]) ([screenlogic docs])
|
||||
- Bump soco to 0.25.3 ([@jjlawren] - [#63548]) ([sonos docs])
|
||||
- Fix KeyError during call to homekit.unpair ([@bdraco] - [#63627]) ([homekit docs])
|
||||
- Ensure selected entity is pre-selected in homekit options flow ([@bdraco] - [#63628]) ([homekit docs])
|
||||
- Bump flux_led to 0.27.41 ([@bdraco] - [#63638]) ([flux_led docs])
|
||||
- Add default mode 'auto' for tradfri starkvind air purifier on turn on ([@leahoswald] - [#63641]) ([tradfri docs])
|
||||
- Bump flux_led to 0.27.42 ([@bdraco] - [#63651]) ([flux_led docs])
|
||||
- Split august motion and image capture binary sensors ([@bdraco] - [#62154]) ([august docs])
|
||||
- Bump yalexs to 1.1.16 ([@bdraco] - [#62700]) ([august docs])
|
||||
- Fix august locks failing to lock/unlock ([@bdraco] - [#63652]) ([august docs])
|
||||
- Switchbot Set initial state for switch ([@RenierM26] - [#63654]) ([switchbot docs])
|
||||
- Fix Tuya climate c_f DP not being a string ([@frenck] - [#63680]) ([tuya docs])
|
||||
- Fix Netgear used method version ([@starkillerOG] - [#63686]) ([netgear docs])
|
||||
- Bump flux_led to 0.27.44 to fix CCT ceiling lights ([@bdraco] - [#63712]) ([flux_led docs])
|
||||
- Bump PySwitchbot to 0.13.2 ([@RenierM26] - [#63713]) ([switchbot docs])
|
||||
- Bump WazeRouteCalculator to 0.14 ([@k-korn] - [#63718]) ([waze_travel_time docs])
|
||||
- Fix zwave_js device actions ([@raman325] - [#63769]) ([zwave_js docs])
|
||||
- Add client metadata to cloud register ([@ludeeus] - [#63794]) ([cloud docs])
|
||||
- Support Tuya strip lights with correct values for saturation and brightness ([@Knodd] - [#63812]) ([tuya docs])
|
||||
- Bump flux_led to 0.27.45 to fix missing controls on ZJ21410 models ([@bdraco] - [#63854]) ([flux_led docs])
|
||||
- Bump aioharmony to 0.2.9 ([@bdraco] - [#63858]) ([harmony docs])
|
||||
- Bump frontend to 20211229.1 ([@balloob] - [#63866]) ([frontend docs])
|
||||
|
||||
[#61477]: https://github.com/home-assistant/core/pull/61477
|
||||
[#62154]: https://github.com/home-assistant/core/pull/62154
|
||||
[#62700]: https://github.com/home-assistant/core/pull/62700
|
||||
[#63429]: https://github.com/home-assistant/core/pull/63429
|
||||
[#63435]: https://github.com/home-assistant/core/pull/63435
|
||||
[#63446]: https://github.com/home-assistant/core/pull/63446
|
||||
[#63533]: https://github.com/home-assistant/core/pull/63533
|
||||
[#63548]: https://github.com/home-assistant/core/pull/63548
|
||||
[#63627]: https://github.com/home-assistant/core/pull/63627
|
||||
[#63628]: https://github.com/home-assistant/core/pull/63628
|
||||
[#63638]: https://github.com/home-assistant/core/pull/63638
|
||||
[#63641]: https://github.com/home-assistant/core/pull/63641
|
||||
[#63651]: https://github.com/home-assistant/core/pull/63651
|
||||
[#63652]: https://github.com/home-assistant/core/pull/63652
|
||||
[#63654]: https://github.com/home-assistant/core/pull/63654
|
||||
[#63680]: https://github.com/home-assistant/core/pull/63680
|
||||
[#63686]: https://github.com/home-assistant/core/pull/63686
|
||||
[#63712]: https://github.com/home-assistant/core/pull/63712
|
||||
[#63713]: https://github.com/home-assistant/core/pull/63713
|
||||
[#63718]: https://github.com/home-assistant/core/pull/63718
|
||||
[#63769]: https://github.com/home-assistant/core/pull/63769
|
||||
[#63794]: https://github.com/home-assistant/core/pull/63794
|
||||
[#63812]: https://github.com/home-assistant/core/pull/63812
|
||||
[#63854]: https://github.com/home-assistant/core/pull/63854
|
||||
[#63858]: https://github.com/home-assistant/core/pull/63858
|
||||
[#63866]: https://github.com/home-assistant/core/pull/63866
|
||||
[@Knodd]: https://github.com/Knodd
|
||||
[@RenierM26]: https://github.com/RenierM26
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@dieselrabbit]: https://github.com/dieselrabbit
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@jjlawren]: https://github.com/jjlawren
|
||||
[@k-korn]: https://github.com/k-korn
|
||||
[@leahoswald]: https://github.com/leahoswald
|
||||
[@ludeeus]: https://github.com/ludeeus
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[august docs]: /integrations/august/
|
||||
[cast docs]: /integrations/cast/
|
||||
[cloud docs]: /integrations/cloud/
|
||||
[flux_led docs]: /integrations/flux_led/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[harmony docs]: /integrations/harmony/
|
||||
[homekit docs]: /integrations/homekit/
|
||||
[netgear docs]: /integrations/netgear/
|
||||
[screenlogic docs]: /integrations/screenlogic/
|
||||
[sonos docs]: /integrations/sonos/
|
||||
[switchbot docs]: /integrations/switchbot/
|
||||
[tradfri docs]: /integrations/tradfri/
|
||||
[tuya docs]: /integrations/tuya/
|
||||
[waze_travel_time docs]: /integrations/waze_travel_time/
|
||||
[xiaomi_miio docs]: /integrations/xiaomi_miio/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2021.12.10 - January 17
|
||||
|
||||
- Avoid removing zwave_js devices for non-ready nodes ([@kpine] - [#59964]) ([zwave_js docs])
|
||||
- Convert siri requests for target heating cooling state auto to a valid mode ([@bdraco] - [#60220]) ([homekit docs])
|
||||
- dlna_dmr: Allow for upnp attributes with None contents ([@chishm] - [#63892]) ([dlna_dmr docs])
|
||||
- Convert disabled_by to DeviceEntryDisabler on load ([@agners] - [#63944]) ([deconz docs]) ([picnic docs])
|
||||
- Fix homekit options being mutated during config_flow/migration ([@bdraco] - [#64003])
|
||||
- Bump nexia to 0.9.13 to fix setting emergency heat ([@bdraco] - [#64020]) ([nexia docs])
|
||||
- Bump flux_led to 0.28.3 to fix setting colorloop on older models ([@bdraco] - [#64094]) ([flux_led docs])
|
||||
- Fix changing the preset mode ([@bieniu] - [#64119]) ([shelly docs])
|
||||
- Fix flux_led turn on when brightness is zero on newer devices ([@bdraco] - [#64129]) ([flux_led docs])
|
||||
- Ensure august status is current when integration loads ([@bdraco] - [#64027]) ([august docs])
|
||||
- Fix august lock/unlock with older bridges ([@bdraco] - [#64143]) ([august docs])
|
||||
- Ignore unavailable entities when creating zwave_js device actions list ([@raman325] - [#64184]) ([zwave_js docs])
|
||||
- Fix KNX onboarding when there is no yaml config defined yet ([@farmio] - [#64216]) ([knx docs])
|
||||
- Bump bimmer_connected to 0.8.10 ([@rikroe] - [#64314]) ([bmw_connected_drive docs])
|
||||
- Ensure status is correct at start for older august bridges ([@bdraco] - [#64144]) ([august docs])
|
||||
- Bump flux_led to 0.28.4 to fix setting white temp on 0x35 devices ([@bdraco] - [#64326]) ([flux_led docs])
|
||||
- Orphaned MAC addresses breaks UniFi options flow ([@Kane610] - [#64327]) ([unifi docs])
|
||||
|
||||
[#59964]: https://github.com/home-assistant/core/pull/59964
|
||||
[#60220]: https://github.com/home-assistant/core/pull/60220
|
||||
[#63892]: https://github.com/home-assistant/core/pull/63892
|
||||
[#63944]: https://github.com/home-assistant/core/pull/63944
|
||||
[#64003]: https://github.com/home-assistant/core/pull/64003
|
||||
[#64020]: https://github.com/home-assistant/core/pull/64020
|
||||
[#64027]: https://github.com/home-assistant/core/pull/64027
|
||||
[#64094]: https://github.com/home-assistant/core/pull/64094
|
||||
[#64119]: https://github.com/home-assistant/core/pull/64119
|
||||
[#64129]: https://github.com/home-assistant/core/pull/64129
|
||||
[#64143]: https://github.com/home-assistant/core/pull/64143
|
||||
[#64144]: https://github.com/home-assistant/core/pull/64144
|
||||
[#64184]: https://github.com/home-assistant/core/pull/64184
|
||||
[#64216]: https://github.com/home-assistant/core/pull/64216
|
||||
[#64314]: https://github.com/home-assistant/core/pull/64314
|
||||
[#64326]: https://github.com/home-assistant/core/pull/64326
|
||||
[#64327]: https://github.com/home-assistant/core/pull/64327
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@agners]: https://github.com/agners
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@chishm]: https://github.com/chishm
|
||||
[@farmio]: https://github.com/farmio
|
||||
[@kpine]: https://github.com/kpine
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@rikroe]: https://github.com/rikroe
|
||||
[august docs]: /integrations/august/
|
||||
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
|
||||
[deconz docs]: /integrations/deconz/
|
||||
[dlna_dmr docs]: /integrations/dlna_dmr/
|
||||
[flux_led docs]: /integrations/flux_led/
|
||||
[homekit docs]: /integrations/homekit/
|
||||
[knx docs]: /integrations/knx/
|
||||
[nexia docs]: /integrations/nexia/
|
||||
[picnic docs]: /integrations/picnic/
|
||||
[shelly docs]: /integrations/shelly/
|
||||
[unifi docs]: /integrations/unifi/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## If you need help...
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
|
||||
|
||||
75
source/_posts/2022-01-07-android-quest.markdown
Normal file
75
source/_posts/2022-01-07-android-quest.markdown
Normal file
@ -0,0 +1,75 @@
|
||||
---
|
||||
title: "Oculus Quest Meet the Smart Home!"
|
||||
description: "Automate your home based on how you use your Quest!"
|
||||
date: 2022-01-07 00:00:00
|
||||
date_formatted: "January 07, 2022"
|
||||
comments: true
|
||||
author: Daniel Shokouhi
|
||||
categories: Release-Notes
|
||||
og_image: /images/blog/2022-01-android-quest/quest_sensors.png
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
Hey Everyone! We hope you all had a great new years and holidays spent with the family! This past holiday season had some pretty cool toys going around. Cool toys to us mean more things to tinker with. One of the most popular gifts this year was no doubt the Oculus Quest and to be honest, how could it not be right?
|
||||
|
||||
Naturally, working on the Android app some of us wondered how does the app perform on such a device? Well, it actually works pretty well and you can start building automations based on your usage today!
|
||||
|
||||
<a href="https://sidequestvr.com/app/6427/home-assistant" style="display:inline-block"><img width="200" class="download-badge" alt="Get it on SideQuest" src="https://sidequestvr.com/assets/images/branding/Get-it-on-SIDEQUEST.png" style='box-shadow:none;border:0'></a>
|
||||
|
||||
|
||||
## Oculus Quest data in Home Assistant
|
||||
|
||||
Home Assistant Companion for Quest gives you access in Home Assistant to over 40 data points about your headset. For example, our [interactive sensor] updates as soon as the screen comes on, which means you're wearing the headset. This allows you to make sure your lights are bright enough to play VR.
|
||||
|
||||
Ever play on your headset until it dies and then sits around waiting for it to charge up? Using the battery sensors you can get notified when your headset is fully charged and ready to play that next round.
|
||||
|
||||
Keep the music on in the background while you are playing? Automate your media player volume level based on whether your Quest microphone is muted.
|
||||
|
||||
It is not all about automations either. You can open the Home Assistant interface on your Quest (in 2D) and see who rang the doorbell. You can even talk back if your doorbell supports it!
|
||||
|
||||
We are just getting started with things. As usual our users are really good at finding more unique use cases that we didn't even consider. So get your device [set up with Sidequest], [install the app] and start automating today!
|
||||
|
||||
|
||||
|
||||
## Hello Sidequest!
|
||||
|
||||
Wait Sidequest, what is that? Sidequest is the alternative App Store for the Oculus Quest.
|
||||
|
||||
In VR terminology our app is a "2D app". The official Oculus Quest store only recently started allowing 2D apps and we are still working on a version that meets their requirements. So while we are waiting, we wanted to release something so we can get feedback how you are using it to automate things.
|
||||
|
||||
The app on Sidequest is the [minimal version] of the Home Assistant Companion Android app. While the Quest runs Android, it doesn't have the Google services. This means no widgets, no shortcuts, and no support for the standard notifications.
|
||||
|
||||
## 2022.1 Release for Android
|
||||
|
||||
We can't just make a post like this and ignore the new release for the Phone app that just went out the other day without highlighting it right?! While the 2022.1 release may not be as jam-packed as 2021.12 we do still have some neat features to cover.
|
||||
|
||||
* A new sensor to determine if your devices [work profile] is active by [zmarties]. This sensor will update as soon as a state change is detected allowing you to make unique automations based on the profile being active.
|
||||
* [dshokouhi] has added a new sensor allowing you to see what the [Last Used App] was. Pair this new sensor with the Quest and you can make specific automations based on what game you are currently playing!
|
||||
|
||||
|
||||
|
||||
* [jpelgrom] has worked on our WebSocket implementation to finally bring in areas to the app. Device controls are the first feature to get area support so you can easily add entities from areas. The area will also be shown in the device control button itself. Be on the lookout for more area support in other parts of the app as it should make finding entities a lot easier.
|
||||
* [JBassett] has also made more progress on the WebSocket implementation by bringing in better error handling to prevent the application from crashing and producing a lot of unnecessary errors.
|
||||
* For the Wear OS app [SkechyWolf] has added support for the back button to properly function and exit the app.
|
||||
|
||||
A big thank you to all of our contributors and users for bringing in awesome features and great feedback/bugs. We look forward to improving the android app even further in 2022! As always please remember to add your feature requests and bugs to GitHub.
|
||||
|
||||
## Changelog
|
||||
|
||||
- 2022.1.1 - https://github.com/home-assistant/android/releases/tag/2022.1.1
|
||||
|
||||
|
||||
[zmarties]: https://github.com/zmarties
|
||||
[dshokouhi]: https://github.com/dshokouhi
|
||||
[JBassett]: https://github.com/JBassett
|
||||
[SkechyWolf]: https://github.com/SkechyWolf
|
||||
[jpelgrom]: https://github.com/jpelgrom
|
||||
[set up with Sidequest]: https://sidequestvr.com/setup-howto
|
||||
[install the app]: https://sidequestvr.com/app/6427/home-assistant
|
||||
[work profile]: https://companion.home-assistant.io/docs/core/sensors#work-profile-sensor
|
||||
[Last Used App]: https://companion.home-assistant.io/docs/core/sensors#last-used-app-sensor
|
||||
[minimal version]: https://companion.home-assistant.io/docs/core/android-flavors
|
||||
[interactive sensor]: https://companion.home-assistant.io/docs/core/sensors#interactive-sensor
|
||||
[good lighting]: https://support.oculus.com/articles/headsets-and-accessories/using-your-headset/turn-off-tracking/
|
||||
26
source/_posts/2022-01-18-streamlining-experiences.markdown
Normal file
26
source/_posts/2022-01-18-streamlining-experiences.markdown
Normal file
@ -0,0 +1,26 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Streamlining Experiences"
|
||||
description: "We have a new motto for 2022. We're going to take our existing features and make them even easier to use."
|
||||
date: 2022-01-19 00:00:00
|
||||
date_formatted: "January 19, 2022"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories:
|
||||
- Announcements
|
||||
---
|
||||
|
||||
With Home Assistant the last few years we’ve been focusing on making things easier, stable, and faster. More things can be managed via the UI, most YAML-based integrations can be reloaded without restarting and if something breaks, safe mode and built-in backups have your back.
|
||||
|
||||
We have amazing contributors who work on making Home Assistant better every single day. However, you can’t keep growing by adding new things in the same structure. An interface made for 4 items will become confusing once the 10th item is added (like our profile page). A veteran Home Assistant user might be fine because they have seen the growth feature by feature and know exactly where to find what. For new users it is overwhelming.
|
||||
|
||||
For 2022 the motto will be “streamlining experiences”. We want to better organize and integrate all the different features that make up Home Assistant.
|
||||
|
||||
For example, there should be a built-in way, for both YAML and the UI, to easily send a notification with a camera snapshot to your phone, pick a song to play for an automation, or use text-to-speech to notify you when something is happening. All these things are possible today but require too much knowledge of how the various parts work.
|
||||
|
||||
We’ll have 11 releases this year and each release should streamline more things.
|
||||
|
||||
Have a good and healthy 2022 and see you at our first release on February 2!
|
||||
|
||||
Paulus
|
||||
BIN
source/images/blog/2022-01-android/Companion.png
Executable file
BIN
source/images/blog/2022-01-android/Companion.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 143 KiB |
BIN
source/images/blog/2022-01-android/app_on_quest.png
Executable file
BIN
source/images/blog/2022-01-android/app_on_quest.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 3.1 MiB |
BIN
source/images/blog/2022-01-android/last_used_app.png
Executable file
BIN
source/images/blog/2022-01-android/last_used_app.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 6.1 KiB |
BIN
source/images/blog/2022-01-android/quest_sensors.png
Executable file
BIN
source/images/blog/2022-01-android/quest_sensors.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 21 KiB |
BIN
source/images/isy994/isy994_switch_variable_example.png
Normal file
BIN
source/images/isy994/isy994_switch_variable_example.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 71 KiB |
BIN
source/images/screenshots/cover_classes_icons.png
Normal file
BIN
source/images/screenshots/cover_classes_icons.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
@ -3,17 +3,28 @@ title: "Setting up local media sources"
|
||||
description: "More information on how to set up local media sources in Home Assistant."
|
||||
---
|
||||
|
||||
In order to use the media browser with Home Assistant, it needs to know where to
|
||||
find your local media.
|
||||
Home Assistant has a local media folder. Any audio or video files placed in this folder will be accessible via the media browser.
|
||||
|
||||
## Home Assistant OS and Supervised
|
||||
The easiest way to manage your local media is using the {% my supervisor_addon title="Samba" addon="core_samba" %}.
|
||||
|
||||
No action is needed from your end to set it up. Home Assistant will
|
||||
automatically use the "media" folder that is provided on these systems.
|
||||
## Using custom folders
|
||||
|
||||
It is also possible to set up custom and additional media directories. To do
|
||||
so, you'll need to adjust the [core configuration][basic-configuration].
|
||||
|
||||
This example adds the two media folders to Home Assistant:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml
|
||||
homeassistant:
|
||||
media_dirs:
|
||||
media: /media
|
||||
recording: /mnt/recordings
|
||||
```
|
||||
|
||||
## Home Assistant Container
|
||||
|
||||
If you run the Home Assistant Container in, for example, Docker, you'll need to
|
||||
If you run the Home Assistant Container you'll need to
|
||||
add a Docker volume mount to the Home Assistant container, to mount in
|
||||
your local media.
|
||||
|
||||
@ -45,8 +56,7 @@ in a similar fashion as listed in the command above.
|
||||
|
||||
## Home Assistant Core
|
||||
|
||||
If you run Home Assistant Core directly in, for example, a Python virtual
|
||||
environment, you'll need to create a media folder yourself.
|
||||
If you run Home Assistant Core you'll need to create a media folder yourself.
|
||||
|
||||
By default, Home Assistant will look for the `media` folder inside your current
|
||||
Home Assistant configuration folder.
|
||||
@ -59,19 +69,4 @@ Then you'll need to create a media folder in that same path:
|
||||
|
||||
`/home/frenck/.homeassistant/media`
|
||||
|
||||
## Using custom folders
|
||||
|
||||
It is also possible to set up custom and additional media directories. To do
|
||||
so, you'll need to adjust the [core configuration][basic-configuration].
|
||||
|
||||
This example adds the two media folders to Home Assistant:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml
|
||||
homeassistant:
|
||||
media_dirs:
|
||||
media: /media
|
||||
recording: /mnt/recordings
|
||||
```
|
||||
|
||||
[basic-configuration]: /docs/configuration/basic/#media_dirs
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user