Hello! I have been using this app for a few days to preheat my car based on if there is an event in my calendar. There are only 1 event a day. It has worked great!
How ever, today I got an alert from Tesla that I had reached my API limit.
Looking at the data in the Tesla Developer Portal, it seems like the Homey integration pings my car once every minute. It is only flagged the category data as being used. I have added the “car” module and the “climate” module for the car from the integration.
Is there a way to make the integration only ping my car when the flow runs?
The app polls your car for data update. You can adjust it in car device settings - perhaps deactivate polling completely. Then you can control functions via flow, but you won’t get current data for triggers/conditions. You can also adjust the interval in settings or via flow. There are some examples in this thread.
Hi Ronny, thanks for the follow up. No haven’t managed to get it to connect. Device shows the correct region, also tried changing the app region to US to see if that helped but no luck.
Tried to further optimize my automatic charging and stop of charging flow. I moved my Homey closer to the Tesla. It is right next to it right now.
During the first few tests I noticed that a few commands don’t seem to work while connected with bluetooth only. For example starting charging, setting the charge level. I see that 121 BLE commands have been sent succesfully and 3343 have returned BLE-Failures.
I placed my Homey Pro itself much closer to my Tesla. I hardly doubt if signal strength is an issue.
Anyway, I don’t mind it being somewhat a hit or miss. I will first test the current flow for a bit. If it is in general working correct in worst case it means for example it is charging with 2 Ampère, the sun starts shining harder and it wants to update the charging power to 3 Ampère, it doesn’t work and it sticks to 2 Ampère
Sometimes it can also happen that the car is blocking BLE requests. But this only an edge case if already three car keys (mobile phones) are connected.
Because, yes, I do have a bunch of phones and tablets connected almost all the time. Not all of them as phone key though. Some are like my daughter’s phone: she can interact with the car, but cannot start driving the car. That’s two different things, right? Being “connected” or “act as phone key”. Because at the same time, it states this:
Hm, don’t know in detail. I think it’s enough to be connected via BLE. If the app is installed and running, It can connect with BLE to open the door. Then it depends on being registered as key to really open the door. But the BLE connection should be established in this case. So yes, this can be a reason.
You can check it:
turn off BLE on most devices.
try the key state button in repair view (fast check if you can connect)
And I am investigating switching to Tibber (energy company) and they offer smart charging too, So perhaps in the longer run I won’t be using this. Perhaps I will
With Tibber, I’m using the HomeyApp. It has flow triggers like ‘one of the 2 cheapest hours between 0:00 and 6:00’. I use rhese triggers to charge the home battery at night in winter.
That can also be used to start/stop charging - with a smart ev-charger or with flows/Tesla app.
Tibber will also only start/stop charging. They won’t control PV charging.
@RonnyW are there any chances you could add a card so we can open doors? Primary the drivers door (left in Denmark). Not the unlock but open the door part.
I checked the API. The reqional URL and region is given by the API/Tesla based on the user settings. So I think it’s based on the account your are using for adding the device (not the developer account if you are using a second account for).
Usint Tesla app it’s only possible to open the door next to the car. I think it’s only allowed via Bluetooth. That means: If I get it to work, you will only be able to open the door from Homey if you are using the BLE connection and the car is in range of Homey BLE.
