TeslaEVStream

The new streaming node server for Tesla EVs have been released as a 90 day trial to the main (production) store The node uses streaming services, so the EV only sends data to the node when the data changes. Given this there is no need to poll data, and as a result there is less battery drain on the EV. Short-poll (5min default) sends a heartbeat and updates the EVs connection status (online, asleep, offline etc). Long-poll (2 hours default) check and updates tokens required to maintain the connection. A few more data fields have been added, and sentry mode control is now supported. It is expected that existing nodes will need to move to this node/mode…

I just tried out the new TeslaEVStream nodeserver and I get all of the nodes but they are all devoid of data. any suggestions?

The tesla plugin is currently free for a limited time, and we are trying to figure out the pricing model. Your input would be very useful. Using vehicule commands incurs a cost. From what I can see, some users do not issue much commands while others are issueing commands on schedules. Schedules like waking a car every 2 hours continuously incurs a high cost. To keep the plugin affordable, we think we need to implement rate limits on wake ups and vehicle commands. I'm currently thinking of these limits: 10 vehicle commands per day 2 wake ups per day (These are the most expensive API calls) FYI, when a command that requires the car to be w…

I switched to the new streaming plugin a week or so ago. Since then a lot of my use cases have stopped working correctly due to out of date information, and no way to trigger an update. One of the main use cases for me has been using the plugin to start/stop charging based on the status of the car (rather than just a plain X-X schedule). I also use it to flash lights in the house if I run our goodnight routine and the car is not plugged in and below X% charge. I also have a button on a keypad link that is lit when the charger is connected, and now that light is never correct. Literally right now it shows the charger port latch is engaged. It's not. The car is in the …

Just upgraded to the new plugin. The plugin installs OK and I get the 2 nodes, but most of the data is missing in the fields. Any suggestions? TeslaEVstream_4-21-2025_100948_AM.zip

A new TeslaEVstream node server has been added to the beta (non-production) store for testing It uses the new tesla official streaming interface allowing data to update when data changes on the EV - NO NEED TO POLL DATA. This node will replace the existing udiTeslaEV2 node going forward. If more or different data is desired take a look at https://developer.tesla.com/docs/fleet-api/fleet-telemetry/available-data to see what data is available (long list) and let me know. I can try to add it during this beta release Short Poll generates a hear beat Long Poll updates the state of the car (Online, Offline , asleep etc). It also checks if tokens need …

Hi This is a heads up - Tesla is planning to charge for access to the API. We are working on an option for streaming changes to the car (vs. polling) and this should be lower cost, but is still work in progress. Note this only works for newer cars + 2021 Suggest to lower the update rate to the case and only wake it if it makes sense When developing the streaming option - are there fields of interest that should be added (I'll see if it is available) - there is a lot more data available

Stopped getting any data from the car. I tried restarting, then rebooting polisy then deleted and readded node. I get the following error 2024-01-25 13:26:01,163 Thread-7 udi_interface ERROR TeslaCloudEVapi:teslaEV_GetIdList: Error getting vehicle list 2024-01-25 13:26:01,164 Thread-7 udi_interface ERROR TeslaCloudEVapi:teslaEV_GetIdList: Trying to reconnect 2024-01-25 13:26:02,051 Thread-7 udi_interface ERROR TeslaEVController:createNodes: Exception Controller start: object of type 'NoneType' has no len() It shows that it is connected and I get the Tesla Node in the admin console but it says zero vehicles.

I have installed the new NS and installed in PG3 (latest firmware). Restarted the NS and ran authenticate, which took me to Tesla.com where I signed in (for my 2017 Model S). NS then returned 4 nodes: Charging info (with 20 sub nodes, most showing data), Climate info (17 sub nodes, most showing data), Tesla EV info (5 sub nodes) and Merrick Tesla (18 sub nodes, mose showing data). On the AC, only 2 nodes show up (see attached) with no data. Attaching the log and some screen shots. Not sure where to go from here. udiTeslaEV2_1-4-2025_12726_PM.zip

I am noticing that my data stops updating after some period of time, maybe a week or so, after I "authenticate" the nodeserver in the PG3x console. once the data gets frozen, in the debug file, it says "Token Expired", and re-authenticating it fixes the problem. any suggestion as to how to avoid having to re-authenticate it routinely?

I made a new release with some of the requested changes Note, it does not address how to deal with Tesla wanting money to use the API (going forward) - we are looking at different options to address this, but no decision made yet. Note, unless you are on OS14, it seems like it is not possible to update the node - it needs to be reinstalled

somehow the data stopped showing up in my admin console, even though it is all in the Nodeserver. any suggestions as to how to diagnose and fix this?

Tesla has now implemented a monthly fee for using the official Tesla API for controlling and accessing information of your Tesla vehicles and energy solutions. I wonder if the UDI Tesla EV2 and UDI Tesla PW2 node servers are going to need to switch to a monthly charge to cover the Tesla API fees?

Hi, Proud owner of a 2024 M3 in Gatineau, Quebec, Canada. I just bought the new Tesla NS. Thanks for reviving this. Right off the bat, clicking this link https://tesla.com/_ak/my.isy.io on the mobile device where the Tesla app is installed won't let me install a virtual key. Basically, I can't send commands to my car. No honk, no trunk, no frunk. etc. And I know my car is compatible with virtual keys because I have another app that needs a Vkey and it works flawlessly. This is what the Tesla app shows : ----------------------------------------- That being said, I am able to authenticate the NS through PG3x 3.2.27. The authentication is sho…

I just played around with this nodeserver a bit and I noticed if I press the "update EV status" in the main node (as opposed to the "Charging info" and the "climate info" node) it only updates the data inside that node. I have to go to the "charging info" node and press "update system data" to get that node to update and then I have to go to the "climate info" node and press "update EV climate data" to get that node to update. I can't imagine why it wouldn't pull all data if it is going to wake up the car... or is it waking the car? is there a single/best command to use in programs to get the most up to date data? and do some commands only get data from a server …

release 0.1.37 Fixed some labeling issues Changed AC to display time since last update (minutes) even if car is offline Few other bug fixes

I have released a new TeslaEV2 node server. It uses the official API (with some restrictions imposed by the API) It uses better security and does not require getting the token It only operates on PG3x There are likely still bugs (especially around sending commands) as I do not have a car locally to test it on The first thing to do is to install a virtual key on the car (allowing commands to be sent) - This is currently only supported for NA EVs On your mobile device open https://tesla.com/_ak/my.isy.io (in browser). It should open the tesla App and you can approve the installation - if the car is too old it may just say it is not needed Ne…

Is anybody else having issues with the node server working? I'm getting this error 2023-06-12 20:08:49,313 Thread-6 udi_interface ERROR TeslaEVController:createNodes: Exception Controller start: 'display_name' 2023-06-12 20:08:49,313 Thread-6 udi_interface INFO TeslaEVController:createNodes: Did not obtain data from EV I tried redoing the refresh token but it did not help and I'm wondering if there is an issue because Tesla changed something.

I have seen this twice now. Tesla server seems to have gone down for a period of time, the node says "failed", but when the Tesla server comes back online, the node still says "failed". Restarting the node does the trick, but it seems like it should have a mechanism to fix itself in this situation.

when i park my car at the airport, my battery seems to go down fairly quickly. I was thinking that it was because my Node Server is keeping the car "awake" often. is this the case? if so, what could I do to stop it from waking my car up (and wasting battery)? turn off the Node Server when I am parked at the airport? or tweak the settings of the Node Server?

Has anyone been able to get TeslaEV to work? It asks for a token, which I can supply but there is no filed in the config for me to add that. I can add a field manually but I don't know what to enter and where.

I have not really used this node server for anything but to show status until today I tried to setup so I could turn the seat heaters on before heading out without opening the app on my phone but the commands don't seem to work but I can see the state change from action done in the app when I update data. Below is the error I see in the log 2022-12-16 20:04:48,965 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed climate1.runCmd(SEAT1) unhashable type: 'dict' Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 795, in _handleInput self.nodes_interna…

I put his here, because this is the current node server having this issue, but I have had this happen many times. I am running 2.0.6 and it says there is an update. I restart, it briefly shows the new version (2.0.8) and then switches back to 2.0.6 and tells me to restart for the update. I even tried restarting PG3, same thing. I also have several other nodes that tell me to restart for a new, even though the current running version is the same as listed in the store. For example, the itach node currently tells me to restart for a new version even though it is running the current version.

Just released 0.2.6 - some new functionality - A reboot of IoP is probably needed to enable all

Hi, would like to also see mileage available displayed on the Charging Info page or where appropriate maybe some time in the future. Thanks Gary