I had to work hard on cleaning up my router. Changed the lease times, set up an exclusion table, statically assigned multiple devices on DHCP reservation table (and on the individual device).
I probably should have done this a long time ago...but way too lazy.
One thing for sure - LFIX bulbs are not your friend...especially when you have a lot. I was experimenting with colored bulbs in a room (15 can lights in the ceiling). Too many IP addresses on a loaded network. I should have factored all the wifi devices into the equation. Stick with zigbee and zwave.
I was going to switch form 192 to 172 for a class B network (but really didn't want to go thru the pain).
He must have changed to a class A/B network and played around with his subnets...I would assume. That's an awful lot of IP addresses to have...assuming there are several dozen other devices.
You can actually change it through an endpoint... For a long time... Since 2.2.9
Restricted non-local access to the hub. Allows non-local subnet whitelisting by using /hub/allowSubnets endpoint, e.g. /hub/allowSubnets?123.123.123.0,124.124.124.0. Running endpoint without parameters displays currently whitelisted subnets.
Almost one week - NO ISSUES. Things seem to finally be working well. It was a messy network. Setting up a cleaner network with some VLAN and a few other chores seems to have helped. I am not sure why the hubs had such a tough time with the DHCP IP addresses though.
4 Hubitat hubs Rev C7 - purchased about 2-3 years ago (can't remember exact date). I had the same problem at that time and was using Homeseer. I tried to convert over with a single test hub at that time and had too many disconnect issues. Stuck with homeseer. I made the jump back because I liked the hardware - single small hub with all the zigbee/zwave built-in. My homeseer set up was running on a PC with 4 seperate znets (no native zigbee) and I didn't want to upgrade all the hardware. So I gave Hubitat another try.