Integration Service not working for Powerwall SW Ver. 20.49.0

@bankstownbloke - it works, thank you!


 2021-02-10 09:13:09,382  INFO [Thread-2] (WebClient.java:226) - >>> https://192.168.0.136/api/login/Basic
2021-02-10 09:13:09,397  INFO [Thread-1] (Controller.java:435) - Found 1 Sensors
2021-02-10 09:13:09,397  INFO [Thread-1] (Controller.java:536) - Added Reader: powerwall0
2021-02-10 09:13:09,397  INFO [Thread-1] (ADataLogReader.java:350) - Output stop at 1080 minutes
2021-02-10 09:13:09,397  INFO [Thread-1] (Controller.java:560) - Log File: powerwall0 [PW0-2021-02-10.log]
2021-02-10 09:13:09,397  INFO [Thread-1] (Controller.java:572) - Export Sensor: 0, id: 0
2021-02-10 09:13:09,413  INFO [Thread-1] (Controller.java:579) - Service: [http://pvoutput.org:80/service/r2/addbatchstatus.jsp] Test: false, End: 18:00
2021-02-10 09:13:09,413  INFO [Thread-1] (Controller.java:587) - Loaded 1 Readers (Import: 0, Export: 1)
2021-02-10 09:13:10,647  INFO [Thread-1] (Controller.java:1524) - Records restored from status.log : 25932
2021-02-10 09:13:11,709  INFO [Thread-2] (PowerwallLogReader.java:72) - Successful gateway authentication
2021-02-10 09:13:11,709  INFO [Thread-2] (WebClient.java:356) - >>> https://192.168.0.136:443/api/meters/aggregates
2021-02-10 09:13:11,834  INFO [Thread-2] (WebClient.java:157) - >>> https://192.168.0.136/api/system_status/soe
2021-02-10 09:13:12,647  INFO [Thread-1] (Controller.java:731) - Startup Complete: Waiting for data...
2021-02-10 09:13:12,678  INFO [Thread-1] (Controller.java:1806) - >>> 20210210,09:15,-1.0,3536,-1,-1,-1000.0,-1.0,10,483.026,60,-3065.93,99.043,3536.38
2021-02-10 09:13:12,678  INFO [Thread-1] (WebClient.java:135) - >>> http://pvoutput.org:80/service/r2/addbatchstatus.jsp?data=20210210,09:15,-1.0,3536,-1,-1,-1000.0,-1.0,10,483.026,60,-3065.93,99.043,3536.38
2021-02-10 09:13:12,804  INFO [Thread-1] (Controller.java:1834) - <<< 20210210,09:15,1
2 Likes

Thanks for confirming this.

PVOutput Integration Service v1.5.5.1 released with the Powerwall authentication requirement for firmware version 20.49.0

5 Likes

I have just reinstalled using your updated PVOutput Integration Service v1.5.5.1 and everything is up and running again - many thanks for addressing this issue so promptly.

1 Like

Good work as always!
I installed everything from scratch using the PVOutput_Integration_Service_v1.5.5.1_Setup
and eventually got everything to work. However, it seems like the wrapper is a 32bit version while I only have JVM 64bit installed.
What do you recommend ?
Here is the error:
STATUS | wrapper | 2021/02/17 20:55:07 | --> Wrapper Started as Service
STATUS | wrapper | 2021/02/17 20:55:07 | Java Service Wrapper Community Edition 32-bit 3.5.4
STATUS | wrapper | 2021/02/17 20:55:07 | Copyright © 1999-2010 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2021/02/17 20:55:07 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2021/02/17 20:55:07 |
STATUS | wrapper | 2021/02/17 20:55:08 | Launching a JVM…
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: Initializing…
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager:
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: WARNING - Unable to load the Wrapper’s native library ‘wrapper.dll’.
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: The file is located on the path at the following location but
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: could not be loaded:
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: C:\Program Files (x86)\PVOutput\bin…\lib\wrapper.dll
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: Please verify that the file is both readable and executable by the
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: current user and that the file has not been corrupted in any way.
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: One common cause of this problem is running a 32-bit version
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa.
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: This is a 64-bit JVM.
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: Reported cause:
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: C:\Program Files (x86)\PVOutput\lib\wrapper.dll: Can’t load IA 32-bit .dll on a AMD 64-bit platform
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager: System signals will not be handled correctly.
INFO | jvm 1 | 2021/02/17 20:55:08 | WrapperManager:
INFO | jvm 1 | 2021/02/17 20:55:08 | *** Starting PVOutput Integration Service v1.5.5.1
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.runtime.name=Java™ SE Runtime Environment
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vm.version=25.281-b09
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vm.vendor=Oracle Corporation
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vendor.url=http://java.oracle.com/
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vm.name=Java HotSpot™ 64-Bit Server VM
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vm.specification.name=Java Virtual Machine Specification
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.runtime.version=1.8.0_281-b09
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.endorsed.dirs=C:\Program Files\Java\jre1.8.0_281\lib\endorsed
INFO | jvm 1 | 2021/02/17 20:55:08 | >> os.arch=amd64
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.io.tmpdir=C:\WINDOWS\system32\config\systemprofile\AppData\Local\Temp
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vm.specification.vendor=Oracle Corporation
INFO | jvm 1 | 2021/02/17 20:55:08 | >> os.name=Windows 10
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.library.path=…/lib
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.specification.name=Java Platform API Specification
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.class.version=52.0
INFO | jvm 1 | 2021/02/17 20:55:08 | >> os.version=10.0
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.awt.printerjob=sun.awt.windows.WPrinterJob
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.specification.version=1.8
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.class.path=…/lib/wrapper.jar;…/lib/org.pvoutput.integration.jar;…/lib/commons-logging-1.1.1.jar;…/lib/httpcore-4.1.2.jar;…/lib/httpclient-4.1.2.jar;…/lib/jetty-http-7.5.1.v20110908.jar;…/lib/jetty-util-7.5.1.v20110908.jar;…/lib/jetty-io-7.5.1.v20110908.jar;…/lib/jetty-server-7.5.1.v20110908.jar;…/lib/jetty-continuation-7.5.1.v20110908.jar;…/lib/servlet-api-2.5.jar;…/lib/json_simple-1.1.jar;…/lib/jxl.jar;…/lib/log4j-1.2.15.jar;…/lib/RXTXcomm.jar;…/lib/jackcess-1.2.2.jar;…/lib/bsh-core-2.0b4.jar;…/lib/sqlitejdbc-v056.jar;…/lib/commons-net-3.1.jar
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vm.specification.version=1.8
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.home=C:\Program Files\Java\jre1.8.0_281
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.specification.vendor=Oracle Corporation
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vm.info=mixed mode
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.version=1.8.0_281
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.ext.dirs=C:\Program Files\Java\jre1.8.0_281\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vendor=Oracle Corporation
INFO | jvm 1 | 2021/02/17 20:55:08 | >> java.vendor.url.bug=http://bugreport.sun.com/bugreport/

Could I suggest that this step is included in the “Upgrading.html” file in the update package? For my PW the default password is the last 5 digits of the serial number https://www.tesla.com/en_gb/support/energy/powerwall/own/monitoring-from-home-network .

Thanks for the install note, John.
I have added the lines to conf\powerwall.ini as per image:

however, getting this error:

NFO [Thread-2] (WebClient.java:226) - >>> https://192.168.1.zzz![19-002|602x500] /api/login/basic
2021-02-19 14:21:46,949 WARN [Thread-2] (DefaultRequestDirector.java:1095) - Authentication error: Unable to respond to any of these challenges: {}
2021-02-19 14:21:46,949 ERROR [Thread-2] (WebClient.java:298) - <<< [401] {“code”:401,“error”:“Provider does not exist basic”,“message”:“Login Error”}
2021-02-19 14:21:46,949 WARN [Thread-2] (PowerwallLogReader.java:77) - Failed gateway authentication

Is that first letter of “basic” case-sensitive? I used the capital letter as in the instructions.

You can check if the password OK by doing a manual login to the gateway’s IP address. It now wants an email address and password in order to show the animate power flow display.

1 Like

Brilliant John!
That was exactly it (Basic with a capital B).
All good now Thank you to you, bankstownbloke and rpfile for getting this working again.
Very happy!

Cheers

This is only a warning, the service should start and pvoutput.log will show activity.

Indeed it does! In fact it has been like that for years.

Let me ask you another thing. I had to services running one for direction = in and one = out
I remember that was your suggestion at the time.
If I just wanted to update the .jar and the two config files, would that be all that is needed?

Like you explained earlier during testing (See below)
" 1. Stop the service
2. Make a backup of file <pvoutput_install>\lib\org.pvoutput.integration.jar
3. Download the patch -

  1. Rename from org.pvoutput.integration_1.5.5.1.jar to org.pvoutput.integration.jar
  2. Copy org.pvoutput.integration.jar to the PVOutput installation lib folder, replacing the existing file.
  3. Edit conf\powerwall.ini and add lines with gateway ip
  • login-url=https://192.168.x.x/api/login/Basic
  • login-pass=your_password
  1. Start the service"

Yes, the jar should be replaced in both locations.

1 Like

Thanks for the suggestion, [bankstownbloke]. That, and googling around a few other sites, enabled me to get my monitoring back on the air. Here is the Linux script which I found to work:

token=curl -c cookies -s -k -X POST -H "Content-Type: application/json" -d '{"username":"customer","password":"yourteslapassword","force_sm_off":false}' https://teslalan.fritz.box/api/login/Basic | jq -r '.token'

curl -b cookies -s -k --header “AuthCookie=$token” “https://teslalan.fritz.box/api/system_status/soe” | jq -r ‘.percentage’

last month my Gateway 2 was replaced, basically by changing the guts. the sticker was not changed…that means i have no record of the password. Is there some way i can find it inside the box (happy to remove the inner cover)? Resetting the password requires me to know the wifi password to do the reset…and that’s what i don’t have as it is the old sticker!

Hi again,
I replaced the jar for both and they both work, however I still don’t get the extended data showing on pvoutput. It was working fine before the 20.49.
I was on 1.5.2 so maybe changing just the Jar file is not enough?

Never mind, what are the odds that my 1 year donation period had expired?
Gladly donated again and it is working fine now.
Keep up the good work and be safe!

Happily getting data again, however, I am not getting any generation data (even though solar data shows up on the extended page) I have double-checked the extended data settings on my pvoutput account against those on MikesGear’s great instructional website. The data is showing on the pvoutput.log, but is not rendering on the “Show Generation” page.
Anyone else seeing this since firmware upgrading 20.49 and software pvoutput.integration_1.5.5.1 update?

Penny dropped!
Need to go through the copy service and make adjustments (as per MikesGear instructions) to get Generation data.
I tried just adding the sign in changes to my generation service powerwall.ini, but that didn’t do it as I assume 1.5.5.1 has some changes to account for the new security measures, so need to go through the whole process again.

All working now.

I opened the inner panel and find that there is a different sticker on the new gateway guts. Trying that password gets me further - still an error - API limit reached for this endpoint

Anyone else seen that?__

And that now solved - too many attempts being carried out by the service with the old password. left it for an hour and it reset itself. all logging again thank goodness!