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.

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

Jump to bottom

Distance to arrival and Tracker Route show up in Watchman Report as Unavailable and Unknown respectively #152

Open
3 tasks done
rdperkins opened this issue Nov 9, 2024 · 7 comments
Open
3 tasks done

Distance to arrival and Tracker Route show up in Watchman Report as Unavailable and Unknown respectively #152

rdperkins opened this issue Nov 9, 2024 · 7 comments

Comments

@rdperkins
Copy link

Checklist

  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of any previous issues..

Describe the issue

The garage door opener automation depends on the distance_to_arrival entity value and Watchman shows it as unavailable. This I'd like fixed. The tracker route I don't care about Except it shows up in the Watchman Report which is annoying. Thanks for your help. The full list of Watchman items related to the Tesla are below in the reproduction steps. Scarlet is the name of my red Tesla :).

Reproduction steps

  1. Set a destination in the Tesla and it didn't change anything.
  2. sensor.scarlet_distance_to_arrival [unavail]
  3. device_tracker.scarlet_route [unknown]
  4. proximity.home_tesla [missing]

Debug logs

No response
@Bre77
Copy link
Member

Bre77 commented Nov 9, 2024

Can you please put a destination into your vehicle, wait 30 seconds, then generate a diagnostic and attach it here.

The sensors you're describing are meant to be unavailable when there is no destination, so if you have configured one in your vehicle and they are not working we will need to figure out why.

@rdperkins
Copy link
Author

rdperkins commented Nov 13, 2024 via email

@Bre77
Copy link
Member

Bre77 commented Nov 13, 2024

Its in the three dot menu of the integration page, or on the device info
image

https://www.home-assistant.io/integrations/diagnostics/

@rdperkins
Copy link
Author

rdperkins commented Nov 16, 2024 via email

@rdperkins
Copy link
Author

rdperkins commented Nov 21, 2024 via email

@Bre77
Copy link
Member

Bre77 commented Nov 23, 2024 •
edited
Loading

Did you receive the email with the attached diagnostics? I sent it on the 16th.

It does not appear to be on the GitHub issue, so I think you'll have to open the issue to attach it. Email seemly doesn't work

@rdperkins
Copy link
Author

No, I didn't receive your email, but am attaching the diagnostic below.
config_entry-teslemetry-e7fe7d7557a3d552b23a9d972d5cb3a9.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Bre77 @rdperkins