Fireboard App Issues

[Nicolaus]

I completed my first cook on my new Big Joe III yesterday.

Near the very end, after exactly 23 hours and 54 minutes of cooking time, my session from the previous day ended without my doing anything, and a new session was “auto created” without my doing anything. The new auto created session captured the last 88 minutes of the cook, thus rendering all of the averaging of probe temperatures and also the graph images less accurate in the previous session.

Does anyone know if and how I could prevent this from happening in future cooks, so as to have all of the data from them in one single session (regardless of how long the cook lasts)? I’d rather not have to jump around to analyze how things went throughout.

[Huskee]

Wow that's a long cook. I suspect it defaults to that since most cooks are less than 24hrs, but alas I do not know so I'll defer to those who do.

[Donw]

Call their support and ask.

[Troutman]

Exactly, call Fireboard. They may have the answer.

[GolfGeezer]

From the Support section of their website:

"Sessions will automatically close after 30 minutes of inactivity (no temperature data). Max session length is 24 hours (emphasis added): a session will automatically roll over into a new session after 24 hours have elapsed."

[Troutman]

Good find Geezer, I did not know that. Of course I don't cook for 24 hours ever so I would have never known that anyway.

[Nicolaus]

From the Support section of their website:

"Sessions will automatically close after 30 minutes of inactivity (no temperature data). Max session length is 24 hours (emphasis added): a session will automatically roll over into a new session after 24 hours have elapsed."

Thank you!

[GolfGeezer]

De nada. They do have one of the better FAQ sections out there. I’ve also found them to be very responsive to emails and calls.