I finally got a successful response back from the meter after hours of no response. This query was sent manually from a different RPi4 than my HassOS RPi. I wanted to see what the complete transaction looked like, not just the grepped meter value. I checked that I used the correct command to generate my key and cert files. Does anybody who is familiar with this kind of input see anything wrong that would upset the meter agent and cause it to close the port?
root@192:~# OPENSSL_CONF=openssl.conf curl --ciphers ECDHE-ECDSA-AES128-CCM8 --insecure -v --url https://192.168.0.12:8081/upt/1/mr/1/r --cert cert.pem --key key.pem
* Trying 192.168.0.12:8081...
* Connected to 192.168.0.12 (192.168.0.12) port 8081 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ECDHE-ECDSA-AES128-CCM8
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Request CERT (13):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, CERT verify (15):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-CCM8
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: [NONE]
* start date: Mar 17 01:53:09 2023 GMT
* expire date: Dec 31 23:59:00 9999 GMT
* issuer: C=US; O=Itron; CN=IEEE 2030.5 MICA; serialNumber=7
* SSL certificate verify result: self-signed certificate in certificate chain (19), continuing anyway.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET /upt/1/mr/1/r HTTP/1.1
> Host: 192.168.0.12:8081
> User-Agent: curl/7.81.0
> Accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Thu, 25 May 2023 22:22:09 GMT
< Content-Length: 252
< Content-Type: application/sep+xml
<
<Reading
xmlns="urn:ieee:std:2030.5:ns"
href="/upt/1/mr/1/r">
<qualityFlags>01</qualityFlags>
<timePeriod>
<duration>1</duration>
<start>1685053328</start>
</timePeriod>
<value>567</value>
</Reading>
* Connection #0 to host 192.168.0.12 left intact
In order to hopefully add something of value as well, I want to post what I found regarding reading the actual meter display:
TL Index is the smaller numbers displayed at the top left. Symbols in parentheses are the small icons displayed at the bottom)