Ok ! Thank you for your answer.
The poll interval was set to 1 min and during the night when the car is charging it’s seems to be “online” so I use 1 call per min during 6 hours 
I will change the poll interval.
You can use the car state or charging state to dynamically adjust the interval via flow. Or just change it time based to avoid a short interval at night.
But you can also check the usage at Tesla developer page. If it don’t charge every night it won’t be a problem I think.
New test version 2.0.7:
- removed rate limit data
- switched API counter from UTC to 0:00 local time for easier use
Newest version seems to crash after each polling. I sent a diagnostic report.
e0157ca7-916c-42a6-906f-5f2b7939bb56
It’s caused by a “CPU Warning Limit Reached” crash. Can’t really imagine how a data reading can cause a CPU limit.
Strange. I reverted to v2.0.6 and that shows no problem. Then reinstalled v2.0.7 and again the issue. V2.0.7 works for 1 minute, then a poll and crash. Already tried repairing, but does not seem to help
I have the same problem (33cca9c4-1824-4c95-ac02-6e26a2405726). How can I revert to v2.0.6?
You can revert to 2.6.0 by reinstalling the regular version
1 Like
I see the same issue since the update to 2.0.7. I will revert back to 2.0.6. I trust a solution in 2.0.8 will be found!
Sorry guys. I didn’t get any issue while testing.
I hope I can present a fix soon.
I found an issue on HP23 when an app removes capabilities from a device.
It seems that removing a capability from a device created a kind of endless loop. The device detail screen is empty in WebApp and mobile app.
I used a previous FW, updated now to current RC version and got the issue, too.
I would say it’s a bug in RC firmware.
Which FW is installed on the Homeys where the app crashes?
I can provided a new test version where I re-add the capabilities. I hope this will fix the issue.
But perhaps better tomorrow to not to crash your app again
@StevenV @Rudi_Hendrix @Paul_Nas
Which FW version is installed on your Homey?
@ others using the test version 2.0.7 without issues:
Which FW version are you using?
This is the Homey version I am running
12.3.2-rc.3
Now off to bed!
Hi, I’m on 12.3.1
New test version 2.0.9:
- fixes HP23 FW issue (re-added capabilities)
@StevenV @Rudi_Hendrix
I hope 2.0.9 will run as expected
I have the following problem and sent you a diagnostic report:
b3d77b45-1be7-49b2-b042-5ca780447c61
When I open the Homey app, the devices are visible and everything is OK. After a couple of seconds, the devices are offline (red sign). When I then close the Homey app completely, then open the app again, the devices are online again, after a couple of seconds then offline again.
I also have a video of it, if that brings you something.
HP23
Vers. 12.3.2-rc.3
Tesla App Vers. 2.0.9
Any chance you can add support for triggering HomeLink in the app?
LP
Erst mal an den Ersteller ein riesen Dankeschön, coole Sache, dass das jetzt so auch im Homey funktioniert. So ist bei mir wieder alles in einem Gerät geregelt ! Danke RonnyW.
Hat schon jemand einen Flow erstellt, der z.B. alle 5 Minuten prüft, wieviel Strom aus Solarerzeugung “über” ist, um damit den Tesla zu laden ? Ich versuche es gerade auf diese Weise, weiß aber nicht, ob das so funktionieren wird (mangels Sonne) …
Der Minus Wert ist das, was wieder zurück ins Netz gespeist wird.
Nachdem ich jetzt die ersten Sonnenstrahlen geneißen konnte, habe ich auch gleich einen Fehler in der Logik (anscheinend)… Nach 5 Minuten wird das Laden gestoppt, obwohl noch weit über 4000 Watt vorhanden sind (bei mir also -4000)…Jemand eine Idee, wo der Haken ist ?
Und das zweite Problem ist wohl die Auswertung, selbst wenn mehr als 4000 Watt vorhanden sind, wird nur mit 5A (also 3000Watt) geladen, daher es wird nicht wirklich berücksichtig, was wirklich über ist…
I received 2.0.9 this morning but unfortunately the app keeps crashing.
My HP23 is on FW 12.3.1
I’m still searching for a possible reason… 
2 Likes
I have stayed on 2.0.6, HP19, using a second Tesla account, that is an invited driver to the car, and no problem to set up the client_id or car key.
Homey app say it is paired for the car key, and when trying to open charge port it worked after several push on the button in Homey app.
I was expecting the counter to increase, but it stayed on zero for the command api, and got a 400 error code.
Is this expected?
Tried to re-repair the key. Same behavior.
