Support /api/products

[andig]

evcc-io/evcc#5826 (reply in thread) has an interesting discussion on how to remote control a powerwall. Access is via Tesla api credentials that we have. It would be nice to provide read-only and potentially write access to the broader Tesla api beyond vehicles.

[GrimmiMeloni]

@bogosj I intend to add this (for the reason state above by @andig) in the coming days. Would appreciate if you could assign this to me.

[andig]

@GrimmiMeloni no longer worth it. Tesla has sunset the api, at least afaiu

[GrimmiMeloni]

Oh. Is there an end date already defined? Asking because it still works for me right now - but maybe that will go away soon? Any words on replacements?

[andig]

See evcc-io/evcc#10460

[bogosj]

@andig - I only took a brief look at https://github.com/teslamotors/vehicle-command - am I reading this correctly that ultimately bogosj/tesla will ultimately be deprecated in favor of this new method? As of now anything using bogosj/tesla can use the proxy provided in the teslamotors repo but if you're building something new you should probably use that directly?

[andig]

I still haven't got it implemented, so no definite answer. It seems the struct definitions are (still) not par of the vehicle-command API. Not sure if those will be the same though. The entire auth should go away...

[GrimmiMeloni]

The tesla repo mentions that pre-2021 models will still use the old owners API. So my understanding is that the API will stay for now, however newer car models will only be accessible via their new SDK.
I hope the same is true for older energy products like the existing Powerwalls.