I tried a firmware update from the normal interface. That got stuck. I left it for at least an hour, then gave it a power cycle.
I looked through various posts, did the "find my hub" which worked. It then also offered to do a firmware update, which I chose to do. That got stuck too.
Now I can do power cycles (waiting more than 30 s), try diagnostic pages, but all to no avail. I can't find any further options in the help. Are there any?
Is there some special sequence to reset to factory original firmware?
I do get a green light (after first being blue). In my router I can see the IP address pop up in the wired list, but it does disappear at times, so perhaps it's not stable, perhaps this is a quirk of the router.
Do not know if this is the issue. I had a similar problem yesterday. I could ping the Hub from my router and when calling from my Firefox browser, I would see a message in bottom left showing that it was actually talking to hub. However nothing happened.
For me, it turned out to be the wifi Mesh mode my Hubitat was (via ethernet cable) connected to had a highly degraded link to the main mesh. Therefore, comms were there but too slow to successfully load the script.
For this, the fix was to reboot the Mesh node. It could also be other issues.
If you can't solve today, contact support or link the message stream to bobbyD (Hubitat support).
Dave
Also:
I also had a similar problem back in November (before I updated to a Mesh router system). I had too many wifi devices and the router was automatically dropping some links. Turns out that many older routers have issues with too many devices (too many devices being 25 or so). You can check this on the internet for your specific router.
My network consists of a router for internet connection and wireless Ethernet, and a switch for the fixed connections, which then funnel through the router of course.
I have the hubitat connected to the fixed Ethernet and have tried "findmyhub" on both a wired and wirelessly connected PC. Neither of them can now even find the hub.
It still shows up in the router's DHCP list, so I know that part works, it is not completely dead.
Given that I had no problems with connection before the firmware debacle, and the fact that my network is not that complex, I am inclined to think the network is not the issue. @bobbyD have you got any other CPR for my dead hubitat?
I've deleted the old DHCP entry and created a DHCP reservation. Once reconnecting Hubitat it showed up with the new IP in the router interface. The light on Hubitat still goes green. But I can't ping or find it in findmyhub.
Ok, this is weird, I tried findmyhub with MAC as the search term. It finds the hub, but on the old IP address. I don't understand how this can happen, but perhaps it means something to someone with deeper knowledge.
Being on the DHCP list does not mean the device is connected to the router. That only means that if it connects, it has an IP address reserved. On my ASUS Router, it would be on the Client List from the Router's top-level status page (see below).
I have seen this. It is due to switch back/forth from wired to wifi (I believe the wired and wifi interface have different MAC addresses that are now loaded). Review your HUBITAT settings.
Go to Hubitat - Setting - Network Setup - Switch to Static IP. You will see the note below. This may help.
"If static IP information turns out to be incorrect, and hub's web interface is no longer accessible, please reset it back to DHCP and reboot by clicking and holding the reset button for 7 seconds or more."
When the device is not connected to the router it disappears from the "status" list. Then when I connect it shows up. And when I assigned another IP address to the MAC address that IP address only showed when I connected the hub. So to me that indicates that the DHCP protocol did assign an IP address to the ethernet port of the hubitat. But it appears that anything at a higher level is dead. It appears to me that a firmware update doesn't touch the DHCP layer, but that other software was corrupted and now I've got a doorstop. Except it's not even heavy enough for that.
I can't go to my hubitat interface, so I can't set a static IP address. I can't do anything with it really, unless someone has a suggestion for recovery beyond what I posted.
That is a router problem. Probably too many devices (again I have seen this). If Hubitat were to do an auto-router-reconnect on a ping failure, it would only temporarily fix the issue - but it would only be a kluge.
That's likely because the old IP address is cached. Regarding the problem you are having, it sounds like you may have assigned 2 devices to the same IP address. Also, worth trying to reset the hub's network, if you didn't already. Locate the physical (hidden) button on the hub and press/hold for 10 seconds: Network Setup | Hubitat Documentation
Hi guys, thanks again for your help. I wasn't able to work on it for a while but today I made progress. Just in case it helps someone else, here is what I did:
Connect hubitat point to point to a PC and run a DHCP server on the PC (Open DHCP).
Connect to hubitat via the web interface. It was unhappy about the database and wanted a soft reset.
Give it a fixed IP address, so I always know the IP and don't have to worry about the router playing up or something like that.
So far so good, at least the hub is not dead.
However, when I connect the hub back to the network, I lose communications, can't ping, can't get the website etc. But if I put a dumb switch between the hub and the main switch I can get comms no problem. What is going on?
If I keep ping running, I get a very occasional response when connected directly to my main switch. No chance with the web interface.
Final update, all is working again.
I did a factory reset on the main switch. I bought it second hand and I don't think I ever got onto the management port, it wasn't active on my subnet. After reset I could get onto the management side but of course all the settings were default, so I don't know if some setting may have influenced previous behaviour. It must have been a setting that then only conflicted once the hubitat firmware was updated.
This usually would happen if Jumbo Frames is enabled on the network. If a JF packet hits the port it is known to take the ethernet down on the hub. A dumb switch will usually drop JF packets so would fix the issue. Did you by chance recently set up anything with JF on your LAN?
Thanks for the tip, I have now made sure jumbo frames are turned off.
The short summary of events is:
Firmware update on hubitat. Comms lost.
Ethernet switch reset to factory defaults. Comms back.
No other new devices have been added immediately before or between those events.
The only reason I can think of is that the new firmware included some networking feature(s) that clashed with the old switch settings. But what features they might be I have no idea.
