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

Key name in dashboard? Using two instances for the same car? #29

Closed
dglaude opened this issue Jul 15, 2024 · 3 comments
Closed

Key name in dashboard? Using two instances for the same car? #29

dglaude opened this issue Jul 15, 2024 · 3 comments
Labels
question Further information is requested

Comments

@dglaude
Copy link
Contributor

dglaude commented Jul 15, 2024

This is more a support question.

I have one working setup on a first Pi, but I try to setup a new Pi to have all the software component on a single machine.

However, doing the key setup with /dashboard on the second Pi failed with Error: failed to connect to vehicle (A): context deadline exceeded (worked fine on the first Pi). I wonder if it could be related to a "friendly key name" and since you cannot specify it, it would be the same for both attempt?

If such a thing as a "key name", then it should be presented in the dashboard with a good default name.

If everything else fail, maybe I will just try to reuse the key from the other Pi.

@dglaude
Copy link
Contributor Author

dglaude commented Jul 17, 2024

This whole issue was based on the wrong assumption that either owner or cloud_key from the following line was the name of the key:
tesla-control -vin YOUR_VIN -ble add-key-request public.pem owner cloud_key

Because nothing was working anymore, I tried on my NUC (creating the container or running TeslaBleHttpProxy => fail again) then I had success with tesla-control and that is where I figured that nor owner nor cloud_key could be changed... well I was considering if charging_manager could be appropriate in place of owner.

Now my Pi is working again, and I don't have a clue what changed.

Maybe this issue could be closed now, or there is something to discuss, like way to detect communication problem and trigger an alarm.

@wimaha
Copy link
Owner

wimaha commented Jul 17, 2024

You can use multiple cars with the same key!
It is not possible to change the name of the key. They named "unknown" or something like this in the car. To rename the key you must use the fleet api.

Error: failed to connect to vehicle (A): context deadline exceeded This error could be that your car was sleeping. You have to manually wake the car during the key setup.

@wimaha wimaha added the question Further information is requested label Jul 17, 2024
@dglaude
Copy link
Contributor Author

dglaude commented Jul 21, 2024

Thanks for the response, my problem seems to be BLE/Wakeup related, very similar to what is experienced in #6.
The issue could be something related to the car and waking up. I'll keep reading and investigate.

@dglaude dglaude closed this as completed Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants