mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-22 00:36:49 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
4202e1da33
36
CODEOWNERS
36
CODEOWNERS
@ -36,6 +36,7 @@ source/_integrations/ambient_station.markdown @bachya
|
||||
source/_integrations/amcrest.markdown @flacjacket
|
||||
source/_integrations/amp_motorization.markdown @starkillerOG
|
||||
source/_integrations/analytics.markdown @home-assistant/core @ludeeus
|
||||
source/_integrations/android_ip_webcam.markdown @engrbm87
|
||||
source/_integrations/androidtv.markdown @JeffLIrion @ollo69
|
||||
source/_integrations/anthemav.markdown @hyralex
|
||||
source/_integrations/apache_kafka.markdown @bachya
|
||||
@ -52,6 +53,7 @@ source/_integrations/atag.markdown @MatsNL
|
||||
source/_integrations/aten_pe.markdown @mtdcr
|
||||
source/_integrations/atome.markdown @baqs
|
||||
source/_integrations/august.markdown @bdraco
|
||||
source/_integrations/august_ble.markdown @bdraco
|
||||
source/_integrations/aurora.markdown @djtimca
|
||||
source/_integrations/aurora_abb_powerone.markdown @davet2001
|
||||
source/_integrations/aussie_broadband.markdown @nickw444 @Bre77
|
||||
@ -86,6 +88,7 @@ source/_integrations/brother.markdown @bieniu
|
||||
source/_integrations/brunt.markdown @eavanvalkenburg
|
||||
source/_integrations/bsblan.markdown @liudger
|
||||
source/_integrations/bt_smarthub.markdown @jxwolstenholme
|
||||
source/_integrations/bthome.markdown @Ernst79
|
||||
source/_integrations/buienradar.markdown @mjj4791 @ties @Robbie1221
|
||||
source/_integrations/button.markdown @home-assistant/core
|
||||
source/_integrations/calendar.markdown @home-assistant/core
|
||||
@ -150,7 +153,8 @@ source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @Hu
|
||||
source/_integrations/dynalite.markdown @ziv1234
|
||||
source/_integrations/ecobee.markdown @marthoc
|
||||
source/_integrations/econet.markdown @vangorra @w1ll1am23
|
||||
source/_integrations/ecovacs.markdown @OverloadUT
|
||||
source/_integrations/ecovacs.markdown @OverloadUT @mib1185
|
||||
source/_integrations/ecowitt.markdown @pvizeli
|
||||
source/_integrations/edl21.markdown @mtdcr
|
||||
source/_integrations/efergy.markdown @tkdrob
|
||||
source/_integrations/egardia.markdown @jeroenterheerdt
|
||||
@ -175,6 +179,7 @@ source/_integrations/ephember.markdown @ttroy50
|
||||
source/_integrations/epson.markdown @pszafer
|
||||
source/_integrations/epsonworkforce.markdown @ThaStealth
|
||||
source/_integrations/eq3btsmart.markdown @rytilahti
|
||||
source/_integrations/escea.markdown @lazdavila
|
||||
source/_integrations/esphome.markdown @OttoWinter @jesserockz
|
||||
source/_integrations/evil_genius_labs.markdown @balloob
|
||||
source/_integrations/evohome.markdown @zxdavb
|
||||
@ -194,7 +199,7 @@ source/_integrations/flexom.markdown @imicknl @vlebourl @tetienne
|
||||
source/_integrations/flick_electric.markdown @ZephireNZ
|
||||
source/_integrations/flipr.markdown @cnico
|
||||
source/_integrations/flo.markdown @dmulcahey
|
||||
source/_integrations/flume.markdown @ChrisMandich @bdraco
|
||||
source/_integrations/flume.markdown @ChrisMandich @bdraco @jeeftor
|
||||
source/_integrations/flunearyou.markdown @bachya
|
||||
source/_integrations/flux_led.markdown @icemanch @bdraco
|
||||
source/_integrations/forecast_solar.markdown @klaasnicolaas @frenck
|
||||
@ -209,6 +214,7 @@ source/_integrations/fritzbox_callmonitor.markdown @cdce8p
|
||||
source/_integrations/fronius.markdown @nielstron @farmio
|
||||
source/_integrations/frontend.markdown @home-assistant/frontend
|
||||
source/_integrations/frontier_silicon.markdown @wlcrs
|
||||
source/_integrations/fully_kiosk.markdown @cgarwood
|
||||
source/_integrations/garages_amsterdam.markdown @klaasnicolaas
|
||||
source/_integrations/gaviota.markdown @starkillerOG
|
||||
source/_integrations/gdacs.markdown @exxamalte
|
||||
@ -241,6 +247,7 @@ source/_integrations/guardian.markdown @bachya
|
||||
source/_integrations/habitica.markdown @ASMfreaK @leikoilja
|
||||
source/_integrations/harmony.markdown @ehendrix23 @bramkragten @bdraco @mkeesey @Aohzan
|
||||
source/_integrations/hassio.markdown @home-assistant/supervisor
|
||||
source/_integrations/hdmi_cec.markdown @inytar
|
||||
source/_integrations/heatmiser.markdown @andylockran
|
||||
source/_integrations/heos.markdown @andrewsayre
|
||||
source/_integrations/here_travel_time.markdown @eifinger
|
||||
@ -304,6 +311,7 @@ source/_integrations/izone.markdown @Swamp-Ig
|
||||
source/_integrations/jellyfin.markdown @j-stienstra
|
||||
source/_integrations/jewish_calendar.markdown @tsvi
|
||||
source/_integrations/juicenet.markdown @jesserockz
|
||||
source/_integrations/justnimbus.markdown @kvanzuijlen
|
||||
source/_integrations/kaiterra.markdown @Michsior14
|
||||
source/_integrations/kaleidescape.markdown @SteveEasley
|
||||
source/_integrations/keba.markdown @dannerph
|
||||
@ -317,10 +325,13 @@ source/_integrations/konnected.markdown @heythisisnate
|
||||
source/_integrations/kostal_plenticore.markdown @stegm
|
||||
source/_integrations/kraken.markdown @eifinger
|
||||
source/_integrations/kulersky.markdown @emlove
|
||||
source/_integrations/lacrosse_view.markdown @IceBotYT
|
||||
source/_integrations/lametric.markdown @robbiet480 @frenck
|
||||
source/_integrations/landisgyr_heat_meter.markdown @vpathuis
|
||||
source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol
|
||||
source/_integrations/laundrify.markdown @xLarry
|
||||
source/_integrations/lcn.markdown @alengwenus
|
||||
source/_integrations/led_ble.markdown @bdraco
|
||||
source/_integrations/leviton_z_wave.markdown @home-assistant/z-wave
|
||||
source/_integrations/lg_netcast.markdown @Drafteed
|
||||
source/_integrations/life360.markdown @pnbruckner
|
||||
@ -328,7 +339,7 @@ source/_integrations/lifx.markdown @bdraco @Djelibeybi
|
||||
source/_integrations/light.markdown @home-assistant/core
|
||||
source/_integrations/linux_battery.markdown @fabaff
|
||||
source/_integrations/litejet.markdown @joncar
|
||||
source/_integrations/litterrobot.markdown @natekspencer
|
||||
source/_integrations/litterrobot.markdown @natekspencer @tkdrob
|
||||
source/_integrations/local_ip.markdown @issacg
|
||||
source/_integrations/lock.markdown @home-assistant/core
|
||||
source/_integrations/logbook.markdown @home-assistant/core
|
||||
@ -339,7 +350,7 @@ source/_integrations/luci.markdown @mzdrale
|
||||
source/_integrations/luftdaten.markdown @fabaff @frenck
|
||||
source/_integrations/lupusec.markdown @majuss
|
||||
source/_integrations/lutron.markdown @JonGilmore
|
||||
source/_integrations/lutron_caseta.markdown @swails @bdraco
|
||||
source/_integrations/lutron_caseta.markdown @swails @bdraco @danaues
|
||||
source/_integrations/luxaflex.markdown @bdraco @kingy444 @trullock
|
||||
source/_integrations/lyric.markdown @timmo001
|
||||
source/_integrations/marantz.markdown @ol-iver @starkillerOG
|
||||
@ -353,6 +364,7 @@ source/_integrations/media_source.markdown @hunterjm
|
||||
source/_integrations/mediaroom.markdown @dgomes
|
||||
source/_integrations/melcloud.markdown @vilppuvuorinen
|
||||
source/_integrations/melissa.markdown @kennedyshead
|
||||
source/_integrations/melnor.markdown @vanstinator
|
||||
source/_integrations/met.markdown @danielhiversen @thimic
|
||||
source/_integrations/met_eireann.markdown @DylanGore
|
||||
source/_integrations/meteo_france.markdown @hacf-fr @oncleben31 @Quentame
|
||||
@ -414,6 +426,7 @@ source/_integrations/nuki.markdown @pschmitt @pvizeli @pree
|
||||
source/_integrations/numato.markdown @clssn
|
||||
source/_integrations/number.markdown @home-assistant/core @Shulyaka
|
||||
source/_integrations/nut.markdown @bdraco @ollo69
|
||||
source/_integrations/nutrichef.markdown @bdraco
|
||||
source/_integrations/nws.markdown @MatthewFlamm
|
||||
source/_integrations/nzbget.markdown @chriscla
|
||||
source/_integrations/obihai.markdown @dshokouhi
|
||||
@ -428,6 +441,7 @@ source/_integrations/onewire.markdown @garbled1 @epenet
|
||||
source/_integrations/onvif.markdown @hunterjm
|
||||
source/_integrations/open_meteo.markdown @frenck
|
||||
source/_integrations/openerz.markdown @misialq
|
||||
source/_integrations/openexchangerates.markdown @MartinHjelmare
|
||||
source/_integrations/opengarage.markdown @danielhiversen
|
||||
source/_integrations/openhome.markdown @bazwilliams
|
||||
source/_integrations/opentherm_gw.markdown @mvn23
|
||||
@ -458,12 +472,15 @@ source/_integrations/progettihwsw.markdown @ardaseremet
|
||||
source/_integrations/prometheus.markdown @knyar
|
||||
source/_integrations/prosegur.markdown @dgomes
|
||||
source/_integrations/proxmoxve.markdown @jhollowe @Corbeno
|
||||
source/_integrations/prusalink.markdown @balloob
|
||||
source/_integrations/ps4.markdown @ktnrg45
|
||||
source/_integrations/pure_energie.markdown @klaasnicolaas
|
||||
source/_integrations/push.markdown @dgomes
|
||||
source/_integrations/pushover.markdown @engrbm87
|
||||
source/_integrations/pvoutput.markdown @frenck
|
||||
source/_integrations/pvpc_hourly_pricing.markdown @azogue
|
||||
source/_integrations/qbittorrent.markdown @geoffreylagaisse
|
||||
source/_integrations/qingping.markdown @bdraco
|
||||
source/_integrations/qld_bushfire.markdown @exxamalte
|
||||
source/_integrations/qnap_qsw.markdown @Noltari
|
||||
source/_integrations/quantum_gateway.markdown @cisasteelersfan
|
||||
@ -507,6 +524,7 @@ source/_integrations/safe_mode.markdown @home-assistant/core
|
||||
source/_integrations/saj.markdown @fredericvl
|
||||
source/_integrations/samsungtv.markdown @chemelli74 @epenet
|
||||
source/_integrations/scene.markdown @home-assistant/core
|
||||
source/_integrations/schedule.markdown @home-assistant/core
|
||||
source/_integrations/schluter.markdown @prairieapps
|
||||
source/_integrations/scrape.markdown @fabaff
|
||||
source/_integrations/screenlogic.markdown @dieselrabbit @bdraco
|
||||
@ -518,6 +536,8 @@ source/_integrations/sense.markdown @kbickar
|
||||
source/_integrations/senseme.markdown @mikelawrence @bdraco
|
||||
source/_integrations/sensibo.markdown @andrey-git @gjohansson-ST
|
||||
source/_integrations/sensor.markdown @home-assistant/core
|
||||
source/_integrations/sensorblue.markdown @bdraco
|
||||
source/_integrations/sensorpro.markdown @bdraco
|
||||
source/_integrations/sensorpush.markdown @bdraco
|
||||
source/_integrations/sentry.markdown @dcramer @frenck
|
||||
source/_integrations/senz.markdown @milanmeu
|
||||
@ -586,7 +606,7 @@ source/_integrations/swiss_hydrological_data.markdown @fabaff
|
||||
source/_integrations/swiss_public_transport.markdown @fabaff
|
||||
source/_integrations/switch.markdown @home-assistant/core
|
||||
source/_integrations/switch_as_x.markdown @home-assistant/core
|
||||
source/_integrations/switchbot.markdown @bdraco @danielhiversen @RenierM26 @murtas
|
||||
source/_integrations/switchbot.markdown @bdraco @danielhiversen @RenierM26 @murtas @Eloston
|
||||
source/_integrations/switcher_kis.markdown @tomerfi @thecode
|
||||
source/_integrations/switchmate.markdown @danielhiversen @qiz-li
|
||||
source/_integrations/syncthing.markdown @zhulik
|
||||
@ -605,6 +625,9 @@ source/_integrations/tellduslive.markdown @fredrike
|
||||
source/_integrations/template.markdown @PhracturedBlue @tetienne @home-assistant/core
|
||||
source/_integrations/tesla_wall_connector.markdown @einarhauks
|
||||
source/_integrations/tfiac.markdown @fredrike @mellado
|
||||
source/_integrations/thermobeacon.markdown @bdraco
|
||||
source/_integrations/thermoplus.markdown @bdraco
|
||||
source/_integrations/thermopro.markdown @bdraco
|
||||
source/_integrations/thethingsnetwork.markdown @fabaff
|
||||
source/_integrations/threshold.markdown @fabaff
|
||||
source/_integrations/tibber.markdown @danielhiversen
|
||||
@ -656,7 +679,7 @@ source/_integrations/vivotek.markdown @HarlemSquirrel
|
||||
source/_integrations/vizio.markdown @raman325
|
||||
source/_integrations/vlc_telnet.markdown @rodripf @MartinHjelmare
|
||||
source/_integrations/volumio.markdown @OnFreund
|
||||
source/_integrations/volvooncall.markdown @molobrakos @decompil3d
|
||||
source/_integrations/volvooncall.markdown @molobrakos
|
||||
source/_integrations/vulcan.markdown @Antoni-Czaplicki
|
||||
source/_integrations/wake_on_lan.markdown @ntilley905
|
||||
source/_integrations/wallbox.markdown @hesselonline
|
||||
@ -690,6 +713,7 @@ source/_integrations/xiaomi_miio.markdown @rytilahti @syssi @starkillerOG @bieni
|
||||
source/_integrations/xiaomi_tv.markdown @simse
|
||||
source/_integrations/xmpp.markdown @fabaff @flowolf
|
||||
source/_integrations/yale_smart_alarm.markdown @gjohansson-ST
|
||||
source/_integrations/yalexs_ble.markdown @bdraco
|
||||
source/_integrations/yamaha_musiccast.markdown @vigonotion @micha91
|
||||
source/_integrations/yandex_transport.markdown @rishatik92 @devbis
|
||||
source/_integrations/yeelight.markdown @zewelor @shenxn @starkillerOG @alexyao2015
|
||||
|
||||
@ -83,7 +83,7 @@ GEM
|
||||
rack-protection (2.2.2)
|
||||
rack
|
||||
rake (13.0.6)
|
||||
rb-fsevent (0.11.1)
|
||||
rb-fsevent (0.11.2)
|
||||
rb-inotify (0.10.1)
|
||||
ffi (~> 1.0)
|
||||
rexml (3.2.5)
|
||||
|
||||
@ -106,9 +106,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 2022
|
||||
current_minor_version: 8
|
||||
current_patch_version: 7
|
||||
date_released: 2022-08-25
|
||||
current_minor_version: 9
|
||||
current_patch_version: 5
|
||||
date_released: 2022-09-18
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -346,6 +346,11 @@ automation:
|
||||
from: "not_home"
|
||||
# Optional
|
||||
to: "home"
|
||||
# If given, will trigger when the condition has been true for X time; you can also use days and milliseconds.
|
||||
for:
|
||||
hours: 0
|
||||
minutes: 1
|
||||
seconds: 0
|
||||
```
|
||||
|
||||
It's possible to give a list of `from` states or `to` states:
|
||||
|
||||
@ -9,14 +9,20 @@ If you're looking on how to use blueprints, see the [automation documentation](/
|
||||
|
||||
</div>
|
||||
|
||||
An automation blueprint is an automation configuration with certain parts marked as configurable. This allows users to create multiple automations based on the same blueprint, with each having its own configuration.
|
||||
<div class='note'>
|
||||
|
||||
While the tutorial only shows how to create an automation blueprint, scripts also support blueprints in the same way.
|
||||
|
||||
</div>
|
||||
|
||||
A blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration.
|
||||
|
||||
Imagine a blueprint that controls a light based on motion, that allows you to configure the motion sensor to trigger on, and the light to control. It is now possible to create two automations that each have their own configuration for this blueprint and that act completely independent, yet are based on the same automation configuration.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
This is an advanced feature and requires knowledge of writing [automations in YAML](/docs/automation/yaml/).
|
||||
This is an advanced feature and requires knowledge of writing [automations](/docs/automation/yaml/) and [scripts](/docs/scripts/) in YAML.
|
||||
|
||||
</div>
|
||||
|
||||
### [Tutorial: Create a blueprint »](/docs/blueprint/tutorial/)
|
||||
### [Tutorial: Create an automation blueprint »](/docs/blueprint/tutorial/)
|
||||
|
||||
@ -283,7 +283,7 @@ The output of this selector is the number of mired selected, for example, `243`.
|
||||
|
||||
## Config entry selector
|
||||
|
||||
The config entry selector allows to user to select a configured integration
|
||||
The config entry selector allows the user to select an integration
|
||||
configuration entry. The selector returns the entry ID of the selected
|
||||
integration configuration entry.
|
||||
|
||||
|
||||
@ -1,9 +1,15 @@
|
||||
---
|
||||
title: "Blueprint tutorial"
|
||||
description: "Tutorial on creating a blueprint."
|
||||
title: "Automation blueprint tutorial"
|
||||
description: "Tutorial on creating an automation blueprint."
|
||||
---
|
||||
|
||||
In this tutorial, we're going to create a blueprint that controls a light based on a motion sensor. We will do this by taking an existing automation and converting it to a blueprint.
|
||||
<div class='note'>
|
||||
|
||||
While the tutorial only shows how to create an automation blueprint, scripts also support blueprints in the same way.
|
||||
|
||||
</div>
|
||||
|
||||
In this tutorial, we're going to create an automation blueprint that controls a light based on a motion sensor. We will do this by taking an existing automation and converting it to a blueprint.
|
||||
|
||||
For this tutorial, we use a simple automation. The process for converting a complex automation is not any different.
|
||||
|
||||
@ -120,6 +126,7 @@ Blueprints are easier to use if it's easy to see what each field is used for. We
|
||||
```yaml
|
||||
blueprint:
|
||||
name: Motion Light Tutorial
|
||||
description: Turn a light on based on detected motion
|
||||
domain: automation
|
||||
input:
|
||||
motion_sensor:
|
||||
|
||||
@ -87,7 +87,7 @@ If you want to trigger automation on a Home Assistant stop event, we recommend u
|
||||
|
||||
| Field | Description |
|
||||
| ----------- | --------------------------------------------------- |
|
||||
| `name` | Name of the entity. Example: `Litchen light`. |
|
||||
| `name` | Name of the entity. Example: `Kitchen light`. |
|
||||
| `message` | Message. Example: `was turned on` |
|
||||
| `domain` | Optional, domain of the entry. Example: `light` |
|
||||
| `entity_id` | Optional, identifier of the entity that was logged. |
|
||||
|
||||
@ -161,7 +161,7 @@ This (large) sensor configuration gives us another example:
|
||||
- platform: steam_online
|
||||
api_key: ["not telling"]
|
||||
accounts:
|
||||
- 76561198012067051
|
||||
- 76561198012067051
|
||||
|
||||
#### TIME/DATE ##################################
|
||||
- platform: time_date
|
||||
|
||||
@ -59,6 +59,7 @@ They are grouped into the below events:
|
||||
- **abode_panel_restore**: Fired when the panel fault is restored.
|
||||
- **abode_disarm**: Fired when the alarm is disarmed.
|
||||
- **abode_arm**: Fired when the alarm is armed (home or away).
|
||||
- **abode_arm_fault**: Fired when the alarm is armed (home or away) and has a fault. This includes open door/windows, low battery, backup connection. abode_arm is not fired if a fault is present.
|
||||
- **abode_test**: Fired when a sensor is in test mode.
|
||||
- **abode_capture**: Fired when an image is captured.
|
||||
- **abode_device**: Fired for device changes/additions/deletions.
|
||||
|
||||
@ -21,7 +21,24 @@ The AccuWeather integration uses the [AccuWeather](https://accuweather.com/) web
|
||||
|
||||
## Setup
|
||||
|
||||
To generate an AccuWeather API key, go to [AccuWeather APIs](https://developer.accuweather.com/) page, register and create application with product **Limited Trial**.
|
||||
To generate an AccuWeather API key, go to [AccuWeather APIs](https://developer.accuweather.com/) page, register and create application with the following settings:
|
||||
- Products
|
||||
- Core Weather
|
||||
- **Core Weather Limited Trial**
|
||||
- Minute Cast
|
||||
- **None**
|
||||
- Where will the API be used?
|
||||
- **Other**
|
||||
- What will you be creating with this API?
|
||||
- **Internal App**
|
||||
- What programming language is your APP written in?
|
||||
- **Python**
|
||||
- Is this for Business to Business or Business to Consumer use?
|
||||
- **Business to Business**
|
||||
- Is this Worldwide or Country specific use?
|
||||
- **Worldwide**
|
||||
|
||||
You can test your newly created API key [here](https://developer.accuweather.com/accuweather-current-conditions-api/apis)
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Advantage Air
|
||||
description: Instructions on how to integrate Advantage Air A/C controller into Home Assistant.
|
||||
ha_category:
|
||||
- Climate
|
||||
- Update
|
||||
ha_release: 0.117
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
@ -15,9 +16,11 @@ ha_platforms:
|
||||
- climate
|
||||
- cover
|
||||
- diagnostics
|
||||
- light
|
||||
- select
|
||||
- sensor
|
||||
- switch
|
||||
- update
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ alarm_control_panel:
|
||||
- condition: state
|
||||
entity_id: device_tracker.paulus
|
||||
state: "home"
|
||||
- service: alarm_control_panel.alarm_arm_home
|
||||
- service: alarm_control_panel.alarm_disarm
|
||||
target:
|
||||
entity_id: alarm_control_panel.real_alarm
|
||||
data:
|
||||
|
||||
@ -140,7 +140,7 @@ The first thing you need to do after signing into the [AWS console](https://cons
|
||||
<img src='/images/integrations/alexa/create_iam_role_attach_permission.png' alt='Screenshot: Attach permission policy to IAM role'>
|
||||
</p>
|
||||
|
||||
- Give your new role a name, such as `AWSLambdaBasicExecutionRole-SmartHome`, then click the `Create role` button at the bottom of the pahe. You should be able to find your new role in the roles list now.
|
||||
- Give your new role a name, such as `AWSLambdaBasicExecutionRole-SmartHome`, then click the `Create role` button at the bottom of the page. You should be able to find your new role in the roles list now.
|
||||
|
||||
### Add Code to the Lambda Function
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@ aws_secret_access_key:
|
||||
required: true
|
||||
type: string
|
||||
profile_name:
|
||||
description: A credentials profile name.
|
||||
description: A credentials profile name. If provided, you must **not** provide an `aws_access_key_id` nor an `aws_secrete_access_key`.
|
||||
required: false
|
||||
type: string
|
||||
region_name:
|
||||
@ -51,12 +51,12 @@ region_name:
|
||||
type: [string, list]
|
||||
default: us-east-1
|
||||
text_type:
|
||||
description: "Specify wherever to use text (default) or ssml markup by default."
|
||||
description: "Whether to interpret messages as `text` or as [`ssml`](https://docs.aws.amazon.com/polly/latest/dg/ssml.html) by default."
|
||||
required: false
|
||||
type: string
|
||||
default: text
|
||||
voice:
|
||||
description: Voice name to be used.
|
||||
description: The [Voice Name/ID](https://docs.aws.amazon.com/polly/latest/dg/voicelist.html) to be used for generated speech by default.
|
||||
required: false
|
||||
type: string
|
||||
output_format:
|
||||
|
||||
@ -38,6 +38,8 @@ For Fire TV devices, the instructions are as follows:
|
||||
- From the main (Launcher) screen, select Settings.
|
||||
- Select My Fire TV > About > Network.
|
||||
|
||||
If Develper Options is missing from Settings then select My Fire TV and press the button seven times on About.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
{% include integrations/option_flow.md %}
|
||||
|
||||
@ -13,6 +13,8 @@ ha_domain: awair
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_zeroconf: true
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
The Awair integration will fetch data from your [Awair devices](https://getawair.com).
|
||||
|
||||
@ -147,7 +147,7 @@ If you do not download them, you will lose them and will have to recreate a new
|
||||
</div>
|
||||
|
||||
- Copy/Paste the two keys that are shown here in your `configuration.yaml` file.
|
||||
- On the left-hand side of the screen go back to "Users" and select the user you just created. On the "Permissions" tab click the "Attach Policy" icon. Search for "SNS" and attach the policy "AmazonSNSFUullAccess".
|
||||
- On the left-hand side of the screen go back to "Users" and select the user you just created. On the "Permissions" tab click the "Attach Policy" icon. Search for "SNS" and attach the policy "AmazonSNSFullAccess".
|
||||
- Back to the AWS Console you now need to find "SNS" and click in to that service. It is under the Mobile Services group.
|
||||
- On the left-hand side, select "Topics" then "Create new topic".
|
||||
- Choose a Topic Name and Display Name.
|
||||
|
||||
@ -11,6 +11,8 @@ ha_codeowners:
|
||||
- '@bdraco'
|
||||
ha_integration_type: integration
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
---
|
||||
|
||||
The Bluetooth integration will detect nearby Bluetooth devices. Discovered devices will show up in the discovered section on the integrations page in the configuration panel.
|
||||
@ -91,7 +93,7 @@ Integrations that have followed the [Best practices for library authors](https:/
|
||||
|
||||
## Passive Scanning
|
||||
|
||||
Passive Scanning on Linux can be enabled in the options flow per adapter if the host system runs BlueZ 4.63 or later with experimental features enabled.
|
||||
Passive Scanning on Linux can be enabled in the options flow per adapter if the host system runs BlueZ 5.63 or later with experimental features enabled.
|
||||
|
||||
Many integrations require active scanning and may not function when scanning is passive.
|
||||
|
||||
|
||||
@ -71,4 +71,4 @@ The integration allows you to customize the list of ignored sources.
|
||||
|
||||
## For TVs older than 2013
|
||||
|
||||
Users of TVs older than 2013 can control their devices using [HDMI-CEC](/integrations/hdmi_cec/), [Broadlink](/integrations/broadlink/) or [Kodi](/integrations/kodi/) integrations.
|
||||
Users of TVs older than 2013 can control their devices using [HDMI-CEC](/integrations/hdmi_cec/), [Broadlink](/integrations/broadlink/) or [Kodi](/integrations/kodi/) integrations.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: BTHome Bluetooth
|
||||
title: BTHome
|
||||
description: Instructions on how to integrate BTHome BLE devices into Home Assistant.
|
||||
ha_category:
|
||||
- Sensor
|
||||
|
||||
@ -11,7 +11,7 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `clickatell` platform uses [Clickatell](https://clickatell.com) to deliver SMS notifications from Home Assistant.
|
||||
The `clickatell` platform uses [Clickatell](https://www.clickatell.com) to deliver SMS notifications from Home Assistant.
|
||||
|
||||
## Setup
|
||||
|
||||
|
||||
@ -100,11 +100,11 @@ The `daikin` sensor platform integrates Daikin air conditioning systems into Hom
|
||||
- Inside temperature
|
||||
- Outside temperature
|
||||
- Inside humidity
|
||||
- Estimated power consumption
|
||||
- Estimated power consumption (not per device, but sum of installation)
|
||||
- Hourly energy consumption in cool mode
|
||||
- Hourly energy consumption in heat mode
|
||||
- Outside unit's compressor frequency
|
||||
- Today's total energy consumption (resets at 00:00)
|
||||
- Today's total energy consumption (not per device, but sum of installation, resets at 00:00)
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -117,7 +117,7 @@ The `daikin` sensor platform integrates Daikin air conditioning systems into Hom
|
||||
|
||||
<div class='note'>
|
||||
|
||||
- The 'Today's total energy consumption' and 'Estimated power consumption' sensor is updated every time 100 Wh are consumed by all different operating modes summed together.
|
||||
- The 'Today's total energy consumption' and 'Estimated power consumption' sensor is updated every time 100 Wh are consumed by all different operating modes summed together. These values are the values for the whole installation, not per device (unless, you have only one device).
|
||||
- The 'Estimated power consumption' sensor is derived from the energy consumption and not provided by the AC directly.
|
||||
- The 'cool/heat' energy sensors are updated hourly with the previous hour energy consumption
|
||||
of a given mode and a given AC.
|
||||
|
||||
@ -33,6 +33,7 @@ ha_platforms:
|
||||
- lock
|
||||
- number
|
||||
- scene
|
||||
- select
|
||||
- sensor
|
||||
- siren
|
||||
- switch
|
||||
|
||||
@ -38,6 +38,7 @@ This integration is a meta-component and configures a default set of integration
|
||||
- [Mobile App Support](/integrations/mobile_app/) (`mobile_app`)
|
||||
- [My Home Assistant](/integrations/my/) (`my`)
|
||||
- [Person](/integrations/person/) (`person`)
|
||||
- [Schedule](/integrations/schedule/) (`schedule`)
|
||||
- [Scene](/integrations/scene/) (`scene`)
|
||||
- [Scripts](/integrations/script/) (`script`)
|
||||
- [Simple Service Discovery Protocol (SSDP)](/integrations/ssdp/) (`ssdp`)
|
||||
|
||||
@ -3,7 +3,7 @@ title: Demo
|
||||
description: Instructions on how to use the Platform demos with Home Assistant.
|
||||
ha_category:
|
||||
- Other
|
||||
- Updates
|
||||
- Update
|
||||
ha_release: 0.7
|
||||
ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
|
||||
@ -62,6 +62,7 @@ Known supported devices:
|
||||
- Denon AVR-S720W
|
||||
- Denon AVR-S750H
|
||||
- Denon AVR-S760H
|
||||
- Denon AVR-S940H
|
||||
- Denon AVR-S950H
|
||||
- Denon AVR-S960H
|
||||
- Denon DN-500AV
|
||||
|
||||
@ -68,7 +68,7 @@ monitored_conditions:
|
||||
| ------------ | -------------------------------------- |
|
||||
| `last_update` | *(time)* Time and date (UTC) of last update from DWD. |
|
||||
| `region_name` | *(str)* Requested region name. This should be the same as the region name in the configuration if a name was given. |
|
||||
| `region_id` | *(int)* Region ID assigned by DWD. This should be the same as the region name in the configuration if an id was given. |
|
||||
| `region_id` | *(int)* Region ID assigned by DWD. This should be the same as the region id in the configuration if an id was given. |
|
||||
| `warning_count` | *(int)* Number of issued warnings. There can be more than one warning issued at once. |
|
||||
| `warning_<x>` | *(list)* The warning as a whole object containing the following attributes as nested attributes. |
|
||||
| `warning_<x>_level` | *(int)* Issued warning level (0 - 4).<br/>0: Keine Warnungen <br/>1: Wetterwarnungen <br/>2: Warnungen vor markantem Wetter<br/>3: Unwetterwarnungen<br/>4: Warnungen vor extremem Unwetter |
|
||||
|
||||
@ -8,6 +8,7 @@ ha_iot_class: Cloud Push
|
||||
ha_release: 0.77
|
||||
ha_codeowners:
|
||||
- '@OverloadUT'
|
||||
- '@mib1185'
|
||||
ha_domain: ecovacs
|
||||
ha_platforms:
|
||||
- vacuum
|
||||
|
||||
@ -11,7 +11,9 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@pvizeli'
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -25,5 +27,7 @@ The following steps must be performed to set up this integration. For security r
|
||||
2. Pick your station -> Menu Others -> DIY Upload Servers.
|
||||
3. Hit next and select 'Customized'
|
||||
4. Pick the protocol Ecowitt, and put in the ip/hostname of your Home Assistant server.
|
||||
5. Path have to match, you can copy with secure token /.
|
||||
5. Path have to match!
|
||||
6. Save configuration.
|
||||
|
||||
Ecowitt doesn't support TLS/SSL, you can use the NGINX TLS Proxy Add-on to support HTTPS and HTTP at the same time.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_domain: escea
|
||||
ha_homekit: true
|
||||
ha_platforms:
|
||||
- climate
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The Escea integration allows monitoring and control of local [Escea](https://escea.com/) fireplaces. These fireplaces are manufactured in New Zealand and sold throughout Australia and New Zealand.
|
||||
@ -44,4 +45,4 @@ logger:
|
||||
pescea: debug
|
||||
```
|
||||
|
||||
This will help you to find network connection issues etc.
|
||||
This will help you to find network connection issues etc.
|
||||
|
||||
12
source/_integrations/file_upload.markdown
Normal file
12
source/_integrations/file_upload.markdown
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
title: File Upload
|
||||
description: File upload integration supports various frontend features within Home Assistant
|
||||
ha_release: 2022.9
|
||||
ha_quality_scale: internal
|
||||
ha_domain: file_upload
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
---
|
||||
|
||||
The file upload integration allows various features in the frontend to upload files.
|
||||
@ -9,6 +9,7 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@ChrisMandich'
|
||||
- '@bdraco'
|
||||
- '@jeeftor'
|
||||
ha_domain: flume
|
||||
ha_dhcp: true
|
||||
ha_platforms:
|
||||
|
||||
@ -5,7 +5,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Presence Detection
|
||||
- Sensor
|
||||
- Updates
|
||||
- Update
|
||||
ha_release: '0.10'
|
||||
ha_domain: fritz
|
||||
ha_config_flow: true
|
||||
|
||||
@ -15,6 +15,7 @@ ha_ssdp: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- climate
|
||||
- cover
|
||||
- diagnostics
|
||||
- light
|
||||
- sensor
|
||||
|
||||
@ -14,9 +14,13 @@ ha_domain: fully_kiosk
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- diagnostics
|
||||
- media_player
|
||||
- number
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
[Fully Kiosk Browser](https://www.fully-kiosk.com) is a powerful kiosk browser for Android devices. It provides a number of features for monitoring and controlling your Android device. This integration gives you access to control your device and view the status in Home Assistant.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
- '@starkillerOG'
|
||||
ha_domain: goodwe
|
||||
ha_platforms:
|
||||
- button
|
||||
- number
|
||||
- select
|
||||
- sensor
|
||||
|
||||
20
source/_integrations/hardware.markdown
Normal file
20
source/_integrations/hardware.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
title: Hardware
|
||||
ha_category:
|
||||
- Other
|
||||
ha_release: 2022.6
|
||||
ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: hardware
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The Hardware integration provides an API which offers information about certain board types, USB dongles, and resource usage.
|
||||
|
||||
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
hardware:
|
||||
```
|
||||
@ -4,7 +4,7 @@ description: Control Supervisor Add-ons and OS from Home Assistant
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
- Updates
|
||||
- Update
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.42
|
||||
ha_domain: hassio
|
||||
|
||||
@ -10,6 +10,8 @@ ha_platforms:
|
||||
- media_player
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@inytar'
|
||||
---
|
||||
|
||||
The `hdmi_cec` integration provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entities for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as sound-bars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use `cec-client` (part of the `libcec` package) to listen to traffic on the CEC bus and discover the correct numbers.
|
||||
|
||||
@ -18,3 +18,5 @@ ha_integration_type: integration
|
||||
The `ipma` weather platform uses the [Instituto Português do Mar e Atmosfera](https://www.ipma.pt/) as a source for current and forecast meteorological data.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
IPMA provides both *hourly* (72h) and *daily* (10 days) forecasts, but you must choose which one will be exposed by the weather entity during initial setup of the integration.
|
||||
|
||||
@ -10,9 +10,11 @@ ha_platforms:
|
||||
- sensor
|
||||
ha_config_flow: true
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@kvanzuijlen'
|
||||
---
|
||||
|
||||
The JustNimbus integration queries the JustNumbus API used by the JustNimbus web dashboard.
|
||||
The JustNimbus integration queries the JustNimbus API used by the JustNimbus web dashboard.
|
||||
This integration allows you to collect and save data to get an historic overview of your water bag
|
||||
usage.
|
||||
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: "LaCrosse View"
|
||||
description: "Get data for LaCrosse View-connected sensors"
|
||||
ha_release: 2022.9
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_quality_scale: platinum
|
||||
title: LaCrosse View
|
||||
description: Get data for LaCrosse View-connected sensors
|
||||
ha_release: '2022.9'
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@IceBotYT'
|
||||
|
||||
@ -22,6 +22,7 @@ ha_category:
|
||||
- Sensor
|
||||
- Siren
|
||||
- Switch
|
||||
- Update
|
||||
ha_domain: leviton_z_wave
|
||||
ha_integration_type: integration
|
||||
works_with:
|
||||
@ -41,6 +42,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- siren
|
||||
- switch
|
||||
- update
|
||||
ha_zeroconf: true
|
||||
ha_supporting_domain: zwave_js
|
||||
ha_supporting_integration: Z-Wave
|
||||
|
||||
@ -10,6 +10,7 @@ ha_config_flow: true
|
||||
ha_domain: lifx
|
||||
ha_homekit: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- light
|
||||
ha_integration_type: integration
|
||||
|
||||
@ -56,3 +56,7 @@ use is automatically detected when using a username and password.
|
||||
- OctoPrint (OctoPi):
|
||||
- MJPEG URL: `http://IP/webcam/?action=stream`
|
||||
- Still Image URL: `http://IP/webcam/?action=snapshot`
|
||||
|
||||
- Legacy Foscam / wanscam
|
||||
- MJPEG URL: `http://IP:PORT/videostream.cgi` (add ?resultion=32 for 640x480 or ?resultion=32 for 320x240)
|
||||
- Still Image URL: `http://IP:PORT/snapshot.cgi`
|
||||
|
||||
@ -79,7 +79,7 @@ timeout:
|
||||
default: 5
|
||||
type: integer
|
||||
type:
|
||||
description: Type of communication. Possible values are `tcp` Modbus messages with Modbus TCP frame on TCP/IP, `udp` Modbus messages with Modbus TCP frame on UDP, `rtuovertcp` Modbus messages with a wrapper TCP/IP simulating a serial line, 'serial' Modbus serial (RS485).
|
||||
description: Type of communication. Possible values are `tcp` Modbus messages with Modbus TCP frame on TCP/IP, `udp` Modbus messages with Modbus TCP frame on UDP, `rtuovertcp` Modbus messages with a wrapper TCP/IP simulating a serial line, `serial` Modbus serial (RS485).
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -3,7 +3,7 @@ title: NETGEAR
|
||||
description: Instructions on how to integrate NETGEAR routers into Home Assistant.
|
||||
ha_category:
|
||||
- Presence Detection
|
||||
- Updates
|
||||
- Update
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: pre 0.7
|
||||
ha_domain: netgear
|
||||
|
||||
@ -16,6 +16,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
NextDNS is a DNS service that protects from all kinds of security threats, blocks ADS and trackers on websites and in apps, and provides a safe and supervised Internet for kids — on all devices and on all networks. The NextDNS integration allows you to monitor NextDNS statistics and control its configuration.
|
||||
|
||||
@ -63,5 +63,5 @@ show_on_map:
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/nmbs-card-example.png' />
|
||||
<p>Example using the <a href="https://github.com/custom-cards/entity-attributes-card">Lovelace Attributes custom card</a> </p>
|
||||
<p>Example using the <a href="https://github.com/custom-cards/entity-attributes-card">Entity Attributes custom card</a> </p>
|
||||
</p>
|
||||
|
||||
@ -21,6 +21,7 @@ The Oncue by Kohler integration will allow you to monitor the state of your [Onc
|
||||
|
||||
## Tested Devices
|
||||
|
||||
- 20RESA
|
||||
- [24RCL](https://kohlerpower.com/en/residential/generators/product/24rcl)
|
||||
- [38RCLB](https://kohlerpower.com/en/residential/generators/product/38rclb)
|
||||
- [48RCLB](https://kohlerpower.com/en/residential/generators/product/48rclb)
|
||||
|
||||
@ -10,6 +10,8 @@ ha_domain: openexchangerates
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@MartinHjelmare'
|
||||
---
|
||||
|
||||
The Open Exchange Rates integration will show you the current exchange rate from [Open Exchange Rates](https://openexchangerates.org) that provides real-time exchange rates for [170 currencies](https://openexchangerates.org/currencies). The free account is limited to only USD as a base currency, allows 1000 requests per month, and updates every hour.
|
||||
|
||||
@ -30,7 +30,7 @@ You need an API key, which is free, but requires a [registration](https://home.o
|
||||
<div class='note'>
|
||||
If you register an new API key with OpenWeatherMap, it will be activated automatically, this typically takes between 10 minutes and 2 hours
|
||||
after your successful registration. Keep in mind when configuring this integration, that you new API key might
|
||||
not be activated yet.
|
||||
not be activated yet. Recent policy changes limit the API access for new registered users with a free plan, they should select the `hourly` mode. The other modes require a paid subscription plan. Invalid API-key errors might occur if your API key is used with the other modes.
|
||||
</div>
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -52,16 +52,14 @@ The Overkiz (by Somfy) integration platform is used by many different vendors, l
|
||||
- Hitachi Hi Kumo
|
||||
- Nexity Eugénie
|
||||
- Rexel Energeasy Connect
|
||||
- Somfy Connectivity Kit
|
||||
- Somfy Connexoon IO
|
||||
- Somfy Connexoon RTS
|
||||
- Somfy TaHoma
|
||||
- Somfy TaHoma Switch [(instructions)](#tahoma-switch)
|
||||
- Somfy Connection Kit
|
||||
- Somfy TaHoma Beecon
|
||||
- Somfy TaHoma Switch
|
||||
- Thermor Cozytouch
|
||||
|
||||
### TaHoma Switch
|
||||
|
||||
Multiple users reported that the TaHoma Switch will work with this integration **after** you create a scene in the TaHoma app and wait for a few hours.
|
||||
|
||||
## Supported devices
|
||||
|
||||
@ -83,8 +81,10 @@ During peak hours, it could happen that the Overkiz platform is unable to execut
|
||||
|
||||
### Internet connectivity required
|
||||
|
||||
This integration communicates via the cloud-based Overkiz API, since Overkiz doesn't expose a local API on their hubs. If you are only using Somfy IO compatible devices, you could purchase a Velux KLF200 hub and use [the Velux integration](/integrations/velux/) which has a local API.
|
||||
This integration communicates via the cloud-based Overkiz API. The Somfy TaHoma v2 and the Somfy TaHoma Switch offer the [Somfy TaHoma Developer Mode (local API)](https://developer.somfy.com/developer-mode), which is not supported in Home Assistant yet.
|
||||
|
||||
Another option if you are only using Somfy IO compatible devices is to purchase a Velux KLF200 hub and use [the Velux integration](/integrations/velux/) which has a local API.
|
||||
|
||||
#### Local API via HomeKit Controller
|
||||
|
||||
If your hub (e.g. Somfy TaHoma or Somfy Connection Kit) supports HomeKit natively, your setup code will be added as a sensor in Home Assistant. Look up your hub in Home Assistant and retrieve the value from the 'HomeKit Setup Code' sensor. You can now configure the [HomeKit Controller](/integrations/homekit_controller/) integration in Home Assistant and benefit from local support.
|
||||
If your hub (e.g. Somfy TaHoma) supports HomeKit natively, your setup code will be added as a sensor in Home Assistant. Look up your hub in Home Assistant and retrieve the value from the 'HomeKit Setup Code' sensor. You can now configure the [HomeKit Controller](/integrations/homekit_controller/) integration in Home Assistant and benefit from local support. Only a [limited amount of devices is supported](https://service.somfy.com/downloads/nl_v5/tahoma-homekitcompatibilitylist_eng.pdf).
|
||||
|
||||
@ -22,6 +22,10 @@ Currently known supported models:
|
||||
- DMP-BDT500
|
||||
- DMP-BBT01
|
||||
|
||||
Models reported not working:
|
||||
|
||||
- DP-UB420
|
||||
|
||||
If your model is not on the list, then give it a try, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/panasonic_bluray.markdown).
|
||||
|
||||
Example configuration:
|
||||
|
||||
@ -5,7 +5,7 @@ ha_category:
|
||||
- Sensor
|
||||
- Switch
|
||||
- System Monitor
|
||||
- Updates
|
||||
- Update
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_release: 0.28
|
||||
|
||||
@ -177,3 +177,31 @@ sources:
|
||||
'Favorites': '45'
|
||||
'Game': '49'
|
||||
```
|
||||
|
||||
#### VSX-1021
|
||||
|
||||
```yaml
|
||||
port: 8102
|
||||
sources:
|
||||
'Phono': '00'
|
||||
'CD': '01'
|
||||
'Tuner': '02'
|
||||
'CD-R/Tape': '03'
|
||||
'DVD': '04'
|
||||
'TV/Sat': '05'
|
||||
'Video 1': '10'
|
||||
'Multi Channel In': '12'
|
||||
'Video 2': '14'
|
||||
'DVR/BDR': '15'
|
||||
'iPod/USB': '17'
|
||||
'XM Radio': '18'
|
||||
'HDMI 1': '19'
|
||||
'HDMI 2': '20'
|
||||
'HDMI 3': '21'
|
||||
'HDMI 4': '22'
|
||||
'HDMI 5': '23'
|
||||
'Blu-Ray': '25'
|
||||
'Home Media Gallery (Internet Radio)': '26'
|
||||
'Sirius': '27'
|
||||
'Adapter Port': '33'
|
||||
```
|
||||
|
||||
@ -10,6 +10,10 @@ ha_codeowners:
|
||||
- '@balloob'
|
||||
ha_domain: prusalink
|
||||
ha_integration_type: integration
|
||||
ha_platforms:
|
||||
- camera
|
||||
- sensor
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
The PrusaLink integration allows you to monitor your [Prusa 3D printer](https://www.prusa3d.com) and its progress with your Home Assistant installation.
|
||||
|
||||
@ -10,6 +10,7 @@ ha_codeowners:
|
||||
- '@klaasnicolaas'
|
||||
ha_domain: pure_energie
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_quality_scale: platinum
|
||||
ha_zeroconf: true
|
||||
|
||||
@ -6,7 +6,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Button
|
||||
- Sensor
|
||||
- Updates
|
||||
- Update
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_domain: qnap_qsw
|
||||
|
||||
@ -4,7 +4,6 @@ description: Home Assistant Repairs informs you about issues it has found in you
|
||||
ha_release: 2022.8
|
||||
ha_category:
|
||||
- Other
|
||||
ha_iot_class: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: repairs
|
||||
|
||||
@ -15,6 +15,6 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `rpi_power` integration allows you to detect [bad power supply](https://www.raspberrypi.org/documentation/hardware/raspberrypi/power/README.md) on Raspberry Pi.
|
||||
The `rpi_power` integration allows you to detect [bad power supply](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#power-supply-warnings) on Raspberry Pi.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -10,7 +10,7 @@ ha_category:
|
||||
- Select
|
||||
- Sensor
|
||||
- Switch
|
||||
- Updates
|
||||
- Update
|
||||
ha_release: 0.44
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
|
||||
@ -47,6 +47,10 @@ SimpliSafe offers several [monitoring plans](https://support.simplisafe.com/hc/e
|
||||
|
||||
## Getting an Authorization Code
|
||||
|
||||
<div class='note warning'>
|
||||
You must have multi-factor authentication (MFA) enabled on your SimpliSafe account for the below instructions to work. Without MFA enabled, you will never receive the correct authorization code!
|
||||
</div>
|
||||
|
||||
SimpliSafe authenticates users via its web app. Due to technical limitations, there is a manual step when adding the integration. For in-depth guidance, refer to step 6 of [the `simplisafe-python` documentation on authentication](https://simplisafe-python.readthedocs.io/en/latest/usage.html#authentication).
|
||||
|
||||
## Services
|
||||
|
||||
@ -121,7 +121,6 @@ You will need a USB GSM stick modem or device like SIM800L v2 connected via USB
|
||||
Need to unlock it using [this guide](http://blog.asiantuntijakaveri.fi/2015/07/convert-huawei-e3372h-153-from.html))
|
||||
- [Huawei E3531](https://www.amazon.com/Modem-Huawei-Unlocked-Caribbean-Desbloqueado/dp/B011YZZ6Q2/ref=sr_1_1?keywords=Huawei+E3531&qid=1581447800&sr=8-1)
|
||||
- [Huawei E3272](https://www.amazon.com/Huawei-E3272s-506-Unlocked-Americas-Europe/dp/B00HBL51OQ)
|
||||
- [SIM800C](https://www.amazon.com/gp/product/B087Z6F953/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1)
|
||||
- ZTE K3565-Z
|
||||
|
||||
### List of modems known to NOT work
|
||||
|
||||
@ -69,7 +69,18 @@ The microphone can only be enabled/disabled from physical buttons on the Sonos d
|
||||
|
||||
The favorites sensor provides the names and `media_content_id` values for each of the favorites saved to My Sonos in the native Sonos app. This sensor is intended for users that need to access the favorites in a custom template. For most users, accessing favorites by using the Media Browser functionality and "Play media" script/automation action is recommended.
|
||||
|
||||
If using the provided `media_content_id` with the `media_player.play_media` service, the `media_content_type` must be set to "favorite_item_id".
|
||||
When calling the `media_player.play_media` service, the `media_content_type` must be set to "favorite_item_id" and the `media_content_id` must be set to just the key portion of the favorite item.
|
||||
|
||||
Example service call:
|
||||
|
||||
```yaml
|
||||
service: media_player.play_media
|
||||
target:
|
||||
entity_id: media_player.sonos_speaker1
|
||||
data:
|
||||
media_content_type: "favorite_item_id"
|
||||
media_content_id: "FV:2/31"
|
||||
```
|
||||
|
||||
Example templates:
|
||||
|
||||
|
||||
@ -18,7 +18,6 @@ ha_integration_type: integration
|
||||
|
||||
The Speedtest.net integration uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance.
|
||||
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
Most Speedtest.net servers require TCP port 8080 outbound to function. Without this port open you may experience significant delays or no results at all. See note on their [help page](https://www.speedtest.net/help).
|
||||
@ -34,15 +33,6 @@ sensors:
|
||||
- Ping sensor: Reaction time in ms of your connection (how fast you get a response after you’ve sent out a request).
|
||||
- Download sensor: The download speed (Mbit/s).
|
||||
- Upload sensor: The upload speed (Mbit/s).
|
||||
|
||||
### Service
|
||||
|
||||
Once loaded, the integration will expose a service (`speedtestdotnet.speedtest`) that can be called to run a Speedtest.net speed test on demand. This service takes no parameters. This can be useful when auto update has been disabled in the integration options.
|
||||
|
||||
```yaml
|
||||
action:
|
||||
service: speedtestdotnet.speedtest
|
||||
```
|
||||
|
||||
This integration uses [speedtest-cli](https://github.com/sivel/speedtest-cli) to gather network performance data from Speedtest.net.
|
||||
Please be aware of the potential [inconsistencies](https://github.com/sivel/speedtest-cli#inconsistency) that this integration may display.
|
||||
|
||||
@ -48,4 +48,4 @@ Type:
|
||||
|
||||
Where compatible, Switch as X will appear on entity properties. A list of entities can be found in {% my entities title="Settings -> Devices & Services -> Entities" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -14,6 +14,7 @@ ha_codeowners:
|
||||
- '@danielhiversen'
|
||||
- '@RenierM26'
|
||||
- '@murtas'
|
||||
- '@Eloston'
|
||||
ha_domain: switchbot
|
||||
ha_bluetooth: true
|
||||
ha_platforms:
|
||||
|
||||
@ -4,7 +4,7 @@ description: Instructions on how to integrate the Synology DSM sensor within Hom
|
||||
ha_category:
|
||||
- Camera
|
||||
- System Monitor
|
||||
- Updates
|
||||
- Update
|
||||
ha_release: 0.32
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: synology_dsm
|
||||
|
||||
@ -411,7 +411,7 @@ template:
|
||||
|
||||
{% endraw %}
|
||||
|
||||
### State based sensor modyfying another sensor's output
|
||||
### State based sensor modifying another sensor's output
|
||||
|
||||
If you don't like the wording of a sensor output, then the Template Sensor can help too. Let's rename the output of the [Sun component](/integrations/sun/) as a simple example:
|
||||
|
||||
|
||||
@ -21,6 +21,8 @@ Integrates [ThermoPro](https://buythermopro.com/) devices into Home Assistant.
|
||||
|
||||
- [TP359](https://buythermopro.com/product/thermopro-tp59-bluetooth-wireless-thermometer-hygrometer-humidity-monitor/)
|
||||
- [TP357](https://buythermopro.com/product/thermopro-tp357-bluetooth-digital-indoor-hygrometer-thermometer/)
|
||||
- [TP358](https://buythermopro.com/product/tp358/)
|
||||
- [TP393](https://buythermopro.com/product/tp393/)
|
||||
|
||||
The ThermoPro integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Time & Date
|
||||
description: Instructions on how to integrate the time and the date within Home Assistant.
|
||||
description: Instructions on how to create time and the date sensors within Home Assistant.
|
||||
ha_category:
|
||||
- Calendar
|
||||
ha_iot_class: Local Push
|
||||
@ -14,7 +14,7 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The time and date (`time_date`) integration allows one to show the current date or time in different formats. All values are based on the timezone which is set in "General Configuration".
|
||||
The time and date (`time_date`) integration allows one to create sensors for the current date or time in different formats. All values are based on the timezone which is set in "General Configuration".
|
||||
|
||||
To have these sensors available in your installation, add the following to your `configuration.yaml` file (each option creates a separate sensor that contains appropriate data, e.g., `sensor.date` for the `date` option):
|
||||
|
||||
@ -36,7 +36,7 @@ sensor:
|
||||
|
||||
{% configuration %}
|
||||
display_options:
|
||||
description: The option to display. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](https://en.wikipedia.org/wiki/Swatch_Internet_Time).
|
||||
description: The sensors to create. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* create combined date and the time sensors. The other types just the time sensor or the date sensor. *beat* creates the [Swatch Internet Time](https://en.wikipedia.org/wiki/Swatch_Internet_Time).
|
||||
required: true
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
@ -50,8 +50,6 @@ Sensors including the time update every minute, the date sensor updates each day
|
||||
|
||||
# Producing your own custom time and date sensor
|
||||
|
||||
Whilst there are a number of `display_options` exposed by this sensor, they cannot hope to satisfy everyone, and large parts of the world will find that their local display conventions are not included.
|
||||
|
||||
The following can be used to create a time and date sensor whose output can be properly customised to use your own preferred formatting, specified in the call to timestamp_custom() using standard [Python datetime formatting](https://docs.python.org/3.8/library/datetime.html#strftime-and-strptime-behavior).
|
||||
|
||||
{% raw %}
|
||||
|
||||
@ -6,7 +6,7 @@ ha_category:
|
||||
- Presence Detection
|
||||
- Sensor
|
||||
- Switch
|
||||
- Updates
|
||||
- Update
|
||||
ha_release: 0.81
|
||||
ha_iot_class: Local Push
|
||||
ha_config_flow: true
|
||||
|
||||
@ -14,8 +14,8 @@ ha_platforms:
|
||||
- switch
|
||||
ha_codeowners:
|
||||
- '@molobrakos'
|
||||
- '@decompil3d'
|
||||
ha_integration_type: integration
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The `volvooncall` integration offers integration with the [Volvo On Call](https://www.volvocars.com/intl/why-volvo/human-innovation/future-of-driving/connectivity/volvo-on-call) cloud service and offers presence detection as well as sensors such as odometer and fuel level.
|
||||
|
||||
@ -30,7 +30,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Binary Sensor
|
||||
- Fan (Belkin WeMo (Holmes) Smart Humidifier)
|
||||
- Light (Belkin WeMo LED lights and [Smart Dimmer Switch](https://www.belkin.com/smart-home/wemo/wemo-wifi-smart-dimmer/p/p-wds060/))
|
||||
- Light (Belkin WeMo LED lights and Smart Dimmer Switch)
|
||||
- Switch ([Belkin WeMo Switches](https://www.belkin.com/us/smart-home/c/wemo/) and includes support for WeMo enabled [Mr. Coffee](https://www.mrcoffee.com/) smart coffee makers.)
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -5,7 +5,7 @@ ha_category:
|
||||
- Light
|
||||
- Sensor
|
||||
- Switch
|
||||
- Updates
|
||||
- Update
|
||||
ha_release: 0.102
|
||||
ha_iot_class: Local Push
|
||||
ha_config_flow: true
|
||||
|
||||
@ -165,9 +165,3 @@ automation:
|
||||
target:
|
||||
entity_id: switch.heater
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
|
||||
Please remember that [as explained here](/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations.
|
||||
|
||||
</div>
|
||||
|
||||
@ -33,7 +33,7 @@ It is possible that we detect your device because it uses the MiBeacon protocol
|
||||
- Moisture
|
||||
- Illumination
|
||||
- Conductivity
|
||||
- Formalehyde
|
||||
- Formaldehyde
|
||||
- Consumable
|
||||
- Voltage
|
||||
- Battery
|
||||
|
||||
@ -37,16 +37,17 @@ If you want to use separate credentials, please contact <service@yosmart.com> to
|
||||
|
||||
The integration is tested and verified for the following devices from YoLink:
|
||||
|
||||
* YS6602/4 (outlet | plug)
|
||||
* YS6602/4 YS6704 (outlet | plug)
|
||||
* YS7103/4/5 (siren)
|
||||
* YS7704 (door sensor)
|
||||
* YS7707 (Contact Sensor)
|
||||
* YS7804/5 (motion sensor)
|
||||
* YS7903/4 (leak sensor)
|
||||
* YS8003 (temperature/humidity sensor)
|
||||
* YS8003/4/5/6 (temperature/humidity sensor)
|
||||
* YS7201 (vibration sensor)
|
||||
* YS7607 (lock)
|
||||
* YS4909 (valve controller)
|
||||
* YS5705 (switch)
|
||||
* YS7A01 (CO & Smoke Sensor)
|
||||
* YS4002 (Thermostat)
|
||||
* YS4906/YS7706 (Garage Door Sensor/ Garage Door Controller)
|
||||
* YS7606/7 (lock)
|
||||
* YS4909 YS5001 (valve controller)
|
||||
* YS5705/6 (switch)
|
||||
* YS7A01/2 (CO & Smoke Sensor)
|
||||
* YS4002/3 (Thermostat)
|
||||
* YS4906/8 YS7706 (Garage Door Sensor/ Garage Door Controller)
|
||||
|
||||
@ -404,6 +404,14 @@ Note that not all devices support binding as it depends on the Zigbee implementa
|
||||
|
||||
Binding a remote directly to a bulb or group has the benefit of faster response time and smoother control. This greatly improves user feedback experience functions like dimming as the remote then directly dims the lightbulb and thus does not have to make the software roundtrip via the ZHA coordinator.
|
||||
|
||||
## Zigbee backup and restore in ZHA
|
||||
|
||||
Zigbee Home Automation (ZHA) integration now features Zigbee network backup, restore/recovery, and migrating between Zigbee coordinators. Backups are taken automatically however, a single backup to a file for easy download can also be manually created from the configuration page under Network Settings.
|
||||
|
||||
After restoring a Home Assistant backup, you can re-configure ZHA and migrate to a new Zigbee Coordinator adapter without any loss of your settings or devices that were connected. This is helpful if your current radio fails or a new radio adapter type and model comes out that you may want to migrate to.
|
||||
|
||||
Within ZHA is possible to use this backup and restore feature to migrate between some different radio types, if the respective radio library supports it. Currently, ZHA supports migrating the Zigbee network between different Zigbee Coordinator adapters based on chips from Silicon Labs, Texas Instruments, or ConBee/RaspBee if the backup was made from inside ZHA.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
To help resolve any kinks or compatibility problems, report bugs as issues with debug logs. Please follow the instructions in this troubleshooting section.
|
||||
|
||||
@ -17,7 +17,7 @@ ha_category:
|
||||
- Sensor
|
||||
- Siren
|
||||
- Switch
|
||||
- Updates
|
||||
- Update
|
||||
ha_release: '2021.2'
|
||||
ha_iot_class: Local Push
|
||||
ha_config_flow: true
|
||||
@ -717,9 +717,9 @@ Some Z-Wave USB sticks can be auto-discovered, which can simplify the Z-Wave set
|
||||
|
||||
| Device | Identifier | Vendor |
|
||||
| -------| ---------- | ------ |
|
||||
| Aeotec Z-Stick Gen5+ | 0658:0200 | https://aeotec.com/z-wave-usb-stick/ |
|
||||
| Aeotec Z-Stick Gen5+ | 0658:0200 | https://aeotec.com/products/aeotec-z-stick-gen5/ |
|
||||
| Nortek HUSBZB-1 | 10C4:8A2A | https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/ |
|
||||
| Zooz ZST10 | 10C4:EA60 | https://www.getzooz.com/zooz-zst10-s2-stick.html |
|
||||
| Zooz ZST10 | 10C4:EA60 | https://www.getzooz.com/zooz-zst10-s2-stick/ |
|
||||
| Z-WaveMe UZB | 0658:0200 | https://z-wave.me/products/uzb/ |
|
||||
|
||||
Additional devices may be discoverable, however only devices that have been confirmed discoverable are listed above.
|
||||
|
||||
796
source/_posts/2022-09-07-release-20229.markdown
Normal file
796
source/_posts/2022-09-07-release-20229.markdown
Normal file
@ -0,0 +1,796 @@
|
||||
---
|
||||
layout: post
|
||||
title: "2022.9: Home Assistant Birthday Release!"
|
||||
description: "New revamped Automation Editor, Weekly Schedule helper to help with automations, and Paul Bottein (Mushroom Cards) joins Nabu Casa"
|
||||
date: 2022-09-07 02:00:00
|
||||
date_formatted: "September 7, 2022"
|
||||
author: Zack Barett
|
||||
author_twitter: zackbarettha
|
||||
comments: true
|
||||
categories:
|
||||
- Release-Notes
|
||||
- Core
|
||||
og_image: /images/blog/2022-09/social.png
|
||||
---
|
||||
|
||||
<a href='/integrations/#version/2022.9'><img src='/images/blog/2022-09/social.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
Home Assistant Core 2022.9! 🎂
|
||||
|
||||
If you don't know yet, this month is Home Assistant's birthday! 🎉🎉 On September 17th, 2013 [Paulus Schoutsen](https://twitter.com/balloob) made the first commit for Home Assistant that started a snowball of Home Automation enthusiasts willing to contribute to the open-source project. 9 Years later, Home Assistant is actively used by more than 500,000 people and growing every day. Nabu Casa also turns 4 this month. Turning 4 years old and gaining a new full-time employee 🍄. This month it seems everyone was in the birthday spirit as we have a jam-packed release!
|
||||
|
||||
The automation engine is a big reason why Home Assistant has so many users. So in the spirit of [Streamlining Experiences](https://www.home-assistant.io/blog/2022/01/19/streamlining-experiences/), we thought a revamp was due. You will notice some huge improvements to the look and feel of the Automation Editor that we think will greatly improve its usability. I know I for sure see a huge difference!
|
||||
|
||||
Now I know that everyone usually expects [@frenck] to be writing these release notes, but he took a well deserved vacation! And now you are stuck with me. Zack 😀. I hope you enjoy the release and everything that was packed into it!
|
||||
|
||||
-- Zack
|
||||
|
||||
<!--more-->
|
||||
|
||||
- [Paul Bottein joins Nabu Casa](#paul-bottein-joins-nabu-casa)
|
||||
- [Streamlining automations](#streamlining-automations)
|
||||
- [New helper: Weekly schedule](#new-helper-weekly-schedule)
|
||||
- [Bluetooth everywhere](#bluetooth-everywhere)
|
||||
- [Z-Wave Firmware updates now live](#z-wave-firmware-updates-now-live)
|
||||
- [Zigbee backup and restore + migration](#zigbee-backup-and-restore--migration)
|
||||
- [Processor and memory usage](#processor-and-memory-usage)
|
||||
- [Other noteworthy changes](#other-noteworthy-changes)
|
||||
- [New Integrations](#new-integrations)
|
||||
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
|
||||
- [Release 2022.9.1 - September 8](#release-202291---september-8)
|
||||
- [Release 2022.9.2 - September 11](#release-202292---september-11)
|
||||
- [Release 2022.9.3 - September 13](#release-202293---september-13)
|
||||
- [Release 2022.9.4 - September 14](#release-202294---september-14)
|
||||
- [Release 2022.9.5 - September 18](#release-202295---september-18)
|
||||
- [Need help? Join the community](#need-help-join-the-community)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [All changes](#all-changes)
|
||||
|
||||
Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=UTltO1-d56s) today at 12:00 PDT / 21:00 CET!
|
||||
|
||||
<lite-youtube videoid="UTltO1-d56s" videotitle="Home Assistant 9th Birthday Release Party (2022.9)"></lite-youtube>
|
||||
|
||||
{% comment %}
|
||||
<!-- Replace the wrapper above with the following after the livestream...-->
|
||||
|
||||
Missed our release party live stream on YouTube? Don't worry! You can watch
|
||||
the recording of it right here!
|
||||
|
||||
<lite-youtube videoid="UTltO1-d56s" videotitle="Home Assistant 9th Birthday Release Party (2022.9)"></lite-youtube>
|
||||
|
||||
{% endcomment %}
|
||||
|
||||
## Paul Bottein joins Nabu Casa
|
||||
|
||||
We are excited to announce the newest member of the Nabu Casa team, [Paul Bottein](https://github.com/piitaya).
|
||||
|
||||
Paul is most known for his [Mushroom cards](https://github.com/piitaya/lovelace-mushroom) and a few additions to Home Assistant frontend like the Icon Picker. Paul is an incredible developer and his expertise in dashboard design will bring a lot to the Home Assistant frontend.
|
||||
|
||||
Welcome aboard and excited to see what Paul will bring to Home Assistant!
|
||||
|
||||
## Streamlining automations
|
||||
|
||||
We felt that there were quite a few improvements we could do in order to better streamline automation creation. That's why this release, we really
|
||||
took a long look at some of the main user experience issues. The new automation editor improvements focus on readability and ease of use. This
|
||||
will also make editing automations on your phone much easier!
|
||||
|
||||
First, you will notice the biggest change, collapsible cards for triggers, conditions, and actions. This change allows you to really focus on what you
|
||||
are currently working on instead of having everything open all at once. When you first open your automation in the editor, you will see all cards collapsed with
|
||||
an auto-generated explanation of what that section is doing. This allows you to easily choose which section you want to edit and focus in on it.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/automation_editor_new.png' alt='Screenshot showing the new automation editor with an easier overview'><br>
|
||||
|
||||
Next, there were a few items and options moved. You can see most of these in the top right overflow menu. For example, if you want to rename or update the description
|
||||
of your automation you can do that via the overflow menu > Rename. Moving these items to the overflow ensures that the main editor page is used for the main functions of
|
||||
your automation.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/automation_overflow.png' alt='Screenshot showing the new automation editor overflow menus'><br>
|
||||
|
||||
Last, but definitely not least, Frenck added some long requested features to the automation forms. **State and Attribute value auto-completion!** Now if you are adding a
|
||||
state trigger, you can choose from a list of known states for that device type. These are also all translated into your language. Now there is no need to remember or find
|
||||
the states possible or format the state that needs to be entered. Just choose a state from the dropdown and let your worries wisp away!
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/automation_state_selector.gif' alt='Screenshot showing the new automation editor state and attribute value selector'><br>
|
||||
|
||||
## New helper: Weekly schedule
|
||||
|
||||
Have you ever wanted to run a schedule-based automation for the same time each week or day? Well, you are now in luck! With the addition of the Schedule helper, you are now able
|
||||
to easily create these schedules to build more consistent automations and timings.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/create_schedule.gif' alt='A gif showcasing the new schedule helper and how to use the user interface'><br>
|
||||
|
||||
{% my config_flow_start badge domain="schedule" %}
|
||||
|
||||
## Bluetooth everywhere
|
||||
|
||||
Last release we introduced the Bluetooth integration. This release, it's on fire 🔥 Not only do we now support multiple Bluetooth adapters, we also support ESPHome devices acting as [Bluetooth proxies](https://esphome.io/components/bluetooth_proxy.html) for your home. Wait what?!
|
||||
|
||||
Yes 😎. You can now greatly expand the Bluetooth reach of Home Assistant using ordinary ESP32 devices. No extra hardware needed.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/bluetooth-proxy-overview.png' alt='Picture of a home showing how Bluetooth data is proxied via ESPHome devices to Home Assistant'><br>
|
||||
|
||||
To get a proxy up and running, head over to the [Bluetooth proxy installer website](https://esphome.github.io/bluetooth-proxies/) and install one straight from your browser.
|
||||
|
||||
Bluetooth proxies are currently limited to forwarding passive data. Active connections are coming in a future release. Bluetooth integrations in Home Assistant will transparently use Bluetooth proxies without any extra coding!
|
||||
|
||||
Most integrations now support using the adapter with the best signal to connect devices that need an active connection. Extension cables, USB-Ethernet extenders, or USB-IP coupled with an additional Bluetooth adapter can significantly extend your active connection range.
|
||||
|
||||
There is more! Besides 9 new supported brands, there is also support for a new open standard: [BTHome](https://bthome.io) by [@Ernst79]. It is automatically discovered by Home Assistant, devices can run over a year on a single battery and it supports data encryption.
|
||||
|
||||
Finally, suppose you are using the Home Assistant Operating System. In that case, we recommend upgrading to version 9 or later when it is released, as it comes with a faster D-Bus broker and newer Bluetooth firmware which can significantly enhance Bluetooth performance.
|
||||
|
||||
Thanks to [@bdraco], [@Ernst79], [@JesseRockz], [@jc2k] for all the hard, amazing and epic work 🙏.
|
||||
|
||||
## Z-Wave Firmware updates now live
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/zwave_updates.png' alt='Screenshot showing zwave device updates in the settings page'><br>
|
||||
|
||||
In 2022.7, we added support for updating Z-Wave device firmware, but the catch was that you needed the firmware files from the manufacturer in order to complete the update. [@AlCalzone] wasn't satisfied with this approach and began working on a better solution. That better solution is here with the introduction of the Z-Wave JS Firmware Update Service! For supported manufacturers, Z-Wave JS can now automatically detect, download, and install a firmware update if it is available for your device. This will be done the same way you are currently updating Home Assistant. You will see a notification in your settings menu and you can update right from there. Thanks [@raman325]
|
||||
|
||||
For now, only Jasco products are supported. Nabu Casa has been talking to other manufacturers to get more devices supported. To ensure our users can take advantage of this feature, we added update entities for your devices that will check once a day for new firmware updates. Nifty!
|
||||
|
||||
## Zigbee backup and restore + migration
|
||||
|
||||
The Zigbee Home Automation (ZHA) integration now supports network backups and migrating between Zigbee coordinators. Backups are taken automatically but can also be manually created from the configuration page. After restoring a Home Assistant backup, you can re-configure ZHA and migrate to a new Zigbee coordinator without any loss of your settings or devices that were connected. This is helpful if your current radio fails or a new radio comes out that you may want to migrate to.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/zigbee.png' alt='Screenshot showing the Zigbee Home Automation configuration page and the new backup functionality'><br>
|
||||
|
||||
## Processor and memory usage
|
||||
|
||||
The Hardware page just got a lot more interesting. You can go check out live statistics on your Memory and Processor usage when you load the Hardware page in your system menu. These statistics will represent your entire Home Assistant instance, giving you insight in how your hardware is handling your day to day tasks. This will not show any history but will display 5 minutes of live data once you load the page.
|
||||
|
||||
<img class="no-shadow" src='/images/blog/2022-09/hardware_page.png' alt='Screenshot showing the processor and memory usage on the hardware page'><br>
|
||||
|
||||
## Other noteworthy changes
|
||||
|
||||
There is much more juice in this release; here are some of the other
|
||||
noteworthy changes this release:
|
||||
|
||||
- Entity more info dialog merged with entity settings. Thanks [@balloob]
|
||||
- You can now enable local control of your Awair Element device. Thanks [@zachberger]
|
||||
- MiFlora now supports polling of the Battery sensor. Thanks [@bdraco]
|
||||
- August locks are now supported under the Yale Access Bluetooth integration. Thanks [@bdraco]
|
||||
- Many more Bluetooth adapters are now supported for the Bluetooth integration. Thanks [@bdraco]
|
||||
- The SwitchBot integration now supports the Color Bulb and Light strips. Thanks [@bdraco]
|
||||
- Automations, Scripts and Scenes tables received a new overflow menu that will allow for more actions directly from the picker. Thanks [@bramkragten] and [@piitaya]
|
||||
- You can now reorder automation elements using drag and drop. Thanks [@piitaya]
|
||||
- Icons have been added to more menus throughout the UI. Thanks [@frenck]
|
||||
- Automation triggers can now be aliased. Thanks [@frenck]
|
||||
|
||||
## New Integrations
|
||||
|
||||
We welcome the following new integrations in this release:
|
||||
|
||||
- [BlueMaestro], added by [@bdraco]
|
||||
- [BThome], added by [@Ernst79]
|
||||
- [Ecowitt], added by [@pvizeli]
|
||||
- [Escea], added by [@lazdavila]
|
||||
- [File Upload], added by [@balloob]
|
||||
- [Fully Kiosk Browser], added by [@cgarwood]
|
||||
- [JustNimbus], added by [@kvanzuijlen]
|
||||
- [LaCrosse View], added by [@IceBotYT]
|
||||
- [Landis+Gyr Heat Meter], added by [@vpathuis]
|
||||
- [LED BLE], added by [@bdraco]
|
||||
- [Melnor Bluetooth], added by [@vanstinator]
|
||||
- [PrusaLink], added by [@balloob]
|
||||
- [Qingping], added by [@bdraco]
|
||||
- [Schedule], added by [@frenck]
|
||||
- [SensorPro], added by [@bdraco]
|
||||
- [ThermoBeacon], added by [@bdraco]
|
||||
- [ThermoPro], added by [@bdraco]
|
||||
- [Yale Access Bluetooth], added by [@bdraco]
|
||||
|
||||
[@AlCalzone]: https://github.com/alcalzone
|
||||
[@zachberger]: https://github.com/zachberger
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@jesserockz]: https://github.com/jesserockz
|
||||
[@jc2k]: https://github.com/jc2k
|
||||
[@cgarwood]: https://github.com/cgarwood
|
||||
[@Ernst79]: https://github.com/Ernst79
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@IceBotYT]: https://github.com/IceBotYT
|
||||
[@kvanzuijlen]: https://github.com/kvanzuijlen
|
||||
[@lazdavila]: https://github.com/lazdavila
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@vanstinator]: https://github.com/vanstinator
|
||||
[@vpathuis]: https://github.com/vpathuis
|
||||
[BlueMaestro]: /integrations/bluemaestro
|
||||
[@piitaya]: https://github.com/piitaya
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[BThome]: /integrations/bthome
|
||||
[Ecowitt]: /integrations/ecowitt
|
||||
[Escea]: /integrations/escea
|
||||
[File Upload]: /integrations/file_upload
|
||||
[Fully Kiosk Browser]: /integrations/fully_kiosk
|
||||
[JustNimbus]: /integrations/justnimbus
|
||||
[LaCrosse View]: /integrations/lacrosse_view
|
||||
[Landis+Gyr Heat Meter]: /integrations/landisgyr_heat_meter
|
||||
[LED BLE]: /integrations/led_ble
|
||||
[Melnor Bluetooth]: /integrations/melnor
|
||||
[PrusaLink]: /integrations/prusalink
|
||||
[Qingping]: /integrations/qingping
|
||||
[Schedule]: /integrations/schedule
|
||||
[SensorPro]: /integrations/sensorpro
|
||||
[ThermoBeacon]: /integrations/thermobeacon
|
||||
[ThermoPro]: /integrations/thermopro
|
||||
[Yale Access Bluetooth]: /integrations/yalexs_ble
|
||||
|
||||
## Integrations now available to set up from the UI
|
||||
|
||||
The following integrations are now available via the Home Assistant UI:
|
||||
|
||||
- [Android IP Webcam], done by [@engrbm87]
|
||||
- [LaMetric], done by [@frenck]
|
||||
- [Open Exchange Rates], done by [@MartinHjelmare]
|
||||
- [Pushover], done by [@engrbm87]
|
||||
- [Volvo On Call], done by [@y34hbuddy]
|
||||
|
||||
[@engrbm87]: https://github.com/engrbm87
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@y34hbuddy]: https://github.com/y34hbuddy
|
||||
[Android IP Webcam]: /integrations/android_ip_webcam
|
||||
[LaMetric]: /integrations/lametric
|
||||
[Open Exchange Rates]: /integrations/openexchangerates
|
||||
[Pushover]: /integrations/pushover
|
||||
[Volvo On Call]: /integrations/volvooncall
|
||||
|
||||
## Release 2022.9.1 - September 8
|
||||
|
||||
- Show progress for zwave_js.update entity ([@raman325] - [#77905]) ([zwave_js docs])
|
||||
- Fix `len` method typo for Osram light ([@Vaskivskyi] - [#78008]) ([osramlightify docs])
|
||||
- Add value ID to zwave_js device diagnostics ([@raman325] - [#78015]) ([zwave_js docs])
|
||||
- Fix zwave_js default emulate hardware in options flow ([@MartinHjelmare] - [#78024]) ([zwave_js docs])
|
||||
- Extract lametric device from coordinator in notify ([@ludeeus] - [#78027]) ([lametric docs])
|
||||
- Bump velbus-aio to 2022.9.1 ([@Cereal2nd] - [#78039]) ([velbus docs])
|
||||
- Fix zwave_js device re-interview ([@MartinHjelmare] - [#78046]) ([zwave_js docs])
|
||||
- Bump bluetooth-adapters to 0.3.5 ([@bdraco] - [#78052]) ([bluetooth docs])
|
||||
- Bump bluetooth-auto-recovery to 0.3.2 ([@bdraco] - [#78063]) ([bluetooth docs])
|
||||
- Fix bug with 1st gen RainMachine controllers and unknown API calls ([@bachya] - [#78070]) ([rainmachine docs])
|
||||
- Bump pylitterbot to 2022.9.1 ([@natekspencer] - [#78071]) ([litterrobot docs])
|
||||
- Allow OpenWeatherMap config flow to test using old API to pass ([@jbouwh] - [#78074]) ([openweathermap docs])
|
||||
- Fix Ecobee remote sensors not updating ([@rlippmann] - [#78035]) ([ecobee docs])
|
||||
|
||||
[#77905]: https://github.com/home-assistant/core/pull/77905
|
||||
[#77968]: https://github.com/home-assistant/core/pull/77968
|
||||
[#78008]: https://github.com/home-assistant/core/pull/78008
|
||||
[#78015]: https://github.com/home-assistant/core/pull/78015
|
||||
[#78024]: https://github.com/home-assistant/core/pull/78024
|
||||
[#78027]: https://github.com/home-assistant/core/pull/78027
|
||||
[#78035]: https://github.com/home-assistant/core/pull/78035
|
||||
[#78039]: https://github.com/home-assistant/core/pull/78039
|
||||
[#78046]: https://github.com/home-assistant/core/pull/78046
|
||||
[#78052]: https://github.com/home-assistant/core/pull/78052
|
||||
[#78063]: https://github.com/home-assistant/core/pull/78063
|
||||
[#78070]: https://github.com/home-assistant/core/pull/78070
|
||||
[#78071]: https://github.com/home-assistant/core/pull/78071
|
||||
[#78074]: https://github.com/home-assistant/core/pull/78074
|
||||
[@Cereal2nd]: https://github.com/Cereal2nd
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@Vaskivskyi]: https://github.com/Vaskivskyi
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[@ludeeus]: https://github.com/ludeeus
|
||||
[@natekspencer]: https://github.com/natekspencer
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@rlippmann]: https://github.com/rlippmann
|
||||
[abode docs]: /integrations/abode/
|
||||
[accuweather docs]: /integrations/accuweather/
|
||||
[acmeda docs]: /integrations/acmeda/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[ecobee docs]: /integrations/ecobee/
|
||||
[lametric docs]: /integrations/lametric/
|
||||
[litterrobot docs]: /integrations/litterrobot/
|
||||
[openweathermap docs]: /integrations/openweathermap/
|
||||
[osramlightify docs]: /integrations/osramlightify/
|
||||
[rainmachine docs]: /integrations/rainmachine/
|
||||
[velbus docs]: /integrations/velbus/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2022.9.2 - September 11
|
||||
|
||||
- Fix reload of MQTT config entries ([@jbouwh] - [#76089]) ([mqtt docs])
|
||||
- Clear MQTT discovery topic when a disabled entity is removed ([@jbouwh] - [#77757]) ([mqtt docs])
|
||||
- Improve warning messages on invalid received modes ([@jbouwh] - [#77909]) ([mqtt docs])
|
||||
- Handle missing supported brands ([@balloob] - [#78090]) ([websocket_api docs])
|
||||
- Fix switchbot writing state too frequently ([@bdraco] - [#78094]) ([switchbot docs])
|
||||
- Fix LIFX light turning on while fading off ([@amelchio] - [#78095]) ([lifx docs])
|
||||
- Fix zwave_js update entity ([@raman325] - [#78116]) ([zwave_js docs])
|
||||
- Improve unique_id collision checks in entity_platform ([@emontnemery] - [#78132])
|
||||
- Allow non-integers in threshold sensor config flow ([@emontnemery] - [#78137]) ([threshold docs])
|
||||
- Bump bluetooth-adapters to 0.3.6 ([@bdraco] - [#78138]) ([bluetooth docs])
|
||||
- Add missing strings for errors in amberelectric config flow ([@Vaskivskyi] - [#78140]) ([amberelectric docs])
|
||||
- Bump aioecowitt to 2022.09.1 ([@pvizeli] - [#78142]) ([ecowitt docs])
|
||||
- Add missing moisture sensor to xiaomi_ble ([@Jc2k] - [#78160]) ([xiaomi_ble docs])
|
||||
- Bump pySwitchbot to 0.19.1 ([@bdraco] - [#78168]) ([switchbot docs])
|
||||
- Bump aiohomekit to 1.5.3 ([@bdraco] - [#78170]) ([homekit_controller docs])
|
||||
- Fix ecowitt typing ([@balloob] - [#78171]) ([ecowitt docs])
|
||||
- Fix sending notification to multiple targets in Pushover ([@engrbm87] - [#78111]) ([pushover docs])
|
||||
- Add dependencies to ecowitt ([@pvizeli] - [#78187]) ([ecowitt docs])
|
||||
- Bump led-ble to 0.8.3 ([@bdraco] - [#78188]) ([led_ble docs])
|
||||
- Fix switchbot not setting up when already connected at startup ([@bdraco] - [#78198]) ([switchbot docs])
|
||||
- Fix Yale Access Bluetooth not setting up when already connected at startup ([@bdraco] - [#78199]) ([yalexs_ble docs])
|
||||
- Bump ZHA dependencies ([@puddly] - [#78201]) ([zha docs])
|
||||
- Close stale switchbot connections at setup time ([@bdraco] - [#78202]) ([switchbot docs])
|
||||
- Bump aiohomekit to 1.5.4 to handle stale ble connections at startup ([@bdraco] - [#78203]) ([homekit_controller docs])
|
||||
- Landis+Gyr integration: increase timeout and add debug logging ([@vpathuis] - [#78025]) ([landisgyr_heat_meter docs])
|
||||
- Bump bluetooth-adapters to 0.4.1 ([@bdraco] - [#78205]) ([bluetooth docs])
|
||||
- Bump `regenmaschine` to 2022.09.1 ([@bachya] - [#78210]) ([rainmachine docs])
|
||||
- Bump led_ble to 0.8.5 ([@bdraco] - [#78215]) ([led_ble docs])
|
||||
- Bump pysensibo to 1.0.20 ([@gjohansson-ST] - [#78222]) ([sensibo docs])
|
||||
- Bump PySwitchbot to 0.19.5 ([@bdraco] - [#78224]) ([switchbot docs])
|
||||
- Bump yalexs-ble to 1.8.1 ([@bdraco] - [#78225]) ([yalexs_ble docs])
|
||||
- Bump led-ble to 0.9.1 ([@bdraco] - [#78226]) ([led_ble docs])
|
||||
- Bump aiohomekit to 1.5.6 ([@bdraco] - [#78228]) ([homekit_controller docs])
|
||||
|
||||
[#76089]: https://github.com/home-assistant/core/pull/76089
|
||||
[#77757]: https://github.com/home-assistant/core/pull/77757
|
||||
[#77909]: https://github.com/home-assistant/core/pull/77909
|
||||
[#77968]: https://github.com/home-assistant/core/pull/77968
|
||||
[#78025]: https://github.com/home-assistant/core/pull/78025
|
||||
[#78081]: https://github.com/home-assistant/core/pull/78081
|
||||
[#78090]: https://github.com/home-assistant/core/pull/78090
|
||||
[#78094]: https://github.com/home-assistant/core/pull/78094
|
||||
[#78095]: https://github.com/home-assistant/core/pull/78095
|
||||
[#78111]: https://github.com/home-assistant/core/pull/78111
|
||||
[#78116]: https://github.com/home-assistant/core/pull/78116
|
||||
[#78132]: https://github.com/home-assistant/core/pull/78132
|
||||
[#78137]: https://github.com/home-assistant/core/pull/78137
|
||||
[#78138]: https://github.com/home-assistant/core/pull/78138
|
||||
[#78140]: https://github.com/home-assistant/core/pull/78140
|
||||
[#78142]: https://github.com/home-assistant/core/pull/78142
|
||||
[#78160]: https://github.com/home-assistant/core/pull/78160
|
||||
[#78168]: https://github.com/home-assistant/core/pull/78168
|
||||
[#78170]: https://github.com/home-assistant/core/pull/78170
|
||||
[#78171]: https://github.com/home-assistant/core/pull/78171
|
||||
[#78187]: https://github.com/home-assistant/core/pull/78187
|
||||
[#78188]: https://github.com/home-assistant/core/pull/78188
|
||||
[#78198]: https://github.com/home-assistant/core/pull/78198
|
||||
[#78199]: https://github.com/home-assistant/core/pull/78199
|
||||
[#78201]: https://github.com/home-assistant/core/pull/78201
|
||||
[#78202]: https://github.com/home-assistant/core/pull/78202
|
||||
[#78203]: https://github.com/home-assistant/core/pull/78203
|
||||
[#78205]: https://github.com/home-assistant/core/pull/78205
|
||||
[#78210]: https://github.com/home-assistant/core/pull/78210
|
||||
[#78215]: https://github.com/home-assistant/core/pull/78215
|
||||
[#78222]: https://github.com/home-assistant/core/pull/78222
|
||||
[#78224]: https://github.com/home-assistant/core/pull/78224
|
||||
[#78225]: https://github.com/home-assistant/core/pull/78225
|
||||
[#78226]: https://github.com/home-assistant/core/pull/78226
|
||||
[#78228]: https://github.com/home-assistant/core/pull/78228
|
||||
[@Jc2k]: https://github.com/Jc2k
|
||||
[@Vaskivskyi]: https://github.com/Vaskivskyi
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@engrbm87]: https://github.com/engrbm87
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[@puddly]: https://github.com/puddly
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@vpathuis]: https://github.com/vpathuis
|
||||
[abode docs]: /integrations/abode/
|
||||
[accuweather docs]: /integrations/accuweather/
|
||||
[acmeda docs]: /integrations/acmeda/
|
||||
[amberelectric docs]: /integrations/amberelectric/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[ecowitt docs]: /integrations/ecowitt/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[landisgyr_heat_meter docs]: /integrations/landisgyr_heat_meter/
|
||||
[led_ble docs]: /integrations/led_ble/
|
||||
[lifx docs]: /integrations/lifx/
|
||||
[mqtt docs]: /integrations/mqtt/
|
||||
[pushover docs]: /integrations/pushover/
|
||||
[rainmachine docs]: /integrations/rainmachine/
|
||||
[sensibo docs]: /integrations/sensibo/
|
||||
[switchbot docs]: /integrations/switchbot/
|
||||
[threshold docs]: /integrations/threshold/
|
||||
[websocket_api docs]: /integrations/websocket_api/
|
||||
[xiaomi_ble docs]: /integrations/xiaomi_ble/
|
||||
[yalexs_ble docs]: /integrations/yalexs_ble/
|
||||
[zha docs]: /integrations/zha/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2022.9.3 - September 13
|
||||
|
||||
- Move up setup of service to make it more robust when running multiple instances of deCONZ ([@Kane610] - [#77621]) ([deconz docs])
|
||||
- Bump blinkpy to 0.19.2 ([@Vaskivskyi] - [#78097]) ([blink docs])
|
||||
- Bump PyViCare==2.17.0 ([@TheJulianJES] - [#78232]) ([vicare docs])
|
||||
- Fix missing dependency for dbus_next ([@d-walsh] - [#78235]) ([bluetooth docs])
|
||||
- Bump bluetooth-auto-recovery to 0.3.3 ([@bdraco] - [#78245]) ([bluetooth docs])
|
||||
- Bump aiodiscover to 1.4.13 ([@bdraco] - [#78253]) ([dhcp docs])
|
||||
- Bump pySwitchbot to 0.19.6 ([@bdraco] - [#78304]) ([switchbot docs])
|
||||
- Make yalexs_ble matcher more specific ([@bdraco] - [#78307]) ([yalexs_ble docs])
|
||||
- Fix sengled bulbs in ZHA ([@dmulcahey] - [#78315]) ([zha docs])
|
||||
- Fix calculating gas cost for gas measured in ft3 ([@emontnemery] - [#78327]) ([energy docs])
|
||||
- Bump bleak to 0.17.0 ([@bdraco] - [#78333]) ([bluetooth docs])
|
||||
- Drop initial when loading input_number from storage ([@emontnemery] - [#78354]) ([input_number docs])
|
||||
- Don't allow partial update of input_number settings ([@emontnemery] - [#78356]) ([input_number docs])
|
||||
- Bump PySwitchbot to 0.19.8 ([@bdraco] - [#78361]) ([switchbot docs])
|
||||
- Bump yalexs-ble to 1.9.0 ([@bdraco] - [#78362]) ([yalexs_ble docs])
|
||||
- Bump xiaomi-ble to 0.9.3 ([@bdraco] - [#78301]) ([xiaomi_ble docs])
|
||||
- Bump xiaomi-ble to 0.10.0 ([@bdraco] - [#78365]) ([xiaomi_ble docs])
|
||||
- Bump led-ble to 0.10.0 ([@bdraco] - [#78367]) ([led_ble docs])
|
||||
- Bump aiohomekit to 1.5.7 ([@bdraco] - [#78369]) ([homekit_controller docs])
|
||||
- Don't allow partial update of counter settings ([@emontnemery] - [#78371]) ([counter docs])
|
||||
- Don't allow partial update of input_boolean settings ([@emontnemery] - [#78372]) ([input_boolean docs])
|
||||
- Don't allow partial update of input_datetime settings ([@emontnemery] - [#78373]) ([input_datetime docs])
|
||||
- Don't allow partial update of input_button settings ([@emontnemery] - [#78374]) ([input_button docs])
|
||||
- Don't allow partial update of input_select settings ([@emontnemery] - [#78376]) ([input_select docs])
|
||||
- Don't allow partial update of input_text settings ([@emontnemery] - [#78377]) ([input_text docs])
|
||||
- Don't allow partial update of timer settings ([@emontnemery] - [#78378]) ([timer docs])
|
||||
- Unregister EcoWitt webhook at unload ([@pvizeli] - [#78388]) ([ecowitt docs])
|
||||
- Fix flapping system log test ([@bdraco] - [#78391]) ([system_log docs])
|
||||
- Fix CI workflow caching ([@cdce8p] - [#78398])
|
||||
- Update frontend to 20220907.1 ([@bramkragten] - [#78404]) ([frontend docs])
|
||||
- Bump govee-ble to 0.17.3 ([@bdraco] - [#78405]) ([govee_ble docs])
|
||||
- Fix bug with RainMachine update entity ([@bachya] - [#78411]) ([rainmachine docs])
|
||||
- Retry on unavailable IPMA api ([@dgomes] - [#78332]) ([ipma docs])
|
||||
|
||||
[#77621]: https://github.com/home-assistant/core/pull/77621
|
||||
[#77968]: https://github.com/home-assistant/core/pull/77968
|
||||
[#78081]: https://github.com/home-assistant/core/pull/78081
|
||||
[#78097]: https://github.com/home-assistant/core/pull/78097
|
||||
[#78169]: https://github.com/home-assistant/core/pull/78169
|
||||
[#78232]: https://github.com/home-assistant/core/pull/78232
|
||||
[#78235]: https://github.com/home-assistant/core/pull/78235
|
||||
[#78245]: https://github.com/home-assistant/core/pull/78245
|
||||
[#78253]: https://github.com/home-assistant/core/pull/78253
|
||||
[#78301]: https://github.com/home-assistant/core/pull/78301
|
||||
[#78304]: https://github.com/home-assistant/core/pull/78304
|
||||
[#78307]: https://github.com/home-assistant/core/pull/78307
|
||||
[#78315]: https://github.com/home-assistant/core/pull/78315
|
||||
[#78327]: https://github.com/home-assistant/core/pull/78327
|
||||
[#78332]: https://github.com/home-assistant/core/pull/78332
|
||||
[#78333]: https://github.com/home-assistant/core/pull/78333
|
||||
[#78354]: https://github.com/home-assistant/core/pull/78354
|
||||
[#78356]: https://github.com/home-assistant/core/pull/78356
|
||||
[#78361]: https://github.com/home-assistant/core/pull/78361
|
||||
[#78362]: https://github.com/home-assistant/core/pull/78362
|
||||
[#78365]: https://github.com/home-assistant/core/pull/78365
|
||||
[#78367]: https://github.com/home-assistant/core/pull/78367
|
||||
[#78369]: https://github.com/home-assistant/core/pull/78369
|
||||
[#78371]: https://github.com/home-assistant/core/pull/78371
|
||||
[#78372]: https://github.com/home-assistant/core/pull/78372
|
||||
[#78373]: https://github.com/home-assistant/core/pull/78373
|
||||
[#78374]: https://github.com/home-assistant/core/pull/78374
|
||||
[#78376]: https://github.com/home-assistant/core/pull/78376
|
||||
[#78377]: https://github.com/home-assistant/core/pull/78377
|
||||
[#78378]: https://github.com/home-assistant/core/pull/78378
|
||||
[#78388]: https://github.com/home-assistant/core/pull/78388
|
||||
[#78391]: https://github.com/home-assistant/core/pull/78391
|
||||
[#78398]: https://github.com/home-assistant/core/pull/78398
|
||||
[#78404]: https://github.com/home-assistant/core/pull/78404
|
||||
[#78405]: https://github.com/home-assistant/core/pull/78405
|
||||
[#78411]: https://github.com/home-assistant/core/pull/78411
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@TheJulianJES]: https://github.com/TheJulianJES
|
||||
[@Vaskivskyi]: https://github.com/Vaskivskyi
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@d-walsh]: https://github.com/d-walsh
|
||||
[@dgomes]: https://github.com/dgomes
|
||||
[@dmulcahey]: https://github.com/dmulcahey
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[abode docs]: /integrations/abode/
|
||||
[accuweather docs]: /integrations/accuweather/
|
||||
[acmeda docs]: /integrations/acmeda/
|
||||
[blink docs]: /integrations/blink/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[counter docs]: /integrations/counter/
|
||||
[deconz docs]: /integrations/deconz/
|
||||
[dhcp docs]: /integrations/dhcp/
|
||||
[ecowitt docs]: /integrations/ecowitt/
|
||||
[energy docs]: /integrations/energy/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[govee_ble docs]: /integrations/govee_ble/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[input_boolean docs]: /integrations/input_boolean/
|
||||
[input_button docs]: /integrations/input_button/
|
||||
[input_datetime docs]: /integrations/input_datetime/
|
||||
[input_number docs]: /integrations/input_number/
|
||||
[input_select docs]: /integrations/input_select/
|
||||
[input_text docs]: /integrations/input_text/
|
||||
[ipma docs]: /integrations/ipma/
|
||||
[led_ble docs]: /integrations/led_ble/
|
||||
[rainmachine docs]: /integrations/rainmachine/
|
||||
[switchbot docs]: /integrations/switchbot/
|
||||
[system_log docs]: /integrations/system_log/
|
||||
[timer docs]: /integrations/timer/
|
||||
[vicare docs]: /integrations/vicare/
|
||||
[xiaomi_ble docs]: /integrations/xiaomi_ble/
|
||||
[yalexs_ble docs]: /integrations/yalexs_ble/
|
||||
[zha docs]: /integrations/zha/
|
||||
|
||||
## Release 2022.9.4 - September 14
|
||||
|
||||
- Update frontend to 20220907.2 ([@bramkragten] - [#78431]) ([frontend docs])
|
||||
|
||||
[#78431]: https://github.com/home-assistant/core/pull/78431
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[frontend docs]: /integrations/frontend
|
||||
|
||||
## Release 2022.9.5 - September 18
|
||||
|
||||
- Fix fan speed regression for some xiaomi fans ([@peteh] - [#78406]) ([xiaomi_miio docs])
|
||||
- Only redact zwave_js values that are worth redacting ([@raman325] - [#78420]) ([zwave_js docs])
|
||||
- Prevent deleting blueprints which are in use ([@emontnemery] - [#78444]) ([automation docs]) ([script docs]) ([blueprint docs])
|
||||
- Bump bleak-retry-connector to 0.17.1 ([@bdraco] - [#78474]) ([bluetooth docs])
|
||||
- Bump python-songpal to 0.15.1 ([@rytilahti] - [#78481]) ([songpal docs])
|
||||
- Bump PySwitchbot to 0.19.9 ([@bdraco] - [#78504]) ([switchbot docs])
|
||||
- Bump yalexs_ble to 1.9.2 ([@bdraco] - [#78508]) ([yalexs_ble docs])
|
||||
- Bump led-ble to 0.10.1 ([@bdraco] - [#78511]) ([led_ble docs])
|
||||
- Bump aiohomekit to 1.5.8 ([@bdraco] - [#78515]) ([homekit_controller docs])
|
||||
- Fix zwave_js update entity startup state ([@raman325] - [#78563]) ([zwave_js docs])
|
||||
- Bump pyrisco to v0.5.5 ([@OnFreund] - [#78566]) ([risco docs])
|
||||
- Fix WebSocket condition testing ([@frenck] - [#78570]) ([websocket_api docs])
|
||||
- Fix switchbot not accepting the first advertisement ([@bdraco] - [#78610]) ([switchbot docs])
|
||||
- Fix reconnect race in HomeKit Controller ([@bdraco] - [#78629]) ([homekit_controller docs])
|
||||
- Bump qingping-ble to 0.7.0 ([@skgsergio] - [#78630]) ([qingping docs])
|
||||
- Add a helpful message to the config_entries.OperationNotAllowed exception ([@bdraco] - [#78631])
|
||||
- Update demetriek to 0.2.4 ([@frenck] - [#78646]) ([lametric docs])
|
||||
- Handle multiple files properly in zwave_js update entity ([@raman325] - [#78658]) ([zwave_js docs])
|
||||
- Remove mDNS iteration from Plugwise unique ID ([@frenck] - [#78680]) ([plugwise docs])
|
||||
- Fix bluetooth callback matchers when only matching on connectable ([@bdraco] - [#78687]) ([bluetooth docs])
|
||||
- Bump thermobeacon-ble to 0.3.2 ([@bdraco] - [#78693]) ([thermobeacon docs])
|
||||
|
||||
[#77968]: https://github.com/home-assistant/core/pull/77968
|
||||
[#78081]: https://github.com/home-assistant/core/pull/78081
|
||||
[#78169]: https://github.com/home-assistant/core/pull/78169
|
||||
[#78406]: https://github.com/home-assistant/core/pull/78406
|
||||
[#78410]: https://github.com/home-assistant/core/pull/78410
|
||||
[#78420]: https://github.com/home-assistant/core/pull/78420
|
||||
[#78438]: https://github.com/home-assistant/core/pull/78438
|
||||
[#78444]: https://github.com/home-assistant/core/pull/78444
|
||||
[#78474]: https://github.com/home-assistant/core/pull/78474
|
||||
[#78481]: https://github.com/home-assistant/core/pull/78481
|
||||
[#78504]: https://github.com/home-assistant/core/pull/78504
|
||||
[#78508]: https://github.com/home-assistant/core/pull/78508
|
||||
[#78511]: https://github.com/home-assistant/core/pull/78511
|
||||
[#78515]: https://github.com/home-assistant/core/pull/78515
|
||||
[#78563]: https://github.com/home-assistant/core/pull/78563
|
||||
[#78566]: https://github.com/home-assistant/core/pull/78566
|
||||
[#78570]: https://github.com/home-assistant/core/pull/78570
|
||||
[#78610]: https://github.com/home-assistant/core/pull/78610
|
||||
[#78629]: https://github.com/home-assistant/core/pull/78629
|
||||
[#78630]: https://github.com/home-assistant/core/pull/78630
|
||||
[#78631]: https://github.com/home-assistant/core/pull/78631
|
||||
[#78646]: https://github.com/home-assistant/core/pull/78646
|
||||
[#78658]: https://github.com/home-assistant/core/pull/78658
|
||||
[#78680]: https://github.com/home-assistant/core/pull/78680
|
||||
[#78687]: https://github.com/home-assistant/core/pull/78687
|
||||
[#78693]: https://github.com/home-assistant/core/pull/78693
|
||||
[@OnFreund]: https://github.com/OnFreund
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@peteh]: https://github.com/peteh
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@rytilahti]: https://github.com/rytilahti
|
||||
[@skgsergio]: https://github.com/skgsergio
|
||||
[abode docs]: /integrations/abode/
|
||||
[accuweather docs]: /integrations/accuweather/
|
||||
[acmeda docs]: /integrations/acmeda/
|
||||
[automation docs]: /integrations/automation/
|
||||
[blueprint docs]: /integrations/blueprint/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[lametric docs]: /integrations/lametric/
|
||||
[led_ble docs]: /integrations/led_ble/
|
||||
[plugwise docs]: /integrations/plugwise/
|
||||
[qingping docs]: /integrations/qingping/
|
||||
[risco docs]: /integrations/risco/
|
||||
[script docs]: /integrations/script/
|
||||
[songpal docs]: /integrations/songpal/
|
||||
[switchbot docs]: /integrations/switchbot/
|
||||
[thermobeacon docs]: /integrations/thermobeacon/
|
||||
[websocket_api docs]: /integrations/websocket_api/
|
||||
[xiaomi_miio docs]: /integrations/xiaomi_miio/
|
||||
[yalexs_ble docs]: /integrations/yalexs_ble/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Need help? Join the community
|
||||
|
||||
Home Assistant has a great community of users who are all more than willing
|
||||
to help each other out. So, join us!
|
||||
|
||||
Our very active [Discord chat server](/join-chat) is an excellent place to be
|
||||
at, and don't forget to join our amazing [forums](https://community.home-assistant.io/).
|
||||
|
||||
Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues),
|
||||
to get it fixed! Or, check [our help page](/help) for guidance for more
|
||||
places you can go.
|
||||
|
||||
Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter)
|
||||
to get the latest news about features, things happening in our community and
|
||||
other news about building an Open Home; straight into your inbox.
|
||||
|
||||
## Breaking Changes
|
||||
|
||||
Below is a listing of the breaking change for this release, per subject or
|
||||
integration. Click on one of those to read more about the breaking change
|
||||
for that specific item.
|
||||
|
||||
{% details "BMW Connected Drive" %}
|
||||
|
||||
Entity `sensor.<your_vehicle>_charging_time_label` (disabled by default) has
|
||||
been removed as it is not provided by the upstream library/API anymore.
|
||||
|
||||
([@rikroe] - [#76616]) ([documentation](/integrations/bmw_connected_drive))
|
||||
|
||||
[@rikroe]: https://github.com/rikroe
|
||||
[#76616]: https://github.com/home-assistant/core/pull/76616
|
||||
|
||||
---
|
||||
|
||||
The attribute `charging_status` of `binary_sensor.<your_car>_charging_status`
|
||||
has been removed. Please use `sensor.charging_status` instead.
|
||||
|
||||
([@rikroe] - [#74921]) ([documentation](/integrations/bmw_connected_drive))
|
||||
|
||||
[#74921]: https://github.com/home-assistant/core/pull/74921
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "HomeKit" %}
|
||||
|
||||
The Homekit PM2.5 µg/m3 mappings in the HomeKit integration now use the values
|
||||
based on the [US AQI set by the EPA](https://www.epa.gov/sites/default/files/2016-04/documents/2012_aqi_factsheet.pdf).
|
||||
|
||||
| HomeKit | Previous PM2.5 µg/m3 | New PM2.5 µg/m3 |
|
||||
|---|---|---|
|
||||
| Excellent | <= 25 | <= 12 |
|
||||
| Good | <= 50 | <= 35.4 |
|
||||
| Fair | <= 100 | <= 55.4 |
|
||||
| Inferior | <= 300 | <= 150.4 |
|
||||
| Poor | > 300 | > 150.4 |
|
||||
|
||||
([@sarabveer] - [#76358]) ([documentation](/integrations/homekit))
|
||||
|
||||
[@sarabveer]: https://github.com/sarabveer
|
||||
[#76358]: https://github.com/home-assistant/core/pull/76358
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "International Space Station (ISS)" %}
|
||||
|
||||
It will no longer be possible to know if the international space station (ISS)
|
||||
is above you nor the timestamp for the next rise of the station as these
|
||||
features have been removed in the underlying API.
|
||||
|
||||
The binary sensor will be removed and all automations relying on this will no
|
||||
longer work. Unfortunately there is no substitute for this. Instead we have
|
||||
introduced a new sensor, that still tells you the location of the ISS,
|
||||
while showing how many people are in space, as main state.
|
||||
|
||||
([@DurgNomis-drol] - [#77218]) ([documentation](/integrations/iss))
|
||||
|
||||
[@DurgNomis-drol]: https://github.com/DurgNomis-drol
|
||||
[#77218]: https://github.com/home-assistant/core/pull/77218
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Litter-Robot" %}
|
||||
|
||||
The previously deprecated `reset_waste_drawer` and `set_wait_time` services from
|
||||
the litterrobot vacuum entity, have been removed.
|
||||
|
||||
([@natekspencer] - [#77052]) ([documentation](/integrations/litterrobot))
|
||||
|
||||
[@natekspencer]: https://github.com/natekspencer
|
||||
[#77052]: https://github.com/home-assistant/core/pull/77052
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "MQTT" %}
|
||||
|
||||
Support for MQTT climate `hold` and `away` modes, which was deprecated in
|
||||
Home Assistant Core 2022.3.0, has been removed. The `hold` and `away` modes
|
||||
are replaced by `preset_mode`.
|
||||
|
||||
([@jbouwh] - [#76299]) ([documentation](/integrations/mqtt))
|
||||
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[#76299]: https://github.com/home-assistant/core/pull/76299
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Open Exchange Rates" %}
|
||||
|
||||
The sensor now has a unit of measurement according to the exchange rate quote.
|
||||
|
||||
([@MartinHjelmare] - [#76017]) ([documentation](/integrations/openexchangerates))
|
||||
|
||||
[#76017]: https://github.com/home-assistant/core/pull/76017
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Roku" %}
|
||||
|
||||
Roku media player will indicate `IDLE` instead of `HOME` when at home screen.
|
||||
You can still detect home screen by looking at `app_id` attribute.
|
||||
|
||||
([@elupus] - [#77385]) ([documentation](/integrations/roku))
|
||||
|
||||
[@elupus]: https://github.com/elupus
|
||||
[#77385]: https://github.com/home-assistant/core/pull/77385
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "SMS notifications via GSM-modem" %}
|
||||
|
||||
Setting up the notify platform of the SMS integration by a platform section in
|
||||
YAML configuration is no longer supported. The `sms` platform section
|
||||
under `notify:` can be removed from your YAML configuration files.
|
||||
|
||||
A recipient can be specified by using the `target` parameter in the notify
|
||||
service call instead.
|
||||
|
||||
([@ocalvo] - [#76733]) ([documentation](/integrations/sms))
|
||||
|
||||
[@ocalvo]: https://github.com/ocalvo
|
||||
[#76733]: https://github.com/home-assistant/core/pull/76733
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Utility Meter" %}
|
||||
|
||||
The previously deprecated `utility_meter` entities, used to change tariffs,
|
||||
have been removed. Please use the provided `select` entity instead.
|
||||
|
||||
([@dgomes] - [#76480]) ([documentation](/integrations/utility_meter))
|
||||
|
||||
[@dgomes]: https://github.com/dgomes
|
||||
[#76480]: https://github.com/home-assistant/core/pull/76480
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Z-Wave" %}
|
||||
|
||||
You must use zwave-js-server 1.22.1 or greater (schema 22).
|
||||
|
||||
With this release, you will need to update your zwave-js-server instance.
|
||||
|
||||
- If you use the zwave_js addon, you need to have at least version `0.1.66`.
|
||||
- If you use the zwavejs2mqtt addon, you need to have at least version `0.46.0`.
|
||||
- If you use the zwavejs2mqtt Docker container, you need to have at least version `7.0.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.22.1`.
|
||||
|
||||
([@raman325] - [#75795] [#76903]) ([documentation](/integrations/zwave_js))
|
||||
|
||||
[@raman325]: https://github.com/raman325
|
||||
[#75795]: https://github.com/home-assistant/core/pull/75795
|
||||
[#76903]: https://github.com/home-assistant/core/pull/76903
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
If you are a custom integration developer and want to learn about breaking
|
||||
changes and new features available for your integration: Be sure to follow our
|
||||
[developer blog][devblog]. The following are the most notable for this release:
|
||||
|
||||
[devblog]: https://developers.home-assistant.io/blog/
|
||||
|
||||
- [AutomationActionType deprecation for 2022.9](https://developers.home-assistant.io/blog/2022/08/15/automation-action-type-deprecation)
|
||||
- [Bluetooth passive sensor API changes for 2022.9](https://developers.home-assistant.io/blog/2022/08/08/bluetooth-api-changes)
|
||||
- [Device tracker deprecations for 2022.9](https://developers.home-assistant.io/blog/2022/07/29/device-tracker_source-type-deprecation/)
|
||||
- [Globally available HomeAssistant object (hass)](https://developers.home-assistant.io/blog/2022/08/24/globally_accessible_hass)
|
||||
- [LightEntity no longer supports white_value](https://developers.home-assistant.io/blog/2022/08/18/light_white_value_removed)
|
||||
- [The issue registry has been moved to homeassistant.helpers](https://developers.home-assistant.io/blog/2022/08/25/issue_registry_moved_to_helpers)
|
||||
|
||||
## 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 2022.9](/changelogs/core-2022.9)
|
||||
1842
source/changelogs/core-2022.9.markdown
Normal file
1842
source/changelogs/core-2022.9.markdown
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -5,14 +5,14 @@ description: "A quick intro on getting your first automation going."
|
||||
|
||||
Once your devices are set up, it's time to put the cherry on the pie: automation. In this guide we're going to create a simple automation rule to **turn on the lights when the sun sets**. Of course, this assumes that you have set up an integration that provides a light at this point.
|
||||
|
||||
In the user interface, click Configuration in the sidebar, then click Automation. You will now see the automation screen from which you can manage all the automations in Home Assistant.
|
||||
In the user interface, click Settings in the sidebar, then click Automations & Scenes. You will now see the automation screen from which you can manage all the automations in Home Assistant.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/getting-started/automation-editor.png'>
|
||||
The automation editor.
|
||||
</p>
|
||||
|
||||
Click the blue button at the bottom right to create a new automation. You are presented with a blank automation screen.
|
||||
Click the blue button at the bottom right to create a new automation. A dialog will appear. Choose "Start with an empty automation". You are presented with a blank automation screen.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/getting-started/new-automation.png'>
|
||||
|
||||
BIN
source/images/blog/2022-09/automation_editor_new.png
Normal file
BIN
source/images/blog/2022-09/automation_editor_new.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
BIN
source/images/blog/2022-09/automation_overflow.png
Normal file
BIN
source/images/blog/2022-09/automation_overflow.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 76 KiB |
BIN
source/images/blog/2022-09/automation_state_selector.gif
Normal file
BIN
source/images/blog/2022-09/automation_state_selector.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 624 KiB |
BIN
source/images/blog/2022-09/bluetooth-proxy-overview.png
Normal file
BIN
source/images/blog/2022-09/bluetooth-proxy-overview.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 83 KiB |
BIN
source/images/blog/2022-09/create_schedule.gif
Normal file
BIN
source/images/blog/2022-09/create_schedule.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.9 MiB |
BIN
source/images/blog/2022-09/hardware_page.png
Normal file
BIN
source/images/blog/2022-09/hardware_page.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 120 KiB |
BIN
source/images/blog/2022-09/social.png
Normal file
BIN
source/images/blog/2022-09/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 248 KiB |
BIN
source/images/blog/2022-09/zigbee.png
Normal file
BIN
source/images/blog/2022-09/zigbee.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 58 KiB |
BIN
source/images/blog/2022-09/zwave_updates.png
Normal file
BIN
source/images/blog/2022-09/zwave_updates.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
24
source/more-info/unsupported/cgroup_version.markdown
Normal file
24
source/more-info/unsupported/cgroup_version.markdown
Normal file
@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "CGroup Version"
|
||||
description: "More information on why CGroup version marks the installation as unsupported."
|
||||
---
|
||||
|
||||
## The issue
|
||||
|
||||
Supervisor depends on a particular version of Docker CGroup to be in use since
|
||||
it depends on its features to work properly.
|
||||
|
||||
Currently Supervisor requires CGroup v1 in a supervised installation.
|
||||
|
||||
However, the feature set changes and improves over time and therefore, the minimal
|
||||
required version may change in the future. When that happens, it will be communicated
|
||||
before we publish a version that will require you to upgrade CGroups.
|
||||
|
||||
## The solution
|
||||
|
||||
In a supervised installation if you have switched to CGroup v2 you will need to
|
||||
revert what you did. Or you can re-run the [supervised installer](https://github.com/home-assistant/supervised-installer)
|
||||
to fix it.
|
||||
|
||||
You should never see this issue on Home Assistant OS as all versions of the OS
|
||||
ship with a supported CGroup version.
|
||||
17
source/more-info/unsupported/connectivity_check.markdown
Normal file
17
source/more-info/unsupported/connectivity_check.markdown
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
title: "Connectivity check"
|
||||
description: "More information on why disabling Network Manager's connectivity check marks the installation as unsupported."
|
||||
---
|
||||
|
||||
## The issue
|
||||
|
||||
Home Assistant needs to know when it has a stable network connection in order to disable functionality which requires that.
|
||||
Without this check you will face an increased number of errors and performance issues due to connection timeouts.
|
||||
|
||||
## The solution
|
||||
|
||||
From the host shell execute the following command to re-enable Network Manager's connectivity check:
|
||||
|
||||
```sh
|
||||
busctl set-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager ConnectivityCheckEnabled b true
|
||||
```
|
||||
@ -8,7 +8,7 @@ description: "More information on why Docker version marks the installation as u
|
||||
The version that is needed by the Supervisor, depends on the features it needs
|
||||
for it to work properly.
|
||||
|
||||
The current minimum supported version of Docker is: `19.03.0`.
|
||||
The current minimum supported version of Docker is: `20.10.17`.
|
||||
|
||||
However, the feature set changes and improves over time and therefore, the minimal
|
||||
required version may change in the future. When that happens, it will be communicated
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user