Skip to content
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.

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

feat: map for entities and multiple map services #196

Merged
merged 1 commit into from
Feb 22, 2019

Conversation

maxandersen
Copy link
Contributor

Why:

  • openstreetmap isn't always the best option.
  • there are more than just configuration with location info.

This change addreses the need by:

  • introduce a --service option to let you choose which
    map service to use. currently: openstreetmap, google and bing
    implemented
  • add optional entity parameter to lookup and it has
    latitiude and longitude in its state it will be mapped.
  • bing has extra feature of allowing showing a name/label, here
    friendly_name is used otherwise entity_id

Future idea: allow to map multiple points, can be done as directions
in google but Bing has better support.

Why:

 * openstreetmap isn't always the best option.
 * there are more than just configuration with location info.

This change addreses the need by:

 * introduce a `--service` option to let you choose which
   map service to use. currently: openstreetmap, google and bing
   implemented
 * add optional entity parameter to lookup and it has
   latitiude and longitude in its state it will be mapped.
 * bing has extra feature of allowing showing a name/label, here
   `friendly_name` is used otherwise `entity_id`

Example usage:

`hass-cli map person.max`
`hass-cli --service bing device_tracker.maxs_phone`

Future idea: allow to map multiple points, can be done as directions
in google but Bing has better support.
@maxandersen maxandersen merged commit 542c0db into home-assistant-ecosystem:dev Feb 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants