mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-16 13:56:53 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
be9d5e15c2
37
CODEOWNERS
37
CODEOWNERS
@ -15,6 +15,7 @@ source/_integrations/acmeda.markdown @atmurray
|
||||
source/_integrations/acomax.markdown @starkillerOG
|
||||
source/_integrations/adax.markdown @danielhiversen
|
||||
source/_integrations/adguard.markdown @frenck
|
||||
source/_integrations/ads.markdown @mrpasztoradam
|
||||
source/_integrations/advantage_air.markdown @Bre77
|
||||
source/_integrations/aemet.markdown @Noltari
|
||||
source/_integrations/aep_ohio.markdown @tronikos
|
||||
@ -51,6 +52,7 @@ source/_integrations/androidtv.markdown @JeffLIrion @ollo69
|
||||
source/_integrations/androidtv_remote.markdown @tronikos @Drafteed
|
||||
source/_integrations/anova.markdown @Lash-L
|
||||
source/_integrations/anthemav.markdown @hyralex
|
||||
source/_integrations/anthropic.markdown @Shulyaka
|
||||
source/_integrations/anwb_energie.markdown @klaasnicolaas
|
||||
source/_integrations/aosmith.markdown @bdr99
|
||||
source/_integrations/apache_kafka.markdown @bachya
|
||||
@ -62,6 +64,7 @@ source/_integrations/application_credentials.markdown @home-assistant/core
|
||||
source/_integrations/apprise.markdown @caronc
|
||||
source/_integrations/aprilaire.markdown @chamberlain2007
|
||||
source/_integrations/aprs.markdown @PhilRW
|
||||
source/_integrations/aps.markdown @tronikos
|
||||
source/_integrations/apsystems.markdown @mawoka-myblock @SonnenladenGmbH
|
||||
source/_integrations/aquacell.markdown @Jordi1990
|
||||
source/_integrations/aranet.markdown @aschmitz @thecode @anrijs
|
||||
@ -70,6 +73,7 @@ source/_integrations/arris_tg2492lg.markdown @vanbalken
|
||||
source/_integrations/arve.markdown @ikalnyi
|
||||
source/_integrations/aseko_pool_live.markdown @milanmeu
|
||||
source/_integrations/assist_pipeline.markdown @balloob @synesthesiam
|
||||
source/_integrations/assist_satellite.markdown @home-assistant/core @synesthesiam
|
||||
source/_integrations/asuswrt.markdown @kennedyshead @ollo69
|
||||
source/_integrations/atag.markdown @MatsNL
|
||||
source/_integrations/aten_pe.markdown @mtdcr
|
||||
@ -124,12 +128,13 @@ source/_integrations/bryant_evolution.markdown @danielsmyers
|
||||
source/_integrations/bsblan.markdown @liudger
|
||||
source/_integrations/bswitch.markdown @jafar-atili
|
||||
source/_integrations/bt_smarthub.markdown @typhoon2099
|
||||
source/_integrations/bthome.markdown @Ernst79
|
||||
source/_integrations/bthome.markdown @Ernst79 @thecode
|
||||
source/_integrations/bticino.markdown @cgtobi
|
||||
source/_integrations/bubendorff.markdown @cgtobi
|
||||
source/_integrations/buienradar.markdown @mjj4791 @ties @Robbie1221
|
||||
source/_integrations/button.markdown @home-assistant/core
|
||||
source/_integrations/calendar.markdown @home-assistant/core
|
||||
source/_integrations/cambridge_audio.markdown @noahhusby
|
||||
source/_integrations/camera.markdown @home-assistant/core
|
||||
source/_integrations/cast.markdown @emontnemery
|
||||
source/_integrations/ccm15.markdown @ocalvo
|
||||
@ -168,6 +173,7 @@ 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/deako.markdown @sebirdman @balake @deakolights
|
||||
source/_integrations/debugpy.markdown @frenck
|
||||
source/_integrations/deconz.markdown @Kane610
|
||||
source/_integrations/default_config.markdown @home-assistant/core
|
||||
@ -201,8 +207,9 @@ source/_integrations/dormakaba_dkey.markdown @emontnemery
|
||||
source/_integrations/downloader.markdown @erwindouna
|
||||
source/_integrations/dremel_3d_printer.markdown @tkdrob
|
||||
source/_integrations/drop_connect.markdown @ChandlerSystems @pfrazer
|
||||
source/_integrations/dsmr.markdown @Robbie1221 @frenck
|
||||
source/_integrations/dsmr.markdown @Robbie1221
|
||||
source/_integrations/dsmr_reader.markdown @sorted-bits @glodenox @erwindouna
|
||||
source/_integrations/duke_energy.markdown @hunterjm
|
||||
source/_integrations/duotecno.markdown @cereal2nd
|
||||
source/_integrations/duquesne_light.markdown @tronikos
|
||||
source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @andarotajo
|
||||
@ -217,6 +224,7 @@ source/_integrations/efergy.markdown @tkdrob
|
||||
source/_integrations/egardia.markdown @jeroenterheerdt
|
||||
source/_integrations/electrasmart.markdown @jafar-atili
|
||||
source/_integrations/electric_kiwi.markdown @mikey0000
|
||||
source/_integrations/elevenlabs.markdown @sorgfresser
|
||||
source/_integrations/elgato.markdown @frenck
|
||||
source/_integrations/elkm1.markdown @gwww @bdraco
|
||||
source/_integrations/elmax.markdown @albertogeniola
|
||||
@ -287,6 +295,7 @@ source/_integrations/fronius.markdown @farmio
|
||||
source/_integrations/frontend.markdown @home-assistant/frontend
|
||||
source/_integrations/frontier_silicon.markdown @wlcrs
|
||||
source/_integrations/fujitsu_anywair.markdown @Bre77
|
||||
source/_integrations/fujitsu_fglair.markdown @crevetor
|
||||
source/_integrations/fully_kiosk.markdown @cgarwood
|
||||
source/_integrations/fyta.markdown @dontinelli
|
||||
source/_integrations/garages_amsterdam.markdown @klaasnicolaas
|
||||
@ -311,9 +320,10 @@ source/_integrations/goodwe.markdown @mletenay @starkillerOG
|
||||
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_cloud.markdown @lufton @tronikos
|
||||
source/_integrations/google_generative_ai_conversation.markdown @tronikos
|
||||
source/_integrations/google_mail.markdown @tkdrob
|
||||
source/_integrations/google_photos.markdown @allenporter
|
||||
source/_integrations/google_sheets.markdown @tkdrob
|
||||
source/_integrations/google_tasks.markdown @allenporter
|
||||
source/_integrations/google_travel_time.markdown @eifinger
|
||||
@ -358,6 +368,7 @@ source/_integrations/homematic.markdown @pvizeli
|
||||
source/_integrations/homematicip_cloud.markdown @hahn-th
|
||||
source/_integrations/homewizard.markdown @DCSBL
|
||||
source/_integrations/honeywell.markdown @rdfurman @mkmer
|
||||
source/_integrations/html5.markdown @alexyao2015
|
||||
source/_integrations/http.markdown @home-assistant/core
|
||||
source/_integrations/huawei_lte.markdown @scop @fphammerle
|
||||
source/_integrations/hue.markdown @balloob @marcelveldt
|
||||
@ -400,13 +411,14 @@ source/_integrations/intellifire.markdown @jeeftor
|
||||
source/_integrations/intesishome.markdown @jnimmo
|
||||
source/_integrations/ios.markdown @robbiet480
|
||||
source/_integrations/iotawatt.markdown @gtdiehl @jyavenard
|
||||
source/_integrations/iotty.markdown @pburgio
|
||||
source/_integrations/iotty.markdown @pburgio @shapournemati-iotty
|
||||
source/_integrations/iperf3.markdown @rohankapoorcom
|
||||
source/_integrations/ipma.markdown @dgomes
|
||||
source/_integrations/iqvia.markdown @bachya
|
||||
source/_integrations/irish_rail_transport.markdown @ttroy50
|
||||
source/_integrations/iron_os.markdown @tr4nt0r
|
||||
source/_integrations/isal.markdown @bdraco
|
||||
source/_integrations/iskra.markdown @iskramis
|
||||
source/_integrations/islamic_prayer_times.markdown @engrbm87 @cpfair
|
||||
source/_integrations/ismartwindow.markdown @starkillerOG
|
||||
source/_integrations/israel_rail.markdown @shaiu
|
||||
@ -477,7 +489,7 @@ source/_integrations/luci.markdown @mzdrale
|
||||
source/_integrations/luftdaten.markdown @fabaff @frenck
|
||||
source/_integrations/lupusec.markdown @majuss @suaveolent
|
||||
source/_integrations/lutron.markdown @cdheiser @wilburCForce
|
||||
source/_integrations/lutron_caseta.markdown @swails @bdraco @danaues @eclair4151
|
||||
source/_integrations/lutron_caseta.markdown @swails @danaues @eclair4151
|
||||
source/_integrations/luxaflex.markdown @bdraco @kingy444 @trullock
|
||||
source/_integrations/lyric.markdown @timmo001
|
||||
source/_integrations/madeco.markdown @starkillerOG
|
||||
@ -517,6 +529,7 @@ source/_integrations/mobile_app.markdown @home-assistant/core
|
||||
source/_integrations/modem_callerid.markdown @tkdrob
|
||||
source/_integrations/modern_forms.markdown @wonderslug
|
||||
source/_integrations/moehlenhoff_alpha2.markdown @j-a-n
|
||||
source/_integrations/monarch_money.markdown @jeeftor
|
||||
source/_integrations/monessen.markdown @jeeftor
|
||||
source/_integrations/monoprice.markdown @etsinko @OnFreund
|
||||
source/_integrations/monzo.markdown @jakemartin-icl
|
||||
@ -551,6 +564,7 @@ source/_integrations/nextcloud.markdown @mib1185
|
||||
source/_integrations/nextdns.markdown @bieniu
|
||||
source/_integrations/nfandroidtv.markdown @tkdrob
|
||||
source/_integrations/nibe_heatpump.markdown @elupus
|
||||
source/_integrations/nice_go.markdown @IceBotYT
|
||||
source/_integrations/nightscout.markdown @marciogranzotto
|
||||
source/_integrations/nilu.markdown @hfurubotten
|
||||
source/_integrations/nina.markdown @DeerMaximum
|
||||
@ -570,6 +584,7 @@ source/_integrations/number.markdown @home-assistant/core @Shulyaka
|
||||
source/_integrations/nut.markdown @bdraco @ollo69 @pestevez
|
||||
source/_integrations/nutrichef.markdown @bdraco
|
||||
source/_integrations/nws.markdown @MatthewFlamm @kamiyo
|
||||
source/_integrations/nyt_games.markdown @joostlek
|
||||
source/_integrations/nzbget.markdown @chriscla
|
||||
source/_integrations/obihai.markdown @dshokouhi @ejpenney
|
||||
source/_integrations/octoprint.markdown @rfleming71
|
||||
@ -615,7 +630,6 @@ source/_integrations/pge.markdown @tronikos
|
||||
source/_integrations/philips_js.markdown @elupus
|
||||
source/_integrations/pi_hole.markdown @shenxn
|
||||
source/_integrations/picnic.markdown @corneyl
|
||||
source/_integrations/pilight.markdown @trekky12
|
||||
source/_integrations/pinecil.markdown @tr4nt0r
|
||||
source/_integrations/ping.markdown @jpbede
|
||||
source/_integrations/piper.markdown @balloob @synesthesiam
|
||||
@ -726,6 +740,7 @@ source/_integrations/sensor.markdown @home-assistant/core
|
||||
source/_integrations/sensorblue.markdown @bdraco
|
||||
source/_integrations/sensorpro.markdown @bdraco
|
||||
source/_integrations/sensorpush.markdown @bdraco
|
||||
source/_integrations/sensoterra.markdown @markruys
|
||||
source/_integrations/sentry.markdown @dcramer @frenck
|
||||
source/_integrations/senz.markdown @milanmeu
|
||||
source/_integrations/serial.markdown @fabaff
|
||||
@ -762,6 +777,7 @@ source/_integrations/smarther.markdown @cgtobi
|
||||
source/_integrations/smarttub.markdown @mdz
|
||||
source/_integrations/smarty.markdown @z0mbieprocess
|
||||
source/_integrations/smhi.markdown @gjohansson-ST
|
||||
source/_integrations/smlight.markdown @tl-sl
|
||||
source/_integrations/sms.markdown @ocalvo
|
||||
source/_integrations/smud.markdown @tronikos
|
||||
source/_integrations/snapcast.markdown @luar123
|
||||
@ -809,8 +825,8 @@ source/_integrations/switch.template.markdown @home-assistant/core
|
||||
source/_integrations/switch_as_x.markdown @home-assistant/core
|
||||
source/_integrations/switchbee.markdown @jafar-atili
|
||||
source/_integrations/switchbot.markdown @danielhiversen @RenierM26 @murtas @Eloston @dsypniewski
|
||||
source/_integrations/switchbot_cloud.markdown @SeraphicRav @laurence-presland
|
||||
source/_integrations/switcher_kis.markdown @thecode
|
||||
source/_integrations/switchbot_cloud.markdown @SeraphicRav @laurence-presland @Gigatrappeur
|
||||
source/_integrations/switcher_kis.markdown @thecode @YogevBokobza
|
||||
source/_integrations/switchmate.markdown @danielhiversen @qiz-li
|
||||
source/_integrations/symfonisk.markdown @jjlawren @peterager
|
||||
source/_integrations/syncthing.markdown @zhulik
|
||||
@ -854,6 +870,7 @@ source/_integrations/todoist.markdown @boralyl
|
||||
source/_integrations/tolo.markdown @MatthiasLohr
|
||||
source/_integrations/tomorrowio.markdown @raman325 @lymanepp
|
||||
source/_integrations/totalconnect.markdown @austinmroczek
|
||||
source/_integrations/touchline_sl.markdown @jnsgruk
|
||||
source/_integrations/tplink.markdown @rytilahti @bdraco @sdb9696
|
||||
source/_integrations/tplink_omada.markdown @MarkGodwin
|
||||
source/_integrations/tplink_tapo.markdown @rytilahti @bdraco @sdb9696
|
||||
@ -866,6 +883,7 @@ source/_integrations/trafikverket_train.markdown @gjohansson-ST
|
||||
source/_integrations/trafikverket_weatherstation.markdown @gjohansson-ST
|
||||
source/_integrations/transmission.markdown @engrbm87 @JPHutchins
|
||||
source/_integrations/trend.markdown @jpbede
|
||||
source/_integrations/triggercmd.markdown @rvmey
|
||||
source/_integrations/tts.markdown @home-assistant/core
|
||||
source/_integrations/tuya.markdown @Tuya @zlinoliver @frenck
|
||||
source/_integrations/twentemilieu.markdown @frenck
|
||||
@ -927,6 +945,7 @@ source/_integrations/webhook.markdown @home-assistant/core
|
||||
source/_integrations/webmin.markdown @autinerd
|
||||
source/_integrations/webostv.markdown @thecode
|
||||
source/_integrations/websocket_api.markdown @home-assistant/core
|
||||
source/_integrations/weheat.markdown @jesperraemaekers
|
||||
source/_integrations/wemo.markdown @esev
|
||||
source/_integrations/whirlpool.markdown @abmantis @mkmer
|
||||
source/_integrations/whisper.markdown @balloob @synesthesiam
|
||||
@ -937,6 +956,7 @@ source/_integrations/wirelesstag.markdown @sergeymaysak
|
||||
source/_integrations/withings.markdown @joostlek
|
||||
source/_integrations/wiz.markdown @sbidy
|
||||
source/_integrations/wled.markdown @frenck
|
||||
source/_integrations/wmspro.markdown @mback2k
|
||||
source/_integrations/wolflink.markdown @adamkrol93 @mtielen
|
||||
source/_integrations/workday.markdown @fabaff @gjohansson-ST
|
||||
source/_integrations/worldclock.markdown @fabaff
|
||||
@ -948,6 +968,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.markdown @bdraco
|
||||
source/_integrations/yale_home.markdown @bdraco
|
||||
source/_integrations/yale_smart_alarm.markdown @gjohansson-ST
|
||||
source/_integrations/yalexs_ble.markdown @bdraco
|
||||
|
||||
2
Gemfile
2
Gemfile
@ -11,7 +11,7 @@ group :development do
|
||||
# > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
|
||||
gem 'sassc', '2.1.0'
|
||||
gem 'rubocop', '1.66.1'
|
||||
gem 'ruby-lsp', '0.18.4'
|
||||
gem 'ruby-lsp', '0.19.0'
|
||||
gem 'rackup', '2.1.0'
|
||||
end
|
||||
|
||||
|
||||
17
Gemfile.lock
17
Gemfile.lock
@ -91,7 +91,7 @@ GEM
|
||||
racc
|
||||
pathutil (0.16.2)
|
||||
forwardable-extended (~> 2.6)
|
||||
prism (1.0.0)
|
||||
prism (1.1.0)
|
||||
public_suffix (6.0.1)
|
||||
racc (1.8.1)
|
||||
rack (3.1.7)
|
||||
@ -108,7 +108,7 @@ GEM
|
||||
rb-fsevent (0.11.2)
|
||||
rb-inotify (0.11.1)
|
||||
ffi (~> 1.0)
|
||||
rbs (3.6.0)
|
||||
rbs (3.6.1)
|
||||
logger
|
||||
regexp_parser (2.9.2)
|
||||
rexml (3.3.8)
|
||||
@ -125,19 +125,18 @@ GEM
|
||||
unicode-display_width (>= 2.4.0, < 3.0)
|
||||
rubocop-ast (1.32.3)
|
||||
parser (>= 3.3.1.0)
|
||||
ruby-lsp (0.18.4)
|
||||
ruby-lsp (0.19.0)
|
||||
language_server-protocol (~> 3.17.0)
|
||||
prism (~> 1.0)
|
||||
prism (>= 1.1, < 2.0)
|
||||
rbs (>= 3, < 4)
|
||||
sorbet-runtime (>= 0.5.10782)
|
||||
ruby-progressbar (1.13.0)
|
||||
ruby2_keywords (0.0.5)
|
||||
safe_yaml (1.0.5)
|
||||
sass (3.4.25)
|
||||
sass-embedded (1.79.4-arm64-darwin)
|
||||
google-protobuf (~> 4.27)
|
||||
sass-embedded (1.79.4-x86_64-linux-gnu)
|
||||
sass-embedded (1.79.4)
|
||||
google-protobuf (~> 4.27)
|
||||
rake (>= 13)
|
||||
sass-globbing (1.1.5)
|
||||
sass (>= 3.1)
|
||||
sassc (2.1.0)
|
||||
@ -150,7 +149,7 @@ GEM
|
||||
rack-protection (= 4.0.0)
|
||||
rack-session (>= 2.0.0, < 3)
|
||||
tilt (~> 2.0)
|
||||
sorbet-runtime (0.5.11589)
|
||||
sorbet-runtime (0.5.11595)
|
||||
stringex (2.8.6)
|
||||
terminal-table (3.0.2)
|
||||
unicode-display_width (>= 1.1.1, < 3)
|
||||
@ -177,7 +176,7 @@ DEPENDENCIES
|
||||
rackup (= 2.1.0)
|
||||
rake (= 13.2.1)
|
||||
rubocop (= 1.66.1)
|
||||
ruby-lsp (= 0.18.4)
|
||||
ruby-lsp (= 0.19.0)
|
||||
sass-globbing (= 1.1.5)
|
||||
sassc (= 2.1.0)
|
||||
sinatra (= 4.0.0)
|
||||
|
||||
@ -107,9 +107,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 2024
|
||||
current_minor_version: 9
|
||||
current_patch_version: 3
|
||||
date_released: 2024-09-24
|
||||
current_minor_version: 10
|
||||
current_patch_version: 1
|
||||
date_released: 2024-10-04
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -26,7 +26,7 @@ badges:
|
||||
entity_id: sensor.living_room_sensor_temperature
|
||||
color: red
|
||||
- type: entity
|
||||
entity_id: sensor.living_room_sensor_humidity
|
||||
entity: sensor.living_room_sensor_humidity
|
||||
color: deep-purple
|
||||
```
|
||||
|
||||
|
||||
@ -37,8 +37,10 @@ It is not possible to migrate dashboards into sections view.
|
||||
1. If you have multiple dashboards, in the left sidebar, select the dashboard to which you want to add the sections view.
|
||||
2. Follow the steps on [adding a new view](/dashboards/views/#adding-a-view-to-a-dashboard).
|
||||
- Under **View type**, select **Sections (experimental)**.
|
||||
3. Select the maximum number of columns you want to see in the new sections view.
|
||||
4. When you are done, select **Save**.
|
||||
3. Under **Max number of sections wide**, select the maximum number of columns you want to see in the new sections view.
|
||||
4. Under **Dense section placement**, select if you want to allow the cards to be arranged automatically in order to fill gaps between cards.
|
||||
- This will remove some gaps, but it also means you have less control over the order of the cards.
|
||||
5. When you are done, select **Save**.
|
||||
- You are now presented with a new, empty view.
|
||||
- If you chose a background image, the page is filled with that image.
|
||||
|
||||
@ -62,8 +64,6 @@ Once you have created a sections view, you can populate it with sections and car
|
||||
- If you define multiple conditions, the section is only shown when all conditions are met.
|
||||
- If you did not define any conditions, the section is always shown, to all users.
|
||||
|
||||
|
||||
|
||||
## Deleting a section
|
||||
|
||||
1. To delete a section, go to the dashboard and in the top right corner, select the edit {% icon "mdi:edit" %} button.
|
||||
|
||||
@ -158,6 +158,8 @@
|
||||
- term: Custom integration
|
||||
definition: >-
|
||||
A custom integration is an integration that has been created by someone from the Home Assistant community and has been published for others to use at their own risk. Custom integrations are not supported by the Home Assistant project. They are not reviewed or tested by the Home Assistant development team and thus may negatively impact the stability of your Home Assistant instance. An example of a custom integration is the [Spook](https://spook.boo/) integration.
|
||||
aliases:
|
||||
- custom integrations
|
||||
- term: Customize
|
||||
definition: >-
|
||||
Customization allows you to overwrite the default parameters of your devices
|
||||
@ -582,6 +584,10 @@
|
||||
Variables are used to store values in memory that can be processed for
|
||||
example, in a script.
|
||||
link: /docs/scripts/#variables
|
||||
- term: YAML
|
||||
definition: >-
|
||||
YAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the `configuration.yaml` or `automations.yaml` files.
|
||||
link: /docs/configuration/yaml/
|
||||
- term: Zone
|
||||
definition: >-
|
||||
Zones allow you to specify certain regions on a map. They enable zone presence-detection and can be used in automations. For example, to start the vacuum after you left home or start the heating at home when you leave the office.
|
||||
|
||||
@ -769,7 +769,7 @@ automation:
|
||||
entity_id: sensor.phone_next_alarm
|
||||
offset: -00:05:00
|
||||
actions:
|
||||
- service: light.turn_on
|
||||
- action: light.turn_on
|
||||
target:
|
||||
entity_id: light.bedroom
|
||||
```
|
||||
|
||||
@ -83,7 +83,7 @@ Blueprints created by the community may go through multiple revisions. Sometimes
|
||||
the community provides feedback, new functionality is added.
|
||||
|
||||
If you do not want to [re-import the blueprint](/docs/automation/using_blueprints/#re-importing-a-blueprint) for some reason, you can manually edit
|
||||
its YAML content to keep it up to date:
|
||||
its {% term YAML %} content to keep it up to date:
|
||||
|
||||
1. Navigate to the blueprints directory (`blueprints/automation/`).
|
||||
The location of this directory depends on the installation method. It's
|
||||
@ -91,7 +91,7 @@ its YAML content to keep it up to date:
|
||||
2. Next, you must find the blueprint to update. The path name of a blueprint consists of:
|
||||
- The username of the user that created it. The name depends on the source of the blueprint:
|
||||
the forum, or GitHub.
|
||||
- The name of the YAML file. For the forum it's the title of the topic in the URL, for GitHub
|
||||
- The name of the {% term YAML %} file. For the forum it's the title of the topic in the URL, for GitHub
|
||||
it's the name of the YAML file.
|
||||
3. Open the YAML file with your editor and update its contents.
|
||||
4. Reload the automations for the changes to take effect.
|
||||
|
||||
@ -3,11 +3,11 @@ title: "Automation YAML"
|
||||
description: "How to use the automation integration with YAML."
|
||||
---
|
||||
|
||||
Automations are created in Home Assistant via the UI, but are stored in a YAML format. If you want to edit the YAML of an {% term automation %}, select the automation, click on the menu button in the top right then on **Edit in YAML**.
|
||||
Automations are created in Home Assistant via the UI, but are stored in a {% term YAML %} format. If you want to edit the {% term YAML %} of an {% term automation %}, select the automation, click on the menu button in the top right then on **Edit in YAML**.
|
||||
|
||||
The UI will write your automations to `automations.yaml`. This file is managed by the UI and should not be edited manually.
|
||||
|
||||
It is also possible to write your automations directly inside {% term "`configuration.yaml`" %} or other YAML files. You can do this by adding a labeled `automation` block to your `configuration.yaml`:
|
||||
It is also possible to write your automations directly inside {% term "`configuration.yaml`" %} or other {% term YAML %} files. You can do this by adding a labeled `automation` block to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# The configuration required for the UI to work
|
||||
@ -125,10 +125,9 @@ actions:
|
||||
<img src='/images/integrations/script/script_modes.jpg'>
|
||||
</p>
|
||||
|
||||
|
||||
## YAML example
|
||||
|
||||
Example of a YAML based automation that you can add to {% term "`configuration.yaml`" %}.
|
||||
Example of a {% term YAML %} based automation that you can add to {% term "`configuration.yaml`" %}.
|
||||
|
||||
{% raw %}
|
||||
|
||||
@ -157,7 +156,7 @@ automation my_lights:
|
||||
after: "16:00:00"
|
||||
before: "23:00:00"
|
||||
actions:
|
||||
# With a single service entry, we don't need a '-' before service - though you can if you want to
|
||||
# With a single action entry, we don't need a '-' before action - though you can if you want to
|
||||
- action: homeassistant.turn_on
|
||||
target:
|
||||
entity_id: group.living_room
|
||||
@ -207,7 +206,7 @@ automation my_lights:
|
||||
|
||||
## Extra options
|
||||
|
||||
When writing automations directly in YAML, you will have access to advanced options that are not available in the user interface.
|
||||
When writing automations directly in {% term YAML %}, you will have access to advanced options that are not available in the user interface.
|
||||
|
||||
### Automation initial state
|
||||
|
||||
@ -223,7 +222,7 @@ automation:
|
||||
|
||||
### Number of debug traces stored
|
||||
|
||||
When using YAML you can configure the number of debugging traces stored for an automation. This is controlled with the `stored_traces` option under `trace`. Set `stored_traces` to the number of traces you wish to store for the particular automation. If not specified the default value of 5 will be used.
|
||||
When using {% term YAML %} you can configure the number of debugging traces stored for an automation. This is controlled with the `stored_traces` option under `trace`. Set `stored_traces` to the number of traces you wish to store for the particular automation. If not specified the default value of 5 will be used.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
@ -263,7 +262,7 @@ If you want to migrate your manual automations to use the editor, you'll have to
|
||||
|
||||
### Deleting automations
|
||||
|
||||
When automations remain visible in the Home Assistant dashboard, even after having deleted in the YAML file, you have to delete them in the UI.
|
||||
When automations remain visible in the Home Assistant dashboard, even after having deleted in the {% term YAML %} file, you have to delete them in the UI.
|
||||
|
||||
To delete them completely, go to UI {% my entities title="**Settings** > **Devices & services** > **Entities**" %} and find the automation in the search field or by scrolling down.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ homeassistant:
|
||||
|
||||
The package configuration can include: `switch`, `light`, `automation`, `groups`, or most other Home Assistant integrations including hardware platforms.
|
||||
|
||||
It can be specified inline or in a separate YAML file using `!include`.
|
||||
It can be specified inline or in a separate {% term YAML %} file using `!include`.
|
||||
|
||||
Inline example, main {% term "`configuration.yaml`" %}:
|
||||
|
||||
@ -74,7 +74,7 @@ Integrations inside packages can only specify platform entries using configurati
|
||||
|
||||
## Create a packages folder
|
||||
|
||||
One way to organize packages is to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory, you can store any number of packages in a YAML file. This entry in your {% term "`configuration.yaml`" %} will load all YAML-files in this _packages_ folder and its subfolders:
|
||||
One way to organize packages is to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory, you can store any number of packages in a {% term YAML %} file. This entry in your {% term "`configuration.yaml`" %} will load all {% term YAML %}-files in this _packages_ folder and its subfolders:
|
||||
|
||||
```yaml
|
||||
homeassistant:
|
||||
|
||||
@ -12,7 +12,7 @@ related:
|
||||
|
||||
The {% term "`configuration.yaml`" %} file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration.
|
||||
|
||||
By using `!secret` you can remove any private information from your configuration files. This separation can also help you to keep easier track of your passwords and API keys, as they are all stored at one place and no longer spread across the {% term "`configuration.yaml`" %} file or even multiple YAML files if you [split up your configuration](/docs/configuration/splitting_configuration/).
|
||||
By using `!secret` you can remove any private information from your configuration files. This separation can also help you to keep easier track of your passwords and API keys, as they are all stored at one place and no longer spread across the {% term "`configuration.yaml`" %} file or even multiple {% term YAML %} files if you [split up your configuration](/docs/configuration/splitting_configuration/).
|
||||
|
||||
## Using `secrets.yaml`
|
||||
|
||||
@ -48,7 +48,7 @@ rest_password: "YOUR_PASSWORD"
|
||||
|
||||
When you start splitting your configuration into multiple files, you might end up with configuration in sub folders. Secrets will be resolved in this order:
|
||||
|
||||
- A `secrets.yaml` located in the same folder as the YAML file referencing the secret,
|
||||
- A `secrets.yaml` located in the same folder as the {% term YAML %} file referencing the secret,
|
||||
- next, parent folders will be searched for a `secrets.yaml` file with the secret, stopping at the folder with the main {% term "`configuration.yaml`" %}.
|
||||
|
||||
To see where secrets are being loaded from, you can either add an option to your `secrets.yaml` file or use the `check_config` script. The latter is only available for {% term "Home Assistant Core" %} installations given it's available through [`hass`](/docs/tools/hass/).
|
||||
|
||||
@ -30,8 +30,8 @@ One of the most common problems with Home Assistant is an invalid {% term "`conf
|
||||
- [Supervised](/common-tasks/supervised/#configuration-check)
|
||||
|
||||
- The configuration files, including {% term "`configuration.yaml`" %} must be UTF-8 encoded. If you see error like `'utf-8' codec can't decode byte`, edit the offending configuration and re-save it as UTF-8.
|
||||
- You can verify your configuration's YAML structure using [this online YAML parser](https://yaml-online-parser.appspot.com/) or [YAML Validator](https://codebeautify.org/yaml-validator/).
|
||||
- To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltproject.io/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).
|
||||
- You can verify your configuration's {% term YAML %} structure using [this online YAML parser](https://yaml-online-parser.appspot.com/) or [YAML Validator](https://codebeautify.org/yaml-validator/).
|
||||
- To learn more about the quirks of {% term YAML %}, read [YAML IDIOSYNCRASIES](https://docs.saltproject.io/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).
|
||||
|
||||
`configuration.yaml` does not allow multiple sections to have the same name. If you want to load multiple platforms for one integration, you can append a number or string to the name or nest them:
|
||||
|
||||
@ -100,7 +100,7 @@ The only characters valid in entity names are:
|
||||
- Numbers
|
||||
- Underscores
|
||||
|
||||
The entity name must not start or end with an underscore. If you create an entity with other characters from the UI, Home Assistant validates the name. If you change the name directly in the YAML file, then Home Assistant may not generate an error for that entity. However, attempts to use that entity will generate errors (or possibly fail silently).
|
||||
The entity name must not start or end with an underscore. If you create an entity with other characters from the UI, Home Assistant validates the name. If you change the name directly in the {% term YAML %} file, then Home Assistant may not generate an error for that entity. However, attempts to use that entity will generate errors (or possibly fail silently).
|
||||
|
||||
For instructions on how to change an entity name, refer to the section on [customizing entities](/docs/configuration/customizing-devices/).
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ scene:
|
||||
|
||||
## How to configure your scene
|
||||
|
||||
In the scene you define in your YAML files, please ensure you use
|
||||
In the scene you define in your {% term YAML %} files, please ensure you use
|
||||
all required parameters as listed below.
|
||||
|
||||
{% configuration %}
|
||||
|
||||
@ -78,5 +78,5 @@ For example:
|
||||
```
|
||||
|
||||
{% note %}
|
||||
Any comments in the YAML file will be lost and templates will be reformatted when you update a scene via the editor.
|
||||
Any comments in the {% term YAML %} file will be lost and templates will be reformatted when you update a scene via the editor.
|
||||
{% endnote %}
|
||||
|
||||
@ -30,7 +30,7 @@ Recovery mode loads a minimum set of integrations to allow troubleshooting the c
|
||||
|
||||
### Resolution
|
||||
|
||||
You need to identify the issue in the configuration files and fix it there. The issue could be caused by something as simple as an invalid YAML file.
|
||||
You need to identify the issue in the configuration files and fix it there. The issue could be caused by something as simple as an invalid {% term YAML %} file.
|
||||
|
||||
- If you are running {% term "Home Assistant Operating System" %}, you can install an add-on such as Studio Code Server to edit the configuration file if needed.
|
||||
- If you are still logged in, you can [edit your configuration](/docs/configuration/#editing-configurationyaml).
|
||||
|
||||
@ -9,12 +9,12 @@ After changing configuration or automation files, check if the configuration is
|
||||
1. Go to {% my profile title="your user profile" %} and enable **Advanced Mode**.
|
||||
2. Go to {% my server_controls title="**Developer tools** > **YAML**" %} and in the **Configuration validation** section, select the **Check configuration** button.
|
||||
- This is to make sure there are no syntax errors before restarting Home Assistant.
|
||||
- It checks for valid YAML and valid config structures.
|
||||
- It checks for valid {% term YAML %} and valid config structures.
|
||||
3. If you need to do a more comprehensive configuration check, [run the check from the CLI](#to-run-a-configuration-check-from-the-cli).
|
||||
|
||||
### Running a configuration check from the CLI
|
||||
|
||||
Use the following command to check if the configuration is valid. The command line configuration check validates the YAML files and checks for valid config structures, as well as some other elements.
|
||||
Use the following command to check if the configuration is valid. The command line configuration check validates the {% term YAML %} files and checks for valid config structures, as well as some other elements.
|
||||
|
||||
```bash
|
||||
ha core check
|
||||
|
||||
@ -112,7 +112,7 @@ In order to use Zigbee or other integrations that require access to devices, you
|
||||
|
||||
The Home Assistant Container is using an alternative memory allocation library [jemalloc](http://jemalloc.net/) for better memory management and Python runtime speedup.
|
||||
|
||||
As jemalloc can cause issues on certain hardware, it can be disabled by passing the environment variable `DISABLE_JEMALLOC` with any value, for example:
|
||||
As the jemalloc configuration used can cause issues on certain hardware featuring a page size larger than 4K (like some specific ARM64-based SoCs), it can be disabled by passing the environment variable `DISABLE_JEMALLOC` with any value, for example:
|
||||
|
||||
{% tabbed_block %}
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -16,6 +16,7 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- cover
|
||||
- light
|
||||
- select
|
||||
- sensor
|
||||
- switch
|
||||
- valve
|
||||
@ -23,6 +24,8 @@ ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
ha_codeowners:
|
||||
- '@mrpasztoradam'
|
||||
---
|
||||
|
||||
The ADS (automation device specification) describes a device-independent and fieldbus independent interface for communication between [Beckhoff](https://www.beckhoff.com/) automation devices running [TwinCAT](https://www.beckhoff.com/en-en/products/automation/twincat/) and other devices implementing this interface.
|
||||
@ -311,4 +314,4 @@ name:
|
||||
required: false
|
||||
description: An identifier for the valve in the frontend.
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -4,6 +4,7 @@ description: Instructions on how to setup AirGradient devices in Home Assistant.
|
||||
ha_category:
|
||||
- Health
|
||||
- Sensor
|
||||
- Update
|
||||
ha_config_flow: true
|
||||
ha_release: 2024.6
|
||||
ha_iot_class: Local Polling
|
||||
|
||||
@ -11,7 +11,7 @@ ha_codeowners:
|
||||
- '@ochlocracy'
|
||||
- '@jbouwh'
|
||||
ha_domain: alexa
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: system
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
---
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -4,7 +4,7 @@ description: Get energy usage from Arizona Public Service (APS) using the Opower
|
||||
ha_category:
|
||||
- Energy
|
||||
- Sensor
|
||||
ha_release: "2024.10"
|
||||
ha_release: 2023.8
|
||||
ha_domain: aps
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: opower
|
||||
|
||||
@ -9,7 +9,7 @@ ha_codeowners:
|
||||
- '@balloob'
|
||||
- '@synesthesiam'
|
||||
ha_domain: assist_pipeline
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: system
|
||||
ha_quality_scale: internal
|
||||
ha_platforms:
|
||||
- select
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -12,8 +12,9 @@ ha_codeowners:
|
||||
ha_domain: bring
|
||||
ha_integration_type: service
|
||||
ha_platforms:
|
||||
- todo
|
||||
- diagnostics
|
||||
- sensor
|
||||
- todo
|
||||
related:
|
||||
- docs: /integrations/todo
|
||||
title: To-do list integration documentation
|
||||
|
||||
@ -8,6 +8,7 @@ ha_release: 2022.9
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@Ernst79'
|
||||
- '@thecode'
|
||||
ha_domain: bthome
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
|
||||
@ -7,11 +7,13 @@ ha_release: '2024.10'
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: cambridge_audio
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- media_player
|
||||
ha_codeowners:
|
||||
- '@noahhusby'
|
||||
ha_config_flow: true
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
ha_zeroconf: true
|
||||
---
|
||||
|
||||
The **Cambridge Audio** {% term integration %} allows you to control all receivers and streamers that support the StreamMagic app.
|
||||
@ -29,7 +31,8 @@ This integration allows you to connect the following devices:
|
||||
- Cambridge Audio CXR120
|
||||
- Cambridge Audio CXR200
|
||||
- Cambridge Audio 851N
|
||||
- Cambridge Audio Edge NQ
|
||||
- Cambridge Audio MXN10
|
||||
- Cambridge Audio AXN10
|
||||
|
||||
Older, RS-232 serial-based amplifiers like the [CXA series](https://www.cambridgeaudio.com/usa/en/products/hi-fi/cx-series-2/cxa81)
|
||||
use a different protocol and are not currently supported.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -9,7 +9,6 @@ ha_config_flow: true
|
||||
ha_domain: dsmr
|
||||
ha_codeowners:
|
||||
- '@Robbie1221'
|
||||
- '@frenck'
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
|
||||
@ -3,7 +3,7 @@ title: Duke Energy
|
||||
description: Instructions on how to integrate Duke Energy within Home Assistant.
|
||||
ha_category:
|
||||
- Energy
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@hunterjm'
|
||||
|
||||
@ -1,15 +1,17 @@
|
||||
---
|
||||
title: ElevenLabs text-to-speech
|
||||
title: ElevenLabs
|
||||
description: Instructions on how to setup ElevenLabs text-to-speech with Home Assistant.
|
||||
ha_category:
|
||||
- Text-to-speech
|
||||
ha_release: 2024.8
|
||||
ha_iot_class: Cloud Push
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: elevenlabs
|
||||
ha_platforms:
|
||||
- tts
|
||||
ha_config_flow: true
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_codeowners:
|
||||
- '@sorgfresser'
|
||||
---
|
||||
|
||||
The **ElevenLabs** text-to-speech {% term integrations %} adds support for [ElevenLabs](https://elevenlabs.io/) as text-to-speech to read a text with natural sounding voices.
|
||||
|
||||
@ -7,7 +7,7 @@ ha_release: 0.29
|
||||
ha_domain: ffmpeg
|
||||
ha_platforms:
|
||||
- camera
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: system
|
||||
---
|
||||
|
||||
The FFmpeg integration allows other Home Assistant integrations to process
|
||||
|
||||
@ -30,8 +30,8 @@ See device section for support information: [water control](#water-control), [ir
|
||||
|
||||
## Water control
|
||||
|
||||
- Water Control Bluetooth ([01889-20](https://www.gardena.com/int/products/watering/water-controls/water-control-bluetooth))
|
||||
- Soil Moisture Sensors ([1867-20](https://www.gardena.com/int/products/watering/water-controls/soil-moisture-sensor/))
|
||||
- Water Control Bluetooth ([01889-20](https://www.gardena.com/int/products/watering/water-controls/water-control-bluetooth/970481101.html))
|
||||
- Soil Moisture Sensors ([1867-20](https://www.gardena.com/int/products/watering/water-controls/soil-moisture-sensor/967926801.html))
|
||||
|
||||
The paring of the device may require a [factory reset](#factory-reset) before it allows a connection.
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -11,6 +11,7 @@ ha_codeowners:
|
||||
- '@exxamalte'
|
||||
ha_domain: gdacs
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- geo_location
|
||||
- sensor
|
||||
ha_integration_type: service
|
||||
|
||||
@ -11,6 +11,7 @@ ha_codeowners:
|
||||
- '@exxamalte'
|
||||
ha_domain: geonetnz_quakes
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- geo_location
|
||||
- sensor
|
||||
ha_integration_type: service
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Cloud Push
|
||||
ha_codeowners:
|
||||
- '@home-assistant/cloud'
|
||||
ha_domain: google_assistant
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: system
|
||||
ha_platforms:
|
||||
- button
|
||||
- diagnostics
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Google Cloud Platform
|
||||
title: Google Cloud
|
||||
description: Google Cloud Platform integration.
|
||||
ha_category:
|
||||
- Speech-to-text
|
||||
|
||||
@ -4,7 +4,7 @@ description: Instructions on how to use Google Photos in Home Assistant.
|
||||
ha_category:
|
||||
- Media source
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_config_flow: true
|
||||
ha_domain: google_photos
|
||||
ha_codeowners:
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -13,6 +13,8 @@ ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
ha_codeowners:
|
||||
- '@alexyao2015'
|
||||
---
|
||||
|
||||
The `html5` notification {% term integration %} enables you to receive push notifications to Chrome or Firefox, no matter where you are in the world. `html5` also supports Chrome and Firefox on Android, which enables native-app-like integrations without actually needing a native app.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -221,7 +221,7 @@ This will override all your schedules during this time. The duration can be give
|
||||
|
||||
```yaml
|
||||
# Replace <name> with the name of your mower.
|
||||
service: husqvarna_automower.override_schedule
|
||||
service: husqvarna_automower.override_schedule_work_area
|
||||
target:
|
||||
entity_id: lawn_mower.<name>
|
||||
data:
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -3,16 +3,17 @@ title: iotty
|
||||
description: Instructions on how to connect iotty Smart Devices to Home Assistant.
|
||||
ha_release: '2024.8'
|
||||
ha_category:
|
||||
- Switch
|
||||
- Cover
|
||||
- Switch
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@pburgio'
|
||||
- '@shapournemati-iotty'
|
||||
ha_domain: iotty
|
||||
ha_platforms:
|
||||
- switch
|
||||
- cover
|
||||
- switch
|
||||
ha_integration_type: device
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Iskra
|
||||
description: Instructions on how to connect your Iskra energy meters to Home Assistant.
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_category:
|
||||
- Energy
|
||||
- Sensor
|
||||
@ -12,10 +12,9 @@ ha_domain: iskra
|
||||
ha_iot_class: Local Polling
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
|
||||
The [Iskra](https://www.iskra.eu/) {% term integration %} allows you to connect Iskra energy meters and power quality analyzers to Home Assistant. Data is polled using Modbus TCP or the Iskra Smart Gateway's REST API.
|
||||
|
||||
## Supported devices
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -13,7 +13,7 @@ ha_codeowners:
|
||||
ha_domain: knocki
|
||||
ha_platforms:
|
||||
- event
|
||||
ha_integration_type: device
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
The **Knocki** {% term integration %} can receive events for the triggers set up from your [Knocki devices](https://knocki.com/).
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -3,7 +3,7 @@ title: Lektrico Charging Station
|
||||
description: Instructions on how to integrate a Lektrico Chargering Station with Home Assistant.
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
@ -11,7 +11,11 @@ ha_codeowners:
|
||||
ha_domain: lektrico
|
||||
ha_zeroconf: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- number
|
||||
- select
|
||||
- sensor
|
||||
ha_integration_type: device
|
||||
---
|
||||
|
||||
The **Lektrico Charging Station** integration integrates your [Lektrico Charging Station](https://lektri.co) into your Home Assistant and allows you to monitor it.
|
||||
|
||||
@ -17,7 +17,6 @@ ha_domain: lutron_caseta
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@swails'
|
||||
- '@bdraco'
|
||||
- '@danaues'
|
||||
- '@eclair4151'
|
||||
ha_zeroconf: true
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -13,6 +13,7 @@ ha_codeowners:
|
||||
ha_domain: madvr
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- diagnostics
|
||||
- remote
|
||||
- sensor
|
||||
ha_integration_type: device
|
||||
|
||||
@ -3,13 +3,14 @@ title: Manual Alarm control panel
|
||||
description: Instructions on how to integrate manual alarms into Home Assistant.
|
||||
ha_category:
|
||||
- Alarm
|
||||
- Helper
|
||||
ha_release: 0.7.6
|
||||
ha_quality_scale: internal
|
||||
ha_domain: manual
|
||||
ha_iot_class: Calculated
|
||||
ha_platforms:
|
||||
- alarm_control_panel
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: helper
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -4,7 +4,7 @@ description: Get energy usage from Mercury NZ Limited using the Opower integrati
|
||||
ha_category:
|
||||
- Energy
|
||||
- Sensor
|
||||
ha_release: 2024.8
|
||||
ha_release: 2023.8
|
||||
ha_domain: mercury_nz
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: opower
|
||||
|
||||
@ -12,7 +12,7 @@ ha_category:
|
||||
- Select
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: 2024.8
|
||||
ha_release: 0.64
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: bmw_connected_drive
|
||||
ha_supporting_integration: BMW Connected Drive
|
||||
|
||||
@ -16,6 +16,7 @@ ha_domain: modern_forms
|
||||
ha_zeroconf: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- diagnostics
|
||||
- fan
|
||||
- light
|
||||
- sensor
|
||||
|
||||
@ -3,14 +3,15 @@ title: Mold Indicator
|
||||
description: How to use the mold growth indication integration in Home Assistant
|
||||
ha_category:
|
||||
- Environment
|
||||
- Helper
|
||||
ha_release: '0.20'
|
||||
ha_iot_class: Local Polling
|
||||
ha_iot_class: Calculated
|
||||
ha_quality_scale: internal
|
||||
ha_domain: mold_indicator
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: helper
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
|
||||
@ -2,17 +2,17 @@
|
||||
title: Monarch Money
|
||||
description: Instructions on the Monarch Money Integration for personal finance.
|
||||
ha_category:
|
||||
- Sensor
|
||||
- Finance
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_codeowners:
|
||||
- '@jeeftor'
|
||||
ha_domain: monarch_money
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: service
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
[Monarch Money](https://www.monarchmoney.com) is a personal finance aggregation and budgeting service that integrates with Plaid, MX, and FinCity, the three major financial backends.
|
||||
|
||||
@ -64,6 +64,7 @@ The following bridges are reported to work with this integration:
|
||||
- SIRO Connect SI7002
|
||||
- SIRO Connect SI7005
|
||||
- Heicko Smart Stick 1ST
|
||||
- DD7006A Smart Home bridge
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -13,6 +13,7 @@ ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- diagnostics
|
||||
- select
|
||||
- sensor
|
||||
ha_integration_type: device
|
||||
|
||||
@ -18,7 +18,7 @@ ha_platforms:
|
||||
- event
|
||||
- light
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
The **Nice G.O.** {% term integration %} lets you control Nice G.O. garage doors through Home Assistant. Device names in Home Assistant are generated based on the names defined in your Nice G.O. mobile app.
|
||||
|
||||
@ -4,13 +4,14 @@ description: Instructions on how to setup NYT Games in Home Assistant.
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_config_flow: true
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@joostlek'
|
||||
ha_domain: nyt_games
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: service
|
||||
---
|
||||
|
||||
The [NYT Games](https://www.nytimes.com/crosswords) integration fetches data about your progress on their daily puzzles.
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: OpenTherm Gateway
|
||||
description: Control your OpenTherm Gateway from Home Assistant.
|
||||
ha_category:
|
||||
- Button
|
||||
- Binary sensor
|
||||
- Button
|
||||
- Climate
|
||||
- Hub
|
||||
- Select
|
||||
@ -15,8 +15,8 @@ ha_codeowners:
|
||||
- '@mvn23'
|
||||
ha_domain: opentherm_gw
|
||||
ha_platforms:
|
||||
- button
|
||||
- binary_sensor
|
||||
- button
|
||||
- climate
|
||||
- select
|
||||
- sensor
|
||||
|
||||
@ -34,7 +34,7 @@ You need an API key, it requires a [subscription](https://openweathermap.org/api
|
||||
|
||||
### OpenWeatherMap API V2.5 Deprecation
|
||||
|
||||
OpenWeatherMap API V2.5 will be closed in June 2024. After this date, you will need to use API V3.0.
|
||||
OpenWeatherMap API V2.5 will be closed on October 7th 2024. After this date, you will need to use API V3.0.
|
||||
|
||||
To continue using the service:
|
||||
|
||||
|
||||
@ -8,8 +8,6 @@ ha_category:
|
||||
- Switch
|
||||
ha_release: 0.26
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@trekky12'
|
||||
ha_domain: pilight
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Pinecil
|
||||
description: Connect and control your Pinecil devices using the IronOS integration
|
||||
ha_category:
|
||||
- Number
|
||||
- Sensor
|
||||
ha_release: 2024.8
|
||||
ha_domain: pinecil
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: Sensoterra
|
||||
description: Instructions on how to integrate your Sensoterra probes with Home Assistant.
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Poll
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_domain: sensoterra
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_codeowners:
|
||||
- '@markruys'
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
This {% term integration %} communicates with your [Sensoterra](https://sensoterra.com) soil moisture probes using the public [Sensoterra Customer API](https://monitor.sensoterra.com/api/v3/) via HTTPS.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
ha_domain: simplefin
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- sensor
|
||||
ha_integration_type: service
|
||||
---
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -14,7 +14,7 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- fan
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
The `smarty` integration lets you control Salda [Smarty](http://www.salda.lt/en/products/category/compact-counter-flow-units) ventilation units from Home Assistant. You need a [MB-GATEWAY](http://www.salda.lt/en/products/item/5637227077) or something similar to connect to your local network.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@dontinelli'
|
||||
ha_domain: solarlog
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -11,8 +11,8 @@ ha_codeowners:
|
||||
ha_config_flow: true
|
||||
ha_dhcp: true
|
||||
ha_platforms:
|
||||
- media_player
|
||||
- binary_sensor
|
||||
- media_player
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -10,6 +10,7 @@ ha_release: 0.93
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@thecode'
|
||||
- '@YogevBokobza'
|
||||
ha_domain: switcher_kis
|
||||
ha_platforms:
|
||||
- button
|
||||
|
||||
@ -9,7 +9,7 @@ ha_codeowners:
|
||||
- '@dmulcahey'
|
||||
ha_domain: tag
|
||||
ha_quality_scale: internal
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: entity
|
||||
---
|
||||
|
||||
<p class='img'>
|
||||
|
||||
@ -3,8 +3,8 @@ title: Tami4 Edge / Edge+
|
||||
description: Tami4 Edge Integration
|
||||
ha_release: 2023.11
|
||||
ha_category:
|
||||
- Sensor
|
||||
- Button
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
|
||||
@ -8,7 +8,10 @@ ha_iot_class: Cloud Polling
|
||||
ha_domain: touchline_sl
|
||||
ha_platforms:
|
||||
- climate
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
ha_codeowners:
|
||||
- '@jnsgruk'
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The **Roth Touchline SL** climate integration enables you to control [Roth Touchline SL](https://www.roth-uk.com/products/control-systems/roth-touchliner-sl-wireless-system) underfloor heating systems.
|
||||
|
||||
@ -74,7 +74,7 @@ Attributes:
|
||||
|
||||
The Traccar Server integration will create devices for each device registered in the Traccar Server with at least one position update.
|
||||
|
||||
These device representations in Home Assistant will have [entities](#entities) associated with them, which you can use in [automations](/docs/automation), [scripts](/docs/script), and display on your [dashboard](/docs/dashboard).
|
||||
These device representations in Home Assistant will have [entities](#entities) associated with them, which you can use in [automations](/docs/automation), [scripts](/docs/scripts), and display on your [dashboard](/dashboards).
|
||||
|
||||
## Entities
|
||||
|
||||
|
||||
@ -2,9 +2,9 @@
|
||||
title: TRIGGERcmd
|
||||
description: How to integrate TRIGGERcmd with Home Assistant.
|
||||
ha_category:
|
||||
- Switch
|
||||
- Automation
|
||||
ha_release: "2024.10"
|
||||
- Switch
|
||||
ha_release: '2024.10'
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
@ -12,8 +12,7 @@ ha_codeowners:
|
||||
ha_domain: triggercmd
|
||||
ha_platforms:
|
||||
- switch
|
||||
ha_zeroconf: false
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
The TRIGGERcmd {% term integration %} allows you to run commands on computers via [TRIGGERcmd](https://triggercmd.com/) with Home Assistant.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- button
|
||||
- cover
|
||||
- sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -2,9 +2,9 @@
|
||||
title: WattTime
|
||||
description: Instructions on how to set up the WattTime integration within Home Assistant.
|
||||
ha_category:
|
||||
- Sensor
|
||||
- Energy
|
||||
- Environment
|
||||
- Sensor
|
||||
ha_release: '2021.10'
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: watttime
|
||||
|
||||
@ -8,7 +8,7 @@ ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: webhook
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: system
|
||||
---
|
||||
|
||||
<script>location.href = '/docs/automation/trigger/#webhook-trigger';</script>
|
||||
|
||||
@ -2,15 +2,14 @@
|
||||
title: Weheat
|
||||
description: Instructions on setting up Weheat within Home Assistant.
|
||||
ha_category:
|
||||
- Energy
|
||||
- Climate
|
||||
- Energy
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@jesperraemaekers'
|
||||
- '@kjell-van-straaten'
|
||||
ha_domain: weheat
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -4,7 +4,7 @@ description: Instructions on how to integrate WAREMA devices via WMS WebControl
|
||||
ha_category:
|
||||
- Cover
|
||||
- Hub
|
||||
ha_release: "2024.10"
|
||||
ha_release: '2024.10'
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@mback2k'
|
||||
@ -12,12 +12,14 @@ ha_domain: wmspro
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- cover
|
||||
ha_integration_type: integration
|
||||
- diagnostics
|
||||
ha_integration_type: hub
|
||||
related:
|
||||
- url: https://www.warema.com/en/smart-home/wms-webcontrol-pro/
|
||||
title: Consumer information about WMS WebControl pro
|
||||
- url: https://smartbuildings.warema.com/en/control-systems/radio-systems/wms/wms-webcontrol-pro/
|
||||
title: Technical documentation for WMS WebControl pro
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
The **WMS WebControl pro** {% term integration %} allows you to integrate WAREMA devices into Home Assistant.
|
||||
|
||||
@ -14,6 +14,7 @@ ha_codeowners:
|
||||
ha_domain: workday
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- diagnostics
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_category:
|
||||
- Event
|
||||
- Lock
|
||||
- Sensor
|
||||
ha_release: 0.64
|
||||
ha_release: 2024.9
|
||||
ha_domain: yale_home
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: yale
|
||||
|
||||
@ -0,0 +1,56 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Home Assistant Connect ZBT-1 issue and replacement"
|
||||
description: "Through extensive testing, we’ve found a fault, but we’re setting up a replacement program."
|
||||
date: 2024-10-02 00:01:01
|
||||
date_formatted: "October 2, 2024"
|
||||
author: Andy Gill
|
||||
comments: true
|
||||
categories: Public-Service-Announcement
|
||||
og_image: /images/blog/2024-10-zbt1-issue/art.jpg
|
||||
---
|
||||
<img src='/images/blog/2024-10-zbt1-issue/art.jpg' alt="Home Assistant Connect ZBT-1 issue and replacement">
|
||||
|
||||
We've found an issue in Home Assistant Connect ZBT-1 that has affected a small number of customers, which appears to be the result of a faulty part incorporated in the most recent batch of ZBT-1 devices. We want to make sure everyone can get a replacement ZBT-1 and ensure they are covered far into the future.
|
||||
|
||||
Though Home Assistant SkyConnect is identical to the ZBT-1 under the hood, it is not affected. The design is not what's at fault, but instead, a defective voltage regulator that was used in this specific batch that is causing the issue. When a ZBT-1 is inserted into certain USB-A ports, the voltage regulator can fail, fully bricking the device. We used high-quality manufacturing and quality control in this and previous batches. We are undertaking an investigation to find out how this could happen and most importantly, to avoid a repeat of anything remotely similar in the future.
|
||||
|
||||
We're sorry for any inconvenience this may cause you. Below are details on our investigation, how devices are affected, and the replacement program.
|
||||
- [Background](#background)
|
||||
- [Pausing sales](#pausing-sales)
|
||||
- [Replacement Program](#replacement-program)
|
||||
- [Conclusion](#conclusion)
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Background
|
||||
|
||||
Around a month ago, we were contacted about one of our latest (and [recently rebranded](/blog/2024/06/13/zbt1-annoucement/)) Home Assistant Connect ZBT-1s not being detected and showing a small mark on the housing. A couple more similar issues were reported, and we began a dialogue with the small number of people who were affected, having them send us the devices to test.
|
||||
|
||||
<p class='img'><img src='/images/blog/2024-10-zbt1-issue/zbt1-issue.jpg' style='border: 0;box-shadow: none;' alt="ZBT-1 case deformation and faulty voltage regulator">Circled in red the deformation on the case and the board showing the failed chip</p>
|
||||
|
||||
When we opened them, we found a dead voltage regulator. The mark in the outer casing is a sign that it overheated and failed. All of our devices are certified by CE and ROHS, and the plastic shell has been designed not to combust. This is a real-life demonstration of just how important this certification is and why we take that step.
|
||||
|
||||
We replaced the voltage regulator on the devices we tested, and the devices sprang back to life. We found our culprit, but why was it failing? As mentioned, the SkyConnect internal design and the manufacturing were effectively identical to the ZBT-1, and we received no reports of any such failures in the literally tens of thousands of them in the wild. In manufacturing runs there is always a little variance, and in this run, something went wrong with the voltage regulator that was sourced - again, we're looking into this.
|
||||
|
||||
It took us a couple of weeks to replicate the problem with our own units. We went down some wrong paths, but eventually found it was triggered only by certain devices, specifically certain desktop PCs (internally, we have only found one desktop that causes this failure). We have not observed the failure occur when the device has only been connected to a Home Assistant Green, Raspberry Pi, or even a Mac. If you have plugged your ZBT-1 into a different device, specifically a desktop PC, and it is not recognized by that system, inspect it for this deformation pictured above. Obviously, we want you to be able to use the device with any hardware, and even if only a small number of devices from this batch have reported issues, it is still unacceptable to us.
|
||||
|
||||
## Pausing sales
|
||||
|
||||
We have asked our distributors to pause sales and return all stock. For the next month, you will see "Out of Stock" banners, and if you are attempting to get a replacement device for a failed unit, this will not be possible until production is resumed.
|
||||
|
||||
We are working to have replacement ZBT-1s shipped by early November.
|
||||
|
||||
## Replacement Program
|
||||
|
||||
If you have purchased Home Assistant Connect ZBT-1, we are working on a replacement program. This program will see Nabu Casa provide a replacement device free of charge for a period of 60 months (5 years) for verified purchases. Regardless of whether the device has failed, we will provide a replacement upon request.
|
||||
|
||||
It is a core value of ours to do things as sustainably as possible, and that's why we've provided such a long coverage period. We want to give owners with working ZBT-1s, who do not expect to use the device in a different system for the foreseeable future, the ability to keep it operating with peace of mind.
|
||||
|
||||
If it's working, keep it plugged into the device it's working with, and don't worry about a replacement until you need it. If you need or want a replacement, please contact the seller where you purchased your device, and they will arrange the return process and replacement. Replacement devices are expected by early November, and we will be prioritizing people with non-functioning devices.
|
||||
|
||||
## Conclusion
|
||||
|
||||
We're sorry for the inconvenience and any disruption to your smart home. As someone who uses Zigbee in their home, which many smart devices rely on, I would hate to have it out of commission.
|
||||
|
||||
Worse things can happen, but this has been a gut punch. All our work at Nabu Casa is to fund the development of Home Assistant and support the Open Home. Issues like this eat into our time, and rob our users of new and great things. Ultimately, we're going to take this setback as a chance to prove we stand by our values and do the right thing.
|
||||
757
source/_posts/2024-10-02-release-202410.markdown
Normal file
757
source/_posts/2024-10-02-release-202410.markdown
Normal file
@ -0,0 +1,757 @@
|
||||
---
|
||||
layout: post
|
||||
title: "2024.10: Heading in the right direction"
|
||||
description: "A brand new heading card, improved YAML syntax for automations, long-term stats repairs, faster upgrades, and more!"
|
||||
date: 2024-10-02 00:00:00
|
||||
date_formatted: "October 2, 2024"
|
||||
author: Franck Nijhof
|
||||
author_twitter: frenck
|
||||
comments: true
|
||||
categories:
|
||||
- Release-Notes
|
||||
- Core
|
||||
og_image: /images/blog/2024-10/social.jpg
|
||||
---
|
||||
|
||||
<lite-youtube videoid="_X2-encNyrA" videotitle="Home Assistant 2024.10 Release Party"></lite-youtube>
|
||||
|
||||
Boo! 👻
|
||||
|
||||
Please don’t be scared; it is October, Halloween is coming, and so is the next
|
||||
Home Assistant release: 2024.10! 🎃
|
||||
|
||||
The release we bring you today is a perfect mix of new UI features, advanced
|
||||
features, improvements, and lots of bug fixes while not being too overwhelming.
|
||||
There is something for everyone in this release.
|
||||
|
||||
Most notably, we have a brand new heading card. It allows you to add titles or
|
||||
subtitles to your dashboards, make them clickable, and even add cute little
|
||||
entities to them. The new section dashboard gets better and better with every
|
||||
release, which is super exciting!
|
||||
|
||||
We also introduce some small YAML automation syntax changes. If you are still
|
||||
a sucker for writing your automations in {% term YAML %} (like me), I’m sure you’ll love
|
||||
these little tweaks that make it all feel more natural.
|
||||
|
||||
Enjoy the release!
|
||||
|
||||
../Frenck
|
||||
|
||||
<!--more-->
|
||||
|
||||
- [Heading in the right direction](#heading-in-the-right-direction)
|
||||
- [Another headline feature](#another-headline-feature)
|
||||
- [Repairs for long-term statistics](#repairs-for-long-term-statistics)
|
||||
- [Improved YAML syntax for automations](#improved-yaml-syntax-for-automations)
|
||||
- [Faster upgrades when using custom integrations](#faster-upgrades-when-using-custom-integrations)
|
||||
- [Integrations](#integrations)
|
||||
- [New integrations](#new-integrations)
|
||||
- [Noteworthy improvements to existing integrations](#noteworthy-improvements-to-existing-integrations)
|
||||
- [Now available to set up from the UI](#now-available-to-set-up-from-the-ui)
|
||||
- [Matter](#matter)
|
||||
- [Other noteworthy changes](#other-noteworthy-changes)
|
||||
- [The source of a repair](#the-source-of-a-repair)
|
||||
- [YAML-editor improvements](#yaml-editor-improvements)
|
||||
- [Patch releases](#patch-releases)
|
||||
- [2024.10.1 - October 4](#2024101---october-4)
|
||||
- [Need help? Join the community!](#need-help-join-the-community)
|
||||
- [Backward-incompatible changes](#backward-incompatible-changes)
|
||||
- [All changes](#all-changes)
|
||||
|
||||
## Heading in the right direction
|
||||
|
||||
Update after update, [Sections] continues to become a customization powerhouse,
|
||||
and this month is no exception. Section titles are replaced with their own card,
|
||||
called the [heading card]. Making them a card rather than an inline title gives
|
||||
you a lot more flexibility, allowing you to put them nearly anywhere.
|
||||
|
||||
The heading card can be used to make titles, but also subtitles, which are half
|
||||
the height and have smaller, lighter text. So, if you have ever had a section
|
||||
that needs to be subdivided, slap a subtitle in there.
|
||||
|
||||
|
||||
|
||||
Titles and subtitles can be made clickable, displaying a chevron
|
||||
{% icon "mdi:chevron-right" %} when you can interact with them. This can
|
||||
perform an action or navigate to a subpage, like having an energy section title
|
||||
navigate to the full energy dashboard.
|
||||
|
||||
Best of all, if you've already added titles to your sections, they will be
|
||||
migrated automatically to the new card. 😎
|
||||
|
||||
[Sections]: /dashboards/sections/
|
||||
[heading card]: /dashboards/heading/
|
||||
|
||||
### Another headline feature
|
||||
|
||||
We had such a fantastic reaction when we released our [renewed badges],
|
||||
and this new heading card has something very similar and equally as visually
|
||||
appealing. It can show multiple entity states to the right of the title or
|
||||
subtitle.
|
||||
|
||||
|
||||
|
||||
Either in a subtle "no color" default or add a splash of color when the entity
|
||||
is in an active state. Other customization options for these entities include
|
||||
changing the icon, visibility, and what happens when you select it.
|
||||
|
||||
[renewed badges]: /dashboards/badges/
|
||||
|
||||
## Repairs for long-term statistics
|
||||
|
||||
[Long-term statistics] are great; they downsample and store the data produced
|
||||
by your {% term sensors %}, allowing Home Assistant to store data indefinitely
|
||||
in a fraction of the space the original readings took up. Take a look back at
|
||||
[your energy usage] from two years ago, or see if your living room really is
|
||||
colder this year compared to last.
|
||||
|
||||
|
||||
|
||||
In the past, if a statistic encountered an issue, it might be quietly broken
|
||||
until you dig into the statistics page. Now, Home Assistant will raise a repair
|
||||
notification when it detects issues with a long-term statistic and give
|
||||
you options for fixing the issue.
|
||||
|
||||
[your energy usage]: /docs/energy/
|
||||
[Long-term statistics]: https://data.home-assistant.io/docs/statistics/
|
||||
|
||||
## Improved YAML syntax for automations
|
||||
|
||||
Recently, we renamed `service` to `action` in the [Home Assistant UI and YAML].
|
||||
This was done with the goal of making the syntax more natural, allowing it
|
||||
to be easier to grasp and read. We want to continue this work to improve the
|
||||
{% term YAML %} syntax, this time focusing on {% term automations %}, and we've made the
|
||||
following changes,
|
||||
|
||||
- The top-level `trigger` key is now `triggers` (plural)
|
||||
- The top-level `condition` key is now `conditions` (plural)
|
||||
- The top-level `action` key is now `actions` (plural)
|
||||
- The `platform` key of a trigger definition is now `trigger`
|
||||
|
||||
The result of all this is that YAML automation syntax now has `triggers` with
|
||||
multiple `trigger` definitions, `conditions` with multiple `condition`
|
||||
definitions, and `actions` with multiple `action` definitions.
|
||||
|
||||
Here is a small example of an automation highlighting these changes.
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/blog/2024-10/YAML-automation-syntax-changes.png" alt="Screenshots; left showing the old automation YAML style, right showing the new style. The differences between them have been highlighted.">
|
||||
The 2024.9 release on the left and this 2024.10 release on the right.
|
||||
</p>
|
||||
|
||||
As with the other syntax changes we've done recently, this is
|
||||
**not a breaking change**, and there will be no deprecation. The previous syntax
|
||||
will continue to work, and there are no plans to remove the old syntax. The new
|
||||
syntax is recommended, and all documentation and examples have been updated.
|
||||
Automations managed by the automation editor will automatically be migrated to
|
||||
the new syntax when saving an automation.
|
||||
|
||||
This is not the only change to our syntax, thanks to [@karwosts] we now support
|
||||
[merging a list of triggers], which is mostly useful for
|
||||
{% term blueprint %} authors.
|
||||
|
||||
[merging a list of triggers]: /docs/automation/trigger/#merging-lists-of-triggers
|
||||
[Home Assistant UI and YAML]: /blog/2024/08/07/release-20248/#goodbye-service-calls-hello-actions-
|
||||
|
||||
## Faster upgrades when using custom integrations
|
||||
|
||||
We want Home Assistant to continue to work on a wide range of hardware. If you
|
||||
look at our [opt-in analytics] you'll see a sizable amount of homes running it
|
||||
on single-board computers from the mid-2010s. A lot of effort has been put into
|
||||
keeping Home Assistant lean, and this release has some good improvements. This
|
||||
is specially for users of custom integrations, and this follows HACS getting a
|
||||
great [speed boost for downloads].
|
||||
|
||||
On each upgrade, all dependencies needed for {% term "custom integrations" %}
|
||||
are now downloaded and installed. We are now using `uv` internally to download
|
||||
and install dependencies, which is a faster and more efficient way to download
|
||||
and install dependencies. If you're not aware, `uv` is what makes our release
|
||||
process so fast nowadays, and [@edenhaus] has done an interesting
|
||||
[developer backstory] on our move from `pip` to `uv` (saving us 200+ hours
|
||||
of execution time a month). [@edenhaus] has also implemented `uv` at runtime
|
||||
as well.
|
||||
|
||||
This speeds up the upgrade process, especially for custom integrations with many
|
||||
dependencies, or installations with many custom integrations. This change is
|
||||
fully transparent to the user, and no action is required. Just sit down, relax,
|
||||
and enjoy the faster upgrade process!
|
||||
|
||||
[@edenhaus]: https://github.com/edenhaus
|
||||
[developer backstory]: https://developers.home-assistant.io/blog/2024/04/03/build-images-with-uv/
|
||||
[opt-in analytics]: https://analytics.home-assistant.io/
|
||||
[speed boost for downloads]: /blog/2024/08/21/hacs-the-best-way-to-share-community-made-projects/#faster-downloads
|
||||
|
||||
## Integrations
|
||||
|
||||
Thanks to our community for keeping pace with the new {% term integrations %}
|
||||
and improvements to existing ones! You’re all awesome 🥰
|
||||
|
||||
### New integrations
|
||||
|
||||
We welcome the following new integrations in this release:
|
||||
|
||||
- **[Cambridge Audio]**, added by [@noahhusby]
|
||||
Control all receivers and streamers that support the [StreamMagic app].
|
||||
- **[Deako Smart Lighting]**, added by [@Balake]
|
||||
Control and automate your [Deako] devices.
|
||||
- **[Duke Energy]**, added by [@hunterjm]
|
||||
Import your energy usage data from Duke Energy into the Home Assistant energy
|
||||
dashboard.
|
||||
- **[Google Photos]**, added by [@allenporter]
|
||||
Upload photos to your [Google Photos library] and use as a [media source].
|
||||
Note that only images uploaded by the integration can be viewed and used.
|
||||
- **[Iskra]**, added by [@iskrakranj]
|
||||
Monitor your energy and power usage from an Iskra energy meter.
|
||||
- **[Lektrico Charging Station]**, added by [@Lektrico]
|
||||
Get in control of your [Lektrico EV charger] from Home Assistant and optimize
|
||||
your energy usage.
|
||||
- **[Monarch Money]**, added by [@jeeftor]
|
||||
Monitor your account balance using the [Monarch Money personal finance service].
|
||||
- **[NYT Games]**, added by [@joostlek]
|
||||
Keep track of your [New York Times games] progress, like Spelling Bee and Wordle.
|
||||
- **[Sensoterra]**, added by [@markruys]
|
||||
Monitor your soil moisture and temperature using [Sensoterra sensors].
|
||||
- **[TRIGGERcmd]**, added by [@rvmey]
|
||||
Execute commands on your computer(s) using the [TRIGGERcmd cloud service].
|
||||
- **[Weheat]**, added by [@jesperraemaekers]
|
||||
Manage and monitor your [Weheat heatpump], keeping your home warm and cozy.
|
||||
- **[WMS WebControl pro]**, added by [@mback2k]
|
||||
Control your [WAREMA] sun shading covers entirely locally.
|
||||
|
||||
[@allenporter]: https://github.com/allenporter
|
||||
[@Balake]: https://github.com/Balake
|
||||
[@hunterjm]: https://github.com/hunterjm
|
||||
[@iskrakranj]: https://github.com/iskrakranj
|
||||
[@jeeftor]: https://github.com/jeeftor
|
||||
[@jesperraemaekers]: https://github.com/jesperraemaekers
|
||||
[@joostlek]: https://github.com/joostlek
|
||||
[@Lektrico]: https://github.com/Lektrico
|
||||
[@markruys]: https://github.com/markruys
|
||||
[@mback2k]: https://github.com/mback2k
|
||||
[@noahhusby]: https://github.com/noahhusby
|
||||
[@rvmey]: https://github.com/rvmey
|
||||
[Cambridge Audio]: /integrations/cambridge_audio
|
||||
[Deako Smart Lighting]: /integrations/deako
|
||||
[Deako]: https://www.deako.com/
|
||||
[Duke Energy]: /integrations/duke_energy
|
||||
[Google Photos library]: https://photos.google.com/
|
||||
[Google Photos]: /integrations/google_photos
|
||||
[Iskra]: /integrations/iskra
|
||||
[Lektrico Charging Station]: /integrations/lektrico
|
||||
[Lektrico EV charger]: https://lektri.co/
|
||||
[media source]: /integrations/media_source
|
||||
[Monarch Money personal finance service]: https://www.monarchmoney.com/
|
||||
[Monarch Money]: /integrations/monarch_money
|
||||
[New York Times games]: https://www.nytimes.com/games
|
||||
[NYT Games]: /integrations/nyt_games
|
||||
[Sensoterra sensors]: https://www.sensoterra.com/sensors/
|
||||
[Sensoterra]: /integrations/sensoterra
|
||||
[StreamMagic app]: https://www.cambridgeaudio.com/usa/en/products/streammagic
|
||||
[TRIGGERcmd cloud service]: https://triggercmd.com
|
||||
[TRIGGERcmd]: /integrations/triggercmd
|
||||
[WAREMA]: https://www.warema.com/
|
||||
[Weheat heatpump]: https://www.weheat.nl/
|
||||
[Weheat]: /integrations/weheat
|
||||
[WMS WebControl pro]: /integrations/wmspro
|
||||
|
||||
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:
|
||||
|
||||
- **[Arizona Public Service (APS)]**, provided by [Opower], added by [@seferino-fernandez]
|
||||
|
||||
[@seferino-fernandez]: https://github.com/seferino-fernandez
|
||||
[Arizona Public Service (APS)]: /integrations/aps
|
||||
[Opower]: /integrations/opower
|
||||
|
||||
### Noteworthy improvements to existing integrations
|
||||
|
||||
It is not just new {% term integrations %} that have been added; existing
|
||||
integrations are also being constantly improved. Here are some of the noteworthy
|
||||
changes to existing integrations:
|
||||
|
||||
- [@Bre77] has been busy with the [Tesla Fleet] integration, adding a bunch of
|
||||
new features and entities to control your Tesla vehicle. It now supports
|
||||
climate, media player, cover, number, select, button, and lock entities.
|
||||
- You can now control the volume, ringtone, and status light of your [Reolink]
|
||||
Hub! Cool, [@starkillerOG]!
|
||||
- [@daniel-k] added support for controlling the volume and [@sdb9696] added a
|
||||
switch for controlling motion detection on [Ring] devices; Nice work team!
|
||||
- The [Switchbot Cloud] integration now supports the [K10+ Mini Robot Vacuum].
|
||||
Thanks, [@Gigatrappeur]!
|
||||
- [@sorgfresser] extended the [ElevenLabs] integration with integration options
|
||||
to control the voice settings. Nice!
|
||||
- The [Squeezebox (Lyrion Music Server)] integration now has new service sensors,
|
||||
and support for your favorites straight from the media browser.
|
||||
Thanks, [@pssc] and [@rajlaud]!
|
||||
- [@tronikos] added [Google Cloud] speech-to-text (STT) to Home Assistant. This
|
||||
allows you to use Google's Cloud speech-to-text with [Assist]! Awesome!
|
||||
- If you are using the [Husqvarna Automower], you can now view the calendar
|
||||
it provides, thanks to [@Thomas55555]!
|
||||
- [@klaasnicolaas] added support for home batteries to the [Autarco]
|
||||
integration so you can use them in your energy dashboard. Great!
|
||||
|
||||
[@Bre77]: https://github.com/Bre77
|
||||
[@daniel-k]: https://github.com/daniel-k
|
||||
[@Gigatrappeur]: https://github.com/Gigatrappeur
|
||||
[@klaasnicolaas]: https://github.com/klaasnicolaas
|
||||
[@pssc]: https://github.com/pssc
|
||||
[@rajlaud]: https://github.com/rajlaud
|
||||
[@sdb9696]: https://github.com/sdb9696
|
||||
[@sorgfresser]: https://github.com/sorgfresser
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@Thomas55555]: https://github.com/Thomas55555
|
||||
[@tronikos]: https://github.com/tronikos
|
||||
[Assist]: /voice_control
|
||||
[Autarco]: /integrations/autarco
|
||||
[ElevenLabs]: /integrations/elevenlabs
|
||||
[Google Cloud]: /integrations/google_cloud
|
||||
[Husqvarna Automower]: /integrations/husqvarna_automower
|
||||
[K10+ Mini Robot Vacuum]: https://eu.switch-bot.com/products/switchbot-mini-robot-vacuum-k10
|
||||
[Reolink]: /integrations/reolink
|
||||
[Ring]: /integrations/ring
|
||||
[Squeezebox (Lyrion Music Server)]: /integrations/squeezebox
|
||||
[Switchbot Cloud]: /integrations/switchbot_cloud
|
||||
[Tesla Fleet]: /integrations/tesla_fleet
|
||||
|
||||
### Now available to set up from the UI
|
||||
|
||||
While most {% term integrations %} can be set up directly from the Home Assistant
|
||||
user interface, some were only available using YAML configuration. We keep moving
|
||||
more integrations to the UI, making them more accessible for everyone
|
||||
to set up and use.
|
||||
|
||||
The following integrations are now available via the Home Assistant UI:
|
||||
|
||||
- **[Emoncms]**, done by [@alexandrecuer]
|
||||
- **[Google Cloud Platform]**, done by [@tronikos]
|
||||
- **[HTML5 Push Notifications]**, done by [@alexyao2015]
|
||||
- **[Mold Indicator]**, done by [@gjohansson-ST]
|
||||
|
||||
[@alexandrecuer]: https://github.com/alexandrecuer
|
||||
[@alexyao2015]: https://github.com/alexyao2015
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[@tronikos]: https://github.com/tronikos
|
||||
[Emoncms]: /integrations/emoncms
|
||||
[Google Cloud Platform]: /integrations/google_cloud
|
||||
[HTML5 Push Notifications]: /integrations/html5
|
||||
[Mold Indicator]: /integrations/mold_indicator
|
||||
|
||||
## Matter
|
||||
|
||||
At this point, our [Matter integration] is almost becoming a monthly recurring
|
||||
topic in our release notes. For a good reason! The development is moving forward
|
||||
at a strong pace; running toward the certification finish line!
|
||||
|
||||
<center><img src='/images/supported_brands/matter.png' alt='Matter logo' class='no-shadow'></center><br>
|
||||
|
||||
In terms of stability, we have improved the robustness of the integration to
|
||||
ensure it sets up correctly every time, even if an issue with one
|
||||
of your devices occurs. Besides the usual bugfixes and improvements, this
|
||||
release has some cool new features and additions:
|
||||
|
||||
- **Button entities**
|
||||
New button entities that allow you to perform an action on a device. For
|
||||
example, to identify a device or reset the filter state.
|
||||
- **Valve entities**
|
||||
Support for water valves, allowing you to control the flow of fluids or gases.
|
||||
- **Support for operation states**
|
||||
Control and monitor the operation state of, for example, dishwashers
|
||||
and other household equipment.
|
||||
- **Support for smoke and CO sensors**
|
||||
Monitor the air quality in your home with smoke and CO sensors.
|
||||
- **Add support for Matter 1.3 power/energy sensors**
|
||||
Especially the energy sensors are great to use with the energy dashboard.
|
||||
|
||||
[Matter integration]: /integrations/matter
|
||||
|
||||
## Other noteworthy changes
|
||||
|
||||
There are many more improvements in this release; here are some of the other
|
||||
noteworthy changes this release:
|
||||
|
||||
- In June, we added support for adding [Model IDs to devices]. This release
|
||||
has lots of integrations that add them, including [Matter], [Plugwise],
|
||||
[Wallbox], and [Govee]. We are calling for contributions to add model IDs to
|
||||
more integrations! Maybe a cool suggestion for an [Hacktoberfest] contribution!
|
||||
- [@bmesuere] improved the accessibility of all graphs by adjusting all the
|
||||
default colors used in those graphs! You are a hero!
|
||||
- When you unignore an integration or device on the integrations page,
|
||||
Home Assistant will instantly try to rediscover it again! Nice! Thanks,
|
||||
[@emontnemery]!
|
||||
- We now have a new unit of measurement for energy entities: calories. Useful,
|
||||
for devices like a treadmill or an exercise bike. Thanks, [@dudanov]!
|
||||
- [@TrevorSchirmer] did something similar, and added a new unit of speed:
|
||||
mm/s and in/s. Thank you!
|
||||
- When you rename a device, you will now see more details about the rename
|
||||
operation. Including a preview of the new entity IDs. Nice, [@karwosts]!
|
||||
- [@gjohansson-ST] added a new template function [`merge_response`] that
|
||||
allows you to merge multiple responses of a single action or multiple actions
|
||||
into a single response. Nice!
|
||||
- [Trigger-based templates] now have support for adding conditions! Just like
|
||||
automations, you can now add conditions to these entities to control when
|
||||
they are rendered. Thanks, [@chammp]!
|
||||
- More template fun! You can now set up your templated alarm control panel
|
||||
straight from the UI. Thanks, [@gjohansson-ST]!
|
||||
- The statistics developer tools have been improved. They now have the new-style
|
||||
data tables and the ability to bulk select items to action. Awesome [@karwosts]!
|
||||
- There is a new entity in town, the [`assist satellite` entity](/integrations/assist_satellite/).
|
||||
It is a building block for remote satellites devices that use [Assist]. This
|
||||
is in preparation for our upcoming satellite hardware. Stay tuned!
|
||||
|
||||
[@bmesuere]: https://github.com/bmesuere
|
||||
[@chammp]: https://github.com/chammp
|
||||
[@dudanov]: https://github.com/dudanov
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[@karwosts]: https://github.com/karwosts
|
||||
[@TrevorSchirmer]: https://github.com/TrevorSchirmer
|
||||
[`merge_response`]: /docs/configuration/templating/#merge-action-responses
|
||||
[Assist]: /voice_control
|
||||
[Govee]: /integrations/govee_light_local
|
||||
[Hacktoberfest]: https://hacktoberfest.digitalocean.com/
|
||||
[Matter]: /integrations/matter
|
||||
[Model IDs to devices]: https://developers.home-assistant.io/blog/2024/07/16/device-info-model-id
|
||||
[Plugwise]: /integrations/plugwise
|
||||
[Trigger-based templates]: /integrations/template/#trigger-based-template-binary-sensors-buttons-images-numbers-selects-and-sensors
|
||||
[Wallbox]: /integrations/wallbox
|
||||
|
||||
### The source of a repair
|
||||
|
||||
{% term Integrations %} can raise issues in your repairs dashboard, they can
|
||||
raise issues for themselves, but also for other integrations. An example of
|
||||
such an issue is an integration that connects to your device that raises an
|
||||
issue on an {% term automation %} that controls it.
|
||||
|
||||
The result is an automation issue in your repair center. This is cool, but
|
||||
you might want to know which integration raised the issue in the first place.
|
||||
|
||||
Thanks to [@wendevlin], we now show the source integration of the repair issue
|
||||
in the issue dialog.
|
||||
|
||||
<img class="no-shadow" src="/images/blog/2024-10/repair-issue-reported-by.png" alt="Screenshot showing the new repairs dialog reporting the integration that raised it.">
|
||||
|
||||
[@wendevlin]: https://github.com/wendevlin
|
||||
|
||||
### YAML-editor improvements
|
||||
|
||||
[@naps62] has been busy improving the YAML editor found in the Home Assistant
|
||||
user interface.
|
||||
|
||||
We now have a vertical line based on indentation, which makes it easier to see
|
||||
the indentation of your YAML configuration and allows you to spot and prevent
|
||||
indentation errors.
|
||||
|
||||
<img class="no-shadow" src="/images/blog/2024-10/YAML-editor-improvements.png" alt="Screenshot showing the YAML editor with collapsed sections and the vertical indentation line.">
|
||||
|
||||
But he didn’t stop there. You can now collapse and expand sections of your
|
||||
YAML configuration based on the indentation level; which is also demonstrated
|
||||
in the screenshot above.
|
||||
|
||||
Nice work [@naps62]!
|
||||
|
||||
|
||||
[@naps62]: https://github.com/naps62
|
||||
|
||||
## Patch releases
|
||||
|
||||
We will also release patch releases for Home Assistant 2024.10 in October. These
|
||||
patch releases only contain bug fixes. Our goal is to release a patch release
|
||||
every Friday.
|
||||
|
||||
### 2024.10.1 - October 4
|
||||
|
||||
- Fix device id support for alarm control panel template ([@piitaya] - [#127340])
|
||||
- Bump pysmlight 0.1.2 ([@tl-sl] - [#127376])
|
||||
- Remove assumption in ConfigEntryItems about unique unique_id ([@emontnemery] - [#127399])
|
||||
- Add missing number platform to init of Tesla Fleet ([@Bre77] - [#127406])
|
||||
- Bump aiomealie to 0.9.3 ([@andrew-codechimp] - [#127454])
|
||||
- Fix int value in unique_id for Tellduslive ([@robinostlund] - [#127526])
|
||||
- Bump matrix-nio to 0.25.2 ([@PaarthShah] - [#127535])
|
||||
- Adjust polling rate of Rituals Perfume Genie ([@frenck] - [#127544])
|
||||
- Create new clientsession for NYT Games ([@joostlek] - [#127547])
|
||||
- Strip the NYT Games token ([@joostlek] - [#127548])
|
||||
- Revert "Bump pychromecast to 14.0.2 (#127333)" ([@joostlek] - [#127555])
|
||||
|
||||
[#126782]: https://github.com/home-assistant/core/pull/126782
|
||||
[#127340]: https://github.com/home-assistant/core/pull/127340
|
||||
[#127376]: https://github.com/home-assistant/core/pull/127376
|
||||
[#127399]: https://github.com/home-assistant/core/pull/127399
|
||||
[#127406]: https://github.com/home-assistant/core/pull/127406
|
||||
[#127454]: https://github.com/home-assistant/core/pull/127454
|
||||
[#127526]: https://github.com/home-assistant/core/pull/127526
|
||||
[#127535]: https://github.com/home-assistant/core/pull/127535
|
||||
[#127544]: https://github.com/home-assistant/core/pull/127544
|
||||
[#127547]: https://github.com/home-assistant/core/pull/127547
|
||||
[#127548]: https://github.com/home-assistant/core/pull/127548
|
||||
[#127555]: https://github.com/home-assistant/core/pull/127555
|
||||
[@Bre77]: https://github.com/Bre77
|
||||
[@PaarthShah]: https://github.com/PaarthShah
|
||||
[@andrew-codechimp]: https://github.com/andrew-codechimp
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@joostlek]: https://github.com/joostlek
|
||||
[@piitaya]: https://github.com/piitaya
|
||||
[@robinostlund]: https://github.com/robinostlund
|
||||
[@tl-sl]: https://github.com/tl-sl
|
||||
|
||||
## 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.
|
||||
|
||||
## Backward-incompatible changes
|
||||
|
||||
We do our best to avoid making changes to existing functionality that might
|
||||
unexpectedly impact your Home Assistant installation. Unfortunately, sometimes,
|
||||
it is inevitable.
|
||||
|
||||
We always make sure to document these changes to make the transition as easy as
|
||||
possible for you. This release has the following backward-incompatible changes:
|
||||
|
||||
{% details "Climate" %}
|
||||
|
||||
We have added more validation to the `climate.set_humidity` action, which
|
||||
enforces that the set target humidity is within the targeted entity's minimum
|
||||
and maximum humidity levels.
|
||||
|
||||
You should adjust automations and scripts to use valid values if you are using
|
||||
this action.
|
||||
|
||||
([@gjohansson-ST] - [#125242]) ([documentation](/integrations/climate))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#125242]: https://github.com/home-assistant/core/pull/125242
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ecobee" %}
|
||||
|
||||
The previously deprecated `aux_heat` attribute has been removed from the
|
||||
provided climate entity.
|
||||
|
||||
([@gjohansson-ST] - [#125246]) ([documentation](/integrations/ecobee))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#125246]: https://github.com/home-assistant/core/pull/125246
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Honeywell Total Connect Comfort (US)" %}
|
||||
|
||||
The previously deprecated `aux_heat` attribute has been removed from the
|
||||
provided climate entity.
|
||||
|
||||
([@gjohansson-ST] - [#125248]) ([documentation](/integrations/honeywell))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#125248]: https://github.com/home-assistant/core/pull/125248
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Humidifier" %}
|
||||
|
||||
We have added more validation to the `humidifier.set_humidity` action, which
|
||||
enforces that the target humidity is within the targeted entity's minimum
|
||||
and maximum humidity levels.
|
||||
|
||||
You might need to adjust automations and scripts to use valid values if you
|
||||
are using this action.
|
||||
|
||||
([@gjohansson-ST] - [#125863]) ([documentation](/integrations/humidifier))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#125863]: https://github.com/home-assistant/core/pull/125863
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Nuki" %}
|
||||
|
||||
The previously deprecated `nuki_id` and `battery_critical` attributes have
|
||||
been removed from the Nuki entities. If you are using these attributes in
|
||||
automations or scripts, you need to update those.
|
||||
|
||||
([@steffenrapp] - [#125348]) ([documentation](/integrations/nuki))
|
||||
|
||||
[@steffenrapp]: https://github.com/steffenrapp
|
||||
[#125348]: https://github.com/home-assistant/core/pull/125348
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "OpenTherm Gateway" %}
|
||||
|
||||
To modernize the OpenTherm Gateway integration, all entities have been split
|
||||
into different devices. As a result, the OpenTherm Gateway climate entity
|
||||
has been moved to a new OpenTherm Thermostat device.
|
||||
|
||||
Configurations that look for the climate entity by device must be adjusted
|
||||
accordingly.
|
||||
|
||||
In the process, all entities were reviewed and some were found to be irrelevant
|
||||
or superfluous. These entities have been removed. All removed entities were
|
||||
previously disabled by default, so anyone who has never manually enabled an
|
||||
entity in the OpenTherm Gateway integration is not affected by this.
|
||||
|
||||
All other users should review their configuration for using OpenTherm Gateway
|
||||
entities that no longer exist or have been assigned to another device.
|
||||
|
||||
([@mvn23] - [#124869]) ([documentation](/integrations/opentherm_gw))
|
||||
|
||||
[@mvn23]: https://github.com/mvn23
|
||||
[#124869]: https://github.com/home-assistant/core/pull/124869
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Pentair ScreenLogic" %}
|
||||
|
||||
Support for use of an area, device, or entity as a target for ScreenLogic
|
||||
actions has been removed. Instead, use `config_entry` with the
|
||||
`entry_id` of the desired ScreenLogic
|
||||
|
||||
Support for using an area, device, or entity as a target for ScreenLogic
|
||||
actions has been removed. Instead, use `config_entry` with the `entry_id` of
|
||||
the desired ScreenLogic.
|
||||
|
||||
([@dieselrabbit] - [#123432]) ([documentation](/integrations/screenlogic))
|
||||
|
||||
[@dieselrabbit]: https://github.com/dieselrabbit
|
||||
[#123432]: https://github.com/home-assistant/core/pull/123432
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Ping" %}
|
||||
|
||||
The binary sensor attributes this integration provided have been
|
||||
replaced with sensor entities in Home Assistant 2024.4. These deprecated
|
||||
attributes have now been removed.
|
||||
|
||||
([@jpbede] - [#125760]) ([documentation](/integrations/ping))
|
||||
|
||||
[@jpbede]: https://github.com/jpbede
|
||||
[#125760]: https://github.com/home-assistant/core/pull/125760
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Ring" %}
|
||||
|
||||
The `ring.update` action was deprecated in the 2024.4 release and has now
|
||||
been removed. Please use `homeassistant.update_entity` if you need
|
||||
a replacement.
|
||||
|
||||
([@jpbede] - [#125762]) ([documentation](/integrations/ring))
|
||||
|
||||
[@jpbede]: https://github.com/jpbede
|
||||
[#125762]: https://github.com/home-assistant/core/pull/125762
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Squeezebox (Lyrion Music Server)" %}
|
||||
|
||||
We previously noticed that the squeezebox platform had deprecated
|
||||
the `squeezebox_sync` and `squeezebox_unsync` actions and the `sync_group`
|
||||
entity attribute in favor of the newer "join" framework common to all
|
||||
media players.
|
||||
|
||||
These deprecated actions and entity attributes have now been removed.
|
||||
|
||||
([@rajlaud] - [#125271]) ([documentation](/integrations/squeezebox))
|
||||
|
||||
[@rajlaud]: https://github.com/rajlaud
|
||||
[#125271]: https://github.com/home-assistant/core/pull/125271
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Templates" %}
|
||||
|
||||
Limit maximum template render output to 256KiB to ensure template renders
|
||||
do not inject unreasonable data into the system and cause a crash.
|
||||
|
||||
256KiB is likely to still block Home Assistant’s event loop for an unreasonable
|
||||
amount of time, but it's likely someone is using the template engine for large
|
||||
blocks of data, so we want a limit that still allows that but has a reasonable
|
||||
safety margin to prevent the system from crashing down.
|
||||
|
||||
([@bdraco] - [#124946])
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[#124946]: https://github.com/home-assistant/core/pull/124946
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ThermoWorks Smoke" %}
|
||||
|
||||
The ThermoWorks Smoke integration is disabled because it creates
|
||||
an unresolvable dependency conflict.
|
||||
|
||||
Contributions to fixing this conflict are greatly appreciated.
|
||||
|
||||
([@edenhaus] - [#125661]) ([documentation](/integrations/thermoworks_smoke))
|
||||
|
||||
[@edenhaus]: https://github.com/edenhaus
|
||||
[#125661]: https://github.com/home-assistant/core/pull/125661
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Tfiac" %}
|
||||
|
||||
The Tfiac integration is disabled because we cannot create valid Python wheels
|
||||
for its dependencies.
|
||||
|
||||
Contributions to fixing this issue are greatly appreciated.
|
||||
|
||||
([@edenhaus] - [#125692]) ([documentation](/integrations/tfiac))
|
||||
|
||||
[@edenhaus]: https://github.com/edenhaus
|
||||
[#125692]: https://github.com/home-assistant/core/pull/125692
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Z-Wave" %}
|
||||
|
||||
With this release, you will need to update your `zwave-js-server` instance.
|
||||
You must use `zwave-js-server` 1.37.0 or greater (schema 37).
|
||||
|
||||
- If you use the Z-Wave JS add-on, you need at least version `0.7.0`.
|
||||
- If you use the Z-Wave JS UI add-on, you need at least version [`3.9.0`](https://github.com/hassio-addons/addon-zwave-js-ui/releases/tag/v3.9.0).
|
||||
- If you use the Z-Wave JS UI Docker container, you need at least version [`9.16.0`](https://github.com/zwave-js/zwave-js-ui/releases/tag/v9.16.0).
|
||||
- If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least `1.37.0`.
|
||||
|
||||
([@MartinHjelmare] - [#125666]) ([documentation](/integrations/zwave_js))
|
||||
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[#125666]: https://github.com/home-assistant/core/pull/125666
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
If you are a custom integration developer and want to learn about 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:
|
||||
|
||||
- [Additional validation in Climate set temperature](https://developers.home-assistant.io/blog/2024/09/24/climate-set-temp-validation)
|
||||
- [Calories added to energy class sensors](https://developers.home-assistant.io/blog/2024/09/10/calories-units)
|
||||
- [Deprecating constants for Media Player](https://developers.home-assistant.io/blog/2024/09/23/constants-media-player-deprecation)
|
||||
- [Deprecating feature flag constants for Vacuum](https://developers.home-assistant.io/blog/2024/09/23/feature-flag-constants-vacuum-deprecation)
|
||||
- [Deprecating state constants for camera](https://developers.home-assistant.io/blog/2024/09/23/state-constants-camera-deprecation)
|
||||
- [Deprecating state constants for lock](https://developers.home-assistant.io/blog/2024/09/23/state-constants-lock-deprecation)
|
||||
- [Enforce SourceType and add shorthand attributes and EntityDescription to device_tracker](https://developers.home-assistant.io/blog/20240924-device-tracker-entity-description)
|
||||
- [Extend deprecation period of @bind_hass and hass.components](https://developers.home-assistant.io/blog/2024/09/11/extending-deprecation-hass-components)
|
||||
- [Introducing the Assist satellite entity](https://developers.home-assistant.io/blog/2024/10/01/assist-satellite-entity/)
|
||||
- [Version compare for Update platform can now be overwritten](https://developers.home-assistant.io/blog/2024/09/28/update-version-compare)
|
||||
|
||||
[devblog]: https://developers.home-assistant.io/blog/
|
||||
|
||||
## 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 2024.10](/changelogs/core-2024.10)
|
||||
2517
source/changelogs/core-2024.10.markdown
Normal file
2517
source/changelogs/core-2024.10.markdown
Normal file
File diff suppressed because it is too large
Load Diff
@ -79,7 +79,7 @@ frontpage_image: /images/connectzbt1/connectzbt1-cover.jpg
|
||||
<div class="content">
|
||||
<div class="material-card text banner-overlay with-box">
|
||||
<div>
|
||||
<div class="banner-overlay-header">Available now</div>
|
||||
<div class="banner-overlay-header">Temporarily unavailable</div>
|
||||
<div class="banner-overlay-content">
|
||||
Home Assistant Connect ZBT-1 (previously known as Home Assistant SkyConnect) is the easiest way to add Zigbee support
|
||||
to your Home Assistant instance.
|
||||
@ -201,7 +201,14 @@ frontpage_image: /images/connectzbt1/connectzbt1-cover.jpg
|
||||
This experimental firmware has been available since December 2022. Through extensive testing, we have found that although it works in some circumstances, it has technical limitations that lead to a worse user experience. We now do not recommend using this firmware, and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant Connect ZBT-1 deliver the best experience to users.<br /><br />
|
||||
|
||||
If you currently have the multiprotocol firmware installed but don't actively use it to connect to Thread devices, we recommend that you <a href="https://connectzbt1.home-assistant.io/procedures/disable-multiprotocol/">disable multiprotocol</a>. <br /><br />
|
||||
Nothing changes for current users of the multiprotocol firmware who are happy with their experience. The experimental multiprotocol firmware will remain available, but we will not recommend it to new users.{% enddetails %}
|
||||
Nothing changes for current users of the multiprotocol firmware who are happy with their experience. The experimental multiprotocol firmware will remain available, but we will not recommend it to new users.
|
||||
{% enddetails %}
|
||||
|
||||
{% details "What is the Home Assistant Connect ZBT-1 replacement program?" %}
|
||||
We’ve found an issue in Home Assistant Connect ZBT-1 that is the result of a faulty part incorporated in the first batch of ZBT-1 devices (sold between June and October of 2024). These devices can fail if plugged into certain USB-A ports, but can operate without issue if plugged into most devices. <br /><br />
|
||||
We have instituted a program to provide a replacement device free of charge for a period of 60 months (effective October 2, 2024) for verified purchases. If it’s working, keep it plugged into the device it’s working with. The long coverage period means you don’t need to worry about a replacement until you require one. Regardless of whether the device has failed, we will provide a replacement upon request. SkyConnect branded devices are unaffected by this issue and do not require replacement. <br /><br />
|
||||
Please contact the seller where you purchased your device, and they will arrange the return process and replacement. For more information on the program, <a href="https://www.home-assistant.io/blog/2024/10/02/connect-zbt1-issue-and-replacement/">read our blog</a>
|
||||
{% enddetails %}
|
||||
</div>
|
||||
|
||||
<div style="margin-top: 24px; text-align: center; font-size: .8rem;">
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user