Btw. I have a flow that reminds me if the car is at home and charger not connected - Telsa probaly found out that is pretty cool, I’ve noticed in the most recent update they have implemented this in the phone app with notification - very relevant (if I remember correct, when the car is belov 50% battery level).
1 Like
very relevant (if I remember correct, when the car is belov 50% battery level)
OT: some study I read a few months ago concluded that degradation is the least when the battery is kept around 30%. So 50% or a bit below shouldn’t be a problem - maybe even the opposite.
P.S: Please don’t ask me to find it again 
I also have another tip for saving the battery. It is best to charge with low current and short intervals, not from 0-100% in one go. gives the battery time to recover.
Unless you have a Tesla with LFP batteries. Then it is advised to every now and then charge to 100%
1 Like
Hello, first of all thank you for your great app!
I have 1 issue though. If I want to set the charging current to for example 10A using a flow, for some reason the actual charging current gets set to 0A and the car doesn’t charge. No matter what charging current I want to set, it always sets it to 0A. Is this a known bug or is there something I’m doing wrong? Thanks in advance!
Please check that you are using the “Command Proxy” in car device settings.
If it’s set to “Command Protocol” that it’s because this implementation is not ready yet.
Wow, that fixed it. Thank you for your fast response and good work overall!
Hi Ronny,
Thanks for your great work!
Trying my first flow to try and automate the charging when plugging in at home
The state change charge port open (laadport geopend) does not trigger it seems
May this be because the app only pings the car every 1 minute when its awake? I assume the car does not send data when the port is opened?
Hope you don’t mind a more generic question too. How would I go about creating an average solar output value to prevent the app from changing the charging amperage every time a cloud passes by?
Thanks again for a great app!
Within the climate app, there seems to be a bug in the when-cards. I can see defrost deactivated twice but defrost activated is missing. The same applies to the climate preconditioning:
In Finland many people are having electricity bills based on spot prices. Thus, it makes sense to use the electricity from the grid only when it’s beneficial.
The car battery is anyways charged during the cheapest hours. Now I am trying to construct a flow that would prevent the electricity usage from the grid when defrosting or preconditioning the car, as long as there is sufficient amount of battery left.
To accomplish this, I would actually need the When-cards for activating the defrost and another one that would trigger if the pre-conditioning is started…
Hi, thanks for the hint. These are trigger for activated/deactivated, but I just missed to change the desctiption for the “activated” cards. It will be fixed in the next version.
2 Likes
The app is polling the data in the set interval (1min default). That means it takes up to 1min to get new data - and then the flow should be triggered.
But: If you have a offline interval of 10min (to not hit the servers too much) and you wake up the car with the Tesla mobile app (or just open the car), the Homey app will get a refresh after the 10min interval. So it’s a bit of a coincidence whether you get a trigger after 1 or after 10 minutes.
You could make a flow to open the port and start it with Alexa (if you are using Alexa). This wakes up the car, opens the latch and sets data interval to 1 min.
1 Like
Good question. You coud read PV production every 30sec for 5min. Sum up into variable. Every 5min, read the variable and calculate the average into a second variable. Then clear the first one and start summation again.
If your average variable changes, you can check the value to decide what to do.
Just as idea 
1 Like
2 Likes
I’m not sure if this could work. As far as I know the car takes energy for defrost/proconditioning from the wallbox independent of charging settings - if the cable is connected.
So you need a wallboy you can control. I don’t think you can prevent wallbox usage for preconditioning if connected to your wallbox.
I have an idea or too. I am thinking to launch “unlock charge port” command. I’ve tested and the trick works at least manually…until after some minute or two it will re-lock the cable to the charge port again 
continues the heating with electricity grid. So need to sort that out as well…
I do have a connected wall box and that’s also in the Homey. I think I can control its relays too.
Let’s see…
hi ronny,
thanx for that great app. I have discovered a problem: when the Tesla car (car older than 2023) does not charge and I use the flow “Laden starten” than charging starts. But if the car ist already charging and I use the flow card “Laden starten” than the car STOPS!! charging!
thats a huge problem because, If I run a complex flow to adjust charging speed dependign on solar power, the car will start and stop repeadetly. Can you fix this problem? The opposite is with the other commands: for example, when charging current is already 5 and the flow chould set charging current to 5 the flow will stop with an erroc code already_set. but unfortunately the whole ongoing flow will STOP at that point! Can you please avoid a error code for the case one setting ist already set?!
The same problem ist with set SOC to x. When SOC is already set to the desired percentage, the flow will stop with eccor code already_set…
Which API is selected in car device settings? Command Proxy?
I have a tesla from 2018. So I must set up REST API, don’t I?
Also starting the charge often does not work, even its not startet yet I don’t know what I have to do that it starts?! Today in the morning it didn’t start as the flow tried to. I Don’t know what I did, suddently it startet and the whole day my flow worked great adjusting the charging speed and state to the amount of solar energy. But now in the night, as I trie out some adjustents to the flow, it doesn’t start anymore.
Teslas documentation is not clear in this point.
Pre2022 S/X can/must still use the REST Api. But you can try to add the app key to your car (repair dialog of car device). If you can add the key, then you can use CommandProxy as Api. If your car can’t add an app key, you have to use REST Api.
About the API errors:
That’s bad if API calls are wirking different. In your case it’s more w warning, but Tesla returns a error. I’ll try to find a possibility to check for such “OK errors” to ignore them all.
