Delayed Charging Timer

[Xtopher]

EppaTo, just out of curiosity, what is your stack for extracting and rendering that data?

Maybe overly complex, but had it all already set up for other purposes:

Python skodaconnect
Telegraf
Influxdb
Grafana

Dont suppose the skodaconnect API is documented somewhere? Or you can publish your work? Would be great to have this connected up to ABRP somehow, even if a homebrew automation set up to pull/push the details.

[EppaTo]

EppaTo, just out of curiosity, what is your stack for extracting and rendering that data?

Maybe overly complex, but had it all already set up for other purposes:

Python skodaconnect
Telegraf
Influxdb
Grafana

Dont suppose the skodaconnect API is documented somewhere? Or you can publish your work? Would be great to have this connected up to ABRP somehow, even if a homebrew automation set up to pull/push the details.

I found it here: https://github.com/lendy007/skodaconnect
I'm using the json (vehicle._states) directly though.

There is also a home assistant component here https://github.com/lendy007/homeassistant-skodaconnect

I have my code also generating a csv, I just modified the example from https://github.com/lendy007/skodaconnect
I was thinking i should make it available as an executable and a docker image for those that want to log for themselves

[jamest]

Thanks EppaTo. I haven't used Telegraf, Influxdb or Grafana. It may be an overkill, but they look like good technologies to learn, so I'd be interested in taking a look at anything you decide to share. Have you got it all configured to run in a single docker container then?

[Xtopher]

I found it here: https://github.com/lendy007/skodaconnect
I'm using the json (vehicle._states) directly though.

There is also a home assistant component here https://github.com/lendy007/homeassistant-skodaconnect

I have my code also generating a csv, I just modified the example from https://github.com/lendy007/skodaconnect
I was thinking i should make it available as an executable and a docker image for those that want to log for themselves

Thanks for the details, I will take a look. Might be a while as my car isn't even schedule to build until week 42

[EppaTo]

Experiment 1,
Startstate: 76%, Targetstate: 80%, Immediate charge to 50%
Preferred times: 22:00-06:00,
No departure time set.
Charger Capacity: 5.5kW

Summary:
05:30 Started charging at 2.5kW
05:45 Increased charging to 5.5kW
06:00 Ended charging
EndState: 77% (increase of 1%)

Comments:
Not the best possible experiment, as my initial charge was quite high. Will try with a lower initial charge to see if there is a corrolation between charge start time and initial charge.
I'll make an attempt at packaging up the code that produces CSV files, so that others can measure their cars as well

[EppaTo]

Thanks EppaTo. I haven't used Telegraf, Influxdb or Grafana. It may be an overkill, but they look like good technologies to learn, so I'd be interested in taking a look at anything you decide to share. Have you got it all configured to run in a single docker container then?

No, I have separate containers for each component, managed by docker-compose. As this is somewhat off-topic, we can take the discussion onto PM's if you'd like more detail

[Perchede]

The graph clearly shows it tries to calculate the start time to finish. With my 7.4 Kw/h charger it appears to calculate correctly but then only uses 3.5 Kw/g thus failing to achieve target.

[tiger tony]

Thanks EppaTo. I haven't used Telegraf, Influxdb or Grafana. It may be an overkill, but they look like good technologies to learn, so I'd be interested in taking a look at anything you decide to share. Have you got it all configured to run in a single docker container then?

No, I have separate containers for each component, managed by docker-compose. As this is somewhat off-topic, we can take the discussion onto PM's if you'd like more detail

You guys should set up a new post with more details of this topic. I'm sure there's plenty of other members here who'd be interested - me included !

[EppaTo]

Experiment 2,
Startstate: 45%, Targetstate: 80%, Immediate charge to 50%
Preferred times: 22:00-06:00,
No departure time set.
Charger Capacity: 5.5kW

Summary:
22:48: started charging at 3.5kW
23:04: stopped charging, gained 2%
--- pause ---
01:36 Started charging at 5.5kW
03:13 Ended charging, gained 10%
Some dips to 2.5 and 3.5 kW during the charging period
EndState: 57% (increase of 12%)

Comments:
Started charging earlier in the available window than previous experiments
Stopped charging after 10% increase, though long before end of window or charge complete
Did not execute immediate charge to 50%
I don't see "mis-estimating" charge capactity beeing the only issue here, though it may certainly contribute...

From communications with the guys making the python library, it seems there are efforts by one of the devs to create his own scheduler. And certainly the skoda connect api would allow for that (it has sime "start charging" and "stop charging" commands).

While i think a DIY scheduler would be cool, i really think Skoda/VW should fix this....

[EppaTo]

The graph clearly shows it tries to calculate the start time to finish. With my 7.4 Kw/h charger it appears to calculate correctly but then only uses 3.5 Kw/g thus failing to achieve target.

That was one of my original hypothesis, however my other charging runs doesnt really support that theory. It could easily be part of the problem though.
In the latest experiment, it stops charging after having gained only 12 (of 35%), way before the "window closes". If the hypothesis was correct, we would see it start "too late", not "end too early"

I'll make an attempt at setting up two windows back-to-back to see if that makes a difference