API deprecated, Tesla will end support per 1/2024. How to move on? #67

Michael-K-at-GitHub · 2023-10-15T19:15:58Z

https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning

Following the release of Tesla Vehicle Command SDK support for REST API vehicle command endpoints is now reaching end of life. Starting 2024 most vehicles will require sending commands via Tesla Vehicle Command SDK.

Are there plans to revise node-red-contrib-tesla? Or do we have to assume that node-red-contrib-tesla will stop working at the beginning of 2024?

onokje · 2023-10-17T15:49:42Z

Good question. I haven't given this library much attention lately, but I am not giving up on it either. I will do some reading and let you know.

Michael-K-at-GitHub · 2023-11-30T22:33:01Z

Any update?

andrasg · 2024-01-19T10:17:58Z

I am not able to use commands, they result in 403, probably because of the deprecation of REST API's. Any plans for supporting the Tesla vehicle commands protocol?

I am assuming not much you can do, as probably the underlying TeslaJS library would need to support it...?

Michael-K-at-GitHub · 2024-01-23T07:42:03Z

I confirm that the old API has been turned off and this node no longer functions.

@onokje we need word from you, ether that you will look into this and find a solution, or that we have to move on to other solutions and abandon node-red-contrib-tesla

Lineflyer · 2024-01-23T08:40:45Z

Starting today it seems Tesla changed/deactivated the "old" API.

It stopped working and the node reports "Precondition failed". Even worse my node-red instance crashes each time I try to open the configuration node to add/change the tokens.

Any plans to work on it, any help I can provide?

onokje · 2024-01-23T08:49:08Z

Hi all, I will definitely take a look, because I still use this myself :) Unfortunately I don't have a lot of time right now, so any help is appreciated.

andrasg · 2024-01-23T08:53:53Z

TeslaJS folks are aware too, looks like they need to figure out auth first.
mseminatore/TeslaJS#353

fascenda · 2024-01-28T21:19:16Z

Sorry to read this, I don't even have my Tesla yet, and new to Node Red. At least you confirm the Precondition Failed return came from Tesla so I must have some configuration correct. (What a horrible choice of words when Precondition already has meaning for Climate and Battery, couldn't they dream of a different word for the API?)

I know it has subscription cost, but maybe node-red-contrib-tesla could use the Tessie API and shift the burden to them when Tesla changes their side. I've looked at Tessie and they expose their own API.

Lineflyer · 2024-01-28T21:24:13Z

@fascenda
The "Precondition failed" is an node internal error as it cannot get a valid result authenticating to the API. Sadly this also leads to a crash of whole node-red due to a seemingly unforeseen condition.

There is IMHO no need to change to some paid third party API. There is still a Tesla API, but just the endpoint and syntax changed. There is now a fleet API endpoint for companies, and also some other possible entry ways.

fascenda · 2024-01-28T21:35:52Z

Thanks @Lineflyer I did understand THAT use of Precondition was relating to the API, okay I see now it's HTTP response 412. Up until that I was getting a variety of other failures, so I call it a success that I got the error. (Along the way, I did have some crashing or hangups in the flow editor and had to restart node-red a few times.)

I agree relying on some subscription product would be best to avoid, as a long-retired software dev, I favor open source wherever I can find it. I just installed an OpenEVSE and also EmonCMS on a Raspberry PI for collecting data. That's where I will be collecting my Tesla data. As I said I don't even have the car yet just getting electric service upgraded and learning all this great software.

Lineflyer · 2024-01-28T21:44:38Z

The API was really great. You have been able to get all relevant (and even unrelevant) information about the current state of your car. For example: You even got the currently played song title ;)
I hope there will be a a way to get that back again...maybe its already possible right now, but I am not technically fit enough to implement a new API myself.

bkr1969 · 2024-01-30T01:24:15Z

I don't understand how the integration still works (all I needed to do was get a new refresh token). I can't seem to reconfigure the config node with this token though. And, unfortunately, I cannot delete it completely because even though all the nodes are deleted, it still shows "in use." Is there a way to reconfigure or can someone help me delete?

fascenda · 2024-01-30T18:56:07Z

@Lineflyer I read the Tesla "unofficial" API docs and I did see all the things you could do like see what's on the radio. I've been reading some of the updated docs, and again I don't have a Tesla (yet) so I'm only taking some of my past software experience and trying to learn/understand what I find in online documentation. It seems as if Tesla API will now only work with requests from known domains, so something like TeslaFi or Tessie (or many others) that have registered URL could gain access to it. That doesn't sound hopeful for our private servers running Node RED.

Which is what was on my mind when I said maybe going via Tessie is the solution, and I understand there is cost there. And I won't be surprised if Tesla starts charging for use of their API, which will potentially increase the cost of these middleware apps. Software has come a long way since I started my software career (40+ years ago). Subscription ($$$) is the way everything is going.

ASomerN · 2024-01-30T19:42:50Z

I've set up my system to move excess solar to the car automatically and that means having access to change amps, something I can't see how to do via tessie right now.

GaPhi · 2024-01-30T19:53:44Z

I have started this weekend a node-red mock-up that uses same messages content as this project do but using the new fleet API. SInce now, it seems working, but there still have some work to achieve to package it for its distribution... The job is not so huge to get it working, then something should come quite soon as a plug and play substitute of this node... Just be a bit patient, as I never coded a new node type. Maybe someone could help a bit? BTW, I have found some mistakes in teslamotors api documentation too, I still have to signal it to them to let them fix it. After this fleet API working with nodered, the telemetry API would be next challenge... Or the fleet API for recent models (I have a 2019 model S) then I do not need it (yet). Le mar. 30 janv. 2024 à 19:56, fascenda ***@***.***> a écrit :

…

@Lineflyer <https://github.com/Lineflyer> I read the Tesla "unofficial" API docs and I did see all the things you could do like see what's on the radio. I've been reading some of the updated docs, and again I don't have a Tesla (yet) so I'm only taking some of my past software experience and trying to learn/understand what I find in online documentation. It seems as if Tesla API will now only work with requests from known domains, so something like TeslaFi or Tessie (or many others) that have registered URL could gain access to it. That doesn't sound good for our private servers running Node RED. Which is what was on my mind when I said maybe going via Tessie is the solution, and I understand there is cost there. And I won't be surprised if Tesla starts charging for use of their API, which will potentially increase the cost of these middleware apps. *Software has come a long way since I started my software career (40+ years ago). Subscription ($$$) is the way everything is going.* — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADUNWNJAPFM4MYWEFNYHSMTYRE65LAVCNFSM6AAAAAA6BGRZ7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJXGY4TCNZVHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Lineflyer · 2024-01-30T20:20:42Z

@GaPhi That sounds great. Pergaps you should put your work on a pull request for this repository so that @onokje can take care of the packaging into a new version of this node?

dnlschmdt · 2024-01-30T20:51:50Z

I have made a few attempts:
After I changed the url from "vehicles" to "products" in line 662 in teslajs.js, the "vehicle or device" list worked again and node-red did not crash.

exports.vehicles = function vehicles(options, args, callback) {
    exports.get(options, '/api/1/products', null, callback);
}

I used @GaPhi fork of this tesla implementation.
After this it was possible to set charge amps and other commands. Getting vehicle data was not possible yet, but have just started.

GaPhi · 2024-01-30T21:30:29Z

Here is my mock-up flow, working with my own other flows... but probably not enough robust or well-packaged yet, and without any explanation about how to configure it... But if you are able to follow teslamotors partner registration process, you should be able to get it work too.

If some contributors are interested, we can set a little project up to progress faster.
The idea is to create 2 nodes :

tesla-api (compatibility with this github)
tesla-fleet (more efficient/evolutive one)
And configuration nodes for Client ID&Secrets/Regions/Domains&Callbacks.

Here is the file (copyright myself)
flows.json

bikeymouse · 2024-01-30T21:39:56Z

I've set up my system to move excess solar to the car automatically and that means having access to change amps, something I can't see how to do via tessie right now.

Have you looked at: https://developer.tessie.com/reference/set-charging-amps ?

bikeymouse · 2024-01-30T21:46:36Z

... But if you are able to follow teslamotors partner registration process, you should be able to get it work too.

Isn’t that the main problem?
Will Tesla really allow thousands of individual users register as “partner”? I think not.

bkr1969 · 2024-01-30T22:08:04Z

I have made a few attempts: After I changed the url from "vehicles" to "products" in line 662 in teslajs.js, the "vehicle or device" list worked again and node-red did not crash.
exports.vehicles = function vehicles(options, args, callback) {
    exports.get(options, '/api/1/products', null, callback);
}
I used @GaPhi fork of this tesla implementation. After this it was possible to set charge amps and other commands. Getting vehicle data was not possible yet, but have just started.

Where is this .js file located? (Using Home Assistant) I'd like to try that.

RobReus · 2024-01-30T22:31:32Z

I have made a few attempts: After I changed the url from "vehicles" to "products" in line 662 in teslajs.js, the "vehicle or device" list worked again and node-red did not crash.
exports.vehicles = function vehicles(options, args, callback) {
    exports.get(options, '/api/1/products', null, callback);
}
I used @GaPhi fork of this tesla implementation. After this it was possible to set charge amps and other commands. Getting vehicle data was not possible yet, but have just started.
Where is this .js file located? (Using Home Assistant) I'd like to try that.

I am running Node Red in a docker, and found the file at /data/node_modules/@gaphi/teslajs/teslajs.js. Check where palettes are installed and you will find it. Otherwise, just do a find -name teslajs.js in the root (/) of the filesystem and find it that way.

I just did this change and it has worked for me as well.

bkr1969 · 2024-01-30T22:32:42Z

Thanks. I started digging while waiting and found it. Giving it a try. Do I need to restart Node Red first?

RobReus · 2024-01-30T22:33:35Z

Thanks. I started digging while waiting and found it. Giving it a try. Do I need to restart Node Red first?

Perhaps. After I did the edit, I tried it which crashed my Node Red again, effectively restarting it. After that, it worked for me.

bkr1969 · 2024-01-30T22:35:36Z

Seems to have worked. I'm going to replace some spots in my flow and see how it does overall. Thanks for your help!

bkr1969 · 2024-01-30T22:48:49Z

Now, can someone tell me how to vent the windows using this API? Unfortunately I deleted all my old nodes and now I keep getting "missing command param" when I try. The climate setting works just fine.

bkr1969 · 2024-01-30T23:31:48Z

I've tested most of the other options and they seem to work . It almost seems like the specific command "windowControl" isn't working for some reason.

Lineflyer · 2024-06-08T18:32:29Z

The bearerToken I defined is simply used as a header information for the HTTP call as written in the Teslemetry documentation.
I defined it as follows:
flow.set('bearerToken', "Bearer " + accessToken)

So its simply your access token prepended by the string `Bearer ".

Within the http request node you have to add two headers as you may see in the screenshot:

I created a sample flow for you to import:

[
    {
        "id": "aa8dfd02dba5b031",
        "type": "function",
        "z": "d15d33a4fa9a8ad9",
        "name": "Build example call",
        "func": "// Call: https://api.teslemetry.com/api/1/vehicles/{vin}?token={token}\n\nlet base_url = \"https://api.teslemetry.com/api/1/vehicles/\"\nlet token = \"insert-your-access-token-here\"\nlet vin = \"insert-your-VIN-here\"\n\n// GET /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/vehicle_data\"\nlet query = \"?endpoints=charge_state%3Bclimate_state%3Bclosures_state%3Bdrive_state%3Bgui_settings%3Blocation_data%3Bvehicle_config%3Bvehicle_state\"\n\nlet url = base_url + vin + scope + query\n\nmsg.url = url\nmsg.bearerToken = \"Bearer \" + token\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 330,
        "y": 2800,
        "wires": [
            [
                "a53074dc554aa469"
            ]
        ]
    },
    {
        "id": "a53074dc554aa469",
        "type": "http request",
        "z": "d15d33a4fa9a8ad9",
        "name": "Teslemetry GET",
        "method": "GET",
        "ret": "obj",
        "paytoqs": "ignore",
        "url": "",
        "tls": "91a33722c228e6f1",
        "persist": false,
        "proxy": "",
        "insecureHTTPParser": false,
        "authType": "",
        "senderr": false,
        "headers": [
            {
                "keyType": "other",
                "keyValue": "authorization",
                "valueType": "msg",
                "valueValue": "bearerToken"
            },
            {
                "keyType": "other",
                "keyValue": "accept",
                "valueType": "other",
                "valueValue": " application/json"
            }
        ],
        "x": 540,
        "y": 2800,
        "wires": [
            [
                "e3633a059c5103aa"
            ]
        ]
    },
    {
        "id": "e3633a059c5103aa",
        "type": "change",
        "z": "d15d33a4fa9a8ad9",
        "name": "Remove response level from object to make it look like Node-Red-contrib-tesla",
        "rules": [
            {
                "t": "move",
                "p": "payload.response",
                "pt": "msg",
                "to": "payload",
                "tot": "msg"
            }
        ],
        "action": "",
        "property": "",
        "from": "",
        "to": "",
        "reg": false,
        "x": 940,
        "y": 2800,
        "wires": [
            []
        ]
    },
    {
        "id": "91a33722c228e6f1",
        "type": "tls-config",
        "name": "",
        "cert": "",
        "key": "",
        "ca": "",
        "certname": "",
        "keyname": "",
        "caname": "",
        "servername": "",
        "verifyservercert": true,
        "alpnprotocol": ""
    }
]

Underground56 · 2024-06-08T19:30:37Z

Oh man, thank you sooo much!!! It's working :) And even better, I have an example now to understand whats happening and hopefully learn the rest by myself.

I would very much like to show my appreciation...

Lineflyer · 2024-06-08T20:12:45Z

Great to hear, have fun.
I am not so 100% happy, that I now have to use paid services to access my Tesla. IMHO not a good choice by Tesla to no longer allow indiviudals free access....the car was expensive enough...

Underground56 · 2024-06-08T20:17:23Z

Yeah, that’s right. I was also quite wondering and annoyed that Tesla changed this service. However, other brands don’t even offer anything like that. Even things like changing charging current in the vehicle is by far not standard. So for me it is worth it…

ChutneyMary · 2024-06-08T21:32:08Z

Likewise, I really appreciate the sample flow from @Lineflyer. Working well now.

What's not so clear to me is how to send commands. The three commands I used previously were Start Charge, Stop Charge, and Set Charging Amps.

Any suggestions?

ChutneyMary · 2024-06-09T00:27:34Z

Answering my own question... Here's a sample flow for Start Charge, Stop Charge and Set Charging Amps to 5 -

[ { "id": "ea0ef801d947afae", "type": "function", "z": "f18596704a26bc97", "name": "Charge Stop", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_stop\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 500, "wires": [ [ "e00e92c60aa1e6b6" ] ] }, { "id": "84e52d1abe17ad5a", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 500, "wires": [ [ "ea0ef801d947afae" ] ] }, { "id": "e00e92c60aa1e6b6", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 500, "wires": [ [ "322dce8059e166de" ] ] }, { "id": "322dce8059e166de", "type": "debug", "z": "f18596704a26bc97", "name": "debug 20", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 500, "wires": [] }, { "id": "b8738ea936a56634", "type": "function", "z": "f18596704a26bc97", "name": "Charge Start", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_start\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 440, "wires": [ [ "febbe529f8d92091" ] ] }, { "id": "0b31a6e235d16557", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 440, "wires": [ [ "b8738ea936a56634" ] ] }, { "id": "febbe529f8d92091", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 440, "wires": [ [ "7bd53abd0b45ca30" ] ] }, { "id": "7bd53abd0b45ca30", "type": "debug", "z": "f18596704a26bc97", "name": "debug 21", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 440, "wires": [] }, { "id": "bdcd206cecb33a1e", "type": "function", "z": "f18596704a26bc97", "name": "Set Charging Amps 5", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/set_charging_amps\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nmsg.payload = {\"charging_amps\": \"5\"}; \n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 440, "y": 560, "wires": [ [ "9c11f1d5c1c00143" ] ] }, { "id": "55f10e8fd2475f49", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 560, "wires": [ [ "bdcd206cecb33a1e" ] ] }, { "id": "9c11f1d5c1c00143", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 560, "wires": [ [ "d101e512cbe59c5a" ] ] }, { "id": "d101e512cbe59c5a", "type": "debug", "z": "f18596704a26bc97", "name": "debug 22", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 560, "wires": [] }, { "id": "91a33722c228e6f1", "type": "tls-config", "name": "", "cert": "", "key": "", "ca": "", "certname": "", "keyname": "", "caname": "", "servername": "", "verifyservercert": true, "alpnprotocol": "" } ]

Underground56 · 2024-06-09T07:58:18Z

Great, many thanks ! The only thing for me that’s missing is how to wake up the car when sleeping. Any hint on this ?

ChutneyMary · 2024-06-09T08:59:25Z

Try the following flow. The "if (msg.payload == 1)" in the Function node is to prevent the Wake Up being triggered on a redeploy of flows.

[
    {
        "id": "26d458d88ccdaba8",
        "type": "inject",
        "z": "e7594237b03366b2",
        "name": "On only",
        "props": [
            {
                "p": "payload"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "1",
        "payloadType": "num",
        "x": 330,
        "y": 240,
        "wires": [
            [
                "7b307d3e82031041"
            ]
        ]
    },
    {
        "id": "7b307d3e82031041",
        "type": "function",
        "z": "e7594237b03366b2",
        "name": "Wake Up",
        "func": "if (msg.payload == 1) {\n    let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\n    let token = \"Your_Teslemetry_token_here\";\n    let vin = \"Your_VIN_here\";\n\n    // POST /api/1/vehicles/{vehicle_tag}/wake_up\n    let query = \"/wake_up\";\n\n    let url = base_url + vin + query;\n\n    // Configure the msg object for the HTTP request\n    msg.method = \"POST\";\n    msg.url = url;\n    msg.headers = {\n        'Authorization': \"Bearer \" + token,\n        'Content-Type': 'application/json'\n    };\n\n    return msg;\n} else {\n    return null;\n}",
        "outputs": 1,
        "timeout": "",
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 520,
        "y": 240,
        "wires": [
            [
                "454d77bb2ab5f4db"
            ]
        ]
    },
    {
        "id": "454d77bb2ab5f4db",
        "type": "http request",
        "z": "e7594237b03366b2",
        "name": "HTTP Request",
        "method": "use",
        "ret": "obj",
        "paytoqs": "ignore",
        "url": "",
        "tls": "91a33722c228e6f1",
        "persist": false,
        "proxy": "",
        "insecureHTTPParser": false,
        "authType": "",
        "senderr": false,
        "headers": [],
        "x": 740,
        "y": 240,
        "wires": [
            [
                "66d8774d0bb5a579"
            ]
        ]
    },
    {
        "id": "66d8774d0bb5a579",
        "type": "debug",
        "z": "e7594237b03366b2",
        "name": "debug 20",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 960,
        "y": 240,
        "wires": []
    },
    {
        "id": "91a33722c228e6f1",
        "type": "tls-config",
        "name": "",
        "cert": "",
        "key": "",
        "ca": "",
        "certname": "",
        "keyname": "",
        "caname": "",
        "servername": "",
        "verifyservercert": true,
        "alpnprotocol": ""
    }
]

Lineflyer · 2024-06-09T18:45:16Z

Great, many thanks ! The only thing for me that’s missing is how to wake up the car when sleeping. Any hint on this ?

Its in the API documentation.
You need to do a HTTP POST with following content (in the syntax of my flows):

// Call: POST /api/1/vehicles/{vehicle_tag}/wake_up

let base_url = "https://api.teslemetry.com/api/1/vehicles/"
let token = flow.get ('accessToken')
let vin = flow.get ('VIN')

let scope = "/wake_up"
let query = ""

let url = base_url + vin + scope + query

msg.url = url
msg.bearerToken = flow.get('bearerToken')
return msg;

Underground56 · 2024-06-09T20:54:06Z

Answering my own question... Here's a sample flow for Start Charge, Stop Charge and Set Charging Amps to 5 -

[ { "id": "ea0ef801d947afae", "type": "function", "z": "f18596704a26bc97", "name": "Charge Stop", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_stop\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 500, "wires": [ [ "e00e92c60aa1e6b6" ] ] }, { "id": "84e52d1abe17ad5a", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 500, "wires": [ [ "ea0ef801d947afae" ] ] }, { "id": "e00e92c60aa1e6b6", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 500, "wires": [ [ "322dce8059e166de" ] ] }, { "id": "322dce8059e166de", "type": "debug", "z": "f18596704a26bc97", "name": "debug 20", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 500, "wires": [] }, { "id": "b8738ea936a56634", "type": "function", "z": "f18596704a26bc97", "name": "Charge Start", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_start\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 440, "wires": [ [ "febbe529f8d92091" ] ] }, { "id": "0b31a6e235d16557", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 440, "wires": [ [ "b8738ea936a56634" ] ] }, { "id": "febbe529f8d92091", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 440, "wires": [ [ "7bd53abd0b45ca30" ] ] }, { "id": "7bd53abd0b45ca30", "type": "debug", "z": "f18596704a26bc97", "name": "debug 21", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 440, "wires": [] }, { "id": "bdcd206cecb33a1e", "type": "function", "z": "f18596704a26bc97", "name": "Set Charging Amps 5", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/set_charging_amps\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nmsg.payload = {\"charging_amps\": \"5\"}; \n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 440, "y": 560, "wires": [ [ "9c11f1d5c1c00143" ] ] }, { "id": "55f10e8fd2475f49", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 560, "wires": [ [ "bdcd206cecb33a1e" ] ] }, { "id": "9c11f1d5c1c00143", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 560, "wires": [ [ "d101e512cbe59c5a" ] ] }, { "id": "d101e512cbe59c5a", "type": "debug", "z": "f18596704a26bc97", "name": "debug 22", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 560, "wires": [] }, { "id": "91a33722c228e6f1", "type": "tls-config", "name": "", "cert": "", "key": "", "ca": "", "certname": "", "keyname": "", "caname": "", "servername": "", "verifyservercert": true, "alpnprotocol": "" } ]

Sorry, but this seems not to work for me. I get following error:
"..."
9.6.2024, 22:52:35node: debug 21
msg.payload : Object
object
response: null
error: "invalid_response"
error_description: "Command proxy response not json"
"..."

Any hint?

Jeoffreybauvin · 2024-06-11T21:45:18Z

If someone is interested, I developed a tiny HTTP API to make BLE request to my Tesla :

https://github.com/Jeoffreybauvin/tesla-http-api-over-ble

Basically, you'll need a bluetooth dongle, and your Tesla in range. I did it last night, so, it's pretty fresh :D.

Underground56 · 2024-06-12T06:52:21Z

Answering my own question... Here's a sample flow for Start Charge, Stop Charge and Set Charging Amps to 5 -

[ { "id": "ea0ef801d947afae", "type": "function", "z": "f18596704a26bc97", "name": "Charge Stop", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_stop\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 500, "wires": [ [ "e00e92c60aa1e6b6" ] ] }, { "id": "84e52d1abe17ad5a", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 500, "wires": [ [ "ea0ef801d947afae" ] ] }, { "id": "e00e92c60aa1e6b6", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 500, "wires": [ [ "322dce8059e166de" ] ] }, { "id": "322dce8059e166de", "type": "debug", "z": "f18596704a26bc97", "name": "debug 20", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 500, "wires": [] }, { "id": "b8738ea936a56634", "type": "function", "z": "f18596704a26bc97", "name": "Charge Start", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_start\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 440, "wires": [ [ "febbe529f8d92091" ] ] }, { "id": "0b31a6e235d16557", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 440, "wires": [ [ "b8738ea936a56634" ] ] }, { "id": "febbe529f8d92091", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 440, "wires": [ [ "7bd53abd0b45ca30" ] ] }, { "id": "7bd53abd0b45ca30", "type": "debug", "z": "f18596704a26bc97", "name": "debug 21", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 440, "wires": [] }, { "id": "bdcd206cecb33a1e", "type": "function", "z": "f18596704a26bc97", "name": "Set Charging Amps 5", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/set_charging_amps\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nmsg.payload = {\"charging_amps\": \"5\"}; \n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 440, "y": 560, "wires": [ [ "9c11f1d5c1c00143" ] ] }, { "id": "55f10e8fd2475f49", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 560, "wires": [ [ "bdcd206cecb33a1e" ] ] }, { "id": "9c11f1d5c1c00143", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 560, "wires": [ [ "d101e512cbe59c5a" ] ] }, { "id": "d101e512cbe59c5a", "type": "debug", "z": "f18596704a26bc97", "name": "debug 22", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 560, "wires": [] }, { "id": "91a33722c228e6f1", "type": "tls-config", "name": "", "cert": "", "key": "", "ca": "", "certname": "", "keyname": "", "caname": "", "servername": "", "verifyservercert": true, "alpnprotocol": "" } ]

Sorry, but this seems not to work for me. I get following error: "..." 9.6.2024, 22:52:35node: debug 21 msg.payload : Object object response: null error: "invalid_response" error_description: "Command proxy response not json" "..."

Any hint?

Can no one help on this issue? Reading the car data does work, but sending a command always results in the error above. Since the car is a leased company car my Access rights are "Driver, not "Owner". Maybe that makes a difference?

ChutneyMary · 2024-06-12T10:04:10Z

The short answer is, I don't know. Some things to check -

Have you linked the Virtual Key as pictured?

Your suspicion sounds correct though. Here's an excerpt out of the Teslemetry documentation under Topics / Access Type -

When a vehicle is shared by the OWNER to another account, you get DRIVER access. This is also common when the vehicle has been leased in European countries and the leasing company has retained OWNER permissions.
Unfortunately with the DRIVER permission you are unable to install the virtual key or configure Fleet Telemetry. Most of the Fleet API will still work except for commands, which depends on your vehicles Command Signing requirement. To fix this you will need to ask the owner to add the Virtual Key.

Underground56 · 2024-06-12T10:53:48Z

The short answer is, I don't know. Some things to check -

Have you linked the Virtual Key as pictured?

Your suspicion sounds correct though. Here's an excerpt out of the Teslemetry documentation under Topics / Access Type -

When a vehicle is shared by the OWNER to another account, you get DRIVER access. This is also common when the vehicle has been leased in European countries and the leasing company has retained OWNER permissions. Unfortunately with the DRIVER permission you are unable to install the virtual key or configure Fleet Telemetry. Most of the Fleet API will still work except for commands, which depends on your vehicles Command Signing requirement. To fix this you will need to ask the owner to add the Virtual Key.

Thank you ChutneyMary! I'm not able to setup a virtual key and I'm pretty sure also the leasing company won't do it for me. If it's true that even such "simple" commands like start charging are not supported without a virtual key, I'm in big trouble :( Since "Command Sign:REQUIRED" is displayed in the teslemetry console, I assume that's true :(

Does someone know which commands need a signing ? A list would be very helpful.

"..."
Unfortunately with the DRIVER permission you are unable to install the virtual key or configure Fleet Telemetry. Most of the Fleet API will still work except for commands, which depends on your vehicles Command Signing requirement. To fix this you will need to ask the owner to add the Virtual Key.
"..."

ChutneyMary · 2024-06-12T11:31:22Z

Read the Teslemetry documentation -
https://teslemetry.com/docs/topics/commandsigning

While this lists all the commands that do not support signing, I can only assume all the rest do require it.

I suggest you investigate the post a few lines above by @Jeoffreybauvin. The Tesla Bluetooth Low Energy API appears to support an off-line method of interacting with the vehicle. I haven't experimented with it yet, but perhaps @Jeoffreybauvin could clarify whether there's any cloud-based authentication occuring?

Jeoffreybauvin · 2024-06-12T12:58:44Z

Indeed @ChutneyMary , no internet access is needed to interact with the vehicle over BLE. The new key paired with the vehicle is seen as a "new car key" for controlling the vehicle.

Underground56 · 2024-06-12T18:10:37Z

I'm a bit smarter now: In the past it was necessary to be the owner of the car to be able to setup a virtual key. Since this is no good solution for all leased cars, Tesla changed it and it is now possible to setup a virtual key a Driver. You need to have the key card and you have to be in the car to do so. See also here:

teslamotors/vehicle-command#45

In car main menu->locks teslemetry is now displayed as Fleet Key, which seems to be fine. However, on Teslemetry console still Access Type:DRIVER Command Sign:REQUIRED is displayed and the Node Red flow is still not working. Maybe Teslemetry did not fully implement the latest changes? Could be true since their documentation does also not mention them...

Hopefully I will find the last parts of this puzzle ;)

tomashonajzer · 2024-06-16T13:50:17Z

Hi, I have copied

Answering my own question... Here's a sample flow for Start Charge, Stop Charge and Set Charging Amps to 5 -

[ { "id": "ea0ef801d947afae", "type": "function", "z": "f18596704a26bc97", "name": "Charge Stop", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_stop\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 500, "wires": [ [ "e00e92c60aa1e6b6" ] ] }, { "id": "84e52d1abe17ad5a", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 500, "wires": [ [ "ea0ef801d947afae" ] ] }, { "id": "e00e92c60aa1e6b6", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 500, "wires": [ [ "322dce8059e166de" ] ] }, { "id": "322dce8059e166de", "type": "debug", "z": "f18596704a26bc97", "name": "debug 20", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 500, "wires": [] }, { "id": "b8738ea936a56634", "type": "function", "z": "f18596704a26bc97", "name": "Charge Start", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/charge_start\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 410, "y": 440, "wires": [ [ "febbe529f8d92091" ] ] }, { "id": "0b31a6e235d16557", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 440, "wires": [ [ "b8738ea936a56634" ] ] }, { "id": "febbe529f8d92091", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 440, "wires": [ [ "7bd53abd0b45ca30" ] ] }, { "id": "7bd53abd0b45ca30", "type": "debug", "z": "f18596704a26bc97", "name": "debug 21", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 440, "wires": [] }, { "id": "bdcd206cecb33a1e", "type": "function", "z": "f18596704a26bc97", "name": "Set Charging Amps 5", "func": "let base_url = \"https://api.teslemetry.com/api/1/vehicles/\";\nlet token = \"Your_Teslemetry_Token_here\";\nlet vin = \"Your_VIN_here\";\n\n// POST /api/1/vehicles/{vehicle_tag}/vehicle_data\nlet scope = \"/command\";\nlet query = \"/set_charging_amps\";\n\nlet url = base_url + vin + scope + query;\n\n// Configure the msg object for the HTTP request\nmsg.method = \"POST\";\nmsg.url = url;\nmsg.headers = {\n    'Authorization': \"Bearer \" + token,\n    'Content-Type': 'application/json'\n};\n\nmsg.payload = {\"charging_amps\": \"5\"}; \n\nreturn msg;", "outputs": 1, "timeout": "", "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 440, "y": 560, "wires": [ [ "9c11f1d5c1c00143" ] ] }, { "id": "55f10e8fd2475f49", "type": "inject", "z": "f18596704a26bc97", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 240, "y": 560, "wires": [ [ "bdcd206cecb33a1e" ] ] }, { "id": "9c11f1d5c1c00143", "type": "http request", "z": "f18596704a26bc97", "name": "Teslemetry POST", "method": "use", "ret": "obj", "paytoqs": "ignore", "url": "", "tls": "91a33722c228e6f1", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "", "senderr": false, "headers": [], "x": 670, "y": 560, "wires": [ [ "d101e512cbe59c5a" ] ] }, { "id": "d101e512cbe59c5a", "type": "debug", "z": "f18596704a26bc97", "name": "debug 22", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 860, "y": 560, "wires": [] }, { "id": "91a33722c228e6f1", "type": "tls-config", "name": "", "cert": "", "key": "", "ca": "", "certname": "", "keyname": "", "caname": "", "servername": "", "verifyservercert": true, "alpnprotocol": "" } ]

hi, this is exactly what I was looking to do... unfortunately any attempt to make an API call ends with a message "invalid token" as shown below. I got the token from iOS app "Auth for Tesla" - tried Both listed on the app, no joy :-(((

{"status":401,"response":null,"error":"invalid_token","service":"auth"}

my flows are identical, imported from yours except for I have the token and vin in flow variables.

any idea what am I doing wrong? any advice much appreciated!

ChutneyMary · 2024-06-16T14:01:42Z

I got the token from iOS app "Auth for Tesla"

It won't work with the iOS app "Auth for Tesla".
I think you've missed a major component required in the flow. Read a bit further back in the thread for more info. The Token comes from a new service provided by a website called Teslemetry -

https://teslemetry.com/

tomashonajzer · 2024-06-16T15:13:21Z

I got the token from iOS app "Auth for Tesla"

It won't work with the iOS app "Auth for Tesla". I think you've missed a major component required in the flow. Read a bit further back in the thread for more info. The Token comes from a new service provided by a website called Teslemetry -

https://teslemetry.com/

thanks! :-) still need to figure out why I get "invalid_respose" while trying to set the charging amps but I at least manage to get some info from my Tesla having the account setup correctly.

Underground56 · 2024-06-16T20:38:12Z

I got the token from iOS app "Auth for Tesla"

It won't work with the iOS app "Auth for Tesla". I think you've missed a major component required in the flow. Read a bit further back in the thread for more info. The Token comes from a new service provided by a website called Teslemetry -
https://teslemetry.com/

thanks! :-) still need to figure out why I get "invalid_respose" while trying to set the charging amps but I at least manage to get some info from my Tesla having the account setup correctly.

Is your car a leased one? If yes and your Access Type ist "just" Driver and not owner, you have the same poblem as I have. See some post before...

tomashonajzer · 2024-06-16T21:12:44Z

I got the token from iOS app "Auth for Tesla"

It won't work with the iOS app "Auth for Tesla". I think you've missed a major component required in the flow. Read a bit further back in the thread for more info. The Token comes from a new service provided by a website called Teslemetry -
https://teslemetry.com/

thanks! :-) still need to figure out why I get "invalid_respose" while trying to set the charging amps but I at least manage to get some info from my Tesla having the account setup correctly.

Is your car a leased one? If yes and your Access Type ist "just" Driver and not owner, you have the same poblem as I have. See some post before...

I am the owner so it won't be the case; I believe it has something to do with the proxy setting -- no understanding here but it feels like it has something to do with the following.

https://developer.tesla.com/docs/fleet-api#charge_start

Newest vehicles require Tesla Vehicle Command protocol (see details).

I do not undestand what's involved but my Model 3 is 2023 version

Underground56 · 2024-06-17T06:08:24Z

Interesting! Since I also get the "invalid response" error, maybe it's not because of the Access Type.

Are you able to read the status of the car (see flow from Lineflyer above)? I can read the status, but not send commands

tomashonajzer · 2024-06-17T06:18:10Z

Same thing here. Its the SDK solvee by usimg a proxy. I am trying HA now it may work

…

On Mon 17. 6. 2024 at 8:08, Underground56 ***@***.***> wrote: Interesting! Since I also get the "invalid response" error, maybe it's not because of the Access Type. Are you able to read the status of the car (see flow from Lineflyer above)? I can read the status, but not send commands — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A44RIBHL4DMXP3QJ2UTN4ZDZHZ4O7AVCNFSM6AAAAAA6BGRZ7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGM3DENZVG4> . You are receiving this because you commented.Message ID: ***@***.***>

ChutneyMary · 2024-06-18T23:49:35Z

Hello @Jeoffreybauvin. I've dropped a question over in your github repository in the issues section. Can you please clarify the device and/or build environment you're running the Tesla BLE interface on? I'm not having much success on a Raspberry Pi Zero W (and first time user with Docker).

Underground56 · 2024-06-26T09:41:49Z

Same thing here. Its the SDK solvee by usimg a proxy. I am trying HA now it may work
…
On Mon 17. 6. 2024 at 8:08, Underground56 @.> wrote: Interesting! Since I also get the "invalid response" error, maybe it's not because of the Access Type. Are you able to read the status of the car (see flow from Lineflyer above)? I can read the status, but not send commands — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A44RIBHL4DMXP3QJ2UTN4ZDZHZ4O7AVCNFSM6AAAAAA6BGRZ7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGM3DENZVG4 . You are receiving this because you commented.Message ID: @.>

Were you able to solve this problem? I'm still hanging on this :( Teslemetry console also still tells me
Access Type: DRIVER
Command Sign: REQUIRED

However, in the car the virtual key seems to be installed correctly:

Very much appreciate every help...

tomashonajzer · 2024-06-26T09:43:41Z

I got it working on Home Assistant, can see all data, control the vehicle as needed.

…

On 26. 6. 2024, at 11:42, Underground56 ***@***.***> wrote: Same thing here. Its the SDK solvee by usimg a proxy. I am trying HA now it may work … <x-msg://25/#> On Mon 17. 6. 2024 at 8:08, Underground56 @.> wrote: Interesting! Since I also get the "invalid response" error, maybe it's not because of the Access Type. Are you able to read the status of the car (see flow from Lineflyer above)? I can read the status, but not send commands — Reply to this email directly, view it on GitHub <#67 (comment) <#67 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A44RIBHL4DMXP3QJ2UTN4ZDZHZ4O7AVCNFSM6AAAAAA6BGRZ7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGM3DENZVG4 . You are receiving this because you commented.Message ID: @.> Were you able to solve this problem? I'm still hanging on this :( Teslemetry console also still tells me Access Type: DRIVER Command Sign: REQUIRED However, in the car the virtual key seems to be installed correctly: teslemetry.jpg (view on web) <https://github.com/onokje/node-red-contrib-tesla/assets/172016531/9fe6ff3d-7a3b-45f2-81bb-7999d0a51e16> Very much appreciate every help... — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A44RIBCU4S774FS3SQSNB43ZJKEHLAVCNFSM6AAAAAA6BGRZ7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJRGI3DGMBVGE>. You are receiving this because you commented.

Underground56 · 2024-06-29T19:28:56Z

Same here: I got everything running (reading and writing values) with Home Assistent and Teslemetry now, so the problem I had has to do with the Node Red Integration. To be honest, I don't want to rebuild my complete logic in HA since I'm used to Node Red and thing the capabilities are much better.

Does anyone know if/when this problem can be fixed in Node Red? Also, I'm wondering why some guys are doing ok in Node red and some don't with the same Code?

tomashonajzer · 2024-06-30T05:52:37Z

I use HA to communicate via API but all the automation is done in nodered which is a part of HA package anyway. Both handy to be a part of home”package”Sent from my iPhoneOn 29. 6. 2024, at 21:29, Underground56 ***@***.***> wrote: Same here: I got everything running with Home Assistent, so the problem has to do with the Node Red Integration. To be honest, I don't want to rebuild my complete logic in HA since I'm used to Node Red and thing the capabilities are much better. Does anyone know if/when this problem can be fixed in Node Red? Also, I'm wondering why some guys are doing ok in Node red and some don't with the same Code? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

svwhisper · 2024-07-04T05:34:44Z

If someone is interested, I developed a tiny HTTP API to make BLE request to my Tesla :

https://github.com/Jeoffreybauvin/tesla-http-api-over-ble

Basically, you'll need a bluetooth dongle, and your Tesla in range. I did it last night, so, it's pretty fresh :D.

There's also this repo for a BLE Proxy: https://github.com/wimaha/TeslaBleHttpProxy

I've been using it for a week now, having migrated off first Telsa API to Tessie (paid service, though) and now off Tessie to local, no cloud involved. I've found I also need to use the Tesla wall connector API, but between that and the BLE proxy (and Node Red, of course), everything works as needed.

Lineflyer mentioned this issue Nov 13, 2023

No location information starting with vehicle software 2023.38.x #69

Open

cycl0ne mentioned this issue Jan 25, 2024

Vehicle list does not auto populate #73

Open

fascenda mentioned this issue Jan 30, 2024

Precondition failed #76

Open

API deprecated, Tesla will end support per 1/2024. How to move on? #67

API deprecated, Tesla will end support per 1/2024. How to move on? #67

Comments

Michael-K-at-GitHub commented Oct 15, 2023

onokje commented Oct 17, 2023

Michael-K-at-GitHub commented Nov 30, 2023

andrasg commented Jan 19, 2024

Michael-K-at-GitHub commented Jan 23, 2024

Lineflyer commented Jan 23, 2024

onokje commented Jan 23, 2024

andrasg commented Jan 23, 2024

fascenda commented Jan 28, 2024

Lineflyer commented Jan 28, 2024

fascenda commented Jan 28, 2024 • edited Loading

Lineflyer commented Jan 28, 2024

bkr1969 commented Jan 30, 2024

fascenda commented Jan 30, 2024 • edited Loading

ASomerN commented Jan 30, 2024

GaPhi commented Jan 30, 2024 via email

Lineflyer commented Jan 30, 2024

dnlschmdt commented Jan 30, 2024

GaPhi commented Jan 30, 2024

bikeymouse commented Jan 30, 2024

bikeymouse commented Jan 30, 2024 • edited Loading

bkr1969 commented Jan 30, 2024

RobReus commented Jan 30, 2024

bkr1969 commented Jan 30, 2024

RobReus commented Jan 30, 2024

bkr1969 commented Jan 30, 2024

bkr1969 commented Jan 30, 2024 • edited Loading

bkr1969 commented Jan 30, 2024

Lineflyer commented Jun 8, 2024

Underground56 commented Jun 8, 2024

Lineflyer commented Jun 8, 2024

Underground56 commented Jun 8, 2024

ChutneyMary commented Jun 8, 2024

ChutneyMary commented Jun 9, 2024 • edited Loading

Underground56 commented Jun 9, 2024

ChutneyMary commented Jun 9, 2024 • edited Loading

Lineflyer commented Jun 9, 2024

Underground56 commented Jun 9, 2024

Jeoffreybauvin commented Jun 11, 2024

Underground56 commented Jun 12, 2024

ChutneyMary commented Jun 12, 2024 • edited Loading

Underground56 commented Jun 12, 2024 • edited Loading

ChutneyMary commented Jun 12, 2024 • edited Loading

Jeoffreybauvin commented Jun 12, 2024

Underground56 commented Jun 12, 2024

tomashonajzer commented Jun 16, 2024

ChutneyMary commented Jun 16, 2024

tomashonajzer commented Jun 16, 2024

Underground56 commented Jun 16, 2024

tomashonajzer commented Jun 16, 2024

Underground56 commented Jun 17, 2024

tomashonajzer commented Jun 17, 2024 via email

ChutneyMary commented Jun 18, 2024

Underground56 commented Jun 26, 2024

tomashonajzer commented Jun 26, 2024 via email

Underground56 commented Jun 29, 2024 • edited Loading

tomashonajzer commented Jun 30, 2024 via email

svwhisper commented Jul 4, 2024

fascenda commented Jan 28, 2024 •

edited

Loading

fascenda commented Jan 30, 2024 •

edited

Loading

bikeymouse commented Jan 30, 2024 •

edited

Loading

bkr1969 commented Jan 30, 2024 •

edited

Loading

ChutneyMary commented Jun 9, 2024 •

edited

Loading

ChutneyMary commented Jun 9, 2024 •

edited

Loading

ChutneyMary commented Jun 12, 2024 •

edited

Loading

Underground56 commented Jun 12, 2024 •

edited

Loading

ChutneyMary commented Jun 12, 2024 •

edited

Loading

Underground56 commented Jun 29, 2024 •

edited

Loading