When a binding no longer is supported, then what?

It seems like the Tesla-binding is no longer working and also no longer supported, (it requires an app to create a token, and it seems like the app is no longer supported by Tesla, which means it cant create any token).

Now, the binding is still available. But I wonder if thats a great idea, when its not working, and hasnt been working since sometime in may this year?

Submit an issue to the openhab-addons repo to remove the no longer working add-on

With luck someone will volunteer to take it over. Otherwise it will be removed as no longer functional and no longer supported.

The maintainers do not use every add-on in the repo. It’s up to us to let them know when one breaks.

Also an idea is to take a look at Home Assistant’s integration. There might have been a workaround implementated there, that one could ‘translate’ to Java.

I’ve been meaning to take a look at it - if someone can confirm the HA addon still works, and there is still a way to generate the necessary token, I’ll commit to trying the get the read-only parts of the binding working. (the commands are a no-go they require the updated API and $$$)

I suppose taking a look at the HA community board will clear that up?

I just had a quick look. They show 3x Integrations:

  • Tesla Fleet
  • Tesla Powerwall
  • Tesla Wall Connector

Tesla Fleet uses the Fleet API which requires self-hosting or a paid subscription - see pre-requisites at Tesla Fleet - Home Assistant

For OH - we do have the Teslascope binding, which supports most of the same channels as the Tesla binding, but isn’t free.

I did adapt the Tesla binding to work with the Fleet API at one point - perhaps that’s the logical path forwards?

I can confirm the Home Assistant Community Store version works fine. Never got Fleet or Powerwall working in HA and I don’t have a wall connector. In the Community Store it is labeled Tesla Custom Integration.

Hello,

I have a tesla model 3, wall charger in my garage and solar panels, and I want to be able to control the charging of the car base on electricity production of the plant. So I plan to make that possible in OH with the new Tesla Fleet API, I guess the best way will be to change the Tesla Binding, if somebody have a better idea I am open to suggestions.

@Paul_Smedley you mentioned that:

Could I take a look at your code?

Tesla binding modified to use Fleet API is at GitHub - psmedley/openhab-addons at tesla-fleet-api · GitHub - note this will come with API cost, which is why I created the Teslascope binding, which is a pretty economic way to do it.

Another way to do it (for free) is an ESP8266 board and GitHub - PedroKTFC/esphome-tesla-ble: Interact with Tesla vehicles over BLE using ESPHome and Home Assistant · GitHub

You actually don’t need the tesla connection for that. You only need to connect to your power meter, if it is sending power to the grid you can start charging. If you car battery state is less than what you have set in the tesla app, the car will charge.

I used to have the tesla binding connected just to read out the battery state of charge but I lost the connection since June, and the principle described works well without it