Hub C5 local access not working (sort of)

🛎️ Get Help
21

Oh and BTW, the internal temp page does work (http://192.168.0.136/hub/advanced/internalTempCelsius) and gives me 41.0

Yes I did when I changed the cable, I used another port just in case.

No my other hub is at the cottage so no it's not on the same network nor are they talking to each other.

22

Well... I'm straight out of ideas. Maybe @thebearmay has something to try? Otherwise support may be your option.

23

Sorry I have no clue either (per usual haha)

Did you try accessing via HTTPS?

24

Actually I did not but after trying got the same results.

1 Like
25

Thanks for the ideas @brad5 !!!

26

Well it's looking more and more like a corrupted hub for some reason, when trying to access the main page or the diagnostics page from Firefox or any other browser I never tried with the hub, the tab for that page will have the correct title, so I looked at the source and found this...

<!DOCTYPE html><html lang=en><head><meta charset=utf-8><meta http-equiv=X-UA-Compatible content="IE=edge"><meta name=viewport content="width=device-width,initial-scale=1"><link rel=icon href=[/images/favicon.ico](view-source:http://192.168.0.136:8081/images/favicon.ico)><title>Hubitat Diagnostic Tool</title><link href=[/js/app.js](view-source:http://192.168.0.136:8081/js/app.js) rel=preload as=script><link href=[/js/chunk-vendors.js](view-source:http://192.168.0.136:8081/js/chunk-vendors.js) rel=preload as=script></head><body><noscript><strong>We're sorry but updatetool doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><div id=app></div><script src=[/js/chunk-vendors.js](view-source:http://192.168.0.136:8081/js/chunk-vendors.js)></script><script src=[/js/app.js](view-source:http://192.168.0.136:8081/js/app.js)></script></body></html>

So it is responding but tells me that javascript is not enabled???

But when I try it in Chrome, my regular browser, I get this...

<!doctype html>

New Tab body { background: #FFFFFF; margin: 0; } 
  #backgroundImage {
    border: none;
    height: 100%;
    pointer-events: none;
    position: fixed;
    top: 0;
    visibility: hidden;
    width: 100%;
  }

  [show-background-image] #backgroundImage {
    visibility: visible;
  }
</style>
27

I was going to say it sounds like the database or firmware is corrupted, As to recovery…if you can get to the restore previous version screen, it might be best to re-pull the firmware.

2 Likes
28

He hasn't been able to get to the diagnostics screen either... might be time for some secret decoder ring action with the guys from support.

29

Hopefully just the top level. Might try: http://hubIpAddress:8081/factory/recovery

1 Like
30

Just sent a message to support, hoping and crossing fingers!

31

Doesn't this zap his radios too?

1 Like
32

Need to go out for a few, I see if that might work but haven't seen it before, so....

33

Believe so. Here are my notes:
Reset Z-Wave & Zigbee radios, delete all data, blow everything away.

1 Like
34

It’s a “menu item” you have to hit confirm before it does anything, but more interested in if you can get to that level.. my development environment is down (old switch failed) or I’d push a little further on my side

1 Like
35

No nothing pops up on that link either.

36

definitely a @bobbyD or @gopher.ny level issue then…

4 Likes
37

Took the liberty to look it up... I see two C5 hubs under the email associated with the account, both respond to support tool requests, and neither appears to be empty, so they are not reset.
Don't reset any hubs just yet.

Since they respond, they got network access. If automations still work, radios are functional. And while there is no header info, responses above appear otherwise normal.

Can you try accessing hub UI from a different device?

2 Likes
38

Hi @gopher.ny well this morning everything seems to respond, I can get to the main menu, to the diagnostics page and all. Not sure if you changed anything but it works. I did do a "deleteDatabaseTraceFiles" command and reboot but this did not seem to have done anything, I got a response like this: deleted files: [], could not delete: []

So now that i'm in, is there anything I might want to check to find out what happened and something I should do to prevent it from happening again.

39

Which hub was acting up? Can you PM me its id? I can look for the clues (assuming there are any).

If anything, a reboot may have had some effect.

40

Sending now