tesla-api VS Spree Commerce

API reference: https://github.com/timdorr/tesla-api/issues/16

It uses the TeslaPy python module. There is an unofficial list of Tesla APIs here: https://tesla-api.timdorr.com/

The easiest way to explore most of what the API could offer is though tesalmate. It's nice because you host the server and own the data yourself rather than trusting some 3rd party to do it. The API is well documented here, although the authentication is a bit convoluted, but there are helpful apps that simplify its retrieval.

I did update the unofficial Tesla API documentation to show the response to some of the energy site endpoints for my setup (Tesla inverter only). If you know Python, it’s fairly easy figure to out since the authentication work has already been done.

I don't know about any pre-built integrations, but you could build your own https://tesla-api.timdorr.com/

For the Tesla API you can use https://tesla-api.timdorr.com. Alternatively you can install some hardware in your car like CANServer https://jwardell.myshopify.com for info directly from the car.

These apps need your API credentials so that they can generate tokens on your behalf. They are most likely using the methods documented by /u/timdorr here since the API is still unofficial. Also, Tesla added CAPTCHAs to their "OAuth" flow, so apps now need to present a WebView whenever they ask to regenerate your token.

A good system to study is Spree https://github.com/spree/spree. It has an inventory and billing system and supports different adjustments and sale configurations. If you don't want to use it wholesale it's a solid Rails application that does most of what you want so you can use it as solid inspiration.

Spree Commerce: https://spreecommerce.org/

Maybe Spree?

I'd say Solidus and Spree are you best options rather than trying to roll out you own ecommerce solution.

When I was working on that company, that mobile ordering app, Counterless, I looked a lot at codebases like Spree, the Spree Commerce codebase. And that's how I learned a lot about how do you model an order with line items and things like that? I saw some amazing things that helped me develop an understanding and save a ton of time by looking at oh, they have a state machine. What are the ways that an order transitions through all these different states as it gets processed and charged? And how do you track all of those things?