Thank you for sharing the link to that thread - I read through it, and while it provided some info about the options for using the roaming feature, it didn't give me an explanation of the roaming feature itself.
Taking a specific example, let's say the device has SSID1 and SSID2 saved in its DCT, and that the device is connected to SSID1, with the roaming trigger set to -50dbm. If the device is moved out of range (<-50dbm) of SSID1 and into the range of SSID2 (>-50dbm), how is the reconnection handled? In what thread's context is the reconnection attempted? How is the success/failure of the reconnect reported back to the application?
Our application uses five SSID/Passwords saved in the DCT - what is the best way to seamlessly transition between these five based on availability? Any examples or implementation suggestions would be greatly appreciated.
1 of 1 people found this helpful
copy some info from internet:
The simplest setup involves setting up multiple APs (or routers set as APs) of any brand, connecting them to the same WiFi network with the same DHCP server, same SSID, same security type (i.e. WPA2-AES, etc.), same passphrase, but different channels.
seems your five SSIDs are not a roaming setting for the tests.
Thank you for your response - I better understand the concept of roaming now. I have gone ahead and set up multiple APs, all connected to the same DHCP server with same SSID, security type, and passphrase. I am working on ensuring they are all on different channels - but why is this a requirement? Most setups in the field have APs which dynamically switch channels all the time.
What prints/callbacks can I enable in WICED in order to see the roaming trigger taking effect and working correctly? Ideally I would like to see that the wifi disassociation and re-association is happening correctly as I move the device between the different APs.