WiFi clients disconnecting and reconnecting every minute

I have just added extra WiFi SSIDs for all things IoT with VLANs to my access points and router, however I have noticed that I have between 2 and 4 clients (Mostly Google minis) but has been some other tasmota devices at times that will constantly disconnect and reconnect every min or so, this is only happening to some devices on the new IoT SSID not the exiting SSID.
The setup I have is a Raspberry pi CM4 with seeed router board running 21.02 and 2 Ubiquiti UniFi AC Lite flashed with 23.05.2 acting as a "dumb AP" with no firewall or routing.
Things I have tried so far are disabling WLAN roaming (802.11r), disabling one of the access points at a time, disabling the 5gig SSID on both APs but the issue just moves from one AP to the other which makes me think its just possible config issue.

Any tips or pointers in the right direction would be greatly appreciated, I have attached some log files and configs if that helps.

Log file from one of the AP

Sat Dec 30 10:55:42 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 10:55:42 2023 kern.info kernel: [ 5349.781490] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 10:55:43 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 10:55:43 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 5)
Sat Dec 30 10:55:43 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 10:55:43 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 10:55:43 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b
Sat Dec 30 10:56:54 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 10:56:55 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 10:56:55 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 1)
Sat Dec 30 10:56:55 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 10:56:55 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 10:56:55 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b
Sat Dec 30 10:58:07 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 10:58:07 2023 kern.info kernel: [ 5494.275352] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 10:58:07 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 10:58:07 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 5)
Sat Dec 30 10:58:07 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 10:58:07 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 10:58:07 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b
Sat Dec 30 10:59:18 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 10:59:18 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 10:59:18 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 1)
Sat Dec 30 10:59:18 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 10:59:18 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 10:59:18 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b
Sat Dec 30 11:00:30 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 11:00:30 2023 kern.info kernel: [ 5638.021405] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 11:00:31 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 11:00:31 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 5)
Sat Dec 30 11:00:31 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 11:00:31 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 11:00:31 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b

Log file from the main router

Sat Dec 30 10:55:41 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.99) 192.168.0.125 46:b8:83:e7:dd:fc
Sat Dec 30 10:55:41 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.99) 192.168.0.125 46:b8:83:e7:dd:fc
Sat Dec 30 10:55:42 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.99) 192.168.0.125 46:b8:83:e7:dd:fc
Sat Dec 30 10:55:42 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.99) 192.168.0.125 46:b8:83:e7:dd:fc
Sat Dec 30 10:55:43 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 10:55:43 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 10:56:26 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.99) 192.168.0.125 46:b8:83:e7:dd:fc
Sat Dec 30 10:56:26 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.99) 192.168.0.125 46:b8:83:e7:dd:fc
Sat Dec 30 10:56:55 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 10:56:55 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 10:58:07 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 10:58:07 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 10:59:19 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 10:59:19 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 11:00:31 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 11:00:31 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 11:00:35 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 11:00:35 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 11:01:47 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 11:01:47 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 11:03:02 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 11:03:02 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser
Sat Dec 30 11:03:06 2023 daemon.info dnsmasq-dhcp[16287]: DHCPREQUEST(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b
Sat Dec 30 11:03:06 2023 daemon.info dnsmasq-dhcp[16287]: DHCPACK(br-lan.3) 192.168.2.176 b0:2a:43:63:78:1b Google-Home-Mini-Laser

WiFi Config (Same on both AP) WiFi channels are different though.

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'pci0000:00/0000:00:00.0'
	option channel '36'
	option band '5g'
	option htmode 'VHT80'
	option cell_density '0'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option mode 'ap'
	option encryption 'psk-mixed'
	option key '********'
	option ssid 'FBI Surveillance Van'
	option ieee80211r '1'
	option mobility_domain '4f57'
	option ft_over_ds '1'
	option ft_psk_generate_local '1'
	option nasid '19216805'
	option skip_inactivity_poll '1'
	option disassoc_low_ack '0'
	option network 'lan'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/ahb/18100000.wmac'
	option band '2g'
	option cell_density '0'
	option htmode 'HT40'
	option channel '6'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option mode 'ap'
	option encryption 'psk-mixed'
	option key '********'
	option ssid 'FBI Surveillance Van'
	option ieee80211r '1'
	option mobility_domain '4f57'
	option ft_over_ds '1'
	option ft_psk_generate_local '1'
	option nasid '19216805'
	option skip_inactivity_poll '1'
	option disassoc_low_ack '0'
	option wmm '0'
	option network 'lan'

config wifi-iface 'wifinet2'
	option device 'radio0'
	option mode 'ap'
	option ssid 'FBI Surveillance Van IoT'
	option key '********'
	option network 'IOT'
	option disassoc_low_ack '0'
	option encryption 'psk-mixed+ccmp'
	option ieee80211r '1'
	option nasid '192168205'
	option mobility_domain '4f58'
	option ft_over_ds '1'
	option ft_psk_generate_local '1'

config wifi-iface 'wifinet3'
	option device 'radio1'
	option mode 'ap'
	option ssid 'FBI Surveillance Van IoT'
	option key '********'
	option network 'IOT'
	option disassoc_low_ack '0'
	option encryption 'psk-mixed+ccmp'
	option ieee80211r '1'
	option nasid '192168205'
	option mobility_domain '4f58'
	option ft_over_ds '1'
	option ft_psk_generate_local '1'

WiFi AP Network config


config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd94:0e90:742b::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'

config interface 'lan'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option ipaddr '192.168.0.5'
	option gateway '192.168.0.1'
	list dns '192.168.0.1'
	list dns '8.8.8.8'
	option device 'br-lan.99'

config bridge-vlan
	option device 'br-lan'
	option vlan '99'
	list ports 'eth0:u*'

config bridge-vlan
	option device 'br-lan'
	option vlan '4'
	list ports 'eth0:t'

config bridge-vlan
	option device 'br-lan'
	option vlan '3'
	list ports 'eth0:t'

config interface 'Guest'
	option device 'br-lan.4'
	option proto 'none'

config interface 'IOT'
	option device 'br-lan.3'
	option proto 'none'

disable all the 802.11r related items on all your APs. See if that helps.

Thanks for the quick reply, I have tried that already and it didn't make any difference.
I forgot to add that to the main post but I have now.

What about using either WPA2 or WPA3 instead of mixed mode? (just use plan psk2)

Switched all SSIDs to plain WPA2-PSK also tried auto, force CCMP, force TKIP and force TKIP and CCMP, but still no joy.

Does this happen with all SSIDs/VLANs, or just one?

Its only happening with the one IoT SSID

What device is this?
It is not the router.
:spiral_notepad: B02A4363781B / B0-2A-43-63-78-1B

Google, Inc. is registered as the vendor for mac address prefix B02A4363781B. Additional vendor information for this prefix can be found below. Click a vendor or brand name for details on the addresses under their authority.

If it's only happening with the IoT SSID, that suggests that the devices may not be able to get an IP, so they are dropping off the network and then trying to reconnect.

We should review the configuration of the router and whatever else is upstream (I assume you have a managed switch)?

Correct me if I'm wrong but it is only one device causing the problem?

Well, we know that there are two APs:

and multiple clients having difficulty:

So this suggests multiple devices are at play here, both AP devices and client devices.

Okay, I'll take that in if you can show me another device that is connecting and disconnecting that I missed.
I only see b0:2a:43:63:78:1b doing it.

I'm just going based on the OP's description. But regardless, the problem exists for at least one device, so we should look upstream to try to understand if there is any reason at the router or switch level that could be related.

Okay.

I see his dumb AP handshaking, connecting and disconnecting.

I see his DHCP router getting constant requests from the same device and, consistently getting assigned 192.168.2.176 .

I may be wrong,

When you set up the devices to connect to the new ssid, did you, also, have them forget the ssid and settings they were originally using?

Would you send a capture of another device with the same behavior?

Yes, I have managed switches in between the router and the WiFi APs

Router network config

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fdd6:f4e6:e0f3::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'
	list ports 'tun0'

config interface 'lan'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option ipaddr '192.168.0.1'
	option device 'br-lan.99'
	option broadcast '192.168.0.255'
	list dns '192.168.0.1'
	list dns '8.8.8.8'

config interface 'docker'
	option device 'docker0'
	option proto 'none'
	option auto '0'

config device
	option type 'bridge'
	option name 'docker0'

config interface 'WAN'
	option proto 'dhcp'
	option device 'eth1'

config interface 'WAN6'
	option proto 'dhcpv6'
	option device 'eth1'
	option reqaddress 'try'
	option reqprefix 'auto'

config interface 'VPN'
	option proto 'none'
	option device 'tun0'

config bridge-vlan
	option device 'br-lan'
	option vlan '99'
	list ports 'eth0:u*'

config bridge-vlan
	option device 'br-lan'
	option vlan '4'
	list ports 'eth0:t'

config bridge-vlan
	option device 'br-lan'
	option vlan '3'
	list ports 'eth0:t'

config interface 'Guest'
	option proto 'static'
	option device 'br-lan.4'
	option netmask '255.255.255.0'
	option ipaddr '192.168.4.1'
	option broadcast '192.168.4.255'

config interface 'IOT'
	option proto 'static'
	option device 'br-lan.3'
	option ipaddr '192.168.2.1'
	option netmask '255.255.255.0'
	option broadcast '192.168.2.255'

config bridge-vlan
	option device 'br-lan'
	option vlan '10'
	list ports 'eth0:t'

config interface 'Cameras'
	option proto 'static'
	option device 'br-lan.10'
	option ipaddr '192.168.10.1'
	option netmask '255.255.255.0'
	option broadcast '192.168.10.255'

config bridge-vlan
	option device 'br-lan'
	option vlan '20'
	list ports 'eth0:t'

config interface 'Security'
	option proto 'static'
	option device 'br-lan.20'
	option ipaddr '192.168.20.1'
	option netmask '255.255.255.0'
	option broadcast '192.168.20.255'

Router dhcp config


config dnsmasq
	option domainneeded '1'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option localservice '1'
	option ednspacket_max '1232'
	option confdir '/tmp/dnsmasq.d'
	option boguspriv '0'
	option enable_tftp '1'

config boot 'linux'
	option serveraddress '192.168.0.20'
	option servername 'Netbootxyz'

config dhcp 'lan'
	option interface 'lan'
	option dhcpv4 'server'
	option leasetime '168h'
	option start '101'
	option limit '99'
	list ra_flags 'none'

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

config odhcpd 'odhcpd'
	option maindhcp '0'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'
	option loglevel '4'

config host
	option mac '78:8A:20:48:65:7A'
	option dns '1'
	option ip '192.168.0.5'
	option name 'WiFi'

config host
	option mac 'B8:27:EB:76:AB:B6'
	option dns '1'
	option ip '192.168.0.100'
	option name 'OpenHab'

config domain
	option name 'Wiser.lan'
	option ip '192.168.0.2'

config domain
	option name 'Storage.lan'
	option ip '192.168.0.4'

config domain
	option name 'Deluge.lan'
	option ip '192.168.0.6'

config domain
	option name 'Matt.lan'
	option ip '192.168.0.50'

config dhcp 'Guest'
	option interface 'Guest'
	option leasetime '12h'
	option start '50'
	option limit '254'
	list ra_flags 'none'

config dhcp 'IOT'
	option interface 'IOT'
	option leasetime '12h'
	option start '50'
	option limit '254'
	list ra_flags 'none'

config host
	option dns '1'
	option mac '1C:53:F9:A6:1B:A5'
	option ip '192.168.2.199'
	option name 'Nest-Doorbell-Battery'

config host
	option dns '1'
	option mac 'B0:2A:43:7E:B6:0A'
	option ip '192.168.2.232'
	option name 'Google-Home-Mini'

config host
	option dns '1'
	option mac 'D8:8C:79:18:FA:AD'
	option ip '192.168.2.151'
	option name 'Google-Home-Display-Kitchen'

config host
	option dns '1'
	option mac '1C:53:F9:BA:CC:E0'
	option ip '192.168.2.181'
	option name 'Google-Home-Display-Bedroom'

config host
	option dns '1'
	option mac 'B0:2A:43:63:78:1B'
	option ip '192.168.2.176'
	option name 'Google-Home-Mini-Laser'

config host
	option dns '1'
	option mac 'B0:2A:43:8F:65:3C'
	option ip '192.168.2.243'
	option name 'Google-Home-Mini-Office'

config dhcp 'Cameras'
	option interface 'Cameras'
	option leasetime '12h'
	option limit '254'
	option start '100'
	list ra_flags 'none'

config dhcp 'Security'
	option interface 'Security'
	option start '100'
	option limit '150'
	option leasetime '7d'
	list ra_flags 'none'

A tunnel should not be bridged with an Ethernet device. Remove tun0 from the bridge.

Your dhcp servers are invalid. The limit is the size of the dhcp pool, not the ending address. Therefore, the equation for the pool is:

Start - (start + limit - 1)

Your dhcp limit must be 205 or less.

Same problem with your cameras dhcp server. Limit here must be 155 or less.

Fix all those things and reboot the router. Test again and let me know if the problem is resolved.

If not, there are other possible things to fix.

1 Like

Yes, I removed all devices and re authenticated to the new SSID

Log file from 1st Ap showing devices
b0:2a:43:63:78:1b (Google-Home-Mini)
a4:cf:12:a5:9e:83 (Tasmota Plug)
b0:2a:43:7e:b6:0a (Google-Home-Mini)
Disconnecting and re connecting

Sat Dec 30 18:41:22 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:7e:b6:0a auth_alg=open
Sat Dec 30 18:41:22 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:7e:b6:0a WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:41:22 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:7e:b6:0a
Sat Dec 30 18:42:06 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:8f:65:3c
Sat Dec 30 18:42:06 2023 kern.info kernel: [18279.525620] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 18:42:08 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sat Dec 30 18:42:08 2023 daemon.err hostapd: nl80211: NL80211_ATTR_STA_VLAN (addr=42:26:5b:2d:22:d6 ifname=phy1-ap0 vlan_id=0) failed: -2 (No such file or directory)
Sat Dec 30 18:42:08 2023 daemon.info hostapd: phy1-ap0: STA 42:26:5b:2d:22:d6 IEEE 802.11: associated (aid 2)
Sat Dec 30 18:42:08 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 42:26:5b:2d:22:d6 auth_alg=ft
Sat Dec 30 18:42:08 2023 daemon.notice hostapd: phy0-ap0: Prune association for 42:26:5b:2d:22:d6
Sat Dec 30 18:42:08 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 42:26:5b:2d:22:d6
Sat Dec 30 18:42:10 2023 kern.info kernel: [18283.643872] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 18:42:22 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 18:42:23 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 18:42:23 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 1)
Sat Dec 30 18:42:23 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 18:42:23 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:42:23 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b
Sat Dec 30 18:42:38 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:7e:b6:0a
Sat Dec 30 18:42:38 2023 kern.info kernel: [18311.150739] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 18:42:38 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:7e:b6:0a IEEE 802.11: authenticated
Sat Dec 30 18:42:38 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:7e:b6:0a IEEE 802.11: associated (aid 2)
Sat Dec 30 18:42:38 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:7e:b6:0a auth_alg=open
Sat Dec 30 18:42:38 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:7e:b6:0a WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:42:38 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:7e:b6:0a
Sat Dec 30 18:42:38 2023 daemon.info hostapd: phy0-ap0: STA 42:26:5b:2d:22:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Dec 30 18:42:57 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sat Dec 30 18:42:57 2023 daemon.err hostapd: nl80211: NL80211_ATTR_STA_VLAN (addr=42:26:5b:2d:22:d6 ifname=phy0-ap0 vlan_id=0) failed: -2 (No such file or directory)
Sat Dec 30 18:42:57 2023 daemon.info hostapd: phy0-ap0: STA 42:26:5b:2d:22:d6 IEEE 802.11: associated (aid 1)
Sat Dec 30 18:42:57 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED 42:26:5b:2d:22:d6 auth_alg=ft
Sat Dec 30 18:42:57 2023 daemon.notice hostapd: phy1-ap0: Prune association for 42:26:5b:2d:22:d6
Sat Dec 30 18:42:57 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 42:26:5b:2d:22:d6
Sat Dec 30 18:43:27 2023 daemon.info hostapd: phy1-ap0: STA 42:26:5b:2d:22:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Dec 30 18:43:33 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 18:43:33 2023 kern.info kernel: [18366.682947] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 18:43:34 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 18:43:34 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 4)
Sat Dec 30 18:43:34 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 18:43:34 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:43:34 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b
Sat Dec 30 18:43:52 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:7e:b6:0a
Sat Dec 30 18:43:52 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:7e:b6:0a IEEE 802.11: authenticated
Sat Dec 30 18:43:52 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:7e:b6:0a IEEE 802.11: associated (aid 1)
Sat Dec 30 18:43:52 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:7e:b6:0a auth_alg=open
Sat Dec 30 18:43:52 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:7e:b6:0a WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:43:52 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:7e:b6:0a
Sat Dec 30 18:44:45 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: authenticated
Sat Dec 30 18:44:45 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: associated (aid 2)
Sat Dec 30 18:44:45 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED a4:cf:12:a5:9e:83 auth_alg=open
Sat Dec 30 18:44:45 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:44:45 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED a4:cf:12:a5:9e:83
Sat Dec 30 18:44:45 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:63:78:1b
Sat Dec 30 18:44:46 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED a4:cf:12:a5:9e:83
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: disassociated
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: disassociated
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: disassociated
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: disassociated
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: disassociated
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: authenticated
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b IEEE 802.11: associated (aid 3)
Sat Dec 30 18:44:46 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:63:78:1b auth_alg=open
Sat Dec 30 18:44:46 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:63:78:1b WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:44:46 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:63:78:1b
Sat Dec 30 18:44:47 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Dec 30 18:44:47 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: authenticated
Sat Dec 30 18:44:47 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 IEEE 802.11: associated (aid 2)
Sat Dec 30 18:44:47 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED a4:cf:12:a5:9e:83 auth_alg=open
Sat Dec 30 18:44:47 2023 daemon.info hostapd: phy1-ap1: STA a4:cf:12:a5:9e:83 WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:44:47 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED a4:cf:12:a5:9e:83

Log file from 2nd Ap showing device
b0:2a:43:8f:65:3c (Google Home Mini)

Disconnecting and re connecting

Sat Dec 30 18:38:25 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:8f:65:3c
Sat Dec 30 18:38:26 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: authenticated
Sat Dec 30 18:38:26 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: associated (aid 1)
Sat Dec 30 18:38:26 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:8f:65:3c auth_alg=open
Sat Dec 30 18:38:26 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:8f:65:3c WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:38:26 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:8f:65:3c
Sat Dec 30 18:38:54 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:8f:65:3c WPA: group key handshake completed (RSN)
Sat Dec 30 18:39:19 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sat Dec 30 18:39:19 2023 daemon.err hostapd: nl80211: NL80211_ATTR_STA_VLAN (addr=42:26:5b:2d:22:d6 ifname=phy0-ap0 vlan_id=0) failed: -2 (No such file or directory)
Sat Dec 30 18:39:19 2023 daemon.info hostapd: phy0-ap0: STA 42:26:5b:2d:22:d6 IEEE 802.11: associated (aid 1)
Sat Dec 30 18:39:19 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED 42:26:5b:2d:22:d6 auth_alg=ft
Sat Dec 30 18:39:39 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:8f:65:3c
Sat Dec 30 18:39:39 2023 kern.info kernel: [12156.633478] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 18:39:40 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: authenticated
Sat Dec 30 18:39:40 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: associated (aid 4)
Sat Dec 30 18:39:40 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:8f:65:3c auth_alg=open
Sat Dec 30 18:39:40 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:39:40 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:8f:65:3c
Sat Dec 30 18:40:54 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:8f:65:3c
Sat Dec 30 18:42:06 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: authenticated
Sat Dec 30 18:42:06 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: associated (aid 4)
Sat Dec 30 18:42:06 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:8f:65:3c auth_alg=open
Sat Dec 30 18:42:06 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:42:06 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:8f:65:3c
Sat Dec 30 18:43:20 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED b0:2a:43:8f:65:3c
Sat Dec 30 18:43:21 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: authenticated
Sat Dec 30 18:43:21 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: associated (aid 1)
Sat Dec 30 18:43:21 2023 daemon.notice hostapd: phy0-ap1: AP-STA-CONNECTED b0:2a:43:8f:65:3c auth_alg=open
Sat Dec 30 18:43:21 2023 daemon.info hostapd: phy0-ap1: STA b0:2a:43:8f:65:3c WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:43:21 2023 daemon.notice hostapd: phy0-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:8f:65:3c
Sat Dec 30 18:44:32 2023 daemon.notice hostapd: phy0-ap1: AP-STA-DISCONNECTED b0:2a:43:8f:65:3c
Sat Dec 30 18:44:32 2023 kern.info kernel: [12448.734010] ath10k_pci 0000:00:00.0: mac flush vdev 1 drop 0 queues 0x2 ar->paused: 0x0  arvif->paused: 0x0
Sat Dec 30 18:44:32 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: authenticated
Sat Dec 30 18:44:32 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c IEEE 802.11: associated (aid 4)
Sat Dec 30 18:44:32 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED b0:2a:43:8f:65:3c auth_alg=open
Sat Dec 30 18:44:32 2023 daemon.info hostapd: phy1-ap1: STA b0:2a:43:8f:65:3c WPA: pairwise key handshake completed (RSN)
Sat Dec 30 18:44:32 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED b0:2a:43:8f:65:3c
Sat Dec 30 18:44:44 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED a4:cf:12:a5:9e:83

Does that AP have any devices it plays nice with?

The OP stated that the issue only exists with the IoT SSID. Although not explicitly stated, this does mean that there are devices on other SSIDs that are working properly with this AP.

So we can reasonably conclude that this is not an AP issue, but rather an SSID/network issue.