Probably a question for @TrystanLea to help with!
I’m currently looking at how to integrate Demandshaper to control charging of my Tesla car.
I’ve delved into the code of OpenEVSE and it seems to make sense.
What I’ve done so far is…
- Write a standalone Python program to interface Tesla API to MQTT
- Added a new “Tesla Vehicle” device into the device API to create inputs and feeds
- Clone some of the OpenEVSE pages to communicate with the MQTT
Point 3 is where I’m a little confused, I can see the OpenEVSE stuff communicates with MQTT so you need to keep polling the backend for status updates.
Can the DemandShaper just using the emoncms input API as its source of data instead of relying on MQTT ?
I will still need to use MQTT to publish the requests to the Tesla API, but it would make more sense for the inputs to drive the web page/interface. I can also use the cached “last known” input values.