My hub is several years old and is still working find, but the Hubitat portal is messed up. It cannot find my hub anymore, and using advanced find doesn't work either. When entering the MAC address, it comes up with the same wrong IP every time, which is currently in use by something else on the network.
I can connect to my hub only via browsing to it now. The App on ALL devices got dumb all of a sudden, and can't even log in to my account from within the app now. mDNS does not work, network scan does not work, and the devices can access the internet fine. I uninstalled/reinstalled the app on both phone and tablet.
The frustrating part is I can see in the address bar that the app is going to the wrong IP, but you cannot edit it. But after reinstalling app, now I cannot log into Hubitat account (except by using a browser).
The main problem with the portal not working is that I can no longer link the Hubitat and Alexa together.
Any ideas how to get the app working again? BTW, problem may have started after the last update, but not 100% sure.
I did that and was able to log in to my account again (from the apps). so thanks for that.
I will try again to give the hub a static IP address outside of the DHCP range. Why doesn't the portal link to the MAC address? This would seem like a far better way to manage devices than to link to something that can change and lock people out of their stuff.
The problem now is that if the device happens to grab a different IP, which obviously happens. Then the user is presented with a perpetual "Fetching data" trying to log into their account.
An improper device setting should not lock out the account (from the app). Instead, it would be better to present user with "There is a problem reaching your hub" with an opportunity to make the portal aware of the current facts.
As it is now, I was down for days trying to figure out what presented like a DNS issue on the router. The irony is, people may not need to log into the portal until they have a problem, and that's precisely when the portal will fail the login.
The solution is to setup a DHCP reservation on your router for your hub's MAC address. Alternatively, assign a static IP address to your hub that is outside of the range assigned by your router's DHCPd.
I did setup a static IP. which took a half dozen reboots before the portal and the device had the same IP at the same time. There is a trick to it that I eventually figured out,
I'm only trying to help... the solution is to not have defaults with a high chance of failure over time.
Anyway, I am good now and appreciate the help. I suggest this is a known "issue" and should be in the FAQ, titled, "App is stuck on fetching data"
