Coming back to your question…
Open charge port should work. I wonder that it works some times for you and the other times you get http-400. I would say, if something is wrong (wrong/old public key added to car) it should never work.
If you tried pairing again and you changed client_id or secret in the view, a new key is created. In this case, you have to remove the old key from the car (car display, remove key using the card) an add the car key again. I think because the same URL is used, the car doesn’t refresh the key.
Hi Ronny, I also can confirm that after the update to 2.0.11 the app is not crashing anymore. Thanks!
But I noticed that after sending a charging command to my Tesla, the app becomes unresponsive. There is an API error and the app stops retrieving information from the car.
Any idea? I sent you a diagnostics report: 28c796e3-81c3-45f2-acdd-a4f1d58aef3c
Hi, I can only see that the command was sent 5 times (retry is active in your device settings). Then the API error response was “requested”. I would say, the command was sent to the war, but there was no real response/confirmation.
I had this one time, Second try worked. But this is caused by the car.
What do you mean with this? The data request is independent from commands. Perhaps the car is not reachable in general atm?
@ users that got CPU crashes last days. Can you please check if the capabilites got removed from car device or is they are still present? Thanks.
measure_api_rate_limit
measure_api_command_charge_count
And I would like to try to remove them again. For that I would need to upload a new test version and then it’s a trial/error situation if CPU crashes are still present.
That’s just a try to collect some data if it’s still present. So I can collect CPU insight screenshots for Athom with capability remove (and crash if it happens) and current situation.
Who wants to help?
Thanks, that makes sense.
I did remove car keys, and added it again, with the same results.
The automation I have to open the charge port when I come out to the car in the morning, and the charging is completed, worked today, so it looks like it’s cosmetic only. I.e. 400 result code, and 0 commands sent, might be wrong. Since the command worked, and tesla statistics at developer portal is updated…
The command is sent in the morning? Because the app counter resets as midnight.
The counter is updated directly before the command is sent.
I’ll keep an eye on this.
But the ‘requested’ response from the car is bad anyway id don’t know if it’s processed or not.
PS: I can see in your log that the app counted the commands up to 6.
New test version 2.0.12
- Next try to remove deprecated capabilities.
Please report if you get CPU crash again. If yes, please add a screenshot of your app CPU usage.
I got again reports about CPU caused app crashes.
I assume the same users affected.
Next test version will fix this again.
Where do I check if these capabilities are present or not?
https://tools.developer.homey.app/tools/devices
Then search for for your device
Thanks! Learned something new 
The device has no capabilities.
When the app is started again, the capabilities should be back 
Ok, I’m getting closer to the crash reason. With a trial/error removement of several changed things I hope to reduce the possibilities to exact one
1 Like
Indeed. The two capabilities you mentioned are not in the list.
1 Like
Hi Ronny,
I think the last test version that I tested was 2.0.11, after which I went back to 2.0.6. With 2.0.6 installed, both capabilities were present.
I now installed 2.0.15 and both capabilities are removed. Also, 2.0.15 seems stable right now, no high CPU 
Hope this helps
Yes, sent in the morning triggered on when I open the front door and the charging is complete.
If ot was easier to remove and then add the car device again, I would do that to make sure no old data is in the way…
Or can it be connected with that the car key is not for an Owner, only Driver, of the car?
I think I got it now.
It seems dependent on a really small change to use local time instead of OTC for counter reset. On some Homeys or regions or languages the time was not converted correctly. And that seems to have created an timeout loop.
It seems I changed it parallel to the capability changes and had not considered it. 
Version 2.0.15 is good for now. Sorry for the trouble. 
2 Likes
Yes, it’s from the first post in the Homey Energy megathread, posted by Emile.
Thank you for the reply!
This was an issue last year. Now it should work also as driver.
I think the difference is that you need the key card in your car to add a key. Owners can do it only from the Tesla app.
