Thanks for the reply. Doing both was my error, however even after changing the Hub settings to DHCP and reserving its IP in the router, out of the scope from my small reserved DHCP pool, I still see the messages, several times per second and repeats every 1-5 minutes.
My guess is the hub is doing this as to try to guarantee its connectivity, in the case of router DHCP IP lease expirations. However the hub should not be doing it at all, when its address is set to static in the hub settings. Many of my other network devices, cameras, NAS, TP-Link, Rpi never do this once they have a static IP set.
Would I be correct to interpret this as.... You reserved a DHCP address for the Hubitat which was not part of the pool of available DHCP addresses . (i.e. Out of the scope of your pool)
EDIT:
Upon further investigation of PFsense I discovered...
"On many routers (including pfSense, ASUSWRT, TP-Link, UniFi, etc.), you can create reservations anywhere inside the LAN subnet, even outside the pool
pfSense and some higher-end systems warn you, but still allow it.
Consumer routers may or may not warn you."
Has the warning message changed since setting the Hubitat to DHCP?
Why don't you reserve an address within the pool, and see if that resolves the warning message.
Thanks for replying and Yes my reserved Hub address is outside of the DHCP pool (.175-.198) Don't know where that info came from, but IIRC the DHCP pool is dynamic and PFSense doesn't allow you to set a static mapping within the DHCP pool, I know because I tried. I'm still seeing the warning in PFSense. I mean everything works fine, but I was curious what the hub was doing. I really think it's a strategy to be certain the hub always has connectivity, especially when the lease expires. As I said,out of many devices the C8P hub is the only one that acts like this. Not my 4 other Hubitats, nor my many other smart devices. And since setting the C8P to DHCP it's still the same.
This is what happens when I attemp to set a static IP within the DHCP pool
