Merge branch 'current' into next

.github/workflows/test.yml

@@ -8,7 +8,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out files from GitHub
-        uses: actions/checkout@v3.1.0
+        uses: actions/checkout@v3.2.0
       - name: Setting up Node.js
         uses: actions/setup-node@v3.5.1
         with:
@@ -25,7 +25,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out files from GitHub
-        uses: actions/checkout@v3.1.0
+        uses: actions/checkout@v3.2.0
       - name: Setting up Node.js
         uses: actions/setup-node@v3.5.1
         with:

CODEOWNERS

@@ -20,14 +20,16 @@ source/_integrations/agent_dvr.markdown @ispysoftware
 source/_integrations/air_quality.markdown @home-assistant/core
 source/_integrations/airly.markdown @bieniu
 source/_integrations/airnow.markdown @asymworks
+source/_integrations/airq.markdown @Sibgatulin @dl2080
 source/_integrations/airthings.markdown @danielhiversen
+source/_integrations/airthings_ble.markdown @vincegio
 source/_integrations/airtouch4.markdown @LonePurpleWolf
 source/_integrations/airvisual.markdown @bachya
 source/_integrations/airzone.markdown @Noltari
 source/_integrations/aladdin_connect.markdown @mkmer
 source/_integrations/alarm_control_panel.markdown @home-assistant/core
-source/_integrations/alert.markdown @home-assistant/core
+source/_integrations/alert.markdown @home-assistant/core @frenck
-source/_integrations/alexa.markdown @home-assistant/cloud @ochlocracy
+source/_integrations/alexa.markdown @home-assistant/cloud @ochlocracy @jbouwh
 source/_integrations/alexa.smart_home.markdown @home-assistant/cloud @ochlocracy
 source/_integrations/almond.markdown @gcampax @balloob
 source/_integrations/amberelectric.markdown @madpilot
@@ -46,6 +48,7 @@ source/_integrations/apple_tv.markdown @postlund
 source/_integrations/application_credentials.markdown @home-assistant/core
 source/_integrations/apprise.markdown @caronc
 source/_integrations/aprs.markdown @PhilRW
+source/_integrations/aranet.markdown @aschmitz
 source/_integrations/arcam_fmj.markdown @elupus
 source/_integrations/arris_tg2492lg.markdown @vanbalken
 source/_integrations/aseko_pool_live.markdown @milanmeu
@@ -84,6 +87,7 @@ source/_integrations/bluetooth.markdown @bdraco
 source/_integrations/bmw_connected_drive.markdown @gerard33 @rikroe
 source/_integrations/bond.markdown @bdraco @prystupa @joshs85 @marciogranzotto
 source/_integrations/bosch_shc.markdown @tschamm
+source/_integrations/brandt.markdown @imicknl @vlebourl @tetienne
 source/_integrations/braviatv.markdown @bieniu @Drafteed
 source/_integrations/brel_home.markdown @starkillerOG
 source/_integrations/broadlink.markdown @danielhiversen @felipediel @L-I-Am
@@ -91,7 +95,7 @@ source/_integrations/brother.markdown @bieniu
 source/_integrations/brunt.markdown @eavanvalkenburg
 source/_integrations/bsblan.markdown @liudger
 source/_integrations/bswitch.markdown @jafar-atili
-source/_integrations/bt_smarthub.markdown @jxwolstenholme
+source/_integrations/bt_smarthub.markdown @typhoon2099
 source/_integrations/bthome.markdown @Ernst79
 source/_integrations/bticino.markdown @cgtobi
 source/_integrations/bubendorff.markdown @cgtobi
@@ -142,6 +146,7 @@ source/_integrations/devolo_home_network.markdown @2Fake @Shutgun
 source/_integrations/dexcom.markdown @gagebenne
 source/_integrations/dhcp.markdown @bdraco
 source/_integrations/diagnostics.markdown @home-assistant/core
+source/_integrations/diaz.markdown @starkillerOG
 source/_integrations/digital_loggers.markdown @esev
 source/_integrations/digital_ocean.markdown @fabaff
 source/_integrations/discogs.markdown @thibmaek
@@ -161,7 +166,6 @@ source/_integrations/ecobee.markdown @marthoc
 source/_integrations/econet.markdown @vangorra @w1ll1am23
 source/_integrations/ecovacs.markdown @OverloadUT @mib1185
 source/_integrations/ecowitt.markdown @pvizeli
-source/_integrations/edl21.markdown @mtdcr
 source/_integrations/efergy.markdown @tkdrob
 source/_integrations/egardia.markdown @jeroenterheerdt
 source/_integrations/eight_sleep.markdown @mezz64 @raman325
@@ -255,10 +259,13 @@ source/_integrations/habitica.markdown @ASMfreaK @leikoilja
 source/_integrations/hardware.markdown @home-assistant/core
 source/_integrations/harmony.markdown @ehendrix23 @bramkragten @bdraco @mkeesey @Aohzan
 source/_integrations/hassio.markdown @home-assistant/supervisor
+source/_integrations/havana_shade.markdown @starkillerOG
 source/_integrations/hdmi_cec.markdown @inytar
 source/_integrations/heatmiser.markdown @andylockran
+source/_integrations/heiwa.markdown @cmroche
 source/_integrations/heos.markdown @andrewsayre
 source/_integrations/here_travel_time.markdown @eifinger
+source/_integrations/hexaom.markdown @imicknl @vlebourl @tetienne
 source/_integrations/hi_kumo.markdown @imicknl @vlebourl @tetienne
 source/_integrations/hikvision.markdown @mezz64
 source/_integrations/hikvisioncam.markdown @fbradyirl
@@ -270,6 +277,7 @@ source/_integrations/home_connect.markdown @DavidMStraub
 source/_integrations/home_plus_control.markdown @chemaaa
 source/_integrations/homeassistant.markdown @home-assistant/core
 source/_integrations/homeassistant_alerts.markdown @home-assistant/core
+source/_integrations/homeassistant_hardware.markdown @home-assistant/core
 source/_integrations/homekit.markdown @bdraco
 source/_integrations/homekit_controller.markdown @Jc2k @bdraco
 source/_integrations/homematic.markdown @pvizeli @danielperna84
@@ -302,6 +310,7 @@ source/_integrations/input_datetime.markdown @home-assistant/core
 source/_integrations/input_number.markdown @home-assistant/core
 source/_integrations/input_select.markdown @home-assistant/core
 source/_integrations/input_text.markdown @home-assistant/core
+source/_integrations/inspired_shades.markdown @starkillerOG
 source/_integrations/insteon.markdown @teharris1
 source/_integrations/integration.markdown @dgomes
 source/_integrations/intellifire.markdown @jeeftor
@@ -317,7 +326,7 @@ source/_integrations/ismartwindow.markdown @starkillerOG
 source/_integrations/iss.markdown @DurgNomis-drol
 source/_integrations/isy994.markdown @bdraco @shbatm
 source/_integrations/izone.markdown @Swamp-Ig
-source/_integrations/jellyfin.markdown @j-stienstra
+source/_integrations/jellyfin.markdown @j-stienstra @ctalkington
 source/_integrations/jewish_calendar.markdown @tsvi
 source/_integrations/juicenet.markdown @jesserockz
 source/_integrations/justnimbus.markdown @kvanzuijlen
@@ -337,7 +346,7 @@ source/_integrations/kostal_plenticore.markdown @stegm
 source/_integrations/kraken.markdown @eifinger
 source/_integrations/kulersky.markdown @emlove
 source/_integrations/lacrosse_view.markdown @IceBotYT
-source/_integrations/lametric.markdown @robbiet480 @frenck
+source/_integrations/lametric.markdown @robbiet480 @frenck @bachya
 source/_integrations/landisgyr_heat_meter.markdown @vpathuis
 source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol
 source/_integrations/laundrify.markdown @xLarry
@@ -353,6 +362,8 @@ source/_integrations/light.markdown @home-assistant/core
 source/_integrations/linux_battery.markdown @fabaff
 source/_integrations/litejet.markdown @joncar
 source/_integrations/litterrobot.markdown @natekspencer @tkdrob
+source/_integrations/livisi.markdown @StefanIacobLivisi
+source/_integrations/local_calendar.markdown @allenporter
 source/_integrations/local_ip.markdown @issacg
 source/_integrations/lock.markdown @home-assistant/core
 source/_integrations/logbook.markdown @home-assistant/core
@@ -362,7 +373,7 @@ source/_integrations/lookin.markdown @ANMalko @bdraco
 source/_integrations/luci.markdown @mzdrale
 source/_integrations/luftdaten.markdown @fabaff @frenck
 source/_integrations/lupusec.markdown @majuss
-source/_integrations/lutron.markdown @JonGilmore
+source/_integrations/lutron.markdown @cdheiser
 source/_integrations/lutron_caseta.markdown @swails @bdraco @danaues
 source/_integrations/luxaflex.markdown @bdraco @kingy444 @trullock
 source/_integrations/lyric.markdown @timmo001
@@ -386,7 +397,7 @@ source/_integrations/meteoclimatic.markdown @adrianmo
 source/_integrations/metoffice.markdown @MrHarcombe @avee87
 source/_integrations/mikrotik.markdown @engrbm87
 source/_integrations/mill.markdown @danielhiversen
-source/_integrations/min_max.markdown @fabaff
+source/_integrations/min_max.markdown @gjohansson-ST
 source/_integrations/minecraft_server.markdown @elmurato
 source/_integrations/minio.markdown @tkislan
 source/_integrations/moat.markdown @bdraco
@@ -399,7 +410,7 @@ source/_integrations/monoprice.markdown @etsinko @OnFreund
 source/_integrations/moon.markdown @fabaff @frenck
 source/_integrations/motion_blinds.markdown @starkillerOG
 source/_integrations/motioneye.markdown @dermotduffy
-source/_integrations/mqtt.markdown @emontnemery
+source/_integrations/mqtt.markdown @emontnemery @jbouwh
 source/_integrations/msteams.markdown @peroyvind
 source/_integrations/mullvad.markdown @meichthys
 source/_integrations/mutesync.markdown @currentoor
@@ -436,6 +447,7 @@ source/_integrations/notify_events.markdown @matrozov @papajojo
 source/_integrations/notion.markdown @bachya
 source/_integrations/nsw_fuel_station.markdown @nickw444
 source/_integrations/nsw_rural_fire_service_feed.markdown @exxamalte
+source/_integrations/nuheat.markdown @tstabrawa
 source/_integrations/nuki.markdown @pschmitt @pvizeli @pree
 source/_integrations/numato.markdown @clssn
 source/_integrations/number.markdown @home-assistant/core @Shulyaka
@@ -449,7 +461,7 @@ source/_integrations/ohmconnect.markdown @robbiet480
 source/_integrations/ombi.markdown @larssont
 source/_integrations/omnilogic.markdown @oliver84 @djtimca @gentoosu
 source/_integrations/onboarding.markdown @home-assistant/core
-source/_integrations/oncue.markdown @bdraco
+source/_integrations/oncue.markdown @bdraco @peterager
 source/_integrations/ondilo_ico.markdown @JeromeHXP
 source/_integrations/onewire.markdown @garbled1 @epenet
 source/_integrations/onvif.markdown @hunterjm
@@ -462,12 +474,14 @@ source/_integrations/opentherm_gw.markdown @mvn23
 source/_integrations/openuv.markdown @bachya
 source/_integrations/openweathermap.markdown @fabaff @freekode @nzapponi
 source/_integrations/opnsense.markdown @mtreinish
+source/_integrations/oralb.markdown @bdraco
 source/_integrations/oru.markdown @bvlaicu
 source/_integrations/overkiz.markdown @imicknl @vlebourl @tetienne
 source/_integrations/ovo_energy.markdown @timmo001
 source/_integrations/p1_monitor.markdown @klaasnicolaas
 source/_integrations/panel_custom.markdown @home-assistant/frontend
 source/_integrations/panel_iframe.markdown @home-assistant/frontend
+source/_integrations/pcs_lighting.markdown @gwww
 source/_integrations/peco.markdown @IceBotYT
 source/_integrations/persistent_notification.markdown @home-assistant/core
 source/_integrations/philips_js.markdown @elupus
@@ -490,6 +504,7 @@ source/_integrations/prusalink.markdown @balloob
 source/_integrations/ps4.markdown @ktnrg45
 source/_integrations/pure_energie.markdown @klaasnicolaas
 source/_integrations/push.markdown @dgomes
+source/_integrations/pushbullet.markdown @engrbm87
 source/_integrations/pushover.markdown @engrbm87
 source/_integrations/pvoutput.markdown @frenck
 source/_integrations/pvpc_hourly_pricing.markdown @azogue
@@ -523,10 +538,10 @@ source/_integrations/rflink.markdown @javicalle
 source/_integrations/rfxtrx.markdown @danielhiversen @elupus @RobBie1221
 source/_integrations/rhasspy.markdown @balloob @synesthesiam
 source/_integrations/ridwell.markdown @bachya
-source/_integrations/ring.markdown @balloob
 source/_integrations/risco.markdown @OnFreund
 source/_integrations/rituals_perfume_genie.markdown @milanmeu
 source/_integrations/rmvtransport.markdown @cgtobi
+source/_integrations/roborock.markdown @rytilahti @syssi @starkillerOG
 source/_integrations/roku.markdown @ctalkington
 source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn
 source/_integrations/roon.markdown @pavoni
@@ -534,6 +549,7 @@ source/_integrations/rpi_power.markdown @shenxn @swetoast
 source/_integrations/rss_feed_template.markdown @home-assistant/core
 source/_integrations/rtsp_to_webrtc.markdown @allenporter
 source/_integrations/ruckus_unleashed.markdown @gabe565
+source/_integrations/ruuvitag_ble.markdown @akx
 source/_integrations/sabnzbd.markdown @shaiu
 source/_integrations/safe_mode.markdown @home-assistant/core
 source/_integrations/saj.markdown @fredericvl
@@ -541,7 +557,8 @@ source/_integrations/samsungtv.markdown @chemelli74 @epenet
 source/_integrations/scene.markdown @home-assistant/core
 source/_integrations/schedule.markdown @home-assistant/core
 source/_integrations/schluter.markdown @prairieapps
-source/_integrations/scrape.markdown @fabaff
+source/_integrations/scrape.markdown @fabaff @gjohansson-ST @epenet
+source/_integrations/screenaway.markdown @starkillerOG
 source/_integrations/screenlogic.markdown @dieselrabbit @bdraco
 source/_integrations/script.markdown @home-assistant/core
 source/_integrations/search.markdown @home-assistant/core
@@ -550,6 +567,7 @@ source/_integrations/select.markdown @home-assistant/core
 source/_integrations/sense.markdown @kbickar
 source/_integrations/senseme.markdown @mikelawrence @bdraco
 source/_integrations/sensibo.markdown @andrey-git @gjohansson-ST
+source/_integrations/sensirion_ble.markdown @akx
 source/_integrations/sensor.markdown @home-assistant/core
 source/_integrations/sensorblue.markdown @bdraco
 source/_integrations/sensorpro.markdown @bdraco
@@ -560,13 +578,15 @@ source/_integrations/serial.markdown @fabaff
 source/_integrations/seven_segments.markdown @fabaff
 source/_integrations/sharkiq.markdown @JeffResc @funkybunch @AritroSaha10
 source/_integrations/shell_command.markdown @home-assistant/core
-source/_integrations/shelly.markdown @balloob @bieniu @thecode @chemelli74
+source/_integrations/shelly.markdown @balloob @bieniu @thecode @chemelli74 @bdraco
 source/_integrations/shodan.markdown @fabaff
 source/_integrations/sia.markdown @eavanvalkenburg
 source/_integrations/sighthound.markdown @robmarkcole
 source/_integrations/signal_messenger.markdown @bbernhard
 source/_integrations/simplepush.markdown @engrbm87
 source/_integrations/simplisafe.markdown @bachya
+source/_integrations/simply_automated.markdown @gwww
+source/_integrations/simu.markdown @imicknl @vlebourl @tetienne
 source/_integrations/sinch.markdown @bendikrb
 source/_integrations/siren.markdown @home-assistant/core @raman325
 source/_integrations/sisyphus.markdown @jkeljo
@@ -587,6 +607,7 @@ source/_integrations/smarttub.markdown @mdz
 source/_integrations/smarty.markdown @z0mbieprocess
 source/_integrations/smhi.markdown @gjohansson-ST
 source/_integrations/sms.markdown @ocalvo
+source/_integrations/snooz.markdown @AustinBrunkhorst
 source/_integrations/solaredge.markdown @frenck
 source/_integrations/solaredge_local.markdown @drobtravels @scheric
 source/_integrations/solarlog.markdown @Ernst79
@@ -626,12 +647,13 @@ source/_integrations/switchbee.markdown @jafar-atili
 source/_integrations/switchbot.markdown @bdraco @danielhiversen @RenierM26 @murtas @Eloston
 source/_integrations/switcher_kis.markdown @tomerfi @thecode
 source/_integrations/switchmate.markdown @danielhiversen @qiz-li
+source/_integrations/symfonisk.markdown @cgtobi @jjlawren
 source/_integrations/syncthing.markdown @zhulik
 source/_integrations/syncthru.markdown @nielstron
 source/_integrations/synology_dsm.markdown @hacf-fr @Quentame @mib1185
 source/_integrations/synology_srm.markdown @aerialls
 source/_integrations/system_bridge.markdown @timmo001
-source/_integrations/tado.markdown @michaelarnauts @north3221
+source/_integrations/tado.markdown @michaelarnauts
 source/_integrations/tag.markdown @balloob @dmulcahey
 source/_integrations/tailscale.markdown @frenck
 source/_integrations/tankerkoenig.markdown @guillempages @mib1185
@@ -641,6 +663,7 @@ source/_integrations/tautulli.markdown @ludeeus @tkdrob
 source/_integrations/tellduslive.markdown @fredrike
 source/_integrations/template.markdown @PhracturedBlue @tetienne @home-assistant/core
 source/_integrations/tesla_wall_connector.markdown @einarhauks
+source/_integrations/text.markdown @home-assistant/core
 source/_integrations/tfiac.markdown @fredrike @mellado
 source/_integrations/thermobeacon.markdown @bdraco
 source/_integrations/thermoplus.markdown @bdraco
@@ -667,6 +690,7 @@ source/_integrations/tts.markdown @pvizeli
 source/_integrations/tuya.markdown @Tuya @zlinoliver @frenck
 source/_integrations/twentemilieu.markdown @frenck
 source/_integrations/twinkly.markdown @dr1rrb @Robbie1221
+source/_integrations/ubiwizz.markdown @imicknl @vlebourl @tetienne
 source/_integrations/ukraine_alarm.markdown @PaulAnnekov
 source/_integrations/unifi.markdown @Kane610
 source/_integrations/unifiled.markdown @florisvdk
@@ -675,7 +699,7 @@ source/_integrations/upb.markdown @gwww
 source/_integrations/upc_connect.markdown @pvizeli @fabaff
 source/_integrations/upcloud.markdown @scop
 source/_integrations/update.markdown @home-assistant/core
-source/_integrations/upnp.markdown @StevenLooman @ehendrix23
+source/_integrations/upnp.markdown @StevenLooman
 source/_integrations/uprise_smart_shades.markdown @starkillerOG
 source/_integrations/uptime.markdown @frenck
 source/_integrations/uptimerobot.markdown @ludeeus @chemelli74
@@ -727,7 +751,7 @@ source/_integrations/xbox.markdown @hunterjm
 source/_integrations/xbox_live.markdown @MartinHjelmare
 source/_integrations/xiaomi_aqara.markdown @danielhiversen @syssi
 source/_integrations/xiaomi_ble.markdown @Jc2k @Ernst79
-source/_integrations/xiaomi_miio.markdown @rytilahti @syssi @starkillerOG @bieniu
+source/_integrations/xiaomi_miio.markdown @rytilahti @syssi @starkillerOG
 source/_integrations/xiaomi_tv.markdown @simse
 source/_integrations/xmpp.markdown @fabaff @flowolf
 source/_integrations/yale_smart_alarm.markdown @gjohansson-ST
@@ -739,6 +763,7 @@ source/_integrations/yeelightsunflower.markdown @lindsaymarkward
 source/_integrations/yi.markdown @bachya
 source/_integrations/yolink.markdown @matrixd2
 source/_integrations/youless.markdown @gjong
+source/_integrations/zamg.markdown @killer0071234
 source/_integrations/zengge.markdown @emontnemery
 source/_integrations/zeroconf.markdown @bdraco
 source/_integrations/zerproc.markdown @emlove

Gemfile

@@ -20,7 +20,7 @@ group :jekyll_plugins do
 end
 
 gem 'sinatra', '3.0.4'
-gem 'nokogiri', '1.13.9'
+gem 'nokogiri', '1.13.10'
 
 # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
 # and associated library

Gemfile.lock

@@ -71,14 +71,14 @@ GEM
     multi_json (1.15.0)
     mustermann (3.0.0)
       ruby2_keywords (~> 0.0.1)
-    nokogiri (1.13.9)
+    nokogiri (1.13.10)
       mini_portile2 (~> 2.8.0)
       racc (~> 1.4)
-    nokogiri (1.13.9-x64-mingw32)
+    nokogiri (1.13.10-x64-mingw32)
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (5.0.0)
+    public_suffix (5.0.1)
     racc (1.6.1)
     rack (2.2.4)
     rack-protection (3.0.4)
@@ -125,7 +125,7 @@ DEPENDENCIES
   jekyll-paginate (= 1.1.0)
   jekyll-sitemap (= 1.4.0)
   jekyll-toc (= 0.17.1)
-  nokogiri (= 1.13.9)
+  nokogiri (= 1.13.10)
   rake (= 13.0.6)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)

_config.yml

@@ -109,9 +109,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2022
-current_minor_version: 11
+current_minor_version: 12
-current_patch_version: 5
+current_patch_version: 6
-date_released: 2022-11-30
+date_released: 2022-12-14
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_docs/automation/using_blueprints.markdown

@@ -13,7 +13,7 @@ Quick links:
 
 Automations based on a blueprint only need to be configured to be used. What needs to be configured differs on each blueprint.
 
-To create your first automation based on a blueprint, go to **{% my config %}** and then **{% my blueprints %}**. Find the blueprint that you want to use and click on "Create Automation".
+To create your first automation based on a blueprint, go to **{% my config %}** -> **Automations & Scenes** -> **{% my blueprints %}**. Find the blueprint that you want to use and click on "Create Automation".
 
 This will open the automation editor with the blueprint selected. Give it a name and configure the blueprint and click on the blue button "Save Automation" in the bottom right.
 

source/_docs/configuration/basic.markdown

@@ -15,6 +15,7 @@ homeassistant:
   elevation: 430
   unit_system: metric
   currency: USD
+  country: US
   time_zone: "America/Los_Angeles"
   external_url: "https://www.example.com"
   internal_url: "http://homeassistant.local:8123"

source/_docs/configuration/templating.markdown

@@ -787,6 +787,7 @@ Some examples:
 
 - Filter `urlencode` will convert an object to a percent-encoded ASCII text string (e.g., for HTTP requests using `application/x-www-form-urlencoded`).
 - Filter `slugify(separator="_")` will convert a given string into a "slug".
+- Filter `ordinal` will convert an integer into a number defining a position in a series (e.g., `1st`, `2nd`, `3rd`, `4th`, etc).
 
 ### Regular expressions
 

source/_docs/energy/electricity-grid.markdown

@@ -45,6 +45,12 @@ We have developed [Home Assistant Glow](https://github.com/klaasnicolaas/home-as
 
 ![Photo of Home Assistant Glow attached to an electricity meter](/images/docs/energy/home-assistant-glow.jpg)
 
+#### Read the meter using an AI-on-the-edge-device
+
+[AI-on-the-edge-device](https://github.com/jomjol/AI-on-the-edge-device) is a project running on an ESP32-CAM and can be fully integrated into Home Assistant using the Home Assistant discovery functionality of MQTT. It digitalizes your gas/water/electricity meter display and provides its data in various ways. 
+
+![Photo of the AI-on-the-edge-device Workflow](/images/docs/energy/ai-on-the-edge-device.jpg)
+
 ### Using a CT clamp sensor
 
 CT clamp sensors measure your energy usage by looking at the current passing through an electrical wire. This makes it possible to calculate the energy usage. In Home Assistant we have support for off-the-shelf CT clamp sensors and you can build your own.

source/_docs/energy/gas.markdown

@@ -22,3 +22,10 @@ The P1 port is a standardized port on electricity meters in the Netherlands, Bel
 We have worked with creator [Marcel Zuidwijk](https://www.zuidwijk.com) to develop [SlimmeLezer+](https://www.zuidwijk.com/product/slimmelezer-plus/). It's an affordable P1 reader powered by [ESPHome](https://esphome.io) that will seamlessly integrate this information in Home Assistant. It is being sold on [his website](https://www.zuidwijk.com/product/slimmelezer-plus/) and the firmware is open source [on GitHub](https://github.com/zuidwijk/dsmr).
 
 ![Photo of SlimmeLezer attached to a smart electricity meter](/images/docs/energy/slimmelezer.jpg)
+
+#### Read the Gas Meter using an AI-on-the-edge-device
+
+[AI-on-the-edge-device](https://github.com/jomjol/AI-on-the-edge-device) is a project running on an ESP32-CAM and can be fully integrated into Home Assistant using the Home Assistant Discovery Functionality of MQTT. It digitalizes your gas/water/electricity meter display and provides its data in various ways. 
+
+![Photo of the AI-on-the-edge-device Workflow](/images/docs/energy/ai-on-the-edge-device.jpg)
+

source/_docs/energy/water.markdown

@@ -24,6 +24,11 @@ Alternatively, the following shops sell ESPHome-based devices, that use a proxim
 - [Slimme Watermeter Gateway](https://smartgateways.nl/product/slimme-watermeter-gateway/) (Dutch)
 - [watermeterkit.nl](https://watermeterkit.nl/) (Dutch)
 
-Maybe you like to build one yourself? Pieter Brinkman has quite a [nice blog article on how to create your own water sensor](https://www.pieterbrinkman.com/2022/02/02/build-a-cheap-water-usage-sensor-using-esphome-home-assistant-and-a-proximity-sensor/) using ESPHome, or [build a water meter](https://www.ztatz.nl/p1-monitor-watermeter/) that works with the [P1 Monitor](/integrations/p1_monitor) integration.
+Maybe you like to build one yourself?
+ - Pieter Brinkman has quite a [nice blog article on how to create your own water sensor](https://www.pieterbrinkman.com/2022/02/02/build-a-cheap-water-usage-sensor-using-esphome-home-assistant-and-a-proximity-sensor/) using ESPHome, or [build a water meter](https://www.ztatz.nl/p1-monitor-watermeter/) that works with the [P1 Monitor](/integrations/p1_monitor) integration.
+ - [AI-on-the-edge-device](https://github.com/jomjol/AI-on-the-edge-device) is a project running on an ESP32-CAM and can be fully integrated into Home Assistant using the Home Assistant Discovery Functionality of MQTT. It digitalizes your gas/water/electricity meter display and provides its data in various ways. 
+ 
+![Photo of the AI-on-the-edge-device Workflow](/images/docs/energy/ai-on-the-edge-device.jpg)
+
 
 For any of the above-listed options, make sure it actually works with the type of water meter you have before getting one.

source/_docs/scripts/conditions.markdown

@@ -5,7 +5,7 @@ toc: true
 no_toc: true
 ---
 
-Conditions can be used within a script or automation to prevent further execution. When a condition does not return true, the script or automation stops executing. A condition will look at the system at that moment. For example, a condition can test if a switch is currently turned on or off.
+Conditions can be used within a script or automation to prevent further execution. When a condition evaluates to true, the script or automation will be executed. If any other value is returned the script or automation stops executing. A condition will look at the system at that moment. For example, a condition can test if a switch is currently turned on or off.
 
 Unlike a trigger, which is always `or`, conditions are `and` by default - all conditions have to be true.
 

source/_docs/z-wave/controllers.markdown

@@ -120,6 +120,6 @@ You should also check the README for details on the overlays. You might find it
 
 <div class='note'>
 
-  If you've installed the Z-Way software, you'll need to ensure you disable it before you install Home Assistant or you won't be able to access the board. Do this with `sudo /etc/init.d/z-way-server stop; sudo update-rc.d z-way-server disable`.
+  If you've installed the Z-Wave.Me Z-Way software. In order to use Z-Wave JS instead of Z-Way, you'll need to ensure you disable it before you install Home Assistant, or you won't be able to access the board. Do this with `sudo /etc/init.d/z-way-server stop; sudo update-rc.d z-way-server disable`. Alternatively, you could use the [Z-Wave.Me](/integrations/zwave_me) integration.
 
 </div>

source/_includes/installation/container.md

@@ -80,7 +80,7 @@ Once the Home Assistant Container is running Home Assistant should be accessible
 
 ### Exposing Devices
 
-In order to use Z-Wave, Zigbee or other integrations that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your container instructions:
+In order to use Zigbee or other integrations that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your container instructions:
 
 {% tabbed_block %}
 

source/_integrations/airq.markdown

@@ -1,20 +1,20 @@
 ---
-title: "air-Q"
+title: air-Q
-description: "Instructions on how to integrate air-Q into Home Assistant"
+description: Instructions on how to integrate air-Q into Home Assistant
 ha_category:
   - Environment
   - Health
   - Sensor
 ha_release: '2022.12'
-ha_iot_class: "Local Polling"
+ha_iot_class: Local Polling
 ha_codeowners:
-  - "@dl2080"
+  - '@Sibgatulin'
-  - "@Sibgatulin"
+  - '@dl2080'
 ha_domain: airq
 ha_config_flow: true
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 This integration allows integrating the sensors, provided by your [air-Q](https://www.air-q.com/) device, into Home Assistant.

source/_integrations/airzone.markdown

@@ -17,6 +17,7 @@ ha_platforms:
 ha_codeowners:
   - '@Noltari'
 ha_integration_type: integration
+ha_dhcp: true
 ---
 
 This integration interacts with the Local API of [Airzone HVAC zoning systems](https://www.airzone.es/en/).

source/_integrations/alexa.markdown

@@ -9,6 +9,7 @@ ha_release: '0.10'
 ha_codeowners:
   - '@home-assistant/cloud'
   - '@ochlocracy'
+  - '@jbouwh'
 ha_domain: alexa
 ha_integration_type: integration
 ---

source/_integrations/aranet.markdown

@@ -12,7 +12,7 @@ ha_domain: aranet
 ha_config_flow: true
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: device
 ---
 
 Integrates [Aranet](https://aranet.com/) devices into Home Assistant.

source/_integrations/bluetooth.markdown

@@ -90,8 +90,9 @@ If you experience an unreliable Bluetooth connection, installing a short USB ext
 - Kinivo BTD-400 (BCM20702A0)
 - LM Technologies LM1010 (BCM20702A0) 📶
 - Nuu You BT40 (CSR8510A10)
+- ORICO BTA-403 (CSR8510A10)
 - Panda Wireless PBU40 (CSR8510A10)
-- Pluggable USB-BT4LE (BCM20702A0)
+- Plugable USB-BT4LE (BCM20702A0)
 - QGOO BT-06A (CSR8510A10)
 - Raspberry Pi 3B+ (CYW43455)
 - Raspberry Pi 4B (CYW43455)
@@ -173,6 +174,7 @@ These adapters do not have a reset pin. If they stop responding, there is curren
 - tp-link UB400 (CSR4) - Frequent connection failures with active connections
 - tp-link UB500 (RTL8761BU) - Frequent connection failures with active connections
 - Unbranded CSR 4.0 clones with USB id 0a12:0001 - Unrecoverable driver failure
+- 5 CORE CSR 4.0 (CSR CLONE) - Unrecoverable driver failure
 
 ## Multiple adapters
 

source/_integrations/brandt.markdown

@@ -0,0 +1,51 @@
+---
+title: Brandt Smart Control
+description: Connect and control your Brandt Smart Control devices using the Overkiz integration
+ha_category:
+  - Alarm Control Panel
+  - Binary Sensor
+  - Button
+  - Climate
+  - Cover
+  - Hub
+  - Light
+  - Lock
+  - Number
+  - Scene
+  - Select
+  - Sensor
+  - Siren
+  - Switch
+  - Water Heater
+ha_domain: brandt
+ha_integration_type: virtual
+ha_supporting_domain: overkiz
+ha_supporting_integration: Overkiz
+ha_release: 2022.2
+ha_codeowners:
+  - '@imicknl'
+  - '@vlebourl'
+  - '@tetienne'
+ha_config_flow: true
+ha_platforms:
+  - alarm_control_panel
+  - binary_sensor
+  - button
+  - climate
+  - cover
+  - diagnostics
+  - light
+  - lock
+  - number
+  - scene
+  - select
+  - sensor
+  - siren
+  - switch
+  - water_heater
+ha_iot_class: Cloud Polling
+ha_dhcp: true
+ha_zeroconf: true
+---
+
+{% include integrations/supported_brand.md %}

source/_integrations/bsblan.markdown

@@ -12,6 +12,7 @@ ha_codeowners:
 ha_domain: bsblan
 ha_platforms:
   - climate
+  - diagnostics
 ha_integration_type: integration
 ---
 

source/_integrations/calendar.markdown

@@ -36,7 +36,7 @@ automation:
       offset: -00:15:00
 ```
 
-Calendar triggers should should generally not use automation mode `single` to ensure the trigger
+Calendar triggers should not generally use automation mode `single` to ensure the trigger
 can fire when multiple events start at the same time (e.g., use `queued` or `parallel` instead). Note that calendars are read once every 15 minutes. When testing, make sure you do not plan events less than 15 minutes away from the current time, or your trigger might not fire.
 
 See [Automation Trigger Variables: Calendar](/docs/automation/templating/#calendar) for additional trigger data available for conditions or actions.

source/_integrations/cozytouch.markdown

@@ -16,6 +16,7 @@ ha_category:
   - Sensor
   - Siren
   - Switch
+  - Water Heater
 ha_domain: cozytouch
 ha_integration_type: virtual
 ha_supporting_domain: overkiz
@@ -41,6 +42,7 @@ ha_platforms:
   - sensor
   - siren
   - switch
+  - water_heater
 ha_iot_class: Cloud Polling
 ha_dhcp: true
 ha_zeroconf: true

source/_integrations/daikin.markdown

@@ -38,7 +38,7 @@ There is currently support for the following device types within Home Assistant:
 - The European versions of the Wifi Controller Unit (BRP069A41, 42, 43, 45), which is powered by the [Daikin Online Controller](https://play.google.com/store/apps/details?id=eu.daikin.remoapp) application. The new version of WiFi Controller Unit BRP069Bxx is also confirmed to work, tested and working devices are the BRP069B41 and BRP069B45.
 - The Australian version of the Daikin Wifi Controller Unit BRP072A42, which is operated by the [Daikin Mobile Controller (iOS)](https://itunes.apple.com/au/app/daikin-mobile-controller/id917168708?mt=8) ([Android](https://play.google.com/store/apps/details?id=ao.daikin.remoapp)) application. Confirmed working on a Daikin Cora Series Reverse Cycle Split System Air Conditioner 2.5kW Cooling FTXM25QVMA with operation mode, temp, fan swing (3d, horizontal, vertical).
   - BRP072Cxx based units (including Zena devices)*.
-- The United States version of the Wifi Controller Unit (BRP069A43), which is powered by the [Daikin Comfort Control](https://play.google.com/store/apps/details?id=us.daikin.comfortcontrols) application. Confirmed working on a Daikin Wall Units FTXS09LVJU, FTXS15LVJU, FTXS18LVJU and a Floor Unit FVXS15NVJU with operation mode, temp, fan swing (3d, horizontal, vertical).
+- The United States version of the Wifi Controller Unit (BRP072A43), which is powered by the [Daikin Comfort Control](https://play.google.com/store/apps/details?id=us.daikin.comfortcontrols) application. Confirmed working on a Daikin Wall Units FTXS09LVJU, FTXS15LVJU, FTXS18LVJU and a Floor Unit FVXS15NVJU with operation mode, temp, fan swing (3d, horizontal, vertical).
 - The Australian version of the Daikin Wifi Controller for **AirBase** units (BRP15B61), which is operated by the [Daikin Airbase](https://play.google.com/store/apps/details?id=au.com.daikin.airbase) application.
 - **SKYFi** based units, which is operated by the SKYFi application*.
 

source/_integrations/deluge.markdown

@@ -14,7 +14,7 @@ ha_platforms:
   - switch
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 There is currently support for the following device types within Home Assistant:

source/_integrations/demo.markdown

@@ -34,6 +34,7 @@ ha_platforms:
   - siren
   - stt
   - switch
+  - text
   - tts
   - update
   - vacuum

source/_integrations/discord.markdown

@@ -11,7 +11,7 @@ ha_codeowners:
   - '@tkdrob'
 ha_platforms:
   - notify
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The [Discord service](https://discordapp.com/) is a platform for the notify component. This allows integrations to send messages to the user using Discord.

source/_integrations/edl21.markdown

@@ -19,7 +19,7 @@ Compatible transceivers:
 
 - [DIY](https://wiki.volkszaehler.org/hardware/controllers/ir-schreib-lesekopf-rs232-ausgang)
 - [Weidmann Elektronik Schreib-/Lesekopf USB](https://shop.weidmann-elektronik.de/index.php?page=product&info=24)
-- [USB IR Lesekopf EHZ Lese-Schreib-Kopf Volkszähler Hichi Smartmeter](https://www.ebay.de/itm/313455434998)
+- [USB IR Lesekopf EHZ Lese-Schreib-Kopf Volkszähler Hichi Smartmeter](https://www.ebay.de/itm/313884760667)
 
 Tested smart meters:
 

source/_integrations/efergy.markdown

@@ -11,7 +11,7 @@ ha_platforms:
   - sensor
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 Integrate your [Efergy](https://efergy.com) meter information into Home Assistant.

source/_integrations/environment_canada.markdown

@@ -7,6 +7,7 @@ ha_category:
   - Weather
 ha_platforms:
   - camera
+  - diagnostics
   - sensor
   - weather
 ha_release: 0.95

source/_integrations/fibaro.markdown

@@ -26,7 +26,7 @@ ha_platforms:
 ha_codeowners:
   - '@rappenze'
 ha_config_flow: true
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The [Fibaro](https://fibaro.com/) hub is a controller mainly connecting to Z-Wave devices.

source/_integrations/flexom.markdown

@@ -16,6 +16,7 @@ ha_category:
   - Sensor
   - Siren
   - Switch
+  - Water Heater
 ha_domain: flexom
 ha_integration_type: virtual
 ha_supporting_domain: overkiz
@@ -41,6 +42,7 @@ ha_platforms:
   - sensor
   - siren
   - switch
+  - water_heater
 ha_iot_class: Cloud Polling
 ha_dhcp: true
 ha_zeroconf: true

source/_integrations/flic.markdown

@@ -17,7 +17,7 @@ The platform does not directly interact with the buttons, *but communicates with
 
 ## Service setup
 
-If you are using the Home Assistant Operating System, you can run the service locally by [installing](/hassio/installing_third_party_addons/) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/hassio-addons).
+If you are using the Home Assistant Operating System, you can run the service locally by [installing](/common-tasks/os#installing-third-party-add-ons) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/home-assistant-addons).
 
 For instructions on how to install the service manually, visit the GitHub repository of the service for [Linux](https://github.com/50ButtonsEach/fliclib-linux-hci), [macOS](https://github.com/50ButtonsEach/flic-service-osx) or [Windows](https://github.com/50ButtonsEach/fliclib-windows).
 

source/_integrations/flick_electric.markdown

@@ -11,7 +11,7 @@ ha_domain: flick_electric
 ha_config_flow: true
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 [Flick Electric Co](https://www.flickelectric.co.nz/) is a power company in New Zealand, based around a transparent pricing model where each component of pricing is provided. This integration uses the mobile app's API from Flick Electric Co to get the current power price as well as each of the components price.

source/_integrations/fritzbox.markdown

@@ -3,11 +3,11 @@ title: AVM FRITZ!SmartHome
 description: Instructions on how to integrate AVM Fritz!DECT components into Home Assistant.
 ha_category:
   - Binary Sensor
+  - Button
   - Climate
   - Light
   - Sensor
   - Switch
-  - Button
 ha_release: 0.68
 ha_iot_class: Local Polling
 ha_domain: fritzbox
@@ -15,17 +15,17 @@ ha_config_flow: true
 ha_ssdp: true
 ha_platforms:
   - binary_sensor
+  - button
   - climate
   - cover
   - diagnostics
   - light
   - sensor
   - switch
-  - button
 ha_codeowners:
   - '@mib1185'
   - '@flabbamann'
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The AVM FRITZ!SmartHome integration for Home Assistant allows you to integrate [FRITZ!DECT](https://en.avm.de/products/fritzdect/) devices like switches, sensors and thermostats.

source/_integrations/gdacs.markdown

@@ -13,7 +13,7 @@ ha_domain: gdacs
 ha_platforms:
   - geo_location
   - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The `gdacs` integration lets you use a GeoRSS feed provided by [GDACS](https://www.gdacs.org/) with information about major droughts, earthquakes, floods, tropical cyclones, tsunamis and volcanic activities worldwide.

source/_integrations/generic_hygrostat.markdown

@@ -62,12 +62,12 @@ min_cycle_duration:
   required: false
   type: [time, integer]
 dry_tolerance:
-  description: Set a minimum amount of difference between the humidity read by the sensor specified in the *target_sensor* option and the target humidity that must change prior to being switched on. For example, if the target humidity is 45 and the tolerance is 3 the humidifier will start when the sensor equals or goes below 42. It is advised to set this parameter equal or above your sensor precision. This parameter is only used on *target_sensor* changes and is ignored on initialization or manual operation.
+  description: Set a minimum amount of difference between the humidity read by the sensor specified in the *target_sensor* option and the target humidity that must change prior to being switched on. For example, if the target humidity is 45 and the tolerance is 3 the humidifier will start when the sensor equals or goes below 42. It is advised to set this parameter equal or above your sensor precision. This parameter is only used on *target_sensor* changes and is ignored on initialization, on manual operation or `humidifier.turn_on` service.
   required: false
   default: 3
   type: float
 wet_tolerance:
-  description: Set a minimum amount of difference between the humidity read by the sensor specified in the *target_sensor* option and the target humidity that must change prior to being switched off. For example, if the target humidity is 45 and the tolerance is 3 the humidifier will stop when the sensor equals or goes above 48. It is advised to set this parameter equal or above your sensor precision. This parameter is only used on *target_sensor* changes and is ignored on initialization or manual operation.
+  description: Set a minimum amount of difference between the humidity read by the sensor specified in the *target_sensor* option and the target humidity that must change prior to being switched off. For example, if the target humidity is 45 and the tolerance is 3 the humidifier will stop when the sensor equals or goes above 48. It is advised to set this parameter equal or above your sensor precision. This parameter is only used on *target_sensor* changes and is ignored on initialization, on manual operation or `humidifier.turn_on` service.
   required: false
   default: 3
   type: float

source/_integrations/geonetnz_quakes.markdown

@@ -13,7 +13,7 @@ ha_domain: geonetnz_quakes
 ha_platforms:
   - geo_location
   - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The `geonetnz_quakes` integration lets you use a GeoJSON feed provided by 

source/_integrations/geonetnz_volcano.markdown

@@ -11,7 +11,7 @@ ha_codeowners:
 ha_domain: geonetnz_volcano
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The `geonetnz_volcano` integration lets you use a GeoJSON feed provided by 

source/_integrations/goalzero.markdown

@@ -15,7 +15,7 @@ ha_platforms:
   - switch
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: device
 ---
 
 This Goal Zero Yeti integration pulls data from a Wifi-enabled [Goal Zero Yeti](https://www.goalzero.com).

source/_integrations/google_assistant.markdown

@@ -282,6 +282,8 @@ Entities that have not been explicitly assigned to rooms but have been placed in
 <div class='note'>
 
 Some devices, such as `scene` or `script`, must be assigned to an `area` before other members of a shared Google Home Household can use them. This is because household members in a shared Google Home will not be able to view devices that are not assigned to a room _unless_ they were the user who linked the service to Google Home. This issue isn't immediately apparent because `script` and `scene` devices aren't visible in the main Google Home dashboard.
+  
+The automatic room assignment will not work when multiple homes are set up in your Google account.
 
 </div>
 

source/_integrations/google_sheets.markdown

@@ -9,7 +9,7 @@ ha_config_flow: true
 ha_domain: google_sheets
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The Google Sheets integration allows you to connect your [Google Drive](https://drive.google.com) to Home Assistant. The integration adds a service to allow you to append rows to a Sheets document. The idea is that you can store data on there for further processing. When you set up a config entry, your drive will have a new sheet called Home Assistant. You can then rename this to whatever you like.

source/_integrations/harmony.markdown

@@ -21,7 +21,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `harmony` remote platform allows you to control the state of your [Harmony Hub Device](https://www.logitech.com/en-us/product/harmony-hub).
+The `harmony` remote platform allows you to control the state of your [Harmony Hub Device](https://support.myharmony.com/hub).
 
 Supported units:
 

source/_integrations/hexaom.markdown

@@ -0,0 +1,51 @@
+---
+title: Hexaom Hexaconnect
+description: Connect and control your Hexaom Hexaconnect devices using the Overkiz integration
+ha_category:
+  - Alarm Control Panel
+  - Binary Sensor
+  - Button
+  - Climate
+  - Cover
+  - Hub
+  - Light
+  - Lock
+  - Number
+  - Scene
+  - Select
+  - Sensor
+  - Siren
+  - Switch
+  - Water Heater
+ha_domain: hexaom
+ha_integration_type: virtual
+ha_supporting_domain: overkiz
+ha_supporting_integration: Overkiz
+ha_release: 2022.2
+ha_codeowners:
+  - '@imicknl'
+  - '@vlebourl'
+  - '@tetienne'
+ha_config_flow: true
+ha_platforms:
+  - alarm_control_panel
+  - binary_sensor
+  - button
+  - climate
+  - cover
+  - diagnostics
+  - light
+  - lock
+  - number
+  - scene
+  - select
+  - sensor
+  - siren
+  - switch
+  - water_heater
+ha_iot_class: Cloud Polling
+ha_dhcp: true
+ha_zeroconf: true
+---
+
+{% include integrations/supported_brand.md %}

source/_integrations/hi_kumo.markdown

@@ -16,6 +16,7 @@ ha_category:
   - Sensor
   - Siren
   - Switch
+  - Water Heater
 ha_domain: hi_kumo
 ha_integration_type: virtual
 ha_supporting_domain: overkiz
@@ -41,6 +42,7 @@ ha_platforms:
   - sensor
   - siren
   - switch
+  - water_heater
 ha_iot_class: Cloud Polling
 ha_dhcp: true
 ha_zeroconf: true

source/_integrations/homeassistant_hardware.markdown

@@ -8,7 +8,6 @@ ha_codeowners:
   - '@home-assistant/core'
 ha_domain: homeassistant_hardware
 ha_integration_type: system
-ha_quality_scale: internal
 ---
 
 The Home Assistant Hardware integration provides functionality

source/_integrations/homewizard.markdown

@@ -10,7 +10,9 @@ ha_domain: homewizard
 ha_codeowners:
   - '@DCSBL'
 ha_platforms:
+  - button
   - diagnostics
+  - number
   - sensor
   - switch
 ha_zeroconf: true
@@ -85,4 +87,3 @@ The HomeWizard Energy devices are designed to work with the HomeWizard Energy ap
 
 Cloud communication is restored when the switch is turned on again. Cloud communications are also restored after a factory reset, or when the device is put in pairing mode.
 This feature is currently only available for the Wifi Energy Socket with firmware version `3.01` or later.
-

source/_integrations/ign_sismologia.markdown

@@ -10,7 +10,7 @@ ha_codeowners:
 ha_domain: ign_sismologia
 ha_platforms:
   - geo_location
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The `ign_sismologia` platform lets you integrate a GeoRSS feed provided by the 

source/_integrations/lidarr.markdown

@@ -11,7 +11,7 @@ ha_codeowners:
   - '@tkdrob'
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The Lidarr integration pulls data from a specified [Lidarr](https://lidarr.audio/) instance.

source/_integrations/litterrobot.markdown

@@ -22,7 +22,7 @@ ha_platforms:
   - sensor
   - switch
   - vacuum
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The Litter-Robot integration allows you to control and monitor your Wi-Fi-enabled, automatic, self-cleaning litter box and pet feeders.

source/_integrations/livisi.markdown

@@ -1,10 +1,10 @@
 ---
-title: LIVISI SmartHome
+title: LIVISI Smart Home
 description: Access and control your LIVISI Smart Home Controller (SHC) and its connected RWE/innogy devices.
 ha_category:
   - Switch
-ha_iot_class: Local Push
+ha_iot_class: Local Polling
-ha_release: 2022.12.0
+ha_release: 2022.12
 ha_config_flow: true
 ha_codeowners:
   - '@StefanIacobLivisi'
@@ -12,15 +12,15 @@ ha_domain: livisi
 ha_platforms:
   - switch
 ha_integration_type: integration
-
 ---
+
 The LIVISI Smart Home integration allows you to connect your LIVISI Smart Home Controller (SHC) to Home Assistant. The SHC can control compatible devices from RWE/innogy connected to it.
  
 The following devices are currently supported by this integration:
  
 - RWE/innogy Smart Plug (PSS)
  
-##Prequisites
+## Prequisites
  
 This integration communicates with the local version of LIVISI SmartHome only. 
  
@@ -36,4 +36,4 @@ The current integration will not find your SHC automatically and needs to be con
  
 ## Device Discovery
 
-All devices are automatically discovered and included by the integration. If you include a new device in LIVISI SmartHome, the device will automatically appear in Home Assistant after a few minutes.
+All devices are automatically discovered and included by the integration. If you include a new device in LIVISI SmartHome, the device will automatically appear in Home Assistant after a few minutes.

source/_integrations/local_calendar.markdown

@@ -28,4 +28,4 @@ Individual Calendar *Events* are what powers automations such as:
 * Send a notification *5 minutes before the start of any event*
 * Stop the media player *30 minutes after* the *end* of the event named *Exercise*.
 
-See [Calendar Automations](/integrations/calendar#automation) for an overview, and read more about [Calendar Trigger Variables](/docs/automation/templating/#calendar) for the available information you can use in a condition or action such as the event `summary`, `description`, `location` and more.
+See [Calendar Automations](/integrations/calendar#automation) for an overview, and read more about [Calendar Trigger Variables](/docs/automation/templating/#calendar) for the available information you can use in a condition or action such as the event `summary`, `description`, `location` and more.

source/_integrations/lutron.markdown

@@ -10,7 +10,7 @@ ha_category:
 ha_release: 0.37
 ha_iot_class: Local Polling
 ha_codeowners:
-  - '@JonGilmore'
+  - '@cdheiser'
 ha_domain: lutron
 ha_platforms:
   - binary_sensor

source/_integrations/mazda.markdown

@@ -27,14 +27,16 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Mazda Connected Services integration allows you to retrieve data from a Mazda vehicle. In order to use this integration, you must first register your vehicle using the MyMazda app ([iOS](https://apps.apple.com/us/app/mymazda/id451886367)/[Android](https://play.google.com/store/apps/details?id=com.interrait.mymazda)).
+The Mazda Connected Services integration allows you to control and retrieve data from a Mazda vehicle. In order to use this integration, you must first register your vehicle using the MyMazda app ([iOS](https://apps.apple.com/us/app/mymazda/id451886367)/[Android](https://play.google.com/store/apps/details?id=com.interrait.mymazda)).
 
 This integration requires an active Mazda Connected Services subscription and a compatible vehicle. The following Mazda vehicles are Mazda Connected Services capable:
 
-- Mazda3: 2019+
 - CX-30: 2020+
 - CX-5: 2021+
+- CX-50: 2023+
+- CX-60: 2022+
 - CX-9: 2021+
+- Mazda3: 2019+
 - MX-30: 2020+
 
 {% include integrations/config_flow.md %}

source/_integrations/media_player.markdown

@@ -147,7 +147,7 @@ Currently only supported on [Denon AVR](/integrations/denonavr/) and  [Songpal](
 
 #### Service `media_player.shuffle_set`
 
-Currently only supported on [Sonos](/integrations/sonos), [Spotify](/integrations/spotify), [MPD](/integrations/mpd), [Kodi](/integrations/kodi), [Roon](/integrations/roon), [Squeezebox](/integrations/squeezebox) and [Universal](/integrations/universal).
+Currently only supported on [Sonos](/integrations/sonos), [Spotify](/integrations/spotify), [MPD](/integrations/mpd), [Kodi](/integrations/kodi), [Roon](/integrations/roon), [Owntone](/integrations/forked_daapd), [Squeezebox](/integrations/squeezebox) and [Universal](/integrations/universal).
 
 | Service data attribute | Optional | Description                                          |
 | ---------------------- | -------- | ---------------------------------------------------- |

source/_integrations/min_max.markdown

@@ -5,11 +5,11 @@ ha_category:
   - Helper
   - Sensor
   - Utility
-ha_iot_class: Local Push
+ha_iot_class: Calculated
 ha_release: 0.31
 ha_quality_scale: internal
 ha_codeowners:
-  - '@fabaff'
+  - '@gjohansson-ST'
 ha_domain: min_max
 ha_config_flow: true
 ha_platforms:

source/_integrations/modem_callerid.markdown

@@ -12,7 +12,7 @@ ha_platforms:
   - button
   - sensor
 ha_config_flow: true
-ha_integration_type: integration
+ha_integration_type: device
 ---
 
 The `modem_callerid` integration uses an available modem for collecting caller ID information. It requires a Hayes AT compatible modem that supports caller ID detection (via AT+VCID=1). Usually any modem that uses a CX93001 will support this.

source/_integrations/mpd.markdown

@@ -26,7 +26,7 @@ media_player:
 
 {% configuration %}
 host:
-  description: IP address of the Host where Music Player Daemon is running.
+  description: Hostname or IP address of the Host where Music Player Daemon is running.
   required: true
   type: string
 port:

source/_integrations/mqtt.markdown

@@ -10,6 +10,7 @@ ha_iot_class: Local Push
 ha_config_flow: true
 ha_codeowners:
   - '@emontnemery'
+  - '@jbouwh'
 ha_domain: mqtt
 ha_platforms:
   - alarm_control_panel
@@ -18,6 +19,7 @@ ha_platforms:
   - camera
   - climate
   - cover
+  - device_tracker
   - diagnostics
   - fan
   - humidifier
@@ -28,11 +30,10 @@ ha_platforms:
   - sensor
   - siren
   - switch
-  - tag
   - text
   - update
-  - vacuum
 ha_integration_type: integration
+ha_quality_scale: gold
 ---
 
 MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport.
@@ -168,7 +169,7 @@ mosquitto_sub -h 127.0.0.1 -v -t "home-assistant/#"
 
 The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the [HTTP binary sensor](/integrations/http/#binary-sensor) and the [HTTP sensor](/integrations/http/#sensor). To prevent multiple identical entries if a device reconnects, a unique identifier is necessary. Two parts are required on the device side: The configuration topic which contains the necessary device type and unique identifier, and the remaining device configuration without the device type.
 
-{% details "Platforms supported by MQTT discovery" %}
+{% details "Entity components supported by MQTT discovery" %}
 
 - [Alarm control panel](/integrations/alarm_control_panel.mqtt/)
 - [Binary sensor](/integrations/binary_sensor.mqtt/)
@@ -218,7 +219,7 @@ Best practice for entities with a `unique_id` is to set `<object_id>` to `unique
 
 #### Discovery payload
 
-The payload must be a serialized JSON dictionary and will be checked like an entry in your `configuration.yaml` file if a new device is added, with the exception that unknown configuration keys are allowed but ignored. This means that missing variables will be filled with the platform's default values. All configuration variables which are *required* must be present in the payload. The reason for allowing unknown documentation keys is allow some backwards compatibility, software generating MQTT discovery messages can then be used with older Home Assistant versions which will simply ignore new features.
+The payload must be a serialized JSON dictionary and will be checked like an entry in your `configuration.yaml` file if a new device is added, with the exception that unknown configuration keys are allowed but ignored. This means that missing variables will be filled with the component's default values. All configuration variables which are *required* must be present in the payload. The reason for allowing unknown documentation keys is allow some backwards compatibility, software generating MQTT discovery messages can then be used with older Home Assistant versions which will simply ignore new features.
 
 Subsequent messages on a topic where a valid payload has been received will be handled as a configuration update, and a configuration update with an empty payload will cause a previously discovered device to be deleted.
 
@@ -623,7 +624,7 @@ Setting up a [light that takes JSON payloads](/integrations/light.mqtt/#json-sch
 #### Use object_id to influence the entity id
 
 
-The entity id is automatically generated from the entity's name. All MQTT entity components optionally support providing an `object_id` which will be used instead if provided.
+The entity id is automatically generated from the entity's name. All MQTT components optionally support providing an `object_id` which will be used instead if provided.
 
 - Configuration topic: `homeassistant/sensor/device1/config`
 - Example configuration payload:
@@ -640,9 +641,9 @@ In the example above, the entity_id will be `sensor.my_super_device` instead of
 
 ## Manual configured MQTT items
 
-For most platforms it is also possible to manual set up MQTT items in `configuration.yaml`. Read more [about configuration in YAML](/docs/configuration/yaml).
+For most components it is also possible to manual set up MQTT items in `configuration.yaml`. Read more [about configuration in YAML](/docs/configuration/yaml).
 
-{% details "MQTT platforms that support setup via YAML" %}
+{% details "MQTT components that support setup via YAML" %}
 
 - [Alarm control panel](/integrations/alarm_control_panel.mqtt/)
 - [Binary sensor](/integrations/binary_sensor.mqtt/)
@@ -671,11 +672,11 @@ If you have a lot of manual configured items you might want to consider [splitti
 
 ## Using Templates
 
-The MQTT platform support templating. Read more [about using templates with the MQTT integration](/docs/configuration/templating/#using-templates-with-the-mqtt-integration).
+The MQTT integration supports templating. Read more [about using templates with the MQTT integration](/docs/configuration/templating/#using-templates-with-the-mqtt-integration).
 
 ## MQTT Notifications
 
-The MQTT notification support is different than the other [notification](/integrations/notify/) platforms. It is a service. This means that you don't have to create a configuration entry but you need to provide more details when calling the service.
+The MQTT notification support is different than for the other [notification](/integrations/notify/) components. It is a service. This means you need to provide more details when calling the service.
 
 **Call Service** section from **Developer Tools** -> **Services** allows you to send MQTT messages. Choose *mqtt.publish*  from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
 
@@ -781,11 +782,39 @@ payload_template: "{{ states('device_tracker.paulus') }}"
 
 {% endraw %}
 
-`payload` must be a string. If you want to send JSON then you need to format/escape it properly. Like:
+`payload` must be a string.
+If you want to send JSON using the YAML editor then you need to format/escape
+it properly. Like:
 
 ```yaml
 topic: home-assistant/light/1/state
-payload: "{\"Status\":\"off\", \"Data\":\"something\"}"
+payload: "{\"Status\":\"off\", \"Data\":\"something\"}"`
+```
+
+When using Home Assistant's YAML editor for formatting JSON
+you should take special care if `payload` contains template content.
+Home Assistant will force you in to the YAML editor and will treat your
+definition as a template. Make sure you escape the template blocks as like
+in the example below. Home Assistant will convert the result to a string
+and will pass it to the MQTT publish service.
+
+```yaml
+service: mqtt.publish
+data:
+  topic: homeassistant/sensor/Acurite-986-1R-51778/config
+  payload: >-
+    {"device_class": "temperature",
+    "name": "Acurite-986-1R-51778-T",
+    "unit_of_measurement": "\u00b0C",
+    "value_template": "{% raw %}{% raw %}{{ value|float }}{%{% endraw %} endraw %}",
+    "state_topic": "rtl_433/rtl433/devices/Acurite-986/1R/51778/temperature_C",
+    "unique_id": "Acurite-986-1R-51778-T",
+    "device": {
+    "identifiers": "Acurite-986-1R-51778",
+    "name": "Acurite-986-1R-51778",
+    "model": "Acurite-986",
+    "manufacturer": "rtl_433" }
+    }
 ```
 
 Example of how to use `qos` and `retain`:

source/_integrations/mystrom.markdown

@@ -17,7 +17,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `mystrom` light platform allows you to control your [myStrom](https://mystrom.ch/en/) WiFi Bulbs.
+The `mystrom` light platform allows you to control your [myStrom](https://mystrom.ch/) WiFi Bulbs.
 
 There is currently support for the following device types within Home Assistant:
 

source/_integrations/ness_alarm.markdown

@@ -22,7 +22,7 @@ There is currently support for the following device types within Home Assistant:
 - Binary Sensor: Reports on zone statuses
 - Alarm Control Panel: Reports on alarm status, and can be used to arm/disarm the system
 
-The module communicates via the [Ness D8x/D16x ASCII protocol](https://ia601401.us.archive.org/34/items/ness-d-8x-d-16x-serial-interface.-ascii-protocol/Ness%20D8x%20D16x%20Serial%20Interface.%20ASCII%20Protocol.pdf).
+The module communicates via the [Ness D8x/D16x ASCII protocol](https://ia802202.us.archive.org/16/items/ness-d-8x-d-16x-serial-interface.-ascii-protocol/Ness%20D8x%20D16x%20Serial%20Interface.%20ASCII%20Protocol.pdf).
 
 ## Configuration
 

source/_integrations/netatmo.markdown

@@ -28,7 +28,7 @@ ha_platforms:
   - select
   - sensor
   - switch
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The Netatmo integration platform is the main integration to integrate all Netatmo related platforms.

source/_integrations/nexity.markdown

@@ -16,6 +16,7 @@ ha_category:
   - Sensor
   - Siren
   - Switch
+  - Water Heater
 ha_domain: nexity
 ha_integration_type: virtual
 ha_supporting_domain: overkiz
@@ -41,6 +42,7 @@ ha_platforms:
   - sensor
   - siren
   - switch
+  - water_heater
 ha_iot_class: Cloud Polling
 ha_dhcp: true
 ha_zeroconf: true

source/_integrations/nfandroidtv.markdown

@@ -11,7 +11,7 @@ ha_platforms:
   - notify
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 Notification integration for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google) and [Notifications for Fire TV](https://www.amazon.com/Christian-Fees-Notifications-for-Fire/dp/B00OESCXEK). You can use this integration to send notifications to your Android TV device. An overlay with the message content will appear for a configurable amount of seconds and then disappear again. Sending images (e.g., security cam) and custom icons is supported too. Icons are essentially the same as images (any image format supported by Android TV is supported), but are displayed small and to the left of the notification whereas images are large and above the notification.

source/_integrations/nsw_rural_fire_service_feed.markdown

@@ -10,7 +10,7 @@ ha_codeowners:
 ha_domain: nsw_rural_fire_service_feed
 ha_platforms:
   - geo_location
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The `nsw_rural_fire_service_feed` platform lets you integrate a GeoJSON feed provided by the [NSW Rural Fire Service](https://www.rfs.nsw.gov.au/fire-information/fires-near-me) with information about bush fires, grass fires, hazard reductions and more. It retrieves incidents from a feed and shows information of those incidents filtered by distance to Home Assistant's location.

source/_integrations/nuheat.markdown

@@ -11,6 +11,8 @@ ha_dhcp: true
 ha_platforms:
   - climate
 ha_integration_type: integration
+ha_codeowners:
+  - '@tstabrawa'
 ---
 
 The `nuheat` integration lets control your connected [NuHeat Signature](https://www.nuheat.com/products/thermostats/signature-thermostat) floor heating thermostats from [NuHeat](https://www.nuheat.com/).

source/_integrations/onewire.markdown

@@ -15,7 +15,7 @@ ha_platforms:
   - diagnostics
   - sensor
   - switch
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 <div class='note warning'>

source/_integrations/overkiz.markdown

@@ -43,7 +43,7 @@ ha_platforms:
   - siren
   - switch
   - water_heater
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The Overkiz (by Somfy) integration platform is used by many different vendors, like Somfy, Hitachi, and Atlantic. This integration will allow users to integrate their devices into Home Assistant using the Overkiz API.

source/_integrations/ovo_energy.markdown

@@ -12,7 +12,7 @@ ha_codeowners:
 ha_domain: ovo_energy
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The `ovo_energy` integration allows you to monitor your energy consumption data

source/_integrations/panasonic_viera.markdown

@@ -146,6 +146,7 @@ The list with all known valid keys can be found [here](https://github.com/floria
 - TX-55EXW604S
 - TX-55FX680W
 - TX-55FZ802B
+- TX-55JZ1000W
 - TX-58AX802B
 - TX-58DX700B
 - TX-58DX800E

source/_integrations/pilight.markdown

@@ -19,7 +19,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-[Pilight](https://www.pilight.org/) is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common [protocols](https://manual.pilight.org/protocols/index.html) are already available.
+[Pilight](https://www.pilight.org/) is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common [protocols](https://manual.pilight.org/protocols/) are already available.
 
 This pilight hub connects to the [pilight-daemon](https://manual.pilight.org/programs/daemon.html) via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication.
 
@@ -48,7 +48,7 @@ host:
   default: 127.0.0.1
   type: string
 port:
-  description: "The network port to connect to, see also: (https://manual.pilight.org/development/socket/index.html)."
+  description: "The network port to connect to, see also: (https://manual.pilight.org/development/socket/)."
   required: false
   default: 5001
   type: integer
@@ -63,7 +63,7 @@ whitelist:
   type: string
 {% endconfiguration %}
 
-In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight [API](https://manual.pilight.org/development/index.html).
+In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight [API](https://manual.pilight.org/development/).
 
 A full configuration sample could look like the sample below:
 
@@ -274,7 +274,7 @@ Variables for the different codes (`on_code` and `off_code`):
 - **'off'** (*Optional*): `1` or `0`
 - **'on'** (*Optional*): `1` or `0`
 
-For possible code entries, look at the [pilight API](https://manual.pilight.org/development/index.html). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring.
+For possible code entries, look at the [pilight API](https://manual.pilight.org/development/). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring.
 
 Variables for the different receive codes (`on_code_receive` and `off_code_receive`):
 
@@ -365,7 +365,7 @@ light:
 
 ## Troubleshooting
 
-- A list of tested RF transceiver hardware is available [here](https://manual.pilight.org/electronics/index.html). This might be useful before buying.
+- A list of tested RF transceiver hardware is available [here](https://manual.pilight.org/electronics/). This might be useful before buying.
 - Sending commands is simple when the protocol is known by pilight, but receiving commands can be rather difficult. It can happen that the code is not correctly recognized due to different timings in the sending hardware or the RF receiver. If this happens follow these steps:
 
 1. [Install](https://manual.pilight.org/installation.html) pilight from source (do not worry that is very easy) and only activate the protocols you are expecting in the pop up menu. This reduces false positives.

source/_integrations/ping.markdown

@@ -39,7 +39,7 @@ host:
   required: true
   type: string
 count:
-  description: Number of packages to be sent up to a maximum of 100.
+  description: Number of packets to be sent up to a maximum of 100.
   required: false
   type: integer
   default: 5

source/_integrations/ps4.markdown

@@ -34,7 +34,10 @@ The `ps4` integration allows you to control a
 
 3. Follow instructions displayed to generate user credentials. You will know this step is completed when a form with fields appears.
 
-4. Pair Home Assistant to your PlayStation 4 by filling in the fields.
+4. On the PS4, go to Settings / Mobile App Connection Settings / Add Device, a PIN will be displayed.
+
+5. Pair Home Assistant to your PlayStation 4 by filling in the fields using the PIN from the above step.
+
 - **Note:** To find your correct region refer to the section [Regions](#regions)
 
 ## Granting Port Access

source/_integrations/pushbullet.markdown

@@ -5,7 +5,6 @@ ha_category:
   - Notifications
   - Sensor
 ha_release: 0.44
-ha_config_flow: true
 ha_iot_class: Cloud Polling
 ha_domain: pushbullet
 ha_platforms:
@@ -14,6 +13,7 @@ ha_platforms:
 ha_integration_type: integration
 ha_codeowners:
   - '@engrbm87'
+ha_config_flow: true
 ---
 
 There is currently support for the following device types within Home Assistant:

source/_integrations/qld_bushfire.markdown

@@ -10,7 +10,7 @@ ha_codeowners:
 ha_domain: qld_bushfire
 ha_platforms:
   - geo_location
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The `qld_bushfire` platform lets you integrate a 

source/_integrations/radarr.markdown

@@ -12,7 +12,7 @@ ha_platforms:
   - sensor
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 This Radarr integration pulls data from a given [Radarr](https://radarr.video/) instance.

source/_integrations/renault.markdown

@@ -20,7 +20,7 @@ ha_platforms:
   - diagnostics
   - select
   - sensor
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The Renault integration offers integration with the **MyRenault** cloud service and provides sensors such as charger state and temperature.

source/_integrations/rexel.markdown

@@ -16,6 +16,7 @@ ha_category:
   - Sensor
   - Siren
   - Switch
+  - Water Heater
 ha_domain: rexel
 ha_integration_type: virtual
 ha_supporting_domain: overkiz
@@ -41,6 +42,7 @@ ha_platforms:
   - sensor
   - siren
   - switch
+  - water_heater
 ha_iot_class: Cloud Polling
 ha_dhcp: true
 ha_zeroconf: true

source/_integrations/samsungtv.markdown

@@ -16,7 +16,7 @@ ha_platforms:
   - media_player
 ha_zeroconf: true
 ha_dhcp: true
-ha_integration_type: integration
+ha_integration_type: device
 ---
 
 The `samsungtv` platform allows you to control a [Samsung Smart TV](https://www.samsung.com/uk/tvs/all-tvs/).

source/_integrations/scrape.markdown

@@ -5,7 +5,6 @@ ha_category:
   - Sensor
 ha_release: 0.31
 ha_iot_class: Cloud Polling
-ha_config_flow: true
 ha_codeowners:
   - '@fabaff'
   - '@gjohansson-ST'
@@ -14,6 +13,7 @@ ha_domain: scrape
 ha_platforms:
   - sensor
 ha_integration_type: integration
+ha_config_flow: true
 ---
 
 The `scrape` sensor platform is scraping information from websites. The sensor loads an HTML page and gives you the option to search and split out a value. As this is not a full-blown web scraper like [scrapy](https://scrapy.org/), it will most likely only work with simple web pages and it can be time-consuming to get the right section.
@@ -91,7 +91,7 @@ scan_interval:
   description: Define the refrequency to call the REST endpoint in seconds.
   required: false
   type: integer
-  default: 30
+  default: 600
 sensor:
   description: A list of sensors to create from the shared data. All configuration settings that are supported by [RESTful Sensor](/integrations/sensor.rest#configuration-variables) not listed above can be used here.
   required: true

source/_integrations/screenlogic.markdown

@@ -26,7 +26,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Pentair ScreenLogic integration allows you to integrate your Pentair IntelliTouch or EasyTouch pool controller with Home Assistant via the [Pentair ScreenLogic](https://www.pentair.com/en-us/products/residential/pool-spa-equipment/pool-automation/screenlogic2_interfaceforintellitouchandeasytouchautomationsystems.html) gateway.
+The Pentair ScreenLogic integration allows you to integrate your Pentair IntelliTouch or EasyTouch pool controller with Home Assistant via the [Pentair ScreenLogic](https://www.pentair.com/products/residential/pool-spa-equipment/pool-automation/screenlogic2_interfaceforintellitouchandeasytouchautomationsystems.html) gateway.
 
 {% include integrations/config_flow.md %}
 

source/_integrations/sensirion_ble.markdown

@@ -23,4 +23,4 @@ The Sensirion BLE integration will automatically discover devices once the [Blue
 
 ## Supported devices
 
-- [Sensirion MyCO2 Gadget](https://sensirion.com/products/catalog/SCD4x-CO2-Gadget/)
+- [Sensirion MyCO2 Gadget](https://sensirion.com/products/catalog/SCD4x-CO2-Gadget/)

source/_integrations/shelly.markdown

@@ -16,6 +16,7 @@ ha_codeowners:
   - '@bieniu'
   - '@thecode'
   - '@chemelli74'
+  - '@bdraco'
 ha_iot_class: Local Push
 ha_domain: shelly
 featured: true
@@ -33,6 +34,7 @@ ha_platforms:
   - switch
   - update
 ha_integration_type: device
+ha_quality_scale: platinum
 ---
 
 Integrate [Shelly devices](https://shelly.cloud) into Home Assistant.
@@ -259,7 +261,7 @@ As soon as you change the temperature, it gets enabled again.
 
 ## CoAP port (generation 1)
 
-In some cases, it may be needed to customize the CoAP port (default: `5683`) your Home Assistant instance is listening to.
+In some cases, it may be needed to customize the CoAP UDP port (default: `5683`) your Home Assistant instance is listening to.
 
 In order to change it, add the following key to your `configuration.yaml`:
 

source/_integrations/shopping_list.markdown

@@ -96,4 +96,3 @@ action:
 ```
 
 {% endraw %}
-

source/_integrations/simplisafe.markdown

@@ -166,4 +166,4 @@ event data that contains the following keys:
 Note that when Home Assistant restarts, `SIMPLISAFE_NOTIFICATION` events will fire once
 again for any notifications still active in the SimpliSafe web and mobile apps. To
 prevent this, either (a) clear them in the web/mobile app or (b) utilize the 
-`simplisafe.clear_notifications` service described above.
+`clear_notifications` button provided by the alarm control panel.

source/_integrations/simu.markdown

@@ -0,0 +1,51 @@
+---
+title: SIMU LiveIn2
+description: Connect and control your SIMU LiveIn2 devices using the Overkiz integration
+ha_category:
+  - Alarm Control Panel
+  - Binary Sensor
+  - Button
+  - Climate
+  - Cover
+  - Hub
+  - Light
+  - Lock
+  - Number
+  - Scene
+  - Select
+  - Sensor
+  - Siren
+  - Switch
+  - Water Heater
+ha_domain: simu
+ha_integration_type: virtual
+ha_supporting_domain: overkiz
+ha_supporting_integration: Overkiz
+ha_release: 2022.2
+ha_codeowners:
+  - '@imicknl'
+  - '@vlebourl'
+  - '@tetienne'
+ha_config_flow: true
+ha_platforms:
+  - alarm_control_panel
+  - binary_sensor
+  - button
+  - climate
+  - cover
+  - diagnostics
+  - light
+  - lock
+  - number
+  - scene
+  - select
+  - sensor
+  - siren
+  - switch
+  - water_heater
+ha_iot_class: Cloud Polling
+ha_dhcp: true
+ha_zeroconf: true
+---
+
+{% include integrations/supported_brand.md %}

source/_integrations/skybell.markdown

@@ -20,7 +20,7 @@ ha_platforms:
   - switch
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The `skybell` implementation allows you to integrate your [Skybell.com](http://www.skybell.com/) doorbells in Home Assistant.

source/_integrations/slack.markdown

@@ -24,7 +24,7 @@ The `slack` platform allows you to deliver notifications from Home Assistant to
 
 1. Create a [new app](https://api.slack.com/apps) under your Slack.com account.
 2. Click the `OAuth & Permissions` link in the sidebar, under the Features heading.
-3. In the Scopes section, add the `chat:write` scope, `Send messages as user`. If you get a `missing_scope` error when trying to send a message, check these permissions.
+3. In the Scopes section, add the `chat:write` and `dnd:read` scopes and select `Send messages as user`. Many errors can occur if these options are not set correctly.
 4. Scroll up to `OAuth Tokens & Redirect URLs` and click `Install to Workspace`.
 5. Copy your `OAuth Access Token` and put that key into the config flow.
 

source/_integrations/steam_online.markdown

@@ -11,7 +11,7 @@ ha_platforms:
   - sensor
 ha_codeowners:
   - '@tkdrob'
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The Steam integration will allow you to track the online status of public [Steam](https://steamcommunity.com) accounts.

source/_integrations/subaru.markdown

@@ -12,6 +12,7 @@ ha_codeowners:
   - '@G-Two'
 ha_domain: subaru
 ha_platforms:
+  - diagnostics
   - lock
   - sensor
 ha_integration_type: integration

source/_integrations/switchbot.markdown

@@ -52,7 +52,7 @@ Please note, device names configured in the SwitchBot app are not transferred in
 - Curtain (WoCurtain)
 - Humidifier (WoHumi)
 - Light Strip (WoStrip)
-- Meter (WoSensorTH)
+- Meter/Meter Plus 70BB (WoSensorTH)
 - Motion Sensor (WoPresence)
 - Plug Mini (WoPlug), both the original (model W1901400) and HomeKit-enabled (model W1901401)
 

source/_integrations/switcher_kis.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
   - '@thecode'
 ha_domain: switcher_kis
 ha_platforms:
+  - button
   - climate
   - cover
   - diagnostics

source/_integrations/system_bridge.markdown

@@ -15,7 +15,7 @@ ha_platforms:
   - binary_sensor
   - sensor
 ha_zeroconf: true
-ha_integration_type: integration
+ha_integration_type: device
 ---
 
 [System Bridge](https://system-bridge.timmo.dev) is an application that runs on your local machine to share system information via its API/WebSocket. You can also send commands to the device such as opening a URL or sending keyboard keypresses.

source/_integrations/tado.markdown

@@ -13,7 +13,6 @@ ha_release: 0.41
 ha_iot_class: Cloud Polling
 ha_codeowners:
   - '@michaelarnauts'
-  - '@north3221'
 ha_domain: tado
 ha_config_flow: true
 ha_homekit: true

source/_integrations/tautulli.markdown

@@ -12,7 +12,7 @@ ha_codeowners:
 ha_domain: tautulli
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The Tautulli integration will monitor activity on a given [Tautulli Server][tautulli]. It will create a sensor that shows the number of currently active streams as the state. If you click the sensor for more details, it will show you more statistics.

source/_integrations/text.markdown

@@ -8,7 +8,6 @@ ha_domain: text
 ha_quality_scale: internal
 ha_codeowners:
   - '@home-assistant/core'
-  - '@raman325'
 ha_integration_type: entity
 ---
 

source/_integrations/transmission.markdown

@@ -20,6 +20,10 @@ ha_integration_type: integration
 
 The Transmission integration allows you to monitor your [Transmission](https://www.transmissionbt.com/) BitTorrent downloads from within Home Assistant and set up automations based on that information.
 
+<div class='note warning'>
+This integration is only compatible with Transmission clients versions 1.31 - 2.82.
+</div>
+
 ## Setup
 
 Your Transmission client must first be configured to allow remote access. In your Transmission client navigate to **Preferences** -> **Remote** tab and then click the **Allow remote access** checkbox.

source/_integrations/ubiwizz.markdown

@@ -0,0 +1,51 @@
+---
+title: Ubiwizz
+description: Connect and control your Ubiwizz devices using the Overkiz integration
+ha_category:
+  - Alarm Control Panel
+  - Binary Sensor
+  - Button
+  - Climate
+  - Cover
+  - Hub
+  - Light
+  - Lock
+  - Number
+  - Scene
+  - Select
+  - Sensor
+  - Siren
+  - Switch
+  - Water Heater
+ha_domain: ubiwizz
+ha_integration_type: virtual
+ha_supporting_domain: overkiz
+ha_supporting_integration: Overkiz
+ha_release: 2022.2
+ha_codeowners:
+  - '@imicknl'
+  - '@vlebourl'
+  - '@tetienne'
+ha_config_flow: true
+ha_platforms:
+  - alarm_control_panel
+  - binary_sensor
+  - button
+  - climate
+  - cover
+  - diagnostics
+  - light
+  - lock
+  - number
+  - scene
+  - select
+  - sensor
+  - siren
+  - switch
+  - water_heater
+ha_iot_class: Cloud Polling
+ha_dhcp: true
+ha_zeroconf: true
+---
+
+{% include integrations/supported_brand.md %}

source/_integrations/ultraloq.markdown

@@ -2,15 +2,12 @@
 title: Ultraloq
 description: Connect and control your Ultraloq Z-Wave series devices using the Z-Wave integration
 ha_release: '2022.11'
-ha_iot_class: Local Push
 ha_category:
   - Lock
 ha_domain: ultraloq
 ha_integration_type: virtual
 works_with:
   - zwave
-ha_platforms:
-  - lock
 ha_iot_standard: zwave
 ---
 

source/_integrations/unifiprotect.markdown

@@ -39,7 +39,7 @@ ha_platforms:
   - sensor
   - switch
   - text
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The UniFi Protect integration adds support for retrieving Camera feeds and Sensor data from a [UniFi Protect application](https://ui.com/camera-security) by [Ubiquiti Networks, inc.](https://www.ui.com/) that is running on a UniFi OS Console.