What color is the LED? Blue means the diag tool should be up, but platform is not.
Check your power supply or swap out for something else to verify.
The diag tool is also giving a 500 server error? I have never heard of that before.
Please try using an inCognito browser tab to rule out a browser cache problem.
Have you tried doing a network reset using the hidden button on the bottom? Hold for 7 seconds then let go, LED will blink then hub reboots. If you had a static IP set on the hub it might come back up with a different IP.
If you get back into the diag tool make note of the version of the hub platform and the diag tool (two separate version numbers).
It is pretty rare that hub will power up but the diag tool does not work, it is very hard to break the diag tool itself. But if the LED is off or you cannot get to the diag tool then there is no other path to recovery
Also, I am logging off for the night soon, but I will check back in the AM.
The Diagnostic Tool is independent of the platform itself, so an update isn't going to affect the Diagnostic Tool, even if the platform isn't running. I would first check the network if you are unable to reach the Diagnostic Tool. There could be something as simple as your router changing the ip address of your hub, or you are trying to connect to the hub from a different network (segment) that can make the Diagnostic Tool seem unreachable.
Do you mean all of your backups are saying it is corrupted?
You are doing a soft reset + logs purge from Diag Tool then loading a downloaded backup after it reboots?
Try these steps below. To revert to 2.3.7 it is in the "Advanced" menu.
For the debug disable endpoint, the main platform needs to be booted.
You can also try booting up fully without restoring from a backup, just to see if that works without issue. Then you can try to load a backup using the UI at Settings > Backup .
If you can get it working on 2.3.7 then you could try updating back to current 2.3.8.140
Might not be a bad idea to get the latest diag tool also:
Navigate to http://[Your Hub IP]/hub/cloud/updateDiagnosticTool , wait a few minutes (you will not see a progress report), and the latest Diagnostic Tool version will be downloaded if needed.
If you see the Corrupted Database message, it means that you can access the hub's interface. If that's the case, you don't need to try to reverse to 2.3.7. Just navigate to this end point in a browser:
yourHubIP*/hub/zwaveDebugDisable
Then reboot the hub from Settings.
Then update to the latest platform version and let us know if that fixes the problem.
Probably could also try updating to .140 from the diag tool using the Download Latest button (then Restore Previous) as well, not sure if that will help anything or not.
Followed all the above and still f***ing Corrupt Database.
I haven't updated to the new Diag Tool yet, so I'll try that, but I'm running out of options.
There's no way 3 previous backups can all be corrupted. Whatever this update is most recently has basically made my device unusable without completely starting from scratch.