I’m not actually too worried about the security side with IoTaWatt. Large scale appliance makers that just are tacking in shiny features that involve the internet tend to not think about security, and rarely will spend any time, money or effort supporting the products that are already out there when they could be investing in new products for people to buy instead, but open source projects like IoTaWatt:
- have reviewable code so security flaws are often quickly found and disclosed by the open source community, and are also auditable for the same reason
- tend to be on a scale that word of mouth matters, so inherent shortcomings have a bigger reputation impact
- often have more tech savvy users who engage with the project to help improve it for long periods of time, avoiding stagnation (at least once they get a bit of following)
So I have a lot more trust in the quality of your code than most of my other internet connected gadgets
Your frequent, positive presence supporting users in this forum only increases that.
The only reason I’m putting the IoTaWatt on that network is so that if I sell up in the next few years, which is getting more likely, it will not need complete (or partial) configuration by the next owners to continue delivering on its purpose, and I’d rather it not go to waste just because it isn’t of particular interest to them. This really is one of those things that a lot of people wouldn’t see much value in as a theoretical, but if it’s already generating the data then it quickly becomes apparent how valuable it is, so I feel leaving a low barrier for entry just makes it more likely it will be used if that eventuates.
The nginx idea does sound like something I could rig in through, I’ll look a bit at that and see what I can do. If I can make it zero maintenance, so it won’t stop working if I’m gone, then it’s totally in
Speaking of your positive support
And I’m not even an actual customer yet!
Thanks a tonne for your time!