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.

@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!

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

I'm on PG3x 3.2.27. polisy and UI: IoX v.5.8.4 my weatherflow data comes from my own weather station on my roof.

After a power outage or power cycling my entire Polisy (isy and PG3x), I always have to go into PG3x and click “restart” to get the data into Polisy. FYI: the info is in the PG3x before I restart it but Polisy doesn’t know that data, so to speak. many suggestions?

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

I've use the Elk RP2 to connect an Elk-6052 smoke detector to my Elk M1 Gold. I'd like to confirm that I have it set up correctly. what settings should I have for "Set Send On for", "Set Send Off For" "Use off node" and "set Poll Voltage"? I'm not sure what these last two really mean. and one more question: how do I test the smoke detector. Pressing and holding the middle of it makes it beep but I'm not able to comfirm that it is telling my alarm that there is smoke, so to speak.

I tried creating a “spoken” in the portal and the only option it gives me is for the weather flow device itself, not its different values to assign to a spoken. Any suggestion?

My Elk is up and running, connected through the PG3 nodeserver, but when I try to assign a "spoke" to it, I click the "ELK" button at the top and I get this error: the other buttons work, by the way. any suggestions?

Okay, thank you! And Thank you to Michel!

@Panda88: any update on this? Or has anyone figured out a workaround. I’ve really appreciated this Tesla connection for some time and would sure love to get it back sometime soon.