Summary of feedback message from tesla-control

[raphmur]

I am logging all the messages brought by the tesla-control commands... This could be used to improve loop performance:

charge-set-limit:

• Failed to execute command: car could not execute command: already_set --> Detect the message and break the loop

charging-start:

• Failed to execute command: car could not execute command: is_charging --> Detect the message and break the loop

Any command:

• Error: failed to find BLE beacon for [VIN] (SxxxxxxxxC): can't scan: context deadline exceeded**** --> Wait for retry delay and relaunch command. If counter >=5: log error "failed to send command to the car. Is the car awake and sufficiently close to bluetooth device?"
• Error: context deadline exceeded --> Same
• Error: failed to find BLE beacon for [VIN](SxxxxxxxxxC): can't dial: can't dial: connection canceled --> Same? Maybe increase the delay between commands

To be completed...

[epenet]

I would say that Failed to execute command: car could not execute command: XXX could be generic. The car has rejected the command, there is no need to try again, regardless of XXX.

[raphmur]

Yes right Indeed Though capturing the message to update an mqtt entity could be useful

[epenet]

Another one that doesn't need a retry:

Attempt 1/5 to send command
Error loading credentials: could not load key: permission denied
tesla-control send command failed exit status 1. Retrying in 5
Attempt 2/5 to send command
Error loading credentials: could not load key: permission denied
...

[raphmur]

This should solve this topic: https://github.com/tesla-local-control/tesla-local-control-addon/pull/40

[raphmur]

PR https://github.com/tesla-local-control/tesla-local-control-addon/pull/40 merged. Confirmed closed