Novy cooked hood integration

source/_dashboards/energy.markdown

@@ -387,6 +387,21 @@ The grid neutrality gauge card represents your energy dependency. If the needle
 type: energy-grid-neutrality-gauge
 ```
 
+## Grid energy balance
+
+<p class='img'>
+  <img src='/images/dashboards/energy/grid-balance.png' alt='Screenshot of the grid energy balance card'>
+  Screenshot of the Grid energy balance card.
+</p>
+
+The grid energy balance card shows your net grid energy as an equation: imported energy minus exported energy. A positive value means you imported more energy from the grid than you exported. A negative value means you exported more energy to the grid than you imported. It includes a visual bar gauge that represents the ratio between imported and exported energy, with the bar filling from a center line toward the dominant direction.
+
+### Example
+
+```yaml
+type: energy-grid-balance
+```
+
 ## Solar consumed gauge
 
 <p class='img'>

source/_dashboards/shortcut.markdown

@@ -0,0 +1,144 @@
+---
+type: card
+title: "Shortcut card"
+sidebar_label: Shortcut
+description: "The shortcut card gives you a quick way to trigger an action from your dashboard, such as navigating to a page, opening a URL, launching the voice assistant, or performing an action."
+related:
+  - docs: /dashboards/actions/
+    title: Card actions
+  - docs: /dashboards/tile/
+    title: Tile card
+  - docs: /dashboards/cards/
+    title: Dashboard cards
+---
+
+The shortcut card gives you a quick way to trigger an action from your dashboard. You can use it to navigate to another page, open a URL, launch the voice assistant, or perform an action. It renders as a tile, so it fits nicely alongside other tile cards on your dashboard.
+
+The label, icon, and color are automatically resolved from the action you configure. For example, if you navigate to a dashboard view, the shortcut picks up the view's title and icon. You can override any of these values if you want something different.
+
+{% include dashboard/edit_dashboard.md %}
+
+## Card settings
+
+Most options can be configured in the UI.
+
+{% configuration_basic %}
+Label:
+  description: The text displayed on the card. If left empty, the label is resolved automatically from the action. For example, the view title for a navigation action, or **Assist** for an assist action.
+Description:
+  description: An optional secondary line displayed under the label.
+Icon:
+  description: The icon displayed on the card. If left empty, the icon is resolved automatically from the action.
+Color:
+  description: The color of the icon and background accent. Accepts a [color token](#available-colors) or a hex color code. Defaults to the primary color of your theme.
+Vertical:
+  description: Displays the icon above the label instead of next to it.
+Tap action:
+  description: The action taken when the card is tapped. For more information, see the [action documentation](/dashboards/actions/#tap-action).
+Hold action:
+  description: The action taken when the card is tapped and held. For more information, see the [action documentation](/dashboards/actions/#hold-action).
+Double tap action:
+  description: The action taken when the card is double-tapped. For more information, see the [action documentation](/dashboards/actions/#double-tap-action).
+{% endconfiguration_basic %}
+
+## YAML configuration
+
+The following YAML options are available when you use YAML mode or prefer to use YAML in the code editor in the UI.
+
+{% configuration %}
+type:
+  required: true
+  description: "`shortcut`"
+  type: string
+label:
+  required: false
+  description: The text displayed on the card. If not set, the label is resolved automatically from the configured `tap_action`.
+  type: string
+description:
+  required: false
+  description: An optional secondary line displayed under the label.
+  type: string
+icon:
+  required: false
+  description: The icon displayed on the card. If not set, the icon is resolved automatically from the configured `tap_action`.
+  type: string
+color:
+  required: false
+  description: The color of the icon and background accent. Accepts a [color token](#available-colors) or hex color code.
+  type: string
+  default: primary
+vertical:
+  required: false
+  description: Displays the icon above the label instead of next to it.
+  type: boolean
+  default: false
+tap_action:
+  required: true
+  description: The action taken on card tap. For more information, see the [action documentation](/dashboards/actions/#tap-action).
+  type: map
+hold_action:
+  required: false
+  description: The action taken on card tap and hold. For more information, see the [action documentation](/dashboards/actions/#hold-action).
+  type: map
+double_tap_action:
+  required: false
+  description: The action taken on card double tap. For more information, see the [action documentation](/dashboards/actions/#double-tap-action).
+  type: map
+{% endconfiguration %}
+
+## Examples
+
+Navigate to a dashboard view. The label and icon are taken from the view:
+
+```yaml
+type: shortcut
+tap_action:
+  action: navigate
+  navigation_path: /lovelace/kitchen
+```
+
+Open an external URL with a custom label and icon:
+
+```yaml
+type: shortcut
+label: "Home Assistant docs"
+icon: mdi:book-open-variant
+tap_action:
+  action: url
+  url_path: https://www.home-assistant.io
+```
+
+Launch the voice assistant:
+
+```yaml
+type: shortcut
+tap_action:
+  action: assist
+```
+
+Perform an action, with a custom color and a description:
+
+```yaml
+type: shortcut
+label: "Good night"
+description: "Turn off all lights"
+color: indigo
+tap_action:
+  action: perform-action
+  perform_action: script.good_night
+```
+
+Vertical layout:
+
+```yaml
+type: shortcut
+label: "Kitchen"
+vertical: true
+tap_action:
+  action: navigate
+  navigation_path: /lovelace/kitchen
+```
+
+## Available colors
+
+The following colors are available to colorize the shortcut card: `primary`, `accent`, `disabled`, `red`, `pink`, `purple`, `deep-purple`, `indigo`, `blue`, `light-blue`, `cyan`, `teal`, `green`, `light-green`, `lime`, `yellow`, `amber`, `orange`, `deep-orange`, `brown`, `grey`, `blue-grey`, `black`, `white`, or any hex color code (for example, `#93c47d`).

source/_dashboards/statistics-graph.markdown

@@ -24,6 +24,11 @@ Screenshot of the statistics graph card with no metered entities and `chart_type
 Screenshot of the statistics graph card with a metered entity and `chart_type` `bar`.
 </p>
 
+<p class='img'>
+<img src='/images/dashboards/statistics_graph_bar_stack.png' alt='Screenshot of the statistics graph card as a bar chart with stacked values'>
+Screenshot of the statistics graph card with values stacked using `chart_type` `bar-stack`.
+</p>
+
 Statistics are gathered every 5 minutes and also hourly for sensors with a state_class of measurement, total or total_increasing. The 5-minute statistics will be retained for the duration set in the [recorder configuration](/integrations/recorder/#purge_keep_days), and hourly statistics will be retained indefinitely. It will either keep the <abbr title="Minimum">`min`</abbr>, <abbr title="Maximum">`max`</abbr>, and <abbr title="Average">`mean`</abbr> of a sensor's value for a specific hour or the <abbr title="Total">`sum`</abbr> for a metered entity.
 
 If your sensor doesn't work with statistics, check [this](/more-info/statistics/).
@@ -52,19 +57,19 @@ days_to_show:
   default: 30
 chart_type:
   required: false
-  description: If the graph should be rendered as a `bar` or a `line` chart.
+  description: If the graph should be rendered as a `bar` or a `line` chart. Alternatively, using `bar-stack` or `line-stack` select stacked versions of the chart.
   type: string
 stat_types:
   required: false
-  description: The statistics types to render. `min`, `max`, `mean`, `sum`, `state`, `change`
+  description: The statistics types to render. `min`, `max`, `mean`, `sum`, `state`, `change`. When using stacked charts, it is recommended to select only one option.
   type: list
 title:
   required: false
   description: The card title.
   type: string
 period:
   required: false
-  description: The period of the rendered graph. `5minute`, `hour`, `day`, `week`, `month` or `year`. If `energy_date_selection` is true, and `period` is not defined, the chart period will auto-select between month/day/hour based on the selected date range.
+  description: The period of the rendered graph. `5minute`, `hour`, `day`, `week`, `month` or `year`. If `energy_date_selection` is true, and `period` is not defined or set to `auto`, the chart period will auto-select between month/day/hour based on the selected date range.
   type: string  
 hide_legend:
   required: false

source/_integrations/airos.markdown

@@ -14,6 +14,7 @@ ha_platforms:
   - button
   - diagnostics
   - sensor
+  - update
 ha_integration_type: device
 ha_quality_scale: platinum
 ha_dhcp: true
@@ -28,6 +29,7 @@ There is currently support for the following platforms within Home Assistant:
 - [Binary sensor](#binary-sensor)
 - [Button](#button)
 - [Sensor](#sensor)
+- [Update](#update)
 
 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.
 
@@ -111,9 +113,18 @@ 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.
 
+## Update
+
+Firmware updates are supported for devices running firmware v8. A link to the release notes is provided, and we strongly recommend reviewing them to avoid unforeseen consequences. Starting an update from Home Assistant will download the available firmware and begin installation on the device.
+
+{% important %}
+Updating firmware will interrupt connectivity. Always review the release notes to confirm compatibility and follow any upgrade order that Ubiquiti recommends for your local and remote devices.
+Update the correct side first to avoid losing access to a remote device, especially when it is physically far away or difficult to troubleshoot on-site.
+{% endimportant %}
+
 ## Data updates
 
-Data is polled from devices every 60 seconds.
+Device data is polled every 60 seconds. Firmware availability is checked once per day.
 
 ## Examples