PGHBubba Posted November 10 Posted November 10 (edited) @Panda88 I just updated to this version of the nodeserver and found that the status condition on Remaining Battery only allows "kWh" or "other" in program conditions whereas the previous version allowed %. There also appears to be a bug when "other" is selected as it only allows "98" or "no data" for the pull down. Any chance the remaining battery can be updated to also allow "%"? The remaining battery value when selected to either Index or kWh also does not report anything in program actions (it is reported on the status screen though). Edited November 10 by PGHBubba Tagged Author & Added additional bugs found. Quote
Panda88 Posted November 10 Posted November 10 I'll take a look - I think Remaining battery is no longer reported by Tesla as a percent, but I'll check again Quote
Panda88 Posted November 11 Posted November 11 BTW - it does seems like the old version is still working - in case you need the battery percentage Quote
PGHBubba Posted November 11 Author Posted November 11 Thanks. I think I will revert back to the old version. I did several experiments and cannot get the powerwall battery value in any program, even set as kWh. It shows up in the nodeserver (GV0) as the correct value as well as the admin console in the main screen and it matches my Tesla app but for whatever reason it is not able to be used in a program. Quote
Panda88 Posted November 11 Posted November 11 Did you install in new slot - or the same slot as before I do not have any of these issues Quote
PGHBubba Posted November 11 Author Posted November 11 Different slot. Tried various things: Stopping the old version. Then deleting the old version in case they were stepping on each other. I also lowered my battery level from 100% (we are in active storm watch mode all day due to weather) to see if it needed to change to be reported. No luck. I created a temporary variable to write the battery value to (as kWh) and it would never change (variable stays at 0.0000). Quote
Panda88 Posted November 11 Posted November 11 I see the problem Let me take a look and see if I can figure out what is happening - it is likely in the node definition Quote
Solution Panda88 Posted November 11 Solution Posted November 11 Found the issue I'll make a new version in a few min 0.1.25 It was a node definition problem 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.