New controller software and app update

[rwhapham]

So many people having completely different results when starting their SF's up in cold weather. I started mine yesterday for it's first run (seasoning) with 28 degrees ambient temp in the driveway. I set the target temp to 460 and started it up with the lid open. Waiting for my first whiff of burning hickory, the controller was showing the target temp and two dashes indicating (I'm speculating) that the pit temp was below it's range of display. Smelling some hickory burning.I closed the lid and waited.

As the pit temp came up the display on the controller eventually showed 40 degrees and slowly started to climb. As I wrote yesterday, the grill responded without a problem to many temperature changes both up, down and then back up before shutdown a couple of hours later. I did not test Smoke Boost.

Seems like a lot of people are having completely different successes and failures with the same version software.

That fact tends to make me a bit uneasy. Knock on wood, I haven't had an issue with any of my cooks; though I've only had it since mid-November. And I get that this thing isn't like an oven where 350F means 350F each and every time. But when people on this forum who have not had problems suddenly start developing them, it adds a little anxiety to the start of every cook. You'd think with all the smarts that has to be built into the SF to make it work, Weber would have created an opt-in to chart cook data and have it sent as diagnostic info to them in the event of a failure. Clearly, the data is available, just seems to be a matter of collecting and sending it. As a software guy myself, data like that would be invaluable.

 

[abmet]

I’ve noticed that the display of colder ambient temps seems to change with software updates. Sometimes when below freezing is blank. Yesterday it was around 23 when I started my EX4 and the grill/ambient temp showed 40 and when I plugged in one temp probe it showed 28. I also no longer get notifications (iPhone) with the last update unless I open the app. I know it’s running in the background as the battery setttings show it was using battery all day listed as running in the background. Seems like hit or miss with the software updates lately. One will be rock solid then next will introduce some new issues. I know there is lot of codIng involved and will always be bugs, but hopefully can avoid ones that cause major issues.

 

[AHoneyman]

That fact tends to make me a bit uneasy. Knock on wood, I haven't had an issue with any of my cooks; though I've only had it since mid-November. And I get that this thing isn't like an oven where 350F means 350F each and every time. But when people on this forum who have not had problems suddenly start developing them, it adds a little anxiety to the start of every cook. You'd think with all the smarts that has to be built into the SF to make it work, Weber would have created an opt-in to chart cook data and have it sent as diagnostic info to them in the event of a failure. Clearly, the data is available, just seems to be a matter of collecting and sending it. As a software guy myself, data like that would be invaluable.

There is a Google analytics collection opt-in feature within the Weber Connect app. What it sends/collects, I do not know. Where it goes, I also do not know.

 

[AHoneyman]

Yesterday it was around 23 when I started my EX4 and the grill/ambient temp showed 40 and when I plugged in one temp probe it showed 28. I also no longer get notifications (iPhone) with the last update unless I open the app.

This is the real big problem that I see right now. When you have warnings for the SF that are not reaching you, what good are the warnings or the app? I got a pellet grill because I did not want to spend XX hours watching a fire overnight to get a brisket cooked. Yes, I can get up and check the grill a couple of times but I have friends that stay up days tied to the grill/fire to get the temp right. I am not going to do that. Without the notifications working, I am right back in that setting.

We are currently seeing variability across the board from people that never had problems before. That tells me that there are variables that Weber has not considered yet. The only thing that I have concluded is that I must run an air probe all of the time to really have an idea about what the SF is doing. And when it works, it works good; when it doesn't, we are guessing why.

 

[rwhapham]

There is a Google analytics collection opt-in feature within the Weber Connect app. What it sends/collects, I do not know. Where it goes, I also do not know.

Typically, Google analytics in an app is to report anonymous data back to the developer about how the app is being used. Though there may be other uses for it; not an expert in that area. I just know that if I were on the team at Weber trying to fix issues and was given the choice between "we have dozens of reports of flameouts" vs. "we have dozens of reports of flameouts and here is PID data history since the grill was started", I know which one I'd pick.

 

[AHoneyman]

I think that the transition from charcoal to wifi/bluetooth/etc. has been really eye opening at Weber.

 

[abmet]

Forgot to mention I sent the notification issues I’m having to Weber support.

 

[rwhapham]

I think that the transition from charcoal to wifi/bluetooth/etc. has been really eye opening at Weber.

I definitely agree with that statement. That's often not surprising when a company that has been historically "low tech", so to speak, suddenly finds themselves having to worry about writing apps and firmware and dealing with a 3rd party OS and controller boards and tech support. Given that they bought the iGrill line and didn't grow it in-house (which is why there is such a lack of feature parity between the iGrill app and the Weber Connect app), this is relatively uncharted territory for Weber. I have faith, though, that it can all be ironed out. Just takes time.

 

[rexster314]

Had about 6 pounds of various sausages to smoke yesterday. Since the purchase the first week of December, I've not had one problem with the SF, including high/low cooks and extensive use of Smokeboost; Starting cooks out in Smokeboost for several hours then increasing the cooking temperature, Cooking, then dropping into Smokeboost, then increasing cook temps without a hitch.
Yesterday was the downfall. Outside temps hovered around 38F all day. I started the SF off in Smokeboost as normal. After about 30 minutes or so, I received the flameout message. Waited for cooldown, vacuumed out the firepot, and surrounding area. Restarted Smokeboost, watched as pellets dribbled down, then put the sausages back on the grates. Same thing happend 30 mins later. Flameout. Same procedure of cleanout. This time I started with a set temp of 300F. Temp shot up as normal and I was setting at 300. Then I dropped it into Smokeboost. This time I had my Fireboard with an ambient probe in the cooker. Temps subsided to around 140 and stayed there for 3 hours in Smokeboost. I then kicked the temps up to 240 to finish the sausages off. The cook finished off in about 45 minutes perfectly. I then shutdown the cooker as normal.
Moral of the story, different procedures for Smokeboost in outside temps of less than 40F

 

[AHoneyman]

From all SB reports that I have heard (includes before the latest updates), it is best to start the SF at 200 degrees, let it stabilize, and then switch to SB. The PID likes things better that way.

But the latest update did change something about SB at lower temps. It may have changed the lower limit of the temp setting. But I would have thought that some of us up north would have noticed the 40 degree bottom on the controller before now (unless it changed).

 

[Dassman5]

This is the real big problem that I see right now. When you have warnings for the SF that are not reaching you, what good are the warnings or the app? I got a pellet grill because I did not want to spend XX hours watching a fire overnight to get a brisket cooked. Yes, I can get up and check the grill a couple of times but I have friends that stay up days tied to the grill/fire to get the temp right. I am not going to do that. Without the notifications working, I am right back in that setting.

We are currently seeing variability across the board from people that never had problems before. That tells me that there are variables that Weber has not considered yet. The only thing that I have concluded is that I must run an air probe all of the time to really have an idea about what the SF is doing. And when it works, it works good; when it doesn't, we are guessing why.

I have been running a 2nd ambient air probe (Weber on sale for $15) since the second week of ownership. It has become my go-to way of monitoring the SF, and on long overnight runs I connect another probe using my Maverick system with over and under set points to send an alarm if it deviates from what I consider to be an acceptable range.

 

[ftank47]

I have been running a 2nd ambient air probe (Weber on sale for $15) since the second week of ownership. It has become my go-to way of monitoring the SF, and on long overnight runs I connect another probe using my Maverick system with over and under set points to send an alarm if it deviates from what I consider to be an acceptable range.

Been doing the same thing. Very interesting how hot and cold spots come up on either side on my grill at different temps. In the 400 range I see differences of 100+ degrees left side to right side. I keep telling myself that if I did this to my oven or other gas grill I would see the same thing. So far sub 300 temps have held fairly well.

 

[MrPhilGrillTX]

From all SB reports that I have heard (includes before the latest updates), it is best to start the SF at 200 degrees, let it stabilize, and then switch to SB. The PID likes things better that way.

But the latest update did change something about SB at lower temps. It may have changed the lower limit of the temp setting. But I would have thought that some of us up north would have noticed the 40 degree bottom on the controller before now (unless it changed).

This strategy worked for me today - let it get to 225 or so, and then engage SB. Plus it was in the sun, unlike my experience on Sunday, when it was cold and cloudy. (The pork shoulder is at 156 or so. Hope it is as good as the loin on Sunday).

If they contracted out the controller and connect app software, they need to get people who like to grill/smoke/etc - that will help the software be better. I know I make more usable code when I use the program I'm writing. "Oh that's annoying, let me fix it". Maybe send the QA team an EX to use to feed the team lunch. (and now I'm engaging in the internet's third favorite pastime: speculating about things I have no direct knowledge of.)

 

[rwhapham]

The more I use my SF, and the more I read about it and pellet grills in general, the more I'm actually impressed that Weber (and other manufacturers) have managed to accomplish what they have. Sure consumers will always want more (myself included); and thankfully a lot of the SF wants I've come across fall under improvements to the Weber Connect app and not necessarily the grill itself. But for those of us who have used "old school" charcoal or wood smokers, we all know that maintaining temperature is simple in nature, but complex in practice. It's a wood fire, after all. Not an electric heating element or a propane burner. All fire needs is fuel and airflow, but any of a dozen (understatement) variables can throw that off: ambient temp, wind, pellet irregularities, ash buildup, grease buildup, airflow in the firepot, and so on. I'm not having to babysit that fire anymore, so call me happy.

 

[MrPhilGrillTX]

I’m feeling a certain amount of this person doesn’t get it. The app would be so much better with OS notifications.
Any third party apps out there?