diff --git a/README.md b/README.md
index 47dfc136597a2ba0e596e3f028fb42e54258442b..c71720a36e27c1f2b41aa103fbe6ebd5b2accdb7 100644
--- a/README.md
+++ b/README.md
@@ -32,6 +32,7 @@ config controller 'controller'
 	option enabled '1'
 	option registrar '5 2'
 	option debug '0'
+	option bcn_metrics_max_num '10'
 	option initial_channel_scan '0'
 	option primary_vid '1'
 	option enable_ts '0'
@@ -39,6 +40,22 @@ config controller 'controller'
 	option allow_bgdfs '0'
 	option channel_plan '0'
 
+config sta_steering
+	option steer_module 'rcpi'
+	option enabled '1'
+	option enable_sta_steer '0'
+	option enable_bsta_steer '0'
+	option use_bcn_metrics '0'
+	option use_usta_metrics '0'
+	option bandsteer '0'
+	option diffsnr '8'
+	option rcpi_threshold_2g '70'
+	option rcpi_threshold_5g '86'
+	option rcpi_threshold_6g '86'
+	option report_rcpi_threshold_2g '80'
+	option report_rcpi_threshold_5g '96'
+	option report_rcpi_threshold_6g '96'
+
 config ap
 	option band '5'
 	option ssid 'iopsysWrt-021000000001'
@@ -389,15 +406,23 @@ supported. For STA to be able to be steered its drivers must support 802.11k
 
 To enable STA steering feature one must set following in map-controller UCI
 config:
+```
+config sta_steering
+	option steer_module 'rcpi'
+	option enabled '1'
+	option enable_sta_steer '1'
+	option use_bcn_metrics '1'
+```
+
+It may also be needed to enable initial channel scan
+
 ```
 config controller 'controller'
-        option enable_sta_steer '1'
-        option use_bcn_metrics '1'
-	option initial_channel_scan '1'
+	 option initial_channel_scan '1'
 ```
 
 BTM steering may also work fine w/o the initial_channel_scan set - it
-depends on the bottom layer implementation.
+depends on the bottom layer implementation (independent channel scan).
 
 Setting the initial_channel_scan option itself will cause a radio scan request
 to be issued towards given node and it's reported radios, providing there was
@@ -405,8 +430,18 @@ no prior scan results reported on given radio. This radio channel scan will
 be issued once controller obtains first scan capability information tlv from
 given node. Radios, opclasses and channels to scan depend on these scan caps.
 
-The steering decision is based upon drop of the STA RCPI below certain
-threshold, which can be modified per radio via UCI config:
+The steering decision is based upon drop of the STA RCPI below report rcpi
+threshold, which can be modified globally using sta_steering section separately
+for each radio band
+
+```
+config sta_steering
+	option report_rcpi_threshold_2g '80'
+	option report_rcpi_threshold_5g '96'
+	option report_rcpi_threshold_6g '96'
+```
+
+Or per radio via radio section of UCI config:
 
 ```
 config radio 'radio_44d4376af4cf'            
@@ -417,15 +452,33 @@ config radio 'radio_44d4376af4cf'            
         option report_rcpi_threshold '96'
 ```
 
-In case the rcpi_threshold is not set it defaults in code to 86 for 5GHz and
-70 for 2.4GHz.
+In case the rcpi_threshold is not set it defaults in code to 86 for 5GHz & 6Ghz
+and to 70 for 2.4GHz.
 
 Once the signal strength goes below the report_rcpi_threshold it’ll trigger
 link metrics response from agent to controller, causing controller to send
 beacon metrics request for the given STA on all operating classes/channels of
 nodes in the mesh. The beacon metrics results will be parsed and if there’s a
 better (at least 10dB difference in RSSI) BSS found for given STA, controller
-will try to to move STA to that BSS using BTM.
+will try to to move STA to that BSS using BTM. Providing the signal dropped
+further below second tier thershold in the meanwhile
+
+```
+config sta_steering
+	option rcpi_threshold_2g '70'
+	option rcpi_threshold_5g '86'
+	option rcpi_threshold_6g '86'
+```
+
+rcpi_threshold_Xg can be set per radio similarily to report_rcpi_threshold_Xg
+
+Also the difference of RSSI of a new and an old AP must be above the diffsnr
+threshold for the steer to trigger
+
+```
+config sta_steering
+	option diffsnr '8'
+```
 
 ### Steer Exclude