New software version

[Dassman5]

Thanks guys, I hope they get this all figured out.

I was actually standing by the grill getting ready to baste the food when it did that: ...screen went blank—> powered off —> powered back up by itself with logo -> all fine with probes, but no set-point —> manually re-entered the set-point, picked up and ran fine thereafter.
One of the reasons I have large USDA Prime packer brisket now frozen instead of on our dinner plates...can’t trust it alone overnight.

 

[Bruno]

I was actually standing by the grill getting ready to baste the food when it did that: ...screen went blank—> powered off —> powered back up by itself with logo -> all fine with probes, but no set-point —> manually re-entered the set-point, picked up and ran fine thereafter.
One of the reasons I have large USDA Prime packer brisket now frozen instead of on our dinner plates...can’t trust it alone overnight.

This is exactly my concern, at this point it’s a grill only if it can’t be trusted.

 

[AHoneyman]

I was actually standing by the grill getting ready to baste the food when it did that: ...screen went blank—> powered off —> powered back up by itself with logo -> all fine with probes, but no set-point —> manually re-entered the set-point, picked up and ran fine thereafter.
One of the reasons I have large USDA Prime packer brisket now frozen instead of on our dinner plates...can’t trust it alone overnight.

I have not seen this. That does not mean that it did not happened to mine. Just that I did not see it in real time. May be different causes or the same. No data at this time.

 

[abmet]

I was actually standing by the grill getting ready to baste the food when it did that: ...screen went blank—> powered off —> powered back up by itself with logo -> all fine with probes, but no set-point —> manually re-entered the set-point, picked up and ran fine thereafter.
One of the reasons I have large USDA Prime packer brisket now frozen instead of on our dinner plates...can’t trust it alone overnight.

I’m wondering if that’s not what causes it every time. Seems like software crashing and rebooting. Loses setpoint and timers for me. Only doing short cooks until this gets resolved. I wish I could go back to previous software version It was rock solid.

 

[AHoneyman]

Seems like software crashing and rebooting.

In my case, the software has never crashed and rebooted to my knowledge and I have been watching it like a hawk since I was inflicted with the firmware version 4042 a couple of weeks before everyone else as a tester (without my knowledge). I have found no correlation to anything. Temp set point just disappears. And I am doing a run this afternoon.

 

[AHoneyman]

And then it ran like a champ today for over 6 hours. Absolutely great performance.

But I have asked about residue in the firebox after all of the updates. I can not remember if it was in this thread or not. I have been getting a pile of junk in the firebox after shutdown. I have switched pellets and I still get this buildup. The photo shows what I got after cleaning the grill and then doing a straight 20 plus hour run and a shutdown without a burn off. I can see where this might cause startup problems. Just a little touch with a plastic putty knife and it falls apart.

 

[abmet]

I did some wings and lost setpoint again in first 15 minutes. I wasn’t out there to see if rebooted. Was still running at 350 when I set it back. I decided to factory reset my controller and reinstall lastest updates after I finished. Doing small turkey breast tomorrow I think so will see if helped or not.

 

[abmet]

Factory reset didn’t fix it. After getting up to 225, I put a turkey breast on at 12:40 along with a probe target for 150 degrees and when I went to check at 12:50 setpoint was dashes and probe target was gone. Sure feels like it crashed and rebooted to me but wasn’t in front of it to witness it. This software, firmware, or combination sucks.

 

[Dassman5]

Factory reset didn’t fix it. After getting up to 225, I put a turkey breast on at 12:40 along with a probe target for 150 degrees and when I went to check at 12:50 setpoint was dashes and probe target was gone. Sure feels like it crashed and rebooted to me but wasn’t in front of it to witness it. This software, firmware, or combination sucks.

My advice, if you have a few minutes, is to file a support complaint with Weber. The more the Merrier, but at some point they need to move this a seriously elevated status....something in their software routine,or more like the PID firmware, is not right.

 

[abmet]

My advice, if you have a few minutes, is to file a support complaint with Weber. The more the Merrier, but at some point they need to move this a seriously elevated status....something in their software routine,or more like the PID firmware, is not right.

I did a couple of weeks ago and just did again today after confirming that factory reset didn’t fix it. Let them know that felt like had finally turned the corner on issues until this version and it either needs to be fixed immediately or let us roll back to the previous version that was actually usable.

 

[tickko]

I'm new to the SF world but I experienced the same issue with the controller (firmware # 2350) rebooting and then losing my set temp and probe settings. After some testing, I found that disconnecting the controller from WiFi stopped the issue from happening.

I contacted Weber CS, after going through some things they told me they would get back to me. Then a day later (Nov 6) I received an email from CS saying to update my controller to 2491.

On 2491, the controller rebooting seemed to stop but I am now getting flare outs / low temp warnings (happen twice in 30 minutes). I removed the WiFi connection from the controller again and the flare out's stopped and the grill ran fine for 2 hours using only the Bluetooth connection.

I emailed back CS and the response I got was that "it might be WiFI signal losing the connection". I suspect that the flare outs are associated to the same WiFi bug that was rebooting the controller in 2350.

I haven't had a chance to test further but my question is, what are others running for WiFi?

I am using Google's mesh WiFi, signal strength is strong. Are there any known issues with using a WiFi connection that is a combined SSID?

 

[JpsBBQ]

I use a mesh system also. I’ve been fortunate to not have had any issues that I ca remember for months now. The last update seemed to really speed up start time and shutdown time as well as the change of temperature.

Stick with it. Once you get the system ironed out you’ll be really please I think.

 

[AHoneyman]

I do not think that it is wifi bug. I would guess that it is trying to update (successfully or unsuccessfully) something in the background. When you are disconnecting, it is simply stopped the update and you can keep cooking. I would update everything and then do a couple of startup and shutdown cycles just to get its mind straight. And make sure that you shut down properly (let the SF complete its cycle and shut off via the switch).

 

[Dassman5]

I'm new to the SF world but I experienced the same issue with the controller (firmware # 2350) rebooting and then losing my set temp and probe settings. After some testing, I found that disconnecting the controller from WiFi stopped the issue from happening.

I contacted Weber CS, after going through some things they told me they would get back to me. Then a day later (Nov 6) I received an email from CS saying to update my controller to 2491.

On 2491, the controller rebooting seemed to stop but I am now getting flare outs / low temp warnings (happen twice in 30 minutes). I removed the WiFi connection from the controller again and the flare out's stopped and the grill ran fine for 2 hours using only the Bluetooth connection.

I emailed back CS and the response I got was that "it might be WiFI signal losing the connection". I suspect that the flare outs are associated to the same WiFi bug that was rebooting the controller in 2350.

I haven't had a chance to test further but my question is, what are others running for WiFi?

I am using Google's mesh WiFi, signal strength is strong. Are there any known issues with using a WiFi connection that is a combined SSID?

I have experienced several loss of WiFi connections from my phone (Android) to the SF. In fact, even after pairing with Bluetooth I was unable to upload the 2491 software. However, when I switched to my iPad, it connected immediately via Bluetooth and loaded the 11/5 rising of the 2491 software to the unit very quickly.

I am running standard dual band WiFi system in my house with 2 range extenders at either end of the house, one of which is to handle communications with my grill and pool. I get a strong signal as far away from the house as 100’ without trouble, far beyond the distance to the SF.

My most recent experience has to with setting the food probe setpoint. After an initial setting of 160, I cancelled the food probe set point and reentered it for 195 (large packer brisket). It transmitted the new setting to the SF, but still showed the old temp of 160 on my iPad. Tried to dismiss and reset several times, but stayed at the original setting on my iPad and the new setting on the SF. The interesting part, however, is that it did notify me via my phone when it reached 195F.

Others, on different websites, are reporting similar experiences but some have reloaded the software and it fixed the problem. I will be doing the same later today, as I believe it may be due to an incomplete software upload.

 

[abmet]

So far the new 2491 software has been good for me. Not one setpoint loss and no low temp drops. I haven’t seen any WiFi issues so far either. I’m running a Eero mesh system and using iPhone 12 pro. Might be good idea to reset the contoller to factory and let it reinstall then new software.