@balmli I installed the app and received a charge plan. The car charged and everything was peachy. Then two days later I was going to charge again and did not receive a charge plan. I reinstalled it and it started working again.
Now two days later it’s not sending me a charge plan. Am I doing something wrong? 
Same question here, I’m doing the same with an Awtrix Light (Ulanzi TC001) matrix display. I’m also seeing some battery drain… could someone answer this?
So I got a charge plan created but will this override the schedule in the tesla or should I remove that?
I have fixed this creating variable for battery level and displaying that one on the smart clock. Variable is updated to #battery on trigger when car finishes charging and when car arrives home. Doesn’t work very reliably (Charger app needs restart from time to time, as it does register “arrived home” & “charging finished” “charging started” maybe on every 3rd time) but it doesn’t drain battery this way. I have also changed poll interval to 720minutes from default 60 minutes.
Ok thank you, I’ll test it as soon as the new version has been released.
Question, what about updates during charging? Does it fetch the battery percentage during charging only when the specified interval (new 720min) has been reached or how often will it be updated during charging?
I try to install the tesla app. When I give the token I get the message: Error: Fetching tokens tailed. How can I fix this?
When do we get the new version?
Hi @balmli
Perhaps it was asked before, but I didn’t find details…
How does the app recognize that the car is awake?
Are all cached requests deprecated now? Also vehicles[0]/[‘state’]?
Sot it can be that when start driving a minute after the last poll, the next request is executed 60min later, and only in then the state is still ‘driving’, the interval is set to 1min?
Something new. Don’t know if this affects your app.
There also seems to be a new auth process (using public key that’s transferred to the vehicle to allow access from 3th party apps.
https://developer.tesla.com/docs/fleet-api
And german forum thread:
Is the geolocation flow cards not working in test mode?
I’ve made a flow that I use when my car arrives at work, but in test mode it does not activate.
I added the work location to the apps geofence with the proper flowcards, and I’ve double checked that the car reports back the exact same latitude and longitude values by reading them through logic cards.
So, the latitude and longitude that the car is currently at matches the ones in my flow card, but the flow card reacts in orange (false) when I try it in test mode.
I’ll see tomorrow if it works organically, but I just found it curious that it failed in test mode.
I’m trying to figure out what I’m doing wrong here.
Yesterday none of my geofencing cards were working (They returned a false reply, not an error). Today they are working, but on the third or fourth try.
Try number 1 resulted in an API error
Try number 2 resulted in an API error
Try number 3 resulted in a “network initializatio request” error or something of that sort
Try number 4 executed perfectly.
Do I have to “wake” the connection up before running my flows? Is there a smooth way to do that?
It’s me again, continuing my monolouge.
The above posts has been sorted out, I think. I just needed to understand how the app and Tesla API worked, and I have concluded that I was triggering flowcards erratically, meaning that they were blocked on Tesla’s end. I have tuned my flows so no cards are triggered often, and it is much more stable.
I have also had good success in “waking” the car up with a small temperature check a minute or two before my flowcard actually activates.
I have a flow I want to activate when I arrive at work. Can someone tell me how this flowcard is supposed to work? It says “Vehicle entered location”, but I cannot choose location. Is it any location in my geofence list?
Hi,
I’ve been working on figuring out what causes my Tesla to wake up every so often (usually every 10-11 minutes). I’ve disabled all third-party apps to rule that out. My goal is to ensure that the car doesn’t stay online constantly.
Now I’m curious if the triggers “The vehicle state changed” are causing the car to go online every 10-11 minutes. I’ve actually created a flow that adjusts based on the vehicle state data fetch interval and status. However, no matter what I try, the car keeps coming online. It’s only when I disable the flow that the car goes into sleep mode.
I’ve also gone through this entire post, but I can’t seem to figure it out.
I’ve tried using this app for a few flows but can’t seem to get the expected results - likely I’m doing something wrong.
I’d like to have the garage door open/close when I arrive home/leave home.
Do I have to set the interval to 1 min (default 60) to make this work without having to wait an hour?
I’ve tried to trigger push notifications when the car leaves to tell me how far from home it is as well without luck.
The charging I get notified correctly to timeline but the location-triggered flows doesn’t work for me.
Has anyone manage to get this working and if so, how? 
Create flows that listen to vehicle state changed. When changed to asleep set data fetch enabled, when set to online you can enable it. I’ve set data fetch interval to 3.
This way it won’t awake your car.
Hi Volden, thanks for your response. I have already set this up like that. I think you mean that the “data fetch enabled” is set to disabled when the status is asleep, right?
Can you perhaps share your flows? And also, what settings have you configured in the advanced settings?
I have been testing for a while. In my other version of the flow, I had also set it to change the “Data fetch interval” every time based on the vehicle state (online is 3 minutes, asleep is 1440 minutes).
I have now adjusted this as you can see in my previous post. So far, this seems to be working. I will keep an eye on it today to see how it goes.
@balmli
Hi,
I just upgraded from Homey Pro 2019 to 2023 and my Teslas location is now just shown as «unknown». See attached screenshot.
Is this a known issue? I’ve tried to remove and add the car again and reinstall the app, but no luck.
Is this a known issue? Any solution?
Same issue here. Worked until just recently.
