mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-20 15:56:51 +00:00
Merge branch 'current' into next
This commit is contained in:
commit
f3e195f7d9
@ -82,7 +82,7 @@ automation:
|
||||
|
||||
<div class='note'>
|
||||
Listing above and below together means the numeric_state has to be between the two values.
|
||||
In the example above, the trigger would fire if a numeric_state goes to 17.1-24.9 (from 17 or below, or 25 or above).
|
||||
In the example above, the trigger would fire if a numeric_state goes to 17.1-24.9 (from strict below 17, or strict above 25).
|
||||
</div>
|
||||
|
||||
The `for:` can also be specified as `HH:MM:SS` like this:
|
||||
@ -378,13 +378,13 @@ Note that a given webhook can only be used in one automation at a time. That is,
|
||||
|
||||
### Zone trigger
|
||||
|
||||
Zone trigger fires when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/gpslogger/), the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).
|
||||
Zone trigger fires when an entity is entering or leaving the zone. The entity can be either a person, or a device_tracker. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/gpslogger/), the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
trigger:
|
||||
platform: zone
|
||||
entity_id: device_tracker.paulus
|
||||
entity_id: person.paulus
|
||||
zone: zone.home
|
||||
# Event is either enter or leave
|
||||
event: enter # or "leave"
|
||||
|
@ -50,6 +50,14 @@ timer:
|
||||
|
||||
Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your timer and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
|
||||
|
||||
## Possible States
|
||||
|
||||
| State | Description |
|
||||
| ----- | ----------- |
|
||||
| `idle` | Timer is idle because the timer finished, was canceled or was never started |
|
||||
| `active` | Timer is currently running because it was (re-)started |
|
||||
| `paused` | Timer is paused because it was paused |
|
||||
|
||||
## Events
|
||||
|
||||
| Event | Description |
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -52,7 +52,7 @@ We will need a few things to get started with installing Home Assistant. The Ras
|
||||
1. Put the SD card in your card reader.
|
||||
2. Open balenaEtcher, select the Home Assistant image and flash it to the SD card.
|
||||
3. Unmount the SD card and remove it from your card reader.
|
||||
4. Follow this step if you want to configure Wi-Fi or a static IP address (this step requires a USB stick). Otherwise, move to step 5.
|
||||
4. The most reliable networking setup for your Raspberry Pi is to connect it using an Ethernet cable, however, if you want to configure Wi-Fi or a static IP address (this step requires a USB stick) you can try this:
|
||||
- Format a USB stick to FAT32 with the volume name `CONFIG`.
|
||||
- Create a folder named `network` in the root of the newly-formatted USB stick.
|
||||
- Within that folder, create a file named `my-network` without a file extension.
|
||||
|
Loading…
x
Reference in New Issue
Block a user