3 hours ago, Panda88 said:

We are working on getting a updated node server working.   Tesla is slowly moving to a new API

 I have released a new node server for Tesla power wall.  UdiTeslaPW2 that uses the new API

Still working on teslaEV.  Tesla added an additional layer of security when controlling the car and this needs to get implemented 

Thank you for your efforts - they are greatly appreciated.

@Panda88 is there any news on when this update will be available?

We have not managed to get the control working yet - effort with UDI - we are still looking but not sure what is not working correctly - sorry 

Is anybody actually working on this?  It has been like 9 months now.

any update on this nodeserver?  I'm looking for some hope that it will be restored to functionality at some point. 😀

Still working on it - we have a server now by Universal devices that helps send the commands - it is not stable yet, but it is making some progress - we can send a command some times

 

There is a beta version in the non-commercial node store to try udiTeslaEV2

I believe the controls work now, but have not been able to test (as I do not have an EV).  

I requires PG3x

Please let me know of issues and incluce a log file for debugging purposes 

To enable commands a electronic key needs to be installed on the car

Got to 

https://tesla.com/_ak/my.isy.io on you mobile device  - this should open the tesla moble app and you can then apprive the installation of the key (I have not personally tried this so I do not know what it will look like)

 

Edited October 18, 20241 yr by Panda88
Added command info

@Panda88 I went to that link, I got this message:   
 

 

I am also getting an error in the new udiTeslaEV2 node server that says “please initiate authentication “.  
 

i put the “REFRESH_TOKEN” in there correctly, by the way. 
 

i really appreciate any help with this!

Edited October 19, 2024Oct 19 by someguy

I do not understand how you can add the token - it should not be needed anymore.   

You should just click the authenticate button when it shows  (on top of node) and you will be taken to a login site at Tesla.

It is possible your car is so old that the virtual key is not supported (there is a limit).  My guess is I can send commends directly without the need for 2nd layer of encryption but I do not know 

We can give it a try once you have the basic node working (be able to see data from car)

PM me a log file and maybe I can figure something out

Hi, I just gave it a try and everything seems to be working. When the car went to sleep the NS, within the 10 min poll period  registered that the car was offline. After waking the car up with a request from the phone app the NS acquired all the data after the 10 min poll period. All the information looks to be present. However, I tried some of the commands like Honk Horn and they don't seem to work even though the car is awake Thanks so much for all your hard work on this difficult NS. 

Did you register the Virtual key.  No commands can be sent without if you have a recent car

 

I just did the authenticate button on the NS page. I was show things that could be authorized like info and commands and checked those off.

That was on the tesla site.

Hopefully this help on basic operation.   We can look at commands next

Thanks

I just copied the log from the Honk Horn command.

New Text Document (3).txt New Text Document (3).txt

13 hours ago, Panda88 said:

I do not understand how you can add the token - it should not be needed anymore.   

You should just click the authenticate button when it shows  (on top of node) and you will be taken to a login site at Tesla.

It is possible your car is so old that the virtual key is not supported (there is a limit).  My guess is I can send commends directly without the need for 2nd layer of encryption but I do not know 

We can give it a try once you have the basic node working (be able to see data from car)

PM me a log file and maybe I can figure something out

Okay, thank you.  I got it working with your further advice.  I didn't notice the "authenticate" button in the nodeserver.  and, by the way, the instructions in the new nodeserver still say to put in the "REFRESH_TOKEN" so that is why I did that. 

I do very much appreciate your time to get this thing working.  I'll report back here any (major) problems I have.  

12 hours ago, garybixler said:

I just copied the log from the Honk Horn command.

New Text Document (3).txt 16.26 kB · 3 downloads New Text Document (3).txt 16.26 kB · 0 downloads

Gary

From log

2024-10-19 22:32:22.008 Command    udi_interface      ERROR    TeslaOauth:_callApi: Call POST https://my.isy.io/api/tesla/api/1/vehicles/5YJSA1E53PF518311/command/honk_horn failed: 500 Server Error: Internal Server Error for url: https://my.isy.io/api/tesla/api/1/vehicles/5YJSA1E53PF518311/command/honk_horn
2024-10-19 22:32:22.008 Command    udi_interface      DEBUG    TeslaEVOauth:teslaEV_HonkHorn: teslaEV_HonkHorn unknown - {"response":null,"error":"vehicle rejected request: your public key has not been paired with the vehicle","error_description":""}

Looks like the virtual key registration did not work - did you try to open site https://tesla.com/_ak/my.isy.io on your mobile device  

58 minutes ago, someguy said:

Okay, thank you.  I got it working with your further advice.  I didn't notice the "authenticate" button in the nodeserver.  and, by the way, the instructions in the new nodeserver still say to put in the "REFRESH_TOKEN" so that is why I did that. 

I do very much appreciate your time to get this thing working.  I'll report back here any (major) problems I have.  

i'll try to find where it is in the documentation - 

Can you send me a log file when you say try to honk horm - maybe it will say something about how to identify if car can support virtual key or not and what to do in that case 

@Panda88 Thank you. That last step with the app did the trick. All is working now. Great job!

I notice that my values in almost all of the nodes in the Nodeserver are 99.  

any suggestions to fix this?

29 minutes ago, someguy said:

any suggestions to fix this

Have you restarted it lately? Make sure you close admin console (if it is open). Restart the plugin. Refresh the webpage. 

Is the car online?

okay, Thank you.  getting the car online and then restarting the Nodeserver has fixed the issue... for now.  I'll check in the future, but I am hopeful that the numbers won't revert to (mostly) 99 each time the car goes to sleep.  

It is default operation at this point when car is offline (not asleep).  I could change it to show last data but in my mind that is not useful either.  I would wake the car if it shows offline

I am open to change it asi am not sure how the border is being used