esphome / esphome/feature-requests

GPS Component - Home Assistant device_tracker integration.

Open
#2,400 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

Describe the problem you have/What new integration you would like

I would like the GPS Component to return an additional formatted string made up of the latitude and longitude states to be used in a device_tracker. If you could also call the device_tracker.see service, that would be helpful.

Please describe your use case for this integration and alternatives you've tried:

It's difficult to implement a device tracker in Home Assistant from the ESPHome GPS Component. An alternative would be to create a text sensor to call device_tracker.see service and send it {"[ " + to_string(id(my_lat).state) + " , " + to_string(id(my_lon).state) + " ]"};

Additional context

This would make the GPS Component, Home Assistant integration much more user-friendly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the GPS Component and the Home Assistant device_tracker integration, then review the device_tracker.see service and the text-sensor workaround described in the issue. Done means the component supports the requested latitude/longitude representation and the device_tracker integration can use it as described.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.