-
Notifications
You must be signed in to change notification settings - Fork 102
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
Support vehicle data over BLE #330
Conversation
7a1121d
to
7cd4d85
Compare
Clients indicate that they support encrypted vehicle responses by setting a flag bit in the request. The flag is authenticated but ignored by vehicles that do not support encryption. Clients should always set the flag when possible. In the future, vehicles may refuse to respond to certain requests if the client does not support this feature.
Vehicle Data commands are intended to work over BLE. The Fleet API vehicle data endpoint is more efficient when using an Internet connection.
7cd4d85
to
eb26f88
Compare
Thanks for this addition! I don't see the DriveState returning the vehicle's location. Any chance we can obtain the vehicle's location via BLE, or will this data remain available via API-only? vehicle-command/pkg/protocol/protobuf/vehicle.proto Lines 172 to 192 in eb26f88
|
@kirichkov The vehicle location API is undergoing some refactoring; I hope to add support to the SDK once the API is stable. |
Thanks for the clarification! |
Description
Adds support for fetching and decrypting vehicle data over BLE. Some types of vehicle data are not available prior to 2024.38.
Fixes #229 #52
Type of change
Please select all options that apply to this change:
Checklist:
Confirm you have completed the following steps: