Timberline XL Issues:

[DKrics]

Hi All,
Check out my heat-up issues with my new Timerberline XL below. This data was collected from Traeger's own Wi-fi data using Home Assistant and a custom plug in.
I set the temp to 450 and it took over 30 mins to hit 350. It took 40 mins (total) to hit 450.
Notice the slope of the heat up. It went from nothing registered to Boom! I don't know if this is true vs heat just not registering at the thermometer.
Notice the slope from start up to 180 is steep, but it slows down from 180 to 300. The heat up from 300 to 450 seems more reasonable.
So, I was cooking thin slices of marinated ribeye (like a Korean BBQ). Thus the number of temp drops when the lid was opened.
Notice how later in the cook, the temp really never gets above 200, despite being set at 500 starting at 708.
Look at the hump at the 7:45 mark. The lid is closed. Target temp is 500. But the "curve" is flat. The temp goes down despite the lid being shut! This is an issue.
I think there has to be a software issue in terms of feedback and heatup. I am afraid this D2 drive or whatever it is called may try to be too fancy for its own good, leading to slow and improper heat ups in the Timberline XL.
Sorry for my rant! But now I have additional data to support it.

 

[JPSBBQ]

Its likely just some software glitch they need to resolve in an update. I know these things can be annoying but every manufacture has experienced some sort of similar issues when launch new and innovative products. I have every confidence they will resolve the issue. Hopefully sooner rather than later. Good luck.

 

[Snowdak]

Same problem. New Timberline xl takes 60 minutes to heat to 500. 31 minutes to reach 300. Support says it needs to be properly seasoned….I am ready to return grill.

 

[DKrics]

Yeah. I think that is BS. My understanding is that seasoning is to burn off the toxins from the paint and the factory. How in the world will that help the microchip that controls the auger and the fan properly respond to heat things up in a timely manner?

 

[Pellet.Rookie]

DKrics, from what I gather on this forum and others it seems like it a hit or miss with the temp issues. The timberline xl I have is now getting up to 350 in about 15 min. I recently had to re-season again due to a lid replacement, but the initial seasoning it was around 30 min before it hit 350. I would like to know more on how you were able to collect the temp data? That’s something I’d like to be able to track. I think it’s dumb the Traeger app doesn’t offer the option to track temp data on cooks.

 

[Snowdak]

DKrics, from what I gather on this forum and others it seems like it a hit or miss with the temp issues. The timberline xl I have is now getting up to 350 in about 15 min. I recently had to re-season again due to a lid replacement, but the initial seasoning it was around 30 min before it hit 350. I would like to know more on how you were able to collect the temp data? That’s something I’d like to be able to track. I think it’s dumb the Traeger app doesn’t offer the option to track temp data on cooks.

Was yours initially slow? My first guess was mine was working as designed which would make this grilll a no for me. If some are working and some are not that would seem to mean hardware issue not firmware.

 

[Snowdak]

Any chance pellet type is cause?

 

[Pellet.Rookie]

Was yours initially slow? My first guess was mine was working as designed which would make this grilll a no for me. If some are working and some are not that would seem to mean hardware issue not firmware.

I felt it was slow getting up to temp at first, but (knock on wood) it seems reasonable now. I’ve only had a couple long cooks & cleaned it good before each. Still keeping an eye on it while I’m within the return window. I have to say, it does cook really well.

 

[DKrics]

Any chance pellet type is cause?

I am open to there always being a chance, But I've used new Traeger pellets. I never had a pellet issue with my older Traeger.
I throw a pellet into a glass of water and it sinks, showing density. It snaps when broken.

 

[DKrics]

DKrics, from what I gather on this forum and others it seems like it a hit or miss with the temp issues. The timberline xl I have is now getting up to 350 in about 15 min. I recently had to re-season again due to a lid replacement, but the initial seasoning it was around 30 min before it hit 350. I would like to know more on how you were able to collect the temp data? That’s something I’d like to be able to track. I think it’s dumb the Traeger app doesn’t offer the option to track temp data on cooks.

It is a big rabbit hole to get things tracked. I am using a home automation system called Home Assistant (homeassistant.io). You run in on a raspberry pi. Then you need to add on a custom component from GitHub to get it to track the Traeger cooks.

 

[DJDDay]

Its likely just some software glitch they need to resolve in an update. I know these things can be annoying but every manufacture has experienced some sort of similar issues when launch new and innovative products. I have every confidence they will resolve the issue. Hopefully sooner rather than later.

To be fair, this grill has been out in the wild among first-look beta testers for quite some time (including popular Traeger promoters like Matt at Meat Church). There has been more than ample time to get software glitches out of the way. This is an almost $4000 USD grill - these sort of issues should *NOT* be happening IMHO.

Traeger support suggesting it needs to be seasoned again is a laughable insult. For any of you XL owners out there experiencing slow heat up times and swings like this, I'd absolutely return the grill and get a full refund.

 

[ARCEE]

I am watching the temps myself. I did a hi-speed brisket cook last Sunday (8 hours total from on the grates to wrapped in a foil pan complete for transport). My Hi-Speed brisket protocol is 325 deg till the point hits 160, then inject and double wrap in foil individually. They go back on the racks at 300 till the flat hits 200 deg internal. Pull packs and rest for 30 - 60 minutes. Finally, slit foil and drain juice. Move and place each brisket into a foil pan and cover with foil. Did 6 briskets for a total of 80 pounds +/-.

I used my Signals thermometer from ThermoWorks. It has 4 probe pickups with temperature reading, averaging and graphing on each probe. Since it is wifi connected, I can monitor things with my IPAD and the company app.

I set an air probe on the second rack and 3 meat probes into 3 of the briskets. I then set the two wired XL probes into 2 more Briskets, and "drove" the XL Meater spike into the last brisket. (I am not in love with this meater probe yet)

The XL onboard sensors and the ThermoWorks air probe stayed within 10 degrees of each other most of the way. Only time it really deviated was reporting changes after door closing. I believe the issue during the door recovery may be due to the point placement of my "air" probe vs the reporting sensors on the XL.

I have done this cook many times on my old Timberline 1300 so I have a baseline "normal" for timing and function. I found my new XL did nothing alarming and performed well. Briskets were delicious. The XL grease management performed flawlessly. Grease management was the reason I moved off the Timberline 1300. In high volume cooks I needed to always be aware of the Timberline 1300 management. The XL had 0 issues.

Subjectively, I believe I am getting a better smoke and more smoke across the continuum using the XL. I am still working on a cleanup protocol, but, it is getting there.

Tomorrow, I will be doing another known cook.

I will do between 12 and 14 racks of St. Louis trim pork ribs cooked dry Memphis style.
I generally run these for between 6 and 7 hours at 275 degrees. I do not wrap them.
I use a rub and yellow mustard, then on the fire for 6 hours till I open the lid for the first check.

I do not use meat probes with ribs. I DO monitor the grill temps. For this cook I WANT my 275 to BE 275. I will probably run 2 air probes to cross check the Traeger sensor temps. For ribs it is all about time and temp. I use poke tests, bend tests, and twist tear testing to judge finish.

I am going to be watching for temperature consistency and accuracy, product delivery cook times and final product outcome meeting what I expect for St Louis ribs (acting normally), and grease management.

Who doesn't love ribs.

I will report any XL issues. This will be a good test for air flow and grease management.

 

[BobbyQ]

Personal lesson learned long time ago: Don’t buy year one of anything.
Sorry to hear of your problems with something that should work out of the box for the price you paid.
BTW, I once owned a Chevy Citation.

 

[Sdsmith1989]

I was having many of the same issues with grill getting up to temp and recovering in a reasonable amount of time. Was taking way longer than my timberline 850. However, I have noticed after using the grill almost daily for the last month, this seems to have gotten better. I have done several long cooks at 225 and 250 recently and it was after these cooks that I have noticed that it was much better getting to 375 and even 450 in a reasonable amount of time

 

[JPSBBQ]

To be fair, this grill has been out in the wild among first-look beta testers for quite some time (including popular Traeger promoters like Matt at Meat Church). There has been more than ample time to get software glitches out of the way. This is an almost $4000 USD grill - these sort of issues should *NOT* be happening IMHO.

Traeger support suggesting it needs to be seasoned again is a laughable insult. For any of you XL owners out there experiencing slow heat up times and swings like this, I'd absolutely return the grill and get a full refund.

I'm not saying I disagree, but many manufactures go though this same sorta thing even after substantial beta testing. I've heard stories from many people with different brands that have experienced issues. It's most prevalent when a new technology upgrade has been introduced. Say a controller or expanded options on the controller. It is hard to believe, but it does happen and not just to Traeger. It will get sorted out.

Not sure about the seasoning comment either. Maybe just a bad rep on a bad day or a miscommunication. Hard to say given the info is second or third hand.

I did hear they had an issue or two that was holding up their launch. Maybe they thought it was 100% resolved only to find out it wasn't. Wonder if it's everyone or just some of the units? If only some of them then why only some? Well, here's to hoping for a quick resolution.