I tried assigning my Hubitat a class B address. It fought me every step of the way. Even if I tried DHCP reservation. It wouldn't stick.... I found a couple of addresses it would use...but still...
There’s a workaround for users that don’t use a class C subnet. Couple threads have discussed this, but here’s a helpful post:
1 Like
weird i have a 255.255.255.253 subnet mask (via dhcp) and my c8 pro works fine with it
ie
did you reboot all your switches and routers cameras and other devices after changing your subnet.. if not things will not work correctly..
255.255.255.253 is "illegal" in the sense that it isn't a mask. A mask wants all 1's to the left and all 0's to the right. 253 is 11111101 and is therefore not legitimate. 252 would be the correct closest value.
The 253 mask would work oddly, in fact it would work only for odd numbers. A 252 has 2 useable addresses, which would mean it would only work for one address, the even address.
3 Likes
Same, my IOT network is 10.11.37.0/25 and Hubitat has never given me any grief...
a /25 is half of a /24 and yields 126 usable IP addresses in a single subnet. That would be 10.11.37.1 through 10.11.37.126 As long as ALL your IOT devices are in that range, then everything can communicate with each other. But imagine adding another Hubitat and you put it at 10.11.37.130/25 (which covers the 10.11.37.129 through 10.11.37.254) -- the two hubitat's couldn't communicate. You'd need a router to pass the traffic between the two subnets. A common enough error is to add the 2nd Hub but use a /24. That would encompass 10.11.37.1 through 10.11.37.254 which therefore would be in the same subnet as the original Hub. The problem is that while the 2nd hub would send directly to the first, the first couldn't answer... unless there was a properly configured router between.
7 Likes
^^^^^
Yeah, this is all very true.
