I have a C8 hub that keeps doing the Blue Light Special....
Many times when it boots, it goes to the Blue Light. Sometimes it's discoverable by the findmyhub site, sometimes not.
Sometimes when it can be found, it can be pinged, but not even the diagnostic port reponds.
I have to unplug/plug in many times to finally get it to boot properly.
Yesterday I upgraded to 2.3.9.166, when it rebooted, it came back to the blue light. Waited over an hour for it to complete the upgrade. I had to unplug/plug again about 6 times, waiting 30 minutes between each cycle, before the upgrade finally completed.
There is a pecularity around that setting that switching it from one to the other sometimes solves speed and connectivity issues. As for booting to a blue LED, normally that is some sort of database corruption - might try doing a reboot with database rebuild.
That's a good question, and a strange one to say the least. If you need help figuring out what might be wrong, please send me a PM along with your hub id. I'd be happy to take a look at the engineering logs for any clues.
Via the network cable to a switch. The Internet is Starlink, which works great.
Why would these things be dependant upon an Internet connection to boot properly anyways? I thought the idea of these things was to be cloud independant.
I think in general they don't need the internet. If memory serves me right there are only a few occasions where internet is needed. The two topics that come to mind are to do upgrades an for NTP occasionally.
They aren't. Outside of NTP and Updates as @mavrrick58 states. (neither are required for actual booting only being set) I am of the opinion you have some database corruption which would explain the improper booting and getting the blue light (platform not loading). I would also as a test swap out your power supply to a new wall wart to see if that helps things. Bad power supplies with voltage fluctuations can also cause symptoms you describe. Most corruption is caused by dirty shutdowns (where power is just cut) but as I said, power fluctuations can cause it too... You can go to yourhubip:8081 and do a soft reset then restore when prompted. If possible download your current database to your pc (which will clean it) and then upload that one after the soft reset. Another thing is to make sure you have a DHCP reservation in your router, then using a toothpick or paper clip, press the network reset button on the bottom of the hub for 7 seconds. (It will be the only round hole out of all the square ones)
I power cycled the hub again, and it came back up. I downloaded a backup and did s soft reset. Now it won't boot again. I see it in FindMyHubitat, but it won't connect to the diagnostic port.
I've power cycled 2 more times and waited at least 10 minutes between each cycle, and it's not coming back.
I'm using the Hubitat provided supply. Do I need to ask Hubitat for a new PS?
Put a DHCP reservation in your router. Likely it changed ip's. Then press and hold the network reset button on the bottom of the hub with a toothpick or paperclip for 7 seconds. (It will be the only round hole out of all the square ones). This will reset the network settings. Then go to the ip you set in your router.
Not really. As a network engineer i find it confusing and need to make sure which way people have things.
That said, glad it's up. I would also for giggles try a different power block for your hub to ensure low voltage or power fluctuations within the power supply aren't affecting things (which can and does happen) If you go POE, don't use a cheap poe splitter either. That causes radio issues. Once your database is restored, shut down the hub and unplug for one minute. This will ensure the radios are cleared... Hopefully when all is said and done your stuff works correctly,.
