I have been running my C8 hub flawlessly for over 6 months, it was an upgrade from a C5, which I had for several years.
I have never had any issues connecting to the hub to check for and apply updates.
However, after the last update, I am not able to connect to the hub, it just times out.
I have verified the IP address in my router and in the app to be the correct address, and it just never connects.
The Dashboard still works and I have tried everything in the massage boards to try to connect to the hub, but nothing works.
I've rebooted switch, router, hubitat, tried port 8081, etc, etc. Nothing allows me to connect to the hub. I have tried wifi and a LAN connection, and I have even tried pinging the IP address and it says nothing there.
I am out of options to try, is anyone else having this issue?
Yes, I held the button for over 7 seconds and the light blinks blue and green until returning to green.
When I try to connect from my app or a PC I get: We can’t connect to the server at hubitat.local., or Safari can't connect open the page because it couldn't connect to the server.
My Dashboard works fine however, and if I try to ping the IP address, it says there is no response.
This certainly a network issue..... if both router and my.hubitat shows the same IP... I would try setting a static local IP that hasn't been used before for the hub and do a hard reboot of the hub... pull the plug and wait a few seconds then plug it back in. Just curious if you subscribe to the hubitat remote admin... if so try to use that from my.hubitat and see if you can connect...
I set a new IP address for my PC to take the place of the IP address my hubitat was using. I rebooted the hubitat, and a new IP address was assigned to the hubitat with no luck. I can access the dashboard and use my devices, but any time I try to connect to the hub, it errors out. I get the message server is unavailable. I am also not able to ping the address. I do not have the remote admin feature.
I have never had an issue, but I am thinking the issue is with the device itself.
There is nothing on my network that would block connecting to the hubitat.
I would do that to prevent the hub from changing ip's and having things looking for it at an expected ip and it's changed because the lease ran out. Once you set a DHCP reservation and reboot the hub, go to my.hubitat.com and see if you can see your hub there
I think there might be a bigger issue at play here. Now, I am no longer able to connect to my receiver to play music over Airplay. I moved my hubitat and connected it directly to my router with the same result. I moved the receiver to wireless from ethernet and I still can no longer play music or connect to the receiver. When I get some time, I am going to test another router to see if the router is the issue. I am thinking the latest Orbi firmware might be the issue.
No one has asked or suggested trying to connect to the diagnostic tool yet???
Also did you try all this including the ping test?
A link to this post was provided in the post template in the Get Help section and the post is also pinned in this section.
I didn't think that was needed since he can use the dashboards and I'm pretty sure that uses the core software and not a standalone software like the diag is.
Well that is really weird..... I dont think its orbi either in this case.... but there is something very weird going on. You wouldnt happen to use linux cause you could nmap the IP and see what ports are open.
Yeah true if the dashboards work I think those get served from the same http server as the main platform, but who knows maybe the dashboards get served up by a different instance and the main platform http is crashing out for some reason (database problem?).
