Ron Van Iwaarden
New member
Ok, I know I am new here and, in fact, my first heatermeter won't be here until next week but I have a feature request for heatermeter already.
About two weeks ago, my buddy posted a link on facebook to his smoker temperature control, a flameboss. I thought this was the coolest thing in the world, having struggled with temperature control on my WSM so I started researching smoker temperature controllers. The flame boss was pricy at $350 if you wanted the internet feature and I eventually found the heatermeter which I thought was far cooler and more fun because of the openness of the project.
The internet capabilities to show a cook over the internet are wonderful while the heatermeter is on but, once it is off, the graphs go away as compared to flame boss where data are stored on some public server somewhere. I know heatermeter already phones home to a public server so you can find the IP address of your heatermeter at http://heatermeter.com/devices/. It would be cool to have this feature extended to also publish and archive the stats of a cook. It would be nice for those who are unable to punch holes through their firewall to display live data as well.
The code to do this is probably relatively simple but the more significant issue I would imagine would be the data load for someone's server and maintaining that server.
Another option would be to create a server that users could install on one of their own machines that does not get turned on and off like the heatermeter does and each user could store their own data. This would require the heatermeter to have a configuration page to tell it where to send the data as the cook runs.
Anyway, just a nice to have feature that would build on the awesomeness that has already been developed.
--Ron
About two weeks ago, my buddy posted a link on facebook to his smoker temperature control, a flameboss. I thought this was the coolest thing in the world, having struggled with temperature control on my WSM so I started researching smoker temperature controllers. The flame boss was pricy at $350 if you wanted the internet feature and I eventually found the heatermeter which I thought was far cooler and more fun because of the openness of the project.
The internet capabilities to show a cook over the internet are wonderful while the heatermeter is on but, once it is off, the graphs go away as compared to flame boss where data are stored on some public server somewhere. I know heatermeter already phones home to a public server so you can find the IP address of your heatermeter at http://heatermeter.com/devices/. It would be cool to have this feature extended to also publish and archive the stats of a cook. It would be nice for those who are unable to punch holes through their firewall to display live data as well.
The code to do this is probably relatively simple but the more significant issue I would imagine would be the data load for someone's server and maintaining that server.
Another option would be to create a server that users could install on one of their own machines that does not get turned on and off like the heatermeter does and each user could store their own data. This would require the heatermeter to have a configuration page to tell it where to send the data as the cook runs.
Anyway, just a nice to have feature that would build on the awesomeness that has already been developed.
--Ron