dunawayfamily
Active member
- Joined
- Apr 23, 2020
- Messages
- 537
- Media
- 39
- Reaction score
- 156
- Location
- King County, WA State, US
- Grill
- PRO 780
I spent a couple of hours on the phone with Traeger support to resolve two issues with my nearly new grill.
Last weekend after about 5 cooks the lid came off in my hands. The left hinge broke. the lid itself seemed a bit wonky as well. Traeger is sending me a new hinge and lid.
We then attempted to tackle the fact that my Pro 780 will not connect to my eero network. We determined that the grill software and firmware are old but I cannot update them until I can successfully connect to my network. I called eero who were very helpful and temporarily turned off 5GHz so the grill could connect to the 2.4 GHz band. No luck after several attempts so I called back to Traeger again and we did more troubleshooting. Still no luck. They think my controller may be faulty and are sending a new one.
I have a 2.4 GHz Nest security camera on my deck that connects and stays connected with no issues. Connecting my grill shouldn't be a problem yet it is. Traeger needs to address this shortcoming. The wifi connectivity was the main reason that I purchased this grill and I expect it to work as advertised.
Unfortunately, Traeger cannot give me a date on when the lid assembly or controller will arrive. I am most concerned about the hinge and lid as without that fixed I cannot use the grill at all and prime grilling season is finally here.
While I am pleased that Traeger are standing behind their product, I am very disappointed as I had big grilling plans this summer and I have 2-month-old grill sitting on my deck that I cannot use.
This hasn't been the stellar introduction to Traeger grills that I was hoping for. ?
The Lid/Hinge failure is very unfortunate ...
The challenges relative to getting WiFIRE setup is a mixed bag - some of it can be a result of the limitations of what WiFIRE requires (App Device connected to the same 2.4GHz) versus what Router / Wireless Access Point and App Device are already in place ... There are other Mesh Network solutions that allow the end user to create separate SSIDs for the 2.4GHz & 5GHz frequencies - eero has stood firm in refusing to do the same (there is a 3+ year old thread on their Community pages with multiple customers making this request over-and-over again) ... usually if someone can locate an old mobile device that only supports 2.4GHz, or defaults to that as the primary/preferred connections, they are able to get the setup process to complete ... the added frustration comes in when you've been sitting on a WiFIRE Controller that needs to be swapped out before you can get it setup / working ...
Cut/Paste from a posting I made yesterday on a separate thread:
The stated "requirement" for a separate 2.4GHz SSID really has nothing to do with the WiFIRE Controller itself, but the App Device being used to initially setup the WiFIRE Controller and connect it to your Home Wi-Fi Network ... most modern mobile devices support both 2.4GHz & 5GHz Wireless Networks and will always default to the preferred frequency when it is available (i.e. 5GHz since it provides better throughput) ... so if the WiFIRE Controller is within range of both frequencies, and your App Device being used during setup supports both frequencies, you can end up with the WiFIRE Controller sitting on the 2.4GHz frequency (the only one it supports), and the App Device sitting on the 5GHz frequency (because it is the default/preferred), thus they won't be able to communicate 1:1 during the setup process ... if the WiFIRE Controller is far enough from your Router / Wireless Access Point that the preferred (or only available) connection for your App Device is the 2.4GHz frequency, then you will not have any issues during the setup process ... if the App Device you use to complete the setup process is old enough that it only supports 2.4GHz Wireless Networks, or will default to 2.4GHz Wireless if given a choice (ex. 802.11b/g/n), then you will not have any issues during the setup process ... since most people have new(er) App Devices, along with potentially old(er) Router / Wireless Access Points, and they probably have limited/zero experience deploying IoT-based devices, they tend to fall into the following category:
The vast majority of Wi-Fi challenges are due to issues with the configuration of the Router / Wireless Access Point and/or issues with the App Device config, both of which can be resolved with minor changes ... people are expecting "plug and play" and not prepared to have to intervene to accommodate the necessary changes / workarounds ...