-
Notifications
You must be signed in to change notification settings - Fork 6
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
Service call to navigation_request endpoint gives various errors #84
Comments
timestamp_ms: >- |
I'm also trying to set up sending addresses to the car.
|
Ok that's definitely a bug, I'll take a look and get that fixed in the next version. |
I had this working both from command line and from HA Action, but forgot to document my work. Posting this here for now, will update when I get the HA YAML correct... This is the syntax from the old Owner API, and appears to be the same with the new Fleet API. Note the timestamp is in milliseconds since the UNIX epoch, not whole seconds (just append three zeros to seconds-based timestamps). The API does not seem very picky about the recency or future-ness of the timestamp, though, just that it has a reasonable number of digits.
|
Checklist
Describe the issue
Attempting to use the teslemetry.navigation_request service call in HA results in various errors depending on what values are filled or not
Reproduction steps
Examples of service call YAML variations that I tried:
Debug logs
The text was updated successfully, but these errors were encountered: