WR902AC CloudHub using only 5GHz WiFI

I installed the CloudHub image on a WR902AC TP-Link router. It all works, but I observe that there is no apparent way, within the VirtualHere UI, to select which radio is used for WiFi. The image defaults to only the 5 GHz radio. In my case, all of the networks that I will be connecting to are 2.4GHz. I was obviously able to change this using uci commands from the lede shell, but that sort of defeats the purpose of an "appliance" device.

Is there a way to change from 5GHz to 2.4GHz or to enable both radios within the UI? If not, this would be a great feature to add. It could be a simple checkbox in the Channel Select screen, perhaps.

I did purchase one unlimited license, BTW.

#2

Yes ill add it in in the next build in a day or two. I did test a few weeks ago with the 2.4ghz but it seems its only 1t1r (150Mbps) rather than 2t2r (300Mbps) , ill play around with the settings a bit more....anyway ill add the setting in the GUI for the cloudhub.

#4

This is now in client 4.3.1 AND virtualhere server firmware 3.4.4

#5

I tested client 4.3.1 and server win54 bit 3.4.4. I was able to make both radios work, in both standalone (AP) and joined (client) WiFi modes, but there is an anomaly.

The following sequence works:
Load firmware update and hard reset (7 second reset button) device
Connect via 5GHz WiFi to SSID cloudhub66
Change to standalone 2.4GHz mode
Connect via 2.4GHz WiFi to SSID cloudhub66
Change to join a network (client) mode
Refresh network list
Choose a 2.4GHz network
Enter PSK
Apply
Verify that device connected to selected network and that it is discovered by VirtualHere client on Windows box

However, the following DOES NOT work:
Load firmware update and hard reset (7 second reset button) device
Connect via 5GHz WiFi to SSID cloudhub66
Change to standalone 2.4GHz mode, AND
Change to join a network (client) mode
Refresh network list
Choose a 2.4GHz network
Enter PSK
Apply
No connection will be established to the 2.4 GHz network.

I repeated the two tests above twice, so have reasonable confidence that it is reproducible.
That being said, there is a perfectly good workaround - don't change both frequency and mode in one step!
It works just fine if one item is changed at a time.

Thanks for dealing with this so quickly

#6

OK i will fix this in the next build of the server of virtualhere which should be early next week at this point...

#7

This is fixed in version 3.4.6 of the firmware