This issue is not as rare as some people think. I just had to create a 2.4GHz ONLY network to connect a newly installed fast EV charger (Blink) at a Chevrolet dealership. In this year of our Lord 2024!
I thought that this requirement died in the last century.
Re: This issue is not as rare as some people think
Something to discuss with the IoT Mfr about. There the ones who design there stuff to only work on 2.4Ghz signals when they fail to make there software work with mobile devices like phones and pads that prefer to connect on 5Ghz signals that are on the SAME NETWORK as 2.4Ghz signals.
I thought I was replying to a topic about the need to set up a 2.4 only network on an Orbi system. I guess not. Oops.
No. I think you were doing just that. But Netgear's community software does this from time to time. It separates the new message from the older conversation.
Knowing that this happens, I should have checked for earlier messages with the same subject.
There are still devices out there today that will not connect to a mixed 2.4/5.0 network.
It is not that those devices will not connect. They cannot connect to 5 GHz but they will connect to 2.4 GHz.
The problem is that too many IoT device makes rely on badly written mobile apps on devices that connect to 5 GHz and cannot find a device with a 2.4 GHz connection on the same network.
This is an ongoing saga.
As @FURRYe38 says, the people to shout at are the ones who created this hopeless app. Just ask them a simple question:
"How do I connect my device to Smart/MESH network?"
Re: This issue is not as rare as some people think
Might ask them more detailed question, why can't your app let the setup mobile device be connected to a MESH system that doesn't support separation of SSID names and why doesn't there software allow setup mobile devices that are connected on 5Ghz signals that are on same network as 2.4Ghz to work in this configuration. 🤔
