Timberline 1300 firmware

[NunyaBzness]

My Timberline is on firmware v2.00.02, config v07.005. It’s turned on 24x7 on WiFi with a signal level at -27dBm (excellent) for the past 2 weeks, since I put a node on the porch 6 feet from it.

What on earth do I need to do to get this thing to update? There’s nothing I can find in the app (iOS 2.05.b6 since yesterday) or menus to trigger activity.

WiFire support has been spotty (being polite) since the app “upgrade” and all I want to do is get on par with where I was a few months ago. Any suggestions? Grill connectivity and status over my Plume mesh has been great, but the automation previously available is still missing...

 

[dunawayfamily]

My Timberline is on firmware v2.00.02, config v07.005. It’s turned on 24x7 on WiFi with a signal level at -27dBm (excellent) for the past 2 weeks, since I put a node on the porch 6 feet from it.

What on earth do I need to do to get this thing to update? There’s nothing I can find in the app (iOS 2.05.b6 since yesterday) or menus to trigger activity.

WiFire support has been spotty (being polite) since the app “upgrade” and all I want to do is get on par with where I was a few months ago. Any suggestions? Grill connectivity and status over my Plume mesh has been great, but the automation previously available is still missing...

The Traeger Cloud back-end utilizes a PUSH (download) mechanism for updating the Firmware / Config Version data on your WiFIRE Controller - it is not end user triggerable (that would be a PULL update). They have made comments that they plan on moving to a PULL update capability in the future, with no committed timeline (this will require updates to the App and the Firmware) ... the May Updates (2.01.02 for Firmware | 07.006 for your Timberline 1300) were released on May 19th/20th ... sometime on Tue/Wed, they may have "paused" the updates from being PUSHed down in order to deal with the subset of WiFIRE Controllers that are experiencing unexpected shutdowns after the May Updates were installed ...

When you refer to the App Update to 2.x, are you having issues with the App staying current with regards to the Temp/Probe/Timer data, thus requiring you to close out of the App and then re-opening to see the current status?

 

[NunyaBzness]

The Traeger Cloud back-end utilizes a PUSH (download) mechanism for updating the Firmware / Config Version data on your WiFIRE Controller - it is not end user triggerable (that would be a PULL update). They have made comments that they plan on moving to a PULL update capability in the future, with no committed timeline (this will require updates to the App and the Firmware) ... the May Updates (2.01.02 for Firmware | 07.006 for your Timberline 1300) were released on May 19th/20th ... sometime on Tue/Wed, they may have "paused" the updates from being PUSHed down in order to deal with the subset of WiFIRE Controllers that are experiencing unexpected shutdowns after the May Updates were installed ...

When you refer to the App Update to 2.x, are you having issues with the App staying current with regards to the Temp/Probe/Timer data, thus requiring you to close out of the App and then re-opening to see the current status?

Actually, the stability of the phone-to-grill has been pretty solid - recently. The last few updates (and probably configuration/notification settings) have proven fairly reliable for remote monitor/manual cooks. I miss the automated cooks (e.g., Smoked Pork Loin) that auto-set time/temp through multiple phases and didn't require a lot of hand holding. When triggered now, it goes directly to step 4 (350 degrees for 20-30 minutes), skipping the entire multi-hour slow smoke. It's a home favorite and now just flat doesn't work...

 

[dunawayfamily]

Yeah - the removal of Custom Cooks for those that utilized it sucks ... they supposedly added the ability to configure 2 Custom Cooks within the WiFIRE Controller directly, but I haven't looked into that since the May Updates were installed ...