Usage of multiple (min. 2) BLE devices for usage on same home address

[toooooobi]

Hello @pkuehnel,

thank you very much for your great project and the possibility to use it since a long time now. I already subscribed lifetime with your API service :-)

Current status:
I have two wallboxes at my home address

• (wb1) in a garage, where my main raspi (rp1) is located having tsc and bleapi on
• (wb2) at a garden shed roughly 50m away from the (wb1)
• Both locations are identified by TSC as "home"

Situation:
(rp1)´s BLE signal does not reach the location if one of my two Tesla vehicles is charging at (wb2)

Wish:
I want to have the possibility to install a 2nd (rp2) near the (wb2) to have also BLE connectivity at this place
The current car setting BLE api only supports one IP address, right?

How could I solve that issue?

Thank you very much ahead for your help!

Tobi

[pkuehnel]

I am working on a home detection via BLE but the issue is, that I use the Tesla BLE software to control the car which is quite unstable and even more if it tries to send commands to the car while it is not There. To resolve this I need to write the complete software for the BLE communication myself, that's why this is a few months away.

The options you have now but all of them are not great:

1. Next week I will release a new version of TSC that can not only detect "home" based on the home address in the Tesla navigation system but also on "work" or "favorite" (Note: TSC can not detect on which favorite location the car is, only that it is on one). You then could change the home address to one that includes one Wallbox location but not the other one (I have no idea in which radius the car is detected as being within that location, that's all coming from Tesla). You then need to install a second TSC where you use "favorite" as home detection. Like I said, this will only be possible with a new version next week, also the car needs to be at least on 2025.2.6.
2. You buy a Fleet API license for the car, then you can enable include tracking relevant fields in the car Settings in TSC, then the in the Base configuration configured Home Geofence is used instead of the Tesla logic of "home". With a second TSC installed you then can use a slightly different home Geofence. The issue for me: I do get your location every 10 seconds which costs me much money, that's why Fleet Api license is required for that.
3. You automate updating the BLE API URL yourself. All the configuration is via REST API, so if you can detect where the car is plugged in (e.g. via API of your Wallbox), you can update the car settings. If you want further information for that, let me know.