someguy

I will try that now. I also considered deleting the nodeserver in the admin console, but wasn't sure what command to use to get the node to reincarnate itself in the admin console.

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?

for no apparent reason, and when all was working well previously, my data in the admin console for the Weatherflow nodeserver is blank. when I look in the PG3X, the data is there. any suggestions? I appreciate any help!!

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 and others ("wake up"?) get them from the car? a few more comments: 1 the "Honk" command now works on the first try (this was discussed previously). Thank you. 2 the "steering wheel heat" variable data says "unknown/not installed" when I do have that option. 3 what is "auto conditioning" vs. "cabin preconditioning"? which one is the one I'd want to turn on when I'm walking to the car to condition it NOW? also: word to the wise: don't change the name of your car (in your car's screen), it will cause problems with some of the ISY settings that you'll have to work on to fix.

the package is too large to PM it, for some reason. I sent the last part of the log, hoping that will work.

I was able to get to the 0.1.34 version but I am getting an "update check failed" error.

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.

@paulbatesOkay, thank you. much appreciated!

here is the file

if someone could point me to some instructions, I'd appreciate it. otherwise, I'd like to have some simple (embarrassing) questions answered: --when I go to the log page, the page is initially blank, then information starts showing up. is this because it only starts logging when I open it? --which of the settings (debug, warning, critical, etc) includes all of the information? --is there a dictionary or somewhere that I can read to better understand the log? what (computer) language is it in?

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?

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.

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.

I notice that my values in almost all of the nodes in the Nodeserver are 99. any suggestions to fix this?

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.