home-assistant · timmo001 · Aug 1, 2025 · Aug 2, 2025 · Aug 3, 2025 · Aug 4, 2025
diff --git a/source/_dashboards/clock.markdown b/source/_dashboards/clock.markdown
@@ -19,21 +19,73 @@ Screenshot of the clock card
 
 All options for this card can be configured via the user interface.
 
-
 ## Card settings
 
-{% configuration_basic %}
-Title:
+{% configuration %}
+title:
   description: Adds a title to the top of the card
-Clock Size:
+  type: string
+  required: false
+clock_style:
+  description: Allows the clock to be displayed in a digital or analog style. Defaults to digital.
+  type: list
+  required: false
+  default: digital
+  keys:
+    digital:
+      description: Digital clock style.
+    analog:
+      description: Analog clock style.
+clock_size:
   description: Adjusts the size of the text allowing a wider range of use with different types of dashboards. Defaults to small.
-Display Seconds:
+  type: list
+  required: false
+  default: small
+  keys:
+    small:
+      description: Small clock size.
+    medium:
+      description: Medium clock size.
+    large:
+      description: Large clock size.
+show_seconds:
   description: Shows seconds alongside the clock, providing the time format is in a 12-hour format.
-Time Format:
+  type: boolean
+  required: false
+  default: false
+time_format:
   description: Allows the time format to be changed on a per-card level. Defaults to the user profile setting.
-Time Zone:
+  type: string
+  required: false
+time_zone:
   description: Change the timezone used for the time on a per-card level. Defaults to the user profile setting.
-{% endconfiguration_basic %}
+  type: string
+  required: false
+analog_options:
+  description: When using the analog clock style, this allows the user to configure the appearance of the clock.
+  type: map
+  required: false
+  keys:
+    border:
+      description: Shows a border around the clock face. Defaults to false.
+      type: boolean
+      required: false
+      default: false
+    ticks:
+      description: Shows ticks (indices) on the clock face. Defaults to hour.
+      type: list
+      required: false
+      default: hour
+      keys:
+        none:
+          description: No ticks are shown.
+        quarter:
+          description: Quarter hour ticks are shown.
+        hour:
+          description: Hour ticks are shown.
+        minute:
+          description: Minute ticks are shown.
+{% endconfiguration %}
 
 ### Examples
 
@@ -48,7 +100,6 @@ type: clock
 Screenshot of the basic clock card
 </p>
 
-
 Example of a larger clock card for tablet dashboards:
 
 ```yaml
@@ -107,3 +158,54 @@ title: New York 🦅
 <img src='/images/dashboards/clock_card_new_york.png' alt='Screenshot of a medium sized, 12 hour clock showing am/pm and seconds based in New York along with a title'>
 Screenshot of a medium sized, 12 hour clock showing am/pm and seconds based in New York along with a title
 </p>
+
+Analog clock with no border and hour ticks:
+
+```yaml
+type: clock
+clock_style: analog
+clock_size: medium
+analog_options:
+  border: false
+  ticks: hour
+```
+
+<p class='img'>
+<img src='/images/dashboards/clock_card_analog_hour_ticks.png' alt='Screenshot of a medium sized, analog clock and hour ticks'>
+Screenshot of a medium sized, analog clock and hour ticks
+</p>
+
+Analog clock with border and minute ticks showing seconds:
+
+```yaml
+type: clock
+clock_style: analog
+clock_size: medium
+show_seconds: true
+analog_options:
+  border: true
+  ticks: minute
+```
+
+<p class='img'>
+<img src='/images/dashboards/clock_card_analog_minute_ticks_border.png' alt='Screenshot of a medium sized, analog clock and minute ticks showing seconds'>
+Screenshot of a medium sized, analog clock and minute ticks showing seconds
+</p>
+
+Analog clock with a title, no ticks and border with seconds:
+
+```yaml
+type: clock
+clock_style: analog
+clock_size: medium
+show_seconds: true
+analog_options:
+  border: true
+  ticks: none
+title: Mountain Time
+```
+
+<p class='img'>
+<img src='/images/dashboards/clock_card_analog_no_ticks_border_title_mountain_time.png' alt='Screenshot of a medium sized, analog clock with a title, no ticks and border showing seconds'>
+Screenshot of a medium sized, analog clock with a title, no ticks and border showing seconds
+</p>
diff --git a/source/_dashboards/conditional.markdown b/source/_dashboards/conditional.markdown
@@ -198,9 +198,31 @@ users:
   type: list
 {% endconfiguration %}
 
+### Location
+
+Specify the visibility of the card based on the current user's current location. The location is based on the state of the `person` entity associated with the current user. If the current user does not have a `person` entity, this condition will always resolve to false.
+
+```yaml
+condition: location
+locations:
+  - home
+  - Home Neigborhood
+```
+
+{% configuration %}
+condition:
+  required: true
+  description: "`location`"
+  type: string
+locations:
+  required: true
+  description: A list of zones, which if any match the current state of the `person`, will cause this condition to be true. 
+  type: list
+{% endconfiguration %}
+
 ### And
 
-Specify that both conditions must be met.
+Specify that all conditions must be met.
 
 ```yaml
 condition: and
@@ -248,4 +270,27 @@ conditions:
   type: list
 {% endconfiguration %}
 
+### Not
+
+Specify that at least one of the conditions must not be met.
+
+```yaml
+condition: not
+conditions:
+  - condition: numeric_state
+    above: 0
+  - condition: user
+    users:
+      - 581fca7fdc014b8b894519cc531f9a04
+```
 
+{% configuration %}
+condition:
+  required: true
+  description: "`not`"
+  type: string
+conditions:
+  required: false
+  description: List of conditions to check. See [available conditions](#conditions-options).
+  type: list
+{% endconfiguration %}
diff --git a/source/_dashboards/energy.markdown b/source/_dashboards/energy.markdown
@@ -259,8 +259,9 @@ title:
   type: string
 layout:
   required: false
-  description: "`vertical` or `horizontal`. Determines the orientation (flow direction) of the card"
+  description: "`vertical`, `horizontal` or `auto`. Determines the orientation (flow direction) of the card. `auto` changes it based on the screen size."
   type: string
+  default: auto
 group_by_area:
   required: false
   description: Whether to group the devices by area

diff --git a/source/_dashboards/todo-list.markdown b/source/_dashboards/todo-list.markdown
@@ -76,6 +76,11 @@ display_order:
   description: "Optionally sorts the items in the to-do list for display. Options are: `none`: Show the list in its original order. `alpha_asc`: Sort the list in alphabetical order. `alpha_desc`: Sort the list in reverse alphabetical order. `duedate_asc`: Sort the list by due date (soonest first). `duedate_desc`: Sort the list by reverse due date (soonest last)."
   type: string
   default: "none"
+item_tap_action:
+  required: false
+  description: "Defines the behavior when an item's body is clicked. Options are: `edit` (opens the edit dialog), `toggle` (marks or unmarks the item as completed, hiding the edit dialog)."
+  type: string
+  default: "edit"  
 {% endconfiguration %}
 
 ### Examples

diff --git a/source/_docs/blueprint/selectors.markdown b/source/_docs/blueprint/selectors.markdown
@@ -1414,7 +1414,7 @@ would return ["Green"] and in the last example it returns ["g"].
 ## State selector
 
 The state selector shows a list of states for a provided entity of which
-one can be selected.
+one or more can be selected.
 
 ![Screenshot of an state selector](/images/blueprints/selector-state.png)
 
@@ -1427,10 +1427,16 @@ hide_states:
   description: The states to exclude from the list of options
   type: list
   required: false
+multiple:
+  description: >
+    Allows selecting multiple states. If set to `true`, the resulting value of
+    this selector will be a list instead of a single string value.
+  type: boolean
+  default: false  
 {% endconfiguration %}
 
 The output of this selector is the select state (not the translated or
-prettified name shown in the frontend).
+prettified name shown in the frontend), or a list of states if `multiple` is true.
 
 For example: `heat_cool`.
 

diff --git a/source/_integrations/airos.markdown b/source/_integrations/airos.markdown
@@ -19,8 +19,9 @@ Ubiquiti <abbr title="Ubiquity Internet Service Provider">UISP</abbr>-range of [
 
 A common use-case is establishing wireless <abbr title="Point-to-Point">PtP</abbr> or <abbr title="Point-to-Multi-Point">PtMP</abbr> links between buildings, remote sites, neighbours or even your shed. This is highly advantageous when traditional fiber-optic or copper network cabling is either impractical or the distance is too far for copper cabling. With <abbr title="Line-of-sight">LoS</abbr> between airOS devices, a stable and high-bandwidth "beam" can be established, eliminating any need for additional infrastructure. This can be an improvement over extending your WiFi coverage using meshing of Access Points, as meshing potentially reduces the capacity and performance of your WiFi network.
 
-There is currently support for the following plaforms within Home Assistant:
+There is currently support for the following platforms within Home Assistant:
 
+- [Binary sensor](#binary-sensor)
 - [Sensor](#sensor)
 
 This integration allows users to pull network metrics and statuses directly into their Home Assistant dashboards, enabling advanced automation, notifications, and comprehensive network oversight within their smart home ecosystem.
@@ -65,14 +66,46 @@ For stations in particular, they can operate in either a 'Bridge' or 'Router' ro
 
 The choice between Bridge and Router mode depends on the network architecture and whether the device is intended to extend an existing network (Bridge) or create a new subnet (Router).
 
-## Sensor
+## Binary sensor
+
+### Port forwarding
+
+Active if any port forwarding is enabled when operating in 'router' mode.
+
+### DHCP client
+
+Active if the device configured to use DHCP for its network settings, inactive if IP address is statically assigned.
+
+### DHCP server
+
+Active if the device itself is configured and acting as a DHCP server.
+
+### DHCPv6 server
+
+Active if the device itself is configured and acting as a DHCP server for IPv6.
+
+### PPPoE
 
-This integration exposes the following sensor entities for your airOS devices:
+Active if the device is configured for PPPoE and the PPPoE link state is active.
+
+## Sensor
 
 ### Network Role
 
 Indicates the role of the device in your network, either 'bridge' or 'router' (see [operating roles](#operating-roles) for more information.
 
+### Wireless Role
+
+Indicates the role of the device in relation to your wireless network, either 'Access point' or 'Station'.
+
+### Wireless Mode
+
+Indicates the mode your device is in 'point-to-point' just two devices connecting to eachother or 'point-to-multipoint' for multiple devices connecting to this device.
+
+### Wireless Distance
+
+The reported distance between your devices.
+
 ### Wireless Frequency
 
 The base frequency set for this device.
@@ -93,6 +126,10 @@ These sensors show the actual data transfer rate (receive and transmit) for this
 
 Performance in <abbr title="decibels">dB</abbr> for the device antenna. See [Gain](https://en.wikipedia.org/wiki/Gain_(antenna)) on Wikipedia.
 
+### Uptime
+
+Time since the device was last started.
+
 ## Data updates
 
 Data is polled from devices every 60 seconds.

diff --git a/source/_integrations/airq.markdown b/source/_integrations/airq.markdown
@@ -14,6 +14,7 @@ ha_domain: airq
 ha_config_flow: true
 ha_platforms:
   - sensor
+  - number
 ha_integration_type: hub
 ---
 
@@ -96,6 +97,10 @@ After the integration has been initialized, the user can configure any of the fo
 
 - **Clip negative values**. Default: `on`. For baseline calibration purposes, certain sensor values may briefly become negative. The default behavior is to clip such values to 0.
 
+## LED Control
+
+In addition to sensor readings, this integration exposes the brightness of the device’s LED strips as a `number` entity named `number.<device_name>_led_brightness`. You can set the brightness (0–100) manually from the Overview panel or in automations. Setting it to 0 will turn the LEDs off.
+
 ## Troubleshooting
 
 For troubleshooting or when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics) and restart the integration. As soon as the issue reoccurs stop the debug logging, which will trigger the download of the debug log file.

diff --git a/source/_integrations/awair.markdown b/source/_integrations/awair.markdown
@@ -7,8 +7,8 @@ ha_config_flow: true
 ha_release: 0.84
 ha_iot_class: Local Polling
 ha_codeowners:
-  - '@ahayworth'
-  - '@danielsjf'
+  - "@ahayworth"
+  - "@danielsjf"
 ha_domain: awair
 ha_platforms:
   - sensor
@@ -39,6 +39,7 @@ The integration will fetch data from each device. The following sensors are supp
 - Temperature
 - Humidity
 - Dew point
+- Absolute humidity
 - Carbon dioxide
 - Total volatile organic compounds
 - PM2.5 density