Doc iframe allow topnav

.textlintrc.json

@@ -142,6 +142,7 @@
         "IP",
         "iPad",
         "iPhone",
+        "ISY",
         "ISY994",
         "iTunes",
         "JSON-RPC",

CODEOWNERS

@@ -192,6 +192,7 @@ source/_integrations/epsonworkforce.markdown @ThaStealth
 source/_integrations/eq3btsmart.markdown @rytilahti
 source/_integrations/escea.markdown @lazdavila
 source/_integrations/esphome.markdown @OttoWinter @jesserockz
+source/_integrations/eufylife_ble.markdown @bdr99
 source/_integrations/evil_genius_labs.markdown @balloob
 source/_integrations/evohome.markdown @zxdavb
 source/_integrations/ezviz.markdown @RenierM26 @baqs
@@ -353,6 +354,7 @@ source/_integrations/landisgyr_heat_meter.markdown @vpathuis
 source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol
 source/_integrations/laundrify.markdown @xLarry
 source/_integrations/lcn.markdown @alengwenus
+source/_integrations/ld2410_ble.markdown @930913
 source/_integrations/led_ble.markdown @bdraco
 source/_integrations/legrand.markdown @cgtobi
 source/_integrations/leviton_z_wave.markdown @home-assistant/z-wave

source/_dashboards/iframe.markdown

@@ -38,6 +38,11 @@ aspect_ratio:
   description: 'Forces the height of the image to be a ratio of the width. Valid formats: Height percentage value (`23%`) or ratio expressed with colon or "x" separator (`16:9` or `16x9`). For a ratio, the second element can be omitted and will default to "1" (`1.78` equals `1.78:1`).'
   type: string
   default: "50%"
+allow_open_top_navigation:
+  required:false
+  description: 'Allow the user to open iframe content links by opening the default browser in HomeAssistant mobile app. It is false by default because it adds allow-top-navigation-by-user-activation on the iframe sandbox attribute which is a less secure. So set it to true if you need it and are confident with the iframe content.'
+  type: boolean
+  default: false
 title:
   required: false
   description: The card title.

source/_dashboards/picture.markdown

@@ -27,6 +27,10 @@ image:
   required: true
   description: "The URL of an image. When you want to store images in your Home Assistant installation use the [hosting files documentation](/integrations/http/#hosting-files). After storing your files, use the `/local` path, for example, `/local/filename.jpg`."
   type: string
+alt_text:
+  required: false
+  description: Alternative text for the image. This is necessary for users of assistive technology. The [W3C images tutorial](https://www.w3.org/WAI/tutorials/images/) provides simple guidance for writing alternative text.
+  type: string
 theme:
   required: false
   description: Override the used theme for this card with any loaded theme. For more information about themes, see the [frontend documentation](/integrations/frontend/).

source/_docs/blueprint/selectors.markdown

@@ -802,6 +802,15 @@ mode:
     will use a `dropdown` input.
   type: string
   required: false
+translation_key:
+  description: >
+    Allows translations provided by an integration where `translation_key`
+    is the translation key that is providing the selector option strings
+    translation. See the documentation on
+    [Backend Localization](https://developers.home-assistant.io/docs/internationalization/core/#selectors)
+    for more information.
+  type: string
+  required: false
 {% endconfiguration %}
 
 Alternatively, a mapping can be used for the options. When you want to return

source/_docs/scripts/conditions.markdown

@@ -681,7 +681,7 @@ Every individual condition can be disabled, without removing it.
 To do so, add `enabled: false` to the condition configuration.
 
 This can be useful if you want to temporarily disable a condition, for example,
-for testing. A disabled condition will always pass.
+for testing. A disabled condition will behave as if it were removed.
 
 For example:
 

source/_integrations/airzone.markdown

@@ -5,6 +5,7 @@ ha_release: 2022.4
 ha_category:
   - Binary Sensor
   - Climate
+  - Select
   - Sensor
 ha_iot_class: Local Polling
 ha_config_flow: true
@@ -13,6 +14,7 @@ ha_platforms:
   - binary_sensor
   - climate
   - diagnostics
+  - select
   - sensor
 ha_codeowners:
   - '@Noltari'
@@ -62,6 +64,16 @@ For each Airzone zone (Thermostat) a *climate entity* is created.
 
 *Slave zones* can only enable/disable the current HVAC mode selected on the corresponding *parent zone*. Attempting to change the HVAC mode on a *child zone* will result on a Home Assistant error.
 
+## Select
+
+For each Airzone zone (Thermostat), the following *selects* are created:
+
+| Condition           | Description                        |
+| :------------------ | :--------------------------------- |
+| Cold Angle          | Grille angle for cooling.          |
+| Heat Angle          | Grille angle for heating.          |
+| Sleep               | Minutes for auto sleep.            |
+
 ## Sensors
 
 For the Airzone WebServer, the following *sensors* are created:

source/_integrations/anwb_energie.markdown

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

source/_integrations/bluetooth_adapters.markdown

@@ -0,0 +1,17 @@
+---
+title: Bluetooth Adapters
+description: Bluetooth Adapters provides access to local and remote Bluetooth Adapters
+ha_release: 2023.2
+ha_category:
+  - Other
+ha_codeowners:
+  - '@bdraco'
+ha_domain: bluetooth_adapters
+ha_integration_type: system
+---
+
+Bluetooth Adapters provides access to local and remote Bluetooth Adapters to integrations that use Bluetooth.
+
+## Configuration
+
+This integration is not user configurable.

source/_integrations/climate.mqtt.markdown

@@ -83,6 +83,14 @@ availability_topic:
   description: The MQTT topic subscribed to receive availability (online/offline) updates. Must not be used together with `availability`.
   required: false
   type: string
+current_humidity_template:
+  description: A template with which the value received on `current_humidity_topic` will be rendered.
+  required: false
+  type: template
+current_humidity_topic:
+  description: The MQTT topic on which to listen for the current humidity.
+  required: false
+  type: string
 current_temperature_template:
   description: A template with which the value received on `current_temperature_topic` will be rendered.
   required: false
@@ -189,10 +197,20 @@ json_attributes_topic:
   description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Usage example can be found in [MQTT sensor](/integrations/sensor.mqtt/#json-attributes-topic-configuration) documentation.
   required: false
   type: string
+max_humidity:
+  description: The minimum target humidity percentage that can be set.
+  required: false
+  type: integer
+  default: 99
 max_temp:
   description: Maximum set point available.
   type: float
   required: false
+min_humidity:
+  description: The maximum target humidity percentage that can be set.
+  required: false
+  type: integer
+  default: 30
 min_temp:
   description: Minimum set point available.
   type: float
@@ -202,7 +220,7 @@ mode_command_template:
   required: false
   type: template
 mode_command_topic:
-  description: The MQTT topic to publish commands to change the HVAC operation mode.
+  description: The MQTT topic to publish commands to change the HVAC operation mode. Use with `mode_command_template` if you only want to publish the power state.
   required: false
   type: string
 mode_state_template:
@@ -227,6 +245,11 @@ object_id:
   description: Used instead of `name` for automatic generation of `entity_id`
   required: false
   type: string
+optimistic:
+  description: Flag that defines if the climate works in optimistic mode
+  required: false
+  type: boolean
+  default: "`true` if no state topic defined, else `false`."
 payload_available:
   description: The payload that represents the available state.
   required: false
@@ -247,10 +270,6 @@ payload_on:
   required: false
   type: string
   default: "ON"
-power_command_topic:
-  description: The MQTT topic to publish commands to change the power state. This is useful if your device has a separate power toggle in addition to mode.
-  required: false
-  type: string
 precision:
   description: The desired precision for this device. Can be used to match your actual thermostat's precision. Supported values are `0.1`, `0.5` and `1.0`.
   required: false
@@ -308,6 +327,22 @@ swing_modes:
   required: false
   default: ['on', 'off']
   type: list
+target_humidity_command_template:
+  description: Defines a [template](/docs/configuration/templating/#using-templates-with-the-mqtt-integration) to generate the payload to send to `target_humidity_command_topic`.
+  required: false
+  type: template
+target_humidity_command_topic:
+  description: The MQTT topic to publish commands to change the target humidity.
+  required: false
+  type: string
+target_humidity_state_topic:
+  description: The MQTT topic subscribed to receive the target humidity. If this is not set, the target humidity works in optimistic mode (see below).
+  required: false
+  type: string
+target_humidity_state_template:
+  description: Defines a [template](/docs/configuration/templating/#using-templates-with-the-mqtt-integration) to extract a value for the climate `target_humidity` state.
+  required: false
+  type: string
 temperature_command_template:
   description: A template to render the value sent to the `temperature_command_topic` with.
   required: false
@@ -377,7 +412,7 @@ value_template:
 
 ## Optimistic mode
 
-If a property works in *optimistic mode* (when the corresponding state topic is not set), Home Assistant will assume that any state changes published to the command topics did work and change the internal state of the entity immediately after publishing to the command topic. If it does not work in optimistic mode, the internal state of the entity is only updated when the requested update is confirmed by the device through the state topic.
+If a property works in *optimistic mode* (when the corresponding state topic is not set), Home Assistant will assume that any state changes published to the command topics did work and change the internal state of the entity immediately after publishing to the command topic. If it does not work in optimistic mode, the internal state of the entity is only updated when the requested update is confirmed by the device through the state topic. You can enforce optimistic mode by setting the `optimistic` option to `true`. When set, the internal state will always be updated, even when a state topic is defined.
 
 ## Using Templates
 
@@ -410,6 +445,8 @@ Similarly for `*_command_topic`s, a template can be specified to render the outg
 
 A full configuration example looks like the one below.
 
+{% raw %}
+
 ```yaml
 # Full example configuration.yaml entry
 mqtt:
@@ -430,11 +467,13 @@ mqtt:
         - "eco"
         - "sleep"
         - "activity"
-      power_command_topic: "study/ac/power/set"
       preset_mode_command_topic: "study/ac/preset_mode/set"
       mode_command_topic: "study/ac/mode/set"
+      mode_command_template: "{{ value if value=="off" else "on" }}"
       temperature_command_topic: "study/ac/temperature/set"
       fan_mode_command_topic: "study/ac/fan/set"
       swing_mode_command_topic: "study/ac/swing/set"
       precision: 1.0
 ```
+
+{% endraw %}