I have just bought a C-8. The migration went well.
Rebuilt my C-7 for deployment on a restrictive network. Meaning, no DHCP, minimal ingress/egress, etc ,etc
I managed to work around the temporary DHCP need to initially change to a different network segment, Boy, that was fairly dumb. Why are you telling me that I can’t change from 10.10.1.10 to 10.10.2.11? What are you really protecting me from?
Netmask math? Did you guys even consider doing that? LOL. if I change to a /16, then your network silly-ness technically doesn’t apply., but it some how does.
OK, cool, got it on my new static address with DHCP turned on for a minute. Did the thing to change it from DHCP to static. “saved”, Reboot, cool. All good…. un plug and boot it up? Naaaaw that’s broken, BACK TO DHCP WE GO! WEEEEEE!
Can we fix these simple super easy networing issues? I’ve seen threads going several years and yet we still are forced to live in this DHCP world all the time because for some reason, someone thinks that’s the only answer to make things work right.
I can understand this is frustrating for you and other users with complex IP networks, but given that the vast majority of home networks (and thus Hubitat users) use DHCP, it’s not irrational for the staff to limit the amount of time spent quashing all possible bugs in the network stack related to static IP addressing.
I’m guessing the OP is referring to the button to enable static IP addressing in the hub UI’s network settings page, not the hardware button on the underside of the hub.
From your post it is hard to tell what your actual issue is. The only bug I know about is if using a net mask other then /24 it incorrectly assumes the IP range and won’t let you set it to certain IPs. It sounds like that is maybe the only real issue preventing you from doing what you want?
There is an endpoint posted on this forum somewhere that can be used to force any IP settings you want. Maybe someone can dig that up for you. I am on my phone so I don’t have easy access to my cheat sheet.
I searched. That link doesn’t allow you to change from a static IP ranges of say 10.0.1.x. to 10.0.20.x. The “webui precautions” are even pulled into the direct URL. so, no go there.
Even if you put up a dhcp server to get it on the vlan you need, then change to a static address with in that vlan, that works, until you need to hard cycle the box (think power outage). Then something in the boot process flips back to dhcp.
if I try to change it to anything other than .10, it will fail with this message. if I use the direct URL method, I get a plain text result with the same error
For some reason I can’t attach a screen shot.
IP address must belong to subnet 192.168.10.xxx or you will not be able to communicate with the hub
That is good to know and makes sense: you are not doing what was described in the post I linked to. You need to just hit that HTTP (GET) endpoint mentioned there, along with the URL parameters you need for your advanced setup. For example, just put this into your browser, replacing the placeholders with real values, and wait a second or two:
