You should set roam_scan_snr and signal_diff_threshold.
They're the main options for roaming.
How did you install it? I have the same issue but the firmware is much smaller that the files I found in my image.
Firmware is 200kb and installed 621kb.
Switched back to Non-CT firmware and mobiles seems to roam fine. But I saw that devices like my Alexa are stick to a specific AP (also the case for -CT)
The Alexa is visible in the hearing map on the AP connected only. The nearest AP (1m away) does not detect it. After restarting Wifi it is shown in hearing map on all APs for some time and then only on the AP connected. Is this common?
"14:0a:c5:fd:xx:xx": {
"signal": -71,
"created": 37004419,
"connected": 38188001,
"snr-kick": {
"seen-below": 0
},
"roam-state-machine": {
"state": "ROAM_TRIGGER_SCAN",
"tries": 3,
"event": 3012,
"kick-count": 0,
"last-kick": 0,
"scan_start": 23040,
"scan_timeout_start": 0
},
"bss-transition-response": {
"status-code": 0,
"age": 0
},
"beacon-measurement-modes": [
],
"link-measurement": false,
"bss-transition-management": false,
"multi-band-operation": false,
"measurements": [
]
It only appears when the device does a "scan" of the wifi networks. Usteer can send a beacon to the device to force this scan, you can configure this beacon depending on some conditions in the config, for example some low signal level.
1 Like
Is this option roam_scan_snr '-60'?
In the logs I can see the following, perhaps it is like it is?
Sun Apr 28 12:06:26 2024 user.debug usteer: STA does not support beacon measurement sta=14:0a:c5:fd:xx:xx Sun Apr 28 12:06:26 2024 user.info usteer: usteer event=probe_req_accept node=hostapd.wl0-ap2 sta=14:0a:c5:fd:xx:xx signal=-75
Will try options to get my Alexas not stick to an AP or does somebody know other options?
option min_connect_snr '-72'
option min_snr '-78'
My config
config usteer
option network 'lan'
option syslog '1'
option local_mode '0'
option ipv6 '0'
option debug_level '3'
option load_balancing_threshold '10'
option band_steering_threshold '20'
option roam_scan_snr '-60'
option signal_diff_threshold '10'
option band_steering_min_snr '-62'
option min_connect_snr '-72'
option min_snr '-78'
list event_log_types 'probe_req_accept'
list event_log_types 'probe_req_deny'
list event_log_types 'signal_kick'
option assoc_steering '1'
option probe_steering '1'
Start your config from scratch and edit only roam_scan_snr and signal_diff_treshold.
Anyway, it seems that Alexa doesn't support beacon measurements... It's not a static device?
You can block MAC from the AP you don't want Alexa connect to..
Usteer works fine now but I disabled support for unsupported devices like Alexa again. Itâs much better than DAWN in my opinion that I tried before.
Any thoughts about blocking MAC from usteer?
Spams logs of static devices...
Short question about ssid_list...the guide marked it as not required but in this thread I found some references that ssid_list has to be set to enable steering.
[OpenWrt Wiki] Setting up usteer and band-steering in OpenWrt
Actually it looks fine to me without this. I cannot see any difference in the logs with or without SSIDs set so is this right? Should it be set and how if I have 3 SSID that are different VLANs..."main", "iot" and "guest" which should be handled separately.
Cheers,
Nils
Iâm sure I said this for a reason. I donât have time right now to chase out all the function calls again but from a very quick glance it will not monitor any SSID not listed in the config.
https://git.openwrt.org/?p=project/usteer.git;a=blob;f=local_node.c;h=e74d945efa05c29b838fbcade49e7e9c3ba2d39e;hb=refs/heads/master#l805
However, looking at the band_steering code I donât see any checks for disabled, so perhaps it is unaffected.
More in depth checks required.
Without SSIDs set I also get the connection message created in that procedure...so it looks fine for me. Perhaps it puts in all SSIDs if nothing is set at another place.
Jun 17 08:13:26 OpenWrt2 usteer: Found nl80211 phy on wdev hostapd.phy0-ap1, ssid=main
Jun 17 08:13:26 OpenWrt2 usteer: Connecting to local node hostapd.phy0-ap1
Jun 17 08:13:26 OpenWrt2 usteer: Creating local node hostapd.phy0-ap2
Hi, I got it installed whith the help of this thread and it seems working great.
But I have 2 subnets, the APs on them with the same SSID. These subnets can communicate between them. It is there any way to tell Usteer the nodes that are not in its subnet should join the team?
There is a notable improvement in the performance of the whole network! Mostly i have Mikrotik SXTsq Lite at 2.4. Before Ulsteer, I have never seen one of these stations reaching more than 30mbits/sec- Now I see peaks of 40, 50, 60 and even 70mb/sec!!. This network is running Openwrt nodes linked with Airmax in a Camping. Before Usteer they were broadcasting CAMP_XXX1, CAMP_XXX2, now they all broadcast the same SSID and the improvement IS HEAVY! I am struggling to understand how a feature I installed to stop having users asking whats the right net to join has improved even the throughput of my APs!
Anyone? Tks!
1 Like
Do you mean you have 2 subnets with 2 SSID on each AP? Or do you mean one subnet per AP? And what do you mean "should join the team"?
1 Like
I mean I have two subnets with 6 APs each broadcasting the same SSID.
I want to have usteer managing all the APs in booth subnets, but it only sees the ones in its subnet.
What I need is to tell the AP with ip 192.168.2.1/22 that AP 192.168.4.5/22 in the other subnet should be integrated as one more AP of the team, but it does not see it. So I have 2 usteer teams with the same SSID.
Any way to add NODES manually?
Tks
i dont think that was implemented as you typically roam within a sub-net. Why not make them all the same sub-net? That really makes most sense.
1 Like
There are two UB Rockets plugged to 2 interfaces of a pFsense. These provide two areas of the camping. I tried bridging these interfaces but it does not work well in pfsense and I do not want to put a cheap switch there. Besides too many stations for a single subnet, it will try to develop it by myself, lets see.
Tks anyway!
I have no experience with pFsense, but consider an openwrt compatible router instead?
you can make the subnet as big as you want. If you use the 10.x.x.x you have space for 16 million devices.
Anyway, good luck!
1 Like
I fixed it by now creating 2 vlans in the wireless interfaces of pfsense, bridging them in one and creating a VLAN interface in Openwrt in each AP just for Usteer, now they see each other ok 
Tks anyway!
1 Like
Usteer does not show Roam src/Roam tgt entries for the AP logged into and also the numbers are different between APs. Is it a bug? From my understanding also the actual AP should show roaming entries...
i believe that is a bug indeed. Im guessing it is only affecting the reporting not the actual roaming.