Start in initial setup: certificate issue?

Energy Monitors Powerwall
#1

I am new to PVOutput today. I am trying to configure my powerwall and solar setup. The service runs but I have an error which repeats every 30 seconds and I think no data is being collected.

Advice badly needed please!

here is the error from the log:

2019-02-25 22:39:57,409 INFO [Thread-2] (WebClient.java:243) - >>> http://10.0.0.169:80/api/meters/aggregates
2019-02-25 22:39:57,425 ERROR [Thread-2] (AHttpLogReader.java:463) - Http Error
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at sun.security.ssl.SSLSessionImpl.getPeerCertificates(Unknown Source)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:397)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at org.pvoutput.integration.reader.AHttpLogReader$ASimpleLogFileWriter.get(AHttpLogReader.java:430)
at org.pvoutput.integration.reader.AHttpLogReader$ASimpleLogFileWriter.run(AHttpLogReader.java:354)

#2

In the config file, try changing the ‘aggregates’ URL to ‘https’ at the beginning instead of ‘http’. The PW2 now uses a security certificate (albeit a badly borked one) and needs secure http.

2 Likes
#3

Thank you - exactly what it needed. If anyone is amending the install notes in future, it would be worth adding this as others as naïve as me may fall into the same hole.
The error with the certificate is that it is issued for the wrong address as well as I think being untrusted so as you say, a right messed up certificate!

1 Like
#4

Yup - we all spent much time diagnosing this when they added the certificate in a firmware update in June last year, and broke all the world’s monitoring until people added the https - and then tickled an obscure PVO bug that prevented the ‘charge %’ from being retreived for another month of hair-pulling. For amusement if nothing else, check through the thread of the time at Tesla Powerwall2 data to PVoutput?. Less than a year ago, seems like ages.:grinning: