Hub registered and PIN entered. Multiple failures on firmware download. Makes it to 30-40% sometimes and won't even start others. Firewalls off. It's satellite internet so there is some latency but it shouldn't be this bad.
Now it won't go past 10%. Anyone have any ideas?
If you have not already, reach out to Hubitat Support - support@hubitat.com
Done. Just looking for things to try while I'm waiting. Thanks.
I just wanted to make sure - I'm not sure how often they check the forum vs. their e-mail. I don't have any suggestions - I have not had a problem but I'm on FIOS fiber . . .
Also, while you're waiting, don't go power cycling the hub if that's what you're doing. That forces the hub to rebuild the database which takes time and hub resources, so things work slower until that's finished. If you get impatient (not implying anything) and you pull the power while it's trying to rebuild the database, it can cause corruption.
You can try accessing the hub at http://[Your Hub IP]:8081
If you're able to access this, find the oldest platform version and ask the hub to restore. Give it time to restore and then if successful, go forward with the platform update from there.
I wouldn't expect a quick response today. Everyone needs a day off.
No older version. This is a fresh startup. I'll leave it at the "Register Hub" screen a while and try again.
True, but doesn't mean he gets one. If you don't get an answer right away, it's because you're in a massive queue.
It keeps getting to 30% or so and failing. I'm thinking it's a Hughesnet thing. Will try it on a friend's DSL tommorow.
1 Like
It could be, but then there could also be a database corruption that has resulted from the failure and it's not able to auto repair because there's nothing to roll back to. If you don't get a good result tomorrow, then support will be able to help you with a manual recovery.
If the DSL doesn't work then I'd bet good money that you are correct. Too many attempts may have scrambled its brain. I know it has scrambled mine. Thanks for your input.
1 Like
Gave up and unplugged it. Came back after dinner and changed LAN socket location and used phone instead of PC. It was one of the three things that solved it. Probably leaving it unplugged for a while. Regardless, it's working now.
2 Likes
Faulty LAN socket sounds like the most plausible to me. Phone vs PC wouldn't affect anything. Unplugged if at least 30 seconds is enough. Longer wouldn't change anything. Glad you got it working!
