I am setting up brand new C7 hub. I have address reservation of 192.168.1.20 and hub is found at this address. Hub is using DHCP server. I access the web interface and attempt register hub
I am presented with choices of using existing account or creating new one. I have tried both - using Hubitat account that I created earlier and creating new account from this page (including verification code). Either way these are hubitat accounts, not a Google login.
After providing account credentials I see a redirect page and return back to where I started - hub home page. My account shows no registered hubs.
My hub settings page advises me to register this hub, again.
Mobile app finds the hub and offers to claim it, but claim button click does nothing - can't even navigate away from this page.
I have gone over this cycle 20 times. I used Chrome and Edge. I did soft reset of the hub. Nothing helped - no error messages and no effect.
I have previously set up a different hub at different address and different account. So, this is not a first I am doing this, but it is the first time I see such quiet quitting.
Anybody else saw this? @support? Screenshots are available.
Yes. Press the network reset button on the bottom of the hub with a toothpick or paperclip for 7 seconds. This will only reset the network settings. Do a DHCP reservation on your Hub (do not set the static settings on your hub itself) then check dns again. If it still does not resolve, use override dns settings and put in 8.8.8.8, 1.1.1.1
Thank you! Resetting network settings with a toothpick did the trick.
This makes me wonder what was wrong to begin with. Initially hub had dynamic IP address, then I set up DHCP reservation and rebooted the hub. No network settings were changed for the hub itself. Web GUI was functioning without problems.
The most frustrating part of this experience is the lack of errors or warnings from Hubitat UI. Network errors cannot be that uncommon and a basic error message would go a long way.
That is strange only because when this situation happenes it's because at some point the hub was set to static on the hub itself and dns isn't set or it's set to static then set back to dhcp in the up and the network stack isn't cleared. Either way I'm glad you got it settled!
