Merge branch 'current' into next

2025-07-23 01:06:52 +00:00 · 2021-10-27 16:32:19 +02:00 · 2021-10-27 16:32:19 +02:00 · f96a41c7a0
commit f96a41c7a0
parent f3c2a84f33 cf40e424e4
9 changed files with 41 additions and 36 deletions
--- a/source/_includes/common-tasks/flashing_n2_otg.md
+++ b/source/_includes/common-tasks/flashing_n2_otg.md
@ -14,34 +14,41 @@ To flash your eMMC using Petitboot and OTG-USB, you will need the following item

 #### Enabling SPI boot mode

-Remove the case of your ODROID-N2+
+To enable the SPI boot mode:

-![Photo of the removed case](/images/hassio/screenshots/case-removed.jpg)
+1. Power off the ODROID-N2+ by unplugging the power cable.
+1. Remove the case.

-Next, locate the toggle for boot mode and switch it from MMC to SPI.
+   ![Photo of the removed case](/images/hassio/screenshots/case-removed.jpg)

-![Photo of the SPI toggle switch](/images/hassio/screenshots/toggle_spi.jpg)
+1. Locate the toggle for boot mode and switch it from MMC to SPI.

-Connect a USB keyboard and HDMI connected monitor to your ODROID-N2+, and then connect power.
+   ![Photo of the SPI toggle switch](/images/hassio/screenshots/toggle_spi.jpg)
+   
+1. Connect the ODROID-N2+ directly to your computer via the USB-OTG port located on the front of the board.
+1. Connect a USB keyboard and a monitor (using HDMI) to your ODROID-N2+.
+1. Plug in the power cable to power on the ODROID-N2+.

 #### Enabling USB drive mode

-The ODROID-N2+ will now boot into a terminal. Select `Exit to shell` from the menu.
+After The ODROID-N2+ is set to SPI boot mode and powered on, it boots into a terminal. To enable the USB drive mode:

-![Exit to shell](/images/hassio/screenshots/exit-shell.png)
+1. Select `Exit to shell` from the menu.

-Use the following command at the console to confirm the storage device node:
+   ![Exit to shell](/images/hassio/screenshots/exit-shell.png)

-```bash
-ls /dev/mmc*
-```
+1. Use the following command at the console to confirm the storage device node:

-Set the storage device on the ODROID-N2+ as a mass storage device using `ums` (USB Mass storage mode)
-This will configure the ODROID-N2+ and OTG to act as a memory card reader.
+   ```bash
+   ls /dev/mmc*
+   ```

-```bash
-ums /dev/mmcblk0
-```
+1. Set the storage device on the ODROID-N2+ as a mass storage device using the `ums` command (USB Mass storage mode).
+This will configure the ODROID-N2+ and OTG to act as a memory card reader:
+
+   ```bash
+   ums /dev/mmcblk0
+   ```

 #### Flashing Home Assistant

--- a/source/_integrations/cover.template.markdown
+++ b/source/_integrations/cover.template.markdown
@ -70,7 +70,7 @@ cover:
        required: false
        type: template
      availability_template:
-        description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`.
+        description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
        required: false
        type: template
        default: true
--- a/source/_integrations/edimax.markdown
+++ b/source/_integrations/edimax.markdown
@ -50,17 +50,15 @@ Starting with [version 2 of the firmware](https://www.edimax.com/edimax/download
 {% raw %}

 ```yaml
-  - platform: template
-    sensors:
-      edimax_current_power:
-        friendly_name: Edimax Current power consumption
-        unit_of_measurement: "W"
-        value_template: "{{ state_attr('switch.edimax_smart_plug',  'current_power_w') | replace('None', 0) }}"
+template:
+  - sensor:
+    - name: Edimax Current power consumption
+      unit_of_measurement: "W"
+      state: "{{ state_attr('switch.edimax_smart_plug', 'current_power_w') | default(0, true) }}"
      
-      edimax_total_power:
-        friendly_name: Edimax Accumulated daily power consumption
-        unit_of_measurement: "kWh"
-        value_template: "{{ state_attr('switch.edimax_smart_plug',  'today_energy_kwh') | replace('None', 0) }}"
+    - name: Edimax Accumulated daily power consumption
+      unit_of_measurement: "kWh"
+      state: "{{ state_attr('switch.edimax_smart_plug', 'current_power_w') | default(0, true) }}"
 ```

 {% endraw %}
--- a/source/_integrations/fan.template.markdown
+++ b/source/_integrations/fan.template.markdown
@ -94,7 +94,7 @@ fan:
        required: false
        type: template
      availability_template:
-        description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`.
+        description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
        required: false
        type: template
        default: true
--- a/source/_integrations/light.template.markdown
+++ b/source/_integrations/light.template.markdown
@ -145,7 +145,7 @@ light:
        required: false
        type: template
      availability_template:
-        description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`.
+        description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
        required: false
        type: template
        default: true
--- a/source/_integrations/lock.template.markdown
+++ b/source/_integrations/lock.template.markdown
@ -56,7 +56,7 @@ lock:
    required: true
    type: template
  availability_template:
-    description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`.
+    description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
    required: false
    type: template
    default: true
--- a/source/_integrations/switch.template.markdown
+++ b/source/_integrations/switch.template.markdown
@ -60,7 +60,7 @@ switch:
        type: template
        default: optimistic
      availability_template:
-        description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`.
+        description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
        required: false
        type: template
        default: true
--- a/source/_integrations/template.markdown
+++ b/source/_integrations/template.markdown
@ -236,7 +236,7 @@ select:
      required: false
      type: template
    availability:
-      description: Defines a template to get the `available` state of the entity. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the component will always be `available`.
+      description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
      required: false
      type: template
      default: true
@ -599,7 +599,7 @@ sensors:
          required: true
          type: template
        availability_template:
-          description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`.
+          description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
          required: false
          type: template
          default: true
--- a/source/_integrations/vacuum.template.markdown
+++ b/source/_integrations/vacuum.template.markdown
@ -65,7 +65,7 @@ vacuum:
            required: true
            type: template          
      availability_template:
-        description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`.
+        description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
        required: false
        type: template
        default: true