mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-15 21:36:52 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
159c4b2cd8
31
CODEOWNERS
31
CODEOWNERS
@ -27,6 +27,7 @@ source/_integrations/airtouch4.markdown @LonePurpleWolf
|
||||
source/_integrations/airvisual.markdown @bachya
|
||||
source/_integrations/airvisual_pro.markdown @bachya
|
||||
source/_integrations/airzone.markdown @Noltari
|
||||
source/_integrations/airzone_cloud.markdown @Noltari
|
||||
source/_integrations/aladdin_connect.markdown @mkmer
|
||||
source/_integrations/alarm_control_panel.markdown @home-assistant/core
|
||||
source/_integrations/alert.markdown @home-assistant/core @frenck
|
||||
@ -40,7 +41,7 @@ source/_integrations/amp_motorization.markdown @starkillerOG
|
||||
source/_integrations/analytics.markdown @home-assistant/core @ludeeus
|
||||
source/_integrations/android_ip_webcam.markdown @engrbm87
|
||||
source/_integrations/androidtv.markdown @JeffLIrion @ollo69
|
||||
source/_integrations/androidtv_remote.markdown @tronikos
|
||||
source/_integrations/androidtv_remote.markdown @tronikos @Drafteed
|
||||
source/_integrations/anova.markdown @Lash-L
|
||||
source/_integrations/anthemav.markdown @hyralex
|
||||
source/_integrations/anwb_energie.markdown @klaasnicolaas
|
||||
@ -121,6 +122,7 @@ source/_integrations/cloudflare.markdown @ludeeus @ctalkington
|
||||
source/_integrations/coinbase.markdown @tombrien
|
||||
source/_integrations/color_extractor.markdown @GenericStudent
|
||||
source/_integrations/comfoconnect.markdown @michaelarnauts
|
||||
source/_integrations/command_line.markdown @gjohansson-ST
|
||||
source/_integrations/compensation.markdown @Petro31
|
||||
source/_integrations/config.markdown @home-assistant/core
|
||||
source/_integrations/configurator.markdown @home-assistant/core
|
||||
@ -135,6 +137,8 @@ source/_integrations/crownstone.markdown @Crownstone @RicArch97
|
||||
source/_integrations/cups.markdown @fabaff
|
||||
source/_integrations/dacia.markdown @epenet
|
||||
source/_integrations/daikin.markdown @fredrike
|
||||
source/_integrations/date.markdown @home-assistant/core
|
||||
source/_integrations/datetime.markdown @home-assistant/core
|
||||
source/_integrations/debugpy.markdown @frenck
|
||||
source/_integrations/deconz.markdown @Kane610
|
||||
source/_integrations/default_config.markdown @home-assistant/core
|
||||
@ -176,6 +180,7 @@ source/_integrations/ecowitt.markdown @pvizeli
|
||||
source/_integrations/efergy.markdown @tkdrob
|
||||
source/_integrations/egardia.markdown @jeroenterheerdt
|
||||
source/_integrations/eight_sleep.markdown @mezz64 @raman325
|
||||
source/_integrations/electrasmart.markdown @jafar-atili
|
||||
source/_integrations/elgato.markdown @frenck
|
||||
source/_integrations/elkm1.markdown @gwww @bdraco
|
||||
source/_integrations/elmax.markdown @albertogeniola
|
||||
@ -259,6 +264,7 @@ source/_integrations/google.markdown @allenporter
|
||||
source/_integrations/google_assistant.markdown @home-assistant/cloud
|
||||
source/_integrations/google_assistant_sdk.markdown @tronikos
|
||||
source/_integrations/google_cloud.markdown @lufton
|
||||
source/_integrations/google_generative_ai_conversation.markdown @tronikos
|
||||
source/_integrations/google_mail.markdown @tkdrob
|
||||
source/_integrations/google_sheets.markdown @tkdrob
|
||||
source/_integrations/google_travel_time.markdown @eifinger
|
||||
@ -305,7 +311,7 @@ source/_integrations/humidifier.markdown @home-assistant/core @Shulyaka
|
||||
source/_integrations/hunterdouglas_powerview.markdown @bdraco @kingy444 @trullock
|
||||
source/_integrations/hurrican_shutters_wholesale.markdown @starkillerOG
|
||||
source/_integrations/hvv_departures.markdown @vigonotion
|
||||
source/_integrations/hydrawise.markdown @ptcryan
|
||||
source/_integrations/hydrawise.markdown @dknowles2 @ptcryan
|
||||
source/_integrations/hyperion.markdown @dermotduffy
|
||||
source/_integrations/ialarm.markdown @RyuzakiKK
|
||||
source/_integrations/iammeter.markdown @lewei50
|
||||
@ -345,6 +351,7 @@ source/_integrations/jellyfin.markdown @j-stienstra @ctalkington
|
||||
source/_integrations/jewish_calendar.markdown @tsvi
|
||||
source/_integrations/juicenet.markdown @jesserockz
|
||||
source/_integrations/justnimbus.markdown @kvanzuijlen
|
||||
source/_integrations/jvc_projector.markdown @SteveEasley
|
||||
source/_integrations/kaiterra.markdown @Michsior14
|
||||
source/_integrations/kaleidescape.markdown @SteveEasley
|
||||
source/_integrations/keba.markdown @dannerph
|
||||
@ -364,6 +371,7 @@ source/_integrations/kulersky.markdown @emlove
|
||||
source/_integrations/lacrosse_view.markdown @IceBotYT
|
||||
source/_integrations/lametric.markdown @robbiet480 @frenck @bachya
|
||||
source/_integrations/landisgyr_heat_meter.markdown @vpathuis
|
||||
source/_integrations/lastfm.markdown @joostlek
|
||||
source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol
|
||||
source/_integrations/laundrify.markdown @xLarry
|
||||
source/_integrations/lcn.markdown @alengwenus
|
||||
@ -447,6 +455,7 @@ source/_integrations/nest.markdown @allenporter
|
||||
source/_integrations/netatmo.markdown @cgtobi
|
||||
source/_integrations/netdata.markdown @fabaff
|
||||
source/_integrations/netgear.markdown @hacf-fr @Quentame @starkillerOG
|
||||
source/_integrations/netgear_lte.markdown @tkdrob
|
||||
source/_integrations/network.markdown @home-assistant/core
|
||||
source/_integrations/nexia.markdown @bdraco
|
||||
source/_integrations/nexity.markdown @imicknl @vlebourl @tetienne @nyroDev
|
||||
@ -491,6 +500,7 @@ source/_integrations/openerz.markdown @misialq
|
||||
source/_integrations/openexchangerates.markdown @MartinHjelmare
|
||||
source/_integrations/opengarage.markdown @danielhiversen
|
||||
source/_integrations/openhome.markdown @bazwilliams
|
||||
source/_integrations/opensky.markdown @joostlek
|
||||
source/_integrations/opentherm_gw.markdown @mvn23
|
||||
source/_integrations/openuv.markdown @bachya
|
||||
source/_integrations/openweathermap.markdown @fabaff @freekode @nzapponi
|
||||
@ -510,6 +520,7 @@ source/_integrations/philips_js.markdown @elupus
|
||||
source/_integrations/pi_hole.markdown @johnluetke @shenxn
|
||||
source/_integrations/picnic.markdown @corneyl
|
||||
source/_integrations/pilight.markdown @trekky12
|
||||
source/_integrations/piper.markdown @balloob @synesthesiam
|
||||
source/_integrations/plaato.markdown @JohNan
|
||||
source/_integrations/plex.markdown @jjlawren
|
||||
source/_integrations/plugwise.markdown @CoMPaTech @bouwew @frenck
|
||||
@ -542,7 +553,7 @@ source/_integrations/qwikswitch.markdown @kellerza
|
||||
source/_integrations/rachio.markdown @bdraco
|
||||
source/_integrations/radarr.markdown @tkdrob
|
||||
source/_integrations/radio_browser.markdown @frenck
|
||||
source/_integrations/radiotherm.markdown @bdraco @vinnyfuria
|
||||
source/_integrations/radiotherm.markdown @vinnyfuria
|
||||
source/_integrations/rainbird.markdown @konikvranik @allenporter
|
||||
source/_integrations/raincloud.markdown @vanstinator
|
||||
source/_integrations/rainforest_eagle.markdown @gtdiehl @jcalbert @hastarin
|
||||
@ -566,7 +577,7 @@ source/_integrations/rfxtrx.markdown @danielhiversen @elupus @RobBie1221
|
||||
source/_integrations/rhasspy.markdown @balloob @synesthesiam
|
||||
source/_integrations/ridwell.markdown @bachya
|
||||
source/_integrations/risco.markdown @OnFreund
|
||||
source/_integrations/rituals_perfume_genie.markdown @milanmeu
|
||||
source/_integrations/rituals_perfume_genie.markdown @milanmeu @frenck
|
||||
source/_integrations/rmvtransport.markdown @cgtobi
|
||||
source/_integrations/roborock.markdown @humbertogontijo @Lash-L
|
||||
source/_integrations/roku.markdown @ctalkington
|
||||
@ -622,7 +633,7 @@ source/_integrations/siren.markdown @home-assistant/core @raman325
|
||||
source/_integrations/sisyphus.markdown @jkeljo
|
||||
source/_integrations/sky_hub.markdown @rogerselwyn
|
||||
source/_integrations/skybell.markdown @tkdrob
|
||||
source/_integrations/slack.markdown @bachya @tkdrob
|
||||
source/_integrations/slack.markdown @tkdrob
|
||||
source/_integrations/sleepiq.markdown @mfugate1 @kbickar
|
||||
source/_integrations/slide.markdown @ualex73
|
||||
source/_integrations/slimproto.markdown @marcelveldt
|
||||
@ -654,7 +665,7 @@ source/_integrations/speedtestdotnet.markdown @rohankapoorcom @engrbm87
|
||||
source/_integrations/spider.markdown @peternijssen
|
||||
source/_integrations/splunk.markdown @Bre77
|
||||
source/_integrations/spotify.markdown @frenck
|
||||
source/_integrations/sql.markdown @dgomes @gjohansson-ST @dougiteixeira
|
||||
source/_integrations/sql.markdown @gjohansson-ST @dougiteixeira
|
||||
source/_integrations/squeezebox.markdown @rajlaud
|
||||
source/_integrations/srp_energy.markdown @briglx
|
||||
source/_integrations/starline.markdown @anonym-tsk
|
||||
@ -678,7 +689,7 @@ source/_integrations/switch.markdown @home-assistant/core
|
||||
source/_integrations/switch_as_x.markdown @home-assistant/core
|
||||
source/_integrations/switchbee.markdown @jafar-atili
|
||||
source/_integrations/switchbot.markdown @bdraco @danielhiversen @RenierM26 @murtas @Eloston @dsypniewski
|
||||
source/_integrations/switcher_kis.markdown @tomerfi @thecode
|
||||
source/_integrations/switcher_kis.markdown @thecode
|
||||
source/_integrations/switchmate.markdown @danielhiversen @qiz-li
|
||||
source/_integrations/symfonisk.markdown @cgtobi @jjlawren
|
||||
source/_integrations/syncthing.markdown @zhulik
|
||||
@ -686,7 +697,7 @@ source/_integrations/syncthru.markdown @nielstron
|
||||
source/_integrations/synology_dsm.markdown @hacf-fr @Quentame @mib1185
|
||||
source/_integrations/synology_srm.markdown @aerialls
|
||||
source/_integrations/system_bridge.markdown @timmo001
|
||||
source/_integrations/tado.markdown @michaelarnauts
|
||||
source/_integrations/tado.markdown @michaelarnauts @chiefdragon
|
||||
source/_integrations/tag.markdown @balloob @dmulcahey
|
||||
source/_integrations/tailscale.markdown @frenck
|
||||
source/_integrations/tankerkoenig.markdown @guillempages @mib1185
|
||||
@ -706,6 +717,7 @@ source/_integrations/thread.markdown @home-assistant/core
|
||||
source/_integrations/tibber.markdown @danielhiversen
|
||||
source/_integrations/tile.markdown @bachya
|
||||
source/_integrations/tilt_ble.markdown @apt-itude
|
||||
source/_integrations/time.markdown @home-assistant/core
|
||||
source/_integrations/time_date.markdown @fabaff
|
||||
source/_integrations/tmb.markdown @alemuro
|
||||
source/_integrations/todoist.markdown @boralyl
|
||||
@ -772,6 +784,7 @@ source/_integrations/webostv.markdown @thecode
|
||||
source/_integrations/websocket_api.markdown @home-assistant/core
|
||||
source/_integrations/wemo.markdown @esev
|
||||
source/_integrations/whirlpool.markdown @abmantis @mkmer
|
||||
source/_integrations/whisper.markdown @balloob @synesthesiam
|
||||
source/_integrations/whois.markdown @frenck
|
||||
source/_integrations/wiffi.markdown @mampfes
|
||||
source/_integrations/wilight.markdown @leofig-rj
|
||||
@ -790,6 +803,7 @@ source/_integrations/xiaomi_ble.markdown @Jc2k @Ernst79
|
||||
source/_integrations/xiaomi_miio.markdown @rytilahti @syssi @starkillerOG
|
||||
source/_integrations/xiaomi_tv.markdown @simse
|
||||
source/_integrations/xmpp.markdown @fabaff @flowolf
|
||||
source/_integrations/yale_home.markdown @bdraco
|
||||
source/_integrations/yale_smart_alarm.markdown @gjohansson-ST
|
||||
source/_integrations/yalexs_ble.markdown @bdraco
|
||||
source/_integrations/yamaha_musiccast.markdown @vigonotion @micha91
|
||||
@ -799,6 +813,7 @@ source/_integrations/yeelightsunflower.markdown @lindsaymarkward
|
||||
source/_integrations/yi.markdown @bachya
|
||||
source/_integrations/yolink.markdown @matrixd2
|
||||
source/_integrations/youless.markdown @gjong
|
||||
source/_integrations/youtube.markdown @joostlek
|
||||
source/_integrations/zamg.markdown @killer0071234
|
||||
source/_integrations/zengge.markdown @emontnemery
|
||||
source/_integrations/zeroconf.markdown @bdraco
|
||||
|
||||
10
Gemfile.lock
10
Gemfile.lock
@ -78,7 +78,7 @@ GEM
|
||||
pathutil (0.16.2)
|
||||
forwardable-extended (~> 2.6)
|
||||
public_suffix (5.0.1)
|
||||
racc (1.6.2)
|
||||
racc (1.7.0)
|
||||
rack (2.2.7)
|
||||
rack-protection (3.0.6)
|
||||
rack
|
||||
@ -91,11 +91,11 @@ GEM
|
||||
ruby2_keywords (0.0.5)
|
||||
safe_yaml (1.0.5)
|
||||
sass (3.4.25)
|
||||
sass-embedded (1.62.1)
|
||||
google-protobuf (~> 3.21)
|
||||
sass-embedded (1.63.2)
|
||||
google-protobuf (~> 3.23)
|
||||
rake (>= 10.0.0)
|
||||
sass-embedded (1.62.1-x64-mingw32)
|
||||
google-protobuf (~> 3.21)
|
||||
sass-embedded (1.63.2-x64-mingw32)
|
||||
google-protobuf (~> 3.23)
|
||||
sass-globbing (1.1.5)
|
||||
sass (>= 3.1)
|
||||
sassc (2.1.0)
|
||||
|
||||
@ -109,9 +109,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 2023
|
||||
current_minor_version: 5
|
||||
current_patch_version: 4
|
||||
date_released: 2023-05-23
|
||||
current_minor_version: 6
|
||||
current_patch_version: 0
|
||||
date_released: 2023-06-07
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -17,6 +17,7 @@
|
||||
<li>{% active_link /voice_control/voice_remote_expose_devices/ Exposing devices to voice assistant %}</li>
|
||||
<li>{% active_link /voice_control/builtin_sentences/ Built-in sentences %}</li>
|
||||
<li>{% active_link /voice_control/custom_sentences/ Custom sentences %}</li>
|
||||
<li>{% active_link /voice_control/using_tts_in_automation/ Using Piper TTS in automations %}</li>
|
||||
<li>{% active_link /voice_control/troubleshooting/ Troubleshooting Assist %}</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
@ -23,17 +23,16 @@ manually:
|
||||
{% endif %}
|
||||
|
||||
- Browse to your Home Assistant instance.
|
||||
- In the sidebar, select **{% my config icon %}**.
|
||||
- From the configuration menu, select **{% my integrations %}**.
|
||||
- Go to **{% my integrations title="Settings > Devices & Services" %}**.
|
||||
{% if page.ha_integration_type == 'helper' %}
|
||||
- In top of the screen, select the tab: **{% my helpers %}**.
|
||||
- In the bottom right, select the
|
||||
- At the top of the screen, select the tab: **{% my helpers %}**.
|
||||
- In the bottom right corner, select the
|
||||
**{% my config_flow_start icon domain=domain title="Create helper" %}** button.
|
||||
{% else %}
|
||||
- In the bottom right, select the
|
||||
- In the bottom right corner, select the
|
||||
**{% my config_flow_start icon domain=domain %}** button.
|
||||
{% endif %}
|
||||
- From the list, search and select **{{ name }}**.
|
||||
- From the list, select **{{ name }}**.
|
||||
- Follow the instructions on screen to complete the setup.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
@ -17,6 +17,8 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@gjohansson-ST'
|
||||
---
|
||||
|
||||
The `command_line` offers functionality that issues specific commands to get data or to control a device.
|
||||
@ -219,7 +221,7 @@ command_line:
|
||||
description: The name used to display the switch in the frontend.
|
||||
required: true
|
||||
type: string
|
||||
icon_template:
|
||||
icon:
|
||||
description: Defines a template for the icon of the entity.
|
||||
required: false
|
||||
type: template
|
||||
|
||||
@ -3,11 +3,11 @@ title: Date/Time
|
||||
description: Instructions on how to set up date/time entities within Home Assistant.
|
||||
ha_category:
|
||||
- Date/Time
|
||||
ha_release: '2023.6'
|
||||
ha_release: "2023.6"
|
||||
ha_domain: datetime
|
||||
ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
- "@home-assistant/core"
|
||||
ha_integration_type: entity
|
||||
---
|
||||
|
||||
@ -25,8 +25,7 @@ Available services: `datetime.set_value`
|
||||
|
||||
Set a new value for the datetime entity.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`'s of datetimes to control.
|
||||
| `datetime` | no | New datetime value to set. If timezone is not included, the Home Assistant instance's timezone will be used.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ------------------------------------------------------------------------------------------------------------ |
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`'s of datetimes to control. |
|
||||
| `datetime` | no | New datetime value to set. If timezone is not included, the Home Assistant instance's timezone will be used. |
|
||||
|
||||
@ -40,6 +40,8 @@ ha_platforms:
|
||||
- vacuum
|
||||
- water_heater
|
||||
- weather
|
||||
- date
|
||||
- time
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
|
||||
@ -21,6 +21,7 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- climate
|
||||
- cover
|
||||
- diagnostics
|
||||
- light
|
||||
- sensor
|
||||
- siren
|
||||
|
||||
@ -4,6 +4,7 @@ description: Integrate EZVIZ camera within Home Assistant.
|
||||
ha_release: 0.107
|
||||
ha_category:
|
||||
- Camera
|
||||
- Update
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: ezviz
|
||||
ha_codeowners:
|
||||
|
||||
@ -98,15 +98,19 @@ If commands don't work try removing superfluous words such as "the". E.g. "play
|
||||
|
||||
If broadcasting doesn't work, make sure: the speakers aren't in do not disturb mode, the Home Assistant server is in the same network as the speakers, and IPv6 is disabled in the router.
|
||||
|
||||
The easiest way to check if the integration is working is to check [My Google Activity](https://myactivity.google.com/myactivity) for the issued commands and their responses.
|
||||
|
||||
## Limitations/known issues
|
||||
|
||||
Multiple Google accounts are not supported.
|
||||
|
||||
Limitations of the underlying library are listed [here](https://github.com/tronikos/gassist_text#limitationsknown-issues) (media playback, routines, and personal results are not working).
|
||||
- Multiple Google accounts are not supported.
|
||||
- Personal results are not supported yet since that requires creating an OAuth client ID of the Desktop app.
|
||||
- If you see the issued commands in [My Google Activity](https://myactivity.google.com/myactivity), the integration is working fine. If the commands don't have the expected outcome, don't open an issue in the Home Assistant Core project or the [underlying library](https://github.com/tronikos/gassist_text). You should instead report the issue directly to Google [here](https://github.com/googlesamples/assistant-sdk-python/issues). Examples of known Google Assistant API issues:
|
||||
- Media playback commands (other than play news, play podcast, play white noise, or play rain sounds) don't work.
|
||||
- Routines don't work.
|
||||
|
||||
## Configuration
|
||||
|
||||
On the configure page, you can set the language code of the interactions with Google Assistant. If not configured, the integration picks one based on Home Assistant's configured language and country. Supported languages are listed [here](https://developers.google.com/assistant/sdk/reference/rpc/languages)
|
||||
On the configure page, you can set the language code of the interactions with Google Assistant. If not configured, the integration picks one based on Home Assistant's configured language and country. Supported languages are listed [here](https://developers.google.com/assistant/sdk/reference/rpc/languages).
|
||||
|
||||
## Services
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ ha_release: 0.71
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: hydrawise
|
||||
ha_codeowners:
|
||||
- '@dknowles2'
|
||||
- '@ptcryan'
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
|
||||
@ -11,7 +11,7 @@ ha_codeowners:
|
||||
ha_domain: jvc_projector
|
||||
ha_platforms:
|
||||
- remote
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
---
|
||||
|
||||
The JVC Projector integration allows for the automation of [JVC Projectors](https://www.jvc.com/usa/projectors/).
|
||||
|
||||
@ -10,6 +10,7 @@ ha_codeowners:
|
||||
- '@IceBotYT'
|
||||
ha_domain: lacrosse_view
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -10,6 +10,8 @@ ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@joostlek'
|
||||
---
|
||||
|
||||
The `lastfm` sensor platform will allow you to see whenever a user starts scrobbling, their play count, last song played, and top song played on [Last.fm](https://www.last.fm/).
|
||||
|
||||
@ -17,6 +17,7 @@ ha_domain: nest
|
||||
ha_quality_scale: platinum
|
||||
ha_dhcp: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- camera
|
||||
- climate
|
||||
- diagnostics
|
||||
@ -54,11 +55,10 @@ Adding Nest to your Home Assistant instance can be done via the user interface,
|
||||
{% details "Manual configuration steps" %}
|
||||
|
||||
1. Browse to your Home Assistant instance.
|
||||
1. In the sidebar click on _**{% my config icon %}**_.
|
||||
1. From the configuration menu select: _**{% my integrations %}**_.
|
||||
1. In the bottom right, click on the
|
||||
_**{% my config_flow_start icon domain=page.ha_domain %}**_ button.
|
||||
1. From the list, search and select _**"Nest"**_ and follow the instructions.
|
||||
1. Go to **{% my integrations title="Settings > Devices & Services" %}**.
|
||||
1. In the bottom right corner, select the
|
||||
**{% my config_flow_start icon domain=page.ha_domain %}** button.
|
||||
1. From the list, select **Nest** and follow the instructions on screen.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
@ -422,9 +422,8 @@ To improve security and reduce phishing risk Google has [deprecated](https://dev
|
||||
{% details "Reconfigure the integration %}
|
||||
|
||||
1. Make sure to upgrade to the latest version of Home Assistant.
|
||||
1. In the sidebar click on _**{% my config icon %}**_.
|
||||
1. From the configuration menu select: _**{% my integrations %}**_.
|
||||
1. The *Nest* integration should appear with alert.
|
||||
1. Go to **{% my integrations title="Settings > Devices & Services" %}**.
|
||||
1. The **Nest** integration should appear with alert.
|
||||
|
||||
|
||||
|
||||
@ -581,4 +580,4 @@ logger:
|
||||
|
||||
The Legacy [Works with Nest](https://developers.nest.com/) API is deprecated, and will be shut down by Google in September 2023.
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -14,6 +14,8 @@ ha_platforms:
|
||||
- notify
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@tkdrob'
|
||||
---
|
||||
|
||||
The NETGEAR LTE integration for Home Assistant allows you to observe and control [NETGEAR LTE modems](https://www.netgear.com/home/mobile-wifi/lte-modems/).
|
||||
|
||||
@ -4,7 +4,7 @@ description: Instructions on how to use public transit data from Nextbus in Home
|
||||
ha_category:
|
||||
- Sensor
|
||||
- Transport
|
||||
ha_iot_class: Local Polling
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.93
|
||||
ha_codeowners:
|
||||
- '@vividboarder'
|
||||
|
||||
@ -9,6 +9,8 @@ ha_domain: opensky
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@joostlek'
|
||||
---
|
||||
|
||||
The `opensky` sensor allows one to track overhead flights in a given region. It uses crowd-sourced data from the [OpenSky Network](https://opensky-network.org/) public API. It will also fire Home Assistant events when flights enter and exit the defined region.
|
||||
|
||||
@ -41,4 +41,4 @@ This integration will create 5 entities.
|
||||
- A sensor that shows the total amount of customers with no power.
|
||||
- A sensor that shows the total amount of customers served in the county.
|
||||
- A sensor that shows the percentage of customers with no power.
|
||||
- A sensor that shows the alert that appears when you open the online outage map.
|
||||
- A sensor that shows the alert that appears when you open the online outage map.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Piper
|
||||
description: Connect and control your Piper instance using the Wyoming Protocol integration
|
||||
description: Connect and control your Piper devices using the Wyoming Protocol integration
|
||||
ha_category:
|
||||
- Voice
|
||||
ha_domain: piper
|
||||
|
||||
@ -9,7 +9,6 @@ ha_release: 0.7.6
|
||||
ha_domain: radiotherm
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@bdraco'
|
||||
- '@vinnyfuria'
|
||||
ha_platforms:
|
||||
- climate
|
||||
|
||||
@ -205,6 +205,18 @@ However, these cameras can work with this integration through an NVR in which th
|
||||
- E1 Pro
|
||||
- E1
|
||||
|
||||
## Initial Setup
|
||||
|
||||
You'll need to configure your new camera/doorbell for your network. If you're using a wired LAN, this is simple enough. Simply plug it in and let it use DHCP to set itself up. Once it's recognized by your network, you can access its configuration with a web browser.
|
||||
|
||||
If you prefer to use Wi-Fi, especially if you want to restrict it to a local IoT network, [here's a quick way to get it connected](https://www.reddit.com/r/reolink/comments/hjn5be/how_to_connect_wifi_without_an_app/). Simply create a QR code with the following XML string:
|
||||
|
||||
<QR><S>ssid</S><P>password</P><C>last4</C></QR>
|
||||
|
||||
Use the `ssid` and `password` of your IoT network. The `last4` is the last 4 digits of the QR code used for the Reolink setup. It's printed under the QR code. You can also scan the QR code and grab the last 4 digits.
|
||||
|
||||
Then power up the camera while pointing it at the QR code. It takes about a minute to initialize, read the QR code, and attach.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
- Older firmware versions do not expose the necessary information the integration needs to function. Ensure the camera is updated to the [latest firmware](https://reolink.com/download-center/) prior to setting up the integration. Note that Reolink auto update and check for update functions in the app/windows/web client often do not show the latest available firmware version. Therefore check the version in the [Reolink download center](https://reolink.com/download-center/) online.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_category:
|
||||
- Switch
|
||||
ha_codeowners:
|
||||
- '@milanmeu'
|
||||
- '@frenck'
|
||||
ha_domain: rituals_perfume_genie
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
|
||||
@ -15,6 +15,8 @@ ha_codeowners:
|
||||
ha_domain: roborock
|
||||
ha_platforms:
|
||||
- select
|
||||
- sensor
|
||||
- switch
|
||||
- vacuum
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -18,6 +18,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- vacuum
|
||||
ha_integration_type: integration
|
||||
ha_zeroconf: true
|
||||
---
|
||||
|
||||
The `roomba` integration allows you to control your [iRobot Roomba](https://www.irobot.com/roomba) vacuum or [iRobot Braava](https://www.irobot.com/braava) m-series mop.
|
||||
|
||||
@ -210,4 +210,3 @@ The following example turns off some entities as soon as a window opens. The sta
|
||||
target:
|
||||
entity_id: scene.before
|
||||
```
|
||||
|
||||
|
||||
@ -8,7 +8,6 @@ ha_config_flow: true
|
||||
ha_domain: slack
|
||||
ha_iot_class: Cloud Push
|
||||
ha_codeowners:
|
||||
- '@bachya'
|
||||
- '@tkdrob'
|
||||
ha_platforms:
|
||||
- notify
|
||||
|
||||
@ -122,6 +122,7 @@ Note: E3372h-153 and E3372h-510 need to be unlocked [this guide](http://blog.asi
|
||||
- [Huawei E3531](https://www.amazon.com/Modem-Huawei-Unlocked-Caribbean-Desbloqueado/dp/B011YZZ6Q2/ref=sr_1_1?keywords=Huawei+E3531&qid=1581447800&sr=8-1) (note: Devices with firmware versions 22.XX need to be unlocked using [this guide](https://community.home-assistant.io/t/trouble-setting-up-huawei-e3531s-2-with-sms-notifications-via-gsm-modem-integration/462737/9?u=alexschmitz222))
|
||||
- [Huawei E3272](https://www.amazon.com/Huawei-E3272s-506-Unlocked-Americas-Europe/dp/B00HBL51OQ)
|
||||
- ZTE K3565-Z
|
||||
- Lenovo F5521gw (mPCI-E)
|
||||
|
||||
### List of modems known to NOT work
|
||||
|
||||
|
||||
@ -8,7 +8,6 @@ ha_release: 0.63
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@dgomes'
|
||||
- '@gjohansson-ST'
|
||||
- '@dougiteixeira'
|
||||
ha_domain: sql
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Speech-to-text (STT)
|
||||
description: Instructions on how to set up speech-to-text (STT) with Home Assistant.
|
||||
ha_release: '0.102'
|
||||
ha_release: "0.102"
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
- '@pvizeli'
|
||||
- "@home-assistant/core"
|
||||
- "@pvizeli"
|
||||
ha_domain: stt
|
||||
ha_quality_scale: internal
|
||||
ha_category: []
|
||||
|
||||
@ -9,7 +9,6 @@ ha_category:
|
||||
ha_release: 0.93
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@tomerfi'
|
||||
- '@thecode'
|
||||
ha_domain: switcher_kis
|
||||
ha_platforms:
|
||||
|
||||
@ -13,6 +13,7 @@ ha_release: 0.41
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@michaelarnauts'
|
||||
- '@chiefdragon'
|
||||
ha_domain: tado
|
||||
ha_config_flow: true
|
||||
ha_homekit: true
|
||||
|
||||
@ -11,6 +11,7 @@ ha_codeowners:
|
||||
- '@MarkGodwin'
|
||||
ha_domain: tplink_omada
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- switch
|
||||
- update
|
||||
ha_integration_type: hub
|
||||
|
||||
@ -6,8 +6,8 @@ ha_category:
|
||||
- Text-to-speech
|
||||
ha_release: 0.35
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
- '@pvizeli'
|
||||
- "@home-assistant/core"
|
||||
- "@pvizeli"
|
||||
ha_domain: tts
|
||||
ha_quality_scale: internal
|
||||
ha_platforms:
|
||||
@ -23,7 +23,7 @@ Text-to-speech (TTS) enables Home Assistant to speak to you.
|
||||
|
||||
Modern platforms will create entities under the `tts` domain, where each entity represents one text-to-speech service provider. These entities may be used as targets for the `tts.speak` service.
|
||||
|
||||
The `tts.speak` service supports `language` and on some platforms also `options` for settings, e.g., *voice, motion, speed, etc*. The text that should be spoken is set with `message`, and the media player that should output the sound is selected with `media_player_entity_id`.
|
||||
The `tts.speak` service supports `language` and on some platforms also `options` for settings, e.g., _voice, motion, speed, etc_. The text that should be spoken is set with `message`, and the media player that should output the sound is selected with `media_player_entity_id`.
|
||||
|
||||
```yaml
|
||||
service: tts.speak
|
||||
@ -35,7 +35,7 @@ data:
|
||||
|
||||
### Service say (legacy)
|
||||
|
||||
The `say` service supports `language` and on some platforms also `options` for settings, e.g., *voice, motion, speed, etc*. The text that should be spoken is set with `message`. Since release 0.92, service name can be defined in configuration `service_name` option.
|
||||
The `say` service supports `language` and on some platforms also `options` for settings, e.g., _voice, motion, speed, etc_. The text that should be spoken is set with `message`. Since release 0.92, service name can be defined in configuration `service_name` option.
|
||||
|
||||
Say to all `media_player` entities:
|
||||
|
||||
@ -91,8 +91,8 @@ Returns a URL to the generated TTS file. The `engine_id` or `platform` parameter
|
||||
|
||||
```json
|
||||
{
|
||||
"engine_id": "tts.amazon_polly",
|
||||
"message": "I am speaking now"
|
||||
"engine_id": "tts.amazon_polly",
|
||||
"message": "I am speaking now"
|
||||
}
|
||||
```
|
||||
|
||||
@ -100,8 +100,8 @@ The return code is 200 if the file is generated. The message body will contain a
|
||||
|
||||
```json
|
||||
{
|
||||
"path": "/api/tts_proxy/265944c108cbb00b2a621be5930513e03a0bb2cd_en_-_tts.demo.mp3",
|
||||
"url": "http://127.0.0.1:8123/api/tts_proxy/265944c108cbb00b2a621be5930513e03a0bb2cd_en_-_tts.demo.mp3"
|
||||
"path": "/api/tts_proxy/265944c108cbb00b2a621be5930513e03a0bb2cd_en_-_tts.demo.mp3",
|
||||
"url": "http://127.0.0.1:8123/api/tts_proxy/265944c108cbb00b2a621be5930513e03a0bb2cd_en_-_tts.demo.mp3"
|
||||
}
|
||||
```
|
||||
|
||||
@ -134,8 +134,8 @@ The `tts` service will send an `https://` URL to the media device, which will ch
|
||||
|
||||
The Google cast devices (Google Home, Chromecast, etc.) present the following problems:
|
||||
|
||||
* They [reject self-signed certificates](#self-signed-certificates).
|
||||
- They [reject self-signed certificates](#self-signed-certificates).
|
||||
|
||||
* They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). If you are _not_ using SSL then setting an internal URL that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname.
|
||||
- They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). If you are _not_ using SSL then setting an internal URL that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname.
|
||||
|
||||
* If you are using SSL (e.g., `https://yourhost.example.org/...`) then you _must_ use the hostname in the certificate (e.g., `external_url: https://yourhost.example.org`). You cannot use an IP address since the certificate won't be valid for the IP address, and the cast device will refuse the connection.
|
||||
- If you are using SSL (e.g., `https://yourhost.example.org/...`) then you _must_ use the hostname in the certificate (e.g., `external_url: https://yourhost.example.org`). You cannot use an IP address since the certificate won't be valid for the IP address, and the cast device will refuse the connection.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Whisper
|
||||
description: Connect and control your Whisper instance using the Wyoming Protocol integration
|
||||
description: Connect and control your Whisper devices using the Wyoming Protocol integration
|
||||
ha_category:
|
||||
- Voice
|
||||
ha_domain: whisper
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Yale Home
|
||||
description: Instructions on how to integrate your Yale Home devices into Home Assistant
|
||||
description: Connect and control your Yale Home devices using the August integration
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Button
|
||||
@ -9,12 +9,13 @@ ha_category:
|
||||
- Lock
|
||||
- Sensor
|
||||
ha_release: 0.64
|
||||
ha_iot_class: Cloud Push
|
||||
ha_config_flow: true
|
||||
ha_domain: yale_home
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: august
|
||||
ha_supporting_integration: August
|
||||
ha_codeowners:
|
||||
- '@bdraco'
|
||||
ha_domain: august
|
||||
ha_dhcp: true
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
@ -22,9 +23,8 @@ ha_platforms:
|
||||
- diagnostics
|
||||
- lock
|
||||
- sensor
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: august
|
||||
ha_supporting_integration: August
|
||||
ha_iot_class: Cloud Push
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
{% include integrations/supported_brand.md %}
|
||||
|
||||
@ -56,4 +56,4 @@ The integration is tested and verified for the following devices from YoLink:
|
||||
* YS5707 (Dimmer)
|
||||
* YS6801/2 (MultiOutlet)
|
||||
* YS3604 (FlexFob)
|
||||
* YS7106 (PowerFailureAlar)
|
||||
* YS7106 (PowerFailureAlar)
|
||||
|
||||
@ -396,7 +396,7 @@ Tip! It is highly recommended that you read through the two segments under the t
|
||||
|
||||
Most mains-powered devices, e.g., many always-powered wall plugs or light bulbs in your Zigbee network will automatically act as a Zigbee router device (sometimes also referred to as a Zigbee "signal repeater" or "range extender").
|
||||
|
||||
Because Zigbee should use a "[wireless mesh network]"(https://en.wikipedia.org/wiki/Wireless_mesh_network) to be effective, you will need to add Zigbee router devices to increase the number of Zigbee devices that can be used in your Zigbee network, both in the total number of devices that can be added as well as the total range and coverage of the network. Some Zigbee router devices do a much better job at routing and repeating Zigbee signals and messages than some other devices. You should not have a setup where Zigbee router devices (e.g. light bulbs) are often powered-off. Zigbee router devices are meant to be always available.
|
||||
Because Zigbee should use a [wireless mesh network](https://en.wikipedia.org/wiki/Wireless_mesh_network) to be effective, you will need to add Zigbee router devices to increase the number of Zigbee devices that can be used in your Zigbee network, both in the total number of devices that can be added as well as the total range and coverage of the network. Some Zigbee router devices do a much better job at routing and repeating Zigbee signals and messages than some other devices. You should not have a setup where Zigbee router devices (e.g. light bulbs) are often powered-off. Zigbee router devices are meant to be always available.
|
||||
|
||||
All Zigbee coordinator firmware will only allow you to directly connect a certain amount of devices. That limit is set for two reasons; firstly, to not overload the Zigbee coordinator, and secondly, to encourage your Zigbee network to quickly begin to utilize a "[mesh networking](https://en.wikipedia.org/wiki/Mesh_networking)" topology instead of only a "[star network](https://en.wikipedia.org/wiki/Star_network)" topology.
|
||||
|
||||
|
||||
@ -42,6 +42,7 @@ ha_platforms:
|
||||
- update
|
||||
ha_integration_type: hub
|
||||
ha_zeroconf: true
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
The Z-Wave integration allows you to control a Z-Wave network via the [Z-Wave JS](https://zwave-js.github.io/node-zwave-js/#/) driver.
|
||||
@ -73,11 +74,10 @@ Use this My button:
|
||||
{% my config_flow_start badge domain="zwave_js" %}, or follow these steps:
|
||||
|
||||
* Browse to your Home Assistant instance.
|
||||
* In the sidebar, select **{% my config icon %}**.
|
||||
* From the configuration menu, select: **{% my integrations %}**.
|
||||
* On the bottom right, select the
|
||||
* Go to **{% my integrations title="Settings > Devices & Services" %}**.
|
||||
* In the bottom right, select the
|
||||
**{% my config_flow_start icon domain="zwave_js" %}** button.
|
||||
* From the list, search and select **Z-Wave**.
|
||||
* From the list, select **Z-Wave**.
|
||||
* Follow the instructions on screen to complete the setup.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
869
source/_posts/2023-06-07-release-20236.markdown
Normal file
869
source/_posts/2023-06-07-release-20236.markdown
Normal file
@ -0,0 +1,869 @@
|
||||
---
|
||||
layout: post
|
||||
title: "2023.6: Network storage, favorite light colors, new integrations dashboard"
|
||||
description: "Add and use network storage, the integrations dashboard got a revamp, add your favorite colors to your lights, copy & paste support for automations, blazing speed through Python 3.11, and Matter and Z-Wave updates."
|
||||
date: 2023-06-07 00:00:00
|
||||
date_formatted: "June 7, 2023"
|
||||
author: Franck Nijhof
|
||||
author_twitter: frenck
|
||||
comments: true
|
||||
categories:
|
||||
- Release-Notes
|
||||
- Core
|
||||
og_image: /images/blog/2023-06/social.png
|
||||
---
|
||||
|
||||
<a href='/integrations/#version/2023.6'><img src='/images/blog/2023-06/social.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
Home Assistant Core 2023.6! 🎉
|
||||
|
||||
Get ready for a classic, old-fashioned, jam-packed release! 🤯
|
||||
|
||||
I am excited about so many things being shipped in this release that it is
|
||||
hard to pick a favorite 😅 This release has it all.
|
||||
|
||||
Being able to directly use and back up my Home Assistant configuration to my
|
||||
network storage is absolutely incredible! But I also really enjoy the new and
|
||||
clean integrations dashboard and pages.
|
||||
|
||||
The feature that greatly improved the Home Approval Factor in my household
|
||||
is definitely the addition of the new favorite colors in the light dialogs 🎨
|
||||
|
||||
Enjoy the release!
|
||||
|
||||
../Frenck
|
||||
|
||||
<!--more-->
|
||||
|
||||
- [Connect and use your existing network storage](#connect-and-use-your-existing-network-storage)
|
||||
- [Integrations dashboard \& pages](#integrations-dashboard--pages)
|
||||
- [Light entity dialog improvements: favorite colors](#light-entity-dialog-improvements-favorite-colors)
|
||||
- [Added to the entity dialog: last changed](#added-to-the-entity-dialog-last-changed)
|
||||
- [Related information](#related-information)
|
||||
- [Copy 'n paste support in the automation editor](#copy-n-paste-support-in-the-automation-editor)
|
||||
- [Python 3.11 and significant performance upgrades](#python-311-and-significant-performance-upgrades)
|
||||
- [Matter 1.1](#matter-11)
|
||||
- [Z-Wave updates](#z-wave-updates)
|
||||
- [New entities! Date, time, date/time](#new-entities-date-time-datetime)
|
||||
- [Other noteworthy changes](#other-noteworthy-changes)
|
||||
- [New Integrations](#new-integrations)
|
||||
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
|
||||
- [Need help? Join the community!](#need-help-join-the-community)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [Farewell to the following](#farewell-to-the-following)
|
||||
- [All changes](#all-changes)
|
||||
|
||||
Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=C1eLZLtvc_k)
|
||||
7 June 2023, at 12:00 PDT / 21:00 CEST!
|
||||
|
||||
<lite-youtube videoid="C1eLZLtvc_k" videotitle="Home Assistant 2023.6 Release Party"></lite-youtube>
|
||||
|
||||
## Connect and use your existing network storage
|
||||
|
||||
Do you have a network storage in your home? Like a QNAP or Synology NAS?
|
||||
This release adds the ability to add and use that storage with Home Assistant!
|
||||
|
||||
This long and highly requested feature is now available when running the
|
||||
Home Assistant Operating System. In the {% my storage title="**Settings** > **System** > **Storage**" %}
|
||||
menu, you can now find a whole new set of controls to connect to your storage
|
||||
and use it to, for example, use your network share as a media source
|
||||
in Home Assistant.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2023-06/network-storage.png' alt='Screenshot showing two external network storages attached to Home Assistant.'>
|
||||
|
||||
Even better: You can use it as a target for your backups so that when
|
||||
Home Assistant creates a backup for you, it will store it directly on
|
||||
your network storage.
|
||||
|
||||
Multiple network storages are also supported; if you like, you can
|
||||
easily add more.
|
||||
|
||||
## Integrations dashboard & pages
|
||||
|
||||
The integrations dashboard has gotten a major overhaul!
|
||||
|
||||
There have been quite some usability issues with the previous version of the
|
||||
integration dashboard. For example, if you use [ESPHome] with many devices,
|
||||
you are undoubtedly familiar with the annoying scrolling in that little card. Or,
|
||||
big error messages stretching those cards out, messing up the whole page.
|
||||
|
||||
This release brings in a whole new integrations dashboard that addresses many
|
||||
of these issues, aiming to provide a cleaner and more consistent experience.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2023-06/integrations-dashboard.png' alt='Screenshot showing the look and feel of the new integrations dashboard.'>
|
||||
|
||||
Device based integrations, like ESPHome, are combined: no more scrolling.
|
||||
A failing integration no longer stretches the layout or makes the
|
||||
layout "jump" during retries. Custom integrations and integrations relying
|
||||
on the cloud are now more visibly marked.
|
||||
|
||||
Selecting the cog icon on the integration card will bring you to a brand new
|
||||
integrations page, showing all information about the integration:
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2023-06/integration-page.png' alt='Screenshot showing an integration page, in this case, the integration page of ESPHome.'>
|
||||
|
||||
In the above example, the ESPHome integration page shows all devices
|
||||
this integration has. All the information and options, previously squashed into
|
||||
the integration dashboard, are now available here.
|
||||
|
||||
These brand new integration pages are helpful in other places in Home Assistant.
|
||||
For example, the device pages can now link back directly to the integration
|
||||
that provided it.
|
||||
|
||||
[ESPHome]: https://esphome.io
|
||||
|
||||
## Light entity dialog improvements: favorite colors
|
||||
|
||||
Recently we introduced new controls in the light entity dialog, and this release
|
||||
iterates on the design by adding the current brightness, new controls,
|
||||
and adding favorite colors! 🎨
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2023-06/light-dialog-favorite-colors.png' alt='Screenshot showing the improved light entity dialog, with the new favorite colors.'>
|
||||
|
||||
Each light (or light group) has its own set of colors. These colors can
|
||||
be added, changed, removed, and reorganized using drag-and-drop. To enter
|
||||
edit mode, select and hold one of the colors:
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2023-06/edit-favorite-colors.gif' alt='Screen recording demonstrating editing favorite colors.'>
|
||||
|
||||
## Added to the entity dialog: last changed
|
||||
|
||||
By popular request, the information on when an entity was last changed has
|
||||
been added back to the new entity information dialogs.
|
||||
|
||||
Not only that, [@piitaya] added a very nice easter egg! You can click on it
|
||||
to toggle between the relative and absolute format!
|
||||
|
||||
<center><img class="no-shadow" src='/images/blog/2023-06/toggle-last-changed.gif' alt='Screen recording demonstrating how to toggle between relative and absolute time.'></center>
|
||||
|
||||
[@piitaya]: https://github.com/piitaya
|
||||
|
||||
## Related information
|
||||
|
||||
Which automation is using that blueprint? Well, Home Assistant can now tell you
|
||||
that! On the {% my blueprints title="**Settings** > **Automations & Scenes** > **Blueprints**" %}
|
||||
page, select the three dotted menu on any blueprint to discover which
|
||||
automations are using that blueprint.
|
||||
|
||||
Not only that, if you accidentally try to remove a blueprint that is still in use,
|
||||
Home Assistant will stop you from removing it and tell you which automations
|
||||
still rely on it.
|
||||
|
||||
Hold on; there is more related! The related items in the entity information
|
||||
dialog were improved as well. The old list of links is gone, and it now shows
|
||||
a way more modern view of all related items for an entity:
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2023-06/related-information.png' alt='Screenshot of the improved related entity information dialog.'>
|
||||
|
||||
Notice how it nicely links back to the new integration page here too!
|
||||
|
||||
## Copy 'n paste support in the automation editor
|
||||
|
||||
An amazing contribution by [@karwosts] in this release that adds cut, copy
|
||||
& paste capabilities to the automation and script editors!
|
||||
|
||||
You can now copy and paste any trigger, condition, and action into different
|
||||
places of your automation and even paste it into a different automation
|
||||
altogether!
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2023-06/cut-copy-past-automations.gif' alt='Screen recording demonstrating cutting & pasting a condition in the automation editor.'>
|
||||
|
||||
[@karwosts]: https://github.com/karwosts
|
||||
|
||||
## Python 3.11 and significant performance upgrades
|
||||
|
||||
This release ships running on Python 3.11! In case you are wondering, what is
|
||||
that? Well, Python is the language the Core of Home Assistant is written in.
|
||||
|
||||
Why it matters? It is seriously faster! 🚀
|
||||
|
||||
If you run the Home Assistant Operating System or are using the Home Assistant
|
||||
Container installation type: You won't have to do anything as we handle the
|
||||
upgrade to Python 3.11 for you.
|
||||
|
||||
And that is not all in terms of performance. We've also upgraded internal parts,
|
||||
including a newer SQLite version that should be faster. Oh! And, of course,
|
||||
[@bdraco] has been all over the place to optimize a lot (a lot lot).
|
||||
|
||||
This release can be expected to be a lot faster (or less consuming) of resources
|
||||
at runtime.
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
|
||||
## Matter 1.1
|
||||
|
||||
The Matter implementation within Home Assistant is now based on the freshly
|
||||
released 1.1 version of the Matter standard. This brings a ton of stability
|
||||
fixes and improvements, but unfortunately, no new features.
|
||||
|
||||
Thanks to [@Diegorro98], we do now have support for tilt covers! Besides that,
|
||||
this Home Assistant release ships with several generic bugfixes and
|
||||
optimizations; we've managed to squeeze out some additional performance to
|
||||
make state updates for your Matter devices lightning-fast 🚀
|
||||
|
||||
All these stability improvements to both the Matter stack and our
|
||||
implementation did not go unnoticed:
|
||||
|
||||
<lite-youtube videoid="PsNdR-m5pwE" videotitle="This ACTUALLY Works Now!?"></lite-youtube>
|
||||
|
||||
[@Diegorro98]: https://github.com/Diegorro98
|
||||
|
||||
## Z-Wave updates
|
||||
|
||||
There has been quite a bit of progress on Z-Wave in Home Assistant.
|
||||
|
||||
Thanks to [@raman325], the integration reached platinum level 🏆 on our
|
||||
[quality scale]. This means the integration now does things right according
|
||||
to best practices which should mean a better user experience in general.
|
||||
|
||||
Have you ever turned on a Z-Wave light from the Home Assistant UI just to see
|
||||
the toggle going off again after a couple of seconds, then after some more
|
||||
seconds seeing it going back to on? This long-standing issue (that even got the
|
||||
nickname flip/flop) for certain devices, that are slow to respond to their
|
||||
state has finally been addressed.
|
||||
|
||||
For those of you that like to automate everything, you can now automate not
|
||||
only the Z-Wave device state but also the device configuration. We added device
|
||||
configuration parameter entities so that almost every Z-Wave device setting
|
||||
is now available as an entity.
|
||||
|
||||
Not stopping there, we also added entities for device connection statistics,
|
||||
which you can use to, for example, create a notification if a device generates
|
||||
more than a certain amount of dropped messages. If you want to track
|
||||
a misbehaving device, you can enable these sensors to view the history
|
||||
of the connection performance.
|
||||
|
||||
In the background, [@AlCalzone] is working tirelessly on the [Z-Wave JS driver],
|
||||
which is the foundation of our Z-Wave integration. Among other things, some
|
||||
devices are now faster to interview during addition, and more devices
|
||||
can be configured.
|
||||
|
||||
[Z-Wave JS driver]: https://github.com/zwave-js/node-zwave-js/
|
||||
[@raman325]: https://github.com/raman325
|
||||
[quality scale]: /docs/quality_scale/
|
||||
[@AlCalzone]: https://github.com/AlCalzone
|
||||
|
||||
## New entities! Date, time, date/time
|
||||
|
||||
We welcome three new entity types in this release:
|
||||
[`date`](/integrations/date), [`time`](/integrations/time) & [`datetime`](/integrations/datetime).
|
||||
|
||||
These entities allow integrations to provide date, time, or date/time input
|
||||
controls from the UI. They are very similar to the [input datetime](/integrations/input_datetime)
|
||||
helper but are available for use by integrations.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-06/new-date-time-entities.png' alt='Screenshot showing the new date & time entities introduced'></a>
|
||||
How the new time, date, and date/time entities will look like on your dashboards.
|
||||
</p>
|
||||
|
||||
They are so new that no integrations are using them yet, but you can expect
|
||||
to see usage in (custom) integrations of these soon!
|
||||
|
||||
Thanks for creating those [@raman325]!
|
||||
|
||||
## Other noteworthy changes
|
||||
|
||||
There are much more easter bunnies in this release; here are some of the other
|
||||
noteworthy changes this release:
|
||||
|
||||
- When using services in the UI (like in the automation editor), only options
|
||||
and settings available to the selected target devices & entities will be shown.
|
||||
This makes the UI much cleaner! Thanks, [@emontnemery] and [@bramkragten]!
|
||||
- The [Roborock] integration (introduced in the previous release) received much
|
||||
love and now provides a wide range of new entities. Thanks [@Lash-L]!
|
||||
- The [Android TV Remote] integration now provides a media player entity too!
|
||||
Nice, [@Drafteed]!
|
||||
- [KNX] now provides its own panel, allowing you to upload your KNX
|
||||
project file, and offers a group monitor for live bus diagnostics.
|
||||
Information from the project is also used for device triggers.
|
||||
Amazing [@marvin-w] and [@farmio]!
|
||||
- [@bdraco] added the option to disable Webhooks for [ONVIF] in case your
|
||||
camera isn't fully following specifications.
|
||||
- The [variables action] is now also available in the automation and script
|
||||
editors in the UI. Thanks, [@piitaya]
|
||||
- The add-on dashboard now has a search bar. Helpful, [@bramkragten]!
|
||||
- The [Samsung TV] now has a remote entity, allowing you to send remote key
|
||||
presses directly to your TV! Thanks [@peitschie]!
|
||||
- The {% my developer_states title="States in the developer tools" %} now
|
||||
uses the entity ID in the entity ID picker. Thanks, [@bramkragten]!
|
||||
- [@gjohansson-ST] added a service to change a running timer helper, [@frenck]
|
||||
did something similar and added a service to set the value of a counter helper.
|
||||
- The [AccuWeather] integration now provides sensors for the weather condition
|
||||
and solar irradiance values. Thanks, [@bieniu]
|
||||
- You can now update your [QNAP QSW] directly from Home Assistant. Nice [@Noltari]!
|
||||
- The [BMW Connected Drive] now allows you to toggle climate on/off and new
|
||||
entities related to the charging of your car. Thanks, [@rikroe] and [@cpoulsen]!
|
||||
|
||||
[@peitschie]: https://github.com/peitschie
|
||||
[Samsung TV]: /integrations/samsungtv
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@cpoulsen]: https://github.com/cpoulsen
|
||||
[@Drafteed]: https://github.com/Drafteed
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@farmio]: https://github.com/farmio
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[@marvin-w]: https://github.com/marvin-w
|
||||
[@Lash-L]: https://github.com/Lash-L
|
||||
[@Noltari]: https://github.com/@Noltari
|
||||
[@piitaya]: https://github.com/piitaya
|
||||
[@rikroe]: https://github.com/rikroe
|
||||
[AccuWeather]: /integrations/accuweather
|
||||
[Android TV Remote]: /integrations/androidtv_remote
|
||||
[BMW Connected Drive]: /integrations/bmw_connected_drive
|
||||
[KNX]: /integrations/knx
|
||||
[ONVIF]: /integrations/onvif
|
||||
[QNAP QSW]: /integrations/qnap_qsw
|
||||
[Roborock]: /integrations/roborock
|
||||
[variables action]: /docs/scripts/#variables
|
||||
|
||||
## New Integrations
|
||||
|
||||
We welcome the following new integrations in this release:
|
||||
|
||||
- **[Airzone Cloud]**, added by [@Noltari]<br />
|
||||
Climate control for your Aidoo, Easyzone, or Flexa air conditioners.
|
||||
- **[Date]**, **[Time]**, and **[Date/Time]**, added by [@raman325]<br />
|
||||
New entity types that allow integrations to provide date/time controls.
|
||||
- **[Electra Smart]**, added by [@jafar-atili]<br />
|
||||
Control your Electra Air air conditioner from Home Assistant.
|
||||
- **[Google Generative AI Conversation]**, added by [@tronikos]<br />
|
||||
A conversation agent powered by Google Generative AI.
|
||||
- **[JVC Projector]**, added by [@SteveEasley]<br />
|
||||
You can now automate your network controllable JVC Projector.
|
||||
- **[YouTube]**, added by [@joostlek]<br />
|
||||
Add your favorite YouTube channels as sensors.
|
||||
|
||||
This release also has a new virtual integration. Virtual integrations
|
||||
are stubs that are handled by other (existing) integrations to help with
|
||||
findability. This one is new:
|
||||
|
||||
- **[Piper]** provided by [Wyoming], added by [@frenck]
|
||||
- **[Whisper]** provided by [Wyoming], added by [@frenck]
|
||||
- **[Yale Home]** provided by [August], added by [@bdraco]
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@jafar-atili]: https://github.com/jafar-atili
|
||||
[@joostlek]: https://github.com/joostlek
|
||||
[@Noltari]: https://github.com/Noltari
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@SteveEasley]: https://github.com/SteveEasley
|
||||
[@tronikos]: https://github.com/tronikos
|
||||
[Airzone Cloud]: /integrations/airzone_cloud
|
||||
[August]: /integrations/august
|
||||
[Date]: /integrations/date
|
||||
[Date/Time]: /integrations/date_time
|
||||
[Electra Smart]: /integrations/electrasmart
|
||||
[Google Generative AI Conversation]: /integrations/google_generative_ai_conversation
|
||||
[JVC Projector]: /integrations/jvc_projector
|
||||
[Piper]: /integrations/piper
|
||||
[Time]: /integrations/time
|
||||
[Whisper]: /integrations/whisper
|
||||
[Wyoming]: /integrations/wyoming
|
||||
[Yale Home]: /integrations/yale_home
|
||||
[YouTube]: /integrations/youtube
|
||||
|
||||
## Integrations now available to set up from the UI
|
||||
|
||||
The following integrations are now available via the Home Assistant UI:
|
||||
|
||||
- **[Deutscher Wetterdienst (DWD) Weather Warnings]**, done by [@andarotajo]
|
||||
- **[GeoJSON]**, done by [@exxamalte]
|
||||
- **[Last.fm]**, done by [@joostlek]
|
||||
- **[Philips Dynalite]**, done by [@ziv1234]
|
||||
|
||||
[@andarotajo]: https://github.com/andarotajo
|
||||
[@exxamalte]: https://github.com/exxamalte
|
||||
[@joostlek]: https://github.com/joostlek
|
||||
[@ziv1234]: https://github.com/ziv1234
|
||||
[Deutscher Wetterdienst (DWD) Weather Warnings]: /integrations/dwd_weather_warnings
|
||||
[GeoJSON]: /integrations/geo_json_events
|
||||
[Last.fm]: /integrations/lastfm
|
||||
[Philips Dynalite]: /integrations/dynalite
|
||||
|
||||
## Need help? Join the community!
|
||||
|
||||
Home Assistant has a great community of users who are all more than willing
|
||||
to help each other out. So, join us!
|
||||
|
||||
Our very active [Discord chat server](/join-chat) is an excellent place to be
|
||||
at, and don't forget to join our amazing [forums](https://community.home-assistant.io/).
|
||||
|
||||
Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues),
|
||||
to get it fixed! Or, check [our help page](/help) for guidance for more
|
||||
places you can go.
|
||||
|
||||
Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter)
|
||||
to get the latest news about features, things happening in our community and
|
||||
other news about building an Open Home; straight into your inbox.
|
||||
|
||||
## Breaking Changes
|
||||
|
||||
{% details "Python" %}
|
||||
|
||||
All Home Assistant versions, of which the Home Assistant project manages the
|
||||
Python version for you, have been upgraded to Python 3.11. This affects
|
||||
the following installation types:
|
||||
|
||||
- Home Assistant Operating System
|
||||
- Home Assistant Container
|
||||
- Home Assistant Supervised
|
||||
|
||||
This might affect you when using custom integrations, as those must be
|
||||
compatible with Python 3.11.
|
||||
|
||||
Furthermore, as of this release, Python 3.10 is deprecated, and support will
|
||||
be removed in Home Assistant 2023.8. This **only** affects you if you are
|
||||
running Home Assistant Core installation type in your own Python virtual
|
||||
environment. Please update your Python version to Python 3.11.
|
||||
|
||||
If you run Home Assistant OS, Home Assistant Container, or Home Assistant
|
||||
Supervised, we have taken care of this for you; you will be using Python 3.11
|
||||
automatically on upgrade.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "APC UPS Daemon" %}
|
||||
|
||||
`sensor.ups_self_test_interval` sensor now properly splits unit "days" from the
|
||||
raw data. Previously, it would show `7 days` as the sensor state.
|
||||
Now it shows `7` with a unit "Days".
|
||||
|
||||
([@yuxincs] - [#93844]) ([documentation](/integrations/apcupsd))
|
||||
|
||||
[@yuxincs]: https://github.com/yuxincs
|
||||
[#93844]: https://github.com/home-assistant/core/pull/93844
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Counter" %}
|
||||
|
||||
The `counter` entities no longer restore their previous manually set
|
||||
configuration (using the - now deprecated - `counter.configure` service) on
|
||||
Home Assistant startup. Instead, it will now use the configuration as set in
|
||||
the helper configuration in the UI (or as configured YAML, if used).
|
||||
|
||||
This behavior is removed, as it caused configuration issues, as the new
|
||||
configuration was never applied again (but forever restored). This behavior was
|
||||
out of the ordinary for Home Assistant and thus now standardized.
|
||||
|
||||
The value of the counter is still restored and available across Home Assistant
|
||||
restarts.
|
||||
|
||||
([@frenck] - [#93344]) ([documentation](/integrations/counter))
|
||||
|
||||
[@frenck]: https://github.com/frenck
|
||||
[#93344]: https://github.com/home-assistant/core/pull/93344
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Command Line" %}
|
||||
|
||||
The Command Line integration changes its YAML configuration format from
|
||||
an old-style platform configuration to a more modern integration-style
|
||||
configuration format.
|
||||
|
||||
For example, if you have a binary sensor configured previously as:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: command_line
|
||||
command: "cat /proc/sys/net/ipv4/ip_forward"
|
||||
```
|
||||
|
||||
That same binary sensor is now configured under the `command_line` integration
|
||||
configuration as:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
command_line:
|
||||
- binary_sensor:
|
||||
command: "cat /proc/sys/net/ipv4/ip_forward"
|
||||
```
|
||||
|
||||
Note: While this is currently not yet a breaking change, it did raise questions
|
||||
during our beta testing period. Hence we have added this as a breaking change
|
||||
to provide more context.
|
||||
|
||||
([@gjohansson-ST] - [#92824]) ([documentation](/integrations/command_line))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#92824]: https://github.com/home-assistant/core/pull/92824
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "D-Link Wi-Fi Smart Plugs" %}
|
||||
|
||||
The previously deprecated YAML configuration of the D-Link Wi-Fi Smart Plugs
|
||||
integration has been removed.
|
||||
|
||||
D-Link Wi-Fi Smart Plugs are now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@gjohansson-ST] - [#92590]) ([documentation](/integrations/dlink))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#92590]: https://github.com/home-assistant/core/pull/92590
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "EDL21" %}
|
||||
|
||||
The previously deprecated YAML configuration of the EDL21
|
||||
integration has been removed.
|
||||
|
||||
EDL21 is now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@gjohansson-ST] - [#93551]) ([documentation](/integrations/edl21))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#93551]: https://github.com/home-assistant/core/pull/93551
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "EZVIZ" %}
|
||||
|
||||
The binary sensor providing "upgrade available" information has been removed
|
||||
and replaced by a new `update` entity. If you use the binary sensor in your
|
||||
automations, scripts, or dashboards, you will need to adjust them to
|
||||
this change.
|
||||
|
||||
([@RenierM26] - [#85377]) ([documentation](/integrations/ezviz))
|
||||
|
||||
[@RenierM26]: https://github.com/RenierM26
|
||||
[#85377]: https://github.com/home-assistant/core/pull/85377
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Frontier Silicon" %}
|
||||
|
||||
The previously deprecated YAML configuration of the Frontier Silicon
|
||||
integration has been removed.
|
||||
|
||||
Frontier Silicon is now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@gjohansson-ST] - [#93552]) ([documentation](/integrations/frontier_silicon))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#93552]: https://github.com/home-assistant/core/pull/93552
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Google Nest" %}
|
||||
|
||||
The Google Nest YAML configuration has been fully removed. You should ensure you
|
||||
have imported your configuration and credentials into the UI before upgrading.
|
||||
|
||||
Nest Desktop or OOB authentication, which was previously disabled by Google,
|
||||
has now been removed.
|
||||
|
||||
([@allenporter] - [#92311]) ([documentation](/integrations/nest))
|
||||
|
||||
[@allenporter]: https://github.com/allenporter
|
||||
[#92311]: https://github.com/home-assistant/core/pull/92311
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "IBM Watson TTS" %}
|
||||
|
||||
Home Assistant was still using the legacy Python pip package resolver, which
|
||||
has been removed. Due to upstream package conflicts, the IBM Watson TTS
|
||||
integration has been disabled.
|
||||
|
||||
The upstream project providing the libraries used has been notified repeatedly
|
||||
in, at least, the past two years; unfortunately, without response. We had no
|
||||
other choice than to disable this integration.
|
||||
|
||||
([@frenck] - [#92124]) ([documentation](/integrations/watson_tts))
|
||||
|
||||
[@frenck]: https://github.com/frenck
|
||||
[#91492]: https://github.com/home-assistant/core/pull/92124
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "IHC Controller" %}
|
||||
|
||||
The default unit of measurement for manually set up sensors from IHC has been
|
||||
removed. Home Assistant now assumes all sensors with a unit of measurement set
|
||||
are a number. IHC sensors can be text, but because of the default unit of
|
||||
measurement, there is currently no way to get text sensors from IHC working.
|
||||
|
||||
This is a breaking fix because if you currently have temperature sensors
|
||||
without a unit of measurement set, you will have to set this for the sensors.
|
||||
|
||||
([@dingusdk] - [#91096]) ([documentation](/integrations/ihc))
|
||||
|
||||
[@dingusdk]: https://github.com/dingusdk
|
||||
[#93054]: https://github.com/home-assistant/core/pull/93054
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "LG Netcast" %}
|
||||
|
||||
LG Netcast media players no longer have fake (assumed) `playing` or `paused`
|
||||
states, and those are replaced with the `on` state.
|
||||
|
||||
If you used the `playing` or `paused` state in your automations, you will need
|
||||
to update them to match this change.
|
||||
|
||||
([@Drafteed] - [#93543]) ([documentation](/integrations/lg_netcast))
|
||||
|
||||
[@Drafteed]: https://github.com/Drafteed
|
||||
[#93543]: https://github.com/home-assistant/core/pull/93543
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Meteorologisk institutt (Met.no)" %}
|
||||
|
||||
The weather forecast provided by the weather entity has changed. The current
|
||||
day has been added to the forecast. If your automations or scripts rely
|
||||
on the first day to be tomorrow, you need to adjust them.
|
||||
|
||||
([@mmalina] - [#91891]) ([documentation](/integrations/met))
|
||||
|
||||
[@mmalina]: https://github.com/mmalina
|
||||
[#91891]: https://github.com/home-assistant/core/pull/91891
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "MQTT" %}
|
||||
|
||||
MQTT sensor configurations that still use `last_reset_topic` will fail. The
|
||||
support was deprecated in Home Assistant 2021.11 and is now removed. Users
|
||||
should use ` last_reset_value_template` instead.
|
||||
|
||||
([@jbouwh] - [#93792]) ([documentation](/integrations/mqtt))
|
||||
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[#93792]: https://github.com/home-assistant/core/pull/93792
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Nextcloud" %}
|
||||
|
||||
The previously deprecated YAML configuration of the Nextcloud
|
||||
integration has been removed.
|
||||
|
||||
Nextcloud is now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@gjohansson-ST] - [#93550]) ([documentation](/integrations/nextcloud))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#93550]: https://github.com/home-assistant/core/pull/93550
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Obihai" %}
|
||||
|
||||
The previously deprecated YAML configuration of the Obihai
|
||||
integration has been removed.
|
||||
|
||||
Obihai is now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@gjohansson-ST] - [#93549]) ([documentation](/integrations/obihai))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#93549]: https://github.com/home-assistant/core/pull/93549
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Persistent notifications" %}
|
||||
|
||||
Persistent notifications are no longer stored in the state machine. This means
|
||||
that we no longer create an entity for each persistent notification.
|
||||
|
||||
If you used these entities in, for example, automations, scripts, or templates,
|
||||
you won't be able to use these anymore.
|
||||
|
||||
([@bdraco] - [#92828]) ([documentation](/integrations/persistent_notification))
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[#92828]: https://github.com/home-assistant/core/pull/92828
|
||||
|
||||
---
|
||||
|
||||
The `persistent_notification.mark_read` service has been removed.
|
||||
|
||||
([@bdraco] - [#94122]) ([documentation](/integrations/persistent_notification))
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[#94122]: https://github.com/home-assistant/core/pull/94122
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Rain Bird" %}
|
||||
|
||||
The previously deprecated YAML configuration of the Rain Bird
|
||||
integration has been removed.
|
||||
|
||||
Rain Bird is now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@gjohansson-ST] - [#92599]) ([documentation](/integrations/rainbird))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#92599]: https://github.com/home-assistant/core/pull/92599
|
||||
|
||||
---
|
||||
|
||||
The previously deprecated `rainbird.rain_delay` service for Rainbird has been
|
||||
removed. Please update any automation or script depending on this service.
|
||||
|
||||
([@gjohansson-ST] - [#92601]) ([documentation](/integrations/rainbird))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#92601]: https://github.com/home-assistant/core/pull/92601
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Salda Smarty" %}
|
||||
|
||||
Home Assistant was still using the legacy Python pip package resolver, which
|
||||
has been removed. Due to upstream package conflicts, the Salda Smarty
|
||||
integration has been disabled.
|
||||
|
||||
The upstream project providing the libraries used has been notified repeatedly
|
||||
in, at least, the past two years; unfortunately, without response. We had no
|
||||
other choice than to disable this integration.
|
||||
|
||||
([@frenck] - [#92124]) ([documentation](/integrations/smarty))
|
||||
|
||||
[@frenck]: https://github.com/frenck
|
||||
[#91492]: https://github.com/home-assistant/core/pull/92124
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Samsung Smart TV" %}
|
||||
|
||||
The previously deprecated YAML configuration of the Samsung Smart TV
|
||||
integration has been removed.
|
||||
|
||||
Samsung Smart TV is now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@epenet] - [#93392]) ([documentation](/integrations/samsungtv))
|
||||
|
||||
[@epenet]: https://github.com/epenet
|
||||
[#93392]: https://github.com/home-assistant/core/pull/93392
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Total Connect" %}
|
||||
|
||||
The tampered and low battery status zone attributes have been moved into their
|
||||
own dedicated binary sensors. If you use these attributes in your automations,
|
||||
scripts, or dashboards, you will need to update those to reflect this change.
|
||||
|
||||
([@austinmroczek] - [#73152]) ([documentation](/integrations/totalconnect))
|
||||
|
||||
[@austinmroczek]: https://github.com/austinmroczek
|
||||
[#73152]: https://github.com/home-assistant/core/pull/73152
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Universal Devices ISY/IoX" %}
|
||||
|
||||
The previously deprecated sensor entities for Insteon devices' On Level and
|
||||
Ramp Rate, as well as ISY Variable sensors, have been removed. Please use the
|
||||
dedicated `number` and `select` entities instead.
|
||||
|
||||
([@shbatm] - [#92255]) ([documentation](/integrations/isy994))
|
||||
|
||||
[@shbatm]: https://github.com/shbatm
|
||||
[#92255]: https://github.com/home-assistant/core/pull/92255
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Vallox" %}
|
||||
|
||||
The previously deprecated YAML configuration of the Vallox
|
||||
integration has been removed.
|
||||
|
||||
Vallox is now configured via the UI. Any existing YAML
|
||||
configuration has been imported in previous releases and can now be safely
|
||||
removed from your YAML configuration files.
|
||||
|
||||
([@slovdahl] - [#91096]) ([documentation](/integrations/vallox))
|
||||
|
||||
[@slovdahl]: https://github.com/slovdahl
|
||||
[#91096]: https://github.com/home-assistant/core/pull/91096
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Z-Wave" %}
|
||||
|
||||
On/Off properties for the Indicator CC are no longer discovered as entities.
|
||||
|
||||
They were previously discovered as sensor entities which were not useful in
|
||||
cases where you wanted to change these values, and you would need to change
|
||||
the value for all three On/Off properties simultaneously in order for them to
|
||||
work, which wasn't supported with our existing discovery model.
|
||||
|
||||
([@raman325] - [#90248]) ([documentation](/integrations/zwave_js))
|
||||
|
||||
[@raman325]: https://github.com/raman325
|
||||
[#90248]: https://github.com/home-assistant/core/pull/90248
|
||||
|
||||
---
|
||||
|
||||
For devices with the `Entry control` generic device class, the `Door lock mode`
|
||||
config parameter no longer gets created as a `sensor` entity and will instead
|
||||
get created as a `select` entity.
|
||||
|
||||
([@raman325] - [#92223]) ([documentation](/integrations/zwave_js))
|
||||
|
||||
[@raman325]: https://github.com/raman325
|
||||
[#92223]: https://github.com/home-assistant/core/pull/92223
|
||||
|
||||
---
|
||||
|
||||
The Nice IBT4ZWAVE module was previously discovered as a light, but now it is
|
||||
discovered as a cover. The light entity will be permanently unavailable and can
|
||||
be safely deleted.
|
||||
|
||||
([@raman325] - [#93946]) ([documentation](/integrations/zwave_js))
|
||||
|
||||
[@raman325]: https://github.com/raman325
|
||||
[#93946]: https://github.com/home-assistant/core/pull/93946
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
If you are a custom integration developer and want to learn about breaking
|
||||
changes and new features available for your integration: Be sure to follow our
|
||||
[developer blog][devblog]. The following are the most notable for this release:
|
||||
|
||||
- [Recent MQTT changes to improve overall performance](https://developers.home-assistant.io/blog/2023/05/21/retained-mqtt-messages-filtered)
|
||||
- [Statistics WebSocket API changes](https://developers.home-assistant.io/blog/2023/04/30/statistics_impossible_values)
|
||||
|
||||
[devblog]: https://developers.home-assistant.io/blog/
|
||||
|
||||
## Farewell to the following
|
||||
|
||||
The following integrations are also no longer available as of this release:
|
||||
|
||||
- **Goalfeed** has been removed. Their service has been discontinued.
|
||||
([@thecode] - [#94129])
|
||||
|
||||
[@thecode]: https://github.com/thecode
|
||||
[#94129]: https://github.com/home-assistant/core/pull/94129
|
||||
|
||||
## All changes
|
||||
|
||||
Of course, there is a lot more in this release. You can find a list of
|
||||
all changes made here: [Full changelog for Home Assistant Core 2023.6](/changelogs/core-2023.6)
|
||||
1629
source/changelogs/core-2023.6.markdown
Normal file
1629
source/changelogs/core-2023.6.markdown
Normal file
File diff suppressed because it is too large
Load Diff
BIN
source/images/assist/tts_action.png
Normal file
BIN
source/images/assist/tts_action.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
BIN
source/images/assist/tts_enter_text.png
Normal file
BIN
source/images/assist/tts_enter_text.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
source/images/assist/tts_select_media_player.png
Normal file
BIN
source/images/assist/tts_select_media_player.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
BIN
source/images/assist/tts_select_media_source.png
Normal file
BIN
source/images/assist/tts_select_media_source.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
BIN
source/images/assist/tts_select_piper.png
Normal file
BIN
source/images/assist/tts_select_piper.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
source/images/blog/2023-06/cut-copy-past-automations.gif
Normal file
BIN
source/images/blog/2023-06/cut-copy-past-automations.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.6 MiB |
BIN
source/images/blog/2023-06/edit-favorite-colors.gif
Normal file
BIN
source/images/blog/2023-06/edit-favorite-colors.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.0 MiB |
BIN
source/images/blog/2023-06/integration-page.png
Normal file
BIN
source/images/blog/2023-06/integration-page.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 125 KiB |
BIN
source/images/blog/2023-06/integrations-dashboard.png
Normal file
BIN
source/images/blog/2023-06/integrations-dashboard.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 140 KiB |
BIN
source/images/blog/2023-06/light-dialog-favorite-colors.png
Normal file
BIN
source/images/blog/2023-06/light-dialog-favorite-colors.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 92 KiB |
BIN
source/images/blog/2023-06/network-storage.png
Normal file
BIN
source/images/blog/2023-06/network-storage.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 78 KiB |
BIN
source/images/blog/2023-06/new-date-time-entities.png
Normal file
BIN
source/images/blog/2023-06/new-date-time-entities.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.1 KiB |
BIN
source/images/blog/2023-06/related-information.png
Normal file
BIN
source/images/blog/2023-06/related-information.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 69 KiB |
BIN
source/images/blog/2023-06/social.png
Normal file
BIN
source/images/blog/2023-06/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 158 KiB |
BIN
source/images/blog/2023-06/toggle-last-changed.gif
Normal file
BIN
source/images/blog/2023-06/toggle-last-changed.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 357 KiB |
40
source/voice_control/using_tts_in_automation.markdown
Normal file
40
source/voice_control/using_tts_in_automation.markdown
Normal file
@ -0,0 +1,40 @@
|
||||
---
|
||||
title: "Using Piper TTS in automations"
|
||||
---
|
||||
|
||||
This procedure shows you how to create a text-to-speech {% term action %}. For this, we use our local text-to-speech engine, Piper, and the media player {% term service %}. Home Assistant can then speak to you over your media player as part of an {% term automation %}.
|
||||
|
||||
1. Go to **{% my automations title="Settings > Automations & Scenes" %}**, and select **Create automation**.
|
||||
1. Select **Create new automation**, then **Add action**.
|
||||
1. From the drop-down menu, select **Play media** and select the media player you want to use for this automation.
|
||||
|
||||
1. Select **Pick media**, then, select **Text-to-speech**.
|
||||
|
||||
1. To use fully local text-to-speech processing, select **Piper**.
|
||||
|
||||
1. Enter the text you want to hear for this automation.
|
||||
|
||||
1. Your text-to-speech action is now ready to be used in your script or automation.
|
||||
|
||||
1. Save your action.
|
||||
1. If you want, you can edit this service in YAML.
|
||||
|
||||
```yaml
|
||||
service: media_player.play_media
|
||||
target:
|
||||
entity_id: media_player.m5stack_atom_echo_a61920
|
||||
data:
|
||||
media_content_id: media-source://tts/tts.piper?message=Your+coffee+is+ready%21+Enjoy.
|
||||
media_content_type: provider
|
||||
metadata:
|
||||
title: Your coffee is ready! Enjoy.
|
||||
thumbnail: https://brands.home-assistant.io/_/tts/logo.png
|
||||
media_class: app
|
||||
children_media_class: null
|
||||
navigateIds:
|
||||
- {}
|
||||
- media_content_type: app
|
||||
media_content_id: media-source://tts
|
||||
- media_content_type: provider
|
||||
media_content_id: media-source://tts/tts.piper?message=Your+coffee+is+ready%21+Enjoy.
|
||||
```
|
||||
Loading…
x
Reference in New Issue
Block a user