TWCManager icon indicating copy to clipboard operation
TWCManager copied to clipboard

Disconnected Install Guidance

Open MikeBishop opened this issue 2 years ago • 2 comments

Now that Tesla API control is enabled, it's almost possible to run TWCManager and take full advantage of it without physically connecting it to the TWC. I think we should consider what changes are needed to enable someone to run TWCManager in Docker with no serial connection and exclusively use the Tesla API to control the charge limit.

Given that we can't control Gen3 TWCs anyway, that might even need to be the default configuration for the project moving forward. Those of us with Gen2 TWCs are going to be rarer and rarer as time goes on.

MikeBishop avatar Apr 26 '22 15:04 MikeBishop

I think the changes we would need are:

  • Ability to run with no serial interface
  • "Virtual" TWC Slave instances for each car on the Tesla API, only if serial is not used (by default):
    • Only for cars that are at home

We'd need some logic to dedupe those virtual instances if someone were using a hybrid installation, but that could come later.

MikeBishop avatar Apr 26 '22 15:04 MikeBishop

Have you seen Charge HQ? They're running in beta at the moment. It's all completely cloud based, no hardware required. Aside from the Tesla API token all l I had to do was add an account to my Fronius Solarweb instance so that they could read the generation/consumption data. I do prefer TWCManager though, quicker to read my generation/consumption info and start/stop charging.

I'm sure that Jay over at Charge HQ would be willing to have a chat?

https://chargehq.net/

drexcia avatar Apr 30 '22 20:04 drexcia