jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into rc

Browse Source
This commit is contained in:
Franck Nijhof 2023-01-30 19:02:15 +01:00
commit ee1fc1da73
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
49 changed files with 428 additions and 600 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/add_prs_to_project.yml vendored
View File

@ -13,7 +13,7 @@ jobs:
- name: Generate app token
id: token
# Pinned to a specific version of the action for security reasons
uses: tibdex/github-app-token@021a2405c7f990db57f5eae5397423dcc554159c # v1.7.0
uses: tibdex/github-app-token@b62528385c34dbc9f38e5f4225ac829252d1ea92 # v1.8.0
with:
app_id: ${{ secrets.PROJECTS_APP_ID }}
private_key: ${{ secrets.PROJECTS_APP_PEM }}

4
Gemfile.lock
View File

@ -114,12 +114,12 @@ GEM
terminal-table (3.0.2)
unicode-display_width (>= 1.1.1, < 3)
tilt (2.0.11)
tzinfo (2.0.5)
tzinfo (2.0.6)
concurrent-ruby (~> 1.0)
tzinfo-data (1.2022.7)
tzinfo (>= 1.0.0)
unicode-display_width (2.4.2)
webrick (1.7.0)
webrick (1.8.1)
PLATFORMS
ruby

759
package-lock.json generated
View File

File diff suppressed because it is too large Load Diff

2
package.json
View File

@ -9,7 +9,7 @@
"remark-lint-fenced-code-flag": "^3.1.1",
"remark-lint-no-shell-dollars": "^3.1.1",
"remark-stringify": "^10.0.2",
"textlint": "^12.6.0",
"textlint": "^13.0.5",
"textlint-filter-rule-comments": "^1.2.2",
"textlint-rule-common-misspellings": "^1.0.1",
"textlint-rule-terminology": "^3.0.4"

19
source/_docs/mqtt.markdown
View File

@ -1,19 +0,0 @@
---
title: "MQTT"
description: "Details about the MQTT support of Home Assistant."
---
MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport.
To integrate MQTT into Home Assistant, you need to setup the [MQTT integration](/integrations/mqtt).
You will also need to setup an MQTT broker, please refer to the [MQTT broker](/docs/mqtt/broker) documentation.
## Additional features
- [Certificate](/docs/mqtt/certificate/)
- [Discovery](/docs/mqtt/discovery/)
- [Publish service](/docs/mqtt/service/)
- [Birth and last will messages](/docs/mqtt/birth_will/)
- [Testing your setup](/docs/mqtt/testing/)
- [Logging](/docs/mqtt/logging/)

16
source/_includes/asides/docs_navigation.html
View File

@ -155,18 +155,18 @@
</ul>
</li>
<li>
<b>{% active_link /docs/mqtt/ MQTT %}</b>
<b>{% active_link /integrations/mqtt MQTT %}</b>
<ul>
<li>{% active_link /docs/mqtt/broker/ Broker %}</li>
<li>{% active_link /docs/mqtt/certificate/ Certificate %}</li>
<li>{% active_link /docs/mqtt/discovery/ Discovery %}</li>
<li>{% active_link /docs/mqtt/service/ Publish service %}</li>
<li>{% active_link /integrations/mqtt/#broker-configuration Broker %}</li>
<li>{% active_link /integrations/mqtt/#advanced-broker-configuration Certificate %}</li>
<li>{% active_link /integrations/mqtt/#mqtt-discovery Discovery %}</li>
<li>{% active_link /integrations/mqtt/#publish--dump-services Publish service %}</li>
<li>
{% active_link /docs/mqtt/birth_will/ Birth and last will messages
{% active_link /integrations/mqtt/#birth-and-last-will-messages Birth and last will messages
%}
</li>
<li>{% active_link /docs/mqtt/testing/ Testing your setup %}</li>
<li>{% active_link /docs/mqtt/logging/ Logging %}</li>
<li>{% active_link /integrations/mqtt/#testing-your-setup Testing your setup %}</li>
<li>{% active_link /integrations/mqtt/#logging Logging %}</li>
</ul>
</li>
</ul>

2
source/_integrations/alarm_control_panel.ifttt.markdown
View File

@ -7,7 +7,7 @@ ha_release: 0.66
ha_domain: ifttt
---
The `ifttt` platform allows you to integrate security systems that have no open API but can be controlled through [IFTTT](https://ifttt.com/discover).
The `ifttt` platform allows you to integrate security systems that have no open API but can be controlled through [IFTTT](https://ifttt.com/explore).
This platform depends on the [IFTTT](/integrations/ifttt/) Home Assistant integration. See the integrations documentation to set it up.

2
source/_integrations/alarm_control_panel.mqtt.markdown
View File

@ -105,7 +105,7 @@ command_topic:
required: true
type: string
device:
description: "Information about the device this alarm panel is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this alarm panel is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

12
source/_integrations/alarmdecoder.markdown
View File

@ -130,13 +130,21 @@ Using a combination of the available services and attributes, you can create swi
friendly_name: Chime
value_template: "{{ is_state_attr('alarm_control_panel.alarm_panel', 'chime', true) }}"
turn_on:
service: alarmdecoder.alarm_toggle_chime
- condition: state
entity_id: alarm_control_panel.alarm_panel
attribute: chime
state: False
- 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
- condition: state
entity_id: alarm_control_panel.alarm_panel
attribute: chime
state: True
- service: alarmdecoder.alarm_toggle_chime
target:
entity_id: alarm_control_panel.alarm_panel
data:

2
source/_integrations/alexa.smart_home.markdown
View File

@ -402,7 +402,7 @@ See [List of Capability Interfaces and Supported Locales][alexa-supported-locale
The `endpoint`, `client_id` and `client_secret` are optional, and are only required if you want to enable Alexa's proactive mode (i.e., "Send Alexa Events" enabled). Please note the following if you want to enable proactive mode:
- There are different endpoint URLs, depending on the region of your skill. Please check the available endpoints at <https://developer.amazon.com/docs/smarthome/send-events-to-the-alexa-event-gateway.html#endpoints>
- There are different endpoint URLs, depending on the region of your skill. Please check the available endpoints at <https://developer.amazon.com/docs/smarthome/send-events.html#endpoints>
- The `client_id` and `client_secret` are not the ones used by the skill that have been set up using "Login with Amazon" (in the [Alexa Developer Console][amazon-dev-console]: Build > Account Linking), but rather from the "Alexa Skill Messaging" (in the Alexa Developer Console: Build > Permissions > Alexa Skill Messaging). To get them, you need to enable the "Send Alexa Events" permission.
- If the "Send Alexa Events" permission was not enabled previously, you need to unlink and relink the skill using the Alexa App, or else Home Assistant will show the following error: "Token invalid and no refresh token available. Also, you need to restart your Home Assistant after each disabling/enabling the skill in Alexa."

2
source/_integrations/ambient_station.markdown
View File

@ -55,4 +55,4 @@ Cloud. Users desiring a local option are encouraged to explore the
[Ecowitt](https://www.ecowitt.com) family of devices, which are able to read RF signals
directly from the PWS and transmit them to a variety of other applications, including
[`ecowitt2mqtt`](https://github.com/bachya/ecowitt2mqtt) (which supports
[MQTT Discovery](/docs/mqtt/discovery)), or the built-in [Ecowitt](/integrations/ecowitt/) integration.
[MQTT Discovery](/integrations/mqtt/#mqtt-discovery)), or the built-in [Ecowitt](/integrations/ecowitt/) integration.

1
source/_integrations/august.markdown
View File

@ -44,6 +44,7 @@ The `august` integration allows you to integrate your [August](https://august.co
| Yale Conexis L1 | yes |
| Yale Conexis L2 | yes |
| Yale Linus | yes |
| Yale Smart Safe | yes |
There is currently support for the following device types within Home Assistant:

2
source/_integrations/binary_sensor.mqtt.markdown
View File

@ -69,7 +69,7 @@ availability_topic:
required: false
type: string
device:
description: "Information about the device this binary sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this binary sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

1
source/_integrations/bluetooth.markdown
View File

@ -92,6 +92,7 @@ If you experience an unreliable Bluetooth connection, installing a short USB ext
- QGOO BT-06A (CSR8510A10)
- ROCKETEK BT4Y (CSR8510A10)
- SABRENT BT-UB40 (CSR8510A10)
- Sena UD100-G03 (CSR8510A10) 📶
- StarTech USBBT1EDR4 (CSR8510A10)
- Techkey PBT06H (CSR8510A10)
- TRENDnet TBW-107UB (CSR8510A10)

2
source/_integrations/button.mqtt.markdown
View File

@ -67,7 +67,7 @@ command_topic:
required: false
type: string
device:
description: "Information about the device this button is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this button is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/camera.mqtt.markdown
View File

@ -69,7 +69,7 @@ availability_topic:
required: false
type: string
device:
description: "Information about the device this camera is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this camera is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/climate.mqtt.markdown
View File

@ -100,7 +100,7 @@ current_temperature_topic:
required: false
type: string
device:
description: 'Information about the device this HVAC device is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
description: 'Information about the device this HVAC device is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
required: false
type: map
keys:

2
source/_integrations/cover.mqtt.markdown
View File

@ -80,7 +80,7 @@ command_topic:
required: false
type: string
device:
description: "Information about the device this cover is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this cover is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/device_tracker.mqtt.markdown
View File

@ -181,7 +181,7 @@ value_template:
### Using the discovery protocol
The device_tracker can be created via publishing to a discovery topic that follows the following [MQTT Discovery](/docs/mqtt/discovery/#discovery-topic) topic name format: `<discovery_prefix>/device_tracker/[<node_id>/]<object_id>/config`.
The device_tracker can be created via publishing to a discovery topic that follows the following [MQTT Discovery](/integrations/mqtt/#mqtt-discovery#discovery-topic) topic name format: `<discovery_prefix>/device_tracker/[<node_id>/]<object_id>/config`.
You can use the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages.

2
source/_integrations/device_trigger.mqtt.markdown
View File

@ -14,7 +14,7 @@ An MQTT device trigger is a better option than a [binary sensor](/integrations/b
## Configuration
MQTT device triggers are only supported through [MQTT discovery](/docs/mqtt/discovery/), manual setup through `configuration.yaml` is not supported.
MQTT device triggers are only supported through [MQTT discovery](/integrations/mqtt/#mqtt-discovery), manual setup through `configuration.yaml` is not supported.
The discovery topic needs to be: `<discovery_prefix>/device_automation/[<node_id>/]<object_id>/config`. Note that only one trigger may be defined per unique discovery topic. Also note that the combination of `type` and `subtype` should be unique for a device.
{% configuration %}

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

@ -75,7 +75,7 @@ command_topic:
required: true
type: string
device:
description: "Information about the device this fan is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this fan is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/flume.markdown
View File

@ -31,7 +31,7 @@ To add `Flume` to your installation, go to **Settings** -> **Devices & Services*
## Notifications
Flume notifications are available via binary sensors. To clear the notifications, you will need to use your Flume app or go to: [https://portal.flumewater.com/notifications]([https://portal.flumewater.com/notifications]) and clear the notification in question.
Flume notifications are available via binary sensors. To clear the notifications, you will need to use your Flume app or go to: [https://portal.flumewater.com/notifications](https://portal.flumewater.com/notifications) and clear the notification in question.
The following notifications are supported:

2
source/_integrations/folder_watcher.markdown
View File

@ -37,7 +37,7 @@ folder:
patterns:
description: Pattern matching to apply
required: false
default: "*"
default: "`*`"
type: string
{% endconfiguration %}

1
source/_integrations/fritzbox.markdown
View File

@ -49,6 +49,7 @@ Additionally, we also support to trigger smarthome templates.
- FRITZ!Box 7490
- FRITZ!Box 7430
- [FRITZ!DECT 200](https://en.avm.de/products/fritzdect/fritzdect-200/)
- [FRITZ!DECT 210](https://en.avm.de/products/fritzdect/fritzdect-210/)
- [FRITZ!DECT 301](https://en.avm.de/products/fritzdect/fritzdect-301/)
- [FRITZ!DECT 500](https://en.avm.de/products/fritzdect/fritzdect-500/)
- [Eurotronic Comet DECT](https://eurotronic.org/produkte/dect-ule-heizkoerperthermostat/comet-dect/)

2
source/_integrations/humidifier.mqtt.markdown
View File

@ -76,7 +76,7 @@ command_topic:
required: true
type: string
device:
description: "Information about the device this humidifier is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this humidifier is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

12
source/_integrations/light.mqtt.markdown
View File

@ -138,7 +138,7 @@ command_topic:
required: true
type: string
device:
description: 'Information about the device this light is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
description: 'Information about the device this light is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
required: false
type: map
keys:
@ -581,7 +581,7 @@ command_topic:
required: true
type: string
device:
description: 'Information about the device this light is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
description: 'Information about the device this light is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
required: false
type: map
keys:
@ -855,11 +855,11 @@ mqtt:
- [McLighting](https://github.com/toblum/McLighting) is another ESP8266 firmware for WS2812 addressable LEDs.
- [MQTT JSON Light](https://github.com/mertenats/Open-Home-Automation/tree/master/ha_mqtt_rgbw_light_with_discovery) is another implementation for ESP8266 including [MQTT discovery](/docs/mqtt/discovery/).
- [MQTT JSON Light](https://github.com/mertenats/Open-Home-Automation/tree/master/ha_mqtt_rgbw_light_with_discovery) is another implementation for ESP8266 including [MQTT discovery](/integrations/mqtt/#mqtt-discovery).
- [ESPHome](https://esphome.io) implements the JSON schema for MQTT based installs and supports [MQTT discovery](/docs/mqtt/discovery/).
- [ESPHome](https://esphome.io) implements the JSON schema for MQTT based installs and supports [MQTT discovery](/integrations/mqtt/#mqtt-discovery).
- [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/integrations/light.mqtt) platform and supports ON/OFF, RGBW colours, brightness, color temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/docs/mqtt/discovery/)) and the MQTT Last Will and Testament is enabled as well.
- [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/integrations/light.mqtt) platform and supports ON/OFF, RGBW colours, brightness, color temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/integrations/mqtt/#mqtt-discovery)) and the MQTT Last Will and Testament is enabled as well.
- [h801-mqtt-json](https://github.com/starkillerOG/h801-mqtt-json) is a custom firmware for the H801 LED dimmer, a 5 channel (RGBWWCW) WiFi LED strip controller for 12V LED strips. The firmware is meant to control the 5 channels of the H801 to simultaneously control an RGB and a Warm-white/Cold-white LED strip such as a 5050 RGB LED strip and a 5025 Dual White strip. It implements the [MQTT JSON light](/integrations/light.mqtt) platform and supports ON/OFF, RGBW colours (RGB strip), brightness, color temperature (CW/WW strip) and transitions.
@ -950,7 +950,7 @@ command_topic:
required: true
type: string
device:
description: 'Information about the device this light is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
description: 'Information about the device this light is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
required: false
type: map
keys:

2
source/_integrations/lock.mqtt.markdown
View File

@ -82,7 +82,7 @@ command_topic:
required: true
type: string
device:
description: 'Information about the device this lock is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
description: 'Information about the device this lock is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device.'
required: false
type: map
keys:

2
source/_integrations/mqtt.markdown
View File

@ -561,7 +561,7 @@ Delete the sensor by sending an empty message.
mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config" -m ''
```
For more details please refer to the [MQTT testing section](/docs/mqtt/testing/).
For more details please refer to the [MQTT testing section](/integrations/mqtt/#testing-your-setup).
#### Sensors

2
source/_integrations/number.mqtt.markdown
View File

@ -61,7 +61,7 @@ command_topic:
required: true
type: string
device:
description: "Information about the device this Number is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this Number is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/select.mqtt.markdown
View File

@ -73,7 +73,7 @@ command_topic:
required: true
type: string
device:
description: "Information about the device this Select is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this Select is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/sensor.mqtt.markdown
View File

@ -61,7 +61,7 @@ availability_topic:
required: false
type: string
device:
description: "Information about the device this sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/siren.mqtt.markdown
View File

@ -84,7 +84,7 @@ command_topic:
required: false
type: string
device:
description: "Information about the device this siren is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this siren is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/snips.markdown
View File

@ -121,7 +121,7 @@ probability_threshold:
### Specifying the MQTT broker
Messages between Snips and Home Assistant are passed via MQTT. We can either point Snips to the MQTT broker used by Home Assistant, as explained above, or tell Home Assistant which [MQTT broker](/docs/mqtt/) to use by adding the following entry to the `configuration.yaml` file:
Messages between Snips and Home Assistant are passed via MQTT. We can either point Snips to the MQTT broker used by Home Assistant, as explained above, or tell Home Assistant which [MQTT broker](/integrations/mqtt) to use by adding the following entry to the `configuration.yaml` file:
```yaml
mqtt:

7
source/_integrations/spotify.markdown
View File

@ -36,9 +36,10 @@ an application at Spotify using the Spotify Developer website. This will
provide you with the Spotify application credentials Home Assistant needs
to allow you to log in with your Spotify account.
1. Log in to the [Spotify Developer](https://developer.spotify.com) Dashboard.
2. Visit the [My Applications](https://developer.spotify.com/my-applications/#!/applications) page.
3. Click the **CREATE AN APP** button in the top right. Enter a name and
1. If Spotify was previously integrated with your Home Assistant with _outdated_ credentials, it might be required to remove these old Spotify account credentials using the {% my application_credentials title="Home Assistant Application Credentials dashboard" %}.
2. Log in to the [Spotify Developer](https://developer.spotify.com) Dashboard.
3. Visit the [My Applications](https://developer.spotify.com/my-applications/#!/applications) page.
4. Click the **CREATE AN APP** button in the top right. Enter a name and
description; feel free to use any name and description you like.
![Creating a Spotify Application](/images/integrations/spotify/create-spotify-application.png)

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

@ -71,7 +71,7 @@ command_topic:
required: false
type: string
device:
description: "Information about the device this switch is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this switch is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/tag.mqtt.markdown
View File

@ -12,7 +12,7 @@ The `mqtt` tag scanner platform uses an MQTT message payload to generate tag sca
## Configuration
MQTT scanners are only supported through [MQTT discovery](/docs/mqtt/discovery/), manual setup through `configuration.yaml` is not supported.
MQTT scanners are only supported through [MQTT discovery](/integrations/mqtt/#mqtt-discovery), manual setup through `configuration.yaml` is not supported.
The discovery topic needs to be: `<discovery_prefix>/tag/[<node_id>/]<object_id>/config`.
{% configuration %}

2
source/_integrations/text.mqtt.markdown
View File

@ -67,7 +67,7 @@ command_topic:
required: true
type: string
device:
description: "Information about the device this of text capability is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this of text capability is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

7
source/_integrations/timer.markdown
View File

@ -14,6 +14,11 @@ The `timer` integration aims to simplify automations based on (dynamic) duration
When a timer finishes or gets canceled the corresponding events are fired. This allows you to differentiate if a timer has switched from `active` to `idle` because the given duration has elapsed or it has been canceled. To control timers in your automations you can use the services mentioned below. When calling the `start` service on a timer that is already running, it resets the duration it will need to finish and restarts the timer without triggering a canceled or finished event. This, for example, makes it easy to create timed lights that get triggered by motion. Starting a timer triggers a started event unless the timer is paused, in that case, it triggers a restarted event.
<div class='note'>
Timers will be restored to their correct state and time on Home Assistant startup and restarts when configured with the `restore` option.
</div>
## Configuration
The preferred way to configure timer helpers is via the user interface at **Settings** -> **Devices & Services** -> **Helpers** and click the add button; next choose the **Timer** option.
@ -54,7 +59,7 @@ timer:
required: false
type: icon
restore:
description: When true, active and paused timers will be restored to the right state on startup. If an active timer was supposed to end while Home Assistant is stopped, the `timer.finished` event will fire on startup for that timer. The `finished_at` property in the event data will provide you with the time that the timer was actually supposed to fire which you can use in automation conditions to decide whether or not to act on it.
description: When true, active and paused timers will be restored to the correct state and time on Home Assistant startup and restarts. If an active timer was supposed to end while Home Assistant is stopped, the `timer.finished` event will fire on startup for that timer. The `finished_at` property in the event data will provide you with the time that the timer was actually supposed to fire which you can use in automation conditions to decide whether or not to act on it.
required: false
type: boolean
default: false

2
source/_integrations/update.mqtt.markdown
View File

@ -64,7 +64,7 @@ command_topic:
required: false
type: string
device:
description: "Information about the device this Update is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this Update is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/vacuum.mqtt.markdown
View File

@ -367,7 +367,7 @@ command_topic:
required: false
type: string
device:
description: "Information about the device this switch is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
description: "Information about the device this switch is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:

2
source/_integrations/webostv.markdown
View File

@ -121,7 +121,7 @@ Available services: `button`, `command`
| Service data attribute | Optional | Description |
| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | no | Target a specific webostv media player. |
| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `MENU`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `PLAY`, `PAUSE`, `NETFLIX`, `GUIDE`, `AMAZON`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` |
| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `MENU`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `YELLOW`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `PLAY`, `PAUSE`, `NETFLIX`, `GUIDE`, `AMAZON`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` |
### Service `webostv.command`

2
source/_integrations/yalexs_ble.markdown
View File

@ -37,6 +37,8 @@ Devices must have a Yale Access module installed to function with this integrati
- YRD420 (Yale Assure Lock 2)
- YRD450 (Yale Assure Lock 2 Key Free)
- YUR/SSDL/1/SIL (Yale Unity Screen Door Lock - Australia)
- IES-D210W-G0 (Yale Smart Safe)
- YRSM-1 (Yale Smart Safe)
- ASL-05 (August WiFi Smart Lock - Gen 4)
- ASL-03 (August Smart Lock Pro - Gen 3)
- ASL-02 (August Smart Lock Pro - Gen 2)

108
source/_posts/2023-01-26-year-of-the-voice-chapter-1.markdown Normal file
View File

@ -0,0 +1,108 @@
---
layout: post
title: "Year of the Voice - Chapter 1: Assist"
description: "Assist is the new feature in Home Assistant to handle all your conversations."
date: 2023-01-26 00:00:00
date_formatted: "January 26, 2023"
author: Paulus Schoutsen
comments: true
categories: Assist
og_image: /images/blog/2023-01-26-year-of-the-voice-chapter-1/social.png
---
This year is Home Assistant's [year of the voice](https://www.home-assistant.io/blog/2022/12/20/year-of-voice/). It is our goal for 2023 to let users control Home Assistant in their own language. Today, one month into 2023, we start our first chapter.
At Home Assistant we believe that technology is meant to be played with, and projects should be usable as soon as possible. Together with the community we can then iterate and refine. That's why today, we're delivering a basic experience for 22 languages to interact with Home Assistant. Oh, and we are also releasing some fun stuff that we cooked up along the way.
_To watch the video presentation of this blog post, including live demos, check [the recording of our live stream](https://www.youtube.com/live/ixgNT3RETPg)._
## Intentions
The core of a voice assistant is to be able to understand the intention of a spoken sentence. What is it the user wants to do? To extract these intentions we created our own template sentence matching format and intent recognizer named [Hassil](https://github.com/home-assistant/hassil).
This new format is used by our new [Home Assistant Intents](https://github.com/home-assistant/intents) project. The goal of this project is to collect home automation sentences in every possible language. Since it's start a month ago, we have had 112 people contribute. The project now supports [22 languages and 14 more are in progress](https://home-assistant.github.io/intents/).
## Assist
We have added a new feature to Home Assistant: <img src='/images/assist/assist-icon.svg' alt='Assist icon' style='height: 32px' class='no-shadow'> Assist. It allow users to use natural language to control Home Assistant. It is powered by Hassil and the sentences from the Home Assistant Intent project.
<!--more-->
We want Assist to be as accessible to as many people as possible. To do this, we made it work without requiring extra hardware – just update to Home Assistant 2023.2 and you can start! Through a combination of smart algorithms combined with sheer brute force (we are collecting a lot of sentences), we have been able to make a system that works for most common sentences. Support for more powerful, AI-powered, intent recognizers might come in the future as an opt-in feature.
Assist is enabled by default in the Home Assistant 2023.2 release. Tap the new Assist icon <img src='/images/assist/assist-icon.svg' alt='Assist icon' style='height: 32px' class='no-shadow'> at the top right of the dashboard to use it.
[Assist documentation.](https://next.home-assistant.io/docs/assist/)
<img src="/images/blog/2023-01-26-year-of-the-voice-chapter-1/assist-dialog.png" alt="Screenshot of the Assist dialog" class='no-shadow' />
## Assist on Android Wear
We want to make it as easy as possible to use Assist. To enable this for Android users, we have added a new tile to the Android Wear app. A simple swipe from the clock face will show the assist button and allows you to send voice commands.
[Assist on Android Wear documentation.](https://next.home-assistant.io/docs/assist/android/)
_The new tile is currently available in the [Android beta](https://play.google.com/apps/testing/io.homeassistant.companion.android) and will be part of the next Android release._
<lite-youtube videoid="Dr_ZCbt8w5k" videotitle="Assist on Android Wear"></lite-youtube>
## Assist via Siri and Apple Shortcuts
For Apple devices we have been able to create a fully hands-free experience by integrating with Siri. This is powered by a new Apple Shortcut action called Assist, which is part of the Home Assistant app. This shortcut action can also be manually triggered from your Mac taskbar, iPhone home screen or Apple Watch complication. We have two ready-made shortcuts that users can import from the documentation with a single tap to unlock these features.
[Assist via Siri and Apple Shortcuts documentation.](https://next.home-assistant.io/docs/assist/apple/)
_The Assist shortcut will be available in the Mac and iOS beta channel today and will be part of the next release for iOS and Mac._
<lite-youtube videoid="sQ7X7jz1SrA" videotitle="Assist on Apple HomePod"></lite-youtube>
## Custom Sentences
With Home Assistant we believe that every home is uniquely yours and that [technology should adapt to you, not the other way around.](https://www.home-assistant.io/blog/2016/01/19/perfect-home-automation/) That's why we have architected Home Assistant to allow users to extensively customize their experience. Our Assist feature is no different.
- Are you into Game of Thrones and want every response to be "hodor"?
- Want to turn on lights in rooms by saying "Hocus pocus living room"?
- Want to trigger your party mode script using a custom sentence?
Assist includes support for custom sentences, responses and intents, allowing you to achieve all of the above, and more. We've designed the custom sentence format in a way that it can be easily shared with the community.
Read [the documentation](https://next.home-assistant.io/docs/assist/custom_sentences) on how to get started.
_In a future release we're planning on adding a user interface to customize and import sentences._
## Custom Assist engines
By default Assist is powered by our own intent recognizer. It is local but it's limited to controlling devices. Maybe you want to be able to ask more wide-range queries or you are looking for a conversational AI that will make up responses and present it as the truth. For such cases the Assist feature supports [swapping out its engine](https://developers.home-assistant.io/docs/core/conversation/custom_agent) that handles all Assist interactions.
The Home Assistant 2023.2 release includes two alternative Assist engines that you can enable: Google Assistant and OpenAI GPT-3.
The Google Assistant Assist engine is able to control your devices if you have linked up your Home Assistant instance to Google Assistant.
All ways to intereact with Assist will work, as they are not bound to the the Assist engine that is being used. So if you ever wanted to use Google Assistant on your HomePod, now you can 🤭
<lite-youtube videoid="orgTMVy0TrI" videotitle="Google Assistant on Apple HomePod"></lite-youtube>
The OpenAI GPT-3 Assist engine will process all your interactions using GPT-3, a sibling of the infamous ChatGPT. It is not able to control your house or [help you automate your house](/blog/2023/01/23/help-others-leave-ai-at-the-dor/). Anything you ask it may or may not be factually correct. But it can be fun!
_In a future release we're planning to make it possible to configure multiple Assist engines to handle interactions._
## What's next
For Year of the Voice - Chapter 1 we focused on building intent recognition into Home Assistant while relying on Google and Apple to do the hard parts (speech recognition). This allowed us the fastest path to get something to the community to play with.
We will continue collecting home automation sentences for all languages ([anyone can help!](https://developers.home-assistant.io/docs/voice/intent-recognition/)). Updates will be included with every major release of Home Assistant.
Our next step is integrating Speech-to-Text and Text-to-Speech with Assist. We don't have a timeline yet when that will be ready. Stay tuned!
## Credits
A lot of people have worked very hard to make all of the above possible.
**Technology:**
[Mike Hansen](https://github.com/synesthesiam), [Paulus Schoutsen](https://github.com/balloob), [Daniel Shokouhi](https://github.com/dshokouhi), [Zac West](https://github.com/zacwest), [Rosemary Orchard](https://github.com/rosemaryorchard), [Tronikos](https://github.com/tronikos)
**Language Leaders:**
[@AalianKhan](https://github.com/AalianKhan), [@Ahmed-farag36](https://github.com/Ahmed-farag36), [@alpdmrel](https://github.com/alpdmrel), [@arunshekher](https://github.com/arunshekher), [@auanasgheps](https://github.com/auanasgheps), [@benjaminlecouteux](https://github.com/benjaminlecouteux), [@bluefoxlee](https://github.com/bluefoxlee), [@cibernox](https://github.com/cibernox), [@cvladan](https://github.com/cvladan), [@davefx](https://github.com/davefx), [@dinhchinh82](https://github.com/dinhchinh82), [@dsimop](https://github.com/dsimop), [@duhow](https://github.com/duhow), [@easterapps](https://github.com/easterapps), [@ErnestStaug](https://github.com/ErnestStaug), [@fadamsen](https://github.com/fadamsen), [@flexy2dd](https://github.com/flexy2dd), [@gabimarchidan](https://github.com/gabimarchidan), [@haim-b](https://github.com/haim-b), [@halecivo](https://github.com/halecivo), [@HepoH3](https://github.com/HepoH3), [@hertzg](https://github.com/hertzg), [@hristo-atanasov](https://github.com/hristo-atanasov), [@huusissa](https://github.com/huusissa), [@joaorgoncalves](https://github.com/joaorgoncalves), [@larsdunemark](https://github.com/larsdunemark), [@leranp](https://github.com/leranp), [@LubosKadasi](https://github.com/LubosKadasi), [@makstech](https://github.com/makstech), [@mojikosu](https://github.com/mojikosu), [@MTrab](https://github.com/MTrab), [@nagyrobi](https://github.com/nagyrobi), [@schizza](https://github.com/schizza), [@Scorpoon](https://github.com/Scorpoon), [@skynetua](https://github.com/skynetua), [@spuljko](https://github.com/spuljko), [@tetele](https://github.com/tetele), [@TheFes](https://github.com/TheFes), [@Uriziel01](https://github.com/Uriziel01), [@xraver](https://github.com/xraver), [@zubir2k](https://github.com/zubir2k)
**Voice Community:**
[@Alexivia](https://github.com/Alexivia), [@Atalonica](https://github.com/Atalonica), [@AwesomeGuy000](https://github.com/AwesomeGuy000), [@BossNeo](https://github.com/BossNeo), [@CedricFinance](https://github.com/CedricFinance), [@Davidsoff](https://github.com/Davidsoff), [@EmilZackrisson](https://github.com/EmilZackrisson), [@FragMenthor](https://github.com/FragMenthor), [@InfiniteBed](https://github.com/InfiniteBed), [@Kalma-House](https://github.com/Kalma-House), [@Licmeth](https://github.com/Licmeth), [@Marlo461](https://github.com/Marlo461), [@N3rdix](https://github.com/N3rdix), [@Nismonx](https://github.com/Nismonx), [@Robin-St](https://github.com/Robin-St), [@TaQuangTien](https://github.com/TaQuangTien), [@ThomDietrich](https://github.com/ThomDietrich), [@TomaszPilch](https://github.com/TomaszPilch), [@Wojciechgc](https://github.com/Wojciechgc), [@alessandroias](https://github.com/alessandroias), [@bemble](https://github.com/bemble), [@berendhaan](https://github.com/berendhaan), [@dejan2101](https://github.com/dejan2101), [@dependabot[@bot]](https://github.com/dependabot[@bot]), [@dobromir-hristov](https://github.com/dobromir-hristov), [@frenck](https://github.com/frenck), [@hugovsky](https://github.com/hugovsky), [@iddiek](https://github.com/iddiek), [@jfisbein](https://github.com/jfisbein), [@jharrvis](https://github.com/jharrvis), [@jorclaret](https://github.com/jorclaret), [@kamildoleglo](https://github.com/kamildoleglo), [@kblin](https://github.com/kblin), [@khymmera](https://github.com/khymmera), [@kroimon](https://github.com/kroimon), [@lellky](https://github.com/lellky), [@ludeeus](https://github.com/ludeeus), [@lukahra](https://github.com/lukahra), [@lunmay](https://github.com/lunmay), [@mardito](https://github.com/mardito), [@martindybal](https://github.com/martindybal), [@mib1185](https://github.com/mib1185), [@michaelmior](https://github.com/michaelmior), [@orrc](https://github.com/orrc), [@pckahrs](https://github.com/pckahrs), [@piitaya](https://github.com/piitaya), [@pmentis](https://github.com/pmentis), [@poltalashka](https://github.com/poltalashka), [@rPonuganti](https://github.com/rPonuganti), [@rechin304](https://github.com/rechin304), [@relust](https://github.com/relust), [@rickydg](https://github.com/rickydg), [@rpochot](https://github.com/rpochot), [@rrakso](https://github.com/rrakso), [@rumbu13](https://github.com/rumbu13), [@sanyatuning](https://github.com/sanyatuning), [@tasmin](https://github.com/tasmin), [@thecode](https://github.com/thecode), [@waltlillyman](https://github.com/waltlillyman), [@witold-gren](https://github.com/witold-gren), [@x15pa3ck15x](https://github.com/x15pa3ck15x), [@yuvalabou](https://github.com/yuvalabou)

2
source/_redirects
View File

@ -232,7 +232,7 @@
/docs/mqtt/birth_will /integrations/mqtt/#birth-and-last-will-messages
/docs/mqtt/broker /integrations/mqtt/#broker-configuration
/docs/mqtt/certificate /integrations/mqtt/#advanced-broker-configuration
/docs/mqtt/discovery /integrations/mqtt/#mqtt-discovery
/integrations/mqtt/#mqtt-discovery /integrations/mqtt/#mqtt-discovery
/docs/mqtt/logging /integrations/mqtt/#logging
/docs/mqtt/service /integrations/mqtt/#publish--dump-services
/docs/mqtt/testing /integrations/mqtt/#testing-your-setup

2
source/docs/index.markdown
View File

@ -19,7 +19,7 @@ The documentation covers beginner to advanced topics around the installation, se
</div>
<div class='title'>Configuration</div>
</a>
<a class='option-card' href='/docs/mqtt/'>
<a class='option-card' href='/integrations/mqtt/'>
<div class='img-container'>
<img src='https://brands.home-assistant.io/mqtt/icon.png' />
</div>

1
source/images/assist/assist-icon.svg Normal file
View File

@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M9,22A1,1 0 0,1 8,21V18H4A2,2 0 0,1 2,16V4C2,2.89 2.9,2 4,2H20A2,2 0 0,1 22,4V16A2,2 0 0,1 20,18H13.9L10.2,21.71C10,21.9 9.75,22 9.5,22V22H9M10,16V19.08L13.08,16H20V4H4V16H10M17,11H15V9H17V11M13,11H11V9H13V11M9,11H7V9H9V11Z" /></svg>
Side by Side

After

Width:  |  Height:  |  Size: 303 B

BIN
source/images/blog/2023-01-26-year-of-the-voice-chapter-1/assist-dialog.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.8 KiB

BIN
source/images/blog/2023-01-26-year-of-the-voice-chapter-1/social.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 96 KiB