-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only poll Tesla API when charging is active #96
Comments
Polling the Tesla API will keep the car awake and prevent it from sleeping.
Right now we are always polling regardless of state. We could stop polling
or poll way less often when the vehicle is not charging or driving.
…On Fri, Jun 26, 2020, 4:31 PM Glyn Hudson ***@***.***> wrote:
After enabling the OpenEVSE Tesla integration I noticed a higher than
average vampire drain (12 miles lost overnight) on a 2015 Model S. I setup
TeslaMate <https://github.com/adriankumpf/teslamate> which logs the state
of the vehicle, as well as lots of useful info.
TeslaMate confirmed my suspicion that the car was not going to sleep.
After the OpenEVSE Tesla integration was switched off at about 13:00
shortly after the car went to sleep.
[image: Screenshot from 2020-06-26 21-22-04]
<https://user-images.githubusercontent.com/758844/85898185-bd5ac580-b7f3-11ea-88c1-c6d1042b81b4.png>
@chris1howell <https://github.com/chris1howell> @lincomatic
<https://github.com/lincomatic> can you replicate this experience? Have
you noticed higher than usual vampire drain if using the OpenEVSE Tesla
API? Do you have any other integrations running using the Tesla API? If so
these could also be keeping the car awake. What is the usual vampire drain
on your cars?
I'll continue to monitor and test this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#96>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN5QH6EPAPY33XGGRSDBYDRYUASRANCNFSM4OJUTB4A>
.
|
@glynhudson sorry, i don't have a Tesla, so I can't do much testing. I developed the API code using Chris' account |
It polls the Tesla API by calling Tesla doesn’t care for their servers being polled repeatably so a streaming websocket API solution might be better? Advantages would be:
Some code samples: edit/ Also Teslamate uses this idea... |
I've added a note to the docs to mention the increased vampire drain if using the integration. This doesn't seem optimal, loosing approx 12 miles/day. That's a lot of energy over a year! Also increased wear on the MCU and DC-DC converter since it's running pretty much continuously. Only polling when charging/driving and less regularly sounds sensible.
Nor do I, I borrowed one from a family member for testing
That sound like a good solution. Would you be able to put together a pull-request for this if you're familiar with the API? |
The streaming API is not yet well documented, for now we should only poll
while actively charging as the vehicle will already be awake. If the
station status is error, connected or Ready we can stop polling to allow
the vehicle to sleep. In the future we could add the streaming API or
polling while driving to update the display with real time charge time
estimates.
…On Sun, Jun 28, 2020 at 6:06 PM Glyn Hudson ***@***.***> wrote:
Polling the Tesla API will keep the car awake and prevent it from sleeping.
I've added a note
<e7fd6aa>
to the docs to mention the increased vampire drain if using the integration.
This doesn't seem optimal, loosing approx 12 miles/day. That's a lot of
energy over a year! Also increased wear on the MCU and DC-DC converter
since it's running pretty much continuously. Only polling when
charging/driving and less regularly sounds sensible.
@glynhudson <https://github.com/glynhudson> sorry, i don't have a Tesla,
so I can't do much testing. I developed the API code using Chris' account
Nor do I, I borrowed one from a family member for testing
Wouldn't it be better to use the streaming websocket API instead?
That sound like a good solution. Would you be able to put together a
pull-request for this if you're familiar with the API?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#96 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN5QH7FG3ASUH2CQ5D7FFDRY65E3ANCNFSM4OJUTB4A>
.
|
Ok |
e.g If evse_state == 3 then do Tesla loop |
After enabling the OpenEVSE Tesla integration I noticed a higher than average vampire drain (12 miles lost overnight) on a 2015 Model S. I setup TeslaMate which logs the state of the vehicle, as well as lots of useful info.
TeslaMate confirmed my suspicion that the car was not going to sleep. After the OpenEVSE Tesla integration was switched off at about 13:00 shortly after the car went to sleep.
@chris1howell @lincomatic can you replicate this experience? Have you noticed higher than usual vampire drain if using the OpenEVSE Tesla API? Do you have any other integrations running using the Tesla API? If so these could also be keeping the car awake. What is the usual vampire drain on your cars?
I'll continue to monitor and test this.
The text was updated successfully, but these errors were encountered: