Hello,
I am experiencing a serious network connectivity issue with my Hubitat C-8 Pro running firmware 2.5.0.143.
The hub was previously functioning normally. I temporarily enabled Wi-Fi so I could move the hub around my house while troubleshooting Zigbee signal issues. During this process I switched between Wi-Fi and Ethernet several times. Then ethernet stop working. I went for the on on-line documentation and in there was said that i should disconect from the internet for the ethernet work.
After this, the hub became completely inaccessible.
Most Important Observation
Before the failure:
-
Disconnecting the Ethernet cable would immediately change the LED state.
-
The LED would alternate between blue and green, indicating loss of network connectivity.
-
Reconnecting Ethernet would restore solid green.
After the failure:
-
Disconnecting Ethernet causes no LED change whatsoever.
-
Reconnecting Ethernet causes no LED change whatsoever.
-
The LED remains solid green continuously, even when the Ethernet cable is physically disconnected.
This makes it appear that the hub is no longer detecting network interface state changes.
Current Symptoms
-
Hub boots normally.
-
LED sequence is blue for approximately one minute, then transitions to solid green.
-
Ethernet link negotiates correctly.
-
Router port LEDs show activity when the Ethernet cable is connected.
-
The hub never obtains a DHCP address.
-
The hub does not appear in DHCP client lists.
-
The hub does not appear in ARP tables.
-
The hub is not discovered by Find My Hub.
-
The hub does not advertise mDNS/Bonjour services.
-
The hub does not respond on any previously assigned addresses.
Network History
Before the failure:
-
Previous Ethernet IP ended in .10
-
Previous Wi-Fi IP ended in .11
The Hubitat cloud portal still shows the wi-fi ip as registered, but it is not shown as online.
Troubleshooting Already Performed
1. Multiple normal reboots
No change.
2. Network reset attempts using the bottom button
-
Approximately 7 seconds
-
Approximately 15 seconds
The hub rebooted but network functionality did not return.
3. Boot while holding the bottom button
-
Hub entered a solid red LED state.
-
Remained solid red for more than two minutes.
-
Releasing the button did not restore network access.
4. Ethernet testing
-
Multiple Ethernet cables tested.
-
Multiple switch/router ports tested.
-
Verified Ethernet link activity on router ports.
5. Direct Ethernet connection between Hubitat and Mac
I connected the Hubitat directly to a Mac using Ethernet with no router involved.
Results:
-
The Mac Ethernet interface became active and self-assigned a 169.254.x.x address.
-
Physical Ethernet link was successfully established.
However:
-
Hubitat did not request DHCP.
-
Hubitat did not appear in ARP.
-
Hubitat did not advertise mDNS services.
-
Hubitat did not generate any visible network traffic.
Commands Executed
ARP inspection
arp -a
No Hubitat entry was found.
MAC lookup
arp -a | grep
Returned no results.
Bonjour / mDNS discovery
dns-sd -B _http._tcp
Only my NAS appeared. Hubitat never appeared.
Packet capture
sudo tcpdump -i en0 arp
Captured only traffic generated by the Mac itself.
No ARP requests, announcements, or network traffic were observed from the Hubitat device.
Additional Observation
When directly connected to a Mac via Ethernet, the hub establishes a physical Ethernet link successfully, but never transmits a single ARP packet.
Packet captures confirm that no traffic is generated by the Hubitat device despite the Ethernet link being active.
Related Community Discussion
I found another community report describing network instability and Wi-Fi/Ethernet issues on a C-8 Pro after network reconfiguration.
However, my case appears more severe because:
-
The hub no longer emits ARP traffic.
-
The hub no longer appears in ARP tables.
-
The hub no longer advertises mDNS services.
-
The status LED no longer reacts to Ethernet link loss.
Additional Checks
-
Ping to the previous Ethernet address fails.
-
Ping to the previous Wi-Fi address fails.
-
The router does not show the Hubitat device anywhere, even without an IP assignment.
-
Find My Hub cannot discover the device.
-
The Diagnostic Tool cannot be reached because no IP address appears to exist.
Current Conclusion
The hub appears to boot successfully, but the networking subsystem does not appear to initialize or transmit any traffic.
Questions
-
What does the solid red LED state mean when booting while holding the button?
-
Is there a recovery procedure available when the hub has no discoverable IP address?
-
Are there any known issues involving switching between Wi-Fi and Ethernet on firmware 2.5.0.143?
-
Is there any method to access recovery or diagnostic functions without network connectivity?
-
Do these symptoms suggest a software/network stack failure or a hardware fault?
Before proceeding with any reset or recovery action that could affect the current configuration, I would like to exhaust all possible troubleshooting and recovery options.
I recently went through a failed migration from a C-7 to this C-8 Pro, which resulted in significant time spent rebuilding and re-pairing a large portion of my Z-Wave network. I am also in the process of rebuilding my Zigbee network. Because of the amount of work already invested in restoring the system, I would very much like to rule out every possible recovery path before performing any reset that could potentially lead to additional rebuilding or data loss.
Thank you for any guidance. Hopping to hear from the support team @support_team
Best regards,
Marcelo Borja
Update - Issue Resolved
I wanted to post an update in case this helps someone else in the future.
After posting here, I received a private message from a Hubitat staff member with some additional troubleshooting suggestions.
One of the recommendations was to perform a Network Reset while the hub was NOT connected to Ethernet.
This turned out to be the key.
What I did:
-
Disconnected the Ethernet cable from the C-8 Pro.
-
Performed a Network Reset using the button on the bottom of the hub (hold for 7+ seconds).
-
Waited for the hub to reboot.
-
The hub entered the Wi-Fi provisioning mode and began broadcasting the temporary SSID: “MyNewHubitat”
-
After connecting to that network, the hub reset its networking configuration and returned to a normal state.
-
Once complete, I reconnected Ethernet and the hub became reachable again.
For reference, before this procedure:
-
The hub would boot normally (blue LED -> green LED).
-
Ethernet link was active.
-
The hub would not obtain a DHCP address.
-
The hub would not appear in ARP tables.
-
Find My Hub could not discover it.
-
The hub did not advertise mDNS services.
-
Even when directly connected to a Mac, the hub generated no visible network traffic.
One particularly confusing symptom was that unplugging the Ethernet cable no longer changed the LED status. Previously, removing Ethernet would cause the LED to indicate a network issue, but after the problem occurred the LED remained solid green even with no Ethernet cable connected.
Performing the Network Reset without Ethernet attached appears to have completely reset the networking subsystem and restored normal operation.
Hopefully this helps someone else who encounters a similar issue.
Thanks to everyone who offered suggestions, and especially to Hubitat staff for pointing me in the right direction.