Please provide your hub model (C7, C8, etc.) and its platform version from Settings>Hub Details.
Had the C8 for couple of years = From go.hubitat.com - says the device is uptodate in firmware - so it sees it (Firefox run). Upon boot - LED goes from Blue to Green. Router says the device is at 192.168.0.55 - has been all the time. Browsers (Firefox, Chrome, Safari) all say - unreachable. Enfored http without the https: - same results. Do I have a dead C8?
You may need to do a soft reset and restore from a backup (make sure you have backups available first). Hopefully you have the automatic backups enabled, which it should be unless you turned it off.
I was about to get the iOS diagnostic tool to find and access the C8. I will make a backup and then do a soft reset. Thanks for the suggestion.
Well did soft reset and went to "connect to the hub" on the iOS app - I get a Safarri page - that says : So now to restore from previous - I get a file on iOS - but nowhere to open it. UGH.
Does it respond to ping? You may have a duplicate IP address. If you have a Windows, Mac or Linux machine on the same network (probably 192.168.0.0/24), open a command or terminal window, do the ping test then immediately after do an "arp -a". Find the entry for 192.168.0.55. Does the MAC address match the one printed on the bottom of your hub? Here's an example on windows using my hub whose address is 10.0.0.11:
If you aren't getting a response to ping, you should still try the ARP test to see if the hub (or some other device) is responding to ARP. If its the hub, then you have a hub issue, otherwise you most likely have a network issue
Is your hub connected by ethernet cable, or are you using a W-iFi connection?
If you are using a Wi-Fi connection, that will no longer work after pressing the reset button. You will have to add the Hub back to your Wi-Fi network manually. Use your phone to search for a Wi-Fi network (SSID) called my newhubitat to confirm this.
How did you perform the soft reset if your hub is not accessible?
For diagnostic purposes, it might be easier to connect the Hub by cable and search for it again on your network.
Good idea - Thanks. on my Mac - ran Terminal - arp -a
The MAC address on the bottom of the Hub does not match ANY of the addresses that are displayed. The Hub is Ethernet connected directly to the router. I am going to reboot the router.
Router says it is there:
on TP Link wifi 6 router - recent - Says it is Ethernet connected.
Habitat
34-E1-D1-81-86-C2
192.168.0.55
i am going to reboot all the devices.
Thanks for this pointer.
Powered down everything (Hub, Router, IP modem, computer)
Modem - Internet running with great speed (SpeedTest)
Hub - Green light - Ethernet connected
Router - Still shows the Hub at its Mac address and IP address 192.168.0.55
No other device has the same Mac Address
Computer - Terminal: arp -a does not show any 102.168.0.55 and does not show any device with the Hub Mac address.
Agree. That may be a clue to your problem I think. The fact that your hub is on a different network is interesting. What is the IP address of your Mac btw? Also wondering if you can reach the diagnostic page on port 8081.
The URL to the HUB diagnostic tool - http://192.168.0.55:8081/ - does not connect.
Mac local IP address: 192.168.0.67 - not connected via Ethernet to Router - but WiFi connected to router - 192.168.0.1
Sounds like maybe your computer or whatever device you are using is firewalled off from reaching your hub. Its some sort of local networking problem, it is going to be very difficult for anyone to help with that.
Something isn't computing here. The hub is responding to ping, your Mac appears to be on the same network, yet the ARP table on your MAC doesn't contain the hub's MAC address. Either way, this looks Hub related to me. For some reason, no UI's are up. If this were my case, I'd take my laptop and connect its ethernet port directly to the hub using a crossover cable, static address it at 192.168.0.10/24 with no gateway then attempt to browse over to the hub at 192.168.0.55 as a final check.
The hub would not be able to get an IP if you connect directly to it, no DHCP. Would need to figure out what IP it assigns itself.
Also if the LED is green, it would be extremely rare for the diagnostic tool to not be running. As in, I donโt ever recall a case of that happening. So thatโs why it sounds like a local issue to me.
You need to confirm that the device you are pinging is the Hubitat and not something else. Does the ping stop responding when you unplug the Ethernet cable from the hub?
If this test confirms the hub is on-line, using that address, then you should be able to connect to it at that address. Since it is unclear about your network layout, don't try to connect with any other device, other than the same Mac which was able to ping the hub.
When connecting, enter http:// 192.168.0.55. If you don't specify http:, and only enter the IP, most browsers will assume https:, which will fail to connect. Also some browsers will refuse to connect to non https connections, but should give you a warning about why, so watch for these warnings when trying to connect.