Thanks much. Really appreciate it.Originally posted by A. Vale:
Amir, do you have a second blower to test with? If not, I can send you mine while you figure this out. Send me an email at elav@sbcglobal.net if you need it (it is the least I can do with all you have provided us).
Seems like a great suggestion. Will put on TODO list....Originally posted by Ken Brown:
Amir,
How about sending out an email alert if all communications to the stoker are lost.
Ken
These are posts that I love. Suggestions which take 5 minutes to implement and would be so usefulOriginally posted by Kenny Davis:
The coolest thing about the update is the temperture panel. I like that with a quick glance i tell how the smoker is doing. Especially from across the room!
On my wish list for the temp panel
a blower indicator
and an always on top would be cool.
Awesome program thanks Amir.
Kenny Davis
Originally posted by Amir:
I also added the logic to add a port number of the IP address for HTTP.
I would think that maybe starting all names for a particular pit with a common designation like [1]Pit ,[1]brisket,[1]butt ,[2]pit, [2]butt might be simpler to code and clearer for the user.Here is a thought I have. And that is, come up wiht a naming convention that automatically tells the program the probes go with pit-1 or pit-2. Thinking of a character at the end of the probe name. Say an "'" mark or something like that. Using this, the program would always detect which probe goes with which cook without you having to tell it. What say you? Would that work?
I am pretty sure it cannot be changed on the stoker. But I assumed the application was some proxy router which did port remapping. Anyway, it was one line of code so if it is of no use, no harm doneOriginally posted by Ken Brown:
I suppose that would assume that the port number of the stoker itself could be changed.
I am too lazy to parse complicated syntax for thisI would think that maybe starting all names for a particular pit with a common designation like [1]Pit ,[1]brisket,[1]butt ,[2]pit, [2]butt might be simpler to code and clearer for the user.
I use telnet just for reading so there is nothing there. And I see no indication in web interface either. I will try to contact the developer to find out any secret codesOriginally posted by Todd D.:
Amir,
Is there an option via the telnet interface to display/change the probe calibration numbers? Can you query the firmware version? Just wondering if some things like this might be nice in a utility menu within your program?