can't connect to vehicle after reboot

[frandess]

From time to time, my raspi is hanging until I reboot it. After that, the bleProxy can't reestablish the connection to the car.
The only way that I found to fix this, is to delete the keys (certs), regenerate them and configure them from scratch, including tapping the nfc card on the console, etc.
logs were like: "failed to connect to vehicle (A): context deadline exceeded"

Is there anything else that I could have done to fix this? Is that a bug (should this be an issue)?

[frandess]

@wimaha what do you think?

[wimaha]

Sounds like a connection issue. Can you bring your device more near to the vehicle?

[frandess]

I don't think the distance is the problem, as the antenna ends like 1m in front of the vehicle.
Also I think I remember having checked that the first time that this happened and the bluetooth utility on the raspi still found the vehicle (when scanning for devices).
I can double check that the next time this happens. Unfortunately the whole thing is not reproducible on purpose and as I had not configured the logs to survive a restart, I cannot provide them yet.

[joeapxc]

Interesting, you seem to have the same problem as me. After some time, it just gets unresponsive and says "context deadline exceeded". Things i was able to spot:

• It only happens when not using the proxy for a bit of time (for example while being at work with the vehicle, coming back and its not responsive). When i use it for a long time period (for example weekend solar charging) it does work flawlessly.
• A reboot of the PC running the proxy helps, it works again
• I can still view the logs, the machine does not freeze itself

The only difference is i do not need to set up the whole key process again, simple VM reboot does the job for me. I can live with it as i have set up automatic reboots of the vm, scheduled at certain times i come home so it is always ready when i need it.

I also just updated from 2.0.3 to the latest 2.1.2 and will check now if anything has changed. Disabled the schedules and test if it will stay responsive or not. I will keep you updated, if its still a concern for you. Maybe updating will also fix your issue.

Greetings
Joe

[joeapxc]

The update did not solve the problem, i still have to reboot the VM on a regular basis to get it working again

[jkasperczyk]

Same problem here (Tesla BLE installed on RPi Zero, Linux tesla 6.6.51+rpt-rpi-v7 #1 SMP Raspbian 1:6.6.51-1+rpt3 (2024-10-08) armv7l GNU/Linux):

2025/09/10 09:00:38 INFO connecting to Vehicle ...
2025/09/10 09:00:53 WARN failed to perform handshake with vehicle (B): context deadline exceeded
2025/09/10 09:00:53 INFO retrying in 3 seconds
2025/09/10 09:01:11 WARN failed to perform handshake with vehicle (B): context deadline exceeded
2025/09/10 09:01:11 INFO retrying in 6 seconds
2025/09/10 09:01:17 INFO received command=wake_up body=map[]
2025/09/10 09:01:32 ERRO stop retrying after 3 attempts error="failed to perform handshake with vehicle (B): context deadline exceeded"
2025/09/10 09:01:33 INFO connecting to Vehicle ...
2025/09/10 09:01:48 WARN failed to perform handshake with vehicle (B): context deadline exceeded
2025/09/10 09:01:48 INFO retrying in 3 seconds
2025/09/10 09:02:06 WARN failed to perform handshake with vehicle (B): context deadline exceeded
2025/09/10 09:02:06 INFO retrying in 6 seconds

but in parallel this command works as expected so I assume keys are OK:

root@tesla:~# curl -X GET http://localhost:8080/api/1/vehicles/LRW#########/body_controller_state
{"response":{"result":true,"reason":"The request was successfully processed.","vin":"LRW###########","command":"body-controller-state","response":{"closureStatuses":{"chargePort":"CLOSURESTATE_OPEN"},"vehicleLockState":"VEHICLELOCKSTATE_LOCKED","vehicleSleepStatus":"VEHICLE_SLEEP_STATUS_AWAKE","userPresence":"VEHICLE_USER_PRESENCE_NOT_PRESENT"}}}

This issue seems to appear for no visible reason - no hardware freeze (RPi), no recent updates (Tesla). Restarting Docker and the whole host does not help. I have not tried to regenerate keys yet.

[bicaluv]

Hm, I compiled the code for my raspy zero 2 W and it works perfectly. Not using docker.

[jkasperczyk]

I forgot to mention the most important thing - it has been working like a charm for several months. Stopped working a few days ago for no reason.

[wimaha]

Maybe this is related to this: #136 (comment)