Yes, like a normal key. You can rename it in the car that you know later where it comes from 
Hehe, just sitting at the Laptop and Firefox highlightes the Tab 
Can you use the same app under Tesla or do you need to create new?
How can I check if the bluetooth key is working and connected? By hitting the “Repair” option and then “Controleer sleutelstatus”?
If it is not connecting constantly most likely the car is out of range of bluetooth of Homey? And the only solution would be to add a Homey bridge or bring the two closer to another?
To use the app on a second Homey, you need a second app (app ID) in your Tesla developer account. So yes, create a second app there.
The app ID is bound to your Homey ID to host the public key with a virtual URL.
All apps in your Tesla account share your 10€ credit.
Don’t use your current clientID in your second Homey. That’s not possible because the clientID is already bound to your Homey ID (better: bound to the URL using your HomeyID to host the public key).
Correct. It would state somwthing like “key is registered in slot #3”.
Yes. A Bridge would be best if you have a HP23. But to test you can try to bring your Homey closer.
You can also check in developer tools under BLE page. Search for a device with advertisement ID “S…C” and try to connect.
Thanks for confirming @RonnyW
It seems that the Tesla Accu app is not yet using the fleet api.
I get the following error when I try to activate the charging.
error: 'Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning',
Can you please advise?
New test version 3.0.2:
- Added car state update via BLE to allow car access if FLeetAPI rate limit is exceeded.
- Fixed missing BLE usable battery value.
The first point addes the ability to read car state (online/offline) via BLE.
Even if the API call to get last known car state is not counted on your credit limit, this endpoint is also blocked if your limit is exeeded. That caused the car device to get unavailable.
When using FleetAPI only, this will be still the case.
When BLE is active, then the app tries to get the car state via BLE. If that’s possible, the car data is read via BLE.
If there is an error and FleetAPI is used instead (which returns the limit exeed error), the device won’t get unavailable. Insted, the API error alarm capability is set and the API error message is stored (e.g. in device settings). The main difference is, that the device keeps available, but perhaps with older data if there are sync errors for BLE.
1 Like
Thanks that resolved the issue!
Not sure what changed, but I am seeing BLE commands being sent to the car. If I am correct that means I can further adapt and finetune my flow that makes sure I optimize the usage of my solar panels to charge the car. As these BLE calls don’t account for my monthly maximum usage
Can I also check in a flow if BLE or 4G is used to connect to the car? If that is the case I can copy the flow and differentiate the number of calls depending on the connection
Do not assume that every call is done via BLE. Even while my Bridge is directly behind the window close to the car, there are a lot of connection errors.
And if you selected “BLE on”, the FleetAPI is used as fallback.
So keep an eye on the API usage even while BLE is used.
The settings is a device setting, so you can’t in flows which API is used.
But you can switch to a BLE only mode with a flow card (car device).
The downside would be: if there are some connection issues and you start driving, you won’t be able to switch back to “BLE on” is Homey doesn’t get a location update for the car (not at home).
As workaround you could use a trigger from your EV charger: connected: “BLE only” / disconnected: “BLE on”.
Thanks for thinking along and the tips!
Good idea to switch to “BLE only” mode when the car is home. I can then still use the Tesla app on my phone to connect to the car and using the Homey app it will only (try to) use BLE for setting the charging power.
Charge with less than 5A using 3 fase home connection
I just found out I can tell my MX 2018 to charge with only 2A using your awesome app
Using the Tesla app one can only select 5-16A
It could be handy to be able to use the lower Amps
Why does Tesla not allow it normally? Is there any downside to doing so?
ps, I am using the older home charge cable ans simply connecting it to a 380V socket with the red connector
Cheers
Cheers
When using 1 phase it would just be 2A x 225V = 450W. And that’s less than basic consumption of your car. I think it’s just about efficiency.
Thanks for the swift reply!
So charging with one phase also has a minimum of 5A? (I have not used 1 phase charging)
If it is about the minimum total Watts, then 5*225V=1125W
When using 3 phase that would mean 1125W/(225V*3)=1.667A
In which case 2A for 3 phase charging sounds reasonable?
Sure, the you get about 600W into your battery without the default car loss. So half your energy gets lost. Using higher power reduces the percentage of energy loss.
Right, 1A of default loss, got it
I think I will only use sub 4A (3 phase) when the car is already charging, assuming loss per kWh in will be less when initial pack warm up is done
If you want to maximize solar, more relative loss could be acceptable
I meant the standard usage from the car itself (HV converter, CPU etc, to keep the car awake). That’s ~500 to 600W - without battery heating (which will be 1 to 2 kW)
Thanks for the clarification Ronny
I am buildling some flows to follow total power in or outflow to regulate the amps the car is charging at
Currently averaging the parameters and rounding to whole numbers every 2 minutes and adjusting to that
Apart from potential API data charges, is there any downside to adjusting the amperage, start stop charging and asking if it is charging etc for that many times?
Thanks again
