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

are reliable acks enabled by default? #318

Open
jbanyer opened this issue Jan 22, 2025 · 3 comments
Open

are reliable acks enabled by default? #318

jbanyer opened this issue Jan 22, 2025 · 3 comments
Labels
bug Something isn't working firmware priority:medium

Comments

@jbanyer
Copy link

jbanyer commented Jan 22, 2025

I'm experiencing lost signals (see #319), and am trying the reliable acks as a possible mitigation.

However I seem to get the following log messages regardless of whether reliable_ack_sources is set in server_config.json or not.

tesla-fleet-telemetry    | {"context":"fleet-telemetry","level":"debug","msg":"message_respond","record_type":"V","response_type":"ack","time":"2025-01-22T00:46:41Z","txid":"78ae54a58800468194dc95-000000397"}

Are reliable acks enabled by default?

@patrickdemers6
Copy link
Collaborator

If reliable acks are not enabled for any data providers, the reliable ack is sent immediately.

Unfortunately - and we have a documentation gap here - the vehicle does not change behavior (i.e. resend a message) based on reliable acks. Creating a ticket internally to properly handle acks.

@dirkbonhomme
Copy link

Is there a use case today for enabling reliable ack if it doesn't change the car behavior?

@patrickdemers6
Copy link
Collaborator

No reason to enable, though I'd recommend it as there's no harm. Future proofing your setup for when the vehicle properly handles reliable acks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working firmware priority:medium
Projects
None yet
Development

No branches or pull requests

3 participants