jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 17:27:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2021-10-27 16:32:19 +02:00
commit f96a41c7a0
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
9 changed files with 41 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
source/_includes/common-tasks/flashing_n2_otg.md
View File

@ -14,34 +14,41 @@ To flash your eMMC using Petitboot and OTG-USB, you will need the following item
#### Enabling SPI boot mode #### 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 #### 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 1. Use the following command at the console to confirm the storage device node:
ls /dev/mmc*
```
Set the storage device on the ODROID-N2+ as a mass storage device using `ums` (USB Mass storage mode) ```bash
This will configure the ODROID-N2+ and OTG to act as a memory card reader. ls /dev/mmc*
```
```bash 1. Set the storage device on the ODROID-N2+ as a mass storage device using the `ums` command (USB Mass storage mode).
ums /dev/mmcblk0 This will configure the ODROID-N2+ and OTG to act as a memory card reader:
```
```bash
ums /dev/mmcblk0
```
#### Flashing Home Assistant #### Flashing Home Assistant

2
source/_integrations/cover.template.markdown
View File

@ -70,7 +70,7 @@ cover:
required: false required: false
type: template type: template
availability_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 required: false
type: template type: template
default: true default: true

18
source/_integrations/edimax.markdown
View File

@ -50,17 +50,15 @@ Starting with [version 2 of the firmware](https://www.edimax.com/edimax/download
{% raw %} {% raw %}
```yaml ```yaml
- platform: template template:
sensors: - sensor:
edimax_current_power: - name: Edimax Current power consumption
friendly_name: Edimax Current power consumption unit_of_measurement: "W"
unit_of_measurement: "W" state: "{{ state_attr('switch.edimax_smart_plug', 'current_power_w') | default(0, true) }}"
value_template: "{{ state_attr('switch.edimax_smart_plug', 'current_power_w') | replace('None', 0) }}"
edimax_total_power: - name: Edimax Accumulated daily power consumption
friendly_name: Edimax Accumulated daily power consumption unit_of_measurement: "kWh"
unit_of_measurement: "kWh" state: "{{ state_attr('switch.edimax_smart_plug', 'current_power_w') | default(0, true) }}"
value_template: "{{ state_attr('switch.edimax_smart_plug', 'today_energy_kwh') | replace('None', 0) }}"
``` ```
{% endraw %} {% endraw %}

2
source/_integrations/fan.template.markdown
View File

@ -94,7 +94,7 @@ fan:
required: false required: false
type: template type: template
availability_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 required: false
type: template type: template
default: true default: true

2
source/_integrations/light.template.markdown
View File

@ -145,7 +145,7 @@ light:
required: false required: false
type: template type: template
availability_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 required: false
type: template type: template
default: true default: true

2
source/_integrations/lock.template.markdown
View File

@ -56,7 +56,7 @@ lock:
required: true required: true
type: template type: template
availability_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 required: false
type: template type: template
default: true default: true

2
source/_integrations/switch.template.markdown
View File

@ -60,7 +60,7 @@ switch:
type: template type: template
default: optimistic default: optimistic
availability_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 required: false
type: template type: template
default: true default: true

4
source/_integrations/template.markdown
View File

@ -236,7 +236,7 @@ select:
required: false required: false
type: template type: template
availability: 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 required: false
type: template type: template
default: true default: true
@ -599,7 +599,7 @@ sensors:
required: true required: true
type: template type: template
availability_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 required: false
type: template type: template
default: true default: true

2
source/_integrations/vacuum.template.markdown
View File

@ -65,7 +65,7 @@ vacuum:
required: true required: true
type: template type: template
availability_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 required: false
type: template type: template
default: true default: true