Now Im wondering, can the ESPAltherma post to Emoncms.org directly? or does the MQTT data need to be forwarded e.g via HomeAssistant? Looking at ESPAltherma/src/setup.h at main · raomin/ESPAltherma · GitHub I see no reference to HTTP/S. @borpin any ideas?
It looks like the issue here is that I’ve limited TLS support to versions 1.2 and 1.3 on the new server as is recommended. The developer of multisibcontrol kindly got in contact and mentioned that this was likely the case and that for windows XP compatibility multisibcontrol uses an older version of .NET without support for these newer TLS versions. The work around for now is for users using this software to use HTTP rather than HTTPS. http://emoncms.org (without the s) works ok, albeit without the secure benefits of HTTPS of course!
On closer inspection I think we moved away from supporting a fixed SHA-1 fingerprint a while ago. Richard is using a fixed ROOT CA configuration which is a different approach and will be updating his devices to the new version I believe.
Mine uses HA as the intermediary which @TrystanLea fixed for me with the white space fix. On mine the topics to upload to Emoncms is set in the config.yaml with the api key used.
John
1 Like
In my case ESPAltherma was posting directly to emoncms.org (but isn’t any longer).
As this doesn’t seem a robust way of doing it, I’ll get an HA bridge, I’ve been wanting to get HA set up for a while for other purposes anyway.
thanks!
2 Likes