Merge branch 'next' into Thomas55555-patch-1

source/_docs/configuration/templating.markdown

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

source/_integrations/climate.markdown

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

source/_integrations/enphase_envoy.markdown

@@ -60,10 +60,17 @@ For models running firmware 5 and older, use `installer` for the username. No pa
 The Enphase Enpower has 4 load shedding relays that can be used to control non-essential loads in your home. These have two main modes of operation:
 
 ### Standard
+
 When the mode entity is set to standard, you can simply set the state of the relay to be powered or not powered for each mode of operation: on grid, off grid, and on generator.
 
 ### Battery level
+
 When the relay mode is set to battery level, the relays will turn on and off based on the remaining battery level of your Encharge batteries. Two number entities are available to control the cutoff and restore levels for the relays. When the battery level drops below the cutoff level, the relays will turn off. When the battery level rises above the restore level, the relays will turn back on.
 
 ## Polling interval
-The default polling interval is 60 seconds. To customize the polling interval, refer to [defining a custom polling interval](/common-tasks/general/#defining-a-custom-polling-interval). Specify the envoy device as a target of the service using the `+ choose device` button. Updating the envoy will also update the related devices like the inverters; there is no need to split them into separate entities or add all inverter devices. When using multiple Envoys, add them as targets or create separate custom polling intervals as needed.
+
+The default polling interval is 60 seconds. To customize the polling interval, refer to [defining a custom polling interval](/common-tasks/general/#defining-a-custom-polling-interval). Specify one single entity from the envoy device as target of the service using the `+ choose entity` button. Updating one entity will update all entities of the Envoy and the related devices like the inverters; there is no need to specify multiple or all entities or add (all) inverter entities. When using multiple Envoys, add one entity for each envoy as targets or create separate custom polling intervals with a single entity as needed.
+
+## Credentials update
+
+This integration supports updating configuration by re-adding the integration and specifying the same or new IP address, username, and password. Use this method if your Enlighten credentials or the device's IP address has changed and needs to be updated.

source/_integrations/flexit_bacnet.markdown

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

source/_integrations/lamarzocco.markdown

@@ -51,6 +51,10 @@ Host:
 | Coffee target temperature | Temperature the coffee boiler is set to | GS3 AV, GS3 MP | - |
 | Steam target temperature | Temperature the steam boiler is set to | GS3 AV, GS3 MP | - |
 | Tea water duration | Dose hot water (in seconds) | GS3 AV, GS3 MP | - |
+| Dose | Doseage (in ticks) for each key | GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
+| Prebrew on time | Time prebrew wets the puck | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
+| Prebrew off time | Time prebrew waits before turning on the pump | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
+| Preinfusion time | Duration of preinfusion | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
 
 
 ## Switches

source/_integrations/myuplink.markdown

@@ -2,6 +2,7 @@
 title: myUplink
 description: Instructions on how to set up the myUplink integration within Home Assistant.
 ha_category:
+  - Binary sensor
   - Sensor
   - Update
 ha_iot_class: Cloud Polling
@@ -11,6 +12,8 @@ ha_codeowners:
   - '@pajzo'
 ha_config_flow: true
 ha_platforms:
+  - binary_sensor
+  - diagnostics
   - sensor
   - update
 ha_integration_type: integration
@@ -29,7 +32,6 @@ Depending on the type of devices in your system, one or more sensor entities to
 - **OAuth Flow**: Authorization Code Grant Flow
 - **Redirect URI**: `https://my.home-assistant.io/redirect/oauth`
 
-
 {% details "I have manually disabled My Home Assistant" %}
 
 If you don't have [My Home Assistant](/integrations/my) on your installation,
@@ -39,7 +41,7 @@ instead.
 The `<HOME_ASSISTANT_URL>` must be the same as used during the configuration/
 authentication process.
 
-Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://homeassistant.local:8123/auth/external/callback`." 
+Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://homeassistant.local:8123/auth/external/callback`."
 
 {% enddetails %}
 

source/_integrations/renson.markdown

@@ -5,6 +5,7 @@ ha_category:
   - Binary sensor
   - Button
   - Fan
+  - Switch
   - Time
   - Number
 ha_release: 2023.7
@@ -17,6 +18,7 @@ ha_platforms:
   - binary_sensor
   - button
   - fan
+  - switch
   - number
   - sensor
   - time

source/_integrations/thermopro.markdown

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

source/_integrations/velux.markdown

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