mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-15 13:26:54 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
a05ce4bc62
2
.github/workflows/add_prs_to_project.yml
vendored
2
.github/workflows/add_prs_to_project.yml
vendored
@ -13,7 +13,7 @@ jobs:
|
||||
- name: Generate app token
|
||||
id: token
|
||||
# Pinned to a specific version of the action for security reasons
|
||||
uses: tibdex/github-app-token@b62528385c34dbc9f38e5f4225ac829252d1ea92 # v1.8.0
|
||||
uses: tibdex/github-app-token@0914d50df753bbc42180d982a6550f195390069f # v2.0.0
|
||||
with:
|
||||
app_id: ${{ secrets.PROJECTS_APP_ID }}
|
||||
private_key: ${{ secrets.PROJECTS_APP_PEM }}
|
||||
|
||||
4
.github/workflows/test.yml
vendored
4
.github/workflows/test.yml
vendored
@ -8,7 +8,7 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v3.6.0
|
||||
uses: actions/checkout@v4.0.0
|
||||
- name: Setting up Node.js
|
||||
uses: actions/setup-node@v3.8.1
|
||||
with:
|
||||
@ -25,7 +25,7 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v3.6.0
|
||||
uses: actions/checkout@v4.0.0
|
||||
- name: Setting up Node.js
|
||||
uses: actions/setup-node@v3.8.1
|
||||
with:
|
||||
|
||||
27
CODEOWNERS
27
CODEOWNERS
@ -23,7 +23,6 @@ source/_integrations/airnow.markdown @asymworks
|
||||
source/_integrations/airq.markdown @Sibgatulin @dl2080
|
||||
source/_integrations/airthings.markdown @danielhiversen
|
||||
source/_integrations/airthings_ble.markdown @vincegio
|
||||
source/_integrations/airtouch4.markdown @LonePurpleWolf
|
||||
source/_integrations/airvisual.markdown @bachya
|
||||
source/_integrations/airvisual_pro.markdown @bachya
|
||||
source/_integrations/airzone.markdown @Noltari
|
||||
@ -124,9 +123,11 @@ source/_integrations/cloudflare.markdown @ludeeus @ctalkington
|
||||
source/_integrations/coinbase.markdown @tombrien
|
||||
source/_integrations/color_extractor.markdown @GenericStudent
|
||||
source/_integrations/comed.markdown @tronikos
|
||||
source/_integrations/comelit.markdown @chemelli74
|
||||
source/_integrations/comfoconnect.markdown @michaelarnauts
|
||||
source/_integrations/command_line.markdown @gjohansson-ST
|
||||
source/_integrations/compensation.markdown @Petro31
|
||||
source/_integrations/coned.markdown @tronikos
|
||||
source/_integrations/config.markdown @home-assistant/core
|
||||
source/_integrations/configurator.markdown @home-assistant/core
|
||||
source/_integrations/control4.markdown @lawtancool
|
||||
@ -164,7 +165,6 @@ source/_integrations/digital_ocean.markdown @fabaff
|
||||
source/_integrations/discogs.markdown @thibmaek
|
||||
source/_integrations/discord.markdown @tkdrob
|
||||
source/_integrations/discovergy.markdown @jpbede
|
||||
source/_integrations/discovery.markdown @home-assistant/core
|
||||
source/_integrations/dlink.markdown @tkdrob
|
||||
source/_integrations/dlna_dmr.markdown @StevenLooman @chishm
|
||||
source/_integrations/dlna_dms.markdown @chishm
|
||||
@ -175,9 +175,8 @@ source/_integrations/dormakaba_dkey.markdown @emontnemery
|
||||
source/_integrations/dremel_3d_printer.markdown @tkdrob
|
||||
source/_integrations/dsmr.markdown @Robbie1221 @frenck
|
||||
source/_integrations/dsmr_reader.markdown @depl0y @glodenox
|
||||
source/_integrations/dunehd.markdown @bieniu
|
||||
source/_integrations/duotecno.markdown @cereal2nd
|
||||
source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @Hummel95 @andarotajo
|
||||
source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @andarotajo
|
||||
source/_integrations/dynalite.markdown @ziv1234
|
||||
source/_integrations/easyenergy.markdown @klaasnicolaas
|
||||
source/_integrations/ecobee.markdown @marthoc @marcolivierarsenault
|
||||
@ -203,7 +202,7 @@ source/_integrations/energy.markdown @home-assistant/core
|
||||
source/_integrations/energyzero.markdown @klaasnicolaas
|
||||
source/_integrations/enigma2.markdown @fbradyirl
|
||||
source/_integrations/enocean.markdown @bdurrer
|
||||
source/_integrations/enphase_envoy.markdown @gtdiehl
|
||||
source/_integrations/enphase_envoy.markdown @bdraco @cgarwood @dgomes @joostlek
|
||||
source/_integrations/entur_public_transport.markdown @hfurubotten
|
||||
source/_integrations/environment_canada.markdown @gwww @michaeldavie
|
||||
source/_integrations/envisalink.markdown @ufodone
|
||||
@ -309,6 +308,8 @@ source/_integrations/home_plus_control.markdown @chemaaa
|
||||
source/_integrations/homeassistant.markdown @home-assistant/core
|
||||
source/_integrations/homeassistant_alerts.markdown @home-assistant/core
|
||||
source/_integrations/homeassistant_hardware.markdown @home-assistant/core
|
||||
source/_integrations/homeassistant_sky_connect.markdown @home-assistant/core
|
||||
source/_integrations/homeassistant_yellow.markdown @home-assistant/core
|
||||
source/_integrations/homekit.markdown @bdraco
|
||||
source/_integrations/homekit_controller.markdown @Jc2k @bdraco
|
||||
source/_integrations/homematic.markdown @pvizeli @danielperna84
|
||||
@ -351,7 +352,7 @@ source/_integrations/intesishome.markdown @jnimmo
|
||||
source/_integrations/ios.markdown @robbiet480
|
||||
source/_integrations/iotawatt.markdown @gtdiehl @jyavenard
|
||||
source/_integrations/iperf3.markdown @rohankapoorcom
|
||||
source/_integrations/ipma.markdown @dgomes @abmantis
|
||||
source/_integrations/ipma.markdown @dgomes
|
||||
source/_integrations/iqvia.markdown @bachya
|
||||
source/_integrations/irish_rail_transport.markdown @ttroy50
|
||||
source/_integrations/islamic_prayer_times.markdown @engrbm87
|
||||
@ -386,6 +387,7 @@ source/_integrations/landisgyr_heat_meter.markdown @vpathuis
|
||||
source/_integrations/lastfm.markdown @joostlek
|
||||
source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol
|
||||
source/_integrations/laundrify.markdown @xLarry
|
||||
source/_integrations/lawn_mower.markdown @home-assistant/core
|
||||
source/_integrations/lcn.markdown @alengwenus
|
||||
source/_integrations/ld2410_ble.markdown @930913
|
||||
source/_integrations/led_ble.markdown @bdraco
|
||||
@ -421,6 +423,7 @@ source/_integrations/mastodon.markdown @fabaff
|
||||
source/_integrations/matter.markdown @home-assistant/matter
|
||||
source/_integrations/mazda.markdown @bdr99
|
||||
source/_integrations/meater.markdown @Sotolotl @emontnemery
|
||||
source/_integrations/media_extractor.markdown @joostlek
|
||||
source/_integrations/media_player.markdown @home-assistant/core
|
||||
source/_integrations/media_source.markdown @hunterjm
|
||||
source/_integrations/mediaroom.markdown @dgomes
|
||||
@ -521,6 +524,7 @@ source/_integrations/opnsense.markdown @mtreinish
|
||||
source/_integrations/opower.markdown @tronikos
|
||||
source/_integrations/oralb.markdown @bdraco @Lash-L
|
||||
source/_integrations/oru.markdown @bvlaicu
|
||||
source/_integrations/oru_opower.markdown @tronikos
|
||||
source/_integrations/otbr.markdown @home-assistant/core
|
||||
source/_integrations/overkiz.markdown @imicknl @vlebourl @tetienne @nyroDev
|
||||
source/_integrations/ovo_energy.markdown @timmo001
|
||||
@ -591,7 +595,6 @@ source/_integrations/renson.markdown @jimmyd-be
|
||||
source/_integrations/reolink.markdown @starkillerOG
|
||||
source/_integrations/repairs.markdown @home-assistant/core
|
||||
source/_integrations/repetier.markdown @MTrab @ShadowBr0ther
|
||||
source/_integrations/rest.markdown @epenet
|
||||
source/_integrations/rexel.markdown @imicknl @vlebourl @tetienne @nyroDev
|
||||
source/_integrations/rflink.markdown @javicalle
|
||||
source/_integrations/rfxtrx.markdown @danielhiversen @elupus @RobBie1221
|
||||
@ -607,7 +610,7 @@ source/_integrations/roon.markdown @pavoni
|
||||
source/_integrations/rpi_power.markdown @shenxn @swetoast
|
||||
source/_integrations/rss_feed_template.markdown @home-assistant/core
|
||||
source/_integrations/rtsp_to_webrtc.markdown @allenporter
|
||||
source/_integrations/ruckus_unleashed.markdown @gabe565
|
||||
source/_integrations/ruckus_unleashed.markdown @gabe565 @lanrat
|
||||
source/_integrations/ruuvi_gateway.markdown @akx
|
||||
source/_integrations/ruuvitag_ble.markdown @akx
|
||||
source/_integrations/rympro.markdown @OnFreund @elad-bar @maorcc
|
||||
@ -617,8 +620,9 @@ 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/schlage.markdown @dknowles2
|
||||
source/_integrations/schluter.markdown @prairieapps
|
||||
source/_integrations/scrape.markdown @fabaff @gjohansson-ST @epenet
|
||||
source/_integrations/scrape.markdown @fabaff @gjohansson-ST
|
||||
source/_integrations/screenaway.markdown @starkillerOG
|
||||
source/_integrations/screenlogic.markdown @dieselrabbit @bdraco
|
||||
source/_integrations/script.markdown @home-assistant/core
|
||||
@ -708,7 +712,7 @@ 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/switchbee.markdown @jafar-atili
|
||||
source/_integrations/switchbot.markdown @bdraco @danielhiversen @RenierM26 @murtas @Eloston @dsypniewski
|
||||
source/_integrations/switchbot.markdown @danielhiversen @RenierM26 @murtas @Eloston @dsypniewski
|
||||
source/_integrations/switcher_kis.markdown @thecode
|
||||
source/_integrations/switchmate.markdown @danielhiversen @qiz-li
|
||||
source/_integrations/symfonisk.markdown @cgtobi @jjlawren
|
||||
@ -748,6 +752,7 @@ source/_integrations/tplink.markdown @rytilahti @thegardenmonkey
|
||||
source/_integrations/tplink_omada.markdown @MarkGodwin
|
||||
source/_integrations/traccar.markdown @ludeeus
|
||||
source/_integrations/tractive.markdown @Danielhiversen @zhulik @bieniu
|
||||
source/_integrations/trafikverket_camera.markdown @gjohansson-ST
|
||||
source/_integrations/trafikverket_ferry.markdown @gjohansson-ST
|
||||
source/_integrations/trafikverket_train.markdown @endor-force @gjohansson-ST
|
||||
source/_integrations/trafikverket_weatherstation.markdown @endor-force @gjohansson-ST
|
||||
@ -787,6 +792,7 @@ source/_integrations/vilfo.markdown @ManneW
|
||||
source/_integrations/vivotek.markdown @HarlemSquirrel
|
||||
source/_integrations/vizio.markdown @raman325
|
||||
source/_integrations/vlc_telnet.markdown @rodripf @MartinHjelmare
|
||||
source/_integrations/vodafone_station.markdown @paoloantinori @chemelli74
|
||||
source/_integrations/voice_assistant.markdown @balloob @synesthesiam
|
||||
source/_integrations/voip.markdown @balloob @synesthesiam
|
||||
source/_integrations/volumio.markdown @OnFreund
|
||||
@ -829,6 +835,7 @@ 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/yardian.markdown @h3l1o5
|
||||
source/_integrations/yeelight.markdown @zewelor @shenxn @starkillerOG @alexyao2015
|
||||
source/_integrations/yeelightsunflower.markdown @lindsaymarkward
|
||||
source/_integrations/yi.markdown @bachya
|
||||
|
||||
@ -27,7 +27,7 @@ GEM
|
||||
ffi (1.15.5)
|
||||
ffi (1.15.5-x64-mingw32)
|
||||
forwardable-extended (2.6.0)
|
||||
google-protobuf (3.24.2)
|
||||
google-protobuf (3.24.3)
|
||||
http_parser.rb (0.8.0)
|
||||
i18n (1.14.1)
|
||||
concurrent-ruby (~> 1.0)
|
||||
|
||||
@ -109,9 +109,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 2023
|
||||
current_minor_version: 8
|
||||
current_patch_version: 4
|
||||
date_released: 2023-08-24
|
||||
current_minor_version: 9
|
||||
current_patch_version: 2
|
||||
date_released: 2023-09-12
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
10
package-lock.json
generated
10
package-lock.json
generated
@ -23,7 +23,7 @@
|
||||
"textlint": "^13.3.3",
|
||||
"textlint-filter-rule-comments": "^1.2.2",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^3.0.5"
|
||||
"textlint-rule-terminology": "^4.0.0"
|
||||
}
|
||||
},
|
||||
"node_modules/@aashutoshrathi/word-wrap": {
|
||||
@ -4069,9 +4069,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/textlint-rule-terminology": {
|
||||
"version": "3.0.5",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.5.tgz",
|
||||
"integrity": "sha512-IZw8byc4GjyccNjGwSMfy5OSxvjwTGk3IK3qMw2rJ0fsgCYQVlx5JThEQrs4CbWNQN6k2hAinIlxTzxgR00Hmw==",
|
||||
"version": "4.0.0",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-4.0.0.tgz",
|
||||
"integrity": "sha512-tbNpzDNLTVsqtDIMXEZNX2i1dvOqryME8Hknopq6Ze3TAjij5N0wBtG63frZLxJ9auE9fZse15sTi4Qe3arNZA==",
|
||||
"dev": true,
|
||||
"dependencies": {
|
||||
"lodash": "^4.17.15",
|
||||
@ -4079,7 +4079,7 @@
|
||||
"textlint-rule-helper": "^2.1.1"
|
||||
},
|
||||
"engines": {
|
||||
"node": ">=14"
|
||||
"node": ">=18"
|
||||
}
|
||||
},
|
||||
"node_modules/textlint-rule-terminology/node_modules/textlint-rule-helper": {
|
||||
|
||||
@ -18,7 +18,7 @@
|
||||
"textlint": "^13.3.3",
|
||||
"textlint-filter-rule-comments": "^1.2.2",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^3.0.5"
|
||||
"textlint-rule-terminology": "^4.0.0"
|
||||
},
|
||||
"resolutions": {
|
||||
"minimist": ">=1.2.5"
|
||||
|
||||
@ -9,7 +9,8 @@ One major advantage of Home Assistant is that it is not dependent on cloud servi
|
||||
|
||||
Here's the summary of what you *must* do to secure your Home Assistant system:
|
||||
|
||||
- Configure [secrets](/docs/configuration/secrets/) (but do remember to back them up)
|
||||
- Centralize sensitive data in [secrets](/docs/configuration/secrets/) (but do remember to back them up)
|
||||
- **Note**: Storing secrets in `secrets.yaml` does not encrypt them.
|
||||
- Regularly keep the system up to date
|
||||
|
||||
## Remote Access
|
||||
|
||||
@ -104,22 +104,22 @@ The first thing you will need before reporting an issue online is debug logs and
|
||||
|
||||
### Enabling Debug Logging
|
||||
|
||||
To enable debug logging for an integration, go to **Settings** > **Devices & Services** and select the integration. Select the triple dots for the integration giving you trouble and select **Enable Debug Logging**.
|
||||
To enable debug logging for an integration, go to **Settings** > **Devices & Services** > **Integrations** and go to the detail page of the integration. Select the **Enable Debug Logging** button on the left side of the integration detail page.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/docs/configuration/enable-debug-logging.png' alt='Example of Enable debug logging'>
|
||||
Example of Enable debug logging.
|
||||
</p>
|
||||
|
||||
### Disable Debug Logging and Download Logs
|
||||
|
||||
Once you enable debug logging, you ideally need to make the error happen. Run your automation, change up your device or whatever was giving you an error and then come back and disable Debug Logging. Disabling debug logging is the same as enabling, but now you will see **Disable Debug Logging**. After you disable debug logging, it will automatically prompt you to download your log file. Save this to a safe location to upload later.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/docs/configuration/disable-debug-logging.gif' alt='Example of Disable Debug Logging'>
|
||||
Example of Disable Debug Logging.
|
||||
</p>
|
||||
Once you enable debug logging, you ideally need to make the error happen. Run your automation, change up your device or whatever was giving you an error and then come back and disable the debug logging. Disabling the debug logging is the same as enabling, but now the button says **Disable Debug Logging**. After you disable it, you will be automatically prompted you to download your log file. Save this to a safe location to upload later.
|
||||
|
||||
### Download Diagnostics
|
||||
|
||||
After you download logs, you will also want to download the diagnostics for the integration giving you trouble. If the integration provides diagnostics, it will appear in the same menu that the Debug Logging toggle appeared.
|
||||
After you download logs, you will also want to download the diagnostics for the integration giving you trouble. If the integration provides diagnostics, it will appear in the three dot menu next to the integration configuration.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/docs/configuration/download-diagnostics.gif' alt='Example of Download Diagnostics'>
|
||||
<img src='/images/docs/configuration/download-diagnostics.png' alt='Example of Download Diagnostics'>
|
||||
Example of Download Diagnostics.
|
||||
</p>
|
||||
|
||||
@ -24,6 +24,9 @@ Alternatively, the following shops sell ESPHome-based devices, that use a proxim
|
||||
- [Slimme Watermeter Gateway](https://smartgateways.nl/product/slimme-watermeter-gateway/) (Dutch)
|
||||
- [watermeterkit.nl](https://watermeterkit.nl/) (Dutch)
|
||||
|
||||
Alternatively, the following shops sell ESPHome-based devices that use a 3-phase light sensor to detect a rotating disk in your water meter and convert this to the amount of water used in milliliters (ml).
|
||||
- [Muino water meter reader](https://watermeter.muino.nl/)
|
||||
|
||||
Maybe you like to build one yourself?
|
||||
- Pieter Brinkman has quite a [nice blog article on how to create your own water sensor](https://www.pieterbrinkman.com/2022/02/02/build-a-cheap-water-usage-sensor-using-esphome-home-assistant-and-a-proximity-sensor/) using ESPHome, or [build a water meter](https://www.ztatz.nl/p1-monitor-watermeter/) that works with the [P1 Monitor](/integrations/p1_monitor) integration.
|
||||
- [AI-on-the-edge-device](https://github.com/jomjol/AI-on-the-edge-device) is a project running on an ESP32-CAM and can be fully integrated into Home Assistant using the Home Assistant Discovery Functionality of MQTT. It digitalizes your gas/water/electricity meter display and provides its data in various ways.
|
||||
|
||||
@ -27,6 +27,8 @@ Users should upgrade the firmware on all 700 series controllers to version 7.17.
|
||||
- Aeotec Z-Stick 7 USB stick (ZWA010) (the EU version is not recommended due to RF performance issues)
|
||||
- Silicon Labs UZB-7 USB Stick (Silabs SLUSB7000A / SLUSB001A)
|
||||
- Zooz S2 Stick 700 (ZST10 700)
|
||||
- HomeSeer SmartStick+ G3
|
||||
- HomeSeer Z-NET G3
|
||||
|
||||
- 500 series controllers
|
||||
- Aeotec Z-Stick Gen5 (see note below)
|
||||
@ -35,6 +37,8 @@ Users should upgrade the firmware on all 700 series controllers to version 7.17.
|
||||
- Sigma Designs UZB stick
|
||||
- Vision USB stick - Gen5
|
||||
- Z-Wave.Me UZB1 stick
|
||||
- HomeSeer SmartStick+ G2
|
||||
- HomeSeer Z-NET G2
|
||||
|
||||
- Raspberry Pi modules
|
||||
- Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025, 700 series)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
## Backups
|
||||
|
||||
Backup of your Home Assistant and add-on data and configuration. They are stored in a compressed archive file (.tar). Backups are made from the Supervisor Backups panel. There is also a service available that allows you to trigger the creation of a backup from an automation. Backups are stored in the `/backup` directory.
|
||||
Backup of your Home Assistant and add-on data and configuration. They are stored in a compressed archive file (.tar). Backups are made from the backups panel under {% my supervisor_backups title="**Settings** > **System** > **Backups**" %}. There is also a service available that allows you to trigger the creation of a backup from an automation. By default, backups are stored locally in the `/backup` directory.
|
||||
|
||||
A full backup includes the following directories:
|
||||
|
||||
@ -12,16 +12,50 @@ A full backup includes the following directories:
|
||||
|
||||
A partial backup consists of any number of the above default directories and installed add-ons.
|
||||
|
||||
### Making a Backup from the UI
|
||||
### Making a backup from the UI
|
||||
|
||||
1. Go to {% my supervisor_backups title="Settings > System > Backups" %} in the UI.
|
||||
2. Click the **Create backup** button in the lower right.
|
||||
1. Go to {% my supervisor_backups title="**Settings** > **System** > **Backups**" %} in the UI.
|
||||
2. Select the **Create backup** button in the lower right.
|
||||
3. Provide a name for the backup.
|
||||
4. Choose full or partial.
|
||||
5. Choose to password protect or not. Password-protected backups cannot easily be browsed outside of Home Assistant OS.
|
||||
6. Click "Create" to begin the backup.
|
||||
5. Optionally, enable password protection.
|
||||
6. Select **Create** to begin the backup.
|
||||
|
||||
### Restoring a Backup on a new install
|
||||
### Alternative: Creating a backup using the Home Assistant Command Line Interface
|
||||
|
||||
1. `ha backups list` - lists backups and their slugnames
|
||||
2. `ha backups restore slugname` - restores a specific backup
|
||||
3. `ha backups new --name nameofbackup` - create a backup
|
||||
|
||||
Use `ha help` to get more information about the command line usage.
|
||||
|
||||
### Copying your backups to another location
|
||||
|
||||
You might need a backup in case your system has crashed. If you only store them on the device itself, you won't be able to access them easily. We recommend that you copy them from `/backup` to another machine on occasion.
|
||||
|
||||
There are multiple ways to store the backup on another device:
|
||||
|
||||
- **Option 1**: Under {% my supervisor_backups title="**Settings** > **System** > **Backups**" %}, select the backup from the list.
|
||||
- In the dialog, select the three dots menu and select **Download backup**.
|
||||
- **Result**: The selected backup is stored in the **Downloads** folder of your computer.
|
||||
- **Option 2**: If you haven't already done so, [configure access to files on Home Assistant](/common-tasks/{{page.installation}}/#configuring-access-to-files), using one of the methods listed there.
|
||||
- For example, [use the samba add-on](/common-tasks/{{page.installation}}/#installing-and-using-the-samba-add-on).
|
||||
- In your file explorer, access Home Assistant, open the `backup` folder and copy the file to your computer.
|
||||
- **Option 3**: You can also change the default location for backups:
|
||||
- [Add a network storage location](/common-tasks/{{page.installation}}/#network-storage) for backups.
|
||||
- [Change the default location](/common-tasks/{{page.installation}}/#change-default-backup-location) for backups.
|
||||
|
||||
- **Option 4**: Or even better, create an automation to handle that.
|
||||
- **Option 5**: Make use of a third-party add-on:
|
||||
- [Google Drive Backup](https://github.com/sabeechen/hassio-google-drive-backup)
|
||||
- [Dropbox Sync](https://github.com/danielwelch/hassio-dropbox-sync)
|
||||
- [OneDrive Backup](https://github.com/lavinir/hassio-onedrive-backup)
|
||||
- [Nextcloud Backup](https://github.com/Sebclem/hassio-nextcloud-backup)
|
||||
- [Remote Backup (scp/rsync/rclone)](https://github.com/ikifar2012/remote-backup-addon)
|
||||
- [Samba backup](https://github.com/thomasmauerer/hassio-addons/tree/master/samba-backup)
|
||||
- [Syncthing](https://github.com/Poeschl/Hassio-Addons/tree/main/syncthing)
|
||||
|
||||
### Restoring a backup
|
||||
|
||||
You can make use of backup which you have copied off of a previous install to restore to a new installation during the onboarding process. Follow the link at the bottom of the account creation page to upload your backup from the previous installation.
|
||||
|
||||
@ -39,24 +73,3 @@ The length of time it takes to create or restore backup will depend on how much
|
||||
If you're looking to slim down your backup, check if your configuration directory contains a large database file (`home-assistant_v2.db`). See the [`recorder`](/integrations/recorder/) integration page for options to keep your database data down to a size that won't cause issues. Note the keep days, purge interval, and include/exclude options.
|
||||
|
||||
When the restore is complete, Home Assistant will restart to apply the new settings. You will lose the connection to the UI and it will return once the restart is completed.
|
||||
|
||||
### Creating backup using the Home Assistant Command Line Interface
|
||||
|
||||
1. `ha backups list` - lists backups and their slugnames
|
||||
2. `ha backups restore slugname` - restores a specific backup
|
||||
3. `ha backups new --name nameofbackup` - create a backup
|
||||
|
||||
Use `ha help` to get more information about the command line usage.
|
||||
|
||||
|
||||
### Copying your backups to another location
|
||||
|
||||
You often need a backup in case your system has crashed. If you only store them on the crashed device, you won't be able to access them easily. We recommend that you manually copy them from `/backup` to another machine on occasion. Or even better, create an automation to handle that, or make use of one of the following add-ons:
|
||||
|
||||
- [Google Drive Backup](https://github.com/sabeechen/hassio-google-drive-backup)
|
||||
- [Dropbox Sync](https://github.com/danielwelch/hassio-dropbox-sync)
|
||||
- [OneDrive Backup](https://github.com/lavinir/hassio-onedrive-backup)
|
||||
- [Nextcloud Backup](https://github.com/Sebclem/hassio-nextcloud-backup)
|
||||
- [Remote Backup (scp/rsync/rclone)](https://github.com/ikifar2012/remote-backup-addon)
|
||||
- [Samba backup](https://github.com/thomasmauerer/hassio-addons/tree/master/samba-backup)
|
||||
- [Syncthing](https://github.com/Poeschl/Hassio-Addons/tree/main/syncthing)
|
||||
|
||||
@ -15,7 +15,7 @@ If you are using Docker then you need to be on at least version 19.03.9, ideally
|
||||
|
||||
Installation with Docker is straightforward. Adjust the following command so that:
|
||||
|
||||
- `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration and run it.
|
||||
- `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration and run it. Make sure that you keep the `:/config` part.
|
||||
- `MY_TIME_ZONE` is a [tz database name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), like `TZ=America/Los_Angeles`.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@ -34,7 +34,7 @@ To use a Z-Wave USB stick for Z-Wave control, the HA Docker container needs extr
|
||||
|
||||
Adjust the following Terminal command as follows :
|
||||
|
||||
- Replace `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration
|
||||
- Replace `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration - make sure that you keep the `:/config` part
|
||||
- Replace `/PATH_TO_YOUR_USB_STICK` matches the path for your USB stick (e.g., `/dev/ttyACM0` for most Synology users)
|
||||
- Replace "Australia/Melbourne" with [your timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
|
||||
|
||||
|
||||
@ -22,9 +22,10 @@ The local integrations only works with newer Adax heaters with both Bluetooth an
|
||||
|
||||
For the cloud integration, you'll need the Account ID (which can be found in the Adax Wifi app, pressing 'Account'). You will also need a credential, which you can create in the Adax app:
|
||||
|
||||
1. Navigate to Account Tab,
|
||||
2. Select “Remote user client API”
|
||||
3. Select “Add Credential”
|
||||
4. Give some name to the created credential and copy the generated password.
|
||||
1. Navigate to the Account tab.
|
||||
2. Go to **Third party integrations**.
|
||||
3. Select **Remote API**.
|
||||
4. Select **Add Credential**.
|
||||
5. Give some name to the created credential (e.g. 'Home Assistant') and copy the generated password.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -6,8 +6,6 @@ ha_category:
|
||||
ha_release: 2021.9
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@LonePurpleWolf'
|
||||
ha_domain: airtouch4
|
||||
ha_platforms:
|
||||
- climate
|
||||
|
||||
@ -292,4 +292,23 @@ but you will still receive the done message.
|
||||
entity_id: alert.garage_door
|
||||
```
|
||||
|
||||
Notifications sent to Home Assistant Companion apps support [replacing](https://companion.home-assistant.io/docs/notifications/notifications-basic/#replacing) and [clearing](https://companion.home-assistant.io/docs/notifications/notifications-basic/#replacing) notifications. To use these functions with alerts, set a `tag` in the message data, send `clear_notification` as the `done_message`, and use `mobile_app_*` as the notifier:
|
||||
|
||||
```yaml
|
||||
alert:
|
||||
garage_door:
|
||||
name: Garage is open
|
||||
done_message: clear_notification
|
||||
entity_id: input_boolean.garage_door
|
||||
state: "on"
|
||||
repeat: 30
|
||||
can_acknowledge: true
|
||||
skip_first: true
|
||||
notifiers:
|
||||
- mobile_app_ryan
|
||||
- mobile_app_kristen
|
||||
data:
|
||||
tag: garage-door
|
||||
```
|
||||
|
||||
[template]: /docs/configuration/templating/
|
||||
|
||||
@ -30,9 +30,9 @@ For a quick introduction on how to get started with Android TV Remote, check out
|
||||
|
||||
## Media player
|
||||
|
||||
This integration adds a `media_player` with basic playback and volume controls. The media player provides volume information and display name of current active app on the Android TV. Due to API limitations, the integration will not display the playback status. It is recommended to use this integration together with [Google Cast integration](https://www.home-assistant.io/integrations/cast/). Two media players can be combined into one using the [Universal Media Player](https://www.home-assistant.io/integrations/universal/) integration.
|
||||
This integration adds a `media_player` with basic playback and volume controls. The media player provides volume information and display name of current active app on the Android TV. Due to API limitations, the integration will not display the playback status. It is recommended to use this integration together with [Google Cast integration](/integrations/cast/). Two media players can be combined into one using the [Universal Media Player](/integrations/universal/) integration. See [Using with Google Cast](#using-with-google-cast) section for more details.
|
||||
|
||||
Using the `media_player.play_media` service, you can launch applications via `Deep Links` and switch channels.
|
||||
Using the `media_player.play_media` service, you can launch applications via `Deep Links` and switch channels. Only `url` and `channel` media types are supported.
|
||||
|
||||
### Launching apps
|
||||
|
||||
@ -72,7 +72,7 @@ target:
|
||||
|
||||
### Switch channels
|
||||
|
||||
You can pass the channel number to switch the channel. The channel number must be an integer.
|
||||
You can pass the channel number to switch channels. The channel number must be an integer.
|
||||
|
||||
Example:
|
||||
|
||||
@ -86,6 +86,46 @@ target:
|
||||
entity_id: media_player.living_room_tv
|
||||
```
|
||||
|
||||
### Using with Google Cast
|
||||
|
||||
Android TV Remote integration provides information about the power status of the device and gives you the ability to control playback. However, it does not provide information about the currently playing content (media title, duration, play/pause state, etc.). In turn, [Google Cast](/integrations/cast/) integration does not provide reliable information about the power status of the device (e.g. on Android TV Home Screen) and does not allow to control playback in Android apps without [MediaSession](https://developer.android.com/reference/android/media/session/MediaSession) support. However, it can display full information about the content being played in supported apps. For convenience, you can combine two media players into one using [Universal Media Player](/integrations/universal/) integration. Universal Media Player will automatically select the appropriate active media player entity.
|
||||
|
||||
{% details "Example YAML configuration" %}
|
||||
|
||||
Replace `media_player.living_room_tv_remote` with your Android TV Remote media player entity ID.
|
||||
Replace `media_player.living_room_tv_cast` with your Google Cast media player entity ID.
|
||||
|
||||
```yaml
|
||||
media_player:
|
||||
- platform: universal
|
||||
name: living_room_tv
|
||||
unique_id: living_room_tv
|
||||
device_class: tv
|
||||
children:
|
||||
- media_player.living_room_tv_remote
|
||||
- media_player.living_room_tv_cast
|
||||
browse_media_entity: media_player.living_room_tv_cast
|
||||
commands:
|
||||
turn_off:
|
||||
service: media_player.turn_off
|
||||
data:
|
||||
entity_id: media_player.living_room_tv_remote
|
||||
turn_on:
|
||||
service: media_player.turn_on
|
||||
data:
|
||||
entity_id: media_player.living_room_tv_remote
|
||||
volume_up:
|
||||
service: media_player.volume_up
|
||||
data:
|
||||
entity_id: media_player.living_room_tv_remote
|
||||
volume_down:
|
||||
service: media_player.volume_down
|
||||
data:
|
||||
entity_id: media_player.living_room_tv_remote
|
||||
```
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
## Remote
|
||||
|
||||
The remote allows you to send key commands to your Android TV device with the `remote.send_command` service.
|
||||
|
||||
@ -22,7 +22,8 @@ To use Apprise supported notifications, add the following to your `configuration
|
||||
```yaml
|
||||
# Example configuration.yaml entry using URLs
|
||||
notify:
|
||||
- platform: apprise
|
||||
- name: NOTIFIER_NAME
|
||||
platform: apprise
|
||||
url: YOUR_APPRISE_URLS
|
||||
```
|
||||
|
||||
@ -32,7 +33,8 @@ You can also pre-define your own configuration files while storing them either r
|
||||
# Example configuration.yaml entry using externally located Apprise
|
||||
# Configuration Files/Sites:
|
||||
notify:
|
||||
- platform: apprise
|
||||
- name: NOTIFIER_NAME
|
||||
platform: apprise
|
||||
config: YOUR_APPRISE_CONFIG_URLS
|
||||
```
|
||||
|
||||
@ -41,7 +43,8 @@ There is no restriction on the number of URLs or Apprise Configuration locations
|
||||
```yaml
|
||||
# Example configuration.yaml entry using all options
|
||||
notify:
|
||||
- platform: apprise
|
||||
- name: NOTIFIER_NAME
|
||||
platform: apprise
|
||||
config: YOUR_APPRISE_CONFIG_URLS
|
||||
url: YOUR_APPRISE_URLS
|
||||
```
|
||||
@ -65,7 +68,7 @@ config:
|
||||
## Example service call
|
||||
|
||||
```yaml
|
||||
- service: notify.apprise
|
||||
- service: notify.NOTIFIER_NAME
|
||||
data:
|
||||
message: "A message from Home Assistant"
|
||||
```
|
||||
@ -73,7 +76,7 @@ config:
|
||||
If you're using configuration files to store your Apprise URLs in, then you have the added bonus of associating tags with them. By default, Apprise in Home Assistant will only notify the elements that have no tags associated with them. You can optionally focus on only notifying a specific service based on the tag(s) you assigned them like so:
|
||||
|
||||
```yaml
|
||||
- service: notify.apprise
|
||||
- service: notify.NOTIFIER_NAME
|
||||
data:
|
||||
message: "A message from Home Assistant"
|
||||
target: [
|
||||
|
||||
@ -60,13 +60,13 @@ Currently the following device types within Home Assistant are supported.
|
||||
### Presence Detection
|
||||
|
||||
- Detect presence of devices connected to the main or the guest wifi
|
||||
- Updates every 10 seconds
|
||||
- Updates every 15 seconds
|
||||
- Automatically adds new devices as disabled entities unless disabled via system option
|
||||
|
||||
### Sensors
|
||||
|
||||
- Number of connected wifi clients
|
||||
- Updates every 10 seconds
|
||||
- Updates every 15 seconds
|
||||
- Is enabled by default
|
||||
- Number of neighbored wifi networks
|
||||
- Updates every 5 minutes
|
||||
|
||||
@ -7,8 +7,6 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.34
|
||||
ha_domain: dunehd
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@bieniu'
|
||||
ha_platforms:
|
||||
- media_player
|
||||
ha_integration_type: integration
|
||||
|
||||
@ -2,9 +2,9 @@
|
||||
title: Duotecno
|
||||
description: Access and control your Duotecno nodes.
|
||||
ha_category:
|
||||
- Switch
|
||||
- Cover
|
||||
- Light
|
||||
- Switch
|
||||
ha_iot_class: Local Push
|
||||
ha_release: '2023.8'
|
||||
ha_config_flow: true
|
||||
|
||||
@ -10,7 +10,6 @@ ha_domain: dwd_weather_warnings
|
||||
ha_codeowners:
|
||||
- '@runningman84'
|
||||
- '@stephan192'
|
||||
- '@Hummel95'
|
||||
- '@andarotajo'
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -10,6 +10,7 @@ ha_codeowners:
|
||||
ha_domain: electric_kiwi
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- select
|
||||
- sensor
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
@ -12,9 +12,8 @@ ha_domain: elmax
|
||||
ha_platforms:
|
||||
- alarm_control_panel
|
||||
- binary_sensor
|
||||
- switch
|
||||
- cover
|
||||
- alarm_control_panel
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: "MQTT Event"
|
||||
description: "Instructions on how to integrate MQTT events into Home Assistant."
|
||||
ha_category:
|
||||
- Event
|
||||
- Events
|
||||
ha_release: 2023.8
|
||||
ha_iot_class: Configurable
|
||||
ha_domain: mqtt
|
||||
@ -221,3 +221,33 @@ The example below demonstrates how event attributes can be added to the event da
|
||||
```bash
|
||||
mosquitto_pub -h 127.0.0.1 -t home/doorbell/state -m '{"event_type": "press", "duration": 0.1}'
|
||||
```
|
||||
|
||||
### Example: processing event data using a value template
|
||||
|
||||
In many cases, translation of an existing published payload is needed.
|
||||
The example config below translates the payload `{"Button1": {"Action": "SINGLE"}}` of
|
||||
the device `Button1` with event type `single` to the required format.
|
||||
An extra attribute `button` will be set to `Button1` and be added to the entity,
|
||||
but only if the `Action` property is set. Empty dictionaries will be ignored.
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
mqtt:
|
||||
- event:
|
||||
name: "Desk button"
|
||||
state_topic: "desk/button/state"
|
||||
event_types:
|
||||
- single
|
||||
- double
|
||||
device_class: "button"
|
||||
value_template: |
|
||||
{ {% for key in value_json %}
|
||||
{% if value_json[key].get("Action") %}
|
||||
"button": "{{ key }}",
|
||||
"event_type": "{{ value_json[key].Action | lower }}"
|
||||
{% endif %}
|
||||
{% endfor %} }
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
@ -26,6 +26,7 @@ ha_codeowners:
|
||||
- '@mib1185'
|
||||
- '@flabbamann'
|
||||
ha_integration_type: hub
|
||||
ha_quality_scale: gold
|
||||
---
|
||||
|
||||
The AVM FRITZ!SmartHome integration for Home Assistant allows you to integrate [FRITZ!DECT](https://en.avm.de/products/smart-home/) devices like switches, sensors and thermostats.
|
||||
@ -43,6 +44,7 @@ Additionally, we also support to trigger smarthome templates.
|
||||
|
||||
#### Tested Devices
|
||||
|
||||
- [FRITZ!Box 5590 Fiber](https://en.avm.de/products/fritzbox/fritzbox-5590-fiber/)
|
||||
- FRITZ!Box 6490 Cable
|
||||
- [FRITZ!Box 6591 Cable](https://en.avm.de/products/fritzbox/fritzbox-6591-cable/)
|
||||
- [FRITZ!Box 7590](https://en.avm.de/products/fritzbox/fritzbox-7590/)
|
||||
|
||||
@ -66,4 +66,4 @@ Gardena Bluetooth lawn mowers are currently not supported due to custom protocol
|
||||
|
||||
### Limitations
|
||||
|
||||
Irrigation valves are currently untested, but expected to work.
|
||||
Irrigation valves are currently untested, but expected to work.
|
||||
|
||||
@ -3,7 +3,6 @@ title: Generic Camera
|
||||
description: Instructions on how to integrate IP cameras within Home Assistant.
|
||||
ha_category:
|
||||
- Camera
|
||||
logo: home-assistant.png
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: generic
|
||||
|
||||
@ -63,4 +63,4 @@ For more detailed steps on how to define a custom polling interval, follow the p
|
||||
|
||||
### Defining a custom polling interval
|
||||
|
||||
{% include common-tasks/define_custom_polling.md %}
|
||||
{% include common-tasks/define_custom_polling.md %}
|
||||
|
||||
@ -85,6 +85,11 @@ If the setup process fails and you see an error message such as *Authentication
|
||||
|
||||
If you have an error with your credentials, you can delete them in the [Application Credentials](/integrations/application_credentials/) user interface.
|
||||
|
||||
### Video Tutorial
|
||||
This video tutorial explains how to set up Google Calendar in Home Assistant and how you can trigger an automation based on a calendar event.
|
||||
|
||||
<lite-youtube videoid="r2WbpxKDOD4" videotitle="How To Use Calendar Events in Home Assistant - Tutorial" posterquality="maxresdefault"></lite-youtube>
|
||||
|
||||
## Calendar Entities
|
||||
|
||||
Each Google Calendar from *My Calendars* ([more info](https://support.google.com/calendar/answer/37095)) is represented as a [calendar](/integrations/calendar) entity in Home Assistant.
|
||||
|
||||
@ -204,6 +204,7 @@ data:
|
||||
## Conversation agent
|
||||
|
||||
You can add an assistant with the conversation agent set to "Google Assistant SDK".
|
||||
See setup your assistant section [here](/voice_control/voice_remote_local_assistant/).
|
||||
Then you can converse with Google Assistant by tapping the Assist icon at the top right of your dashboard:
|
||||
|
||||
|
||||
|
||||
@ -49,14 +49,19 @@ Basic instruction for all APIs:
|
||||
6. Set up authentication:
|
||||
|
||||
1. Visit [this link](https://console.cloud.google.com/apis/credentials/serviceaccountkey)
|
||||
2. From the `Service account` list, select `New service account`.
|
||||
2. From the toolbar above the `Service account` list, select `Create service account`.
|
||||
3. In the `Service account name` field, enter any name.
|
||||
|
||||
If you are requesting a text-to-speech API key:
|
||||
|
||||
4. Don't select a value from the Role list. **No role is required to access this service**.
|
||||
5. Click `Create`. A note appears, warning that this service account has no role.
|
||||
6. Click `Create without role`. A JSON file that contains your `API key` downloads to your computer.
|
||||
5. Click `Create`. If a note appears, warning that this service account has no role, you may ignore that.
|
||||
6. Return to the `Service account` list page and click on the service account you created in step 5 to see the details for this service account.
|
||||
7. Choose the `Keys` tab within the details view for this service account.
|
||||
8. In the `Add Key` dropdown, select `Create New Key`.
|
||||
9. Specify a `JSON` key type and click `Create`.
|
||||
10. A `[serviceaccountname].json` file will download to your browser.
|
||||
|
||||
|
||||
## Google Cloud text-to-speech
|
||||
|
||||
@ -66,10 +71,13 @@ Basic instruction for all APIs:
|
||||
|
||||
The Cloud text-to-speech API is priced monthly based on the amount of characters to synthesize into audio sent to the service.
|
||||
|
||||
| Feature | Monthly free tier | Paid usage |
|
||||
| Voice | Monthly free tier | Paid usage |
|
||||
| ----------------------------- | ------------------------- | --------------------------------- |
|
||||
| Standard (non-WaveNet) voices | 0 to 4 million characters | $4.00 USD / 1 million characters |
|
||||
| WaveNet voices | 0 to 1 million characters | $16.00 USD / 1 million characters |
|
||||
| Neural2 | 0 to 1 million bytes | $16.00 USD / 1 million bytes |
|
||||
| Polyglot (Preview) | 0 to 1 million bytes | $16.00 USD / 1 million bytes |
|
||||
| Studio (Preview) | 0 to 100 thousand bytes | $160.00 USD / 1 million bytes |
|
||||
| Standard | 0 to 4 million characters | $4.00 USD / 1 million characters |
|
||||
| WaveNet | 0 to 1 million characters | $16.00 USD / 1 million characters |
|
||||
|
||||
### Text-to-speech configuration
|
||||
|
||||
|
||||
@ -94,4 +94,4 @@ For more detailed steps on how to define a custom polling interval, follow the p
|
||||
|
||||
### Defining a custom polling interval
|
||||
|
||||
{% include common-tasks/define_custom_polling.md %}
|
||||
{% include common-tasks/define_custom_polling.md %}
|
||||
|
||||
@ -38,6 +38,7 @@ Any Gree Smart device working with the Gree+ app should be supported, including
|
||||
- Proklima
|
||||
- Tadiran
|
||||
- Heiwa
|
||||
- Ekokai
|
||||
|
||||
## Climate
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ description: Instructions on how to setup groups within Home Assistant.
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Cover
|
||||
- Fan
|
||||
- Event
|
||||
- Fan
|
||||
- Helper
|
||||
- Light
|
||||
- Lock
|
||||
|
||||
@ -14,6 +14,12 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
<div class="note warning">
|
||||
|
||||
The Legrand Home+ Control cloud is shutting down in December. Use [the Netatmo integration](/integrations/netatmo/) to integrate your Legrand Home+ Control devices.
|
||||
|
||||
</div>
|
||||
|
||||
The Home+ Control integration platform allows you to control a range of Legrand in-wall switches and power outlets that have smart home functionality thanks to their "with Netatmo" capabilities.
|
||||
|
||||
This integration works against the Home+ Control API, which is one of the many APIs offered through the [*Works with Legrand*](https://developer.legrand.com/) program. The API is capable of managing "Legrand/Btcino with Netatmo" devices, such as light switches, power outlets and rolling shutters.
|
||||
|
||||
20
source/_integrations/homeassistant_sky_connect.markdown
Normal file
20
source/_integrations/homeassistant_sky_connect.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
title: Home Assistant SkyConnect
|
||||
description: Home Assistant SkyConnect provides hardware information for the hardware configuration page.
|
||||
ha_release: 2022.9
|
||||
ha_category:
|
||||
- Other
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: homeassistant_sky_connect
|
||||
ha_integration_type: hardware
|
||||
---
|
||||
|
||||
The Home Assistant SkyConnect integration provides hardware information for the hardware configuration page.
|
||||
|
||||
For documentation on the Home Assistant SkyConnect, please visit the [documentation page](https://skyconnect.home-assistant.io/documentation/).
|
||||
If you are looking to buy one, please visit the [product page](https://home-assistant.io/skyconnect)
|
||||
|
||||
## Configuration
|
||||
|
||||
This integration is not user configurable.
|
||||
20
source/_integrations/homeassistant_yellow.markdown
Normal file
20
source/_integrations/homeassistant_yellow.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
title: Home Assistant Yellow
|
||||
description: Home Assistant Yellow provides hardware information for the hardware configuration page.
|
||||
ha_release: 2022.7
|
||||
ha_category:
|
||||
- Other
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: homeassistant_yellow
|
||||
ha_integration_type: hardware
|
||||
---
|
||||
|
||||
The Home Assistant Yellow integration provides hardware information for the hardware configuration page.
|
||||
|
||||
For documentation on the Home Assistant Yellow, please visit the [documentation](https://yellow.home-assistant.io/documentation/).
|
||||
If you are looking to buy one, please visit the [product page](https://home-assistant.io/yellow).
|
||||
|
||||
## Configuration
|
||||
|
||||
This integration is not user configurable.
|
||||
@ -8,7 +8,6 @@ ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@dgomes'
|
||||
- '@abmantis'
|
||||
ha_domain: ipma
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -89,4 +89,4 @@ For more detailed steps on how to define a custom polling interval, follow the p
|
||||
|
||||
#### Defining a custom polling interval
|
||||
|
||||
{% include common-tasks/define_custom_polling.md %}
|
||||
{% include common-tasks/define_custom_polling.md %}
|
||||
|
||||
@ -21,6 +21,8 @@ The `life360` integration allows you to detect presence using the [unofficial AP
|
||||
You must first [create a Life360 account](https://app.life360.com/sign-up).
|
||||
Individual Members must enable Location Sharing in their Life360 app to show up as a tracked entity in Home Assistant.
|
||||
|
||||
> When adding your Life360 account to Home Assistant, you must use the email address associated with your Life360 account, not the phone number.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
### Account options
|
||||
|
||||
@ -8,6 +8,8 @@ ha_release: 0.49
|
||||
ha_quality_scale: internal
|
||||
ha_domain: media_extractor
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@joostlek'
|
||||
---
|
||||
|
||||
The `media_extractor` integration gets a stream URL and sends it to a media player entity. This integration can extract entity specific streams if configured accordingly.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: modbus
|
||||
title: Modbus
|
||||
description: Instructions on how to integrate modbus and platforms.
|
||||
ha_category:
|
||||
- Hub
|
||||
|
||||
@ -601,6 +601,7 @@ The following software has built-in support for MQTT discovery:
|
||||
- [SpeedTest-CLI MQTT](https://github.com/adorobis/speedtest-CLI2mqtt)
|
||||
- [SwitchBot-MQTT-BLE-ESP32](https://github.com/devWaves/SwitchBot-MQTT-BLE-ESP32)
|
||||
- [Tasmota](https://github.com/arendst/Tasmota) (starting with 5.11.1e, development halted)
|
||||
- [TeddyCloud](https://github.com/toniebox-reverse-engineering/teddycloud)
|
||||
- [Teleinfo MQTT](https://fmartinou.github.io/teleinfo2mqtt) (starting with 3.0.0)
|
||||
- [Tydom2MQTT](https://fmartinou.github.io/tydom2mqtt/)
|
||||
- [What's up Docker?](https://fmartinou.github.io/whats-up-docker/) (starting with 3.5.0)
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Neato Botvac
|
||||
description: Instructions on how to integrate your Neato within Home Assistant.
|
||||
ha_category:
|
||||
- Button
|
||||
- Camera
|
||||
- Sensor
|
||||
- Switch
|
||||
- Button
|
||||
- Vacuum
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.33
|
||||
@ -15,10 +15,10 @@ ha_codeowners:
|
||||
- '@Santobert'
|
||||
ha_domain: neato
|
||||
ha_platforms:
|
||||
- button
|
||||
- camera
|
||||
- sensor
|
||||
- switch
|
||||
- button
|
||||
- vacuum
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -17,7 +17,6 @@ ha_domain: nest
|
||||
ha_quality_scale: platinum
|
||||
ha_dhcp: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- camera
|
||||
- climate
|
||||
- diagnostics
|
||||
|
||||
@ -18,6 +18,7 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- climate
|
||||
- diagnostics
|
||||
- number
|
||||
- scene
|
||||
- sensor
|
||||
- switch
|
||||
@ -100,4 +101,4 @@ Sets the humidify setpoint. This setting will affect all zones on the same therm
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`'s of climate devices to control.
|
||||
| `humidity` | no | Humidify setpoint level, from 35 to 65.
|
||||
| `humidity` | no | Humidify setpoint level, from 35 to 65.
|
||||
|
||||
@ -60,7 +60,7 @@ Alternatively, you can create a new TOTP secret for your account and use the "no
|
||||
|
||||
### Exelon subsidiaries
|
||||
|
||||
When using Opower with any of the Exelon subsidiaries, such as such as BGE, ComEd, PECO, Pepco, etc., you need to actively disable two-factor authentication. Log onto the website, select **Don't use 2FA** and **Don't ask me again**. If you have already enabled 2FA, disable it.
|
||||
When using Opower with any of the Exelon subsidiaries, such as BGE, ComEd, PECO, Pepco, etc., you need to actively disable two-factor authentication. Log onto the website, select **Don't use 2FA** and **Don't ask me again**. If you have already enabled 2FA, disable it.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: Get energy usage from Orange and Rockland Utilities using the Opowe
|
||||
ha_category:
|
||||
- Energy
|
||||
- Sensor
|
||||
ha_release: 2023.9
|
||||
ha_release: 2023.8
|
||||
ha_domain: oru_opower
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: opower
|
||||
|
||||
@ -54,7 +54,6 @@ The Overkiz (by Somfy) integration platform is used by many different vendors, l
|
||||
- Atlantic Cozytouch
|
||||
- Hitachi Hi Kumo
|
||||
- Nexity Eugénie
|
||||
- Rexel Energeasy Connect
|
||||
- Somfy Connectivity Kit
|
||||
- Somfy Connexoon IO
|
||||
- Somfy Connexoon RTS
|
||||
@ -84,7 +83,7 @@ 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. 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.
|
||||
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://github.com/Somfy-Developer/Somfy-TaHoma-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.
|
||||
|
||||
|
||||
@ -272,6 +272,7 @@ Then power up the camera while pointing it at the QR code. It takes about a minu
|
||||
- On some camera models, the RTMP port needs to be enabled in order for the HTTP(S) port to function properly. Make sure this port is also enabled if you get a `Cannot connect to host` error while one of the HTTP/HTTPS ports is already enabled.
|
||||
- Setting a static IP address for Reolink cameras/NVRs in your router is advisable to prevent (temporal) connectivity issues when the IP address changes.
|
||||
- Do not set a static IP in the Reolink device itself, but leave the **Connection Type** on **DHCP** under **Settings** > **Network** > **Network Information** > **Set Up**. If you set it to **static** on the Reolink device itself, this is known to cause incorrect DHCP requests on the network. The incorrect DHCP request causes Home Assistant to use the wrong IP address for the camera, resulting in connection issues. The issue originates from the Reolink firmware, which keeps sending DCHP requests even when you set a static IP address in the Reolink device.
|
||||
- Reolink cameras can support a limited amount of simultaneous connections. Therefore using third-party software like Frigate, Blue Iris, or Scrypted, or using the ONVIF integration at the same time can cause the camera to drop connections. This results in short unavailabilities of the Reolink entities in Home Assistant. Especially when the connections are coming from the same device (IP) where Home Assistant is running, the Reolink cameras can get confused, dropping one connection in favor of the other originating from the same host IP. If you experience disconnections/unavailabilities of the entities, please first temporarily shut down the other connections (like Frigate) to diagnose if that is the problem. If that is indeed the problem, you could try moving the third-party software to a different host (IP address) since that is known to solve the problem most of the time. You could also try switching the protocol to FLV on Home Assistant and/or the third-party software, as that is known to be less resource-intensive on the camera.
|
||||
|
||||
### Reducing latency of motion events
|
||||
|
||||
|
||||
@ -13,8 +13,6 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@epenet'
|
||||
---
|
||||
|
||||
The `rest` sensor platform is consuming a given endpoint which is exposed by a [RESTful API](https://en.wikipedia.org/wiki/Representational_state_transfer) of a device, an application, or a web service. The sensor has support for GET and POST requests.
|
||||
|
||||
@ -8,10 +8,11 @@ ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@gabe565'
|
||||
- '@lanrat'
|
||||
ha_domain: ruckus_unleashed
|
||||
ha_platforms:
|
||||
- device_tracker
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
This platform allows you to connect to a [Ruckus Unleashed](https://support.ruckuswireless.com/product_families/19-ruckus-unleashed) access point.
|
||||
|
||||
@ -16,6 +16,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_domain: schlage
|
||||
---
|
||||
|
||||
The Schlage integration provides connectivity with Schlage WiFi smart locks through Schlage's cloud API.
|
||||
|
||||
@ -8,7 +8,6 @@ ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
- '@gjohansson-ST'
|
||||
- '@epenet'
|
||||
ha_domain: scrape
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -22,7 +22,7 @@ The type of data a sensor returns impacts how it is displayed in the frontend. T
|
||||
- **None**: Generic sensor. This is the default and doesn't need to be set.
|
||||
- **apparent_power**: Apparent power in VA.
|
||||
- **aqi**: Air Quality Index (unitless).
|
||||
- **atmospheric_pressure**: Atmospheric pressure in cbar, bar, hPa, inHg, kPa, mbar, Pa or psi
|
||||
- **atmospheric_pressure**: Atmospheric pressure in cbar, bar, hPa, mmHg, inHg, kPa, mbar, Pa or psi
|
||||
- **battery**: Percentage of battery that is left in %
|
||||
- **carbon_dioxide**: Carbon Dioxide in CO2 (Smoke) in ppm
|
||||
- **carbon_monoxide**: Carbon Monoxide in CO (Gas CNG/LPG) in ppm
|
||||
|
||||
@ -13,7 +13,7 @@ ha_codeowners:
|
||||
- '@G-Two'
|
||||
ha_domain: subaru
|
||||
ha_platforms:
|
||||
- device tracker
|
||||
- device_tracker
|
||||
- diagnostics
|
||||
- lock
|
||||
- sensor
|
||||
|
||||
@ -68,7 +68,7 @@ availability_topic:
|
||||
type: string
|
||||
command_topic:
|
||||
description: The MQTT topic to publish commands to change the switch state.
|
||||
required: false
|
||||
required: true
|
||||
type: string
|
||||
device:
|
||||
description: "Information about the device this switch is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
|
||||
|
||||
@ -11,7 +11,6 @@ ha_category:
|
||||
ha_release: 0.78
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@bdraco'
|
||||
- '@danielhiversen'
|
||||
- '@RenierM26'
|
||||
- '@murtas'
|
||||
|
||||
@ -4,6 +4,7 @@ description: Instructions on how to integrate Template Sensors into Home Assista
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Button
|
||||
- Helper
|
||||
- Image
|
||||
- Number
|
||||
- Select
|
||||
@ -31,7 +32,8 @@ ha_platforms:
|
||||
- switch
|
||||
- vacuum
|
||||
- weather
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: helper
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The `template` integration allows creating entities which derive their values from other data. This is done by specifying [templates](/docs/configuration/templating/) for properties of an entity, like the name or the state.
|
||||
|
||||
22
source/_integrations/ultraloq.markdown
Normal file
22
source/_integrations/ultraloq.markdown
Normal file
@ -0,0 +1,22 @@
|
||||
---
|
||||
title: Ultraloq
|
||||
description: Connect and control your Ultraloq Z-Wave series devices using the Z-Wave integration
|
||||
ha_release: '2022.11'
|
||||
ha_category:
|
||||
- Lock
|
||||
ha_domain: ultraloq
|
||||
ha_integration_type: virtual
|
||||
works_with:
|
||||
- zwave
|
||||
ha_iot_standard: zwave
|
||||
---
|
||||
|
||||
Ultraloq smart locks allow users to enter their homes without a key. The lock can be controlled remotely using the Ultraloq app or by using Home Assistant. U-tec, their parent company, is a member of the Works with Home Assistant partner program. This means they are committed to making sure the Ultraloq Z-Wave products are up-to-date and ready to use with Home Assistant.
|
||||
|
||||
Ultraloq Z-Wave Series smart locks work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave stick required).
|
||||
|
||||
To add Ultraloq Z-Wave products, pair them as Z-Wave devices:
|
||||
|
||||
{% my add_zwave_device badge domain=page.ha_domain %}
|
||||
|
||||
[Learn more about Z-Wave in Home Assistant.](/integrations/zwave_js/)
|
||||
@ -12,7 +12,6 @@ ha_codeowners:
|
||||
ha_iot_class: Local Polling
|
||||
ha_platforms:
|
||||
- device_tracker
|
||||
ha_ssdp: false
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
|
||||
@ -81,61 +81,3 @@ use_webhook:
|
||||
default: false
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
## Bonus: Template Sensors to Convert Kilograms to Pounds
|
||||
|
||||
In a text editor, replace ```USER_PROFILE_NAME``` in the template sensors below with your Withings User Profile Name defined in the Withings integration configuration.
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
template:
|
||||
- sensor:
|
||||
- name: Withings weight lbs USER_PROFILE_NAME
|
||||
unit_of_measurement: "lbs"
|
||||
state: >-
|
||||
{{
|
||||
(states('sensor.withings_weight_kg_USER_PROFILE_NAME') | float(0) * 2.20462262185)
|
||||
| round(2, default=0)
|
||||
}}
|
||||
icon: "mdi:weight-pound"
|
||||
|
||||
- name: Withings bone mass lbs USER_PROFILE_NAME
|
||||
unit_of_measurement: "lbs"
|
||||
state: >-
|
||||
{{
|
||||
(states('sensor.withings_bone_mass_kg_USER_PROFILE_NAME') | float(0) * 2.20462262185)
|
||||
| round(2, default=0)
|
||||
}}
|
||||
icon: "mdi:weight-pound"
|
||||
|
||||
- name: Withings fat free mass lbs USER_PROFILE_NAME
|
||||
unit_of_measurement: "lbs"
|
||||
state: >-
|
||||
{{
|
||||
(states('sensor.withings_fat_free_mass_kg_USER_PROFILE_NAME') | float(0) * 2.20462262185)
|
||||
| round(2, default=0)
|
||||
}}
|
||||
icon: "mdi:weight-pound"
|
||||
|
||||
- name: Withings fat mass lbs USER_PROFILE_NAME
|
||||
unit_of_measurement: "lbs"
|
||||
state: >-
|
||||
{{
|
||||
(states('sensor.withings_fat_mass_kg_USER_PROFILE_NAME') | float(0) * 2.20462262185)
|
||||
| round(2, default=0)
|
||||
}}
|
||||
icon: "mdi:weight-pound"
|
||||
|
||||
- name: Withings muscle mass lbs USER_PROFILE_NAME
|
||||
unit_of_measurement: "lbs"
|
||||
state: >-
|
||||
{{
|
||||
(states('sensor.withings_muscle_mass_kg_USER_PROFILE_NAME') | float(0) * 2.20462262185)
|
||||
| round(2, default=0)
|
||||
}}
|
||||
icon: "mdi:weight-pound"
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
@ -234,7 +234,7 @@ data:
|
||||
|
||||
### Service `zwave_js.bulk_set_partial_config_parameters`
|
||||
|
||||
This service will bulk set multiple partial configuration parameters. Be warned that correctly using this service requires advanced knowledge of Z-Wave to use correctly.
|
||||
This service will bulk set multiple partial configuration parameters. Be warned that correctly using this service requires advanced knowledge of Z-Wave.
|
||||
|
||||
| Service Data Attribute | Required | Description |
|
||||
| ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|
||||
@ -12,10 +12,6 @@ categories:
|
||||
og_image: /images/blog/2022-10-25-ultraloq-partner/social.png
|
||||
---
|
||||
|
||||
<div class="note important">
|
||||
On July 11th, 2023, due to fundamentally different perceptions of best Home Assistant user experience, Ultraloq by U-tec was removed from <a href="/blog/2022/07/12/partner-program">Works With Home Assistant</a> partner program.
|
||||
</div>
|
||||
|
||||
<img src='/images/works_with/works-with-zwave.png' width="256" align="right" alt="Works via Zigbee with Home Assistant" class='no-shadow'>
|
||||
|
||||
Today we are excited to announce that [Ultraloq by U-tec](https://u-tec.com) has joined the Works with Home Assistant program as a Z-Wave partner.
|
||||
|
||||
830
source/_posts/2023-09-06-release-20239.markdown
Normal file
830
source/_posts/2023-09-06-release-20239.markdown
Normal file
@ -0,0 +1,830 @@
|
||||
---
|
||||
layout: post
|
||||
title: "2023.9: New climate entity dialogs, lots of tile features, and template sensors from the UI!"
|
||||
description: "New entity dialogs for climate and others, lots of tile features, create template sensors from the UI and more!"
|
||||
date: 2023-09-06 00:00:00
|
||||
date_formatted: "September 6, 2023"
|
||||
author: Bram Kragten
|
||||
author_twitter: bramkragten
|
||||
comments: true
|
||||
categories:
|
||||
- Release-Notes
|
||||
- Core
|
||||
og_image: /images/blog/2023-09/social.png
|
||||
---
|
||||
|
||||
<a href='/integrations/#version/2023.9'><img src='/images/blog/2023-09/social.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
Home Assistant Core 2023.9! 🎉
|
||||
|
||||
Frenck is enjoying a well earned holiday, so I'm taking care of the release this month.
|
||||
|
||||
This month, on the 17th, it has been 10 years since Home Assistant started. We'll be preparing a special event on the [Home Assistant YouTube channel](https://www.youtube.com/channel/UCbX3YkedQunLt7EQAdVxh7w) to celebrate, reflect and look ahead. We will have some cool announcements too! We hope you can join us on the 17th @ 12:00 PDT / 21:00 CET!
|
||||
|
||||
This release is pretty packed! With some very nice updates to the UI with new entity dialogs for climate entities, and lots of tile card features. Template sensors can be created from the UI now, and for the more advanced template sensors, the ability to get data from services!
|
||||
A new service to get the weather forecast, and better options to display different forecasts.
|
||||
|
||||
And something you will probably not see when you are already using Home Assistant: the onboarding flow is completely redesigned!
|
||||
|
||||
I absolutely love it!
|
||||
|
||||
Enjoy the release!
|
||||
|
||||
Bram
|
||||
|
||||
<!--more-->
|
||||
|
||||
- [New climate, humidifier, and water heater entity dialogs](#new-climate-humidifier-and-water-heater-entity-dialogs)
|
||||
- [Lots of new tile features](#lots-of-new-tile-features)
|
||||
- [Lawn mower](#lawn-mower)
|
||||
- [Group previews](#group-previews)
|
||||
- [Template sensors from the UI](#template-sensors-from-the-ui)
|
||||
- [Actions for trigger template entities](#actions-for-trigger-template-entities)
|
||||
- [Weather forecast service](#weather-forecast-service)
|
||||
- [Onboarding](#onboarding)
|
||||
- [Other noteworthy changes](#other-noteworthy-changes)
|
||||
- [New integrations](#new-integrations)
|
||||
- [Release 2023.9.1 - September 8](#release-202391---september-8)
|
||||
- [Release 2023.9.2 - September 12](#release-202392---september-12)
|
||||
- [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=JSNRrWk9IHs)
|
||||
6 September 2023, at 12:00 PDT / 21:00 CEST!
|
||||
|
||||
<lite-youtube videoid="JSNRrWk9IHs" videotitle="Home Assistant 2023.9 Release Party"></lite-youtube>
|
||||
|
||||
## New climate, humidifier, and water heater entity dialogs
|
||||
|
||||
The entity dialogs for climate, humidifier, and water heater entities got an update, and if you ask me, it looks absolutely stunning!
|
||||
It now has a newly designed circular slider showing the current and target temperatures and allows you to easily swipe to the desired target temperature.
|
||||
There are also dedicated buttons to change the target, so it is easy to use if you are not using a touchscreen.
|
||||
It will glow in the middle to show its current action, for example when it is heating or cooling.
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/climate-card.png'>
|
||||
Screenshot of the more info dialog of a climate entity.
|
||||
</p>
|
||||
|
||||
## Lots of new tile features
|
||||
|
||||
The tile card gets many new features this release.
|
||||
|
||||
The features of a tile card are a great way to bring more functionalities directly into your dashboard, without needing to open the more info dialog.
|
||||
|
||||
- HVAC mode
|
||||
- Water heater mode
|
||||
- Temperature control
|
||||
- Cover position
|
||||
- Cover tilt
|
||||
- Lawn mower commands
|
||||
- Color temperature
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/tile-features.png'>
|
||||
Screenshot of tile cards with the new features.
|
||||
</p>
|
||||
|
||||
## Lawn mower
|
||||
|
||||
A new entity type was added this release: the lawn mower!
|
||||
|
||||
You can now integrate your lawn mower into Home Assistant!
|
||||
Never worry about the lawn mower when it starts raining, you can now automate the lawn mower to stop and go back when it rains.
|
||||
For now, just MQTT is supported, but keep an eye out for other integrations!
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/lawn-mower.png'>
|
||||
Screenshot of the more info dialog of a lawn mower entity.
|
||||
</p>
|
||||
|
||||
|
||||
## Group previews
|
||||
|
||||
When setting up a helper, sometimes it can be useful to see how the entity that you are creating looks while you are setting it up. That's why we added a preview when you create or change a group helper.
|
||||
|
||||
It will show exactly what the entity will look like with the current settings.
|
||||
|
||||
And talking about groups, we also got a new group, the `event` group!
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/group-preview.png'>
|
||||
Screenshot of creating a sensor group.
|
||||
</p>
|
||||
|
||||
|
||||
## Template sensors from the UI
|
||||
|
||||
We also added preview support to another helper that finally made its way into the UI, the template sensor.
|
||||
|
||||
From the UI you can use a template to set the state of the sensor.
|
||||
You can pick a unit of measurement, set the device class, and select a state class.
|
||||
Both sensors and binary sensors are supported.
|
||||
|
||||
This will make most of the use cases for template sensors available through the UI and one less need for YAML!
|
||||
|
||||
Other more advanced fields, like attributes, are unavailable from the UI. You will still have to set those up in YAML.
|
||||
|
||||
With the preview, you see a live update of the sensor value while writing the template.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/template-sensor.png'>
|
||||
Screenshot of creating a template sensor.
|
||||
</p>
|
||||
|
||||
|
||||
## Actions for trigger template entities
|
||||
|
||||
Trigger template entities can now have an action block that is executed after the trigger but before the entities are rendered.
|
||||
|
||||
This will allow users to fetch things like calendar events and weather forecasts using services with responses and use them in their template entities. You can even use OpenAI to set the value of your entities now!
|
||||
|
||||
All variables from the action block will be available in the template.
|
||||
|
||||
An example that checks at midnight if you have something on your calendar tomorrow and sets a binary sensor:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
template:
|
||||
- trigger:
|
||||
- platform: time
|
||||
at: "00:00:00"
|
||||
action:
|
||||
- service: calendar.list_events
|
||||
target:
|
||||
entity_id: calendar.calendar
|
||||
data:
|
||||
start_date_time: "{{ today_at() + timedelta(days=1) }}"
|
||||
duration:
|
||||
hours: 24
|
||||
response_variable: events
|
||||
binary_sensor:
|
||||
- name: Calendar events tomorrow
|
||||
state: "{{ events.events is defined and events.events | count > 0 }}"
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
|
||||
## Weather forecast service
|
||||
|
||||
We added a new service for weather entities, `weather.get_forecast`, that responds with the weather forecast.
|
||||
|
||||
Previously you would have to look at the `forecast` attribute of a weather entity to get the forecast, now this can be done by calling a new service, `weather.get_forecast`, that will respond with the forecast.
|
||||
You can also specify what type of forecast you want. Do you want to see the forecast by day or do you want to know it for every hour? This means you no longer need separate entities for every forecast type, but it can all be done in 1 entity.
|
||||
|
||||
All weather integrations are updated to support this new service.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/get-forecast-service.png'>
|
||||
Screenshot of service developer tools showing the weather forecast service.
|
||||
</p>
|
||||
|
||||
If an entity supports multiple forecasts, you can choose which forecast you want to see in the more info dialog.
|
||||
In the weather card in your dashboard, you can also now pick what kind of weather forecast you want to show in that card.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/weather-more-info.png'>
|
||||
Screenshot of the weather more info dialog.
|
||||
</p>
|
||||
|
||||
With this change, the `forecast` attribute of the weather entity is deprecated, and will be removed in Home Assistant Core 2024.3.
|
||||
|
||||
This will make it possible to have on-demand forecasts, that update when you want them to, instead of them being updated all the time.
|
||||
It will also make the system faster; all state data gets sent to your browser or mobile app every time it is opened so the frontend has the latest states of your entities. The forecast attribute makes the state of weather entities very big, causing everything to be loaded slower.
|
||||
|
||||
While the way to access this data has changed and may impact your automations, you will not experience any loss in functionality. Even with this change, rest assured that the forecast cards in your dashboard will still work, they will now just use the service to retrieve the forecast data asynchronously instead of reading it from the state attribute. The end result is that your dashboards will load faster, and the frontend will be leaner.
|
||||
|
||||
You can use the newly added `action` part of a template entity to fetch the forecast and use it in your template:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
template:
|
||||
- trigger:
|
||||
- platform: time
|
||||
at: "00:00:00"
|
||||
action:
|
||||
- service: weather.get_forecast
|
||||
target:
|
||||
entity_id: weather.home
|
||||
data:
|
||||
type: daily
|
||||
response_variable: forecast
|
||||
binary_sensor:
|
||||
- name: Is it going to rain?
|
||||
state: "{{ forecast.forecast[0].precipitation > 0 }}"
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
## Onboarding
|
||||
|
||||
While it is certain that Home Assistant is a great tool once you understand how it works, one part that was often overlooked is its associated learning curve.
|
||||
We are now actively working to flatten that curve so that you can get more from your home faster and simpler.
|
||||
This release shows the first result of that effort, a new onboarding flow.
|
||||
|
||||
Something you probably have not seen for a while, but we gave our onboarding a fresh new look! It is shortened to get users in Home Assistant as fast as possible, so they can enjoy tinkering with their home faster!
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2023-09/onboarding.png'>
|
||||
Screenshot of the onboarding screen.
|
||||
</p>
|
||||
|
||||
## Other noteworthy changes
|
||||
|
||||
There are many more improvements in this release; here are some of the other
|
||||
noteworthy changes this release:
|
||||
|
||||
- [Enphase Envoy] has gotten a lot of love this release, ensure it works
|
||||
perfectly with the latest firmware available. Thanks [@bdraco] and [@cgarwood]!
|
||||
- The [Shelly] integration now supports the Shelly Gas Valve addon. Thanks [@bieniu]!
|
||||
- [@starkillerOG] added zoom buttons and AI detection delay time controls to
|
||||
the [Reolink] integration. Nice!
|
||||
- You can now set separate damping factors for morning and evening in the
|
||||
[Forecast Solar] integration. Thanks [@joostlek]!
|
||||
- [@Kane610] added a restart device button to the [UniFi] integration. Thanks!
|
||||
- The [Tomorrow.io] integration now reports humidity and dew point in its weather
|
||||
forecasts. Thanks [@lymanepp]!
|
||||
- Support for soil moisture sensors was added to the [Gardena] integration.
|
||||
Thanks [@elupus]!
|
||||
- [@timmo001] added a power service to the [System Bridge] integration. Thanks!
|
||||
- If you change your password, you will be asked if you want to logout everywhere.
|
||||
- The file and image upload elements have been revamped.
|
||||
- You can now sort the options of an input select entity. Thanks [@karwosts]!
|
||||
- Local Bluetooth has been optimized and is now faster, thanks [@bdraco]!
|
||||
|
||||
[@karwosts]: https://github.com/karwosts
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@cgarwood]: https://github.com/cgarwood
|
||||
[@elupus]: https://github.com/elupus
|
||||
[@joostlek]: https://github.com/joostlek
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@lymanepp]: https://github.com/lymanepp
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@timmo001]: https://github.com/timmo001
|
||||
[Enphase Envoy]: /integrations/enphase_envoy
|
||||
[Forecast Solar]: /integrations/forecast_solar
|
||||
[Gardena]: /integrations/gardena_bluetooth
|
||||
[Reolink]: /integrations/reolink
|
||||
[Shelly]: /integrations/shelly
|
||||
[System Bridge]: /integrations/system_bridge
|
||||
[Tomorrow.io]: /integrations/tomorrowio
|
||||
[Unifi]: /integrations/unifi
|
||||
|
||||
## New integrations
|
||||
|
||||
We welcome the following new integrations in this release:
|
||||
|
||||
- **[Comelit SimpleHome]**, added by [@chemelli74]<br />
|
||||
Control your Comelit home automation devices.
|
||||
- **[Lawn mower]**, added by [@mikey0000]<br />
|
||||
A new entity type, that allows integrations to provide lawn mower entities.
|
||||
- **[Schlage]**, added by [@dknowles2]<br />
|
||||
Use your Schlage WiFi smart locks with Home Assistant.
|
||||
- **[Trafikverket Camera]**, added by [@gjohansson-ST]<br />
|
||||
Adds Swedish traffic camera feeds from Trafikverket.
|
||||
- **[Vodafone Station]**, added by [@chemelli74]<br />
|
||||
Provides device tracker support for Vodafone Station router.
|
||||
- **[Yardian]**, added by [@h3l1o5]<br />
|
||||
Support for your Yardan Smart Sprinkler Controller.
|
||||
|
||||
This release also has a new virtual integration. Virtual integrations are stubs that are handled by other (existing) integrations to help with findability. These are new:
|
||||
|
||||
- **[Consolidated Edison (ConEd)]** provided by [Opower]
|
||||
- **[Orange and Rockland Utilities (ORU) Opower]** provided by [Opower]
|
||||
|
||||
|
||||
[@chemelli74]: https://github.com/chemelli74
|
||||
[@dknowles2]: https://github.com/dknowles2
|
||||
[@gjohansson-ST]: http://github.com/gjohansson-ST
|
||||
[@h3l1o5]: https://github.com/h3l1o5
|
||||
[@mikey0000]: https://github.com/mikey0000
|
||||
[Comelit SimpleHome]: /integrations/comelit
|
||||
[Lawn mower]: /integrations/lawn_mower
|
||||
[Schlage]: /integrations/schlage
|
||||
[Trafikverket Camera]: /integrations/trafikverket_camera
|
||||
[Vodafone Station]: /integrations/vodafone_station
|
||||
[Yardian]: /integrations/yardian
|
||||
[Opower]: /integrations/opower
|
||||
[Consolidated Edison (ConEd)]: /integrations/coned
|
||||
[Orange and Rockland Utilities (ORU) Opower]: /integrations/oru_opower
|
||||
|
||||
## Release 2023.9.1 - September 8
|
||||
|
||||
- Fix the Hydrawise status sensor ([@dknowles2] - [#99271]) ([hydrawise docs])
|
||||
- Fix tradfri asyncio.wait ([@cdce8p] - [#99730]) ([tradfri docs])
|
||||
- Handle alexa invalid climate temp adjustment ([@jbouwh] - [#99740]) ([alexa docs])
|
||||
- Revert "Bump pyoverkiz to 1.10.1 (#97916)" ([@joostlek] - [#99742]) ([overkiz docs])
|
||||
- Fix Freebox disk free space sensor ([@Quentame] - [#99757]) ([freebox docs])
|
||||
- Fix Freebox Home battery sensor ([@Quentame] - [#99756]) ([freebox docs])
|
||||
- Bump sense_energy to 0.12.1 ([@bdraco] - [#99763])
|
||||
- Add support for more busy codes for Epson ([@pszafer] - [#99771]) ([epson docs])
|
||||
- Bump `aiorecollect` to 2023.09.0 ([@bachya] - [#99780]) ([recollect_waste docs])
|
||||
- Bump pyenphase to 1.9.3 ([@bdraco] - [#99787]) ([enphase_envoy docs])
|
||||
- Bump pylutron-caseta to v0.18.2 ([@swamplynx] - [#99789]) ([lutron_caseta docs])
|
||||
- Fix missing dew point and humidity in tomorrowio forecasts ([@lymanepp] - [#99793]) ([tomorrowio docs])
|
||||
- Always set severity level flag on render_template error events ([@emontnemery] - [#99804]) ([websocket_api docs])
|
||||
- Improve error handling in /api/states POST ([@emontnemery] - [#99810]) ([api docs])
|
||||
- Use correct config entry id in Livisi ([@joostlek] - [#99812]) ([livisi docs])
|
||||
- Fix missing name and identifiers for ELKM1 connected devices ([@bdraco] - [#99828]) ([elkm1 docs])
|
||||
- Bump aiovodafone to 0.1.0 ([@chemelli74] - [#99851]) ([vodafone_station docs])
|
||||
- Bump dbus-fast to 1.95.0 ([@bdraco] - [#99749]) ([bluetooth docs])
|
||||
- Bump dbus-fast to 1.95.2 ([@bdraco] - [#99852]) ([bluetooth docs])
|
||||
- Bump ZHA dependencies ([@puddly] - [#99855]) ([zha docs])
|
||||
- Fix NOAA tides warnings ([@jbouwh] - [#99856]) ([noaa_tides docs])
|
||||
- Upgrade bluetooth deps to fix timeout behavior on py3.11 ([@bdraco] - [#99879]) ([bluetooth docs])
|
||||
- Update frontend to 20230908.0 ([@bramkragten] - [#99939]) ([frontend docs])
|
||||
- Bump pymodbus v3.5.0 ([@janiversen] - [#99343]) ([modbus docs])
|
||||
- Bump pymodbus v.3.5.1 ([@janiversen] - [#99940]) ([modbus docs])
|
||||
- Bump pyenphase to v1.11.0 ([@joostlek] - [#99941]) ([enphase_envoy docs])
|
||||
- Fix key error MQTT binary_sensor when no name is set ([@jbouwh] - [#99943]) ([mqtt docs])
|
||||
- Bump zeroconf to 0.93.1 ([@bdraco] - [#99516]) ([zeroconf docs])
|
||||
- Bump zeroconf to 0.96.0 ([@bdraco] - [#99549]) ([zeroconf docs])
|
||||
- Bump zeroconf to 0.97.0 ([@bdraco] - [#99554]) ([zeroconf docs])
|
||||
- Bump zeroconf to 0.98.0 ([@bdraco] - [#99748]) ([zeroconf docs])
|
||||
- Make WS command render_template not give up if initial render raises ([@emontnemery] - [#99808]) ([websocket_api docs])
|
||||
- Bump hatasmota to 0.7.1 ([@emontnemery] - [#99818]) ([tasmota docs])
|
||||
- Bump millheater to 0.11.2 ([@Danielhiversen] - [#99683]) ([mill docs])
|
||||
|
||||
[#99271]: https://github.com/home-assistant/core/pull/99271
|
||||
[#99343]: https://github.com/home-assistant/core/pull/99343
|
||||
[#99516]: https://github.com/home-assistant/core/pull/99516
|
||||
[#99549]: https://github.com/home-assistant/core/pull/99549
|
||||
[#99554]: https://github.com/home-assistant/core/pull/99554
|
||||
[#99683]: https://github.com/home-assistant/core/pull/99683
|
||||
[#99730]: https://github.com/home-assistant/core/pull/99730
|
||||
[#99740]: https://github.com/home-assistant/core/pull/99740
|
||||
[#99741]: https://github.com/home-assistant/core/pull/99741
|
||||
[#99742]: https://github.com/home-assistant/core/pull/99742
|
||||
[#99748]: https://github.com/home-assistant/core/pull/99748
|
||||
[#99749]: https://github.com/home-assistant/core/pull/99749
|
||||
[#99756]: https://github.com/home-assistant/core/pull/99756
|
||||
[#99757]: https://github.com/home-assistant/core/pull/99757
|
||||
[#99763]: https://github.com/home-assistant/core/pull/99763
|
||||
[#99771]: https://github.com/home-assistant/core/pull/99771
|
||||
[#99780]: https://github.com/home-assistant/core/pull/99780
|
||||
[#99787]: https://github.com/home-assistant/core/pull/99787
|
||||
[#99789]: https://github.com/home-assistant/core/pull/99789
|
||||
[#99793]: https://github.com/home-assistant/core/pull/99793
|
||||
[#99804]: https://github.com/home-assistant/core/pull/99804
|
||||
[#99808]: https://github.com/home-assistant/core/pull/99808
|
||||
[#99810]: https://github.com/home-assistant/core/pull/99810
|
||||
[#99812]: https://github.com/home-assistant/core/pull/99812
|
||||
[#99818]: https://github.com/home-assistant/core/pull/99818
|
||||
[#99828]: https://github.com/home-assistant/core/pull/99828
|
||||
[#99851]: https://github.com/home-assistant/core/pull/99851
|
||||
[#99852]: https://github.com/home-assistant/core/pull/99852
|
||||
[#99855]: https://github.com/home-assistant/core/pull/99855
|
||||
[#99856]: https://github.com/home-assistant/core/pull/99856
|
||||
[#99879]: https://github.com/home-assistant/core/pull/99879
|
||||
[#99939]: https://github.com/home-assistant/core/pull/99939
|
||||
[#99940]: https://github.com/home-assistant/core/pull/99940
|
||||
[#99941]: https://github.com/home-assistant/core/pull/99941
|
||||
[#99943]: https://github.com/home-assistant/core/pull/99943
|
||||
[@Danielhiversen]: https://github.com/Danielhiversen
|
||||
[@Quentame]: https://github.com/Quentame
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@chemelli74]: https://github.com/chemelli74
|
||||
[@dknowles2]: https://github.com/dknowles2
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@janiversen]: https://github.com/janiversen
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[@joostlek]: https://github.com/joostlek
|
||||
[@lymanepp]: https://github.com/lymanepp
|
||||
[@pszafer]: https://github.com/pszafer
|
||||
[@puddly]: https://github.com/puddly
|
||||
[@swamplynx]: https://github.com/swamplynx
|
||||
[abode docs]: /integrations/abode/
|
||||
[accuweather docs]: /integrations/accuweather/
|
||||
[acmeda docs]: /integrations/acmeda/
|
||||
[adax docs]: /integrations/adax/
|
||||
[adguard docs]: /integrations/adguard/
|
||||
[ads docs]: /integrations/ads/
|
||||
[alexa docs]: /integrations/alexa/
|
||||
[api docs]: /integrations/api/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[elkm1 docs]: /integrations/elkm1/
|
||||
[enphase_envoy docs]: /integrations/enphase_envoy/
|
||||
[epson docs]: /integrations/epson/
|
||||
[freebox docs]: /integrations/freebox/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[hydrawise docs]: /integrations/hydrawise/
|
||||
[livisi docs]: /integrations/livisi/
|
||||
[lutron_caseta docs]: /integrations/lutron_caseta/
|
||||
[mill docs]: /integrations/mill/
|
||||
[modbus docs]: /integrations/modbus/
|
||||
[mqtt docs]: /integrations/mqtt/
|
||||
[noaa_tides docs]: /integrations/noaa_tides/
|
||||
[overkiz docs]: /integrations/overkiz/
|
||||
[recollect_waste docs]: /integrations/recollect_waste/
|
||||
[tasmota docs]: /integrations/tasmota/
|
||||
[tomorrowio docs]: /integrations/tomorrowio/
|
||||
[tradfri docs]: /integrations/tradfri/
|
||||
[vodafone_station docs]: /integrations/vodafone_station/
|
||||
[websocket_api docs]: /integrations/websocket_api/
|
||||
[zeroconf docs]: /integrations/zeroconf/
|
||||
[zha docs]: /integrations/zha/
|
||||
|
||||
## Release 2023.9.2 - September 12
|
||||
|
||||
- Remove modbus pragma no cover and solve nan ([@janiversen] - [#99221]) ([modbus docs])
|
||||
- Bugfix: Electric Kiwi reduce interval so oauth doesn't expire ([@mikey0000] - [#99489]) ([electric_kiwi docs])
|
||||
- Read modbus data before scan_interval ([@janiversen] - [#99243]) ([modbus docs])
|
||||
- Make modbus retry fast on read errors ([@janiversen] - [#99576]) ([modbus docs])
|
||||
- Fix Soma cover tilt ([@ratsept] - [#99717]) ([soma docs])
|
||||
- Cache device trigger info during ZHA startup ([@puddly] - [#99764]) ([zha docs])
|
||||
- Airthings BLE unique id migration ([@LaStrada] - [#99832]) ([airthings_ble docs])
|
||||
- Update RestrictedPython to 6.2 ([@cdce8p] - [#99955]) ([python_script docs])
|
||||
- Bump bleak to 0.21.1 ([@bdraco] - [#99960]) ([bluetooth docs])
|
||||
- Bump python-roborock to 33.2 ([@Lash-L] - [#99962]) ([roborock docs])
|
||||
- Handle disconnects in zwave_js repair flow ([@raman325] - [#99964]) ([zwave_js docs])
|
||||
- Bump plugwise to v0.32.2 ([@bouwew] - [#99973]) ([plugwise docs])
|
||||
- Bump bluetooth-auto-recovery to 1.2.3 ([@bdraco] - [#99979]) ([bluetooth docs])
|
||||
- Avoid probing ipp printers for unique_id when it is available via mdns ([@bdraco] - [#99982]) ([ipp docs])
|
||||
- Bump pymodbus to v3.5.2 ([@janiversen] - [#99988]) ([modbus docs])
|
||||
- Bump pywaze to 0.4.0 ([@eifinger] - [#99995]) ([waze_travel_time docs])
|
||||
- Bump systembridgeconnector to 3.8.2 ([@timmo001] - [#100051]) ([system_bridge docs])
|
||||
- Bump aiovodafone to 0.2.0 ([@chemelli74] - [#100062]) ([vodafone_station docs])
|
||||
- Remove Comelit alarm data retrieval ([@chemelli74] - [#100067]) ([comelit docs])
|
||||
- Fix addon slug validation ([@mdegat01] - [#100070]) ([hassio docs])
|
||||
- Remove duplicated word in enphase description text ([@greiginsydney] - [#100098]) ([enphase_envoy docs])
|
||||
- Fix TriggerEntity.async_added_to_hass ([@emontnemery] - [#100119]) ([template docs])
|
||||
- Bump hatasmota to 0.7.2 ([@emontnemery] - [#100129]) ([tasmota docs])
|
||||
- Update frontend to 20230911.0 ([@bramkragten] - [#100139]) ([frontend docs])
|
||||
- Fix devices not always reporting IP - bump aiounifi to v62 ([@Kane610] - [#100149]) ([unifi docs])
|
||||
- Fix AVM Fritz!Tools update entity ([@mib1185] - [#100151]) ([fritz docs])
|
||||
- Bump ZHA dependencies ([@puddly] - [#100156]) ([zha docs])
|
||||
- Bump zwave-js-server-python to 0.51.2 ([@raman325] - [#100159]) ([zwave_js docs])
|
||||
- Adjust tasmota sensor device class and icon mapping ([@emontnemery] - [#100168]) ([tasmota docs])
|
||||
- Bump hatasmota to 0.7.3 ([@emontnemery] - [#100169]) ([tasmota docs])
|
||||
- Bump Ultraheat to version 0.5.7 ([@vpathuis] - [#100172]) ([landisgyr_heat_meter docs])
|
||||
- Fix entity name attribute on mqtt entity is not removed on update ([@jbouwh] - [#100187]) ([mqtt docs])
|
||||
- Bump hass-nabucasa from 0.70.0 to 0.71.0 ([@ludeeus] - [#100193]) ([cloud docs])
|
||||
|
||||
[#100051]: https://github.com/home-assistant/core/pull/100051
|
||||
[#100062]: https://github.com/home-assistant/core/pull/100062
|
||||
[#100067]: https://github.com/home-assistant/core/pull/100067
|
||||
[#100070]: https://github.com/home-assistant/core/pull/100070
|
||||
[#100098]: https://github.com/home-assistant/core/pull/100098
|
||||
[#100119]: https://github.com/home-assistant/core/pull/100119
|
||||
[#100129]: https://github.com/home-assistant/core/pull/100129
|
||||
[#100139]: https://github.com/home-assistant/core/pull/100139
|
||||
[#100149]: https://github.com/home-assistant/core/pull/100149
|
||||
[#100151]: https://github.com/home-assistant/core/pull/100151
|
||||
[#100156]: https://github.com/home-assistant/core/pull/100156
|
||||
[#100159]: https://github.com/home-assistant/core/pull/100159
|
||||
[#100168]: https://github.com/home-assistant/core/pull/100168
|
||||
[#100169]: https://github.com/home-assistant/core/pull/100169
|
||||
[#100172]: https://github.com/home-assistant/core/pull/100172
|
||||
[#100187]: https://github.com/home-assistant/core/pull/100187
|
||||
[#100188]: https://github.com/home-assistant/core/pull/100188
|
||||
[#100193]: https://github.com/home-assistant/core/pull/100193
|
||||
[#99221]: https://github.com/home-assistant/core/pull/99221
|
||||
[#99243]: https://github.com/home-assistant/core/pull/99243
|
||||
[#99489]: https://github.com/home-assistant/core/pull/99489
|
||||
[#99576]: https://github.com/home-assistant/core/pull/99576
|
||||
[#99717]: https://github.com/home-assistant/core/pull/99717
|
||||
[#99741]: https://github.com/home-assistant/core/pull/99741
|
||||
[#99764]: https://github.com/home-assistant/core/pull/99764
|
||||
[#99832]: https://github.com/home-assistant/core/pull/99832
|
||||
[#99950]: https://github.com/home-assistant/core/pull/99950
|
||||
[#99955]: https://github.com/home-assistant/core/pull/99955
|
||||
[#99960]: https://github.com/home-assistant/core/pull/99960
|
||||
[#99962]: https://github.com/home-assistant/core/pull/99962
|
||||
[#99964]: https://github.com/home-assistant/core/pull/99964
|
||||
[#99973]: https://github.com/home-assistant/core/pull/99973
|
||||
[#99979]: https://github.com/home-assistant/core/pull/99979
|
||||
[#99982]: https://github.com/home-assistant/core/pull/99982
|
||||
[#99988]: https://github.com/home-assistant/core/pull/99988
|
||||
[#99995]: https://github.com/home-assistant/core/pull/99995
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@LaStrada]: https://github.com/LaStrada
|
||||
[@Lash-L]: https://github.com/Lash-L
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bouwew]: https://github.com/bouwew
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@chemelli74]: https://github.com/chemelli74
|
||||
[@eifinger]: https://github.com/eifinger
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@greiginsydney]: https://github.com/greiginsydney
|
||||
[@janiversen]: https://github.com/janiversen
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[@ludeeus]: https://github.com/ludeeus
|
||||
[@mdegat01]: https://github.com/mdegat01
|
||||
[@mib1185]: https://github.com/mib1185
|
||||
[@mikey0000]: https://github.com/mikey0000
|
||||
[@puddly]: https://github.com/puddly
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@ratsept]: https://github.com/ratsept
|
||||
[@timmo001]: https://github.com/timmo001
|
||||
[@vpathuis]: https://github.com/vpathuis
|
||||
[abode docs]: /integrations/abode/
|
||||
[accuweather docs]: /integrations/accuweather/
|
||||
[acmeda docs]: /integrations/acmeda/
|
||||
[adax docs]: /integrations/adax/
|
||||
[adguard docs]: /integrations/adguard/
|
||||
[ads docs]: /integrations/ads/
|
||||
[airthings_ble docs]: /integrations/airthings_ble/
|
||||
[bluetooth docs]: /integrations/bluetooth/
|
||||
[cloud docs]: /integrations/cloud/
|
||||
[comelit docs]: /integrations/comelit/
|
||||
[electric_kiwi docs]: /integrations/electric_kiwi/
|
||||
[enphase_envoy docs]: /integrations/enphase_envoy/
|
||||
[fritz docs]: /integrations/fritz/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[hassio docs]: /integrations/hassio/
|
||||
[ipp docs]: /integrations/ipp/
|
||||
[landisgyr_heat_meter docs]: /integrations/landisgyr_heat_meter/
|
||||
[modbus docs]: /integrations/modbus/
|
||||
[mqtt docs]: /integrations/mqtt/
|
||||
[plugwise docs]: /integrations/plugwise/
|
||||
[python_script docs]: /integrations/python_script/
|
||||
[roborock docs]: /integrations/roborock/
|
||||
[soma docs]: /integrations/soma/
|
||||
[system_bridge docs]: /integrations/system_bridge/
|
||||
[tasmota docs]: /integrations/tasmota/
|
||||
[template docs]: /integrations/template/
|
||||
[unifi docs]: /integrations/unifi/
|
||||
[vodafone_station docs]: /integrations/vodafone_station/
|
||||
[waze_travel_time docs]: /integrations/waze_travel_time/
|
||||
[zha docs]: /integrations/zha/
|
||||
[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
|
||||
|
||||
{% details "BMW Connected Drive" %}
|
||||
|
||||
The "Refresh from cloud" button has been removed. Use the
|
||||
`homeassistant.update_entity` service with any BMW entity for a
|
||||
full reload instead.
|
||||
|
||||
([@rikroe] - [#97864]) ([documentation](/integrations/bmw_connected_drive))
|
||||
|
||||
[@rikroe]: https://github.com/rikroe
|
||||
[#97864]: https://github.com/home-assistant/core/pull/97864
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "DoorBird" %}
|
||||
|
||||
The `doorbird_reset_favorites` event is no longer fired when the clear webhook
|
||||
is called. Note: this event was never documented.
|
||||
|
||||
([@bdraco] - [#98585]) ([documentation](/integrations/doorbird))
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[#98585]: https://github.com/home-assistant/core/pull/98585
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Enphase Envoy" %}
|
||||
|
||||
Envoy versions < 3.9 (pre-API) are no longer supported as they require
|
||||
web scraping which is disallowed by [ADR-0004](https://github.com/home-assistant/architecture/blob/master/adr/0004-webscraping.md).
|
||||
|
||||
([@bdraco] - [#97862]) ([documentation](/integrations/enphase_envoy))
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[#97862]: https://github.com/home-assistant/core/pull/97862
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ESPHome" %}
|
||||
|
||||
To prevent cross-linked devices, replacing an ESPHome device with a different
|
||||
board is no longer allowed. Instead, delete the integration entry and re-add
|
||||
the new device when the mac address of the board changes.
|
||||
|
||||
([@bdraco] - [#98787]) ([documentation](/integrations/esphome))
|
||||
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[#98787]: https://github.com/home-assistant/core/pull/98787
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "EZVIZ" %}
|
||||
|
||||
Only switches supported by the camera will be created. Non switchable switches have been removed.
|
||||
|
||||
([@RenierM26] - [#95672]) ([documentation](/integrations/ezviz))
|
||||
|
||||
[@RenierM26]: https://github.com/RenierM26
|
||||
[#95672]: https://github.com/home-assistant/core/pull/95672
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Flume" %}
|
||||
|
||||
You might get false positives for leak detected and high flow sensors if you
|
||||
have old unread notifications in the Flume app.
|
||||
|
||||
Before, the leak detected and high flow sensors would only trigger until you
|
||||
read the notification in the Flume app which was too late for Home Assistant
|
||||
to take any automated action.
|
||||
|
||||
Now, they trigger regardless if you have read or not the notification. They will
|
||||
remain active until you delete the notification in the Flume app,
|
||||
similar to [the old behavior documented](/integrations/flume/#notifications).
|
||||
|
||||
([@tronikos] - [#98560]) ([documentation](/integrations/flume))
|
||||
|
||||
[@tronikos]: https://github.com/tronikos
|
||||
[#98560]: https://github.com/home-assistant/core/pull/98560
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Hive" %}
|
||||
|
||||
The previously deprecated service `hive.boost_heating` has been removed.
|
||||
|
||||
([@gjohansson-ST] - [#97444]) ([documentation](/integrations/hive))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#97444]: https://github.com/home-assistant/core/pull/97444
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "HTTP / Webserver" %}
|
||||
|
||||
Home Assistant can't be put in an iframe anymore by default. If you still want
|
||||
to embed the Home Assistant interface in a frame, you can do so by disabling
|
||||
`use_x_frame_options` by setting it to `false` in the `http` configuration.
|
||||
|
||||
([@frenck] - [#97784]) ([documentation](/integrations/http))
|
||||
|
||||
[@frenck]: https://github.com/frenck
|
||||
[#97784]: https://github.com/home-assistant/core/pull/97784
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Météo-France" %}
|
||||
|
||||
The Météo-France weather entities have been updated:
|
||||
|
||||
- The `forecast` state attribute is deprecated and will be removed in
|
||||
Home Assistant Core 2024.3, you should instead use the `weather.get_forecast`
|
||||
service.
|
||||
- The config entry option to select hourly or daily forecast can no longer be
|
||||
adjusted, but any existing configuration of the forecast period will be
|
||||
respected until Home Assistant Core 2024.3.
|
||||
- Météo-France now provides a single weather entity which supports both
|
||||
hourly and daily forecast.
|
||||
|
||||
([@emontnemery] - [#98022]) ([documentation](/integrations/meteo_france))
|
||||
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[#98022]: https://github.com/home-assistant/core/pull/98022
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Mill" %}
|
||||
|
||||
Mill has moved to a new IoT solution and released a new API. The unique ID from
|
||||
the old API is no longer available, so all devices will be shown as new devices.
|
||||
Support for the heater fan will be added later.
|
||||
|
||||
([@Danielhiversen] - [#97497]) ([documentation](/integrations/mill))
|
||||
|
||||
[@Danielhiversen]: https://github.com/Danielhiversen
|
||||
[#97497]: https://github.com/home-assistant/core/pull/97497
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "MQTT" %}
|
||||
|
||||
MQTT device trackers no longer always update when there is no state change.
|
||||
This means that automations that trigger on a state change no longer are
|
||||
triggered if there is no change.
|
||||
|
||||
([@jbouwh] - [#98838]) ([documentation](/integrations/mqtt))
|
||||
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[#98838]: https://github.com/home-assistant/core/pull/98838
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Nextcloud" %}
|
||||
|
||||
The CPU load sensor has been replaced, it is not a list of 3 values anymore,
|
||||
but there are now three single sensors for
|
||||
CPU load within last 1, 5, and 15 minutes.
|
||||
|
||||
([@mib1185] - [#99141]) ([documentation](/integrations/nextcloud))
|
||||
|
||||
[@mib1185]: https://github.com/mib1185
|
||||
[#99141]: https://github.com/home-assistant/core/pull/99141
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Plugwise" %}
|
||||
|
||||
The `maximum_boiler_temperature` sensor entity has been replaced by a number
|
||||
entity, allowing control as well.
|
||||
|
||||
([@CoMPaTech] - [#97203]) ([documentation](/integrations/plugwise))
|
||||
|
||||
[@CoMPaTech]: https://github.com/CoMPaTech
|
||||
[#97203]: https://github.com/home-assistant/core/pull/97203
|
||||
|
||||
---
|
||||
|
||||
The additional schema state attributes of the climate entity have been removed.
|
||||
They have beeen previously replaced by a select entity.
|
||||
|
||||
([@bouwew] - [#98153]) ([documentation](/integrations/plugwise))
|
||||
|
||||
[@bouwew]: https://github.com/bouwew
|
||||
[#98153]: https://github.com/home-assistant/core/pull/98153
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Start.ca" %}
|
||||
|
||||
Start.ca `limit`, `usage`, and `used_remaining` sensors will no longer be created
|
||||
when there's no bandwidth cap.
|
||||
|
||||
([@emontnemery] - [#98525]) ([documentation](/integrations/startca))
|
||||
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[#98525]: https://github.com/home-assistant/core/pull/98525
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Trafikverket Train" %}
|
||||
|
||||
All attributes have been converted into their own sensors.
|
||||
The original sensor is now renamed with suffix "Departure time".
|
||||
|
||||
Any automation or script depending on these attributes needs to be adjusted
|
||||
to use these new sensors.
|
||||
|
||||
([@gjohansson-ST] - [#71432]) ([documentation](/integrations/trafikverket_train))
|
||||
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[#71432]: https://github.com/home-assistant/core/pull/71432
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Z-Wave" %}
|
||||
|
||||
The entity naming logic has been updated to be less brittle. As a result,
|
||||
some `zwave_js` entities that you haven't given a custom name to may be renamed.
|
||||
|
||||
Since they are registered in the entity registry, the entity IDs will not change
|
||||
and your automations should therefore not be impacted by the change.
|
||||
|
||||
([@raman325] - [#98140]) ([documentation](/integrations/zwave_js))
|
||||
|
||||
With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 1.31.0 or greater (schema 31).
|
||||
|
||||
If you use the Z-Wave JS add-on, you need at least version 0.1.88.
|
||||
If you use the Z-Wave JS UI add-on, you need at least version 1.15.9.
|
||||
If you use the Z-Wave JS UI Docker container, you need at least version 8.23.2.
|
||||
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.31.0.
|
||||
|
||||
([@raman325] - [#99250]) ([documentation](/integrations/zwave_js))
|
||||
|
||||
[@raman325]: https://github.com/raman325
|
||||
[#98140]: https://github.com/home-assistant/core/pull/98140
|
||||
[#99250]: https://github.com/home-assistant/core/pull/99250
|
||||
|
||||
{% 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:
|
||||
|
||||
- [Entity state formatting](https://developers.home-assistant.io/blog/2023/08/29/hass-format-state)
|
||||
- [HomeAssistant.__init__ requires passing a string to it](https://developers.home-assistant.io/blog/2023/08/29/homeassistant-changed-signature)
|
||||
- [Numerical sensors are no longer allowed to set their state to NaN or inf](https://developers.home-assistant.io/blog/2023/08/23/sensor-updates)
|
||||
- [Weather entity forecast types](https://developers.home-assistant.io/blog/2023/08/07/weather_entity_forecast_types/)
|
||||
|
||||
[devblog]: https://developers.home-assistant.io/blog/
|
||||
|
||||
## All changes
|
||||
|
||||
Of course, there is a lot more in this release. You can find a list of
|
||||
all changes made here: [Full changelog for Home Assistant Core 2023.9](/changelogs/core-2023.9)
|
||||
17
source/_posts/2023-09-13-coming-soon-10-years-ha.markdown
Normal file
17
source/_posts/2023-09-13-coming-soon-10-years-ha.markdown
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Celebrate 10 years with us"
|
||||
description: "Join us on September 17 to look back on ten years of Home Assistant and hear some very special announcements..."
|
||||
date: 2023-09-13 00:00:00
|
||||
date_formatted: "September 13, 2023"
|
||||
author: Paulus Schoutsen
|
||||
comments: true
|
||||
categories: Announcements
|
||||
og_image: /images/frontpage/HA10_-_Website_banner.png
|
||||
---
|
||||
|
||||
Join us on September 17 to look back on ten years of Home Assistant and hear some very special announcements...
|
||||
|
||||
<lite-youtube autoload videoid="EmLV6lJLzSU" videotitle="Home Assistant 10th Anniversary Event #HA10">
|
||||
<a class="lite-youtube-fallback" href="https://www.youtube.com/watch?v=EmLV6lJLzSU">Watch on YouTube: Home Assistant 10th Anniversary Event #HA10</a>
|
||||
</lite-youtube>
|
||||
@ -544,7 +544,6 @@ layout: null
|
||||
/integrations/trackr /more-info/removed-integration 301
|
||||
/integrations/ubee /more-info/removed-integration 301
|
||||
/integrations/uber /more-info/removed-integration 301
|
||||
/integrations/ultraloq /more-info/removed-integration 301
|
||||
/integrations/updater /more-info/removed-integration 301
|
||||
/integrations/ups /more-info/removed-integration 301
|
||||
/integrations/uscis /more-info/removed-integration 301
|
||||
|
||||
2525
source/changelogs/core-2023.9.markdown
Normal file
2525
source/changelogs/core-2023.9.markdown
Normal file
File diff suppressed because it is too large
Load Diff
@ -5,22 +5,21 @@ description: "Instructions to get Home Assistant configured."
|
||||
|
||||
Alright, you made it here. The tough part is done.
|
||||
|
||||
After entering the Home Assistant device's address in your browser's address bar, the preparation screen is shown. Depending on your hardware, preparation may take a while.
|
||||
After entering the Home Assistant device's address in your browser's address bar, the welcome screen is shown. Depending on your hardware, preparation may take a while.
|
||||
|
||||
|
||||
|
||||
To show the logs, select the blue pulsing circle.
|
||||
|
||||
|
||||
|
||||
With Home Assistant installed, it's time to set up the basics.
|
||||
|
||||
In this step, you will create the owner account of Home Assistant. This account is an administrator account. It will always be able to change everything.
|
||||
In this step, you will create the owner's account of Home Assistant. This account is an administrator account. It will always be able to change everything.
|
||||
|
||||
1. Enter a name, username, and password. Select **Create account**.
|
||||
1. If this is your initial installation, select **Create my smart home**.
|
||||
- If you want to restore from a backup of a previous installation, select **Restore from backup**.
|
||||
- The following steps describe how to create a new installation, not how to restore from backup.
|
||||
2. Enter a name, username, and password. Select **Create account**.
|
||||
|
||||
|
||||
|
||||
2. Enter a name for your home.
|
||||
3. Enter the location of your home.
|
||||
- The location is used to populate settings such as time zone, unit system, and currency.
|
||||
- It is also used for location-based information and automations: for example showing the weather-forecast, opening the shades at sunrise, or starting the vacuum when you leave the home.
|
||||
@ -28,26 +27,21 @@ In this step, you will create the owner account of Home Assistant. This account
|
||||
- You can always change this information later in the settings.
|
||||
|
||||
|
||||
|
||||
4. Check if the location based information is correct and change if necessary.
|
||||
- You can always change this information later in the settings.
|
||||
|
||||
|
||||
|
||||
5. Select which information you are willing to share.
|
||||
4. Select which information you are willing to share.
|
||||
- Sharing is disabled by default. However, we would like to encourage you to share some of this data.
|
||||
- This information helps us to find out which platforms we need to support and where to focus our efforts.
|
||||
- The data is anonymized and aggregated. To see the charts we generate out of this data, take a look at our [analytics page](https://analytics.home-assistant.io/).
|
||||
|
||||
|
||||
|
||||
6. Once you are done, select **Next**.
|
||||
5. Once you are done, select **Next**.
|
||||
- Home Assistant will then show any {% term devices %} it has discovered on your network.
|
||||
- Don't be alarmed if you see fewer items than shown below; you can always manually add devices later.
|
||||
|
||||
|
||||
|
||||
7. Finally, select **Finish**.
|
||||
- Now you're brought to the Home Assistant web interface. This screen will show all of your devices.
|
||||
6. Finally, select **Finish**.
|
||||
- Now you're brought to the Home Assistant web interface. If some of your devices were discovered and setup automatically, this default dashboard may already show some of your devices.
|
||||
|
||||
{% include getting-started/next_step.html step="Concepts & Terminology" link="/getting-started/concepts-terminology/" %}
|
||||
|
||||
@ -22,6 +22,12 @@ The current logo was created by [Jeremy Geltman](https://jeremygeltman.com/). Fu
|
||||
|
||||
Home Assistant is open source software and available under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) license.
|
||||
|
||||
## Hardware
|
||||
|
||||
- End of 2020, [Home Assistant Blue](/blue/) was launched. The first dedicated smart home hub for Home Assistant. This limited edition is based on an ODROID and known for its blue aluminum case.
|
||||
- In September 2021, [Home Assistant Yellow](/yellow/) was launched. This extendable smart home hub is a custom, open-source design powered by a Raspberry Pi Compute Module 4. Home Assistant Yellow supports both Zigbee and Thread.
|
||||
- End of 2022, [Home Assistant SkyConnect](skyconnect) was launched: a USB dongle that provides Zigbee and Thread network support for hubs that do not have this built-in.
|
||||
|
||||
## Numbers
|
||||
|
||||
This sections just contains some random numbers of the Home Assistant eco-system. Sorry, only the main repository counts.
|
||||
|
||||
BIN
source/images/blog/2023-09/climate-card.png
Normal file
BIN
source/images/blog/2023-09/climate-card.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
BIN
source/images/blog/2023-09/get-forecast-service.png
Normal file
BIN
source/images/blog/2023-09/get-forecast-service.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
source/images/blog/2023-09/group-preview.png
Normal file
BIN
source/images/blog/2023-09/group-preview.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.1 KiB |
BIN
source/images/blog/2023-09/lawn-mower.png
Normal file
BIN
source/images/blog/2023-09/lawn-mower.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.8 KiB |
BIN
source/images/blog/2023-09/onboarding.png
Normal file
BIN
source/images/blog/2023-09/onboarding.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
BIN
source/images/blog/2023-09/social.png
Normal file
BIN
source/images/blog/2023-09/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 179 KiB |
BIN
source/images/blog/2023-09/template-sensor.png
Normal file
BIN
source/images/blog/2023-09/template-sensor.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
BIN
source/images/blog/2023-09/tile-features.png
Normal file
BIN
source/images/blog/2023-09/tile-features.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
BIN
source/images/blog/2023-09/weather-more-info.png
Normal file
BIN
source/images/blog/2023-09/weather-more-info.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 140 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 360 KiB |
BIN
source/images/docs/configuration/download-diagnostics.png
Normal file
BIN
source/images/docs/configuration/download-diagnostics.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 159 KiB |
BIN
source/images/docs/configuration/enable-debug-logging.png
Normal file
BIN
source/images/docs/configuration/enable-debug-logging.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 109 KiB |
BIN
source/images/frontpage/HA10_-_Website_banner.png
Normal file
BIN
source/images/frontpage/HA10_-_Website_banner.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 66 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 122 KiB After Width: | Height: | Size: 221 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 60 KiB |
BIN
source/images/getting-started/onboarding_preparing_01_.png
Normal file
BIN
source/images/getting-started/onboarding_preparing_01_.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 44 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 27 KiB After Width: | Height: | Size: 48 KiB |
@ -90,6 +90,16 @@ feedback: false
|
||||
</a>
|
||||
</div>
|
||||
<div class="grid__item two-thirds lap-two-thirds palm-one-whole">
|
||||
<!-- 10 YEAR HA -->
|
||||
<a
|
||||
href="https://www.youtube.com/watch?v=EmLV6lJLzSU"
|
||||
class="material-card picture-promo"
|
||||
style="
|
||||
background-image: url(/images/frontpage/HA10_-_Website_banner.png);
|
||||
background-size: cover;
|
||||
padding-top: 55%;
|
||||
"
|
||||
></a>
|
||||
<!-- Year of the voice chapter 3 -->
|
||||
<a
|
||||
href="/blog/2023/07/20/year-of-the-voice-chapter-3/"
|
||||
@ -111,17 +121,6 @@ feedback: false
|
||||
padding-top: 45%;
|
||||
"
|
||||
></a>
|
||||
<!-- State of the Open Home 2022 -->
|
||||
<a
|
||||
href="https://www.youtube.com/watch?v=D936T1Ze8-4"
|
||||
target="_blank"
|
||||
class="material-card picture-promo"
|
||||
style="
|
||||
background-image: url(/images/frontpage/state-of-the-open-home-2022.png);
|
||||
background-size: cover;
|
||||
padding-top: 45%;
|
||||
"
|
||||
></a>
|
||||
|
||||
{% assign pages_by_date = site.pages | sort: "date" | reverse %}
|
||||
{% for page in pages_by_date %}
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: landingpage
|
||||
title: "Home Assistant Yellow"
|
||||
description: "The easiest way to run Home Assistant. Now available for pre-order."
|
||||
description: "Home Assistant Yellow is your Matter-ready, upgradeable, and extendable smart home hub. You won't need anything else."
|
||||
date: 2022-10-05
|
||||
tagline: Home Assistant Yellow
|
||||
tagline_wide: false
|
||||
@ -180,7 +180,7 @@ frontpage_image: /images/frontpage/yellow-frontpage.jpg
|
||||
</div>
|
||||
</div>
|
||||
<div class="yellow-variant">
|
||||
<div><img src="/images/yellow/yellow-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit Power-over-Ethernet variant"></div>
|
||||
<div><img src="/images/yellow/yellow-kit-poe-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit Power-over-Ethernet variant"></div>
|
||||
<div>
|
||||
<b>Yellow Kit with Power-over-Ethernet</b><br>
|
||||
<a href="https://yellow.home-assistant.io/poe/">Some assembly required!</a> This kit supports Power-over-Ethernet (PoE) but is otherwise almost the same as the flagship version. <b>Without the Raspberry Pi Compute Module 4</b>.
|
||||
@ -189,7 +189,7 @@ frontpage_image: /images/frontpage/yellow-frontpage.jpg
|
||||
</div>
|
||||
</div>
|
||||
<div class="yellow-variant">
|
||||
<div><img src="/images/yellow/yellow-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit"></div>
|
||||
<div><img src="/images/yellow/yellow-kit-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit"></div>
|
||||
<div>
|
||||
<b>Yellow Kit with power supply</b><br>
|
||||
<a href="https://yellow.home-assistant.io/power-supply/">Some assembly required!</a> This kit is almost the same as the flagship version. <b> Without the Raspberry Pi Compute Module 4</b>.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user