Traeger app

Hoffer

New member
Joined
May 25, 2020
Messages
1
Reaction score
0
Points
1
Location
Denmark
Grill
Traeger Ironwood 885
Hi there , any one have the same problem as I with the traeger app ? When my app is open and I set the temp or timer or super smoke - the app and my ironwood 885 Is getting the information , but if i give my app some new information sutch of turn super smoke off , set a new temp or something else, the grill is getting the information but the app dont respond to the changes - but if I close the app down and turn it on again , then the changes I did before closing the app is now showing in the app - I can then start all over again - it won't update in the app either ? Meaning that if I use the probe - the temp in meat won't update - I need again to close the app again and start the app up again and then the app have updated the temp. Real annoying ???

best regards

mr hoffmann
 

dunawayfamily

Active member
Joined
Apr 23, 2020
Messages
484
Reaction score
142
Points
43
Location
King County, WA State, US
Grill
PRO 780
Hi there , any one have the same problem as I with the traeger app ? When my app is open and I set the temp or timer or super smoke - the app and my ironwood 885 Is getting the information , but if i give my app some new information sutch of turn super smoke off , set a new temp or something else, the grill is getting the information but the app dont respond to the changes - but if I close the app down and turn it on again , then the changes I did before closing the app is now showing in the app - I can then start all over again - it won't update in the app either ? Meaning that if I use the probe - the temp in meat won't update - I need again to close the app again and start the app up again and then the app have updated the temp. Real annoying ???

best regards

mr hoffmann

Seeing similar issues on the App requiring closing/re-launching to get it to update the Temp/Probe/Timer data ... the App is somehow losing refresh status to the Traeger Cloud back-end ... it has been an issue since the last few minor 2.x updates (don't remember if this started with 2.x or not) ...
 
Top