OK, I've just been upgraded to 1.20.0 at last. For logging only, you need to do the following things:
- 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.
This is should be all you need to get logging working again; you change your logging config to
https://powerwall (from say
http://192.168.1.123) and all of the API end points used for logging are still accessible.
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.