Merge branch 'next' into govee-local-update

source/_integrations/cookidoo.markdown

@@ -63,6 +63,39 @@ The _clear shopping list_ button entity allows you to clear both the shopping li
 
 This button entity will appear automatically in your Home Assistant instance after adding the integration. You can use it in automations or add it to your dashboard using the Button card.
 
+## Sensor entities
+
+### Diagnostics
+
+1. **Subscription**
+   - State: `premium`, `trial`, or `free`
+   - Description: Indicates the current subscription type
+     - `premium`: Yearly subscription with full recipe access
+     - `trial`: Time-limited premium access (available during account creation or new device linking)
+     - `free`: Limited recipe access with full shopping list features
+
+2. **Subscription expiration date**
+   - State: ISO 8601 timestamp or `unknown`
+   - Description: Shows when the current subscription expires
+     - For `premium` and `trial` subscriptions: Timestamp of expiration date
+     - For `free` subscriptions: Returns `unknown` state
+
+These sensor entities will appear automatically in your Home Assistant instance after adding the integration.
+
+{% details "Example state attributes" %}
+
+```yaml
+subscription:
+  state: premium
+  icon: mdi:account-star
+
+subscription_expiration_date:
+  state: "2025-01-15T23:59:59+00:00"
+  icon: mdi:clock-reactivate
+```
+
+{% enddetails %}
+
 ## Known Limitations
 
 {% important %}

source/_integrations/heos.markdown

@@ -13,6 +13,7 @@ ha_ssdp: true
 ha_platforms:
   - media_player
 ha_integration_type: integration
+ha_quality_scale: silver
 ---
 
 The HEOS {% term integration %} is used to connect a [HEOS](https://www.denon.com/en-gb/category/heos/) System to Home Assistant. HEOS is a wireless audio ecosystem

source/_integrations/homee.markdown

@@ -0,0 +1,61 @@
+---
+title: Homee
+description: Instructions on how to setup Homee devices in Home Assistant.
+ha_category:
+  - Cover
+ha_config_flow: true
+ha_release: 2025.2
+ha_iot_class: Local Push
+ha_codeowners:
+  - '@Taraman17'
+ha_domain: homee
+ha_platforms:
+  - cover
+  - sensor
+ha_integration_type: hub
+---
+
+[Homee](https://hom.ee) is a smart home system, able to integrate various protocols such as Z-Wave, Zigbee, EnOcean, and more. The Homee {% term integration %} will let you use the {% term devices %} from your Homee in Home Assistant.
+
+There is currently support for the following device types in Home Assistant:
+
+- cover
+- sensor
+
+
+## Prerequisites
+
+You need to create a new user in your Homee app. Create a user that is only used by Home Assistant. For security reasons, it's recommended to:
+
+- Use a strong, unique password.
+- Restrict the user's permissions for what you want to do from Home Assistant.
+- Do not use this account for any other purpose.
+
+1. In your Homee app, in the top-left corner, tap the menu button.
+2. On the top right of the opening menu, tap the gear {% icon "mdi:gear-outline" %} icon.
+3. Choose **Manage users**.
+4. Choose **Add user** and configure the desired values.
+
+{% include integrations/config_flow.md %}
+
+{% configuration_basic %}
+Host:
+  description: The IP Address of your Homee.
+User:
+  description: The username you chose in the Prerequisites.
+Password:
+  description: The password for that user.
+{% endconfiguration_basic %}
+
+Available devices will automatically show up in your Home Assistant installation.
+New devices added to Homee will be automatically discovered after a restart of Home Assistant. This restart is only required when adding new devices, not for state updates of existing devices.
+
+## Limitations
+
+Changed values are reported from Homee in defined time intervals and not always in realtime. For example, while a cover moves, the position is updated only every few seconds and intermediate states may be missed by Home Assistant.
+
+## Removing the integration
+
+This integration follows standard integration removal, and once the integration is removed, you can also remove the dedicated user from your Homee.
+
+{% include integrations/remove_device_service.md %}

source/_integrations/homewizard.markdown

@@ -79,6 +79,11 @@ Sensors for Water meter:
 - **Water usage (L/min)**: Flow of water measured at that time.
 - **Total water usage (m³)**: Total water usage since the installation of the HomeWizard Water meter.
 
+Sensors for Plug-In Battery:
+
+- **Cycles**: Number of charge cycles the battery has gone through.
+- **State of charge (%)**: The current state of charge of the battery.
+
 ## Energy Socket
 
 The Energy Socket outlet state and status light can be controlled. There are two switches:

source/_integrations/ohme.markdown

@@ -12,8 +12,11 @@ ha_config_flow: true
 ha_domain: ohme
 ha_platforms:
   - button
+  - number
+  - select
   - sensor
   - switch
+  - time
 ha_quality_scale: silver
 ha_integration_type: device
 ---
@@ -56,6 +59,18 @@ The Ohme integration provides the following entities.
   - **Description**: If sensor **Status** is `Pending approval`, this will approve the charge.
   - **Available for devices**: all
 
+#### Numbers
+
+- **Target percentage**
+  - **Description**: Sets the charge target for your vehicle.
+  - **Available for devices**: all
+
+#### Selects
+
+- **Charger mode**
+  - **Description**: Sets the mode of the charger. Possible options: `Smart charge`, `Max charge`, `Paused`. This is only available with a vehicle plugged in.
+  - **Available for devices**: all
+
 #### Sensors
 
 - **Status**
@@ -86,6 +101,12 @@ The Ohme integration provides the following entities.
   - **Description**: Turn off the screen of the device after a few minutes of inactivity.
   - **Available for devices**: Home Pro
 
+#### Times
+
+- **Target time**
+  - **Description**: Sets the time you need your vehicle charged by.
+  - **Available for devices**: all
+
 ## Actions
 
 The integration provides the following actions.

source/_integrations/reolink.markdown

@@ -242,6 +242,7 @@ Depending on the supported features of the camera, switch entities are added for
 - Doorbell button sound
 - Record
 - Manual record
+- Privacy mode+
 - Push notifications
 - Hub ringtone on event
 - Email on event
@@ -250,6 +251,8 @@ Depending on the supported features of the camera, switch entities are added for
 - PIR reduce false alarm*
 - Chime LED
 
+When the **Privacy mode** is ON, almost all other entities will be unavailable because the camera shuts down the API and camera streams. When turning OFF the **Privacy mode**, all entities will become available again. Take this into consideration when making automations; ensure the **Privacy mode** is OFF before changing camera settings using other entities.
+
 When the **Infrared lights in night mode** entity is set to OFF, the infrared LEDs are always OFF. When the **Infrared lights in night mode** entity is set to ON, the infrared LEDs will be on when the camera is in night vision mode. For more information, see the **Day night mode** select entity.
 
 For NVRs, a global switch for **Record**, **Push**, **Hub ringtone on event**, **Email**, and **FTP** will be available under the NVR device as well as a switch per channel of the NVR under the camera device. The respective feature will only be active for a given channel if both the global and that channel switch are enabled (as is also the case in the Reolink app/client).
@@ -652,6 +655,7 @@ Prerequisites:
 
 ### Entities intermittently become unavailable
 
+- Note that almost all entities, including motion/ai detection and the camera streams, will be unavailable when privacy mode is turned ON. Check the history of the **Privacy mode** entity to see if this is causing the issues. 
 - Setting a static IP address for Reolink cameras/NVRs in your router is advisable to prevent (temporal) connectivity issues when the IP address changes.
 - Do not set a static IP in the Reolink device itself, but leave the **Connection Type** on **DHCP** under **Settings** > **Network** > **Network Information** > **Set Up**. If you set it to **static** on the Reolink device itself, this is known to cause incorrect DHCP requests on the network. The incorrect DHCP request causes Home Assistant to use the wrong IP address for the camera, resulting in connection issues. The issue originates from the Reolink firmware, which keeps sending DCHP requests even when you set a static IP address in the Reolink device.
 - Reolink cameras can support a limited amount of simultaneous connections. Therefore using third-party software like Frigate, Blue Iris, or Scrypted, or using the ONVIF integration at the same time can cause the camera to drop connections. This results in short unavailabilities of the Reolink entities in Home Assistant. Especially when the connections are coming from the same device (IP) where Home Assistant is running, the Reolink cameras can get confused, dropping one connection in favor of the other originating from the same host IP. If you experience disconnections/unavailabilities of the entities, please first temporarily shut down the other connections (like Frigate) to diagnose if that is the problem. If that is indeed the problem, you could try moving the third-party software to a different host (IP address) since that is known to solve the problem most of the time. You could also try switching the protocol to FLV on Home Assistant and/or the third-party software, as that is known to be less resource-intensive on the camera.

source/_integrations/synology_dsm.markdown

@@ -16,6 +16,7 @@ ha_codeowners:
 ha_config_flow: true
 ha_ssdp: true
 ha_platforms:
+  - backup
   - binary_sensor
   - button
   - camera
@@ -27,7 +28,7 @@ ha_integration_type: integration
 ha_zeroconf: true
 ---
 
-The Synology DSM integration provides access to various statistics from your [Synology NAS](https://www.synology.com) (_DSM 5.x and higher_) as well as cameras from the [Surveillance Station](https://www.synology.com/surveillance).
+The Synology DSM integration provides access to various statistics from your [Synology NAS](https://www.synology.com) (_DSM 5.x and higher_), as well as cameras from the [Surveillance Station](https://www.synology.com/surveillance) and will allow to use the [File Station](https://www.synology.com/en-us/dsm/feature/file_sharing) as a {% term backup %} location.
 
 {% include integrations/config_flow.md %}
 
@@ -51,6 +52,8 @@ When creating the user, it is possible to deny access to all locations and appli
 
 If you want to add cameras from [Surveillance Station](https://www.synology.com/surveillance), the user needs application permission for [Surveillance Station](https://www.synology.com/surveillance).
 
+If you want to use a shared folder from the [File Station](https://www.synology.com/en-us/dsm/feature/file_sharing) as {% term backup %} location, the user needs application permission for [File Station](https://www.synology.com/en-us/dsm/feature/file_sharing) and read/write permissions on the specific shared folder.
+
 ### If you utilize 2-Step Verification or Two Factor Authentication (2FA) with your Synology NAS
 
 If you have the "Enforce 2-step verification for the following users" option checked under **Control Panel > Security > Account > 2-Factor Authentication**, you'll need to configure the 2-step verification/one-time password (OTP) for the user you just created before the credentials for this user will work with Home Assistant.