jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-22 16:56:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'rc' into current

Browse Source
This commit is contained in:
Franck Nijhof 2024-03-06 20:38:28 +01:00
commit d49d5894b0
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
109 changed files with 3579 additions and 513 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.textlintrc.json
View File

@ -150,7 +150,6 @@
"iTunes",
"JSON-RPC",
"JSON",
"JuiceNet",
"Kafka",
"KEF",
"KNX",

52
CODEOWNERS
View File

@ -12,6 +12,7 @@ source/_integrations/3_day_blinds.markdown @starkillerOG
source/_integrations/abode.markdown @shred86
source/_integrations/accuweather.markdown @bieniu
source/_integrations/acmeda.markdown @atmurray
source/_integrations/acomax.markdown @starkillerOG
source/_integrations/adax.markdown @danielhiversen
source/_integrations/adguard.markdown @frenck
source/_integrations/advantage_air.markdown @Bre77
@ -37,7 +38,6 @@ source/_integrations/alert.markdown @home-assistant/core @frenck
source/_integrations/alexa.markdown @home-assistant/cloud @ochlocracy @jbouwh
source/_integrations/alexa.smart_home.markdown @home-assistant/cloud @ochlocracy @jbouwh
source/_integrations/amberelectric.markdown @madpilot
source/_integrations/ambiclimate.markdown @danielhiversen
source/_integrations/ambient_station.markdown @bachya
source/_integrations/amcrest.markdown @flacjacket
source/_integrations/amp_motorization.markdown @starkillerOG
@ -57,6 +57,7 @@ source/_integrations/appalachianpower.markdown @tronikos
source/_integrations/apple_tv.markdown @postlund
source/_integrations/application_credentials.markdown @home-assistant/core
source/_integrations/apprise.markdown @caronc
source/_integrations/aprilaire.markdown @chamberlain2007
source/_integrations/aprs.markdown @PhilRW
source/_integrations/aranet.markdown @aschmitz @thecode
source/_integrations/arcam_fmj.markdown @elupus
@ -90,7 +91,7 @@ source/_integrations/beewi_smartclim.markdown @alemuro
source/_integrations/bge.markdown @tronikos
source/_integrations/binary_sensor.markdown @home-assistant/core
source/_integrations/bizkaibus.markdown @UgaitzEtxebarria
source/_integrations/blebox.markdown @bbx-a @riokuu
source/_integrations/blebox.markdown @bbx-a @riokuu @swistakm
source/_integrations/blink.markdown @fronzbot @mkmer
source/_integrations/bliss_automation.markdown @starkillerOG
source/_integrations/bloc_blinds.markdown @starkillerOG
@ -103,7 +104,7 @@ source/_integrations/bluetooth_adapters.markdown @bdraco
source/_integrations/bmw_connected_drive.markdown @gerard33 @rikroe
source/_integrations/bond.markdown @bdraco @prystupa @joshs85 @marciogranzotto
source/_integrations/bosch_shc.markdown @tschamm
source/_integrations/brandt.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/brandt.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/braviatv.markdown @bieniu @Drafteed
source/_integrations/brel_home.markdown @starkillerOG
source/_integrations/bring.markdown @miaucl @tr4nt0r
@ -148,7 +149,7 @@ source/_integrations/conversation.markdown @home-assistant/core @synesthesiam
source/_integrations/coolmaster.markdown @OnFreund
source/_integrations/counter.markdown @fabaff
source/_integrations/cover.markdown @home-assistant/core
source/_integrations/cozytouch.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/cozytouch.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/cpuspeed.markdown @fabaff
source/_integrations/cribl.markdown @Bre77
source/_integrations/crownstone.markdown @Crownstone @RicArch97
@ -192,13 +193,14 @@ source/_integrations/drop_connect.markdown @ChandlerSystems @pfrazer
source/_integrations/dsmr.markdown @Robbie1221 @frenck
source/_integrations/dsmr_reader.markdown @depl0y @glodenox
source/_integrations/duotecno.markdown @cereal2nd
source/_integrations/duquesne_light.markdown @tronikos
source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @andarotajo
source/_integrations/dynalite.markdown @ziv1234
source/_integrations/eastron.markdown @DCSBL
source/_integrations/easyenergy.markdown @klaasnicolaas
source/_integrations/ecoforest.markdown @pjanuario
source/_integrations/econet.markdown @w1ll1am23
source/_integrations/ecovacs.markdown @OverloadUT @mib1185 @edenhaus
source/_integrations/ecovacs.markdown @OverloadUT @mib1185 @edenhaus @Augar
source/_integrations/ecowitt.markdown @pvizeli
source/_integrations/efergy.markdown @tkdrob
source/_integrations/egardia.markdown @jeroenterheerdt
@ -251,7 +253,7 @@ source/_integrations/fitbit.markdown @allenporter
source/_integrations/fivem.markdown @Sander0542
source/_integrations/fjaraskupan.markdown @elupus
source/_integrations/flexit_bacnet.markdown @lellky @piotrbulinski
source/_integrations/flexom.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/flexom.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/flick_electric.markdown @ZephireNZ
source/_integrations/flipr.markdown @cnico
source/_integrations/flo.markdown @dmulcahey
@ -316,8 +318,8 @@ source/_integrations/heatmiser.markdown @andylockran
source/_integrations/heiwa.markdown @cmroche
source/_integrations/heos.markdown @andrewsayre
source/_integrations/here_travel_time.markdown @eifinger
source/_integrations/hexaom.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/hi_kumo.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/hexaom.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/hi_kumo.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/hikvision.markdown @mezz64
source/_integrations/hikvisioncam.markdown @fbradyirl
source/_integrations/hisense_aehw4a1.markdown @bannhead
@ -346,6 +348,7 @@ source/_integrations/huisbaasje.markdown @dennisschroer
source/_integrations/humidifier.markdown @home-assistant/core @Shulyaka
source/_integrations/hunterdouglas_powerview.markdown @bdraco @kingy444 @trullock
source/_integrations/hurrican_shutters_wholesale.markdown @starkillerOG
source/_integrations/husqvarna_automower.markdown @Thomas55555
source/_integrations/huum.markdown @frwickst
source/_integrations/hvv_departures.markdown @vigonotion
source/_integrations/hydrawise.markdown @dknowles2 @ptcryan
@ -390,7 +393,6 @@ source/_integrations/isy994.markdown @bdraco @shbatm
source/_integrations/izone.markdown @Swamp-Ig
source/_integrations/jellyfin.markdown @j-stienstra @ctalkington
source/_integrations/jewish_calendar.markdown @tsvi
source/_integrations/juicenet.markdown @jesserockz
source/_integrations/justnimbus.markdown @kvanzuijlen
source/_integrations/jvc_projector.markdown @SteveEasley @msavazzi
source/_integrations/kaiterra.markdown @Michsior14
@ -409,6 +411,7 @@ source/_integrations/kodi.markdown @OnFreund
source/_integrations/konnected.markdown @heythisisnate
source/_integrations/kostal_plenticore.markdown @stegm
source/_integrations/kraken.markdown @eifinger
source/_integrations/krispol.markdown @starkillerOG
source/_integrations/kulersky.markdown @emlove
source/_integrations/lacrosse_view.markdown @IceBotYT
source/_integrations/lamarzocco.markdown @zweckj
@ -438,7 +441,6 @@ source/_integrations/local_todo.markdown @allenporter
source/_integrations/lock.markdown @home-assistant/core
source/_integrations/logbook.markdown @home-assistant/core
source/_integrations/logger.markdown @home-assistant/core
source/_integrations/logi_circle.markdown @evanjd
source/_integrations/london_underground.markdown @jpbede
source/_integrations/lookin.markdown @ANMalko @bdraco
source/_integrations/loqed.markdown @mikewoudenberg
@ -446,9 +448,10 @@ source/_integrations/luci.markdown @mzdrale
source/_integrations/luftdaten.markdown @fabaff @frenck
source/_integrations/lupusec.markdown @majuss @suaveolent
source/_integrations/lutron.markdown @cdheiser @wilburCForce
source/_integrations/lutron_caseta.markdown @swails @bdraco @danaues
source/_integrations/lutron_caseta.markdown @swails @bdraco @danaues @eclair4151
source/_integrations/luxaflex.markdown @bdraco @kingy444 @trullock
source/_integrations/lyric.markdown @timmo001
source/_integrations/madeco.markdown @starkillerOG
source/_integrations/marantz.markdown @ol-iver @starkillerOG
source/_integrations/martec.markdown @starkillerOG
source/_integrations/mastodon.markdown @fabaff
@ -460,7 +463,6 @@ 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
source/_integrations/melcloud.markdown @vilppuvuorinen
source/_integrations/melissa.markdown @kennedyshead
source/_integrations/melnor.markdown @vanstinator
source/_integrations/met.markdown @danielhiversen
@ -469,6 +471,7 @@ source/_integrations/meteo_france.markdown @hacf-fr @oncleben31 @Quentame
source/_integrations/meteoalarm.markdown @rolfberkenbosch
source/_integrations/meteoclimatic.markdown @adrianmo
source/_integrations/metoffice.markdown @MrHarcombe @avee87
source/_integrations/microbees.markdown @microBeesTech
source/_integrations/mijndomein_energie.markdown @klaasnicolaas
source/_integrations/mikrotik.markdown @engrbm87
source/_integrations/mill.markdown @danielhiversen
@ -494,7 +497,7 @@ source/_integrations/mutesync.markdown @currentoor
source/_integrations/my.markdown @home-assistant/core
source/_integrations/mysensors.markdown @MartinHjelmare @functionpointer
source/_integrations/mystrom.markdown @fabaff
source/_integrations/myuplink.markdown @pajzo
source/_integrations/myuplink.markdown @pajzo @astrandb
source/_integrations/nam.markdown @bieniu
source/_integrations/nanoleaf.markdown @milanmeu
source/_integrations/neato.markdown @dshokouhi @Santobert
@ -507,7 +510,7 @@ source/_integrations/netgear.markdown @hacf-fr @Quentame @starkillerOG
source/_integrations/netgear_lte.markdown @tkdrob
source/_integrations/network.markdown @home-assistant/core
source/_integrations/nexia.markdown @bdraco
source/_integrations/nexity.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/nexity.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/nextbus.markdown @vividboarder
source/_integrations/nextcloud.markdown @mib1185
source/_integrations/nextdns.markdown @bieniu
@ -561,7 +564,7 @@ source/_integrations/oru_opower.markdown @tronikos
source/_integrations/osoenergy.markdown @osohotwateriot
source/_integrations/otbr.markdown @home-assistant/core
source/_integrations/ourgroceries.markdown @OnFreund
source/_integrations/overkiz.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/overkiz.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/ovo_energy.markdown @timmo001
source/_integrations/p1_monitor.markdown @klaasnicolaas
source/_integrations/panel_custom.markdown @home-assistant/frontend
@ -641,7 +644,7 @@ source/_integrations/reolink.markdown @starkillerOG
source/_integrations/repairs.markdown @home-assistant/core
source/_integrations/repetier.markdown @ShadowBr0ther
source/_integrations/rest_command.markdown @jpbede
source/_integrations/rexel.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/rexel.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/rflink.markdown @javicalle
source/_integrations/rfxtrx.markdown @danielhiversen @elupus @RobBie1221
source/_integrations/rhasspy.markdown @balloob @synesthesiam
@ -653,7 +656,7 @@ source/_integrations/rmvtransport.markdown @cgtobi
source/_integrations/roborock.markdown @humbertogontijo @Lash-L
source/_integrations/roku.markdown @ctalkington
source/_integrations/romy.markdown @xeniter
source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn @Xitee1
source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn @Xitee1 @Orhideous
source/_integrations/roon.markdown @pavoni
source/_integrations/rpi_power.markdown @shenxn @swetoast
source/_integrations/rss_feed_template.markdown @home-assistant/core
@ -664,6 +667,7 @@ source/_integrations/ruuvitag_ble.markdown @akx
source/_integrations/rympro.markdown @OnFreund @elad-bar @maorcc
source/_integrations/sabnzbd.markdown @shaiu
source/_integrations/saj.markdown @fredericvl
source/_integrations/samsam.markdown @klaasnicolaas
source/_integrations/samsungtv.markdown @chemelli74 @epenet
source/_integrations/scene.markdown @home-assistant/core
source/_integrations/schedule.markdown @home-assistant/core
@ -699,7 +703,7 @@ source/_integrations/signal_messenger.markdown @bbernhard
source/_integrations/simplepush.markdown @engrbm87
source/_integrations/simplisafe.markdown @bachya
source/_integrations/simply_automated.markdown @gwww
source/_integrations/simu.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/simu.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/sinch.markdown @bendikrb
source/_integrations/siren.markdown @home-assistant/core @raman325
source/_integrations/sisyphus.markdown @jkeljo
@ -727,7 +731,7 @@ source/_integrations/solaredge_local.markdown @drobtravels @scheric
source/_integrations/solarlog.markdown @Ernst79
source/_integrations/solax.markdown @squishykid
source/_integrations/soma.markdown @ratsept @sebfortier2288
source/_integrations/somfy.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/somfy.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/sonarr.markdown @ctalkington
source/_integrations/songpal.markdown @rytilahti @shenxn
source/_integrations/sonos.markdown @jjlawren
@ -809,6 +813,7 @@ source/_integrations/tomorrowio.markdown @raman325 @lymanepp
source/_integrations/totalconnect.markdown @austinmroczek
source/_integrations/tplink.markdown @rytilahti @thegardenmonkey @bdraco @sdb9696
source/_integrations/tplink_omada.markdown @MarkGodwin
source/_integrations/tplink_tapo.markdown @rytilahti @thegardenmonkey @bdraco @sdb9696
source/_integrations/traccar.markdown @ludeeus
source/_integrations/traccar_server.markdown @ludeeus
source/_integrations/tractive.markdown @Danielhiversen @zhulik @bieniu
@ -823,7 +828,7 @@ source/_integrations/tuya.markdown @Tuya @zlinoliver @frenck
source/_integrations/twentemilieu.markdown @frenck
source/_integrations/twinkly.markdown @dr1rrb @Robbie1221 @Olen
source/_integrations/twitch.markdown @joostlek
source/_integrations/ubiwizz.markdown @imicknl @vlebourl @tetienne @nyroDev
source/_integrations/ubiwizz.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117
source/_integrations/ukraine_alarm.markdown @PaulAnnekov
source/_integrations/unifi.markdown @Kane610
source/_integrations/unifi_direct.markdown @tofuSCHNITZEL
@ -842,10 +847,10 @@ source/_integrations/usgs_earthquakes_feed.markdown @exxamalte
source/_integrations/utility_meter.markdown @dgomes
source/_integrations/v2c.markdown @dgomes
source/_integrations/vacuum.markdown @home-assistant/core
source/_integrations/vallox.markdown @andre-richter @slovdahl @viiru-
source/_integrations/vallox.markdown @andre-richter @slovdahl @viiru- @yozik04
source/_integrations/valve.markdown @home-assistant/core
source/_integrations/velbus.markdown @Cereal2nd @brefra
source/_integrations/velux.markdown @Julius2342
source/_integrations/velux.markdown @Julius2342 @DeerMaximum
source/_integrations/venstar.markdown @garbled1 @jhollowe
source/_integrations/vermont_castings.markdown @jeeftor
source/_integrations/versasense.markdown @imstevenxyz
@ -872,8 +877,10 @@ source/_integrations/watttime.markdown @bachya
source/_integrations/waze_travel_time.markdown @eifinger
source/_integrations/weather.markdown @home-assistant/core
source/_integrations/weatherflow.markdown @natekspencer @jeeftor
source/_integrations/weatherflow_cloud.markdown @jeeftor
source/_integrations/weatherkit.markdown @tjhorner
source/_integrations/webhook.markdown @home-assistant/core
source/_integrations/webmin.markdown @autinerd
source/_integrations/webostv.markdown @thecode
source/_integrations/websocket_api.markdown @home-assistant/core
source/_integrations/wemo.markdown @esev
@ -916,6 +923,7 @@ source/_integrations/zerproc.markdown @emlove
source/_integrations/zeversolar.markdown @kvanzuijlen
source/_integrations/zha.markdown @dmulcahey @adminiuga @puddly @TheJulianJES
source/_integrations/zodiac.markdown @JulienTant
source/_integrations/zondergas.markdown @klaasnicolaas
source/_integrations/zone.markdown @home-assistant/core
source/_integrations/zoneminder.markdown @rohankapoorcom @nabbi
source/_integrations/zwave_js.markdown @home-assistant/z-wave

6
_config.yml
View File

@ -109,9 +109,9 @@ social:
# Home Assistant release details
current_major_version: 2024
current_minor_version: 2
current_patch_version: 5
date_released: 2024-02-27
current_minor_version: 3
current_patch_version: 0
date_released: 2024-03-06
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

24
source/_dashboards/energy.markdown
View File

@ -196,3 +196,27 @@ The following example limits the number of shown devices to 5:
type: energy-devices-graph
max_devices: 5
```
## Detail devices energy graph
<p class='img'>
<img src='/images/dashboards/energy/devices-detail-graph.png' alt='Screenshot of the devices energy graph card'>
Screenshot of the detail devices energy graph card.
</p>
The **Detail devices energy graph** card is similar to the **Devices energy graph** card, but shows the individual usage on a time scale.
By default, this card will show all your devices. Optionally, the number of devices can be limited by adding the `max_devices` option and specifying the maximum number of devices to show. If there are more devices available than shown, the devices with the highest energy usage are shown.
### Examples
```yaml
type: energy-devices-detail-graph
```
The following example limits the number of shown devices to 5:
```yaml
type: energy-devices-detail-graph
max_devices: 5
```

30
source/_dashboards/sections.markdown Normal file
View File

@ -0,0 +1,30 @@
---
type: view
title: Sections (experimental)
sidebar_label: Sections (experimental)
description: "Lets you organize your cards in sections on a grid."
---
The sections view lets you organize your cards in sections on a grid.
It allows you to group card directly in sections, without having to use horizontal or vertical stack cards.
There are a few options to rearrange cards. You can move cards within the section,
move them from one section into another or even move the entire section.
You can also copy and paste cards.
To see how it works, check out the demo:
<lite-youtube videoid="XyBy0ckkiDU" videoStartAt="2047" videotitle="A Home-Approved Dashboard - Chapter 1: What about Grace?" posterquality="maxresdefault"></lite-youtube>
{% configuration %}
type:
required: false
description: "`sections`"
type: string
{% endconfiguration %}
## Related topics
- [Masonry view](/dashboards/masonry/)
- [Panel view](/dashboards/panel/)
- [Sidebar view](/dashboards/sidebar/)

26
source/_docs/configuration/templating.markdown
View File

@ -325,6 +325,32 @@ List of lights that are on with a brightness of 255:
{% endraw %}
### State translated
Not supported in [limited templates](#limited-templates).
The `state_translated` function returns a translated state of an entity using a language that is currently configured in the [general settings](https://my.home-assistant.io/redirect/general/).
#### State translated examples
{% raw %}
```text
{{ states("sun.sun") }} # below_horizon
{{ state_translated("sun.sun") }} # Below horizon
{{ "sun.sun" | state_translated }} # Below horizon
```
```text
{{ states("binary_sensor.movement_backyard") }} # on
{{ state_translated("binary_sensor.movement_backyard") }} # Detected
{{ "binary_sensor.movement_backyard" | state_translated }} # Detected
```
{% endraw %}
### Working with groups
Not supported in [limited templates](#limited-templates).

4
source/_includes/asides/dashboards_navigation.html
View File

@ -46,12 +46,12 @@
<h1 class="title delta">Advanced</h1>
<ul class="divided sidebar-menu">
<li>{% active_link /dashboards/features/ Features %}</li>
<li>{% active_link /dashboards/header-footer/ Headers & Footers %}</li>
<li>{% active_link /dashboards/header-footer/ Headers & footers %}</li>
<li>{% active_link /dashboards/actions/ Actions %}</li>
<li>
<a
href="https://developers.home-assistant.io/docs/frontend/custom-ui/custom-card/"
>Developing Custom Cards
>Developing custom cards
<i class="icon-external-link"></i>
</a>
</li>

4
source/_integrations/3_day_blinds.markdown
View File

@ -1,12 +1,12 @@
---
title: 3 Day Blinds
description: Connect and control your 3 Day Blinds devices using the Motion Blinds integration
description: Connect and control your 3 Day Blinds devices using the Motionblinds integration
ha_category:
- Cover
ha_domain: 3_day_blinds
ha_integration_type: virtual
ha_supporting_domain: motion_blinds
ha_supporting_integration: Motion Blinds
ha_supporting_integration: Motionblinds
ha_release: 2020.12
ha_codeowners:
- '@starkillerOG'

21
source/_integrations/acomax.markdown Normal file
View File

@ -0,0 +1,21 @@
---
title: Acomax
description: Connect and control your Acomax devices using the Motionblinds integration
ha_category:
- Cover
ha_domain: acomax
ha_integration_type: virtual
ha_supporting_domain: motion_blinds
ha_supporting_integration: Motionblinds
ha_release: 2020.12
ha_codeowners:
- '@starkillerOG'
ha_config_flow: true
ha_platforms:
- cover
- sensor
ha_iot_class: Local Push
ha_dhcp: true
---
{% include integrations/supported_brand.md %}

1
source/_integrations/aemet.markdown
View File

@ -9,6 +9,7 @@ ha_iot_class: Cloud Polling
ha_config_flow: true
ha_domain: aemet
ha_platforms:
- diagnostics
- sensor
- weather
ha_integration_type: integration

1
source/_integrations/airthings.markdown
View File

@ -9,6 +9,7 @@ ha_release: '2021.10'
ha_iot_class: Cloud Polling
ha_codeowners:
- '@danielhiversen'
- '@LaStrada'
ha_domain: airthings
ha_config_flow: true
ha_platforms:

74
source/_integrations/ambiclimate.markdown
View File

@ -1,74 +0,0 @@
---
title: Ambiclimate
description: Instructions on how to integrate Ambiclimate A/C controller into Home Assistant.
ha_category:
- Climate
ha_release: 0.93
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@danielhiversen'
ha_domain: ambiclimate
ha_platforms:
- climate
ha_integration_type: integration
---
Integrates [Ambiclimate](https://ambiclimate.com/) Air Conditioning controller into Home Assistant.
You must create an application [here](https://api.ambiclimate.com/clients) to obtain a `client_id` and `client_secret`.
The `callback url` should be configured as your Home Assistant external URL + `/api/ambiclimate`, e.g., `https://example.com/api/ambiclimate`.
To enable this platform, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
ambiclimate:
client_id: CLIENT_ID
client_secret: CLIENT_SECRET
```
Restart Home Assistant. Then, go to the frontend and authorize Ambiclimate.
{% configuration %}
client_id:
description: Your Ambiclimate API client ID.
required: true
type: string
client_secret:
description: Your Ambiclimate API client secret.
required: true
type: string
{% endconfiguration %}
Note that you have to select manual mode from the Ambiclimate app to be able to control the A/C from Home Assistant.
{% include integrations/config_flow.md %}
## Integration {% term services %}
Enable comfort mode on your AC:
`climate.set_comfort_mode`
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `Name` | yes | String with device name.
Send feedback for comfort mode:
`climate.send_comfort_feedback`
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `Name` | yes | String with device name.
| `value` | yes | Send any of the following comfort values: too_hot, too_warm, bit_warm, comfortable, bit_cold, too_cold, freezing
Enable temperature mode on your AC:
`climate.set_temperature_mode`
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `Name` | yes | String with device name.
| `value` | yes | Target value in Celsius

31
source/_integrations/aprilaire.markdown Normal file
View File

@ -0,0 +1,31 @@
---
title: Aprilaire
description: Instructions on how to integrate Aprilaire devices into Home Assistant.
ha_category:
- Climate
ha_iot_class: Local Push
ha_release: 2024.3
ha_domain: aprilaire
ha_codeowners:
- '@chamberlain2007'
ha_config_flow: true
ha_platforms:
- climate
ha_integration_type: device
---
The Aprilaire integration allows you to control an Aprilaire thermostat.
## Supported Models
This integration supports Aprilaire [8800-series Home Automation Wi-Fi Thermostats](https://www.aprilaire.com/whole-house-products/thermostats/home-automation) and [6000-series Wi-Fi Zone Control devices](https://www.aprilaire.com/whole-house-products/zone-control) which support setting the thermostat to automation mode. It is known that there are some models which are marketed as home automation capable that do not support automation mode, and are therefore not supported.
## Prerequisites
In order to connect to the thermostat, you will need to enable automation mode. This involves going into the Contractor Menu on your thermostat and changing the Connection Type to Automation. As the specific instructions can vary per model, consult the manual for your specific model.
{% include integrations/config_flow.md %}
## Caution regarding device limitations
Due to limitations of the thermostats, only one automation connection to a device is permitted at one time (the Aprilaire app is not included in this limitation as it uses a separate protocol). Attempting to connect multiple times to the same thermostat simultaneously can cause various issues, including the thermostat becoming unresponsive and shutting down. If this does occur, power cycling the thermostat should restore functionality.

12
source/_integrations/asterisk_cdr.markdown
View File

@ -1,12 +0,0 @@
---
title: Asterisk Call Detail Records
description: Instructions on how to integrate an Asterisk CDR within Home Assistant.
ha_category:
- Mailbox
ha_iot_class: Local Polling
ha_release: 0.79
ha_domain: asterisk_cdr
ha_integration_type: integration
---
The Asterisk Call Data Recorder provides access to Asterisk call logs on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail integration](/integrations/asterisk_mbox/) configuration if the `asterisk_mbox_server` is configured to provide CDR data. More information on configuring the server can be found in the [Asterisk PBX configuration guide](/docs/asterisk_mbox/).

49
source/_integrations/asterisk_mbox.markdown
View File

@ -1,49 +0,0 @@
---
title: Asterisk Voicemail
description: Instructions on how to integrate your existing Asterisk voicemail within Home Assistant.
ha_category:
- Mailbox
ha_iot_class: Local Push
ha_release: 0.51
ha_domain: asterisk_mbox
ha_integration_type: integration
---
The `asterisk_mbox` Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The integration includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google's API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.
To enable the integration, a configuration is required in both Home Assistant as well as on the Asterisk server.
First follow the [Asterisk PBX configuration guide](/docs/asterisk_mbox/) to setup the necessary server on the Asterisk PBX server (this is needed even if Asterisk and Home Assistant are running on the same server)
## Configuration
Once that is complete, add the following entry `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
asterisk_mbox:
password: ASTERISK_PBX_PASSWORD
host: ASTERISK_PBX_SERVER_IP_ADDRESS
port: ASTERISK_PBX_SERVER_PORT
```
This will add a new 'Mailbox' side-panel, as well as a sensor to indicate # of messages available.
{% configuration %}
password:
description: The password that was set during Asterisk PBX configuration
required: true
type: string
host:
description: The IP-address of the server that is running the Asterisk PBX
required: true
type: string
port:
description: The port on the Asterisk PBX server that was configured during Asterisk PBX configuration
required: true
type: string
{% endconfiguration %}
<div class='note warning'>
Communication between the Asterisk PBX server and Home Assistant is password-protected, but the data transmission is not encrypted. It is recommended to only use this integration when communication is contained within a local area network.
</div>

6
source/_integrations/balboa.markdown
View File

@ -4,12 +4,16 @@ description: Instructions on how to integrate Balboa Spa WiFi within Home Assist
ha_category:
- Binary sensor
- Climate
- Fan
- Light
ha_release: 2021.12
ha_iot_class: Local Push
ha_domain: balboa
ha_platforms:
- binary_sensor
- climate
- fan
- light
ha_codeowners:
- '@garbled1'
- '@natekspencer'
@ -23,6 +27,8 @@ There is currently support for the following device types within Home Assistant:
- Binary sensor (Filter cycles and circulation pumps)
- Climate
- Fan (Pumps/Jets)
- Light
## Compatible hardware

1
source/_integrations/blebox.markdown
View File

@ -9,6 +9,7 @@ ha_config_flow: true
ha_codeowners:
- '@bbx-a'
- '@riokuu'
- '@swistakm'
ha_domain: blebox
ha_platforms:
- binary_sensor

1
source/_integrations/brandt.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

10
source/_integrations/climate.markdown
View File

@ -19,7 +19,7 @@ The **Climate** {% term integration %} allows you to control and monitor HVAC (h
### Climate control services
Available services: `climate.set_aux_heat`, `climate.set_preset_mode`, `climate.set_temperature`, `climate.set_humidity`, `climate.set_fan_mode`, `climate.set_hvac_mode`, `climate.set_swing_mode`, `climate.turn_on`, `climate.turn_off`
Available services: `climate.set_aux_heat`, `climate.set_preset_mode`, `climate.set_temperature`, `climate.set_humidity`, `climate.set_fan_mode`, `climate.set_hvac_mode`, `climate.set_swing_mode`, `climate.turn_on`, `climate.turn_off`, `climate.toggle`
<div class='note'>
@ -234,6 +234,14 @@ Turn climate device off. This is only supported if the climate device has the HV
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
### Service `climate.toggle`
Toggle climate device. This is only supported if the climate device supports being turned on and off.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
## Attributes
The climate entity has extra attributes to represent the state of the thermostat.

1
source/_integrations/comelit.markdown
View File

@ -13,6 +13,7 @@ ha_platforms:
- alarm_control_panel
- climate
- cover
- humidifier
- light
- sensor
- switch

1
source/_integrations/cozytouch.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

1
source/_integrations/daikin.markdown
View File

@ -9,7 +9,6 @@ ha_category:
ha_release: 0.59
ha_iot_class: Local Polling
ha_config_flow: true
ha_quality_scale: platinum
ha_codeowners:
- '@fredrike'
ha_domain: daikin

1
source/_integrations/demo.markdown
View File

@ -65,7 +65,6 @@ Available demo platforms:
- [Image processing](/integrations/image_processing/) (`image_processing`)
- [Light](/integrations/light/) (`light`)
- [Lock](/integrations/lock/) (`lock`)
- [Mailbox](/integrations/mailbox/) (`mailbox`)
- [Media player](/integrations/media_player/) (`media_player`)
- [Notification](/integrations/notify/) (`notify`)
- [Number](/integrations/number/) (`number`)

20
source/_integrations/duquesne_light.markdown Normal file
View File

@ -0,0 +1,20 @@
---
title: Duquesne Light
description: Get energy usage from Duquesne Light using the Opower integration
ha_category:
- Energy
- Sensor
ha_release: 2023.8
ha_domain: duquesne_light
ha_integration_type: virtual
ha_supporting_domain: opower
ha_supporting_integration: Opower
ha_codeowners:
- '@tronikos'
ha_config_flow: true
ha_platforms:
- sensor
ha_iot_class: Cloud Polling
---
{% include integrations/supported_brand.md %}

8
source/_integrations/ecovacs.markdown
View File

@ -1,8 +1,9 @@
---
title: Ecovacs
description: Instructions on how to integrate Ecovacs vacuums within Home Assistant.
description: Instructions on how to integrate Ecovacs vacuums and mowers within Home Assistant.
ha_category:
- Hub
- Lawn mower
- Vacuum
ha_iot_class: Cloud Push
ha_release: 0.77
@ -10,6 +11,7 @@ ha_codeowners:
- '@OverloadUT'
- '@mib1185'
- '@edenhaus'
- '@Augar'
ha_config_flow: true
ha_domain: ecovacs
ha_platforms:
@ -25,7 +27,7 @@ ha_platforms:
ha_integration_type: integration
---
The `ecovacs` {% term integration %} is the main integration to integrate [Ecovacs](https://www.ecovacs.com) (Deebot) vacuums. You will need your Ecovacs account information (username, password) to discover and control vacuums in your account.
The `ecovacs` {% term integration %} is the main integration to integrate [Ecovacs](https://www.ecovacs.com) (Deebot) vacuums and mowers. You will need your Ecovacs account information (username, password) to discover and control vacuums and mowers in your account.
{% include integrations/config_flow.md %}
@ -140,4 +142,4 @@ Depending on your setup of the self-hosted instance, you can connect to the serv
Replace `SELF_HOSTED_INSTANCE` with either the IP address or the hostname of your instance.
The above configuration is based on the information from [Bumper's documentation](https://bumper.readthedocs.io).
The above configuration is based on the information from [Bumper's documentation](https://bumper.readthedocs.io).

33
source/_integrations/enphase_envoy.markdown
View File

@ -36,9 +36,22 @@ This integration will offer various sensors depending on the configuration of yo
- Historical energy production & consumption
- Power production per-inverter
Production and consumption sensors for each phase are available for Envoy S Metered / IQ Gateway Metered with installed and configured current transformers (CT) on more than 1 phase.
_Consumption sensors require your Envoy to be properly configured with consumption <abbr title="current transformers">CT</abbr> sensors installed._
_Consumption sensors require your Envoy to be properly configured with consumption CT sensors installed._
For Envoy S Metered / IQ Gateway Metered with installed and configured current transformers (CT), additional features are available:
- Production and consumption sensors for each phase, if <abbr title="current transformers">CT</abbr> are installed on more than 1 phase.
- Sensors for net production (grid export) and net consumption (grid import) if the consumption <abbr title="current transformers">CT</abbr> is a net-consumption <abbr title="current transformers">CT</abbr>.
- Disabled sensors for:
- Phase net production and net consumption.
- Frequency net consumption <abbr title="current transformers">CT</abbr> (aggregate and phase).
- Voltage net consumption <abbr title="current transformers">CT</abbr> (aggregate and phase).[^1]
- Metering status for net consumption and production <abbr title="current transformers">CT</abbr> (`normal` | `not-metering` | `check-wiring`) (aggregate and phase).
- Meter status flags active for net consumption and production <abbr title="current transformers">CT</abbr> (aggregate and phase).[^2]
[^1]: For multi-phase systems, the Envoy sums the voltages of the phases. May be valid for split-phase, but for 3-phase systems use the individual phases rather than the summed value.
[^2]: If this value is non-zero, consult the diagnostic report of the Envoy and look for `raw_data` - `/ivp/meters` - `statusFlags` for set flags (`production-imbalance` | `negative-production` | `power-on-unused-phase` | `negative-total-consumption`).
For Enphase Ensemble systems with the Enpower/IQ System Controller and Encharge/IQ Batteries installed, additional features are available:
@ -70,3 +83,19 @@ When the relay mode is set to battery level, the relays will turn on and off bas
## Polling interval
The default polling interval is 60 seconds. To customize the polling interval, refer to [defining a custom polling interval](/common-tasks/general/#defining-a-custom-polling-interval). Specify one single entity from the envoy device as target of the service using the `+ choose entity` button. Updating one entity will update all entities of the Envoy and the related devices like the inverters; there is no need to specify multiple or all entities or add (all) inverter entities. When using multiple Envoys, add one entity for each envoy as targets or create separate custom polling intervals with a single entity as needed.
## Credentials update
This integration supports updating configuration by re-adding the integration and specifying the same or new IP address, username, and password. Use this method if your Enlighten credentials or the device's IP address has changed and needs to be updated.
## Energy dashboard
This integration provides several values suitable for the energy dashboard:
- For `Solar production`, use the `Envoy Lifetime energy production` entity.
- For `Grid consumption`, use the `Envoy Lifetime net energy consumption` entity.[^3]
- For `Return to grid`, use the `Envoy Lifetime net energy production` entity.[^3]
[^3]: Only applies when using Envoy S Metered / IQ Gateway Metered with installed and configured current transformers (<abbr title="current transformers">CT</abbr>).
There are no readily available battery energy sensors for use with the `Home Battery storage`. You can consider using the Encharge `real_power_mw` entity as an input to Riemann integrators for charge (negative) or discharge (positive) values. As the [polling interval](#polling-interval) is 1 minute, these may be off though.

11
source/_integrations/flexit_bacnet.markdown
View File

@ -9,6 +9,7 @@ ha_domain: flexit_bacnet
ha_platforms:
- binary_sensor
- climate
- number
- sensor
- switch
ha_integration_type: device
@ -63,6 +64,16 @@ The integration adds entities for sensors with different readings from the devic
The integration adds an entity for a binary sensor called _Air filter polluted_ which tells if it's time to change the filters in the unit.
### Number
The integration adds entities for setting setpoints for the fan in the respective mode:
- Away
- Home
- Fireplace
- High
- Cooker hood
### Switch
The integration adds an entity for a switch called _Electric heater_ that controls the heating element in the unit.

1
source/_integrations/flexom.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

4
source/_integrations/fujitsu_anywair.markdown
View File

@ -2,14 +2,14 @@
title: Fujitsu anywAIR
description: Connect and control your Fujitsu anywAIR devices using the Advantage Air integration
ha_category:
- Binary switch
- Binary sensor
- Climate
- Cover
- Light
- Select
- Sensor
- Switch
- Update
- Update
ha_release: 0.117
ha_domain: fujitsu_anywair
ha_supporting_domain: advantage_air

4
source/_integrations/generic_thermostat.markdown
View File

@ -89,6 +89,10 @@ comfort_temp:
description: "Set the temperature used by `preset_mode: comfort`."
required: false
type: float
eco_temp:
description: "Set the temperature used by `preset_mode: eco`."
required: false
type: float
home_temp:
description: "Set the temperature used by `preset_mode: home`."
required: false

3
source/_integrations/govee_light_local.markdown
View File

@ -25,6 +25,7 @@ To enable local control on your Govee device, refer to the instructions availabl
H6046,
H6047,
H6051,
H6052,
H6056,
H6059,
H6061,
@ -37,6 +38,8 @@ H6073,
H6076,
H6078,
H6087,
H6088,
H608A,
H610A,
H610B,
H6117,

1
source/_integrations/hexaom.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

1
source/_integrations/hi_kumo.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

2
source/_integrations/history.markdown
View File

@ -53,4 +53,4 @@ The history information is also available through the
## Related topics
- [Recorder integration](/integrations/recorder/)
- [Home Assistant Data Science Portal](https://data.home-assistant.io)
- [Home Assistant Data Science Portal](https://data.home-assistant.io)

56
source/_integrations/hunterdouglas_powerview.markdown
View File

@ -4,6 +4,7 @@ description: Instructions on how to setup Hunter Douglas PowerView scenes within
ha_category:
- Button
- Cover
- Number
- Scene
- Select
- Sensor
@ -20,6 +21,7 @@ ha_platforms:
- button
- cover
- diagnostics
- number
- scene
- select
- sensor
@ -34,36 +36,54 @@ There is currently support for the following device types within Home Assistant:
- Button
- Cover
- Number
- Scene
- Select
- Sensor
<div class="note">
The Powerview Hub does not automatically wake shades or report position changes made via pebble remotes.
{% include integrations/config_flow.md %}
Calling the update entity service (`homeassistant.update_entity`) on a shade entity will trigger the hub to awaken a shade and report its current position. [An example automation is available](#force-update-shade-position) below for mains powered shades. While the automation will work for battery-powered shades, it will quickly drain their batteries for these devices.
## Hub capabilities
### Generation 1 + 2
Generation 1 and 2 hubs work better with Home Assistant when all calls are made directly via the Powerview application or Home Assistant itself.
Generation 1 and 2 Pebble remotes use proprietary Bluetooth Low Energy (PLE) and do not report shade position changes back to the hub.
This will result in the shade positioning displayed within Home Assistant being incorrect.
<div class="note">
Calling the update entity service (`homeassistant.update_entity`) on a shade entity will trigger the hub to awaken a shade and report its current position.
[An example automation is available](#force-update-shade-position) below for mains powered shades. While the automation will work for battery-powered shades, it will quickly drain the batteries for these devices.
</div>
{% include integrations/config_flow.md %}
### Generation 3
Generation 3 introduced RF Radio Pebble Remotes.
Generation 3 shades report position changes back to the hub automatically. They should appear correctly in Home Assistant without requiring any additional automations or considerations for positioning.
## Shades
### Known working devices
<div class="note">
If your shade is not listed please raise a feature request on the community forum.
Your shades may still make work even if not listed. If you encounter issues, please raise a feature request on the community forum.
</div>
| Name (Type) | Capabilities |
| :---------------------------------------- | :------------------------------ |
| AC Roller (49) | Bottom Up |
| Banded Shades (52) | Bottom Up |
| Bottom Up (5) | Bottom Up |
| Curtain, Left Stack (69) | Vertical |
| Curtain, Right Stack (70) | Vertical |
| Curtain, Split Stack (71) | Vertical |
| Facette (43) | Bottom Up TiltOnClosed 90° |
| Designer Roller (1) | Bottom Up |
| Duette (6) | Bottom Up |
| Duette, Top Down Bottom Up (8) | Top Down Bottom Up |
| Duette and Applause SkyLift (10) | Bottom Up |
| Duette Architella, Top Down Bottom Up (9) | Top Down Bottom Up |
| Duette DuoLite, Top Down Bottom Up (9) | Top Down Bottom Up |
| Duolite Lift (79) | Dual Shade Overlapped |
@ -71,6 +91,7 @@ If your shade is not listed please raise a feature request on the community foru
| Palm Beach Shutters (66) | Tilt Only 180° |
| Pirouette (18) | Bottom Up TiltOnClosed 90° |
| Pleated, Top Down Bottom Up (47) | Top Down Bottom Up |
| Provenance Woven Wood (19) | Bottom Up |
| Roman (4) | Bottom Up |
| Silhouette (23) | Bottom Up TiltOnClosed 90° |
| Silhouette Duolite (38) | Dual Shade Overlapped Tilt 90° |
@ -84,6 +105,9 @@ If your shade is not listed please raise a feature request on the community foru
| Vertical Slats, Left Stack (54) | Vertical TiltAnywhere 180° |
| Vertical Slats, Right Stack (55) | Vertical TiltAnywhere 180° |
| Vertical Slats, Split Stack (56) | Vertical TiltAnywhere 180° |
| Vignette (31) | Bottom Up |
| Vignette (32) | Bottom Up |
| Vignette (84) | Bottom Up |
| Vignette Duolite (65) | Dual Shade Overlapped |
## Capabilities Information
@ -157,6 +181,9 @@ Three different entities that will be created for each blind: Front, Rear and Co
### Calibrate
<div class="note">
Gen 1 and Gen 2 Only.
</div>
Initiate a calibration of the shade position. Calibration is a common requirement with Duette-type shades with a string drop that lowers and raises the blind and less so with roller types.
### Identify
@ -165,14 +192,29 @@ Identify will 'jog' the shade position as a diagnostic tool to ensure the shade
### Favorite
<div class="note">
Gen 1 and Gen 2 Only.
</div>
Move the shade to the favorite position as programmed physically on the device. This will perform the same move as the heart on the pebble remote.
## Selection Entities
### Power Source
<div class="note">
Gen 1 and Gen 2 Only.
</div>
Set the type for connected power source. Available options are Hardwired Power Supply, Battery Wand and Rechargeable Battery
## Number entities
### Velocity
<div class="note">
Gen 3 Only.
</div>
Velocity controls the speed of the shade. The default speed from Hunter Douglas is 0; setting this higher will increase the speed of the shade.
## Example Automations
### Calling a Powerview Scene

109
source/_integrations/husqvarna_automower.markdown Normal file
View File

@ -0,0 +1,109 @@
---
title: Husqvarna Automower
description: Instructions on how to integrate Husqvarna Automower lawn mowers into Home Assistant.
ha_category:
- Lawn Mower
- Sensor
- Switch
ha_release: 2024.3
ha_iot_class: Cloud Push
ha_config_flow: true
ha_codeowners:
- '@Thomas55555'
ha_platforms:
- lawn_mower
- sensor
- switch
ha_integration_type: integration
ha_domain: husqvarna_automower
---
The Husqvarna Automower integration provides connectivity with Husqvarna Automowers lawn mowers through Husqvarna's cloud API. Only mowers with *Automower® Connect* or with the *Automower® Connect Module* are supported.
In order to use this integration you must properly configure OAuth2 credentials using your Husqvarna account. Refer to [this guide](https://developer.husqvarnagroup.cloud/docs/get-started) for general overview of the process.
Your Husqvarna account username/password used for the *Automower® Connect* phone app is required. Most users probably created a Husqvarna account during initial mower setup.
1. Go to the [Husqvarna Developer Portal](https://developer.husqvarnagroup.cloud) and sign in with your Husqvarna account. Authorize *Developer Portal* to access Husqvarna account when prompted.
2. After signing in you will be automatically redirected to "My applications". (Otherwise go to: [Applications](https://developer.husqvarnagroup.cloud/applications))
3. Create a new application:
- Name is required but can be anything, for example "My Home Assistant"
- Description is optional
- Redirect URL: `https://my.home-assistant.io/redirect/oauth`
Make sure no extra spaces were appended at end of URL from copy and paste.
![Create new Application](/images/integrations/husqvarna_automower/create_new_application.png)
- Click **CREATE**. *Application Key* and *Application Secret* will be generated and shown. Protect these like a username and password.
4. Click on **CONNECT NEW API** and connect the **Authentication API**.
![Authentication API*](/images/integrations/husqvarna_automower/connect_authentication_api.png)
5. Click on **CONNECT NEW API** again and connect the **Automower Connect API**.
![Automower Connect API](/images/integrations/husqvarna_automower/connect_automower_api.png)
6. Leave this tab open in browser and continue with Home Assistant configuration.
![Application Overview](/images/integrations/husqvarna_automower/application_overview.png)
### Home Assistant
The My Home Assistant redirect feature needs to be setup to redirect to your Home Assistant installation. See [My FAQ](https://my.home-assistant.io/faq) for additional information.
1. Add the integration to your Home Assistant installation and test the redirect feature by following below link:
[![my_button](https://my.home-assistant.io/badges/config_flow_start.svg)](https://my.home-assistant.io/redirect/config_flow_start/?domain=husqvarna_automower)
2. Acknowledge prompts to open link, install Husqvarna Automower integration.
3. Acknowledge prompt to setup application credentials.
4. Enter the following from the Husqvarna developer tab:
- A name of the application
- Copy and paste the *Application key* into the *OAuth Client ID* field
- Copy and paste the *Application secret* into the *OAuth Client Secret* field
5. Click **Create**
6. Browser will be redirected to Husqvarna Developer site. Sign in and Authorize the integration to connect with your Husqvarna account
7. After authorizing the integration the browser will show the My Home Assistant redirect link to link this account. Click on **Link Account**.
8. Confirm successful connection of mower and assign to an area.
{% include integrations/config_flow.md %}
## Entities
Once you have enabled the Husqvarna Automower integration, you should see the following entities:
### Lawn Mower
The integration will create a lawn mower entity to control the mower. This entity can:
- Resume the schedule
- Pause mowing
- Park until next schedule
### Sensor
The integration will create the following sensors:
- Battery level
- Cutting blade usage time (if available)
- Mode
- Next start
- Number of charging cycles
- Number of collisions
- Total charging time
- Total cutting time
- Total drive distance
- Total running time
- Total searching time
### Switch
The integration will create a switch to enable or disable the schedule of the mower. If the switch is on, the mower will mow according to the schedule. If the switch is off the mower will return to the dock and park until further notice.

1
source/_integrations/imap.markdown
View File

@ -7,6 +7,7 @@ ha_release: 0.25
ha_iot_class: Cloud Push
ha_domain: imap
ha_platforms:
- diagnostics
- sensor
ha_integration_type: integration
ha_codeowners:

49
source/_integrations/juicenet.markdown
View File

@ -1,49 +0,0 @@
---
title: JuiceNet
description: Instructions on how to setup WiFi-equipped JuiceNet/JuiceBox charging stations with Home Assistant.
ha_category:
- Car
- Energy
- Number
- Sensor
- Switch
ha_iot_class: Cloud Polling
ha_release: 0.47
ha_codeowners:
- '@jesserockz'
ha_domain: juicenet
ha_config_flow: true
ha_platforms:
- number
- sensor
- switch
ha_integration_type: integration
---
The `juicenet` platform pulls data from a [JuiceNet](https://evcharging.enelx.com/products/juicebox) charging station equipped with a Wi-Fi connection. It will access and make available all of the devices attached to your account. It also exposes a switch allowing you to charge your car now instead of waiting for the pre-set schedule.
{% include integrations/config_flow.md %}
## Sensor
The `juicenet` sensor platform allows you to get data from your [JuiceNet](https://evcharging.enelx.com/products/juicebox) charger.
### Added sensors
These sensors will be added for each JuiceNet device in your account:
- Status
- Temperature (inside the device)
- Voltage
- Amps
- Watts
- Charge time of session
- Energy added this session
## Switch
The `juicenet` switch platform allows you to override the charging schedule for your JuiceNet device.
## Number
The `juicenet` number platform allows you to control the charging amperage limit.

2
source/_integrations/keymitt_ble.markdown
View File

@ -12,7 +12,7 @@ ha_bluetooth: true
ha_platforms:
- switch
ha_config_flow: true
ha_integration_type: integration
ha_integration_type: hub
---
This integration allows you to locally control a [MicroBot Push](https://keymitt.com/products/microbot-push) (previously manufactured by Naran but now under the Keymitt brand).

2
source/_integrations/kitchen_sink.markdown
View File

@ -10,9 +10,11 @@ ha_codeowners:
ha_domain: kitchen_sink
ha_iot_class: Calculated
ha_platforms:
- button
- image
- lock
- sensor
- switch
- weather
ha_integration_type: integration
---

21
source/_integrations/krispol.markdown Normal file
View File

@ -0,0 +1,21 @@
---
title: Krispol
description: Connect and control your Krispol devices using the Motionblinds integration
ha_category:
- Cover
ha_domain: krispol
ha_integration_type: virtual
ha_supporting_domain: motion_blinds
ha_supporting_integration: Motionblinds
ha_release: 2020.12
ha_codeowners:
- '@starkillerOG'
ha_config_flow: true
ha_platforms:
- cover
- sensor
ha_iot_class: Local Push
ha_dhcp: true
---
{% include integrations/supported_brand.md %}

9
source/_integrations/lamarzocco.markdown
View File

@ -11,6 +11,7 @@ ha_domain: lamarzocco
ha_platforms:
- binary_sensor
- button
- calendar
- diagnostics
- number
- select
@ -59,6 +60,10 @@ Host:
| Coffee target temperature | Temperature the coffee boiler is set to | GS3 AV, GS3 MP | - |
| Steam target temperature | Temperature the steam boiler is set to | GS3 AV, GS3 MP | - |
| Tea water duration | Dose hot water (in seconds) | GS3 AV, GS3 MP | - |
| Dose | Doseage (in ticks) for each key | GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
| Prebrew on time | Time prebrew wets the puck | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
| Prebrew off time | Time prebrew waits before turning on the pump | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
| Preinfusion time | Duration of preinfusion | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
## Switches
@ -99,3 +104,7 @@ Host:
|-------------|-------------| ------------------------| ---------------------- |
| Prebrew/-infusion mode | Whether to use prebrew, preinfusion, or neither | Disabled, Prebrew, Preinfusion | Linea Micra, Linea Mini, GS3 AV |
| Steam level | The level your steam boiler should run at | 1,2,3 | Linea Micra |
## Calendar
The integration exposes a calendar for the auto on/off schedule set for the machine. The schedule will be displayed recurringly: If you set the machine to start up on Mondays at 8:00, and shut down at 9:00, you will get events for all Mondays in your calendar. On days when you have the auto on/off feature disabled, you won't get an event in the calendar. Also, if you have the auto on/off feature disabled globally (for example, through the switch "Auto on/off"), there will be no events in the calendar.

166
source/_integrations/logi_circle.markdown
View File

@ -1,166 +0,0 @@
---
title: Logi Circle
description: Instructions on how to integrate your Logi Circle cameras within Home Assistant.
ha_category:
- Camera
- Sensor
ha_release: 0.79
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@evanjd'
ha_domain: logi_circle
ha_platforms:
- camera
- sensor
ha_integration_type: integration
---
The `logi_circle` implementation allows you to integrate your [Logi Circle](https://circle.logi.com/) cameras in Home Assistant. To connect Logi Circle, you will have to [sign up for API access](#requesting-api-access) and get a `client_id`, `client_secret` and `api_key`.
## Requesting API access
1. Navigate to the [Circle OAuth2 Client Request Form](https://docs.google.com/forms/d/184FUILJ10rVxotyOQR5DAiu6GcCbK31AZszUdzT1ybs).
2. Fill out your contact name and e-mail address.
3. For the User Visible Client Name, specify "Home Assistant"
4. Request the following scopes:
- `circle:activities`
- `circle:accessories`
- `circle:live_image`
- `circle:live`
- `circle:notifications`
- `circle:summaries`
5. Request the `authorization_code` grant type.
6. For the redirect URI, specify your Home Assistant URL followed by `/api/logi_circle`. For example, if your Home Assistant URL is `https://abc123.ui.nabu.casa`, then request `https://abc123.ui.nabu.casa/api/logi_circle`. The redirect URI must meet the following criteria:
- The URL must be HTTPS with a SSL certificate issued by a trusted CA (i.e., trusted by normal browsers).
- At the time you submit your request to Logitech, you need to demonstrate that you have exclusive control of the fully qualified domain name in your redirect URI. An active Home Assistant instance at the redirect URI will suffice. If you don't want to expose your Home Assistant instance publicly, you may also place a static page at the redirect URI with a short message that you will manage redirection of the authorization token to your local Home Assistant instance. Free static hosts that issue subdomains for hosting (e.g., Netlify) are permitted.
- As the redirect URI must be public facing, no local/reserved TLDs are permitted (eg. .local, .localhost, .example, etc. are not allowed).
Please note that the turn-around time for API access takes up to a month after which you will be contacted by Logitech using the email address you provided in the form.
## Configuration
To integrate cameras linked with your [Logi Circle](https://circle.logi.com/) account, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
logi_circle:
client_id: YOUR_CLIENT_ID
client_secret: YOUR_CLIENT_SECRET
api_key: YOUR_API_KEY
redirect_uri: YOUR_REDIRECT_URI
```
{% configuration %}
client_id:
description: The client ID issued to you by Logitech.
required: true
type: string
client_secret:
description: The client secret issued to you by Logitech.
required: true
type: string
api_key:
description: The API key issued to you by Logitech.
required: true
type: string
redirect_uri:
description: >
The redirect URI that corresponds to your Home Assistant instance.
It must match one of the redirect URIs specified when you requested API
access from Logitech.
required: true
type: string
{% endconfiguration %}
### Camera
The `logi_circle` camera platform allows you to view still frames from your [Logi Circle](https://circle.logi.com/) camera's live stream in Home Assistant.
Logi Circle cameras support the `camera.turn_on` and `camera.turn_off` services. This will set the streaming mode property of your camera accordingly, controlling whether the live stream is available and activity recordings are captured.
### Sensor
The `logi_circle` sensor platform lets you monitor sensors connected to your [Logi Circle](https://circle.logi.com) cameras in Home Assistant.
To customize which sensors are setup, you can extend the Logi Circle integration configuration in your `configuration.yaml` file with the following settings:
```yaml
# Example configuration.yaml entry
logi_circle:
sensors:
monitored_conditions:
- battery_level
- last_activity_time
- recording
- signal_strength_category
- signal_strength_percentage
- streaming
```
By default, all sensors available from your Logi Circle devices will be monitored. Leave `monitored_conditions` blank to disable all sensors for the Logi Circle integration. Devices without an internal battery will not expose a `battery_level` sensor.
{% configuration %}
sensor:
description: Configuration to pass to all sensors.
required: false
type: map
keys:
monitored_conditions:
description: The conditions to create sensors from.
required: false
type: list
default: all
keys:
battery_level:
description: Returns the battery level percentage from the camera.
last_activity_time:
description: Return the timestamp from the last time the Logi Circle camera detected any activity.
recording:
description: The camera's recording mode. If false, the camera will not capture activities.
signal_strength_category:
description: Return the Wi-Fi signal level from the camera.
signal_strength_percentage:
description: Return the Wi-Fi signal percentage from the camera.
streaming:
description: The soft on/off status of the camera.
{% endconfiguration %}
## Services
The `logi_circle` platform exposes 3 services for interacting with your Logi Circle device. When calling a service with one or more entity IDs, please ensure you target the camera entity (eg. `camera.living_room_camera`).
### Service `logi_circle.livestream_record`
Initiates a recording of the camera's live stream.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------ |
| `entity_id` | yes | Name(s) of entities to initiate a recording for, e.g., `camera.living_room_camera`. If blank, targets all Logi Circle cameras. |
| `filename ` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/recording_{{ entity_id }}.mp4`{% endraw %}. |
| `duration` | no | Duration of recording, in seconds. |
The path part of `filename` must be an entry in the `allowlist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file.
### Service `logi_circle.livestream_snapshot`
Take a snapshot from a camera's live stream. This differs from the generic [snapshot](/integrations/camera/#service-snapshot) service in that explicitly requests a fresh image from Logi Circle's API. This will force cameras in a deep sleep state to wake.
Please note that new snapshots will only be generated if the cached snapshot is older than 30s. Requesting multiple snapshots in quick succession will likely return the same image. Likewise, requesting a snapshot from a camera that is actively streaming (ie. is not in deep sleep) will return a cached image no older than 30s.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | yes | Name(s) of entities to create a live stream snapshot from, e.g., `camera.living_room_camera`. If blank, targets all Logi Circle cameras. |
| `filename` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/snapshot_{{ entity_id }}.jpg`{% endraw %}. |
The path part of `filename` must be an entry in the `allowlist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file.
### Service `logi_circle.set_config`
Sets a configuration property for your camera.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | yes | Name(s) of entities to set the operation mode for, e.g., `camera.living_room_camera`. If blank, targets all Logi Circle cameras. |
| `mode` | no | Configuration property to set. Allowed values: `LED`, `RECORDING_MODE` |
| `value` | no | Mode value. Allowed values: `true`, `false` |

1
source/_integrations/lutron_caseta.markdown
View File

@ -19,6 +19,7 @@ ha_codeowners:
- '@swails'
- '@bdraco'
- '@danaues'
- '@eclair4151'
ha_zeroconf: true
ha_homekit: true
ha_platforms:

2
source/_integrations/luxaflex.markdown
View File

@ -4,6 +4,7 @@ description: Connect and control your Luxaflex devices using the Hunter Douglas
ha_category:
- Button
- Cover
- Number
- Scene
- Select
- Sensor
@ -21,6 +22,7 @@ ha_platforms:
- button
- cover
- diagnostics
- number
- scene
- select
- sensor

21
source/_integrations/madeco.markdown Normal file
View File

@ -0,0 +1,21 @@
---
title: Madeco
description: Connect and control your Madeco devices using the Motionblinds integration
ha_category:
- Cover
ha_domain: madeco
ha_integration_type: virtual
ha_supporting_domain: motion_blinds
ha_supporting_integration: Motionblinds
ha_release: 2020.12
ha_codeowners:
- '@starkillerOG'
ha_config_flow: true
ha_platforms:
- cover
- sensor
ha_iot_class: Local Push
ha_dhcp: true
---
{% include integrations/supported_brand.md %}

17
source/_integrations/mailbox.markdown
View File

@ -1,17 +0,0 @@
---
title: Mailbox
description: Instructions on how to setup your mailboxes with Home Assistant.
ha_release: 0.51
ha_domain: mailbox
ha_quality_scale: internal
ha_category: []
ha_integration_type: entity
---
Mailboxes provide a list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend.
Home Assistant currently supports only the [Asterisk Voicemail](/integrations/asterisk_mbox/) mailbox.
Each mailbox also provides an entity to indicate the number of messages available on the main page.
{% include integrations/building_block_integration.md %}

38
source/_integrations/matter.markdown
View File

@ -277,6 +277,44 @@ Follow these steps if you have added a Matter device to Home Assistant and you w
- For example, if you shared it with Google Home, it lists **Google LLC**.
![image](/images/integrations/matter/matter_share-device-with-other-platform.png)
## Removing a device from a Matter controller
Follow these steps if you want to remove a device from a particular Matter controller.
1. Go to {% my integrations title="**Settings** > **Devices & services**" %} and on the **Matter (BETA)** integration card, select **Devices**.
2. From the list of devices, select the device you want to remove from a controller.
3. In the **Device info** section, next to **Share device**, select the three-dot menu. Then, select **Manage fabrics**.
4. From the list, remove the controller of interest.
- If you want to remove Apple Home, also remove the Apple Keychain entry.
![image](/images/integrations/matter/matter-remove-from-network.png)
5. If you want to remove the device from Home Assistant itself, select the three-dot menu and select **Delete**.
## About Matter device information
The device information section provides some diagnostic information of a device.
1. To view the device details, go to {% my integrations title="**Settings** > **Devices & services**" %} and on the **Matter (BETA)** integration card, select **Devices**.
2. From the list of devices, select the device you want to look at.
<p class='img'>
<img src='/images/integrations/matter/matter_device-info.png' alt='Matter device information'>
</p>
This section provides a bit more information on some of the categories:
**Network type**: Shows which network type the device belongs to. For example, Thread or Wi-Fi.
**Device type**: There are 4 device types:
- **End device**: End device that always keeps its radio on. Typically these devices are not battery-powered.
- **Sleepy end device**: non-routing end device. Normally sleeping, wakes on occasion to check for messages. Typically battery-powered.
- **Routing end device**: End device that always keeps its radio on and can route traffic for other, routing and non-routing end devices.
- **Bridge**
**Network name**: Name of the network the device joined when it was commissioned.
**IP addresses**: Typically more than one IPv6 address is shown: link local, unique local, and global unicast. In some cases a device also supports IPv4. In that case there will also be listed an IPv4 address here.
## Experiment with Matter using a ESP32 dev board
You do not yet have any Matter-compatible hardware but you do like to try it out or maybe create your own DIY Matter device? We have [prepared a page for you](https://nabucasa.github.io/matter-example-apps/) where you can easily flash Matter firmware to a supported ESP32 development board. We recommend the M5 Stamp C3 device running the Lighting app.

2
source/_integrations/melcloud.markdown
View File

@ -6,8 +6,6 @@ ha_category:
ha_release: 0.106
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@vilppuvuorinen'
ha_domain: melcloud
ha_platforms:
- climate

34
source/_integrations/microbees.markdown Normal file
View File

@ -0,0 +1,34 @@
---
title: microBees
description: Instructions on how to integrate microBees devices into Home Assistant.
ha_category:
- Button
- Light
- Sensor
- Switch
ha_release: 2024.3
ha_codeowners:
- '@microBeesTech'
ha_config_flow: true
ha_domain: microbees
ha_iot_class: Cloud Polling
ha_platforms:
- button
- light
- sensor
- switch
ha_integration_type: integration
---
The microbees integration allows you to control your [microBees devices](https://www.microbees.com/) such as plugs and wall switches.
To use this integration you need OAuth2 Client ID and Client Secret and your user credentials.
To retrieve the OAuth2 Client ID and Client Secret go to [microBees Developer Dashboard](https://developers.microbees.com/dashboard), login with your microBees account and [create a new app](https://developers.microbees.com/dashboard/?p=wizard), choose a Label for your App, select WebApplication and input https://my.home-assistant.io as Website URL.
There is currently support for the following device types within Home Assistant:
- **Switch**
- **Button**
- **Light**
- **Sensor**
{% include integrations/config_flow.md %}

6
source/_integrations/mopeka.markdown
View File

@ -27,3 +27,9 @@ The integration only supports measuring LPG (Liquefied petroleum gas). Other sub
- [Pro Plus](https://www.mopekaiot.com/product/mopeka-pro-plus-sensor) (M1015)
- [Pro Check](https://www.mopekaiot.com/product/mopeka-pro-check-sensor-aluminum-lpg-cylinders-w-collar) (M1017)
- Pro-200
- [Pro H2O](https://www.mopekaiot.com/product/mopeka-pro-check-water-sensor-bottom-mount-w-collar)
- [Lippert BottleCheck](https://store.lci1.com/lippert-propane-tank-sensor-2021130655)
- [TD40](https://www.mopekaiot.com/product/mopeka-td40)
- TD200
- [Pro Check Universal](https://www.mopekaiot.com/procheckuniversal)

3
source/_integrations/motion_blinds.markdown
View File

@ -7,7 +7,7 @@ ha_iot_class: Local Push
ha_release: 2020.12
ha_domain: motion_blinds
ha_codeowners:
- "@starkillerOG"
- '@starkillerOG'
ha_config_flow: true
ha_platforms:
- cover
@ -33,6 +33,7 @@ Additionally the following brands have been reported to also work with this inte
- [Hurrican Shutters Wholesale](https://www.hurricaneshutterswholesale.com/)
- [Inspired Shades](https://www.inspired-shades.com/)
- [iSmartWindow](https://www.ismartwindow.co.nz/)
- [Krispol](https://krispol.eu/en/drives/)
- [Madeco](https://www.madeco.fr/)
- [Martec](https://www.martec.co.nz/)
- [Motionblinds](https://motionblinds.com/)

17
source/_integrations/myuplink.markdown
View File

@ -2,21 +2,31 @@
title: myUplink
description: Instructions on how to set up the myUplink integration within Home Assistant.
ha_category:
- Binary sensor
- Number
- Sensor
- Switch
- Update
ha_iot_class: Cloud Polling
ha_release: '2024.2'
ha_domain: myuplink
ha_codeowners:
- '@pajzo'
- '@astrandb'
ha_config_flow: true
ha_integration_type: integration
ha_platforms:
- binary_sensor
- diagnostics
- number
- sensor
- switch
- update
ha_integration_type: integration
---
The myUplink integration lets you get information about the devices supporting myUplink using the [official cloud API](https://dev.myuplink.com).
Depending on the type of devices in your system, one or more sensor entities to Home Assistant. Currently, there is only support for reading sensor states.
Depending on the type of devices in your system, one or more entities are added to Home Assistant. Currently, there is support for reading sensor states. There is also support for switches and number entities if suitable data points are discovered in the system. Note that you may need a valid subscription with MyUplink to control your equipment with switches and number entities.
## Prerequisites
@ -27,7 +37,6 @@ Depending on the type of devices in your system, one or more sensor entities to
- **OAuth Flow**: Authorization Code Grant Flow
- **Redirect URI**: `https://my.home-assistant.io/redirect/oauth`
{% details "I have manually disabled My Home Assistant" %}
If you don't have [My Home Assistant](/integrations/my) on your installation,
@ -37,7 +46,7 @@ instead.
The `<HOME_ASSISTANT_URL>` must be the same as used during the configuration/
authentication process.
Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://homeassistant.local:8123/auth/external/callback`."
Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://homeassistant.local:8123/auth/external/callback`."
{% enddetails %}

1
source/_integrations/nexity.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

1
source/_integrations/opower.markdown
View File

@ -30,6 +30,7 @@ More than 175 utilities use Opower. Currently only the following utilities are s
- City of Austin Utilities
- Consolidated Edison (ConEd) and subsidiaries
- Orange & Rockland Utilities (ORU)
- Duquesne Light Company (DQE)
- Enmax Energy
- Evergy
- Exelon subsidiaries

1
source/_integrations/overkiz.markdown
View File

@ -25,6 +25,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_domain: overkiz
ha_dhcp: true
ha_zeroconf: true

2
source/_integrations/pi_hole.markdown
View File

@ -66,4 +66,4 @@ target:
## Switches
The integration creates a switch for the Pi-hole allowing you to toggle the Pi-hole on and off.
The integration creates a switch for the Pi-hole allowing you to toggle the Pi-hole on and off.

5
source/_integrations/proximity.markdown
View File

@ -11,6 +11,10 @@ ha_iot_class: Calculated
ha_integration_type: integration
ha_codeowners:
- '@mib1185'
ha_platforms:
- diagnostics
- sensor
ha_config_flow: true
---
The `proximity` integration allows you to monitor the proximity of devices or persons to a particular [zone](/integrations/zone/) and the direction of travel.
@ -73,4 +77,3 @@ This sensor shows the direction of travel of the nearest device or person to the
This comprehensive video tutorial explains how to utilize the Proximity integration to automatically adjust the heating in your home based on your presence, whether you're leaving or entering an area around your house.
<lite-youtube videoid="0ojMz1s3Y84" videotitle="Mastering Geofencing in Home Assistant with Proximity and Presence Detection: An Ultimate Guide" posterquality="maxresdefault"></lite-youtube>

1
source/_integrations/qingping.markdown
View File

@ -34,3 +34,4 @@ The Qingping integration will automatically discover devices once the [Bluetooth
- [Motion & Ambient Light Sensor](https://www.qingping.co/motion-light-sensor/overview) (CGPR1)
- [Temp RH M](https://www.qingping.co/temp-rh-monitor/overview#mi) (CGG1)
- [Temp RH Pro E](https://www.qingping.co/temp-rh-monitor-pro-e/overview) (CGF1W)
- [CO2 Temp RH](https://www.qingping.co/co2-temp-rh-monitor/overview) (GCP22C)

2
source/_integrations/recovery_mode.markdown
View File

@ -29,4 +29,4 @@ to re-try.
## Related topics
- [General troubleshooting](/docs/troubleshooting_general/)
- [General troubleshooting](/docs/troubleshooting_general/)

2
source/_integrations/renson.markdown
View File

@ -6,6 +6,7 @@ ha_category:
- Button
- Fan
- Number
- Switch
- Time
ha_release: 2023.7
ha_iot_class: Local Polling
@ -19,6 +20,7 @@ ha_platforms:
- fan
- number
- sensor
- switch
- time
ha_integration_type: integration
---

1
source/_integrations/rexel.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

1
source/_integrations/roomba.markdown
View File

@ -11,6 +11,7 @@ ha_codeowners:
- '@cyr-ius'
- '@shenxn'
- '@Xitee1'
- '@Orhideous'
ha_domain: roomba
ha_config_flow: true
ha_dhcp: true

20
source/_integrations/samsam.markdown Normal file
View File

@ -0,0 +1,20 @@
---
title: SamSam
description: Get the energy market prices from SamSam using the EnergyZero integration.
ha_category:
- Energy
ha_domain: samsam
ha_release: 2023.2
ha_integration_type: virtual
ha_supporting_domain: energyzero
ha_supporting_integration: EnergyZero
ha_codeowners:
- '@klaasnicolaas'
ha_config_flow: true
ha_platforms:
- diagnostics
- sensor
ha_iot_class: Cloud Polling
---
{% include integrations/supported_brand.md %}

1
source/_integrations/simu.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

1
source/_integrations/somfy.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

6
source/_integrations/systemmonitor.markdown
View File

@ -8,6 +8,8 @@ ha_iot_class: Local Push
ha_domain: systemmonitor
ha_config_flow: true
ha_platforms:
- binary_sensor
- diagnostics
- sensor
ha_integration_type: integration
ha_codeowners:
@ -55,9 +57,9 @@ memory usage, CPU usage, and running processes.
- Swap use
- Swap usage (percent)
### Add `process` sensor
## Add `process` binary sensor
The `process` sensor needs to be configured by the config entry options. Go to **{% my integrations title="Settings > Devices & Services" %}**, select the **System Monitor** integration and click **Configure** to select which `process` sensors should be created.
The `process` binary sensor needs to be configured by the config entry options. Go to **{% my integrations title="Settings > Devices & Services" %}**, select the **System Monitor** integration and click **Configure** to select which `process` binary sensors should be created.
## Disk usage

31
source/_integrations/tado.markdown
View File

@ -142,3 +142,34 @@ automation:
{{ (-(tado_temp - room_temp) + current_offset)|round(1) }}
```
{% endraw %}
### Service `tado.add_meter_reading`
You can use the service `tado.add_meter_reading` to add your meter readings to Tado Energy IQ. With Energy IQ, you can track your energy consumption and take control of your heating expenses.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------------------------------------------------- |
| `config_entry` | no | String, Config entry to add meter readings to. |
| `reading` | no | Integer, Reading in m³ or kWh without decimals. |
Examples:
{% raw %}
```yaml
# Example automation add meter readings on a daily basis.
automation:
# Trigger on specified time.
trigger:
- platform: time
at: "00:00:00"
# Add meter readings from `sensor.gas_consumption` to Tado.
# Retrieve your `config_entry` id by setting this automation up in UI mode.
# Notice that you may have to convert the reading to integer.
action:
- service: tado.add_meter_reading
data:
config_entry: ef2e84b3dfc0aee85ed44ac8e8038ccf
reading: "{{ states('sensor.gas_consumption')|int }}"
```
{% endraw %}

7
source/_integrations/technove.markdown
View File

@ -13,6 +13,7 @@ ha_codeowners:
ha_platforms:
- binary_sensor
- sensor
- switch
ha_integration_type: device
---
@ -44,3 +45,9 @@ The {% term integration %} adds the following sensors:
- Wi-Fi signal strength
- Wi-Fi network name
- Status
## Switch
The {% term integration %} adds the following switch:
- Auto-charge mode

5
source/_integrations/tessie.markdown
View File

@ -116,7 +116,10 @@ The integration will create device tracker entities for the vehicle's current lo
### Lock
The integration will create a lock entity for each vehicle and for the charge cable lock.
The integration will create lock entities to lock and unlock the vehicle, and to control:
- Charge cable
- Speed limit
### Media Player

1
source/_integrations/thermopro.markdown
View File

@ -26,6 +26,7 @@ Integrates [ThermoPro](https://buythermopro.com/) devices into Home Assistant.
- [TP393](https://buythermopro.com/product/tp393/)
- [TP960](https://buythermopro.com/product/tempspike/)
- [TP962](https://buythermopro.com/twin-tempspike/)
- [TP970](https://buythermopro.com/product/tempspike-plus-tp970/)
The ThermoPro integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional.

8
source/_integrations/tplink_tapo.markdown
View File

@ -1,6 +1,6 @@
---
title: Tapo
description: Connect and control your Tapo devices using the TP-Link integration
description: Connect and control your Tapo devices using the TP-Link Smart Home integration
ha_category:
- Hub
- Light
@ -10,22 +10,20 @@ ha_domain: tplink_tapo
ha_release: 0.89
ha_integration_type: virtual
ha_supporting_domain: tplink
ha_supporting_integration: tplink
ha_supporting_integration: TP-Link Smart Home
ha_codeowners:
- '@rytilahti'
- '@thegardenmonkey'
- '@bdraco'
- '@sdb9696'
ha_config_flow: true
ha_platforms:
- diagnostics
- light
- sensor
- switch
ha_iot_class: Local Polling
ha_config_flow: true
ha_dhcp: true
ha_quality_scale: platinum
ha_integration_type: integration
---
{% include integrations/supported_brand.md %}

3
source/_integrations/traccar_server.markdown
View File

@ -5,13 +5,14 @@ ha_release: 2024.2
ha_category:
- Car
- Presence detection
ha_iot_class: Local Polling
ha_iot_class: Local Push
ha_config_flow: true
ha_codeowners:
- '@ludeeus'
ha_domain: traccar_server
ha_platforms:
- device_tracker
- diagnostics
ha_integration_type: integration
---

13
source/_integrations/tuya.markdown
View File

@ -55,12 +55,15 @@ All Home Assistant platforms are supported by the Tuya integration, except the l
You need to have the Tuya Smart or Smart Life app installed, with an account created and
at least one device added to that account.
You will need your **User Code**. You can find this code in the Smart Life app or
Tuya Smart app in **Settings** > **Account and Security** screen, and enter the
code shown on the **User Code** field.
### Obtaining User Code for sign-in
Please note, that the user code is case sensitive, please be sure to enter it
exactly as shown in the app.
To sign-in, you will need to get your **User Code** from the Smart Life /
Tuya Smart app. You can find it by opening the app and:
1. On the tab bar, select **Me**.
2. Select the **⚙️ (gear)** icon in the top-right corner.
3. Tap **Account and Security**.
4. At the bottom, **User Code** will be shown; you need to when setting up this integration.
{% include integrations/config_flow.md %}

1
source/_integrations/ubiwizz.markdown
View File

@ -27,6 +27,7 @@ ha_codeowners:
- '@vlebourl'
- '@tetienne'
- '@nyroDev'
- '@tronix117'
ha_config_flow: true
ha_platforms:
- alarm_control_panel

36
source/_integrations/vallox.markdown
View File

@ -19,21 +19,41 @@ ha_codeowners:
- '@andre-richter'
- '@slovdahl'
- '@viiru-'
- '@yozik04'
ha_integration_type: integration
---
The **Vallox** {% term integration %} lets you control any Vallox ventilation unit that is supported by the [vallox_websocket_api](https://github.com/yozik04/vallox_websocket_api) (follow the link for a list of supported units).
The **fan** platform of this {% term integration %} allows you to turn on/off the complete unit via the toggle switch, control fan speed and select a ventilation profile.
The **sensor** platform exposes a number of relevant metrics like fan speed, various air temperatures, and humidity.
The **switch** platform allows locking heat recovery bypass.
The **number** platform allows to control supply air temperatures.
{% include integrations/config_flow.md %}
## Platforms
### Fan
The fan platform of this integration allows you to control the entire unit. You can turn the unit on/off using the toggle switch, adjust the fan speed, and select a ventilation profile.
### Sensor
The sensor platform allows you to monitor various metrics such as fan speeds, air temperatures, humidity, remaining filter life, cell state, and more.
### Binary sensor
The binary sensor platform allows you to monitor the status of the post heater.
### Switch
The switch platform allows you to lock the heat recovery bypass.
### Number
The number platform gives you control over the supply air temperatures.
### Date
The date platform allows you to set the filter change date.
## Profile switching
For convenient switching of ventilation profiles in the GUI, just click on the `Vallox` fan {% term entity %} to get a drop-down menu to select from. Alternatively, the service `fan/set_preset_mode` can be used.

24
source/_integrations/velux.markdown
View File

@ -5,9 +5,11 @@ ha_category:
- Cover
- Scene
ha_release: 0.49
ha_config_flow: true
ha_iot_class: Local Polling
ha_codeowners:
- '@Julius2342'
- '@DeerMaximum'
ha_domain: velux
ha_platforms:
- cover
@ -26,27 +28,7 @@ There is currently support for the following device types within Home Assistant:
- Light
- Scene
## Configuration
A `velux` section must be present in the `configuration.yaml` file and contain the following options as required:
```yaml
# Example configuration.yaml entry
velux:
host: IP_ADDRESS
password: VELUX_PASSWORD
```
{% configuration %}
host:
description: The IP address or hostname of the KLF 200 to use.
required: true
type: string
password:
description: The password of the KLF 200 interface. Note that this is the same as the Wi-Fi password (in the upper box on the back), *not* the password for the web login.
required: true
type: string
{% endconfiguration %}
{% include integrations/config_flow.md %}
## Services

2
source/_integrations/verisure.markdown
View File

@ -90,4 +90,4 @@ Some users have reported that this integration currently doesn't work in the fol
- France
- Ireland
- Italy
- Sweden
- Sweden

2
source/_integrations/vesync.markdown
View File

@ -62,6 +62,8 @@ This {% term integration %} supports devices controllable by the VeSync App. Th
- Core 300S: Smart True HEPA Air Purifier
- Core 400S: Smart True HEPA Air Purifier
- Core 600S: Smart True HEPA Air Purifier
- Vital 100S Smart True HEPA Air Purifier (LAP-V102S-WUS)
- Vital 200S Smart True HEPA Air Purifier (LAP-V201S-WUS)
- LEVOIT Smart Wifi Air Purifier (LV-PUR131S)
## Prerequisite

20
source/_integrations/weatherflow_cloud.markdown Normal file
View File

@ -0,0 +1,20 @@
---
title: WeatherFlow Cloud
description: Instructions on the Cloud based WeatherFlow integration
ha_release: 2024.3
ha_category:
- Environment
- Weather
ha_platforms:
- weather
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@jeeftor'
ha_domain: weatherflow_cloud
ha_integration_type: integration
---
The **WeatherFlow Cloud** integration provides access to cloud provided Weather Forecast of a user's Tempest Weather Stations. In order to access the station you will need to configure the integration with an [Api Key](https://weatherflow.github.io/Tempest/api/).
{% include integrations/config_flow.md %}

35
source/_integrations/webmin.markdown Normal file
View File

@ -0,0 +1,35 @@
---
title: Webmin
description: Instructions on how to set up Webmin with Home Assistant.
ha_category:
- System monitor
ha_release: 2024.3
ha_iot_class: Local Polling
ha_config_flow: true
ha_codeowners:
- '@autinerd'
ha_domain: webmin
ha_integration_type: device
ha_platforms:
- sensor
---
[Webmin](https://webmin.com) is a web-based interface for the system administration of Unix-like servers.
This {% term integration %} provides sensors for monitoring the CPU and memory usage of your server.
{% include integrations/config_flow.md %}
## Sensors
**All entities are disabled by default, you need to enable the entities that you wish to use.**
Following sensors will be added:
- Load (1m)
- Load (5m)
- Load (15m)
- Memory total
- Memory free
- Swap total
- Swap free

6
source/_integrations/whisper.markdown
View File

@ -13,10 +13,14 @@ ha_codeowners:
- '@synesthesiam'
ha_config_flow: true
ha_platforms:
- binary_sensor
- number
- select
- stt
- switch
- tts
- wake_word
ha_iot_class: Local Push
ha_zeroconf: true
---
{% include integrations/supported_brand.md %}

1
source/_integrations/wyoming.markdown
View File

@ -17,6 +17,7 @@ ha_platforms:
- stt
- switch
- tts
- wake_word
ha_config_flow: true
ha_zeroconf: true
---

39
source/_integrations/xiaomi_ble.markdown
View File

@ -20,42 +20,15 @@ ha_platforms:
ha_integration_type: integration
---
Integrates devices that implement the Xiaomi Mijia BLE MiBeacon protocol and other Xiaomi BLE devices that support passive collection. It listens to Bluetooth broadcasts that the device makes by itself, allowing us to track the latest sensor values without needing to wake it up from deep sleep to poll and conserving its battery power.
Integrates devices that implement the Xiaomi Mijia BLE MiBeacon protocol and the BLE protocols implemented in the MiScales and the MiFora plant sensor. The integration listens to Bluetooth broadcasts that the device makes by itself, allowing it to track the latest sensor values or events without waking the device up for polling. This method conserves battery lifetime.
The integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional.
The integration automatically discovers devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional. The entities are added after the values are first received. This means that entities might show up later if the corresponding values are broadcasted at a lower interval (for example, battery).
{% include integrations/config_flow.md %}
## Supported device classes
## Supported devices
It is possible that we detect your device because it uses the MiBeacon protocol but don't yet support any or all of its sensors. We currently actively test devices with the following sensor classes.
- Temperature
- Humidity
- Moisture
- Illumination
- Conductivity
- Formaldehyde
- Consumable
- Voltage
- Battery
It also supports the following classes of binary sensors:
- Door
- Light
- Moisture
- Motion
- Opening
- Smoke
- Toothbrush
And also supports the following events:
- Motion detected (MUE4094RT only)
- Button press
The entities are added after the values are first received. This means entities for values that are broadcasted at a lower interval (e.g., battery) might show up later.
From the devices that support the Xiaomi Mijia BLE MiBeacon protocol, currently locks are not implemented yet. This integration also does not support Xiaomi BLE Mesh devices.
## Encryption
@ -69,7 +42,9 @@ This key is called the bindkey or beaconkey.
There are a few ways to obtain a bindkey for your device:
- Extract the keys from Xiaomi Cloud using a [token extractor](https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor) tool.
- Set your own. The [Telink Flasher](https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html) allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). The new bind key will work with Home Assistant, but the Mi Home app will not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app.
- Set your own. The [Telink Flasher](https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html) by pvvx allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). This online flashing tool also allows you to upload alternative firmware, with some improvements compared to the stock firmware, like faster sensor updates. Note that the new bind key works with Home Assistant, but the Mi Home app does not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app.
- An alternative [Telink Flasher](https://atc1441.github.io/Temp_universal_mi_activate.html) by atc1441 also allows you to generate new bind keys, and supports even more Xiaomi devices compared to the Telink Flasher by pvvx.
- Yeelight Remote (YLYK01YL) and dimmers (YLKG07YL and YLKG08YL) can use V2/V3 MiBeacon encryption, although more recent devices seem to be supplied with V4/V5 encryption. For V2/V3 MiBeacon encryption, the bindkey can't be determined with the above methods. Instructions on how to get the bindkey for these devices can be found in the [BLE monitor FAQ](https://custom-components.github.io/ble_monitor/faq#how-to-get-the-mibeacon-v2v3-encryption-key).
## Devices

2
source/_integrations/zha.markdown
View File

@ -101,6 +101,7 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
- [ITead SONOFF Zigbee 3.0 USB Dongle Plus Model "ZBDongle-E" (EFR32MG21 variant)](https://itead.cc/product/zigbee-3-0-usb-dongle/)
- [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs-usb-adapter.html)/POPP ZB-Stick (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
- [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs-zigbee-shield.html) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
- [SMLIGHT SLZB-07](https://smlight.tech/product/slzb-07/) (EFR32MG21-based USB dongle)
- Texas Instruments based radios (via the [zigpy-znp](https://github.com/zigpy/zigpy-znp) library for zigpy)
- [CC2652P/CC2652R/CC2652RB USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
- [CC1352P/CC1352R USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
@ -206,6 +207,7 @@ Some devices can be auto-discovered, which can simplify the ZHA setup process. T
| [ConBee III](https://phoscon.de/conbee3) | USB | 0403:6015 |
| [Nortek HUSBZB-1](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) | USB | 10C4:8A2A |
| [slae.sh CC2652RB development stick](https://slae.sh/projects/cc2652/) | USB | 10C4:EA60 |
| [SMLIGHT SLZB-07](https://smlight.tech/product/slzb-07/) | USB | 10C4:EA60 |
| [ZigStar Stick (CC2652 + CH340B variant)](https://zig-star.com/projects/zigbee-stick-v4/) | USB | 1A86:7523 |
| [Tube’s EFR32 Pro Ethernet/Serial Coordinator](https://www.tubeszb.com/) | USB | 10C4:EA60 |
| [ZigStar Coordinators](https://zig-star.com/) | USB | 1A86:7523 |

20
source/_integrations/zondergas.markdown Normal file
View File

@ -0,0 +1,20 @@
---
title: ZonderGas
description: Connect and control your ZonderGas devices using the EnergyZero integration
ha_category:
- Energy
ha_domain: zondergas
ha_release: 2023.2
ha_integration_type: virtual
ha_supporting_domain: energyzero
ha_supporting_integration: EnergyZero
ha_codeowners:
- '@klaasnicolaas'
ha_config_flow: true
ha_platforms:
- diagnostics
- sensor
ha_iot_class: Cloud Polling
---
{% include integrations/supported_brand.md %}

556
source/_posts/2024-03-06-release-20243.markdown Normal file
View File

@ -0,0 +1,556 @@
---
layout: post
title: "Drag 'n Drop it like it's hot! 🎉"
description: "Drag 'n drop in your dashboards using a brand-new sections view and start up twice as fast! Run scripts with user input from your dashboards, a new energy graph for individual devices, new sentences for Assist, translate states in your templates, and more!"
date: 2024-03-06 00:00:00
date_formatted: "March 6, 2024"
author: Franck Nijhof
author_twitter: frenck
comments: true
categories:
- Release-Notes
- Core
og_image: /images/blog/2024-03/social.png
---
<a href='/integrations/#version/2024.3'><img src='/images/blog/2024-03/social.png' style='border: 0;box-shadow: none;'></a>
Home Assistant Core 2024.3! 🎉
Yes, you read the title right! I'm super stoked about this one. It has been
talked about for ages... I promise it is real:
**Drag 'n drop for dashboards is finally here! 🎉**
A first experimental version of the section dashboard that supports drag 'n drop.
A tremendous step forward and an even bigger milestone for Home Assistant!
But don't be blinded by these Dungeons 'n Dragons; there is a lot more!
New intents for Assist (I can finally tell my vacuum to start cleaning!), using
script inputs/fields from the dashboard, and a new energy graph for individual
devices. And that is just the tip of the iceberg!
Enjoy the release!
../Frenck
PS: A big thanks and shoutout to [@bramkragten] & [@balloob] for organizing
and running the beta and everyone who helped out making these release notes
happen during my absence this beta. 🥰
[@bramkragten]: https://github.com/bramkragten
[@balloob]: https://github.com/balloob
<!--more-->
- [A new experimental sections view](#a-new-experimental-sections-view)
- [Drag-and-drop rearrangement of cards and sections!](#drag-and-drop-rearrangement-of-cards-and-sections)
- [Running script from your dashboard with user input](#running-script-from-your-dashboard-with-user-input)
- [New energy graph for individual devices](#new-energy-graph-for-individual-devices)
- [New sentences for Assist](#new-sentences-for-assist)
- [Disabling the remote activation of the Home Assistant Remote UI](#disabling-the-remote-activation-of-the-home-assistant-remote-ui)
- [Translating states in your templates](#translating-states-in-your-templates)
- [Home Assistant boots twice as fast](#home-assistant-boots-twice-as-fast)
- [Other noteworthy changes](#other-noteworthy-changes)
- [New integrations](#new-integrations)
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
- [Need help? Join the community!](#need-help-join-the-community)
- [Backward-incompatible changes](#backward-incompatible-changes)
- [All changes](#all-changes)
Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=Jxup-fKFpfs)
6 March 2024, at 20:00 GMT / 12:00 PST / 21:00 CET!
<lite-youtube videoid="Jxup-fKFpfs" videotitle="Home Assistant 2024.3 Release Party"></lite-youtube>
## A new experimental sections view
Our dashboard currently comes with three view layout types:
[Panel](/dashboards/panel/), [Sidebar](/dashboards/sidebar/),
and [Masonry](/dashboards/masonry/). Since the past year, we have been working
hard to research and ideate on how to make dashboards easier to customize
and use, and we learned that our current layouts are not the best for such
purposes. Drag-and-drop rearrangement of cards cannot work well with the
Masonry layout.
We came up with a few solutions, and the first thing we would like to share
with you is a new view layout type called "Sections".
Home Assistant dashboards are robust and packed with information. Users will
often place dozens of cards for all sorts of buttons, switches, graphs,
indicators, and more.
<p class='img'>
<img width="66%" src="/images/blog/2024-03-dashboard-chapter-1/sections-section-example.png" alt="Example of a dashboard section"/>
Example of a dashboard section
</p>
By grouping cards into “sections”, you can reduce the number of items you
need to scan through when you are looking for a certain card, as you'll be
able to look for the relevant group title first and then reduce the scope to
scan that particular group for the information.
By packing cards in a section into a grid with a fixed number of columns,
the relative positions of the cards within a section are not affected by
changes in screen sizes, and so the spatial memory of the cards is retained,
leading to a faster and less cumbersome experience.
<p class='img'>
<img src="/images/blog/2024-03-dashboard-chapter-1/sections-example-dashboard.png" alt="A fully populated dashboard in Sections view layout"/>
A fully populated dashboard in the Sections view layout
</p>
Cards in the new sections view type are all aligned in a tidy grid to ensure
consistency and predictability of their positions when the screen size changes.
We currently have three cards reworked to fit the grid:
[Tile](/dashboards/tile/), [Sensor](/dashboards/sensor/),
and [Button](/dashboards/button/) cards. These cards will occupy the right
amount of space in the grid, while other cards will occupy the full width
of a section by default at the moment. Moreover, we have tweaked our
"Add Cards" dialogs to recommend Tile cards by default when the sections
view type is in use.
<div class='note warning'>
The new Sections view is experimental! Please do not build your daily dashboard on top of it yet! We are releasing this early so that we can collect your feedback.
</div>
To get started with the new Sections view type, create a new view on your
dashboard and select **Sections (experimental)** as the view type.
We currently do not have the option to migrate your current dashboard over yet.
For more information, check out our blog post about our new
series [A Home-Approved Dashboard: Chapter 1](/blog/2024/03/04/dashboard-chapter-1/).
Amazing work! Thanks [Paul](https://github.com/piitaya),
[Matthias](https://github.com/matthiasdebaat),
and [Madelena](https://github.com/madelena)!
## Drag-and-drop rearrangement of cards and sections!
Wow! At long last!! The stars have aligned, and our experimental drag-and-drop
feature for dashboards is finally here! 🥲
With the new sections view type, we can finally implement a way to arrange
cards and sections that is intuitive with drag-and-drop gestures and predictable
with how the cards will rearrange while creating a dashboard that is easy to
navigate and remember. You will no longer need to pray and guess where the cards
will land when they change their order!
### How to drag and drop <!-- omit from toc -->
While your dashboard is in edit mode:
<p class='img'>
<img src="/images/blog/2024-03-dashboard-chapter-1/drag-and-drop-sections.gif" alt="Rearranging sections with drag-and-drop"/>
Rearranging sections with drag-and-drop
</p>
- To rearrange sections, tap and hold the
<img height="28px" src="/images/blog/2024-03-dashboard-chapter-1/mdi-edit.png" alt="Edit icon"/>
**Move** handle and then move your cursor or finger towards your desired
location. Other sections will move out of the way for where the selected
section will drop.
<p class='img'>
<img src="/images/blog/2024-03-dashboard-chapter-1/drag-and-drop-cards.gif" alt="Rearranging cards with drag-and-drop"/>
Rearranging sections with drag-and-drop
</p>
- To rearrange cards, tap and hold anywhere on the card and then move your
cursor or finger towards your desired location.
Don’t you love it when instructions are so short? Simplicity FTW! 🦄
Thanks again [Paul](https://github.com/piitaya),
[Matthias](https://github.com/matthiasdebaat),
and [Madelena](https://github.com/madelena)!
## Running script from your dashboard with user input
{% term Scripts %} in Home Assistant allow you to capture a sequence of actions
and choices in a reusable way. Scripts are extra powerful because they can
have input fields, allowing you to send in data for when the script runs.
Script fields can be defined in the script editor and show up when you call the
script in your automation. In this release, script fields will be available
in the more info dialog when tapping a script on a dashboard.
This allows you to provide the input fields and run the script, unlocking a
whole new dimension of possibilities.
<lite-youtube videoid="Ulkl1L8F1L4" videotitle="Calling scripts from the dashboard"></lite-youtube>
To accompany this new functionality, we’ve created two blueprints to help you
get started with using scripts on your dashboard:
**Announce message**: This blueprint allows you to create an announce script for
your dashboard pre-configured to a specific media player and text-to-speech
engine. When activated, it will ask the user for the message to play.
{% my blueprint_import badge blueprint_url="https://community.home-assistant.io/t/announce-text-to-speech-on-media-player/699186" %}
**Add to to-do list**: This blueprint allows you to create a script to add an
item to a to-do list pre-configured to a specific to-do list. When activated,
it will ask the user for the item to add.
{% my blueprint_import badge blueprint_url="https://community.home-assistant.io/t/add-to-do-item/699193" %}
## New energy graph for individual devices
Digging into your energy data is a very interesting way to find ways to reduce
your household's energy usage and environmental footprint. 🌱
One of the missing bricks was the ability to see the energy consumption
of individual devices over time. Thanks to [@karwosts], we have a
brand new graph on the energy dashboard that provides this insight!
Using this new graph, you can now easily spot which devices are responsible
for which part of your energy usage over time.
<img class="no-shadow" src='/images/blog/2024-03/individual-devices-usage.png' alt='Screenshot showing the new energy stacked bar graph of individual devices over time.'>
For example, in the above picture, it is very easy to see that the dishwasher
was responsible for the morning spike and the oven for the spike in the evening.
[@karwosts]: https://github.com/karwosts
## New sentences for Assist
[Assist](/voice_control/), our private voice assistant, learned a few tricks this month.
Support for valves has been added. You can now ask Assist to adjust the position
of a valve, or just open or close a valve completely.
Also, cover support has been extended to support the control of the position of
your devices. Currently, most languages only support a single use-case as a
starting point. Setting the position of a single device by targeting its
name:
> Set the curtain position to 80%
We are working on extending the use-case coverage to set the position
of multiple devices or complete areas, similar to what is possible with
the open and close sentences.
<img class="no-shadow" src='/images/blog/2024-03/new-assist-commands.png' alt='Screenshot showing a few of the new Assist commands.'>
The next new trick could be considered a bug fix: Until today it was not
possible to start or stop a vacuum cleaner by voice; Now it can! Assist knows
how to start a vacuum and return it to its base. Here are some example
sentences, in case you have a vacuum cleaner named Dusty:
> Start Dusty
> Return Dusty to base
The biggest set of changes is for media players. Assist can now pause playback,
resume playback, skip to the next media, and set the volume of media players!
Be aware that currently, these sentences are limited to targeting a single
device by its name, for example:
> Skip to the next song on the TV
We are actively working on extending the logic of these new intents to allow
you to target areas and only affect the desired media player(s).
## Disabling the remote activation of the Home Assistant Remote UI
If you are using [Home Assistant Cloud](https://nabucasa.com), you can access
your Home Assistant instance remotely using the Remote UI feature.
Suppose this feature is, for some reason, disabled, and you are currently not
at home. In that case, you can enable the Remote UI feature remotely by
logging into your [Nabu Casa account](https://account.nabucasa.com/) and
request your Home Assistant instance to turn it on.
Feedback from the community has shown that this feature is not always desired,
and this release adds a new option to disable the remote activation of the
Remote UI feature. Once disabled, the Remote UI feature can only be enabled
locally from your Home Assistant instance.
<img class="no-shadow" src='/images/blog/2024-03/home-assistant-cloud-disable-remove-activation.png' alt='Screenshot showing the new advanced option that allows disabling remote activation of the Home Assistant remote UI.'>
## Translating states in your templates
Are you using {% term templates %} to send notifications in automations? If so,
[@PiotrMachowski] might just have added something new you need!
A new template method, `state_translated`, to translate entity states directly
from your templates! Consider this template example:
{% raw %}
```yaml
# Untranslated
{{ states("binary_sensor.movement_backyard") }} # Shows: on
{{ states("sun.sun") }} # Shows: below_horizon
```
{% endraw %}
The above example shows the raw state of two entities. However, with the
new `state_translated` method, you can get the state in a human-readable form:
{% raw %}
```yaml
# Translated
{{ state_translated("binary_sensor.movement_backyard") }} # Shows: Detected
{{ state_translated("sun.sun") }} # Shows: Below horizon
```
{% endraw %}
Even better, it uses the default language of your Home Assistant instance. So,
if you use Home Assistant in a different language, the translated state will
be in that language.
[@PiotrMachowski]: https://github.com/PiotrMachowski
## Home Assistant boots twice as fast
In case you didn't know, every release [@bdraco] improves the performance
on some aspect of Home Assistant. He has been on it for a long time and keeps
pushing to improve it.
As a matter of fact, it has become so regular that we don't always highlight
his enormous efforts toward this goal in our release notes. _Sorry! 🙏_
However, in this release, his efforts are so noticeable that we wanted to
call it out: **Home Assistant now boots on average twice as fast!** 🚀
That is a huge improvement [@bdraco]!! Thank you for your continuous work on
making Home Assistant faster and faster! ❤️
[@bdraco]: https://github.com/bdraco
## Other noteworthy changes
There are many more improvements in this release; here are some of the other
noteworthy changes this release:
- The [climate entity] now has a toggle service (`climate.toggle`).
Thanks [@arturpragacz]!
- [Matter] lights now support transitions, nice! Thanks, [@marcelveldt]!
- We heard you like downloading CSVs! So, we added the ability to download
the energy dashboard data to a CSV file now as well! Thanks [@karwosts]!
- After feedback and reports on the automatic Zigbee device firmware updates
introduced in a previous release, this release brings a stricter and
more robust update system to [ZHA]. Thanks [@dmulcahey] & [@puddly]!
- The [Tessie] integration now provides charging and range sensors.
Thanks [@Bre77]!
- [myUplink] devices can now be updated directly from Home Assistant.
Awesome [@astrandb]!
- [DuneHD] media players now support browsing media files and playing them.
Thanks [@iliessens]!
- The [Bring!] now brings in a new "recently" list. Nice [@miaucl]!
- [@lellky] added setpoints as number entities for fans to the
[Flexit Nordic (BACnet)] integration, thanks!
- The dialog to adjust long-term statistics now has automated outlier detection!
That is a very smart and helpful addition. Thanks [@karwosts]!
[@arturpragacz]: https://github.com/arturpragacz
[@astrandb]: https://github.com/astrandb
[@Bre77]: https://github.com/Bre77
[@dmulcahey]: https://github.com/dmulcahey
[@iliessens]: https://github.com/iliessens
[@karwosts]: https://github.com/karwosts
[@lellky]: https://github.com/lellky
[@marcelveldt]: https://github.com/marcelveldt
[@miaucl]: https://github.com/miaucl
[@puddly]: https:///github.com/puddly
[Bring!]: /integrations/bring
[climate entity]: /integrations/climate
[DuneHD]: /integrations/dunehd
[Flexit Nordic (BACnet)]: /integrations/flexit_bacnet
[Matter]: /integrations/matter
[myUplink]: /integrations/myuplink
[Tessie]: /integrations/tessie
[ZHA]: /integrations/zha
## New integrations
We welcome the following new integrations in this release:
- **[Aprilaire]**, added by [@chamberlain2007]<br />
Monitor and control your Aprilaire thermostats.
- **[Husqvarna Automower]**, added by [@Thomas55555]<br />
The Husqvarna Automower integration allows you to integrate and control
your lawn mower straight from Home Assistant.
- **[microBees]**, added by [@marcolettieri]<br />
Control your microBees devices, such as plugs and wall switches.
- **[WeatherFlow Cloud]**, added by [@jeeftor]<br />
The WeatherFlow Cloud is an alternative to the existing [local WeatherFlow]
integration and pulls in data from your Tempest Weather Station.
- **[Webmin]**, added by [@autinerd]<br />
Monitor the CPU and memory usage of your Webmin-managed server.
[@autinerd]: https://github.com/autinerd
[@chamberlain2007]: https://github.com/chamberlain2007
[@jeeftor]: https://github.com/jeeftor
[@marcolettieri]: https://github.com/marcolettieri
[@Thomas55555]: https://github.com/Thomas55555
[Aprilaire]: /integrations/aprilaire
[Husqvarna Automower]: /integrations/husqvarna_automower
[local WeatherFlow]: /integrations/weatherflow
[microBees]: /integrations/microbees
[WeatherFlow Cloud]: /integrations/weatherflow_cloud
[Webmin]: /integrations/webmin
This release also has new virtual integrations. Virtual integrations are stubs
that are handled by other (existing) integrations to help with findability.
The following virtual integrations have been added:
- **[Acomax]**, provided by [Motionblinds]
- **[Duquesne Light]**, provided by [Opower]
- **[Krispol]**, provided by [Motionblinds]
- **[Madeco]**, provided by [Motionblinds]
- **[SamSam]**, provided by [EnergyZero]
- **[ZonderGas]**, provided by [EnergyZero]
[Acomax]: /integrations/acomax
[Duquesne Light]: /integrations/duquesne_light
[EnergyZero]: /integrations/energyzero
[Krispol]: /integrations/krispol
[Madeco]: /integrations/madeco
[Motionblinds]: /integrations/motion_blinds
[Opower]: /integrations/opower
[SamSam]: /integrations/samsam
[ZonderGas]: /integrations/zondergas
## Integrations now available to set up from the UI
The following integration us now available via the Home Assistant UI:
- **[Velux]**, done by [@DeerMaximum]
[@DeerMaximum]: https://github.com/DeerMaximum
[Velux]: /integrations/velux
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing
to help each other out. So, join us!
Our very active [Discord chat server](/join-chat) is an excellent place to be
at, and don't forget to join our amazing [forums](https://community.home-assistant.io/).
Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues),
to get it fixed! Or, check [our help page](/help) for guidance for more
places you can go.
Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter)
to get the latest news about features, things happening in our community and
other news about building an Open Home; straight into your inbox.
## Backward-incompatible changes
{% details "AEMET" %}
The daily data for the current day wasn't available after midday, and
now it will be. Automations and scripts relying on `day[0]` for checking
the next-day forecast will have to be adjusted to use `day[1]` instead.
([@Noltari] - [#107795]) ([documentation](/integrations/aemet))
[@Noltari]: https://github.com/Noltari
[#107795]: https://github.com/home-assistant/core/pull/107795
{% enddetails %}
{% details "JuiceNet" %}
The JuiceNet integration has been removed.
Enel X has migrated from JuiceNet to JuicePass, rendering the JuiceNet
integration useless. Background and alternative solutions to the juicenet
integration can be found in the related
[issue](https://github.com/home-assistant/core/issues/86588).
([@emontnemery] - [#111477])
[#111477]: https://github.com/home-assistant/core/pull/111477
{% enddetails %}
{% details "Met.no" %}
The met.no integration previously created two entities for each configured
location: one provided daily weather forecasts,
and one provided hourly forecasts.
The met.no integration now only creates a single entity that provides
both daily and hourly weather forecasts.
([@emontnemery] - [#97023]) ([documentation](/integrations/met))
[@emontnemery]: https://github.com/emontnemery
[#97023]: https://github.com/home-assistant/core/pull/97023
{% enddetails %}
{% details "MQTT" %}
Aux heat, deprecated in Home Assistant Core 2023.9, is now removed from
the MQTT climate.
([@jbouwh] - [#109513]) ([documentation](/integrations/mqtt))
[@jbouwh]: https://github.com/jbouwh
[#109513]: https://github.com/home-assistant/core/pull/109513
{% enddetails %}
{% details "Z-Wave" %}
For Z-Wave `climate` entities, the behavior of the `climate.turn_on` service
has changed. Previously, the service would act in the following order depending
on whether the corresponding conditions were met:
1. If the entity supported the `off` mode and exactly one additional mode,
`climate.turn_on` would set the mode to the additional mode.
2. If conditions for 1 were not met and at least one of the following modes were
available, the service would set the mode to the first mode it found
in the specified order: `heat_cool`, `heat`, `cool`.
3. If conditions for 1 and 2 were not met, the service would silently do nothing.
Now, the service follows the following behavior in order:
1. If the entity supports the `resume` thermostat mode, it will be used to
restore the last mode you used before the entity was turned off.
2. If the condition for 1 isn't met and the entity was turned off in
Home Assistant, and Home Assistant wasn't restarted, Home Assistant
remembers the last "on" mode and will set it to that mode. Home Assistant
will be unable to set the entity to the previous mode if Home Assistant
starts with the entity already in `off` mode since the integration will
not know what the previous mode was.
3. If conditions for 1 and 2 are not met and at least one of the following
modes is available, the service sets the mode to the first mode it finds
in the specified order: `heat_cool`, `heat`, `cool`
(no change to condition 2 above).
4. If conditions for 1, 2, and 3 are not met, the mode will be set to the first
supported mode it finds (like `dry` or `fan_only`).
([@raman325] - [#109187]) ([documentation](/integrations/zwave_js))
[@raman325]: https://github.com/raman325
[#109187]: https://github.com/home-assistant/core/pull/109187
{% 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:
- [Altering config entries](https://developers.home-assistant.io/blog/2024/02/12/async_update_entry/)
- [Deprecate use of @bind_hass and hass.components](https://developers.home-assistant.io/blog/2024/02/27/deprecate-bind-hass-and-hass-components)
- [Introducing device name translations](https://developers.home-assistant.io/blog/2024/02/28/device-name-translations)
- [It is now required for lights to set color mode](https://developers.home-assistant.io/blog/2024/02/12/light-color-mode-mandatory/)
- [New Climate entity toggle method](https://developers.home-assistant.io/blog/2024/02/25/Climate-toggle-service)
- [New single instance only manifest option](https://developers.home-assistant.io/blog/2024/02/26/single-instance-only-manifest-option)
- [Support for platform translations in separate files will be removed](https://developers.home-assistant.io/blog/2024/03/05/platform_entity_translations_deprecation)
[devblog]: https://developers.home-assistant.io/blog/
## All changes
Of course, there is a lot more in this release. You can find a list of
all changes made here: [Full changelog for Home Assistant Core 2024.3](/changelogs/core-2024.3)

7
source/_redirects
View File

@ -208,7 +208,6 @@ layout: null
/components/image_processing.* /integrations/:splat
/components/light.* /integrations/:splat
/components/lock.* /integrations/:splat
/components/mailbox.* /integrations/:splat
/components/media_player.* /integrations/:splat
/components/notify.* /integrations/:splat
/components/remote.* /integrations/:splat
@ -479,9 +478,12 @@ layout: null
/integrations/alarmdotcom /more-info/removed-integration 301
/integrations/almond /more-info/removed-integration 301
/integrations/ambee /more-info/removed-integration 301
/integrations/ambiclimate /more-info/removed-integration 301
/integrations/apns /more-info/removed-integration 301
/integrations/arlo /more-info/removed-integration 301
/integrations/arduino /more-info/removed-integration 301
/integrations/asterisk_cdr /more-info/removed-integration 301
/integrations/asterisk_mbox /more-info/removed-integration 301
/integrations/bbb_gpio /more-info/removed-integration 301
/integrations/bh1750 /more-info/removed-integration 301
/integrations/binary_sensor.mychevy /more-info/removed-integration 301
@ -527,16 +529,19 @@ layout: null
/integrations/hydroquebec /more-info/removed-integration 301
/integrations/ialarm_xr /more-info/removed-integration 301
/integrations/iota /more-info/removed-integration 301
/integrations/juicenet /more-info/removed-integration 301
/integrations/life360 /more-info/removed-integration 301
/integrations/lifx_legacy /more-info/removed-integration 301
/integrations/linksys_ap /more-info/removed-integration 301
/integrations/linky /more-info/removed-integration 301
/integrations/liveboxplaytv /more-info/removed-integration 301
/integrations/lockitron /more-info/removed-integration 301
/integrations/logi_circle /more-info/removed-integration 301
/integrations/loop_energy /more-info/removed-integration 301
/integrations/loopenergy /more-info/removed-integration 301
/integrations/lyft /more-info/removed-integration 301
/integrations/magicseaweed /more-info/removed-integration 301
/integrations/mailbox /more-info/removed-integration 301
/integrations/mazda /more-info/removed-integration 301
/integrations/mcp23017 /more-info/removed-integration 301
/integrations/mhz19 /more-info/removed-integration 301

2170
source/changelogs/core-2024.3.markdown Normal file
View File

File diff suppressed because it is too large Load Diff

36
source/dashboards/views.markdown
View File

@ -3,17 +3,30 @@ title: "Views"
description: "A view is a tab inside a dashboard."
---
A View is a tab inside a dashboard.
To display cards on the UI you have to define them in views.
A view is a tab inside a dashboard. Views control the layout.
You can add a view to your user interface, by clicking the menu (three dots at the top right of the screen) and then **Edit Dashboard**.
Click the `+` button in the top menu bar.
<p class="img">
<img src="/images/dashboards/views.png" alt="Views toolbar">
Use titles and icons to describe the content of views.
<p class='img'>
<img src='/images/dashboards/layout-types.png' alt='The three basic view layouts: Panel, sidebar, and masonry'>
The three basic view layouts: panel, sidebar, and masonry
</p>
There are four different view types:
- **Panel**: Displays one card in full width. For example a map or an image.
- **Sidebar**: Arranges cards in 2 columns, a wide one and a smaller one on the right.
- **Masonry (default)**: Arranges cards in columns based on their card size.
- **Sections (experimental)**: Arranges cards in a grid system and lets you group them in sections.
## Adding a view to a dashboard
1. To add a view to your user interface, in the top right corner, select the pencil icon.
2. Then, select the `+` button in the top menu bar.
<p class="img">
<img src="/images/dashboards/views.png" alt="Views toolbar">
Use titles and icons to describe the content of views.
</p>
## Path
You can link to one view from a card in another view when using cards that support navigation (`navigation_path`). The string supplied here will be appended to the string `/lovelace/` to create the path to the view. Do not use special characters in paths. Do not begin a path with a number. This will cause the parser to read your path as a view index.
@ -235,3 +248,10 @@ Subview configuration:
entities:
- sensor.today_avg_price
```
## Related topics
- [Masonry view](/dashboards/masonry/)
- [Panel view](/dashboards/panel/)
- [Sidebar view](/dashboards/sidebar/)
- [Sections view](/dashboards/sections/)

BIN
source/images/assist/assist-assistants-page.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 48 KiB

After

Width:  |  Height:  |  Size: 50 KiB

BIN
source/images/assist/assistants_ha_cloud.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 23 KiB

After

Width:  |  Height:  |  Size: 22 KiB

BIN
source/images/assist/esp32-atom_silence_detection_01.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 25 KiB

After

Width:  |  Height:  |  Size: 37 KiB

BIN
source/images/assist/wake_word_disable_on_atom_echo.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 18 KiB

BIN
source/images/assist/wake_word_select_assistant.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 25 KiB

After

Width:  |  Height:  |  Size: 36 KiB

BIN
source/images/blog/2024-03/home-assistant-cloud-disable-remove-activation.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 283 KiB

BIN
source/images/blog/2024-03/individual-devices-usage.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 227 KiB

BIN
source/images/blog/2024-03/new-assist-commands.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 50 KiB

BIN
source/images/blog/2024-03/social.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 208 KiB

BIN
source/images/dashboards/energy/devices-detail-graph.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 47 KiB

Some files were not shown because too many files have changed in this diff Show More