New software version

This stuff is out of my wheelhouse, but could this be an Android thing or is it on both platforms?
Very good question. Since Weber releases their updates for iOS and Android at different times I am never quite sure which is newer or even if they are ever the same. I will finish the run today, like yesterday, solely on Android, and the switch to the iPad version for the next couple of cooks.
 
After that 17 hour run, I shut it down for about two hours. Then I was told to go smoke some nuts for snacks. I fired the SF back up for another 5 hours (nuts and apple crisp). It worked fine. Not a whimper. I have no idea why it goes south when it does.
 
After that 17 hour run, I shut it down for about two hours. Then I was told to go smoke some nuts for snacks. I fired the SF back up for another 5 hours (nuts and apple crisp). It worked fine. Not a whimper. I have no idea why it goes south when it does.
It’s a puzzlement : Several people on other sites have reported similar issues, all related to the set-point disappearing, followed by cool down and flame-out.

I am now starting to wonder, given what I witnessed standing by my unit yesterday getting ready to spritz — sudden white blank screen, 5 seconds totally dark and blank, re-powered like normal start-up with Connect logo showing, then grill temp and 2 other probes showing accurately, but no set-point, manually set to where it had been and continued to smoke fine — I am wondering if Weber did release some type of patch????

BTW, no power flicker, and I was not touching the unit...but then it is almost 🎃
 
This is a quote from someone on another SmokeFire site. Not sure if it helps:

“Dave Smith Same thing has happened to me a bunch of times. So far I have not had the grill actually cool down - even after a few hours sitting like that. Another reason why I almost never cook without my Inkbird thermometer in there as well.

It seems like the set point is still in there somewhere, just whatever part of the software deals with the display and controls doesn't know about it.”
 
Hummm, that sounds a little different. When mine loses the display, the temp starts dropping. There are so many variables to chase. I understand Weber's problem.
 
Hummm, that sounds a little different. When mine loses the display, the temp starts dropping. There are so many variables to chase. I understand Weber's problem.
However, the controller dropping the set-point display sound like a simple software glitch that results in a re-set and reboot.
 
Mine has started losing set point constantly. My last two cooks were only 1 and 2 hours long and I lost set point in both, and twice in the two hour cook. I also had a timer going in one and it was removed when the set point was lost. Most of the time I’ve had this happen the grill stays at the previous set temp, though I have been monitoring more regularly to make sure set temp back since I did have a time where it also stopped feeding pellets and grill went out completely before I caught it. No low temp warning. Right now I can’t trust my grill to do any longer cooks unless I’m able to constantly monitor it. I guess I need to call Weber as I submitted a ticket a couple weeks ago and haven’t heard back. Maybe was lost in the intertubes.
 
What exactly does this mean losing set point? Are we assuming this is due to the latest update?
Thanks
If you look at post #84 in this thread, there are photos of both the controller and the app. Something happens and the app/controller loses the temp set point. On both units, the set point is replaced by dashes. Since there is no longer a set point, the controller does not know what to do - feed pellets, increase fan speed, etc. So it just sets there. And the temp slowly drops. If you catch it soon enough and reenter a temp, it may correct and continue the run. Or temp drops too low and you enter a temp which causes a pellet dump and a flare.
 
Mine has started losing set point constantly. My last two cooks were only 1 and 2 hours long and I lost set point in both, and twice in the two hour cook. I also had a timer going in one and it was removed when the set point was lost. Most of the time I’ve had this happen the grill stays at the previous set temp, though I have been monitoring more regularly to make sure set temp back since I did have a time where it also stopped feeding pellets and grill went out completely before I caught it. No low temp warning. Right now I can’t trust my grill to do any longer cooks unless I’m able to constantly monitor it. I guess I need to call Weber as I submitted a ticket a couple weeks ago and haven’t heard back. Maybe was lost in the intertubes.
In the meantime, if you are not doing so already, use a separate grill temperate probe to keep an eye on it remotely via your connect app.
 
In the meantime, if you are not doing so already, use a separate grill temperate probe to keep an eye on it remotely via your connect app.
The reason that Dassman5 is suggesting this is that at times I have seen a 70 degree difference between the air probe and the controller, which is driven by the PID to show temps relative to the programing. Others have also seen this.
 
C9B6D5D1-E09B-476A-90B0-DFFD044C814A.jpeg

Running it to 600 after a thorough cleaning, looked up and noticed this.
weber better get this worked out.
what would it have done if I didn’t reset the temp?
 
View attachment 2319
Running it to 600 after a thorough cleaning, looked up and noticed this.
weber better get this worked out.
what would it have done if I didn’t reset the temp?
Same thing happened to me in the middle of making pork belly a week or so ago. But it has worked fine since.
 
What would it have done if I didn’t reset the temp?
The temp would have kept dropping until you got either a low temp warning or an out of pellets warning. In either case, you would end up in the shut down mode. If you catch it late and reset the temp, you may get a pellet dump and a flare. I have been getting this starting with the recent updates and Weber is very aware of this situation. At this time, they have no suggestions.

And as Dassman5 said, the damn thing works fine for 20 plus hours and then crashes 3 times in two hours and then runs fine again. Currently, no correlation with anything.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Back
Top