Hi @David-TP

1) I receive mesaages from HomeKit several times a day (~5 times) that nor the AppleTV nor the HomePod mini are connected to the Wifi. So they will will drop off from the Wifi network many times per day.

2) Will send detailed logs via the support-ticket

3) Have not connected the devices to the IOT network yet, but the IOT network only support 2.4GHz clients so bandwidth is limited.

  @David-TP 

I have the same problem. Clients are dropping randomly multiple times in an hour and then reconnects in a few minutes. 

75pro, upgraded to latest firmware. 

Regards

Edmond 

Same here on the XE75 Pro, devices just keep dropping, tried all the suggestions and multiple beta firmwares but devices drop upto 20 times a day. 

  @David-TP   I'm having this exact problem with my XE75 mesh wifi network.  Did the senior engineers ever come up with a solution for this?  I would be nice if solutions are posted if problems are resolved for the OP.

  @AirMax2023 I've had a similar issue and for me specifically most of my Apple Homekit devices

  @phillykeepiv exactly the same for me, rendering this system practically useless.   Most of my IoT devices are offline, my alarm notifies 4-5 an hour that it has disconnected and reconnect.   I've tried everything, mapping to 2.4Ghz, using IoT Network, turning off Beamforming and Fast Roaming and nothing makes a difference.   I've tried technical support but they have been unable to help so I've not got a network that is grinding to a hault, multiple disconnections per day and no way to resolve.   It's helpful to know I'm not alone though.   I'm thinking of boxing the whole lot up and returning.   I would rather however get to the root of the problem.

  @AirMax2023 I now am having a similar issue with possibly a different cause. My DECO mesh has been working fine for about 2 months and nothing has been changed settings wise to the deco's. Then just today all of a sudden my Main Deco unit (XE75 Pro) started dropping the node decos (another XE75 pro and a X50 Outdoor) to where they would show as disconnected. That happened several times until I rebooted the Main deco. After reboot they re-appeared like the network went back to normal but I was wrong. The node decos did come back to being sho9wn in the network but the Main deco reports only 1 connected device and the nodes show 0 devices. I can't recall where my device count was at before this started but I do know before moving here I was over 100 devices. I don't think I have reconnected that many devices yet since my move a couple months ago but I'm sure heading that direction, its infact one of the reasons I switched to the deco unit because of the sale statement of being able to support over 100 smart devices. Without going too deep into the logs yet it seems like it can't assign any IPs constantly reporting the ip it wants to assign a device as already in use therefore in "conflict" and it is doing that for every device until eventually it craps out again and puts everything back to square one,cycle repeat.

With making no setting changes or topology changes to the network since install I am at a loss of what could have happened. The ONLY thing that was done around the client dump was adding a new smart backlighting to a tv in my house.

If anyone has insight or a possible direction to go in I would be beyond appreciative. I work from home and I won't be able to handle this happening many times per day. :(

Snippet of one of the logs from the deco listed here:

Tue Apr 30 20:48:39 2024 daemon.err udhcpd[15808]: find_free_or_expired_nip

Tue Apr 30 20:48:39 2024 daemon.err udhcpd[15808]: checked a node ip same

Tue Apr 30 20:48:39 2024 daemon.err udhcpd[15808]: ip conflict, find a new ip: 192.168.68.58, ready to arp check

Tue Apr 30 20:48:39 2024 daemon.err udhcpd[15808]: send arp packet:192.168.68.58

Tue Apr 30 20:48:39 2024 daemon.err udhcpd[15808]: checked a ip conflict node:192.168.68.58

Tue Apr 30 20:48:39 2024 daemon.err udhcpd[15808]: find_free_or_expired_nip

Tue Apr 30 20:48:39 2024 daemon.err udhcpd[15808]: checked a node ip same

Edit* couple things extra to note: Both nodes are connected via ethernet backhaul. The main unit is behind an Arriss s33 docsis 3.1 modem (its modem only) So the Main XE75 pro is the only thing setup as dhcp hub. The one client that the app shows as the only connected client, is a smart light switch that is installed in the same soom as the Arriss and the Deco (comm closet under the staircase)

  @Superdeleted 

Hello,

It definitely sounds like your DHCP server has ran out of IP addresses?  I had an issue where a faulty device would request an IP address from the DHCP server and then be allocated that IP address and then request another and another IP address until all the IP addresses were used up.  As soon as I identified the faulty device and removed it, then everything eventually returned back to normal?  Maybe you are seeing the same issue?

Good luck

  @Fl1nst0ne thanks for your input but I don't believe so as this all started happening without any new devices being added to the network. I'll also add after going back to look at some of the logs again, that whatever issue I was having that day righted itself but the dropped clients is still in full effect and my logs appear to be identical the the original posters. With devices not being found in the arp table and being disconnected after counter 2.

Also I have this error spammed all over in the logs:

apsd_check_eth_has_neigh:1432: Error: can't find ifname[eth1.591] in eth_ifname

but I don't know what it means. I did a search in google though and it seems to pull up lots of users reports of it in troubleshooting so I guess I have some reading to do.