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

FR/question: Sensor for current driver profile in use? #83

Closed
3 tasks done
fhteagle opened this issue May 13, 2024 · 2 comments
Closed
3 tasks done

FR/question: Sensor for current driver profile in use? #83

fhteagle opened this issue May 13, 2024 · 2 comments

Comments

@fhteagle
Copy link

Checklist

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

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

Is there an existing sensor for which driver profile is in currently in use? I.e. if the car has an "Alice" profile, and a "Bob" profile, can we get which one is selected at that time? Obviously controlling it would be even better (i.e. to pre-set the driver seat position before departure), but even being able to read which profile is active could help with intelligently routing notifications. I looked through the Tesla Fleet API doc and could not find this data exposed, but wondered if there is a field that is exposed but not documented?

Additional context

No response

@Bre77
Copy link
Contributor

Bre77 commented May 14, 2024

This definitely was a field in the owners API, but it would seem it's not on the Fleet API, we simply get a user present Boolean, rather than the users ID.

As such, I don't think this is possible anymore.

@fhteagle
Copy link
Author

Yeah it looks like Tesla forgot this when implementing the Fleet API. Boo.

I'll mark it "Won't Fix" for now, but hopefully they add that back in the future...

@fhteagle fhteagle closed this as not planned Won't fix, can't repro, duplicate, stale May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants