Traeger is a terrible company. My WiFi broadcasts in 2.4ghz and 5 ghz. The WiFi is smart enough to know what frequency a product needs. 2.4 or 5. Unfortunately Traeger can’t handle mesh WiFi. It’s not smart enough. In this day and age how can Traeger not be selling a product that syncs to 5ghz? Go figure. I spoke to a representative and Traeger is aware of the issue but apparently they don’t care. What an attitude.
What mesh networking product are you using? Have you been able to get it working? With the exception of eero, most other mesh products allow you to control the radios to allow either an SSID rename of one of the networks, or allow you to temporarily disable the 5GHz radio long enough to complete the setup process (and then you can turn it back on given that the Traeger Cloud back-end brokers all communications between WiFIRE and the App Device) ... eero requires you to contact their support and interactively work with them to temporarily disable the 5GHz radio while you complete the setup process ...
Here is a recap as to the "why" of selecting a 2.4GHz radio for an IoT-device is "commonplace" within the industry ... what is "at issue" is the App and the manner in which it handles the App Device passing the Home Wi-Fi Network information to the WiFIRE Controller ... there are other IoT vendors using similar setup routines that successfully complete without requiring some of the workarounds that WiFIRE requires ... Using the WiFIRE Controller display to select the Wi-Fi Network and then to input the WPA2 Password via the Dial should be an option (albeit a painful one) ...
==========
The goal for all IoT-device vendors is to reach the widest possible customer base "out-of-the-box" ... that means targeting the most widely implemented Wi-Fi Standard possible ... the following table is a quick summary of the timeline of the "major" releases with regards to Wi-Fi that have been widely adopted by the industry:
Predominant Wi-Fi Network Standards in use today ...
802.11b - circa 2000 - 2.4GHz - 11Mb/sec max data rate
802.11g - circa 2003 - 2.4GHz - 54Mb/sec max data rate
802.11n (aka Wi-Fi 4) - circa 2009 - 2.4GHz & 5GHz - 600Mb/sec max data rate
802.11ac (aka Wi-Fi 5) - circa 2013 - 2.4GHz & 5GHz - 600Mb/sec max data rate
+ wider channels & more streams & higher-order modulation & addition of MU-MIMO
+ Mesh Networks starting to become available 2017+
802.11ax (aka Wi-Fi 6) - circa 2019/2020 - 2.4GHz & 5GHz
+ goal is to provide 4x the throughput of 802.11ac
+ OFDMA introduced for multiplexing
Given the above, almost all IoT-device vendors implement Wi-Fi via a chipset that supports 802.11b/g/n, as that will reach the widest possible customer base, thus creating the requirement for connecting the IoT-device to a 2.4GHz Wireless Network ... what seems a bit "unique" to the chipset used in the WiFIRE Controllers is the inability to connect to a single Wireless Network Name (SSID) that includes both 2.4GHz & 5GHz, thus needing to rename one of the frequencies ... In my setup, I choose to rename the 5GHz channel (idIOT & idIOT 5GHz) ... Traeger is not the first/only vendor to make the "you must have separate Wireless Network Names" requirement, but I would agree that in 2018-2020+, that caught me off-guard, but since I have run into it in the past, I was prepared to make the necessary changes during my initial setup phase of the WiFIRE Controller ...