I can confirm that access to the aggregates works after changing to https, but access to the SOE doesn’t, now my system upgraded to 1.20.0 this morning.
I can’t see any change in the JSON output after changing to https:
This is the JSON output from the older version of firmware, that worked with a ‘http://’ (no ‘s’) URL:
This is the JSON output from the new firmware for https://192.168.0.63/api/system_status/soe
There is an extra digit after the decimal point, would that affect the parsing?
Perhaps the issue is with the setting up the SSL link now that the ‘s’ in https is required - although hard to see how the https processing would be different between the SOE URL (which doesn’t work) and the ‘aggregates’ URL for the other stats (which does work ok). Is there any difference in the code setting up the SSL link and processing the self-signed certificate between these two accesses?
I can punch a hole in the firewall and give you live access to test against BB, if it would help.