mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-12-10 00:30:02 -06:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
f4d743a3cd
18
CODEOWNERS
18
CODEOWNERS
@ -20,6 +20,7 @@ source/_integrations/acaia.markdown @zweckj
|
||||
source/_integrations/accuweather.markdown @bieniu
|
||||
source/_integrations/acmeda.markdown @atmurray
|
||||
source/_integrations/acomax.markdown @starkillerOG
|
||||
source/_integrations/actron_air.markdown @kclif9 @JagadishDhanamjayam
|
||||
source/_integrations/adax.markdown @danielhiversen @lazytarget
|
||||
source/_integrations/adguard.markdown @frenck
|
||||
source/_integrations/ads.markdown @mrpasztoradam
|
||||
@ -290,7 +291,9 @@ source/_integrations/file.markdown @fabaff
|
||||
source/_integrations/file_upload.markdown @home-assistant/core
|
||||
source/_integrations/filesize.markdown @gjohansson-ST
|
||||
source/_integrations/filter.markdown @dgomes
|
||||
source/_integrations/fing.markdown @Lorenzo-Gasparini
|
||||
source/_integrations/fire_tv.markdown @JeffLIrion @ollo69
|
||||
source/_integrations/firefly_iii.markdown @erwindouna
|
||||
source/_integrations/fireservicerota.markdown @cyberjunky
|
||||
source/_integrations/firmata.markdown @DaAwesomeP
|
||||
source/_integrations/fitbit.markdown @allenporter
|
||||
@ -357,6 +360,7 @@ source/_integrations/gpsd.markdown @fabaff @jrieger
|
||||
source/_integrations/gree.markdown @cmroche
|
||||
source/_integrations/greeneye_monitor.markdown @jkeljo
|
||||
source/_integrations/group.markdown @home-assistant/core
|
||||
source/_integrations/growatt_server.markdown @johanzander
|
||||
source/_integrations/guardian.markdown @bachya
|
||||
source/_integrations/habitica.markdown @tr4nt0r
|
||||
source/_integrations/hardware.markdown @home-assistant/core
|
||||
@ -427,6 +431,7 @@ source/_integrations/immich.markdown @mib1185
|
||||
source/_integrations/improv_ble.markdown @emontnemery
|
||||
source/_integrations/incomfort.markdown @jbouwh
|
||||
source/_integrations/indianamichiganpower.markdown @tronikos
|
||||
source/_integrations/inels.markdown @epdevlab
|
||||
source/_integrations/influxdb.markdown @mdegat01
|
||||
source/_integrations/inkbird.markdown @bdraco
|
||||
source/_integrations/input_boolean.markdown @home-assistant/core
|
||||
@ -440,7 +445,7 @@ source/_integrations/insteon.markdown @teharris1
|
||||
source/_integrations/integration.markdown @dgomes
|
||||
source/_integrations/intellifire.markdown @jeeftor
|
||||
source/_integrations/intesishome.markdown @jnimmo
|
||||
source/_integrations/iometer.markdown @MaestroOnICe
|
||||
source/_integrations/iometer.markdown @jukrebs
|
||||
source/_integrations/ios.markdown @robbiet480
|
||||
source/_integrations/iotawatt.markdown @gtdiehl @jyavenard
|
||||
source/_integrations/iotty.markdown @shapournemati-iotty
|
||||
@ -481,6 +486,7 @@ source/_integrations/knocki.markdown @joostlek @jgatto1 @JakeBosh
|
||||
source/_integrations/knx.markdown @Julius2342 @farmio @marvin-w
|
||||
source/_integrations/kodi.markdown @OnFreund
|
||||
source/_integrations/konnected.markdown @heythisisnate
|
||||
source/_integrations/konnected_esphome.markdown @jesserockz @kbx81 @bdraco
|
||||
source/_integrations/kostal_plenticore.markdown @stegm
|
||||
source/_integrations/kraken.markdown @eifinger
|
||||
source/_integrations/krispol.markdown @starkillerOG
|
||||
@ -526,6 +532,7 @@ source/_integrations/lookin.markdown @ANMalko @bdraco
|
||||
source/_integrations/loqed.markdown @mikewoudenberg
|
||||
source/_integrations/luci.markdown @mzdrale
|
||||
source/_integrations/luftdaten.markdown @fabaff @frenck
|
||||
source/_integrations/lunatone.markdown @MoonDevLT
|
||||
source/_integrations/lupusec.markdown @majuss @suaveolent
|
||||
source/_integrations/lutron.markdown @cdheiser @wilburCForce
|
||||
source/_integrations/lutron_caseta.markdown @swails @danaues @eclair4151
|
||||
@ -554,6 +561,7 @@ source/_integrations/melnor.markdown @vanstinator
|
||||
source/_integrations/met.markdown @danielhiversen
|
||||
source/_integrations/met_eireann.markdown @DylanGore
|
||||
source/_integrations/meteo_france.markdown @hacf-fr @oncleben31 @Quentame
|
||||
source/_integrations/meteo_lt.markdown @xE1H
|
||||
source/_integrations/meteoalarm.markdown @rolfberkenbosch
|
||||
source/_integrations/meteoclimatic.markdown @adrianmo
|
||||
source/_integrations/metoffice.markdown @MrHarcombe @avee87
|
||||
@ -617,6 +625,7 @@ source/_integrations/nightscout.markdown @marciogranzotto
|
||||
source/_integrations/niko_home_control.markdown @VandeurenGlenn
|
||||
source/_integrations/nilu.markdown @hfurubotten
|
||||
source/_integrations/nina.markdown @DeerMaximum
|
||||
source/_integrations/nintendo_parental_controls.markdown @pantherale0
|
||||
source/_integrations/nissan_leaf.markdown @filcole
|
||||
source/_integrations/noaa_tides.markdown @jdelaney72
|
||||
source/_integrations/nobo_hub.markdown @echoromeo @oyvindwe
|
||||
@ -656,6 +665,7 @@ source/_integrations/openerz.markdown @misialq
|
||||
source/_integrations/openexchangerates.markdown @MartinHjelmare
|
||||
source/_integrations/opengarage.markdown @danielhiversen
|
||||
source/_integrations/openhome.markdown @bazwilliams
|
||||
source/_integrations/openrgb.markdown @felipecrs
|
||||
source/_integrations/opensky.markdown @joostlek
|
||||
source/_integrations/opentherm_gw.markdown @mvn23
|
||||
source/_integrations/openuv.markdown @bachya
|
||||
@ -696,7 +706,6 @@ source/_integrations/plaato.markdown @JohNan
|
||||
source/_integrations/playstation_network.markdown @jackjpowell @tr4nt0r
|
||||
source/_integrations/plex.markdown @jjlawren
|
||||
source/_integrations/plugwise.markdown @CoMPaTech @bouwew
|
||||
source/_integrations/plum_lightpad.markdown @ColinHarrington @prystupa
|
||||
source/_integrations/point.markdown @fredrike
|
||||
source/_integrations/pooldose.markdown @lmaertin
|
||||
source/_integrations/poolsense.markdown @haemishkyd
|
||||
@ -819,7 +828,7 @@ source/_integrations/seven_segments.markdown @fabaff
|
||||
source/_integrations/seventeentrack.markdown @shaiu
|
||||
source/_integrations/sfr_box.markdown @epenet
|
||||
source/_integrations/sftp_storage.markdown @maretodoric
|
||||
source/_integrations/sharkiq.markdown @JeffResc @funkybunch
|
||||
source/_integrations/sharkiq.markdown @JeffResc @funkybunch @TheOneOgre
|
||||
source/_integrations/shell_command.markdown @home-assistant/core
|
||||
source/_integrations/shelly.markdown @bieniu @thecode @chemelli74 @bdraco
|
||||
source/_integrations/shodan.markdown @fabaff
|
||||
@ -861,7 +870,7 @@ source/_integrations/snapcast.markdown @luar123
|
||||
source/_integrations/snmp.markdown @nmaggioni
|
||||
source/_integrations/snoo.markdown @Lash-L
|
||||
source/_integrations/snooz.markdown @AustinBrunkhorst
|
||||
source/_integrations/solaredge.markdown @frenck @bdraco
|
||||
source/_integrations/solaredge.markdown @frenck @bdraco @tronikos
|
||||
source/_integrations/solaredge_local.markdown @drobtravels @scheric
|
||||
source/_integrations/solarlog.markdown @Ernst79 @dontinelli
|
||||
source/_integrations/solax.markdown @squishykid @Darsstar
|
||||
@ -890,6 +899,7 @@ source/_integrations/stt.markdown @home-assistant/core
|
||||
source/_integrations/subaru.markdown @G-Two
|
||||
source/_integrations/suez_water.markdown @ooii @jb101010-2
|
||||
source/_integrations/sun.markdown @home-assistant/core
|
||||
source/_integrations/sunricher_dali_center.markdown @niracler
|
||||
source/_integrations/supla.markdown @mwegrzynek
|
||||
source/_integrations/surepetcare.markdown @benleb @danielhiversen
|
||||
source/_integrations/swepco.markdown @tronikos
|
||||
|
||||
2
Gemfile
2
Gemfile
@ -11,7 +11,7 @@ group :development do
|
||||
# > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
|
||||
gem 'sassc', '2.1.0'
|
||||
gem 'sass-embedded', '1.93.2'
|
||||
gem 'rubocop', '1.81.6'
|
||||
gem 'rubocop', '1.81.7'
|
||||
gem 'ruby-lsp', '0.26.2'
|
||||
gem 'rackup', '2.2.1'
|
||||
end
|
||||
|
||||
@ -99,7 +99,7 @@ GEM
|
||||
prism (1.6.0)
|
||||
public_suffix (6.0.2)
|
||||
racc (1.8.1)
|
||||
rack (3.2.3)
|
||||
rack (3.2.4)
|
||||
rack-protection (4.2.1)
|
||||
base64 (>= 0.1.0)
|
||||
logger (>= 1.6.0)
|
||||
@ -119,7 +119,7 @@ GEM
|
||||
regexp_parser (2.11.3)
|
||||
rexml (3.4.4)
|
||||
rouge (4.6.1)
|
||||
rubocop (1.81.6)
|
||||
rubocop (1.81.7)
|
||||
json (~> 2.3)
|
||||
language_server-protocol (~> 3.17.0.2)
|
||||
lint_roller (~> 1.1.0)
|
||||
@ -183,7 +183,7 @@ DEPENDENCIES
|
||||
nokogiri (= 1.18.10)
|
||||
rackup (= 2.2.1)
|
||||
rake (= 13.3.1)
|
||||
rubocop (= 1.81.6)
|
||||
rubocop (= 1.81.7)
|
||||
ruby-lsp (= 0.26.2)
|
||||
sass-embedded (= 1.93.2)
|
||||
sass-globbing (= 1.1.5)
|
||||
|
||||
@ -107,9 +107,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 2025
|
||||
current_minor_version: 10
|
||||
current_patch_version: 4
|
||||
date_released: 2025-10-24
|
||||
current_minor_version: 11
|
||||
current_patch_version: 0
|
||||
date_released: 2025-11-05
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -174,17 +174,6 @@ yellow:
|
||||
ship_to: America
|
||||
url: https://cloudfree.shop/product/home-assistant-yellow/
|
||||
logo: /images/distributors/cloudfree.webp
|
||||
- name: Seeed Studio
|
||||
ship_from: US
|
||||
ship_to: America
|
||||
url: https://www.seeedstudio.com/Home-Assistant-Yellow-Kit-with-selectable-CM4.html
|
||||
logo: /images/distributors/seeed-studio.webp
|
||||
# Asia
|
||||
- name: Seeed Studio
|
||||
ship_from: China
|
||||
ship_to: Asia
|
||||
url: https://www.seeedstudio.com/Home-Assistant-Yellow-Kit-with-selectable-CM4.html
|
||||
logo: /images/distributors/seeed-studio.webp
|
||||
# Australia
|
||||
- name: Smart Guys
|
||||
ship_from: Australia
|
||||
@ -192,16 +181,6 @@ yellow:
|
||||
url: https://smartguys.com.au/product/home-assistant-yellow-smart-hub/
|
||||
logo: /images/distributors/smart-guys.webp
|
||||
# Europe
|
||||
- name: Botland
|
||||
ship_from: Poland
|
||||
ship_to: Europe
|
||||
url: https://botland.com.pl/centralki-i-bramki-sieciowe/24698-home-assistant-yellow-standard-kit-inteligenta-centralka-zigbee-thread-nabu-casa-yellow-kit-std-794677011741.html
|
||||
logo: /images/distributors/botland.webp
|
||||
- name: Mauser
|
||||
ship_from: Portugal
|
||||
ship_to: Europe
|
||||
url: https://mauser.pt/catalog/product_info.php?products_id=095-3150
|
||||
logo: /images/distributors/mauser.png
|
||||
- name: Pi-Shop.ch
|
||||
ship_from: Switzerland
|
||||
ship_to: Europe
|
||||
@ -212,21 +191,6 @@ yellow:
|
||||
ship_to: Europe
|
||||
url: https://raspberrypi.dk/en/product/home-assistant-yellow/
|
||||
logo: /images/distributors/RaspberryPi-dk.webp
|
||||
- name: Seeed Studio
|
||||
ship_from: Germany
|
||||
ship_to: Europe
|
||||
url: https://www.seeedstudio.com/Home-Assistant-Yellow-Kit-with-selectable-CM4.html
|
||||
logo: /images/distributors/seeed-studio.webp
|
||||
- name: The Pi Hut
|
||||
ship_from: UK
|
||||
ship_to: Europe
|
||||
url: https://thepihut.com/products/home-assistant-yellow
|
||||
logo: /images/distributors/pi-hut.webp
|
||||
- name: Domadoo
|
||||
ship_from: France
|
||||
ship_to: Europe
|
||||
url: https://www.domadoo.fr/en/smart-home-hub/7113-nabu-casa-home-assistant-yellow-kit-with-power-supply.html
|
||||
logo: /images/distributors/domadoo.jpg
|
||||
zbt-1:
|
||||
name: "<strong>Home Assistant Connect ZBT-1</strong>"
|
||||
distributors:
|
||||
|
||||
@ -23,6 +23,22 @@
|
||||
</a>
|
||||
{% endif %}
|
||||
|
||||
<a href="https://www.youtube.com/watch?v=HSRvso6cbf0" class="material-card picture-promo picture-top" target="_blank"
|
||||
rel="noopener noreferrer" aria-label="Join the livestream for our latest product reveal!"
|
||||
style="background-image: url(/images/frontpage/feature-nov19.webp);background-size: cover;aspect-ratio: 900/600;">
|
||||
<div class="caption">
|
||||
<div>
|
||||
<div class="title">
|
||||
Product launch incoming
|
||||
</div>
|
||||
<div class="subtitle">
|
||||
Join the livestream for our latest product reveal!<br />
|
||||
November 19 @ 12PM PT / 3PM ET / 21:00 CET
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</a>
|
||||
|
||||
{% assign releases_post_limit = 2 %}
|
||||
{% assign blog_post_limit = 4 %}
|
||||
<!-- Home Assistant updates posts -->
|
||||
|
||||
@ -7,11 +7,14 @@ ha_release: 2025.11
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- "@kclif9"
|
||||
- '@kclif9'
|
||||
- '@JagadishDhanamjayam'
|
||||
ha_domain: actron_air
|
||||
ha_platforms:
|
||||
- climate
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: bronze
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
The **Actron Air** {% term integration %} allows you to control [Actron Air](https://www.actronair.com.au/) Air Conditioning controllers into Home Assistant.
|
||||
@ -39,4 +42,3 @@ Each zone will be reflected as a separate climate entity. You can set the temper
|
||||
This integration follows standard integration removal.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
|
||||
@ -13,8 +13,8 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: bronze
|
||||
ha_integration_type: device
|
||||
ha_quality_scale: silver
|
||||
---
|
||||
|
||||
Ubiquiti <abbr title="Ubiquity Internet Service Provider">UISP</abbr>-range of [wireless](https://techspecs.ui.com/uisp/wireless) products offer a comprehensive suite of devices specifically designed for interconnecting various locations. As long as these airOS devices can 'see' each other without any (or limited) obstructions like buildings or trees, a stable and high-bandwidth "beam" can be established. Even their most cost-effective devices can achieve up to 450 Mbps real TCP/IP throughput and maintain reliable links up 10km range!
|
||||
|
||||
@ -19,7 +19,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: hub
|
||||
ha_quality_scale: silver
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
The **Alexa Devices** {% term integration %} lets you control Alexa-enabled devices connected to your Amazon account.
|
||||
|
||||
@ -11,6 +11,7 @@ ha_codeowners:
|
||||
- '@bdr99'
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- select
|
||||
- sensor
|
||||
- water_heater
|
||||
ha_integration_type: integration
|
||||
|
||||
@ -21,6 +21,24 @@ The **Brother Printer** {% term integration %} allows you to read current data f
|
||||
It usually provides information about the device's state, the left amount of ink or toner and the remaining lifetime of the drum or other parts of the printer.
|
||||
The integration monitors every supported part.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- To enable SNMP, navigate to the printer's web interface (for example: `http://192.168.5.6`) and turn it on under **Network** > **Protocol** > **SNMP**.
|
||||
- For some models, access to the web interface is password-protected.
|
||||
- For some printers, the default password is printed on a sticker on the back of the printer, preceded by **Pwd**.
|
||||
- If the printer does not have a password on the sticker, the default password is `initpass`.
|
||||
|
||||
- For some Brother devices, **SNMPv3 read-write access and v1/v2c read-only access** is the option required (under advanced settings).
|
||||
|
||||
|
||||
|
||||
## Unsupported devices
|
||||
|
||||
The following devices are not supported by the integration:
|
||||
|
||||
- MFC-8660DN
|
||||
- MFC-8860DN
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
{% configuration_basic %}
|
||||
@ -34,21 +52,98 @@ Type of the printer:
|
||||
description: "Brother printer type: ink or laser."
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Supported functionality
|
||||
|
||||
The Brother integration provides the following entities.
|
||||
|
||||
### Sensors
|
||||
|
||||
- **Belt unit remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the belt unit
|
||||
- **Black drum page counter**
|
||||
- **Description**: Total number of pages printed with the black drum
|
||||
- **Black drum remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the black drum
|
||||
- **Black drum remaining pages**
|
||||
- **Description**: Estimated number of pages remaining for the black drum
|
||||
- **Black ink remaining**
|
||||
- **Description**: Percentage of black ink remaining
|
||||
- **Black toner remaining**
|
||||
- **Description**: Percentage of black toner remaining
|
||||
- **B/W pages**
|
||||
- **Description**: Total number of black and white pages printed
|
||||
- **Color pages**
|
||||
- **Description**: Total number of color pages printed
|
||||
- **Cyan drum page counter**
|
||||
- **Description**: Total number of pages printed with the cyan drum
|
||||
- **Cyan drum remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the cyan drum
|
||||
- **Cyan drum remaining pages**
|
||||
- **Description**: Estimated number of pages remaining for the cyan drum
|
||||
- **Cyan ink remaining**
|
||||
- **Description**: Percentage of cyan ink remaining
|
||||
- **Cyan toner remaining**
|
||||
- **Description**: Percentage of cyan toner remaining
|
||||
- **Drum page counter**
|
||||
- **Description**: Total number of pages printed using the main drum
|
||||
- **Drum remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the main drum
|
||||
- **Drum remaining pages**
|
||||
- **Description**: Estimated number of pages remaining for the main drum
|
||||
- **Duplex unit page counter**
|
||||
- **Description**: Total number of pages printed using the duplex unit
|
||||
- **Fuser remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the fuser unit
|
||||
- **Laser remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the laser unit
|
||||
- **Last restart**
|
||||
- **Description**: Date and time of the last printer restart
|
||||
- **Remarks**: This entity is disabled by default
|
||||
- **Magenta drum page counter**
|
||||
- **Description**: Total number of pages printed with the magenta drum
|
||||
- **Magenta drum remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the magenta drum
|
||||
- **Magenta drum remaining pages**
|
||||
- **Description**: Estimated number of pages remaining for the magenta drum
|
||||
- **Magenta ink remaining**
|
||||
- **Description**: Percentage of magenta ink remaining
|
||||
- **Magenta toner remaining**
|
||||
- **Description**: Percentage of magenta toner remaining
|
||||
- **Page counter**
|
||||
- **Description**: Total number of pages printed by the printer
|
||||
- **PF Kit 1 remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of paper feed kit 1
|
||||
- **PF Kit MP remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of multipurpose tray feed kit
|
||||
- **Status**
|
||||
- **Description**: Current printer status or condition
|
||||
- **Yellow drum page counter**
|
||||
- **Description**: Total number of pages printed with the yellow drum
|
||||
- **Yellow drum remaining lifetime**
|
||||
- **Description**: Remaining lifetime percentage of the yellow drum
|
||||
- **Yellow drum remaining pages**
|
||||
- **Description**: Estimated number of pages remaining for the yellow drum
|
||||
- **Yellow ink remaining**
|
||||
- **Description**: Percentage of yellow ink remaining
|
||||
- **Yellow toner remaining**
|
||||
- **Description**: Percentage of yellow toner remaining
|
||||
|
||||
{% note %}
|
||||
Some very old Brother printers use different data format and these models are not supported. The integration will show information about that during configuration.
|
||||
Not all printer models support all the listed entities, the set of entities is tailored to a specific printer model.
|
||||
{% endnote %}
|
||||
|
||||
## Configuring the printer
|
||||
## Data updates
|
||||
|
||||
To enable SNMP, navigate to the printer's web interface (for example: `http://192.168.5.6`) and turn it on under Network / Protocol / SNMP. For some models, access to the web interface is password-protected. For some printers, the default password is printed on a sticker on the back of the printer, preceded by "Pwd:". If the printer does not have a password on the sticker, the default password is "initpass".
|
||||
By default, the integration {% term polling polls %} data from the device every 30 seconds.
|
||||
|
||||
For some Brother devices, `SNMPv3 read-write access and v1/v2c read-only access` is the option required (under advanced settings).
|
||||
## Possible use-cases
|
||||
|
||||
|
||||
- Monitor printer status and send notifications when paper jams or other unexpected events occur.
|
||||
|
||||
## Sensor example
|
||||
## Examples
|
||||
|
||||
You can configure Home Assistant to alert you when the printer jams or runs out of paper as follows. First, add the following to {% term "`configuration.yaml`" %} under the `template:` section (Note: replace `sensor.hl_l2340d_status` with the actual name of your sensor):
|
||||
You can configure Home Assistant to alert you when the printer jams or runs out of paper as follows. First, add the following to {% term "`configuration.yaml`" %} under the `template:` section.
|
||||
Replace `sensor.hl_l2340d_status` with the actual name of your sensor.
|
||||
|
||||
{% raw %}
|
||||
|
||||
@ -90,3 +185,30 @@ Then, add this under the `alert:` section:
|
||||
The above will send an alert for paper jam or out of paper whenever the condition is detected, assuming you have the Home Assistant app configured on your phone so that alerts can be sent directly to it. If you don't use the Home Assistant app, you will need to set up a different notifier.
|
||||
|
||||
Change `my_phone_notify` to the actual notifier you are using.
|
||||
|
||||
## Known limitations
|
||||
|
||||
- Some very old Brother printers use a different data format. Those models are not supported. The integration will show information about that during configuration.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Printer is unavailable after changing SNMP community
|
||||
|
||||
After changing the SNMP community in the printer configuration, you need to reconfigure the device in Home Assistant. To do this:
|
||||
|
||||
1. Go to {% my integrations title="**Settings** > **Devices & services**" %}.
|
||||
2. Select **Brother Printer**.
|
||||
3. Click {% icon "mdi:dots-vertical" %}.
|
||||
4. Select **Reconfigure**.
|
||||
|
||||
### Integration reports problems with communication or data updating
|
||||
|
||||
1. Check if the printer is online and available on the local network.
|
||||
2. Check in the printer's web interface if SNMP is enabled.
|
||||
3. In the printer's web interface, verify that **SNMPv3 read/write access and v1/v2c read-only access** is enabled, if available.
|
||||
|
||||
## Removing the integration
|
||||
|
||||
This integration follows standard integration removal. No extra steps are required.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -201,7 +201,7 @@ json_attributes_topic:
|
||||
required: false
|
||||
type: string
|
||||
max_humidity:
|
||||
description: The minimum target humidity percentage that can be set.
|
||||
description: The maximum target humidity percentage that can be set.
|
||||
required: false
|
||||
type: float
|
||||
default: 99
|
||||
@ -210,7 +210,7 @@ max_temp:
|
||||
type: float
|
||||
required: false
|
||||
min_humidity:
|
||||
description: The maximum target humidity percentage that can be set.
|
||||
description: The minimum target humidity percentage that can be set.
|
||||
required: false
|
||||
type: float
|
||||
default: 30
|
||||
|
||||
@ -26,7 +26,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: hub
|
||||
ha_quality_scale: silver
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
The **Comelit SimpleHome** {% term integration %} allows you to control your [Comelit home automation devices](https://comelitgroup.it/installatore/offerta/home-building-automation/).
|
||||
|
||||
@ -8,7 +8,7 @@ ha_quality_scale: internal
|
||||
ha_domain: downloader
|
||||
ha_codeowners:
|
||||
- '@erwindouna'
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ ha_domain: dsmr_reader
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
---
|
||||
|
||||
The `dsmr_reader` sensor integration allows you to easily add all sensors that [DSMR Reader](https://dsmr-reader.readthedocs.io/en/latest/) (Dutch Smart Meter Requirements Reader) exposes to MQTT. It adds a separate sensor for every field in the MQTT topics which is named `sensor_dsmr_<mqtt_topic>`.
|
||||
|
||||
@ -1,27 +1,31 @@
|
||||
---
|
||||
title: UK Environment Agency Flood Monitoring
|
||||
description: Monitor nearby water levels and be prepared for flooding with the UK Environment Agency API integration.
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.115
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@Jc2k'
|
||||
---
|
||||
|
||||
The `eafm` integration offers integration with the [UK Environment Agency Flood Monitoring](https://environment.data.gov.uk/flood-monitoring/doc/reference) API to provide sensors for nearby water levels. Combined with Home Assistant notifications, you could give yourself a warning if a nearby river was likely to flood your local cycle path or the only road out of your village.
|
||||
|
||||
{% important %}
|
||||
|
||||
The UK Environment Agency Flood Monitoring only provides data for England - Northern Ireland, Scotland and Wales have their own flood agencies.
|
||||
|
||||
{% endimportant %}
|
||||
|
||||
## Configuration
|
||||
|
||||
Home Assistant offers the flood monitoring integration through **Settings** -> **Devices & services** -> **Environment Agency Flood Gauges**.
|
||||
|
||||
You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://check-for-flooding.service.gov.uk/river-and-sea-levels).
|
||||
|
||||
Sensors for that monitoring station should then appear in your Home Assistant instance.
|
||||
---
|
||||
title: Environment Agency Flood Gauges
|
||||
description: Monitor nearby water levels and be prepared for flooding with the UK Environment Agency API integration.
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.115
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@Jc2k'
|
||||
ha_domain: eafm
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `eafm` integration offers integration with the [UK Environment Agency Flood Monitoring](https://environment.data.gov.uk/flood-monitoring/doc/reference) API to provide sensors for nearby water levels. Combined with Home Assistant notifications, you could give yourself a warning if a nearby river was likely to flood your local cycle path or the only road out of your village.
|
||||
|
||||
{% important %}
|
||||
|
||||
The UK Environment Agency Flood Monitoring only provides data for England - Northern Ireland, Scotland and Wales have their own flood agencies.
|
||||
|
||||
{% endimportant %}
|
||||
|
||||
## Configuration
|
||||
|
||||
Home Assistant offers the flood monitoring integration through **Settings** -> **Devices & services** -> **Environment Agency Flood Gauges**.
|
||||
|
||||
You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://check-for-flooding.service.gov.uk/river-and-sea-levels).
|
||||
|
||||
Sensors for that monitoring station should then appear in your Home Assistant instance.
|
||||
|
||||
@ -25,7 +25,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
- vacuum
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
The `ecovacs` {% term integration %} is the main integration to integrate [Ecovacs](https://www.ecovacs.com) (Deebot) vacuums and mowers.
|
||||
|
||||
@ -7,17 +7,23 @@ ha_category:
|
||||
- Switch
|
||||
ha_domain: eltako
|
||||
ha_integration_type: brand
|
||||
works_with:
|
||||
- matter
|
||||
ha_platforms:
|
||||
- switch
|
||||
ha_iot_standard: matter
|
||||
ha_brand: true
|
||||
---
|
||||
|
||||
[Eltako](https://www.eltako.com) is committed to making sure their products are up-to-date and ready to use in Home Assistant.
|
||||
|
||||
Eltako Matter devices work locally and integrate seamlessly with the Matter integration in Home Assistant. As all connectivity is happening locally, status updates and controlling your devices happen instantly in Home Assistant.
|
||||
{% include integrations/wwha.md url="https://www.eltako.com" name="Eltako" %}
|
||||
|
||||
{% my add_matter_device badge domain=page.ha_domain %}
|
||||
## Supported devices
|
||||
|
||||
[Learn more about Matter in Home Assistant.](/integrations/matter/)
|
||||
The following devices are supported:
|
||||
|
||||
- [Universal dimming actuator EUD62NPN-IPM](https://www.eltako.com/en/catalog/products/1238/eud62npn-ipm110-240v)
|
||||
- [Universal dimming actuator EUD64NPN-IPM](https://www.eltako.com/en/catalog/products/1761/eud64npn-ipm)
|
||||
- [Impulse switch ESR64PF-IPM](https://www.eltako.com/en/catalog/products/1760/esr64pf-ipm)
|
||||
- [Impulse switch ESR64NP-IPM](https://www.eltako.com/en/catalog/products/1759/esr64np-ipm)
|
||||
- [Shading actuator ESB64NP-IPM](https://www.eltako.com/en/catalog/products/1792/esb64np-ipm)
|
||||
|
||||
@ -118,7 +118,16 @@ This section shows a similar example to the example automation shown above in YA
|
||||
- Type `event` and select your button entity.
|
||||
- **Important**: Leave the other fields **empty**.
|
||||
|
||||
4. Define the condition when something should happen.
|
||||
4. Prevent the automation from running on unavailable or unknown states.
|
||||
- Under **Conditions**, select **Add building block**, then, select **Not**.
|
||||
- Inside the **Not** block, select **Add condition**, then, select **Entity** > **State**.
|
||||
- Type `event` and select your button event entity.
|
||||
- Under **State**, select **Unavailable**.
|
||||
- **Important**: Leave the other fields **empty**.
|
||||
- Add another condition inside the **Not** block, but this time select **Unknown** as the state.
|
||||
- **Note** Alternatively, instead of conditions this can be done using the `not_state` attribute of the state trigger, in YAML.
|
||||
|
||||
5. Define the condition when something should happen.
|
||||
- Under **Then do**, select **Add action**.
|
||||
- Type `choose` and select **Add condition**.
|
||||
- Select **Entity** > **State** and select your button event entity from the list.
|
||||
@ -126,12 +135,12 @@ This section shows a similar example to the example automation shown above in YA
|
||||
- Under **State**, select the state change you want to act as trigger, for example **Pressed once**.
|
||||
- **Pressed once** is the event type. But the state of this event is the timestamp of when the button was pressed. This is why we automate on the state change so that it is triggered every time the button is pressed.
|
||||
|
||||
5. Define what should happen when your automation is triggered (when the button is pressed, for example).
|
||||
6. Define what should happen when your automation is triggered (when the button is pressed, for example).
|
||||
- Select **Add action** and define your action.
|
||||
6. Repeat these steps for each event type you want to monitor.
|
||||
7. Repeat these steps for each event type you want to monitor.
|
||||
- In this example, we want to do something else when the button was pressed twice.
|
||||
|
||||
7. **Save** the automation.
|
||||
8. **Save** the automation.
|
||||
|
||||
## Device class
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ha_domain: fastdotcom
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
---
|
||||
|
||||
The `fastdotcom` integration uses the [Fast.com](https://fast.com/) web service to measure network bandwidth performance.
|
||||
|
||||
@ -10,7 +10,7 @@ ha_domain: feedreader
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- event
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
related:
|
||||
- docs: /common-tasks/general/#defining-a-custom-polling-interval
|
||||
title: Defining a custom polling interval
|
||||
|
||||
@ -1,17 +1,18 @@
|
||||
---
|
||||
title: Fing
|
||||
description: "Instructions on integrating your Fing Agent with Home Assistant"
|
||||
ha_release: "2025.11"
|
||||
ha_category:
|
||||
- Presence detection
|
||||
description: Instructions on integrating your Fing Agent with Home Assistant
|
||||
ha_release: '2025.11'
|
||||
ha_category:
|
||||
- Presence detection
|
||||
ha_platforms:
|
||||
- device_tracker
|
||||
- device_tracker
|
||||
ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@Lorenzo-Gasparini'
|
||||
ha_domain: fing
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: bronze
|
||||
---
|
||||
|
||||
The **Fing** {% term integration %} allows Home Assistant to retrieve detailed information about the devices on your local network. [Fing](https://www.fing.com/) helps home users and IT professionals monitor, protect, and understand their networks with intuitive tools that make connectivity management simple and effective.
|
||||
|
||||
@ -3,15 +3,17 @@ title: Firefly III
|
||||
description: Instructions on how to integrate Firefly III with Home Assistant.
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_release: "2025.11"
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: '2025.11'
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@erwindouna'
|
||||
ha_domain: firefly_iii
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: hub
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: bronze
|
||||
---
|
||||
|
||||
The Firefly III {% term integration %} is used as an interface to the [Firefly III API](https://api-docs.firefly-iii.org/).
|
||||
@ -44,4 +46,4 @@ This integration follows standard integration removal.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
After removing the integration, consider deleting the Firefly III access token.
|
||||
After removing the integration, consider deleting the Firefly III access token.
|
||||
|
||||
@ -25,7 +25,7 @@ ha_platforms:
|
||||
- switch
|
||||
- update
|
||||
ha_ssdp: true
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
related:
|
||||
- docs: /common-tasks/general/#enabling-or-disabling-entities
|
||||
title: Enabling or disabling entities
|
||||
|
||||
@ -25,3 +25,9 @@ Measuring station:
|
||||
Name:
|
||||
description: "Service name in Home Assistant, by default, this is the name of your Home Assistant instance. For example `Home`."
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Removing the integration
|
||||
|
||||
This integration follows standard integration removal, no extra steps are required.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -35,6 +35,7 @@ ha_platforms:
|
||||
- notify
|
||||
- sensor
|
||||
- switch
|
||||
- valve
|
||||
ha_integration_type: helper
|
||||
---
|
||||
|
||||
|
||||
@ -13,6 +13,8 @@ ha_platforms:
|
||||
- switch
|
||||
ha_config_flow: true
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@johanzander'
|
||||
---
|
||||
|
||||
The Growatt integration allows you to retrieve data from Growatt inverters. During setup, you can choose from various regional endpoint servers:
|
||||
|
||||
@ -15,13 +15,14 @@ ha_platforms:
|
||||
- calendar
|
||||
- diagnostics
|
||||
- image
|
||||
- notify
|
||||
- sensor
|
||||
- switch
|
||||
- todo
|
||||
ha_codeowners:
|
||||
- '@tr4nt0r'
|
||||
ha_config_flow: true
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
related:
|
||||
- docs: /integrations/todo
|
||||
title: To-do list integration documentation
|
||||
|
||||
@ -11,6 +11,7 @@ ha_domain: homeassistant_connect_zbt2
|
||||
ha_integration_type: hardware
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- switch
|
||||
- update
|
||||
published: false
|
||||
ha_quality_scale: bronze
|
||||
|
||||
@ -10,6 +10,7 @@ ha_codeowners:
|
||||
ha_domain: homeassistant_hardware
|
||||
ha_integration_type: system
|
||||
ha_platforms:
|
||||
- switch
|
||||
- update
|
||||
---
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ha_domain: homeassistant_sky_connect
|
||||
ha_integration_type: hardware
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- switch
|
||||
- update
|
||||
---
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ ha_codeowners:
|
||||
ha_domain: homeassistant_yellow
|
||||
ha_integration_type: hardware
|
||||
ha_platforms:
|
||||
- switch
|
||||
- update
|
||||
---
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ ha_platforms:
|
||||
- select
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
ha_domain: husqvarna_automower
|
||||
ha_quality_scale: silver
|
||||
---
|
||||
|
||||
@ -13,7 +13,7 @@ ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: silver
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
IMGW-PIB {% term integration %} uses hydrological data from [Institute of Meteorology and Water Management - National Research Institute](https://hydro.imgw.pl) to present information about rivers and water reservoirs in Poland.
|
||||
|
||||
@ -16,7 +16,7 @@ ha_platforms:
|
||||
- update
|
||||
ha_codeowners:
|
||||
- '@mib1185'
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_quality_scale: silver
|
||||
---
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ha_domain: inels
|
||||
ha_platforms:
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: bronze
|
||||
---
|
||||
|
||||
The **iNELS** {% term integration %} allows you to control and monitor the devices connected to your control units ([BUS](https://www.elkoep.com/wired) or [eLAN](https://www.elkoep.com/wireless)).
|
||||
|
||||
@ -6,7 +6,7 @@ ha_category:
|
||||
- Energy
|
||||
- Sensor
|
||||
ha_codeowners:
|
||||
- '@MaestroOnICe'
|
||||
- '@jukrebs'
|
||||
ha_quality_scale: bronze
|
||||
ha_domain: iometer
|
||||
ha_integration_type: device
|
||||
|
||||
@ -15,7 +15,7 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@tr4nt0r'
|
||||
ha_domain: iron_os
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Konnected.io
|
||||
title: Konnected.io (Legacy)
|
||||
description: Connect wired alarm sensors and siren using the NodeMCU based Konnected Alarm Panel
|
||||
ha_category:
|
||||
- Alarm
|
||||
|
||||
@ -12,6 +12,10 @@ ha_supporting_domain: esphome
|
||||
ha_supporting_integration: ESPHome
|
||||
works_with:
|
||||
- local
|
||||
ha_codeowners:
|
||||
- '@jesserockz'
|
||||
- '@kbx81'
|
||||
- '@bdraco'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- alarm_control_panel
|
||||
|
||||
@ -8,12 +8,14 @@ ha_release: 0.49
|
||||
ha_domain: london_underground
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_codeowners:
|
||||
- '@jpbede'
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
ha_quality_scale: legacy
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The `london_underground` {% term integration %} will display the status of London underground lines, as well as the overground lines and the DLR.
|
||||
|
||||
@ -12,7 +12,8 @@ ha_domain: lunatone
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- light
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
ha_quality_scale: silver
|
||||
---
|
||||
|
||||
The **Lunatone** {% term integration %} is used to integrate with the devices of [Lunatone](https://www.lunatone.com) that offer a REST API.
|
||||
|
||||
@ -12,7 +12,7 @@ ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
- water_heater
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
ha_codeowners:
|
||||
- '@erwindouna'
|
||||
---
|
||||
|
||||
@ -12,6 +12,7 @@ ha_domain: meteo_lt
|
||||
ha_platforms:
|
||||
- weather
|
||||
ha_integration_type: service
|
||||
ha_quality_scale: bronze
|
||||
---
|
||||
|
||||
The **Meteo.lt** {% term integration %} uses meteorological data from the [Lithuanian Hydrometeorological Service](https://www.meteo.lt) (<abbr title="Lietuvos hidrometeorologijos tarnyba">LHMT</abbr>) to provide weather forecasts for locations in Lithuania. You can set up one or more locations via the user interface.
|
||||
@ -72,4 +73,3 @@ Weather data is automatically updated every 30 minutes from the Meteo.lt <abbr t
|
||||
This integration follows standard integration removal. No extra steps are required.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
- vacuum
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
ha_zeroconf: true
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
@ -43,7 +43,7 @@ ha_platforms:
|
||||
- vacuum
|
||||
- valve
|
||||
- water_heater
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
|
||||
@ -18,6 +18,18 @@ ha_integration_type: integration
|
||||
|
||||
The **Music Assistant** (MA) {% term integration %} allows you to connect Home Assistant to a [Music Assistant Server](https://music-assistant.io/) (Required version 2.4 or later). Once configured, all [MA Players](https://music-assistant.io/player-support/) show up as Home Assistant [media player entities](/integrations/media_player/). Media players will allow you to control media playback and see the currently playing item.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before installing this integration, ensure you have a running Music Assistant server. Instructions for installing the Music Assistant server are available in the [Music Assistant documentation](https://www.music-assistant.io/installation/)
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
### Manual configuration
|
||||
|
||||
Under normal circumstances, Home Assistant automatically discovers your running Music Assistant server. If there is something special about the Home Assistant or Music Assistant setup (for example, the Music Assistant server is running as a remote Docker container) or discovery is not working, you can manually specify the URL to your Music Assistant server.
|
||||
|
||||
## Supported functionality
|
||||
|
||||
There is currently support for the following Home Assistant Platforms:
|
||||
|
||||
- [Media player](#media-player-entities)
|
||||
@ -26,27 +38,19 @@ There is currently support for the following Home Assistant Platforms:
|
||||
|
||||
All of the Home Assistant [Media Player Control Actions](https://www.home-assistant.io/integrations/media_player/#media-control-actions) are supported.
|
||||
|
||||
The `media_content_id` payload for `media_player.play_media` can be any of the following:
|
||||
If using `media_player.play_media`, then note the `media_content_id` payload can be any of the following:
|
||||
|
||||
- The name of a track, artist, or album. For example, `Queen`.
|
||||
- A track or album combined with the artist's name. For example, `Queen - Innuendo`.
|
||||
- A streaming provider URI. For example, `spotify://artist/12345`.
|
||||
- A streaming provider URL. For example, `https://open.spotify.com/track/31cWPvM99ZHxMl3mdgiw4I`.
|
||||
|
||||
The `media_content_id` payload for `media_player.browse_media` must be a URI of the form `library://artist/1`, `library://album/20`, or `spotify://album/5zj4Ej0FrlJQaSo0d6cttH`. The type of item that the URI refers to must be an album or artist.
|
||||
If using `media_player.browse_media`, then the `media_content_id` payload must be a URI of the form `library://artist/1`, `library://album/20`, or `spotify://album/5zj4Ej0FrlJQaSo0d6cttH`. The type of item that the URI refers to must be an album or artist.
|
||||
|
||||
These URIs can be obtained from, for example, the output of the `get_library` or `search` actions described below or the `media_player.browse_media` action from Home Assistant.
|
||||
These URIs can, for example, be obtained from the output of the `get_library` or `search` actions described below or the `media_player.browse_media` action from Home Assistant.
|
||||
|
||||
Streaming provider URLs can be obtained from the web interface of the provider.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
### Manual configuration
|
||||
|
||||
Under normal circumstances, Home Assistant automatically discovers your running Music Assistant Server. If there is something special about the Home Assistant or MA setup (for example, the MA server is running as a remote Docker container) or discovery is not working, you can manually specify the URL to your Music Assistant server. If the Music Assistant Server is not installed, then follow these [installation instructions](https://music-assistant.io/installation/).
|
||||
|
||||
## Supported functionality
|
||||
|
||||
### Media player entities
|
||||
|
||||
The Music Assistant integration creates media player entities for all players and groups available in MA, including those imported from Home Assistant. This is needed to provide the full functionality Music Assistant has to offer. This full functionality includes transfer of the playing queue of music from one player to another, automatic pausing of playback during announcements, and richer options for selecting the media for playback. These entities will display media information, playback progress, and playback controls.
|
||||
|
||||
@ -23,7 +23,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
- update
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
related:
|
||||
- url: https://myuplink.com/
|
||||
title: myUplink web portal
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Neo
|
||||
description: Integrate Neo (Powered by Shelly) devices
|
||||
description: Connect and control your Neo devices using the Shelly integration
|
||||
ha_category:
|
||||
- Binary sensor
|
||||
- Climate
|
||||
@ -16,16 +16,16 @@ ha_category:
|
||||
- Update
|
||||
- Valve
|
||||
ha_release: 0.115
|
||||
ha_domain: neo
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: shelly
|
||||
ha_supporting_integration: Shelly
|
||||
ha_codeowners:
|
||||
- '@balloob'
|
||||
- '@bieniu'
|
||||
- '@thecode'
|
||||
- '@chemelli74'
|
||||
- '@bdraco'
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: neo
|
||||
ha_config_flow: true
|
||||
ha_zeroconf: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
@ -41,9 +41,8 @@ ha_platforms:
|
||||
- text
|
||||
- update
|
||||
- valve
|
||||
ha_integration_type: virtual
|
||||
ha_supporting_domain: shelly
|
||||
ha_supporting_integration: Shelly
|
||||
ha_iot_class: Local Push
|
||||
ha_zeroconf: true
|
||||
---
|
||||
|
||||
{% include integrations/supported_brand.md %}
|
||||
{% include integrations/supported_brand.md %}
|
||||
|
||||
@ -15,7 +15,7 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- sensor
|
||||
- update
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
---
|
||||
|
||||
The `nextcloud` integration pulls summary [Nextcloud](https://nextcloud.com/) information into Home Assistant.
|
||||
|
||||
@ -16,7 +16,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: service
|
||||
ha_quality_scale: bronze
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
NextDNS is a DNS service that protects from all kinds of security threats, blocks ADS and trackers on websites and in apps, and provides a safe and supervised Internet for kids — on all devices and on all networks. The NextDNS integration allows you to monitor NextDNS statistics and control its configuration.
|
||||
@ -366,4 +366,4 @@ automation:
|
||||
|
||||
## Known limitations
|
||||
|
||||
There are no known limitations.
|
||||
There are no known limitations.
|
||||
|
||||
@ -1,20 +1,22 @@
|
||||
---
|
||||
title: Nintendo Switch Parental Controls
|
||||
title: Nintendo Switch parental controls
|
||||
description: The Nintendo Switch Parental Controls integration allows you to monitor and control screentime for children via the Nintendo Switch Parental Controls service.
|
||||
ha_release: 2025.11
|
||||
ha_iot_class: cloud_polling
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@pantherale0'
|
||||
ha_domain: nintendo_parental
|
||||
ha_domain: nintendo_parental_controls
|
||||
ha_integration_type: integration
|
||||
ha_platforms:
|
||||
- sensor
|
||||
- time
|
||||
- switch
|
||||
- number
|
||||
- sensor
|
||||
- switch
|
||||
- time
|
||||
ha_category: []
|
||||
ha_quality_scale: bronze
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
|
||||
The **Nintendo Switch Parental Controls** {% term integration %} integrates with the Nintendo Switch Parental Controls service, allowing parents to monitor and control screentime for their children.
|
||||
|
||||
## Supported devices
|
||||
|
||||
@ -10,13 +10,13 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@tr4nt0r'
|
||||
ha_domain: ntfy
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- event
|
||||
- notify
|
||||
- sensor
|
||||
ha_quality_scale: bronze
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
The **ntfy** {% term integration %} allows publishing push notifications on [ntfy.sh](https://ntfy.sh/) or other ntfy services.
|
||||
|
||||
@ -18,6 +18,7 @@ ha_platforms:
|
||||
- switch
|
||||
ha_integration_type: hub
|
||||
ha_zeroconf: true
|
||||
ha_quality_scale: silver
|
||||
---
|
||||
|
||||
The Onewire integration supports sensors that use the 1-wire bus for communication.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: OPNSense
|
||||
title: OPNsense
|
||||
description: Instructions on how to configure OPNsense integration
|
||||
ha_category:
|
||||
- Hub
|
||||
|
||||
@ -11,10 +11,11 @@ ha_domain: portainer
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- switch
|
||||
- sensor
|
||||
- button
|
||||
ha_integration_type: integration
|
||||
- diagnostics
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: hub
|
||||
ha_quality_scale: bronze
|
||||
---
|
||||
|
||||
|
||||
@ -13,6 +13,7 @@ related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
ha_quality_scale: legacy
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The `prowl` {% term integration %} uses [Prowl](https://www.prowlapp.com/) to deliver push notifications from Home Assistant to your iOS device.
|
||||
|
||||
@ -421,6 +421,7 @@ The following models have been tested and confirmed to work with a direct link t
|
||||
- **[RLC-823S2](https://reolink.com/product/rlc-823s2/)**
|
||||
- [RLC-830A](https://reolink.com/product/rlc-830a/)
|
||||
- [RLC-833A](https://reolink.com/product/rlc-833a/)
|
||||
- [RLC-840A](https://reolink.com/product/rlc-840a/)
|
||||
- [RLC-843A](https://reolink.com/product/rlc-843a/)
|
||||
- [RLC-1212A](https://reolink.com/product/rlc-1212a/)
|
||||
- **[RLC-1224A](https://reolink.com/product/rlc-1224a/)**
|
||||
|
||||
@ -91,3 +91,15 @@ For example:
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Removing the integration
|
||||
|
||||
This integration follows standard integration removal steps.
|
||||
|
||||
{% note %}
|
||||
Removing this integration from Home Assistant will not end or disrupt your paid subscription.
|
||||
{% endnote %}
|
||||
|
||||
Any pickups scheduled or modified by this integration will persist after removing the integration, and they can continue to be managed using the Ridwell site or app.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -17,11 +17,10 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- diagnostics
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
ha_quality_scale: legacy
|
||||
---
|
||||
|
||||
The `satel_integra` {% term integration %} will allow Home Assistant users who own a Satel Integra alarm panel to leverage their alarm system and its sensors to provide Home Assistant with information about their homes. Connectivity between Home Assistant and the alarm is accomplished through a ETHM extension module that must be installed in the alarm. Compatible with ETHM-1 Plus module with firmware version > 2.00 (version 2.04 confirmed).
|
||||
|
||||
@ -9,6 +9,7 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@JeffResc'
|
||||
- '@funkybunch'
|
||||
- '@TheOneOgre'
|
||||
ha_domain: sharkiq
|
||||
ha_platforms:
|
||||
- vacuum
|
||||
|
||||
@ -180,7 +180,7 @@ The integration creates a sub-device for every relay (channel) and uses the foll
|
||||
- If a `Device Name` is set in the device, the integration will use it to generate the main device name and entity names assigned to the main device.
|
||||
- If a `Device Name` is not set, the integration will use the `Device ID` to generate the main device name and entity names assigned to the main device.
|
||||
- If a `Channel Name` is set in the device, the integration will use it to generate the sub-device name and entity names assigned to this sub-device (channel/relay).
|
||||
- If a `Channel Name` is set to the default value in the device, the integration will use the device name and this ddefault channel name to generate the sub-device name and entity names assigned to this sub-device (channel/relay).
|
||||
- If a `Channel Name` is set to the default value in the device, the integration will use the device name and this default channel name to generate the sub-device name and entity names assigned to this sub-device (channel/relay).
|
||||
|
||||
Examples:
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@tr4nt0r'
|
||||
ha_domain: sleep_as_android
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- event
|
||||
|
||||
@ -14,7 +14,7 @@ ha_domain: sma
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
|
||||
@ -15,6 +15,7 @@ ha_codeowners:
|
||||
ha_domain: snoo
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- event
|
||||
- select
|
||||
- sensor
|
||||
|
||||
@ -49,19 +49,37 @@ In this section you will find some real-life examples of how to use this integra
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
automation:
|
||||
- alias: "Internet Speed Glow Connect Great"
|
||||
- alias: Turn On Green Light When Download Speed Is Good
|
||||
description: >-
|
||||
This automation turns on the Yeelight bulb with a green color when the
|
||||
download speed exceeds 10 megabits per second.
|
||||
It ensures that the light is an indicator of the health of your
|
||||
network connection.
|
||||
triggers:
|
||||
- trigger: template
|
||||
value_template: "{{ states('sensor.speedtest_download')|float >= 10 }}"
|
||||
value_template: "{{ states('sensor.speedtest_download') | float >= 10 }}"
|
||||
actions:
|
||||
- action: shell_command.green
|
||||
- action: light.turn_on
|
||||
target:
|
||||
entity_id: light.yeelight_bulb
|
||||
data:
|
||||
rgb_color: [0, 100, 0]
|
||||
|
||||
- alias: "Internet Speed Glow Connect Poor"
|
||||
- alias: Turn On Red Light When Download Speed Is Poor
|
||||
description: >-
|
||||
This automation turns on the Yeelight bulb with a red color when the
|
||||
download speed drops below 10 megabits per second.
|
||||
It ensures that the light is an indicator of the health of your
|
||||
network connection.
|
||||
triggers:
|
||||
- trigger: template
|
||||
value_template: "{{ states('sensor.speedtest_download')|float < 10 }}"
|
||||
value_template: "{{ states('sensor.speedtest_download') | float < 10 }}"
|
||||
actions:
|
||||
- action: shell_command.red
|
||||
- action: light.turn_on
|
||||
target:
|
||||
entity_id: light.yeelight_bulb
|
||||
data:
|
||||
rgb_color: [255, 0, 0]
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
@ -20,7 +20,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
- update
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
The Squeezebox integration allows you to control music players from the [Lyrion Music Server](https://lyrion.org/) (LMS) ecosystem. Lyrion Music Server was formerly known as [Logitech Media Server](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29).
|
||||
@ -167,24 +167,22 @@ data:
|
||||
|
||||
## Supported functionality
|
||||
|
||||
The integration provides the following functionality:
|
||||
|
||||
### Switches
|
||||
|
||||
- **Alarm**: Enables a scheduled alarm to sound. Alarms must also be enabled on the associated player for the alarm to sound, using the Alarms Enabled switch or directly on the Lyrion Music Server for that player.
|
||||
- **Alarms Enabled**: Enables a player to sound alarms. Disabling will prevent all alarms from sounding on that player, regardless of whether the individual alarm is enabled
|
||||
- **Alarms Enabled**: Enables a player to sound alarms. Disabling will prevent all alarms from sounding on that player, regardless of whether the individual alarm is enabled.
|
||||
|
||||
### Binary sensors
|
||||
|
||||
The integration provides the following entities.
|
||||
|
||||
#### Binary sensors
|
||||
|
||||
- **Needs restart**
|
||||
- **Description**: Server Service needs to be restarted (typically, this is needed to apply updates).
|
||||
|
||||
- **Library rescan**
|
||||
- **Description**: The music library is currently being scanned by LMS (depending on the type of scan, some content may be unavailable).
|
||||
|
||||
#### Buttons
|
||||
### Buttons
|
||||
|
||||
- **Preset 1 ... Preset 6**
|
||||
- **Description**: Play media stored in Preset 1 to Preset 6 on Squeezebox.
|
||||
@ -201,7 +199,7 @@ The integration provides the following entities.
|
||||
- **Description**: Adjust the treble on Logitech Squeezebox players, such as Radio and Boom.
|
||||
- **Available on**: Logitech hardware players such as Radio, Duet, and Boom.
|
||||
|
||||
#### Sensors
|
||||
### Sensors
|
||||
|
||||
- **Last scan**
|
||||
- **Description**: Date of the last library scan.
|
||||
|
||||
@ -65,7 +65,7 @@ The Starlink integration allows you to integrate your [Starlink](https://www.sta
|
||||
|
||||
### Buttons
|
||||
|
||||
- Reboot - Reboots your Starlink system
|
||||
- Restart - Restart your user terminal
|
||||
|
||||
### Switches
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ha_codeowners:
|
||||
ha_domain: sunricher_dali
|
||||
ha_platforms:
|
||||
- light
|
||||
ha_integration_type: hub
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: bronze
|
||||
related:
|
||||
- url: https://www.sunricher.com/din-rail-ethernet-dali-gateway-sr-gw-eda.html
|
||||
|
||||
@ -76,7 +76,7 @@ command_topic:
|
||||
required: true
|
||||
type: string
|
||||
default_entity_id:
|
||||
description: Use `default_entity_id` instead of name for automatic generation of the entity ID. For example, `swicth.foobar`. When used without a `unique_id`, the entity ID will update during restart or reload if the entity ID is available. If the entity ID already exists, the entity ID will be created with a number at the end. When used with a `unique_id`, the `default_entity_id` is only used when the entity is added for the first time. When set, this overrides a user-customized entity ID if the entity was deleted and added again.
|
||||
description: Use `default_entity_id` instead of name for automatic generation of the entity ID. For example, `switch.foobar`. When used without a `unique_id`, the entity ID will update during restart or reload if the entity ID is available. If the entity ID already exists, the entity ID will be created with a number at the end. When used with a `unique_id`, the `default_entity_id` is only used when the entity is added for the first time. When set, this overrides a user-customized entity ID if the entity was deleted and added again.
|
||||
required: false
|
||||
type: string
|
||||
device:
|
||||
|
||||
@ -22,7 +22,7 @@ ha_iot_standard: matter
|
||||
ha_brand: true
|
||||
---
|
||||
|
||||
{% include integrations/wwha.md url="https://www.switchbot.com/" %}
|
||||
{% include integrations/wwha.md url="https://www.switch-bot.com/" %}
|
||||
|
||||
## Supported devices
|
||||
|
||||
|
||||
@ -22,6 +22,7 @@ ha_platforms:
|
||||
- switch
|
||||
ha_config_flow: true
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: silver
|
||||
---
|
||||
|
||||
This `Switcher` integration allows you to control your [Switcher Devices](https://www.switcher.co.il/).
|
||||
|
||||
@ -25,7 +25,7 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
- update
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: device
|
||||
ha_zeroconf: true
|
||||
---
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ ha_platforms:
|
||||
- switch
|
||||
- water_heater
|
||||
ha_dhcp: true
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
---
|
||||
|
||||
The Tado integration platform is used as an interface to the [my.tado.com](https://my.tado.com/) website.
|
||||
|
||||
@ -19,7 +19,7 @@ ha_config_flow: true
|
||||
related:
|
||||
- docs: /common-tasks/general/#defining-a-custom-polling-interval
|
||||
title: Defining a custom polling interval
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
|
||||
@ -12,6 +12,8 @@ ha_quality_scale: bronze
|
||||
ha_codeowners:
|
||||
- '@hanwg'
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- event
|
||||
- notify
|
||||
---
|
||||
|
||||
|
||||
@ -272,7 +272,7 @@ actions:
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
#### Do something when a device are speeding
|
||||
#### Do something when a device is speeding
|
||||
|
||||
The allows you to do something when the device "Millennium Falcon" exceeds a defined speed.
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@tr4nt0r'
|
||||
ha_domain: uptime_kuma
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: service
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
|
||||
@ -12,6 +12,7 @@ ha_codeowners:
|
||||
ha_domain: vegehub
|
||||
ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- url: https://vegetronix.com/Products/ha/VG-HUB-RELAY/
|
||||
|
||||
@ -18,7 +18,7 @@ ha_platforms:
|
||||
- cover
|
||||
- light
|
||||
- scene
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_codeowners:
|
||||
- '@synesthesiam'
|
||||
- '@jaminh'
|
||||
ha_domain: voip
|
||||
ha_integration_type: integration
|
||||
ha_integration_type: hub
|
||||
ha_quality_scale: internal
|
||||
ha_platforms:
|
||||
- assist_satellite
|
||||
|
||||
@ -16,6 +16,8 @@ ha_category:
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- device_tracker
|
||||
- diagnostics
|
||||
- lock
|
||||
- sensor
|
||||
ha_quality_scale: platinum
|
||||
@ -61,19 +63,26 @@ Features available depend on model, year and location.
|
||||
It's recommended to add an API application per vehicle you want to add. There is a maximum on the number of requests that can be made per API key per day.
|
||||
|
||||
{% note %}
|
||||
Home Assistant will use account linking provided by Nabu Casa for authenticating with Volvo, this service is provided for free and does not require a Nabu Casa subscription.
|
||||
Home Assistant will use account linking provided by Nabu Casa for authenticating with Volvo. This service is **provided for free**, does not require a Nabu Casa subscription, and is the preferred way of using this integration.
|
||||
|
||||
If you want to use your own `client id` and `client secret`, or you have the [cloud integration](/integrations/cloud) disabled, proceed to "**Using custom application credentials**".
|
||||
Read the "**Using custom application credentials**"-section if you have the [cloud integration](/integrations/cloud) disabled.
|
||||
{% endnote %}
|
||||
|
||||
{% details "Using custom application credentials" icon="mdi:account-key" %}
|
||||
|
||||
{% important %}
|
||||
Custom Volvo application credentials have a 6-day grant period, which means you'll need to re-authenticate with Volvo every 6 days.
|
||||
Data updates will stop working once the grant expires until you re-authenticate.
|
||||
|
||||
For a better user experience, it's recommended to use the default Nabu Casa account linking instead.
|
||||
{% endimportant %}
|
||||
|
||||
1. On Volvo's API application page, click the **Publish** button underneath your API application.
|
||||
2. Fill in all required fields in the screen that follows. Pay attention to:
|
||||
- **Scopes**: Make sure to select them all (you need to expand the sections).
|
||||
- **Redirect URI(s)**: Add `https://my.home-assistant.io/redirect/oauth`.
|
||||
3. Click **View summary** and **confirm**.
|
||||
4. Grab the `client id` and `client secret` from the confirmation page and add them to your [application credentials](/integrations/application_credentials).
|
||||
4. Grab the `client id` and `client secret` from the confirmation page and **add them** to your [application credentials](/integrations/application_credentials).
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
|
||||
@ -16,6 +16,7 @@ ha_platforms:
|
||||
- media_player
|
||||
- notify
|
||||
ha_integration_type: integration
|
||||
ha_quality_scale: platinum
|
||||
---
|
||||
|
||||
The `webostv` platform allows you to control a [LG](https://www.lg.com/) webOS TV.
|
||||
|
||||
@ -248,3 +248,10 @@ Here is an example of all of these put together into an automation:
|
||||
data:
|
||||
value: 255
|
||||
```
|
||||
|
||||
|
||||
## Removing the integration
|
||||
|
||||
This integration follows standard integration removal. No extra steps are required.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -14,10 +14,13 @@ ha_domain: xbox
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- image
|
||||
- media_player
|
||||
- remote
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_ssdp: true
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
The **Xbox** {% term integration %} allows you to control Xbox One (or newer) consoles from Home Assistant.
|
||||
|
||||
619
source/_posts/2025-11-05-release-202511.markdown
Normal file
619
source/_posts/2025-11-05-release-202511.markdown
Normal file
@ -0,0 +1,619 @@
|
||||
---
|
||||
layout: post
|
||||
title: "2025.11: Pick, automate, and a slice of pie 🥧"
|
||||
description: "A brand new target picker with full context, redesigned dialog for adding automation blocks, flexible entity naming on dashboard cards, energy pie charts, and progress tracking for Home Assistant and add-on updates!"
|
||||
date: 2025-11-05 00:00:00
|
||||
date_formatted: "November 5, 2025"
|
||||
author: Franck Nijhof
|
||||
author_twitter: frenck
|
||||
comments: true
|
||||
categories:
|
||||
- Release-Notes
|
||||
- Core
|
||||
og_image: /images/blog/2025-11/social.png
|
||||
---
|
||||
|
||||
<lite-youtube videoid="aFsINNDTPjU" videotitle="Home Assistant 2025.11 Release Party"></lite-youtube>
|
||||
|
||||
Home Assistant 2025.11! 🎉
|
||||
|
||||
November is here, and we've been hard at work refining some of the main experiences that you interact with every day, and I think you're going to love what we've built.
|
||||
|
||||
My personal favorite this release? The brand new target picker. 🎯
|
||||
|
||||
It's one of those changes that seems simple on the surface, but makes such a huge difference in how you build automations. You can finally see exactly what you're targeting, with full context about which device an entity belongs to and which area it's in. No more guessing whether you're controlling the right ceiling light when you have three of them!
|
||||
|
||||
But that's just the beginning. We're continuing with the automation editor improvements, this time with a completely redesigned dialog for adding triggers, conditions, and actions. It's cleaner, easier to read, and sets the foundation for some really exciting stuff coming in future releases. 🤫
|
||||
|
||||
And speaking of making things clearer, you can now control exactly how entity names appear on your dashboard cards. Want to show just the entity name? The device name? The area? Or combine them? Even if you rename things, your dashboards will stay perfectly in sync. No more manual updates needed!
|
||||
|
||||
Oh, and energy dashboard fans will appreciate the new pie chart view for device energy, complete with totals displayed in the corner of every energy card. 🥧
|
||||
|
||||
Enjoy the release!
|
||||
|
||||
../Frenck
|
||||
|
||||
PS: Oh, and pssst... Don't tell anyone 🤫, but there might be something exciting being released on November 19th. [Hit the bell on this announced YouTube stream to not miss it](https://www.youtube.com/watch?v=HSRvso6cbf0). Stay tuned! 😀
|
||||
|
||||
<!--more-->
|
||||
|
||||
- [A brand new target picker](#a-brand-new-target-picker)
|
||||
- [A brand new way to add triggers, conditions, and actions in your automations](#a-brand-new-way-to-add-triggers-conditions-and-actions-in-your-automations)
|
||||
- [Naming entities on your dashboard](#naming-entities-on-your-dashboard)
|
||||
- [Energy pie](#energy-pie)
|
||||
- [Progress for Home Assistant and Add-on updates](#progress-for-home-assistant-and-add-on-updates)
|
||||
- [Integrations](#integrations)
|
||||
- [New integrations](#new-integrations)
|
||||
- [Noteworthy improvements to existing integrations](#noteworthy-improvements-to-existing-integrations)
|
||||
- [Now available to set up from the UI](#now-available-to-set-up-from-the-ui)
|
||||
- [Integration quality scale achievements](#integration-quality-scale-achievements)
|
||||
- [Farewell to the following](#farewell-to-the-following)
|
||||
- [Other noteworthy changes](#other-noteworthy-changes)
|
||||
- [Improved logging efficiency](#improved-logging-efficiency)
|
||||
- [The new Home Dashboard keeps getting smarter](#the-new-home-dashboard-keeps-getting-smarter)
|
||||
- [Need help? Join the community](#need-help-join-the-community)
|
||||
- [Backward-incompatible changes](#backward-incompatible-changes)
|
||||
- [All changes](#all-changes)
|
||||
|
||||
_A huge thank you to all the contributors who made this release possible! And a special shout-out to [@bramkragten], [@JLo], [@MindFreeze], [@agners], and [@piitaya] who helped write the release notes this release. Also, [@silamon] and [@GemPolisher] for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️_
|
||||
|
||||
[@agners]: https://github.com/agners
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@GemPolisher]: https://github.com/GemPolisher
|
||||
[@JLo]: https://github.com/jlpouffier
|
||||
[@MindFreeze]: https://github.com/MindFreeze
|
||||
[@piitaya]: https://github.com/piitaya
|
||||
[@silamon]: https://github.com/silamon
|
||||
|
||||
## A brand new target picker
|
||||
|
||||
Have you ever been building an automation and wondered, "Wait, which ceiling light is this?" when you see three entities all named "Ceiling light"? Or tried to figure out how many lights you're actually controlling when you target an entire floor or area?
|
||||
|
||||
We've all been there. Until now, the target picker didn't show you the full picture. You couldn't see which device an entity belonged to or which area it was assigned to. And when you selected a floor or area as your target, you had no idea how many entities you were actually affecting. This uncertainty meant many of you stuck with targeting individual entities, even though larger targets (like areas and floors) can make your automations much more flexible.
|
||||
|
||||
The new target picker changes all that. Now you get full context for everything you're targeting, and you can see exactly how many entities will be affected by your action.
|
||||
|
||||
<img class="no-shadow" alt="Screenshot of a light action configuration with targets picked." src="/images/blog/2025-11/target-picker.png" />
|
||||
|
||||
Want to dig deeper? You can expand any floor, area, or device to see exactly which entities are included and where they're coming from.
|
||||
|
||||
<img class="no-shadow" alt="Screenshot of the details of a target." src="/images/blog/2025-11/target-details.png" />
|
||||
|
||||
This makes it so much easier to build automations that scale with your home. When you target an area or floor, your automation automatically adapts as you add or remove devices. No more updating your automations every time you add a new light or sensor. Your automations just work, which is exactly how it should be.
|
||||
|
||||
## A brand new way to add triggers, conditions, and actions in your automations
|
||||
|
||||
It's no secret that we're currently working hard on making automations easier to create. After the release of the automation sidebar [two releases ago](/blog/2025/09/03/release-20259/#automation-editor-sidebar), we are now introducing a new dialog to add triggers, conditions, and actions.
|
||||
|
||||
The changes are purely cosmetic: the dialog is bigger, so the description of each block is simpler to read, with a two-pane layout to ease both navigation and block selection.
|
||||
|
||||
<img class="no-shadow" alt="Screenshot of the new dialog to add an action." src="/images/blog/2025-11/add-automation-dialog.png" />
|
||||
|
||||
The building blocks (which are used to perform more complex conditions or sequences of actions, such as repeating actions or branching out your sequence into multiple paths) have been moved into the main dialog on a second tab. There is now a single entry point to add something to an automation instead of two, greatly reducing the number of buttons in complex automations.
|
||||
|
||||
<img class="no-shadow" alt="Screenshot of the new dialog to add a building block to an action." src="/images/blog/2025-11/add-automation-dialog-blocks.png" />
|
||||
|
||||
As mentioned above, these changes are purely cosmetic, for now! But this new dialog is the foundation of what’s coming next, and we cannot wait to present that to you once it finally lands.
|
||||
|
||||
## Naming entities on your dashboard
|
||||
|
||||
A few releases ago, we gave the entity picker a big upgrade by adding more context so you could easily see where each entity belongs ([May 2025 release](/blog/2025/05/07/release-20255/#picking-entities)). In this release, we're bringing that same flexibility to your dashboards.
|
||||
|
||||
You can now choose how names appear on your cards: show the entity, device, area, floor, or even combine them. This gives you full control over how your dashboards look and feel. For example, in a dedicated section for a specific device, you might choose to display only the entity name to avoid repeating the device name on every card.
|
||||
|
||||
Of course, you can still set a custom name if you want complete control over the text shown.
|
||||
|
||||
And the best part? If you rename an entity or device, your dashboards will automatically stay in sync. No more manual edits needed; everything just updates itself.
|
||||
|
||||
<img class="no-shadow" alt="Screenshot of the configuration dialog of a tile card." src="/images/blog/2025-11/card-naming.png" />
|
||||
|
||||
## Energy pie
|
||||
|
||||
We've added a new layout to the devices energy graph: "pie" 🥧. You can toggle between the regular bar chart and the new pie chart by clicking the icon in the top-right corner.
|
||||
|
||||
<img class="no-shadow" alt="Screenshot showing the devices energy graph in pie layout." src="/images/blog/2025-11/pie-chart.png" />
|
||||
|
||||
Doing this made the top-right corner of the other energy cards feel empty, so we used that space to display the total energy for the selected period. For example, if the date picker is set to today, the total solar energy for today will be displayed in the corner of the solar production graph card.
|
||||
|
||||
## Progress for Home Assistant and Add-on updates
|
||||
|
||||
With this release, you can now track the progress of updates to Home Assistant and Add-ons (managed by the Supervisor)! The progress includes the stages of downloading and unpacking, so the time required will vary based on your internet speed, CPU performance, and system load. As a result, the progress is not reflected as perfectly linear, but it does still provide a good estimate of how far along the update is.
|
||||
|
||||
<img class="no-shadow" alt="Screen recording showing an add-on update with progress reporting." src="/images/blog/2025-11/supervisor-progress-report.gif" />
|
||||
|
||||
## Integrations
|
||||
|
||||
Thanks to our community for keeping pace with the new {% term integrations %} and improvements to existing ones! You're all awesome. 🥰
|
||||
|
||||
### New integrations
|
||||
|
||||
We welcome the following new integrations in this release:
|
||||
|
||||
- **[Actron Air]**, added by [@kclif9]
|
||||
The Actron Air integration allows you to control Actron Air air conditioning controllers in Home Assistant.
|
||||
|
||||
- **[Sunricher DALI]**, added by [@niracler]
|
||||
Integrate with [Sunricher DALI], a platform for managing and monitoring DALI-based lighting systems.
|
||||
|
||||
- **[Fing]**, added by [@Lorenzo-Gasparini]
|
||||
The [Fing] integration provides network scanning, device detection, and presence monitoring capabilities using the Fing platform.
|
||||
|
||||
- **[Firefly III]**, added by [@erwindouna]
|
||||
Integrate with the [Firefly III project], a free open source personal finance manager with full transaction management, budgets, categories, and reports.
|
||||
|
||||
- **[iNELS]**, added by [@epdevlab]
|
||||
Integrate with the [iNELS] smart home system to manage lighting, heating, and automation components for enhanced home control.
|
||||
|
||||
- **[Lunatone Gateway]**, added by [@MoonDevLT]
|
||||
Integrate with [Lunatone Gateway], enabling control and monitoring of DALI lighting systems through Lunatone's DALI gateway interface.
|
||||
|
||||
- **[Meteo.lt]**, added by [@xE1H]
|
||||
The Meteo.lt integration uses meteorological data from the [Lithuanian Hydrometeorological Service] (LHMT) to provide regional weather forecasts for locations in Lithuania.
|
||||
|
||||
- **[Nintendo Parental Controls]**, added by [@pantherale0]
|
||||
The [Nintendo Parental Controls] integration connects with Nintendo's parental management service, allowing you to monitor and manage device usage and restrictions.
|
||||
|
||||
- **[OpenRGB]**, added by [@felipecrs]
|
||||
The [OpenRGB] integration allows unified control of RGB lighting across various hardware brands and devices through the OpenRGB project.
|
||||
|
||||
[@epdevlab]: https://github.com/epdevlab
|
||||
[@erwindouna]: https://github.com/erwindouna
|
||||
[@felipecrs]: https://github.com/felipecrs
|
||||
[@kclif9]: https://github.com/kclif9
|
||||
[@Lorenzo-Gasparini]: https://github.com/Lorenzo-Gasparini
|
||||
[@MoonDevLT]: https://github.com/MoonDevLT
|
||||
[@niracler]: https://github.com/niracler
|
||||
[@pantherale0]: https://github.com/pantherale0
|
||||
[@xE1H]: https://github.com/xE1H
|
||||
[Actron Air]: /integrations/actron_air
|
||||
[Sunricher DALI]: /integrations/sunricher_dali
|
||||
[Fing]: /integrations/fing
|
||||
[Firefly III project]: https://www.firefly-iii.org/
|
||||
[Firefly III]: /integrations/firefly_iii
|
||||
[iNELS]: /integrations/inels
|
||||
[Lithuanian Hydrometeorological Service]: https://www.meteo.lt/en/
|
||||
[Lunatone Gateway]: /integrations/lunatone
|
||||
[Meteo.lt]: /integrations/meteo_lt
|
||||
[Nintendo Parental Controls]: /integrations/nintendo_parental_controls
|
||||
[OpenRGB]: /integrations/openrgb
|
||||
|
||||
### Noteworthy improvements to existing integrations
|
||||
|
||||
It's not just new {% term integrations %} that have been added; existing integrations are also being constantly improved. Here are some of the noteworthy changes:
|
||||
|
||||
- The [SwitchBot] integration now supports garage door openers. Thanks [@zerzhang]!
|
||||
- [@tr4nt0r] added support for notifications to the [Habitica] integration. Nice work!
|
||||
- The [VegeHub] integration now has support for switches to control actuators. Cool [@Thulrus]!
|
||||
- The [Portainer] integration gained support for switches, buttons, and sensors, so you can control and monitor all your containers! Well done [@erwindouna]!
|
||||
- The [Volvo] integration can now show the location of your car and has buttons to control it. We got [@thomasddn] to thank for that!
|
||||
- [ElevenLabs] can now be used for speech-to-text. Thanks [@ehendrix23]!
|
||||
- You can now control the LEDs of supported [UniFi] network devices! Thanks [@Sese-Schneider]!
|
||||
- [@barneyonline] added binary sensors to the [Yardian] integration. Nice!
|
||||
- You can now set the temperature of your 3D printer's tool and bed with the [OctoPrint] integration. Thanks [@AmadeusW]!
|
||||
- The [Niko Home Control] integration now also adds your scenes into Home Assistant! Thanks [@VandeurenGlenn]!
|
||||
- Your [Control4] climate devices (for example, thermostats) are now supported in Home Assistant. Thanks [@davidrecordon]!
|
||||
- Support for controlling [Growatt] MIN/TLX inverters was added, and you can now enable grid charge! Thanks [@johanzander]!
|
||||
- [@hanwg] added event entities to the [Telegram] bot integration. You can use these entities to more easily automate when you get a message, for example! Cool!
|
||||
- The [Xbox] integration now has support for images! It shows an image of the game you are currently playing, the avatar, and the Gamerpic for yourself and your friends. Thanks [@tr4nt0r]!
|
||||
- [@AndyTempel] added support for solar production forecasting to [Victron Remote Monitoring], so you can now use it in the energy dashboard to see a forecast of how much solar energy you will produce today!
|
||||
- The [Shelly] integration now supports climate and valve entities. Thanks [@thecode]!
|
||||
- [@starkillerOG] improved the [Reolink] integration; it can now report bicycles and the type of person, vehicle, and animal. So you now know if a man or a woman is detected on your cameras. Great work!
|
||||
|
||||
[SwitchBot]: /integrations/switchbot
|
||||
[Habitica]: /integrations/habitica
|
||||
[VegeHub]: /integrations/vegehub
|
||||
[Portainer]: /integrations/portainer
|
||||
[Volvo]: /integrations/volvo
|
||||
[ElevenLabs]: /integrations/elevenlabs
|
||||
[Growatt]: /integrations/growatt_server
|
||||
[UniFi]: /integrations/unifi
|
||||
[Yardian]: /integrations/yardian
|
||||
[OctoPrint]: /integrations/octoprint
|
||||
[Control4]: /integrations/control4
|
||||
[Niko Home Control]: /integrations/niko_home_control
|
||||
[Telegram]: /integrations/telegram_bot
|
||||
[Xbox]: /integrations/xbox
|
||||
[Victron Remote Monitoring]: /integrations/victron_remote_monitoring
|
||||
[Shelly]: /integrations/shelly
|
||||
[Reolink]: /integrations/reolink
|
||||
[@zerzhang]: https://github.com/zerzhang
|
||||
[@AndyTempel]: https://github.com/AndyTempel
|
||||
[@tr4nt0r]: https://github.com/tr4nt0r
|
||||
[@Thulrus]: https://github.com/Thulrus
|
||||
[@erwindouna]: https://github.com/erwindouna
|
||||
[@thomasddn]: https://github.com/thomasddn
|
||||
[@ehendrix23]: https://github.com/ehendrix23
|
||||
[@barneyonline]: https://github.com/barneyonline
|
||||
[@Sese-Schneider]: https://github.com/Sese-Schneider
|
||||
[@AmadeusW]: https://github.com/AmadeusW
|
||||
[@VandeurenGlenn]: https://github.com/VandeurenGlenn
|
||||
[@davidrecordon]: https://github.com/davidrecordon
|
||||
[@johanzander]: https://github.com/johanzander
|
||||
[@hanwg]: https://github.com/hanwg
|
||||
|
||||
### Now available to set up from the UI
|
||||
|
||||
While most {% term integrations %} can be set up directly from the Home Assistant user interface, some were only available using a YAML configuration. We keep moving more integrations to the UI, making them more accessible for everyone to set up and use.
|
||||
|
||||
The following integration is now available via the Home Assistant UI:
|
||||
|
||||
- **[London Underground]** by [@HarvsG]
|
||||
|
||||
[@HarvsG]: https://github.com/HarvsG
|
||||
[London Underground]: /integrations/london_underground
|
||||
|
||||
### Integration quality scale achievements
|
||||
|
||||
One thing we are incredibly proud of in Home Assistant is our [integration quality scale]. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.
|
||||
|
||||
This release, we celebrate several {% term integrations %} that have improved their quality scale:
|
||||
|
||||
- **Seven integrations reached platinum** 🏆
|
||||
- [APC UPS Daemon], thanks to [@yuxincs]
|
||||
- [IMGW-PIB], thanks to [@bieniu]
|
||||
- [LG WebOS TV], thanks to [@thecode]
|
||||
- [Mealie], thanks to [@andrew-codechimp]
|
||||
- [NextDNS], thanks to [@bieniu]
|
||||
- [ntfy], thanks to [@tr4nt0r]
|
||||
- [Volvo], thanks to [@thomasddn]
|
||||
|
||||
- **Four integrations reached silver** 🥈
|
||||
- [1-wire], thanks to [@epenet]
|
||||
- [Ubiquiti airOS], thanks to [@CoMPaTech]
|
||||
- [LetPot], thanks to [@jpelgrom]
|
||||
- [Switcher], thanks to [@thecode]
|
||||
|
||||
This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.
|
||||
|
||||
A big thank you to all the contributors involved! 👏
|
||||
|
||||
[integration quality scale]: /docs/quality_scale/
|
||||
|
||||
[@andrew-codechimp]: https://github.com/andrew-codechimp
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@CoMPaTech]: https://github.com/CoMPaTech
|
||||
[@epenet]: https://github.com/epenet
|
||||
[@jpelgrom]: https://github.com/jpelgrom
|
||||
[@thecode]: https://github.com/thecode
|
||||
[@thomasddn]: https://github.com/thomasddn
|
||||
[@tr4nt0r]: https://github.com/tr4nt0r
|
||||
[@yuxincs]: https://github.com/yuxincs
|
||||
[1-wire]: /integrations/onewire
|
||||
[Ubiquiti airOS]: /integrations/airos
|
||||
[APC UPS Daemon]: /integrations/apcupsd
|
||||
[IMGW-PIB]: /integrations/imgw_pib
|
||||
[LetPot]: /integrations/letpot
|
||||
[LG WebOS TV]: /integrations/webostv
|
||||
[Mealie]: /integrations/mealie
|
||||
[NextDNS]: /integrations/nextdns
|
||||
[ntfy]: /integrations/ntfy
|
||||
[Switcher]: /integrations/switcher
|
||||
[Volvo]: /integrations/volvo
|
||||
|
||||
### Farewell to the following
|
||||
|
||||
The following {% term integrations %} are no longer available as of this release:
|
||||
|
||||
- **Vultr** has been removed. The integration has not been working since the API v1 that it used was taken offline in September 2023.
|
||||
- **IBM Watson IoT Platform** has been removed. On September 8, 2020, IBM announced the withdrawal of its support for the IBM Watson IoT Platform and successively discontinued all versions until September 30, 2022.
|
||||
- **Plum Lightpad** has been removed. Their servers have been shut down, which made the integration non-functional.
|
||||
|
||||
## Other noteworthy changes
|
||||
|
||||
There are many more improvements in this release; here are some of the other noteworthy changes:
|
||||
|
||||
- [@thecode] added [group] support for valves, so you can group multiple valves into one.
|
||||
- Searching in data tables got a lot better; you can now search over multiple columns at once. Thanks [@wendevlin]!
|
||||
- Energy graphs now show the total of the period in the top-right corner. Great addition, [@MindFreeze]!
|
||||
- Thanks to [@karwosts], you can now use images from any integration providing images for your dashboard background.
|
||||
|
||||
[@karwosts]: https://github.com/karwosts
|
||||
[@wendevlin]: https://github.com/wendevlin
|
||||
[group]: /integrations/group
|
||||
|
||||
### Improved logging efficiency
|
||||
|
||||
If you're using the Home Assistant Operating System, we have some great news for you! We've made our logging system way more efficient. 🚀
|
||||
|
||||
You might not realize it, but all those Home Assistant logs you can find in **Settings** > **System** > **Logs** were actually being stored on your disk twice. 🙈
|
||||
|
||||
Home Assistant OS keeps all logs for everything, including Home Assistant itself, in a very efficient way, even across restarts! But on top of that, we were also writing them to a log file in your Home Assistant configuration folder.
|
||||
|
||||
That's not ideal. It takes twice the disk space, but more importantly, it causes unnecessary wear on your storage medium, which means it will fail sooner. This is especially concerning if you're using an SD card in, for example, a Raspberry Pi.
|
||||
|
||||
As of this release, we've stopped writing logs to the configuration folder. You can still view and download all logs from the Home Assistant settings page, just like before. We've adapted that page to read the logs from the OS directly instead.
|
||||
|
||||
{% tip %}
|
||||
Are you more into the command line? No worries, our Home Assistant CLI has you covered. Check it out by running `ha core logs --help` for more information.
|
||||
{% endtip %}
|
||||
|
||||
### The new Home Dashboard keeps getting smarter
|
||||
|
||||
Following the improvements introduced in the latest releases, this release makes the experience even smoother and more intuitive.
|
||||
|
||||
We've simplified and reorganized things:
|
||||
|
||||
- Suggested entities and favorites are now combined into a single, smart section, showing you what's most relevant in one place.
|
||||
- Areas are now grouped by floor, making it easier to browse and understand your home's layout at a glance.
|
||||
- The Lights, Climate, and Security views have been moved to their own dedicated dashboards, so you can access them directly under **Settings** > **Dashboards**. These dashboards now also include devices that aren't assigned to any specific area, ensuring nothing is overlooked.
|
||||
|
||||
These improvements bring everything together more naturally, helping your Home Dashboard feel less like a setup and more like a true reflection of your home.
|
||||
|
||||
<img class="no-shadow" alt="New built-in dashboards in dashboards config panel" src="/images/blog/2025-11/config-dashboards.png" />
|
||||
|
||||
## 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, 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 on more places you can go.
|
||||
|
||||
Are you more into email? [Sign up for the Open Home Foundation Newsletter](/newsletter) to get the latest on features, things happening in our community, and other projects that support the Open Home straight into your inbox.
|
||||
|
||||
## Backward-incompatible changes
|
||||
|
||||
We do our best to avoid making changes to existing functionality that might unexpectedly impact your Home Assistant installation. Unfortunately, sometimes, it is inevitable.
|
||||
|
||||
We always make sure to document these changes to make the transition as easy as possible for you. This release has the following backward-incompatible changes:
|
||||
|
||||
---
|
||||
|
||||
{% details "Set assumed state to group if at least one child has assumed state" %}
|
||||
|
||||
Previously, the group’s assumed state was always false, regardless of the state of its child entities.
|
||||
|
||||
This has now changed:
|
||||
|
||||
The group will now have an assumed state of `true` if at least one child entity has an assumed state.
|
||||
This makes the group's assumed state reflect the uncertainty of its children more accurately.
|
||||
These domains have been added: switch, fan, light, and cover.
|
||||
|
||||
([@piitaya] - [#154163]) ([group docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Asuswrt" %}
|
||||
|
||||
The `last_time_reachable` attribute has been removed from the `asuswrt` device tracker.
|
||||
Use the `last_changed` attribute instead in your automations.
|
||||
|
||||
([@ollo69] - [#154219]) ([asuswrt docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "LG webOS TV" %}
|
||||
|
||||
The state of LG webOS TV media player entities that do not have an automation trigger to turn on the device will be set to `unavailable` instead of `off`.
|
||||
|
||||
([@thecode] - [#155164]) ([webostv docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Mealie" %}
|
||||
|
||||
The `mealie` integration now requires Mealie version 2 or later.
|
||||
|
||||
Mealie version 1 is no longer supported. Version 2 was released in October 2024, so over a year ago. Given the differences between versions 1 and 2, we are no longer able to support or test backward compatibility with version 1.
|
||||
|
||||
([@andrew-codechimp] - [#153203]) ([mealie docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Motion Blinds" %}
|
||||
|
||||
The tilt position of `motion_blinds` devices has been corrected to align with the Home Assistant standards.
|
||||
The new tilt position will be: 0 = closed/covering the window opening, 100 = open/letting light through.
|
||||
The previous tilt position can be converted to the new tilt position as follows:
|
||||
|
||||
- `new` = `100 - old`
|
||||
- `current_tilt_position` = `100 -> 0`
|
||||
- `current_tilt_position` = `75 -> 25`
|
||||
- `current_tilt_position` = `50 -> 50`
|
||||
- `current_tilt_position` = `25 -> 75`
|
||||
- `current_tilt_position` = `0 -> 100`
|
||||
- `open_cover_tilt` -> `close_cover_tilt`
|
||||
- `close_cover_tilt` -> `open_cover_tilt`
|
||||
|
||||
Any automations concerning Motion Blinds devices that use the `current_tilt_position` attribute or use tilt open/close will need to be adjusted.
|
||||
|
||||
([@starkillerOG] - [#149777]) ([motion_blinds docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Mobile app" %}
|
||||
|
||||
The `mobile_app` integration, which supports the iPhone and Android companion apps, now handles zone-only updates better. When your companion app sends just the zone name (not the exact coordinates), the device tracker will show the zone's friendly name.
|
||||
|
||||
The `person` entity now shows the zone's friendly name (not its object ID) for custom zones. This might break existing automations that trigger on a person's state.
|
||||
|
||||
As an example, if you have a zone named `zone.kids_school` with the friendly name `School`:
|
||||
|
||||
- **Before** this change, the state of the corresponding `person` and `device_tracker` entities would be `kids_school` when the "Location Sent" in the companion app was set to send "Zone Name Only" and `School` when it was set to "Exact".
|
||||
- **After** this change, the state of the corresponding `person` and `device_tracker` entities will be `School` for both the "Location Sent" settings in the companion app.
|
||||
|
||||
([@Ashus] - [#149453]) ([mobile_app docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Nederlandse Spoorwegen" %}
|
||||
|
||||
The Nederlandse Spoorwegen entity is now displayed as a timestamp entity, rather than a string. Please adapt your automations and scripts.
|
||||
|
||||
([@joostlek] - [#154011]) ([nederlandse_spoorwegen docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ONVIF" %}
|
||||
|
||||
The `Speed` parameter in the ONVIF `GoToPreset` action is now optional.
|
||||
|
||||
The default of `0.5` is no longer set. If you want to restore the previous behavior you have to set `speed` to `0.5` in your action.
|
||||
|
||||
([@carlos-sarmiento] - [#149636]) ([onvif docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "OralB" %}
|
||||
|
||||
In the OralB integration, states and attributes have changed.
|
||||
|
||||
In multiple places, spaces have been replaced with underscores:
|
||||
|
||||
- Toothbrush state:
|
||||
|
||||
- `flight menu` → `flight_menu`
|
||||
- `selection menu` → `selection_menu`
|
||||
- `final test` → `final_test`
|
||||
- `pcb test` → `pcb_test`
|
||||
|
||||
- Brushing mode:
|
||||
|
||||
- `daily clean` → `daily_clean`
|
||||
- `gum care` → `gum_care`
|
||||
- `tongue cleaning` → `tongue_cleaning`
|
||||
- `super sensitive` → `super_sensitive`
|
||||
- `deep clean` → `deep_clean`
|
||||
|
||||
- Pressure:
|
||||
|
||||
- `power button pressed` → `power_button_pressed`
|
||||
- `button pressed` → `button_pressed`
|
||||
|
||||
- Sector:
|
||||
|
||||
- `no sector` → `no_sector`
|
||||
- `sector 1` → `sector_1`
|
||||
- `sector 2` → `sector_2`
|
||||
- `sector 3` → `sector_3`
|
||||
- `sector 4` → `sector_4`
|
||||
|
||||
Automations should be updated to use the new states and attributes.
|
||||
|
||||
([@tr4nt0r] - [#153605]) ([oralb docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Renault" %}
|
||||
|
||||
The discovery of Renault functionality was previously based on assumptions that may have created invalid and non-functional entities.
|
||||
These will no longer be created.
|
||||
|
||||
([@epenet] - [#154137]) ([renault docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Traccar Server" %}
|
||||
|
||||
The Traccar integration has been updated to use a more secure API Token for authentication. This is a required, one-time breaking change to align with Traccar's security recommendations and ensure the integration continues to work.
|
||||
|
||||
This release migrates the integration away from the older username/password method, ensuring continued stability and security for all users while also allowing users with SSO-based setups to use the integration.
|
||||
|
||||
When you update Home Assistant, the existing Traccar integration will need to be re-authenticated:
|
||||
|
||||
1. Generate an API Token on your Traccar server (you'll find this option in your Traccar server's user settings).
|
||||
2. Go to **Settings** > **Devices & Services** > **Traccar Server**.
|
||||
3. Click "Reconfigure" and enter your new API Token when prompted.
|
||||
|
||||
Once you've done this, your Traccar devices and entities will work exactly as they did before.
|
||||
|
||||
([@pantherale0] - [#155297]) ([traccar_server docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Xbox" %}
|
||||
|
||||
The `Account tier` and `Gold tenure` sensors have been retired, as they no longer receive updates following the transition from Xbox Live Gold to Xbox Game Pass. Additionally, the `In party` and `In multiplayer` binary sensors have been removed, since they’ve been non-functional for quite some time.
|
||||
|
||||
([@tr4nt0r] - [#154891]) ([xbox docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
[@abmantis]: https://github.com/abmantis
|
||||
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||
[@mib1185]: https://github.com/mib1185
|
||||
[@tr4nt0r]: https://github.com/tr4nt0r
|
||||
[@andrew-codechimp]: https://github.com/andrew-codechimp
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@joostlek]: https://github.com/joostlek
|
||||
[@flabbamann]: https://github.com/flabbamann
|
||||
[@epenet]: https://github.com/epenet
|
||||
[@ollo69]: https://github.com/ollo69
|
||||
[@piitaya]: https://github.com/piitaya
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@Ashus]: https://github.com/Ashus
|
||||
[@carlos-sarmiento]: https://github.com/carlos-sarmiento
|
||||
[@thecode]: https://github.com/thecode
|
||||
[@pantherale0]: https://github.com/pantherale0
|
||||
[#146675]: https://github.com/home-assistant/core/pull/146675
|
||||
[#153367]: https://github.com/home-assistant/core/pull/153367
|
||||
[#153366]: https://github.com/home-assistant/core/pull/153366
|
||||
[#153363]: https://github.com/home-assistant/core/pull/153363
|
||||
[#153364]: https://github.com/home-assistant/core/pull/153364
|
||||
[#153560]: https://github.com/home-assistant/core/pull/153560
|
||||
[#153567]: https://github.com/home-assistant/core/pull/153567
|
||||
[#153605]: https://github.com/home-assistant/core/pull/153605
|
||||
[#153590]: https://github.com/home-assistant/core/pull/153590
|
||||
[#153472]: https://github.com/home-assistant/core/pull/153472
|
||||
[#153203]: https://github.com/home-assistant/core/pull/153203
|
||||
[#153370]: https://github.com/home-assistant/core/pull/153370
|
||||
[#149777]: https://github.com/home-assistant/core/pull/149777
|
||||
[#153473]: https://github.com/home-assistant/core/pull/153473
|
||||
[#154011]: https://github.com/home-assistant/core/pull/154011
|
||||
[#154037]: https://github.com/home-assistant/core/pull/154037
|
||||
[#154038]: https://github.com/home-assistant/core/pull/154038
|
||||
[#154152]: https://github.com/home-assistant/core/pull/154152
|
||||
[#154112]: https://github.com/home-assistant/core/pull/154112
|
||||
[#154137]: https://github.com/home-assistant/core/pull/154137
|
||||
[#154114]: https://github.com/home-assistant/core/pull/154114
|
||||
[#154219]: https://github.com/home-assistant/core/pull/154219
|
||||
[#154163]: https://github.com/home-assistant/core/pull/154163
|
||||
[#153939]: https://github.com/home-assistant/core/pull/153939
|
||||
[#149453]: https://github.com/home-assistant/core/pull/149453
|
||||
[#149636]: https://github.com/home-assistant/core/pull/149636
|
||||
[#154035]: https://github.com/home-assistant/core/pull/154035
|
||||
[#155164]: https://github.com/home-assistant/core/pull/155164
|
||||
[#155263]: https://github.com/home-assistant/core/pull/155263
|
||||
[#154902]: https://github.com/home-assistant/core/pull/154902
|
||||
[#155297]: https://github.com/home-assistant/core/pull/155297
|
||||
[#154891]: https://github.com/home-assistant/core/pull/154891
|
||||
|
||||
[lock docs]: /integrations/lock/
|
||||
[media_player docs]: /integrations/media_player/
|
||||
[camera docs]: /integrations/camera/
|
||||
[vacuum docs]: /integrations/vacuum/
|
||||
[vultr docs]: /integrations/vultr/
|
||||
[watson_iot docs]: /integrations/watson_iot/
|
||||
[oralb docs]: /integrations/oralb/
|
||||
[plum_lightpad docs]: /integrations/plum_lightpad/
|
||||
[mealie docs]: /integrations/mealie/
|
||||
[motion_blinds docs]: /integrations/motion_blinds/
|
||||
[nederlandse_spoorwegen docs]: /integrations/nederlandse_spoorwegen/
|
||||
[cover docs]: /integrations/cover/
|
||||
[alarm_control_panel docs]: /integrations/alarm_control_panel/
|
||||
[fritzbox docs]: /integrations/fritzbox/
|
||||
[renault docs]: /integrations/renault/
|
||||
[asuswrt docs]: /integrations/asuswrt/
|
||||
[group docs]: /integrations/group/
|
||||
[mobile_app docs]: /integrations/mobile_app/
|
||||
[onvif docs]: /integrations/onvif/
|
||||
[webostv docs]: /integrations/webostv/
|
||||
[neato docs]: /integrations/neato/
|
||||
[homeassistant_alerts docs]: /integrations/homeassistant_alerts/
|
||||
[analytics_insights docs]: /integrations/analytics_insights/
|
||||
[traccar_server docs]: /integrations/traccar_server/
|
||||
[xbox docs]: /integrations/xbox/
|
||||
|
||||
If you are a custom integration developer and want to learn about changes and new features available for your integration, be sure to follow our [developer blog][devblog]. The following changes are the most notable for this release:
|
||||
|
||||
- [Changes to the recorder statistics API](https://developers.home-assistant.io/blog/2025/10/16/recorder-statistics-api-changes)
|
||||
- [Device filter has been removed from target selector](https://developers.home-assistant.io/blog/2025/10/14/device-filter-removed-from-target-selector)
|
||||
- [Service translations removed from WebSocket get_services and REST /api/services](https://developers.home-assistant.io/blog/2025/10/24/service-web-api-changes)
|
||||
- [TemperatureConverter.convert_interval deprecation](https://developers.home-assistant.io/blog/2025/11/04/convert-interval-deprecation/)
|
||||
- [Update coordinator now allows retriggering](https://developers.home-assistant.io/blog/2025/10/05/coordinator-retrigger)
|
||||
|
||||
[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 here: [Full changelog for Home Assistant Core 2025.11](/changelogs/core-2025.11)
|
||||
2251
source/changelogs/core-2025.11.markdown
Normal file
2251
source/changelogs/core-2025.11.markdown
Normal file
File diff suppressed because it is too large
Load Diff
BIN
source/images/blog/2025-11/add-automation-dialog-blocks.png
Normal file
BIN
source/images/blog/2025-11/add-automation-dialog-blocks.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 277 KiB |
BIN
source/images/blog/2025-11/add-automation-dialog.png
Normal file
BIN
source/images/blog/2025-11/add-automation-dialog.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 261 KiB |
BIN
source/images/blog/2025-11/card-naming.png
Normal file
BIN
source/images/blog/2025-11/card-naming.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 202 KiB |
BIN
source/images/blog/2025-11/config-dashboards.png
Normal file
BIN
source/images/blog/2025-11/config-dashboards.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 696 KiB |
BIN
source/images/blog/2025-11/pie-chart.png
Normal file
BIN
source/images/blog/2025-11/pie-chart.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
BIN
source/images/blog/2025-11/social.png
Normal file
BIN
source/images/blog/2025-11/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 316 KiB |
BIN
source/images/blog/2025-11/supervisor-progress-report.gif
Normal file
BIN
source/images/blog/2025-11/supervisor-progress-report.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 277 KiB |
BIN
source/images/blog/2025-11/target-details.png
Normal file
BIN
source/images/blog/2025-11/target-details.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 475 KiB |
BIN
source/images/blog/2025-11/target-picker.png
Normal file
BIN
source/images/blog/2025-11/target-picker.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 390 KiB |
BIN
source/images/frontpage/feature-nov19.webp
Normal file
BIN
source/images/frontpage/feature-nov19.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Loading…
x
Reference in New Issue
Block a user