Node-Red Sleep Charging Flow for Octopus or Time of Use Electricity

[chrisgla]

Hello all!

I am trying to integrate my Modbus charger, Octopus Energy and Tesla API to charge at best time.

I've only been using Node-Red for a month and not a developer so surprised how far I'm getting!

I have the charger integrated. able to get best charging times from Octopus API and using Node-Red-contrib-Tesla I can see vehicle data but I've not quite got the logic right to avoid vampire drain.

Does anyone have flows they can share on how they implemented anti-vampire measures?

I have most of the not waking vehicle up bit working based on checking if vehicle is online and outside temperature is not a number- the main thing I'm struggling with is how to watch for the vehicle waking so I know I can change from vehicle "offline" query to a full all data query.
It should be simple- but in these things so am I!

Part of the reason is I did use TeslaFi, but it doesn't have capability to feed in actually half hourly electricity prices to work out how much a charge actually cost. Later stage...

 

[denouche]

Hello,
You have different API endpoints.
You can find the list here:
List
State And Settings
Commands

The endpoints GET /vehicles and GET /vehicles/{id} does not prevent the car to go asleep.
These 2 endpoints also give you the current vehicle "state" (asleep, online).
If the vehicle is "online" you can call the endpoint GET /vehicle/{id}/vehicle_data (otherwise you will get a 408 response error)
In this endpoint you will have a lot of informations you can use.
You can poll this endpoint (for example every 1 or 2 minutes).
To know if the car want to go to sleep, you can check the "drive_state.shift_state" field. If it's null, it's because the vehicle is parked and want to go to sleep. At this moment, stop polling and wait the vehicle state is "asleep" (in the GET /vehicle/{id} response).
When the vehicle is asleep, start again polling until the vehicle is back online.

There is some others fields you can check to determine if the vehicle want to go asleep:
- if vehicle_state.sentry_mode is true, the vehicle will never go to sleep (even if shift_state is null)
- if charge_state.charging_state is "Charging", same thing
In these cases you can continue polling the vehicle_data endpoint.

 

[denouche]

You can also come here TeslaFi Sleep Setting
to see what algorithm @Seth2020 is describing

 

[denouche]

Some other interesting reading:
Enabling sleep settings to limit vampire loss. / Knowledge base / TeslaFi

 

[chrisgla]

Thanks.
I managed a basic flow- it is only to check if the vehicle is awake and if so, get online data. It never tries to wake the car- I do that elsewhere.
It's not a TeslaFi replacement, all this flow is for is to know and query appropriate online/ offline state, and to provide data I use to optimise charging at home.

Here for reference:-
Node-red-contrib-tesla anti-vampire drain function