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-21 16: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-06-30 16:52:30 +02:00
commit e10d6c3f95
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_integrations/device_tracker.markdown
View File

@ -104,8 +104,8 @@ The `device_tracker.see` service can be used to manually update the state of a d
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `dev_id` | no | The second half of the `entity_id`, for example `tardis` for `device_tracker.tardis` |
| `location_name` | no | The location, `home`, `not_home`, or the name of the zone |
| `dev_id` | no | The `object_id`, for example `tardis` for `device_tracker.tardis` |
| `location_name` | yes | The location, `home`, `not_home`, or the name of the zone |
| `host_name` | yes | The hostname of the device tracker |
| `mac` | yes | The MAC address of the entity (only specify if you're updating a network based tracker) |
| `gps` | yes | If you're providing a location, for example `[51.513845, -0.100539]` |

2
source/_integrations/statistics.markdown
View File

@ -14,7 +14,7 @@ ha_platforms:
- sensor
---
The `statistics` sensor platform consumes the state from other sensors. It exports the `mean` value as state and the following values as attributes: `count`, `mean`, `median`, `quantiles`, `stdev`, `variance`, `total`, `min_value`, `max_value`, `min_age`, `max_age`, `change`, `average_change` and `change_rate`. If the source is a binary sensor then only state changes are counted.
The `statistics` sensor platform consumes the state from other sensors. It exports the `mean` value as state and the following values as attributes: `count`, `mean`, `median`, `quantiles`, `standard_deviation`, `variance`, `total`, `min_value`, `max_value`, `min_age`, `max_age`, `change`, `average_change` and `change_rate`. If the source is a binary sensor then only state changes are counted.
Assuming the [`recorder`](/integrations/recorder/) integration is running (either configured explicitly or as part of a meta-integration/dependency, e.g., [`default_config`](/integrations/default_config/), [`history`](/integrations/history/), etc.), historical sensor data is read from the database on startup and is available immediately after a restart of the platform. If the [`recorder`](/integrations/recorder/) integration is *not* running, it can take time for the sensor to start reporting data because some attribute calculations require more than one value.