Jump to content

Tesla Node Stopped Working


Recommended Posts

Posted

@someguy Do the commands work in your setup - I think you have an older car that does not support virtual keys.  Please let me know as I expected to have to have special code for this case, but maybe Tesla handles this on their side

How would you expect the automation to work when car is offline - I assume there will be no triggers as data does not change.  Time since last update should show how old the data is, but I still do not see the use of old data in context of automation

Again, I am open to change the behavior if people request it 

Posted
13 hours ago, Panda88 said:

I would wake the car if it shows offline

No! Please don't wake the car (IMO). Some might want/need info while the car is idle/asleep, but in my use I'd prefer not to phantom drain the car just to send data to the eisy. I like how Tesla's own app has been able to not wake the car until you send a command to the car.

It would be interesting to learn what others are attempting to do with the plugin and the car that they would need the car to be online/awake more often. I prefer to leave the car in sleep mode as much as possible to save the phantom drain.

Posted

the commands do seem to work.  I did try the "honk" command and the first time I press it, I get the indication that it didn't work (in "Last Command Status" LCS), but the second time I press it, it works (LCS says "OK" and the car honks.  this would seem to be due to the car being asleep, but when I do this while it is awake, it still takes two commands (first one with an error) to get the horn to honk.

as far as the automation question:  the main thing that I'm using this for is to remind me to plug it in.  the data I'm using is "Homelink Nearby" and battery percentage.  I'd like these to be whatever the last known data is.

Posted (edited)

Currently - short poll updates data if car is on-line, long poll tried to wake the car and then fetch data, so users can play with these numbers.  

Tesla does offer an option to have an external server running to collect data and users would then poll this - data would automatically upload from the car once online.  However, this will require the UI team to implement and maintain this server - probably depends on number of requests for this - it should be the most energy efficient solution as data only uploads when car is on line 

Naturally one would be able to wake the car to get it to push data - I assume this is silimar to the tesla approach.  Another benefit is there would be no limits on API calls

 

Edited by Panda88
Posted
Quote

Tesla does offer an option to have an external server running to collect data and users would then poll this - data would automatically upload from the car once online.  However, this will require the UI team to implement and maintain this server - probably depends on number of requests for this - it should be the most energy efficient solution as data only uploads when car is on line 

 

I'm not sure I understand what you mean.  What would be the difference between my Polisy (or Eisy) collecting the data and an external server doing so?

Posted (edited)

It is similar - the car will push the data to the server  (either at Tesla or at UD) and the ISY will query the server - It is what is happening now, but there are limits on number of calls to retrieve data (to limit bandwidth at Tesla) - the external server would not have these limitation 

Currently the poll for more data is API call limited, so fewer updates will happen 

I think commands count would still be limited, but I do not know for sure.  

Tesla offers a prototype server to install, but I have not looked at it

Edited by Panda88
  • Thanks 1
Posted

Released a new beta 0.1.33 - give it a try - I think it is close 

Data will remain when EV is asleep or offline (time since last update and state is updated)

Fixed some bugs

Will try 2 times for commands if first fails (seems to be issue with old cars)

There may be an issue with Mobile App - some results shows numbers than text - may be fixed but cannot test it easily - may need to install in new node address 

 

Posted (edited)

is the best way to upgrade to press the update button in the PG3x node page?

and Thank you!!

1.33 is not up yet.  the 1.27 version is the latest version I can see.  

Edited by someguy
Posted

It may take a little time to propagate 

If you want to test the mobile App - I would reinstall in new slot 

If just using AC - I would just upgrade - it should work - it is difficult for me to test as I do not have an EV to test 

 

Posted (edited)

Not sure what that means - let me try to rebuild and issue a new version. Mine installs fine, but I have the new library that I added already - Did you try to force an update from the store?

Can you PM me the log Package file 

Edited by Panda88
Posted (edited)

It is correct - it is a new node with a new code base so not easy to move back into the original one 

Furthermore, Michel and team have been helping by making and running a server to allow commands to be transferred to the car. 

If important you could try to reach out to Michel and see if he will allow a transfer - I would be fine with it, but since Michel and team are running a server now to allow commands, I think it is fair they get a little extra income to compensate for this (It is not to make money I do this - it is more for fun and to keep my brain going)

 

Edited by Panda88
Posted

Thank you so much for your efforts in this.  When Awake, i'm receiveing data from my tesla just fine.  However, it doesn't seem to be receiving data when I send a command from my eISY to the car.  Is the data stream one way, or might have i configured something incorrectly?

Posted

Everything seems to work.  Then, after a few minutes, all the fields change to unknown or not reported and I have to hit the update status button.  And after hitting update, it only updates the screen I'm on.  The climate screen for example continues to say unknown after hitting update on the charge screen.  Even though it reports the last update as 0 minutes ago.

Posted (edited)

If I put it in a different location I will need to rewrite all of my programs.  I just don't see why it would have a problem at one node location and not another.  They all function the same using the same code and same hardware.

And yes, unknown and not reported is what it says on the admin console until I hit the update button.  Then after a period of time, maybe 10 or 15 minutes, it reverts to unknown/not reported

Edited by apostolakisl
Posted

some times the config files are “sticky” and do not get replaced.   at least that is what i think is happening.  i have had issues where an updates will not install but the same code is fine in a new slot

it is pg3x behavior.  i have no control

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...