While let's encrypt is great when compared to not having anything.
There are conveniences ~$150 per year buys you with an okay wildcard certificate. Certificates being valid for a span of years... Free revocation and reissue all day every day (versus a few times in a week). ...wild card subdomain support, you don't need a new cert if you roll out a new host on newhost.domain.com . Tech support tickets.
The conveniences and stability a paid SSL solution provides are likely more attractive to onion.io than saving $150. What is time worth? You have more of it if you are not dicking around with a certificate with more points of failure-- I know that. And I say that as a fan and supporter of Let's Encrypt. They are doing great things over there and have no reservations against someone using a Let's Encrypt cert-- when it makes sense to.
I've made some wiring improvements and added plots. I've also gone back and forth on having the python script continuously run and waiting with sleep() statements vs exit and run again via cron. I've settled on cron and have written more data to file.
I have been trying to get a drop down on the web page to set the setpoint temperature (update keezerparams.txt) but have not had any luck.
you'd need some server-side functionality (e.g. with PHP) for interacting via a webpage. For me, I rarely need to change the temperature setpoint so I haven't bothered.
An onion console app on the cloud would be nice, but I haven't learned how to do that yet. Maybe Blynk?