Skip to content

Proximity List and Configurable Unit of Measure #698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 8, 2016
Merged

Proximity List and Configurable Unit of Measure #698

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8b0cd89
Proximity List and Configurable Unit of Measure
Jul 30, 2016
8288355
Add type to code segment
Jul 30, 2016
1c474fc
Add default value to markdown
Jul 30, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions source/_components/proximity.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,7 @@ proximity:
- device_tracker.eleanorsiphone
- device_tracker.tsiphone
tolerance: 50
unit_of_measurement: mi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this one still relevant?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It allows you to have the proximity in a different unit than the
application wide unit system. It should be marked optional though

On Aug 7, 2016 6:59 PM, "Paulus Schoutsen" notifications@github.com wrote:

In source/_components/proximity.markdown
#698 (comment)
:

@@ -47,6 +47,7 @@ proximity:
- device_tracker.eleanorsiphone
- device_tracker.tsiphone
tolerance: 50

  • unit_of_measurement: mi

Is this one still relevant?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant.io/pull/698/files/1c474fca52a0c0fce5e2fb8878861b14b44eaa2d#r73813102,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZaqo70UfmcNePJ5AWkrsp292lE4vks5qdn-DgaJpZM4JYthw
.

```

Configuration variables:
Expand All @@ -55,4 +56,19 @@ Configuration variables:
- **ignored_zones** array (*Optional*): Where proximity is not calculated for a device (either the device being monitored or ones being compared (e.g. work or school).
- **devices** array (*Optional*): A list of devices to compare location against to check closeness to the configured zone.
- **tolerance** (*Optional*): The tolerance used to calculate the direction of travel in meters (m) to filter out small GPS coordinate changes.
- **unit_of_measurement** (*Optional*): The unit of measurement for distance. Valid values are (km, m, mi, ft) [kilometers, meters, miles and feet respectfully]. The default value is kilometers.

To add multiple proximity components, simply use a list in your `configuration.yaml` file:

```yaml
# Example configuration.yaml entry
proximity:
- zone: home
devices:
- device_tracker.tsiphone
tolerance: 50
- zone: work
devices:
- device_tracker.elanorsiphone
tolerance: 10
```