Unless you can get Sensibo to improve their product, or give you some tools to manage their devices, I'm afraid there might not be much to do. It is the device that determines what AP to connect to and when it's time to roam.Had it been e.g. a Windows Client with Intel Wireless, you'd most likely have to options on the Wireless NIC to set roaming aggressiveness, making the device more prone to roam to better APs, based on the current RF environment.
So if you'd want to have your Sensibo device to connect to a specific AP, you'll have to look into making that single AP look more favorable from an RF point of view, than the other APs. The adverse effect would be that it would make all other wireless clients try to favor that AP in stead of the rest of the infrastructure.
Alternatively. you could create an Facility SSID called, say, HVAC, and have that SSID only broadcasted on tagged APs. In your case that specific AP in the computer room.
Another possible reason could be that the AP in the Computer room is loaded, in terms of clients. Perhaps, it owuld help to disable Client Balancing on the Radio Profile.
However, with that being said, is it really an issue that the Sensibo device is connecting to a different AP than intended? Does it have a poor connection on the "wrong" AP?
LinkedIn :::
https://blog.rhbirkelund.dk/Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution
🙂All code examples are provided as is. Responsibility for Code execution lies solely your own.
