Sorry, the I meant to enter https. I also checked my router and this is the correct IP. Did you see my post above that I called Tesla and they confirmed that they remotely shutoff my access to the API and the Wizard? Initially upon receiving 1.20.0 I was able to change the pvoutput ini files to https and that worked, but two days later my access was fully shutoff.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Firmware 1.20.0
- Thread starter Parzival
- Start date
Sorry - I lost track of the thread and who was posting what. I'm kind of surprised they would completely shut off the web interface. I can understand blocking the Wizard, but I don't see why they would shut off the status display, which is all that pvoutput integration requires.
Unfortunately I don't know what they've done to your system. It's quite possible they just turned off the web server, in which case there would be no way to access the wizard on the local interface. I'm hoping they don't do the same to mine. I'm kind of regretting calling Powerwall support now.
Jigglypuff
Member
I'm not sure if this issue was mentioned earlier but I am no longer able, using the Tesla mobile application, to change the Operation Mode or modify Reserve %age of my Powerwall 2. It has recently updated to V1.20 from 1.17
We had a 6 hour scheduled grid outage yesterday and I tried to change, in advance, the mode to backup only. The app accepted the change but (after waiting an hour) there was no discernible change in Powerwall behaviour (ie charging from the grid). I then tried increasing the reserve &age and that also made no difference. Again the app accepted the update but no behavioural change occurred.
Luckily it was a sunny day and the previously set 15%+solar was enough to get me through the day (I work online from home).
24 hours later the app still shows the higher reserve &age but the powerwall itself still sits at 15%
Is this an issue with 1.20?
We had a 6 hour scheduled grid outage yesterday and I tried to change, in advance, the mode to backup only. The app accepted the change but (after waiting an hour) there was no discernible change in Powerwall behaviour (ie charging from the grid). I then tried increasing the reserve &age and that also made no difference. Again the app accepted the update but no behavioural change occurred.
Luckily it was a sunny day and the previously set 15%+solar was enough to get me through the day (I work online from home).
24 hours later the app still shows the higher reserve &age but the powerwall itself still sits at 15%
Is this an issue with 1.20?
Shygar
Member
I had to update my scripts to pull from https also and install the self signed cert into my keystone. It's working again to poll for the data
I got upgraded to 1.20.0 yesterday (at 7:25 pm, annoyingly). I tried to get the cert into the keystore, but obviously I don't understand my jdk well enough because it didn't work. I'm now using a cors proxy to convert to http. I need it any way because the non-authenticated API calls duplicate all the headers, which breaks CORS in a way that node.js doesn't like. I'd report the bug to Tesla, but I suspect they'd turn off my web interface if I did.
bkp_duke
Well-Known Member
We'll I'm now in the same boat and VERY pissed off about it. I got upgraded from 1.15.3 to 1.20.0 yesterday and output to PVOutput.org stopped.
Now today, my access to the web server via browser is not working.
EDIT - got the cert into the Java keystore. We will see if that fixes PVOutput or not.
Now today, my access to the web server via browser is not working.
EDIT - got the cert into the Java keystore. We will see if that fixes PVOutput or not.
Last edited:
Rang Tesla support last Friday. Tech could see that my customization updates were not taking effect. He tried forcing the update himself. After an appropriate wait (several hours) the update had still had no effect so he escalated the issue.
Monday morning it all came good. The update to the %age the tech applied was in effect and the local web interface was working again. As a test I adjusted the %age again and after the expected delay that also to effect sop I'm a happy customer again.
Firmware still shows as V1.20.0.
The exact same symptoms would happen to me when my gateway was connected to WiFi even on 1.15.0 (API endpoints were accessible though). Connecting to the Gateway via ethernet (it's actually ethernet to a separate Netgear WiFi Client Bridge) allowed me to use the Web UI again.
Since then, I've been upgraded to 1.20.0 and can still access the Web UI. Really not liking these changes though.
OK, I've just been upgraded to 1.20.0 at last. For logging only, you need to do the following things:
Control will require a change to your login json body, as well as possibly needed to change the installer password, but the API end points are still the same. I'll save that for another post.
- Set up a hosts entry (windows is \windows\system32\drivers\etc, *nix is /etc) for powerwall mapped to the IP address you've got your powerwall running on (use a static IP or DHCP assignment so it is always on the same IP) - you're probably doing this already if you're logging, but the key is the hosts name on the device doing the logging
- Navigate to https://powerwall on a browser on your logging device; you'll be prompted with a certificate error, but get past that to the point you can see the powerwall GUI.
- Now save the certificate to your device
- Now import the certificate; in windows, double click, choose to import to the Local Machine store, and choose to store in the Trusted Root Certificates store. For *nix / java, you'll need to install the certificate in your keystore.
- Close and re-open your browser; if you navigate to https://powerwall, you should not get any certificate warnings.
Control will require a change to your login json body, as well as possibly needed to change the installer password, but the API end points are still the same. I'll save that for another post.
bkp_duke
Well-Known Member
Thoughts on getting this to work if you can no longer get to the powerwall GUI? Tesla has turned this off for some of us (appears to be those of us pulling the data for export to PV Output).
For what it's worth, I've been pulling data to PVOutput since February and still have access to the web UI.
It might be worth trying to see if you can connect to the Powerwalls using the TEG-1AS wireless network. I'm wondering if the web UI will still be there.
Did you spontaneously lose access, or did it go away after you called support?
I am unable to connect to the web UI any method. I have tried many times to connect to the PW2 internal WiFi. I can connect to the WiFi without issue (TEG-7XX); however, I cannot connect to the web UI (Wizard or otherwise) through this connection or when on my WiFi. Please read post #6 above. I also called Tesla and they confirmed that they shutoff my web server remotely shortly after my 1.20.0 firmware update. My WiFi is still sending Tesla data, not their cellular. They seem to be targeting folks accessing the API. Trust me, all I used previously was PVOUTPUT.org integration services, nothing more. I'm pretty upset about the whole thing.
I'm pretty surprised that they would turn off the web interface even for access via the TEG wifi access point.
If a technician needed to get local access because their remote access wasn't working, they'd be replacing your gateway brains!
But, assuming that's what they've done, toggling the power switch on the powerwall (if you've got more than one powerwall any powerwall) might be enough - it's what is used to reset the password.
