I have had my 640 for about 6 weeks now. I have probably cooked on it 7 or 8 times. It has been hit or miss with the fireboard schedule. Maybe half the time I start the schedule, everything is fine than maybe an hour later I look and the schedule isn't running. I have even restarted the schedule only to find it stopped running again at some point.
Any ideas or others that have experienced this?
BTW, I have contacted Fireboard but they had little to say other than a loss of wifi signal may be the issue. I have a strong signal to the 640 and haven't experienced any issues connecting to it.
Just looking to see if someone has had this and found a solution. At this point I can't trust using the schedules.
Whoops, guess I'm on my own with this issue. Setting the temp manually isn't a problem, was just fun creating and using the schedule
scooter wrote:I have had my 640 for about 6 weeks now. I have probably cooked on it 7 or 8 times. It has been hit or miss with the fireboard schedule. Maybe half the time I start the schedule, everything is fine than maybe an hour later I look and the schedule isn't running. I have even restarted the schedule only to find it stopped running again at some point.
Any ideas or others that have experienced this?
BTW, I have contacted Fireboard but they had little to say other than a loss of wifi signal may be the issue. I have a strong signal to the 640 and haven't experienced any issues connecting to it.
Just looking to see if someone has had this and found a solution. At this point I can't trust using the schedules.
I've experienced the same issue - most recently - yesterday. Any chance you could share your versionImage and yfbVersion information?
Thanks. I have been back and forth with fireboard ever since. I will forward this to them.
kc0czi wrote:I've experienced the same issue - most recently - yesterday. Any chance you could share your versionImage and yfbVersion information?
Well I have FW ver 1.0.21. I did a cook this weekend and once again the schedule stopped. So, the update didnt fix the problem. I think it now happens every time I cook.
scooter wrote:Well I have FW ver 1.0.21. I did a cook this weekend and once again the schedule stopped. So, the update didnt fix the problem. I think it now happens every time I cook.
I *MAY* have stumbled upon a potential resolution:
In the fireboard app dashboard, top left there is a choice of two 'views'
- Show All
- Show Active
It has been my experience today:
- If the dashboard is only showing the active probes, then the drive program continues to run.
- If the dashboard is showing ALL probes (and one is inactive), then the drive program fails.
Anyone else able to give this a try? I've also provided this feedback to Fireboard.
kc0czi wrote:I *MAY* have stumbled upon a potential resolution:
In the fireboard app dashboard, top left there is a choice of two 'views'
- Show All
- Show Active
It has been my experience today:
- If the dashboard is only showing the active probes, then the drive program continues to run.
- If the dashboard is showing ALL probes (and one is inactive), then the drive program fails.
Anyone else able to give this a try? I've also provided this feedback to Fireboard.
There's a difference in iOS and Android.
Since 'Meat 2' is displayed, you're currently in 'show all' mode (showing all probes). In my experience that's the mode that will shutdown a program because a probe is not sending data (even though it's not part of the program).
Perhaps in the three-dots menu you could choose a 'show active' mode.
I've sent my findings to Fireboard, to be honest, they didn't seem very concerned, nor interested.
scooter wrote:Fyi, I don't see that setting.
kc0czi wrote:I *MAY* have stumbled upon a potential resolution:
In the fireboard app dashboard, top left there is a choice of two 'views'
- Show All
- Show Active
It has been my experience today:
- If the dashboard is only showing the active probes, then the drive program continues to run.
- If the dashboard is showing ALL probes (and one is inactive), then the drive program fails.
Anyone else able to give this a try? I've also provided this feedback to Fireboard.
Fireboard support updated my firmware to .23 about a week ago. Since than I have had 3 cooks and the schedule has worked each time.