Hub not communicating via ethernet

Still running scheduled devices but it's not found on the network even when searching by MAC address. Have changed to a different switch port and no luck. It's a few years old. Any options other than to replace it?

Does your home router have an admin interface where you can go to see connected devices? If so, that's one way you might be able to tell if it's truly connected, then find its IP address (or if you have a DHCP reservation or static IP configured, I suppose you'd already know). Once you know that (or, again, if you already do), it sounds like the "regular" interface isn't working, so my suggestion would be to try the Diagnostic Tool to see if you can access it that way at all and use it to reboot (which may help this other problem) if so. You can see more in the article I linked to, but basically, the Diagnostic Tool can be accessed at port 8081.

If you can't do that at all, a last resort would be just pulling power, waiting at least a few seconds, then restoring power to force the hub to reboot. Perhaps it will reconnect after a reboot. If not, consider trying a different network cable or any other troubleshooting that seems reasonable based on what you might know about your home network (I'm assuming your switch is the same on your computer is connected to and you don't have separate LANs/vLANs, for example).

It's possible something died on the hub, too...just would want to rule out other things first!


One other thing that @bertabcd1234 did not mention, is just in case you had previously given your hub a static IP assignment, this can be reset back to DHCP with a small button on the underside of the hub.

Shown here, step #2: Network Setup - Hubitat Documentation


Another thing you can try, is http://hubitat.local. Just in case…

1 Like

Do you have any sort of vlan's set up?

There are some IP scanners that will report every device on your LAN by IP and MAC addresses.

On Windows I use Advanced IP scanner.
On Android, I use Network Scanner.

Well, interestingly enough it’s back on line at its old IP(at least for now). I did change out its network cable and I did try the suggestion below even though it didn’t switch back to DHCP. It appears that most likely that the network cable was probably the culprit.

I do have another question for you guys. I’ve thought about changing to the newest hub when it has gone on sale in the past. This one is around five years old. I’m thinking that the hardware changes in between are probably worth upgrading seeing how the hub cost is pretty reasonable.

Your thoughts and thanks for the replies. This is a great forum.


700 will give you some advantages over a c5 but the c5 is still very viable. You could also break up your HA and do z-wave and rm on one, and zigbee and wifi on the other and use hub mesh...


If yours is truly almost five years old, then you have a C-3 or a C-4 (these were first publicly avaiable in late January 2018, so not quite 5 years yet :slightly_smiling_face:). If yours is from Feburary 2019 or later, then it's probably a C-5, and it sounds like you definitely don't have a C-7 (July 2020 or so).

I mention this because the biggest functional change, as mentioned above, is the 700-series Z-Wave on the C-7. But the C-5 and later also run a more finely tuned OS that many users find better with memory management and long-term stability (so if you're one of the people who found scheduled reboots necessary on a C-3/C-4, probably not anymore). I think that upgrade is worth it; but if you already have a C-5, then the C-7 really only matters if you care about the new Z-Wave features (S2, topology map and other new network information, SmartStart, or just a 700-series radio). So, it may depend on exactly what hub you have and what you care about.


It's a C-5