UniFi APs and Controller Kicking Blink Sync Module

Hello Everyone,

I am running into an issue with Blink's Sync Module 2 that basically gets disassociated after being on the WiFi for about 30 seconds. It 100% repeatable on any UniFi system, using any Blink Sync Module (1 or 2).

A little background on me, I am a long time UniFi admin.

I am connecting a Blink Sync Module 2 to an SSID (configured as per below specs) on my UniFi Dream Machine or my Unifi FlexHD access points or both at home.

I also tested on my system at work which consists of 100+ nanoHD Access Points and a UniFi Controller.

The Blink Sync Module will only connect over 2.4 GHz and is named walnut (default name).

The SSID being tested was named IoTRoD (at home)

Securiy: WPA Personal

Wifi Band: 2.4 GHz

WPA Mode: WPA2 only, Encryption: AES/CCMP Only

Group Rekey Interval: Enable GTK rekeying every 3600 seconds

BSS Transition: Allow BSS Transition with WNM

Tried on UDM firmware 1.8.4 and 1.8.5

Tried on UAP-FlexHD version 5.43.19.12493 and 4.3.21 and 4.0.80

Tried building a new controller on version 6.0.43, 6.0.41 and 5.14.23 on Windows and Linux.

I also have a ticket open with Ubiquiti Support and they have suggested I try the following which I have with the same results and log output:

1. Disable Auto-Optimize network (was already but I enabled and re-disabled)
2. Disable Block LAN to WAN Multicast and Broadcast Data (was already but I enabled and re-disabled)
3. Disable Fast Roaming (was already but I enabled and re-disabled)
4. Disable High-performance devices (was already but I enabled and re-disabled)

All with the same results with the same message as below.

Radius is not enabled what so ever, which is why it is so confusing to why there are these radius events. No other device triggers this to happen and as stated the exact same thing happens in my stable work environment.

Below is a snippet from the /var/log/messages file

# tail -f messages |grep a0:d0:dc:b1:37:XX

Dec 30 01:59:00 BasementAP daemon.info hostapd: ra1: STA a0:d0:dc:b1:37:XX IEEE 802.11: associated

Dec 30 01:59:00 BasementAP user.info wevent: wevent[17715]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ra1: a0:d0:dc:b1:37:XX / 12

Dec 30 01:59:00 BasementAP daemon.info hostapd: ra1: STA a0:d0:dc:b1:37:XX WPA: pairwise key handshake completed (RSN)

Dec 30 01:59:00 BasementAP daemon.info dnsmasq-dhcp[2146]: DHCPDISCOVER(br0) a0:d0:dc:b1:37:XX

Dec 30 01:59:00 BasementAP daemon.info dnsmasq-dhcp[2146]: DHCPOFFER(br0) 172.XXX.XXX.171 a0:d0:dc:b1:37:XX

Dec 30 01:59:00 BasementAP daemon.info dnsmasq-dhcp[2146]: DHCPREQUEST(br0) 172.XXX.XXX.171 a0:d0:dc:b1:37:XX

Dec 30 01:59:00 BasementAP daemon.info dnsmasq-dhcp[2146]: DHCPACK(br0) 172.XXX.XXX.171 a0:d0:dc:b1:37:XX walnut

Dec 30 01:59:00 BasementAP user.info wevent: wevent[17715]: wevent.ubnt_custom_event(): EVENT_STA_IP ra1: a0:d0:dc:b1:37:XX / 172.XXX.XXX.171

Dec 30 01:59:10 BasementAP daemon.info hostapd: ra1: STA a0:d0:dc:b1:37:XX RADIUS: starting accounting session 562CB5429F4E6E9C

Dec 30 01:59:10 BasementAP user.info stahtd: stahtd[17719]: [STA-TRACKER].stahtd_dump_event(): {"message_type":"STA_ASSOC_TRACKER","mac":"a0:d0:dc:b1:37:XX","vap":"ra1","event_type":"success","assoc_status":"0","ip_delta":"300000","ip_assign_type":"dhcp","wpa_auth_delta":"40000","assoc_delta":"20000","auth_delta":"0","event_id":"1","auth_ts":"19573.719202","arp_reply_gw_seen":"yes"}

Dec 30 01:59:37 BasementAP daemon.info hostapd: ra1: STA a0:d0:dc:b1:37:XX IEEE 802.11: disassociated

Dec 30 01:59:37 BasementAP user.info wevent: wevent[17715]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ra1: a0:d0:dc:b1:37:XX / 12

Dec 30 01:59:37 BasementAP user.warn kernel: [19610.522673] ra1: AUTH - receive DE-AUTH(seq-28) from a0:d0:dc:b1:37:XX, reason=3

Dec 30 01:59:37 BasementAP user.warn kernel: [19610.522892] Can't find pEntry(a0:d0:dc:b1:37:XX) in ApStaDel

Dec 30 01:59:37 BasementAP user.info stahtd: stahtd[17719]: [STA-TRACKER].stahtd_dump_event(): {"message_type":"STA_ASSOC_TRACKER","mac":"a0:d0:dc:b1:37:XX","vap":"ra1","event_type":"sta_leave","assoc_status":"0","event_id":"1"}

Any ideas on how to fix or troubleshoot further would be greatly appreciated.