They're called too-smart bulbs, now.

I assume the issue was the bulb was getting assigned by DHCP the same address that was supposed to be reserved for their PC, thus their wifi appearing not to work for their PC.

Haha not quite. Sounds like an interesting post though. I’ll have to look that one up. From all the help given to me here though it looks like my “static” ip is within dhcp range so my router is giving everyone else my key to the castle and therefore invalidating my key.

Then that’s likely your issue.

Your router occasionally gives out the ip of your pihole to someone else, and everything shuts the bed.

Try picking x.x.x.254 as the pihole address or x.x.x.2

Often routers won’t use either the top end or low end of the available addresses.

The machines on your network that are dhcp, do they go below 100? Do they go above 200?

You’re going to be guessing a little here.

What is your “net mask”

Are you on the same subnet as your router or are you on the subnet that your custom dhcp server is handing out? If your router is 192.168.1.1 and your ip is on the 192.168.2.x range, they aren't going to be able to communicate.

That sucks, it’s be good if you could disable DHCP overall and do it on the PiHole.

Haha yeah a big strong network person would be running proxmox or Ubuntu server or Debian or something and having a better time. I’m my defense, I’m both lazy and stupid so while (almost) everything is working, I’m keeping windows