I just discovered that it seems like my IotaWatt has suddenly stopped sending data to EmonCMS. Both the IotaWatt and EmonCMS are up and reachable, and on the same network, and in the IotaWatt’s interface, I can see that it’s still logging data, however, in EmonCMS, it’s listed as ‘Inactive’, and even after rebooting both the IotaWatt and EmonCMS, it’s still not reporting in. I had thought that maybe it’s EmonCMS, but I’m not sure how likely that is as I have two other Wifi ESP8266-based nodes that are still reporting in just fine. Any suggestions as to what I might be able to look at to see why it doesn’t seem to be sending to EmonCMS?
Can you upload a copy of your config.txt file in a private message?
Also, please post the recent message log.
I had the same issue. It seems it has to do with the https part in Emoncms’s Data Uploader setting. Message log says:
5/03/21 19:50:58 emoncms: HTTPS specified but no HTTPSproxy server configured, stopping.
The message before is the update:
5/03/21 18:50:57z Updater: Installing update files for version 02_06_02
The hour in between has to do with time zones i think (so its a second instead of an hour). If you change https to http, it starts uploading again. https still has my preference.
Thanks for that post. I was pretty sure it was related to the 02_06_02 release, but no idea what the issue was. 02_06_02 has been out in ALPHA since March 20 and no current issues.
Even though older releases accepted the https:// URL for Emoncms, http:// is actually used. Note that there has always been an alternative encrypted protocol for Emoncms that is used when the account number is specified.
With 02_06_02, there is now a way to actually send https:// transactions through a proxy server, as explained in the docs: https://docs.iotawatt.com/en/02_06_00/HTTPSproxy.html
When a proxy server is configured, specifying https:// takes on new meaning. So the options are:
-
Change the https:// to http:// and specify the account to get alternate encryption.
-
Provide a https:// proxy server.
While the Emoncms uploader is stopped, the IoTaWatt is still logging as usual. After uploading is restored by one of the above methods. the backlog will be uploaded automatically, so nothing lost.
That’s right. The timestamp that end with ‘z’ is UTC time. The other is local time.
If I’m understanding your reply, it sounds like in the past, if ‘https’ was used for the EmonCMS address, it would still work and send over HTTP, but EmonCMS will use some form of encryption if a username is specified. My config shows the EmonCMS address configured with ‘http://’, not ‘https://’, and I’m using an API key, userid field is blank.
Thank you for your, as always, quick reply. As i understand, http is not encrypted, https is. Nobody can see what i send to emoncms’s servers. If i understand correctly, with this new firmware a https proxy server is mandatory to send data over an encrypted connection.
Im using InfluxDB since my latest topic on these forums. Since the server is running locally i dont mind running it over http. But emoncms does not run locally and i care about my privacy. I presume im missing something to get this back to work to https.
Change the https:// to http:// and specify the account to get alternate encryption.
Could you clarify what you mean by in the case of emoncms?
Edit:
If I’m understanding your reply, it sounds like in the past, if ‘https’ was used for the EmonCMS address, it would still work and send over HTTP, but EmonCMS will use some form of encryption if a username is specified. My config shows the EmonCMS address configured with ‘http://’. not ‘https://’, and I’m using an API key, userid field is blank.
I should read more often. Settings say:
Specifying userid triggers secure encrypted protocol.
I’ve got it specified. Curious as to how this gonna work for Cougar281.
Right, https:// uses TLS or Transport Level Security. Lower level; layers of the TCP stack handshake with the server, validate it’s domain, establish a shared key and encrypt the entire message using that shared key. IoTaWatt doesn’t have the resources to do that, so Emoncms has a higher level protocol where the data is encrypted using the shared secret API key.
https has never worked with Emoncms or anything else. It was an oversight to allow it to be specified.
@Cougar281 has a different problem.
I’m not sure if that’s a good thing or not 