We have a second home with a small smart home setup running on a C8. Internet is via T-Mobile Home Internet.
We recently arrived to prepare the home for a winter stay. I added a couple of leak detectors with no issues, but during the process I noted devices all reporting excessive load on the hub. I initiated a reboot, which went well. Then I started a firmware update and went to bed. Woke up to things not working. Couldn’t log into the hub by any method, though findmy site seemed to see it.
My assumption was a DHCP mismatch, so I initiated a network reset. No joy. Rebooted the gateway and still no joy. Did a hub networking reset again and still couldn’t connect. Tried another gateway reset, and then tried another networking reset. The networking reset this time seemed to have no effect, with the blue light remaining on the entire time I was pushing the button.
It should be noted that the T-Mobile gateway is locked down hard, and DHCP reservations aren’t possible.
I’m at a loss. The C8 seems to be fully bricked. No communication possible at all.
That’s not good. Try a different power supply. If that doesn’t work, then submit a warranty claim at support.hubitat.com, if your hub is within the warranty period.
Unfortunately well outside warranty. After leaving it unpowered overnight, it seems to be responding properly to a networking reset, so I’m holding out a bit of hope. But still not showing on the network. Tried a different ethernet cable and getting ready to try a third. I’ve been burned by a bad cable off the shelf before.
I wish there was a hardware method of factory reset for the C8, but I wish more that T-Mobile would unlock the gateway so people who know what they are doing can do normal tasks. It’s just the best option here now without spending $3100 to have cable extended when fiber will be here in two years.
Plain old persistence has paid off, at least temporarily.
I turned off the wifi radios and unplugged all ethernet cables from the gateway except for the C8. Then I rebooted the gateway and did the networking reset on the C8. Then I could see the C8 on the list of clients connected to the gateway. But it kept dropping off as unconnected and then showing up with a different IP address.
I tried numerous times to login to the diagnostic tool, but It generally would fail. A few times it let me login, but was unresponsive. Each time I could see the C8 had disconnected or gotten a new IP address. I chased it around with numerous attempts to use the tool and finally got it to prompt me when I clicked on the option to rollback the firmware. I elected to return to .160, which it successfully accomplished and rebooted. It’s been stable for 15 minutes now.
I don’t know if there is a hardware issue with my C8 causing a sketchy ethernet connection, or if there is a bug in the .167 firmware. Maybe even a corrupt installation of the .167 firmware for whatever reason. But the hardware seems the likely culprit since my understanding is that the Diagnostic Tool is separate code that should have worked reliably.
Regardless, I don’t have the warm fuzzy feeling I’d like to have, especially considering this is a remote installation.
I can see I need to look at a solution for my Internet to allow reserved IP addresses to avoid complications. I had hoped my backup power system would mitigate that, but apparently not.
Thank you again for your responses. At the very least, explaining it helped me organize my thought process.
