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.

Do you haver a screen shot and log - It is always difficult to predict how the node fails, so If I can determine the failure, it should be possible to add the automatic reconnect 

 

43 minutes ago, Panda88 said:

Do you haver a screen shot and log - It is always difficult to predict how the node fails, so If I can determine the failure, it should be possible to add the automatic reconnect 

 

It isn't the node that fails per se, it is the Tesla server that goes offline, then the node isn't resetting when the server comes back online.  I knew that Tesla was offline because my Tesla phone app stopped working too.

Edited March 23, 20232 yr by apostolakisl

OK - I'll think about how to do this 

 

If PG3 is reporting the node server's status as "Failed", that means that it has stopped communicating with PG3. 

On 3/24/2023 at 1:04 PM, bpwwer said:

If PG3 is reporting the node server's status as "Failed", that means that it has stopped communicating with PG3. 

As far as I can tell, this has only happened twice, and both times I know that Tesla server was down because my phone app wouldn't talk to the car.  So the pathway to failure would seem to have something to do with the Tesla server not responding.

When/if it happens again, capture the node server log and send it to the Tesla node server author.

I tried to add some code to try to reconnect - I am not 100% sure how the node fails without log, but I gave it a try 

It is under beta test TesleEV_Beta (0.2.55) - let me know if it works - I have no way to test as I do not own a car

I also updated how I believe car is sleeping works now (API changed) 

Let me know if this works and/or has errors

 

@Panda88  Sorry, just noticed this today.  Hard to test since Tesla server needs to go down and who knows when that will happen.  Perhaps never?  Anyway, I'll load it up and let you know if there are any issues.

@Panda88 I wasn't able to find any beta version.  Also, installing a beta version means it will not have any of the programs and stuff I use with it to test unless I want to redo all of them.  I saw the beta version in my previous purchases section, but clicking on that didn't work.

I think I released the beta using the same node so it should be possible to install it and replace the existing one (and then do the same again with the released one) - that should prevent having to redo all the AC work

Let me know if it is not the case and I can try to do the release again into the beta store

I am travelling this week, so no easy access to my system so a new release would have to be next week