Integrating iTach WiFi units with Ubiquiti APs The iTach WiFi uses an older 802.11b wireless protocol. This protocol is not enabled by default on Ubiquiti APs. To enable 802.11b and allow the iTach WiFi to connect follow the instructions below: 1) From the home page of the Unifi management screen, select the "Settings" Icon on the bottom left.2) Once in Settings, select Wireless Networks3) Click on the "pencil" icon on the far upper right of the screen to edit the "WLAN Group" settings. NOT the "EDIT" on the same line as the AP Wireless Network name.4) Select the checkbox for "Enable legacy device support (i.e. 11b)". 5) Edit: Set the Name fields to match the WLAN group name that contains the wireless network the iTach will be connected to.6) Click on "SAVE" UAP-HD Users: A recent user report indicates that on UAP-HD APs the 2G minimum data rate may also need to be changed. Change 2G Data Rate Control from 6Mbps to 1Mbps: UAP-HD_DataRate.png (70 KB) UAP-HD_ModifiedDataRate.png (100 KB) Have more questions? Submit a request 8 Comments Date Votes 0 Krister Ekberg October 19, 2019 15:12 I upgraded my unify controller to 5.11.50 and after that the itach refused to connect to to the wifi. After countless resets and re-setups i gave up and reverted the controller software to 5.11.47 and the itach started working again. 0 Julian November 10, 2019 22:30 I've the exact same problem. My current config: Also unifi controller 5.11.50 UniFi AP-AC-Pro version 18.104.22.16832 Lagacy mode is on. minimum data rate control 1mbps on 2.4 radio. Also the SSID For 2.4 and 5 GHz is splitterd. DTIM: default values checked. The Itach is standing under a access point, so it could not be a out of range problem. 0 Garrett Gustafson November 25, 2019 22:15 Hello Krister and Julian,Thank you for the reports. We have obtained an AP-AC-Pro AP for testing and are able to successfully connect the iTach WiFi with the following controller and AP versions. UniFi Controller: 5.12.35 UniFi AP-AC-Pro version: 22.214.171.12471 If either of you are still seeing issues on the latest versions above please send an email to email@example.com and we can troubleshoot further. Best regards, -Garrett Edited by Garrett Gustafson November 25, 2019 22:22 0 Trent Jensen March 26, 2020 05:20 I was so glad to come across this thread. When i upgraded to 5.12.66 my iTach was unable to associate with the legacy network any longer. I manipulated as many settings as seemed reasonable, but no luck. I then downgraded to 5.12.35 and iTach came right back online. I'd love to know the plan for the future? Would like an iTach that could support current protocols. 0 Ellery Coffman April 04, 2020 07:09 For those having problems after upgrading the AP Pro, it was necessary for me to do both: legacy settings and lower data rate control. Before things worked with just the Unify Legacy setting checked. 0 James Sheeler July 30, 2020 05:58 I upgraded to the new UDM-PRO with controller 5.14.18 and even with these settings that worked previously with a USG-3 on controller 5.12 no longer works.... Controller 5.14.18 UDM 1.8.0-rc.7.2870 AP-AC-PRO 126.96.36.19957 Edited by James Sheeler July 30, 2020 06:01 0 Trent Jensen July 30, 2020 13:55 Latest controller version on ui.com is 15.13.32 and the settings are working for me. In the Wifi Network where iTach is associated I set the Data Rate to 1Mbps for 2G data. That Wifi Network is assigned to a Wifi Network Group that has Legacy Support Enabled. 0 Vince Bray October 18, 2020 01:34 On controller 188.8.131.52 with the legacy ssid on a nanohd, got the itachs to connect to wifi but couldn't ping them. Go to settings, and turn off new settings. Under wifi, your ssid for legacy devices, make sure the option for Block LAN to WLAN Multicast and Broadcast Data is off. I can then ping and control the itach. Set the dtim on that ssid to 1 for 2.4. Set the ssid to only broadcast on 2.4 (not sure if this matters but it is set) edit: updated the beta firmware on the ac-lite ap and the GC devices quit working. Rolled back to the release version and it fixed it. Just adding because it can be just as simple as your AP version having an issue with 802.11b. Edited by Vince Bray October 27, 2020 01:31 Please sign in to leave a comment.