Teslascope Binding

Add-ons Bindings
21

Hi Francois,

I have implemented all the commands that Teslascope currently supports. Right now, that only includes auto-conditioning - which conditions the cabin of the car; not pre-conditioning the battery of the car.

I’ll ping the Teslascope developer and ask if it can be easily added.

Edit: https://x.com/PaulSmedley/status/1824370914399752677

22

Hi Paul,
Did you manage to contact the Teslascope developer about the additional commands ?

23

Unfortunately, I didn’t get any response.

24

I found under the Channels, “charge-limit” is missing..

But, in your example.items it is included, but does not update on when using the item as it is not linked to a working channel.

Dimmer              TeslaChargeLimit            {channel="teslascope:vehicle:model3:charge-limit"}

Is this a typo, or is it not suppoted? Eveything else seems to be reporting properly.

Thanks for all your work.

25

Hi Justin,
This is currently not supported by Teslascope, and shouldn’t have been listed. I’ve pinged the Teslascope developer on X to see if he can expose the charge limit setting.

Cheers,

Paul

26

Thanks for the effort !

27

I should be able to expand the binding to support more commands/data soon - see https://x.com/teslascope/status/1879583741594812918

28

Hi Paul, Looking forward to the new channels. Thanks for staying involved in the binding.

29

The updates with Teslascope v5 refresh have broken a few things - for one - the switch that shows whether the car is charging or not. Fix incoming, I just need to test it :slight_smile:

https://smedley.id.au/tmp/org.openhab.binding.teslascope-5.0.0-SNAPSHOT.jar

Fixes the following:

  • detection of charging (charge_state previously reporting “Charging” now “Enable”
  • sentry_mode enabled was previously an int, is now a boolean
30

Binding updated… I found detailed_charge_state which has the same information as the old charging_state, so am using this instead.

I also added an item as a switch that logs whether the charging port is connected or not.

31

charge-limit-soc is working now - https://smedley.id.au/tmp/org.openhab.binding.teslascope-5.0.0-SNAPSHOT.jar

Tyler (teslascope dev) is also going to add support for set_preconditioning_max

32

btw bug fixes are also included in OH 4.3.4 :slight_smile:

33

FYI there will be some breaking changes in OH5. The binding will be split into an Account Handler and a Vehicle thing. The benefit here is that you just add your apikey and discovery can work.

I’ve had this running locally for several weeks, but it it would be good to get this more widely tested.

For users running the Teslascope binding, what OH versions are you running? Anyone on the OH5.0 milestones can test with: https://smedley.id.au/tmp/org.openhab.binding.teslascope-5.0.0-SNAPSHOT.jar

34

I use OH 5.0.1 on windows, and its works great. I only use one function at the moment, but it really makes my everyday life easier. I use a Shelly button that triggers the unlock function for the charging cable, so I don’t have to take out my phone every time to unlock it. Now I just press the button, unplug the cable, and get in the car. Thank for a great binding.

35

I use OH openHAB 5.1.2 and Teslascope 5.1.2, but it is not working at all. I have two connected items (Battery level and Charge Limit SOC). Both show NULL.

If i try https://teslascope.com/api/vehicle/???/detailed?api_key=??? in a browser where i used the right public id and api key (both are the same as in openHAB), then all values are shown correct in the browser. So i think the Teslascope binding is simply not reading values.

I signed in at teslascope a few days ago, so i am still in the trial period where everything is unlocked.

My first teslascope binding was 5.1.1. Today i updated to 5.1.2, but all values are still not updated.

I don’t know what i did wrong and what i can try to solve this issue.

36

trace logs will help. I assume you have setup the account bridge, and a thing for your vehicle? The vehicle thing needs to be linked to the bridge. File based config of using the UI?

37

Yes. I have a account bridge thing, with the correct api key. I have a vehicle thing with the correct public key. Both is online. The account bridge is selected in the vehicle thing. There is nothing related to tesla or teslascope in the log viewer.

Today i saw both things had a comm error “Teslascope returned error <500> ..”. After i disabled the account thing and enabled it again, both is online and green again. But the values are still not updated.

I use the UI based config.

The logging level of the teslascope binding was “Info”. I changed it to “trace”.
Then i see every 5 minutes:

In the JSON response i see the VIN, color code and odometer of my car. So it is clearly my car. I also can see that “premium_ends_at” 22.2.2026. But i can see no charge information. For me it seems that additional information is missing.

Thank you for the hint about the “trace” log. Do you have an idea, why there are too less information requested by the binding or answered by teslascope.

38

Currently the binding only requests the vehicles basic information and not the vehicles detailed information. I am only a teslascope free member within trial period and not a plus oder pro member. I think this is the reason.

I just had a look at Teslascopes developer documentation. There i can see, that free members cannot acces the detailed information. I only want to read the battery SOC from my car. My hope was that this is possible also for free member.

Now i know Teslascope will be useless for me and i have to look for something different :pensive_face: