Stew Ellis
TVWBB Member
After a lot of searching and reading on this website I decided that the Stoker would be the most open platform within my limits of software and hardware knowledge. So I ordered a Stoker with 1 pit and 3 food probes, 5cfm fan, handle, and WSM adapter on Thursday. Called Friday and they said they have all parts in stock and it should ship Monday. Trying to get my ducks lined up before it gets here.
The goal is to be able to control, monitor and graph cook sessions in as open as possible a way, meaning it has to be able to be done with a standard browser (not IE or Safari) and/or software tools that are open-source and free that can run on Linux, OSX, BSD and even Windows. Amir helpfully pointed me to webapp discussions earlier in the Winter, and Curt Timmerman pointed to his BBQ Monitor website, http://curttimmerman.net/logger/bbqmonitor.html , which I had visited before, but I had missed the buttons across the bottom which included the source to all the modules for that service.
I have now read all those docs and code, and have a sense of how it works, although I have not ctag'ed the perl and stepped through it in emacs yet. As Curt states, it does not have any fan code since he is using it on an electric smoker. It also does not do any control functions, but that is something that can be done with just the browser and the builtin http server on the Stoker. I hope it will not be beyond my abilities to add a stunt to the cgi and to the javascript? code to store and graph fan condition (off, on, % ?). Although I only live in MI, not AK, we do get kind of cold here and I would like to be able to store and chart ambient temp as well.
The only problem I see is that you it looks like you have to be running a web server to be able to record and chart the Stoker. The logging part of bbqmonitor is a perl cgi script. Of course, the iphone is going to have to access the charts on a server somewhere since I cannot write my own iphone apps. How much data does the Stoker keep? Does it keep whole cooks? Can you step back and forth in the Stoker's own web interface?
I will definitely be using bbqmonitor for home cooks, but I am a little concerned about exposing my home network to the internet. Right now all I am letting through from o/side is ssh. Haven't had to worry about web security since my university hired a full time person to run the website and server about 12 years ago. I am less concerned about security for the Stoker since they now have the ability to lock the controls. I guess I am going to have to think about ssh tunnelling of http, which I think I used to do a long time ago.
Of course all this is affected somewhat by how I tie the Stoker to my home network. Right now I have found an ancient D-link bridge/AP in my basement, but I have not fired it up yet.
Is there anyway to load barebones session graphing to the Stoker's web server?
There is also the possibility of accessing the Stoker data with telnet or ftp and parsing it into a form that can be plotted by gnuplot.
Then RJ Riememsnider drew my attention to RRD for graphing and MRTG for gathering SNMP statistics. I have loaded all the rrd and mrtg packages available to Ubuntu Karmic and will be looking through them in the next few days.
If anyone else has any ideas or code to share, please post it here.
The goal is to be able to control, monitor and graph cook sessions in as open as possible a way, meaning it has to be able to be done with a standard browser (not IE or Safari) and/or software tools that are open-source and free that can run on Linux, OSX, BSD and even Windows. Amir helpfully pointed me to webapp discussions earlier in the Winter, and Curt Timmerman pointed to his BBQ Monitor website, http://curttimmerman.net/logger/bbqmonitor.html , which I had visited before, but I had missed the buttons across the bottom which included the source to all the modules for that service.
I have now read all those docs and code, and have a sense of how it works, although I have not ctag'ed the perl and stepped through it in emacs yet. As Curt states, it does not have any fan code since he is using it on an electric smoker. It also does not do any control functions, but that is something that can be done with just the browser and the builtin http server on the Stoker. I hope it will not be beyond my abilities to add a stunt to the cgi and to the javascript? code to store and graph fan condition (off, on, % ?). Although I only live in MI, not AK, we do get kind of cold here and I would like to be able to store and chart ambient temp as well.
The only problem I see is that you it looks like you have to be running a web server to be able to record and chart the Stoker. The logging part of bbqmonitor is a perl cgi script. Of course, the iphone is going to have to access the charts on a server somewhere since I cannot write my own iphone apps. How much data does the Stoker keep? Does it keep whole cooks? Can you step back and forth in the Stoker's own web interface?
I will definitely be using bbqmonitor for home cooks, but I am a little concerned about exposing my home network to the internet. Right now all I am letting through from o/side is ssh. Haven't had to worry about web security since my university hired a full time person to run the website and server about 12 years ago. I am less concerned about security for the Stoker since they now have the ability to lock the controls. I guess I am going to have to think about ssh tunnelling of http, which I think I used to do a long time ago.
Of course all this is affected somewhat by how I tie the Stoker to my home network. Right now I have found an ancient D-link bridge/AP in my basement, but I have not fired it up yet.
Is there anyway to load barebones session graphing to the Stoker's web server?
There is also the possibility of accessing the Stoker data with telnet or ftp and parsing it into a form that can be plotted by gnuplot.
Then RJ Riememsnider drew my attention to RRD for graphing and MRTG for gathering SNMP statistics. I have loaded all the rrd and mrtg packages available to Ubuntu Karmic and will be looking through them in the next few days.
If anyone else has any ideas or code to share, please post it here.