C7 interfaces not working (automations still running)

🛎️ Get Help
1

Since a few weeks, after updating my C-7 to 2.3.1.137 the interfaces (app, web, diagnostic) stop working, all automation keeps working, just no dashboard ect.. After a hard reboot (unplugging power) the interfaces work again for about 24 hours.

Currently I've tried updating to 2.3.1.139 and a soft reset but the issue remains, any advise on where to look to further troubleshoot this?

Thanks

2

This sounds like one for support, tagging @bobbyD.

Best I can suggest is....Well not much.... :slight_smile: Hopefully the engineering logs might provide some insights for the boffins at HE HQ.

On a side note, pulling the power plug is not recommended from memory (pun intended...), bad things can happen, not always, but they can....

3

@alexander Do you have a static ip set on the hub or do you have a DHCP reservation?

Have you tried to do a soft reset?

Post a copy of your z-wave details page

Any devices excessively power reporting?

2 Likes
4

Pulling the plug isn't the best thing to do, I know, but there are no other options when you have no interface :frowning:
Btw, running with static IP (which works after plugpulling), soft reset done, no excessive reporting (no changes in config over the past year, the few which are reporting only report once per hour)..

Not sure how to post a copy of the z-wave page but if we are looking for ghosts, I have 2 in my small setup of 20 devices. This morning I've ordered a z-wave stick to be able to remove them.

5

Fair point... good that you know that an it's not your default go to...

1 Like
6

Connected via ethernet or WiFi?

If it is over ethernet, is ethernet set set to 100 mbps or Auto-negotiated? Whichever it is, switch to the other, reboot, and see if it makes difference.

Make sure that DHCP auto-reconnect is not disabled. 300s should be fine for most ethernet networks.

7

Ethernet was Fixed 100mbps , switching to "auto negotiated", reboot...
The results won't be in until tomorrow as it takes a while for the interfaces to stop working..

1 Like
8

Some added suggestions:

  • Device and App stat logs
    • Check for high % of total from any app or device.
      • Are any above 2%? Above 5%?
    • Check for high state sizes
    • Check for large event sizes
    • Do this again 4 hours or so later, and look for extreme growth in numbers.
  • ANY changes to your LAN configuration (at all) since before the issues started?
  • If the problem occurs again, (before rebooting) try entering the Diagnostic Tool address into your browser:
    • {Hub IP addr};8081
    • example: 192.168.99.197:8081
  • In the Diagnostic, you could also roll-back to the 2.3.0 version of the driver
    • Best if you are not using new features or you have not updated custom apps/drivers since starting 2.3.1.
9

Will keep an eye on the logs, but as nothing has changed over the past year (HUB and LAN) I doubt this will bring additional insights.. then again, haven't checked before :slight_smile:

Diagnostics is one of the interfaces which stops working, dead end there

10

Ghosts can cause similar lock ups because something is trying to reach them. I would also press the reset button on the hub to reset the network interface then use a DHCP reserveration. Once you are back in, do a softreset/restore to clean up any potential database corruption that you might have incurred from having to do dirty shutdown. I suspect it is the network interface but could be the ghosts.

11

When you say the hub's IP is static, is it configured that way on the hub or is it configured as reserved in the router's DHCP table? If the former, is the hub assigned an IP that is out of the DHCP range of your router? When the interface goes down can you still ping the hub's IP? If so, is it possible there is another device on your network with the same IP?

And don't forget @aaiyar's recommendation to set auto-reconnect to something other than disabled.

1 Like
12

24 hrs after change from static IP configured in network settings to DHCP and all interface still reachable, Not sure I understand why because the static IP was out of the DHCP scope in my network and no other devices are using the same IP.

Thanks for the help sofar and will keep you posted

1 Like
13

@gopher.ny We've seen this before. What's your take?

14

Most likely cause of described behavior is hub jumping to a different IP. The workaround is accessing it through http://hubitat.local/. But I see that the hub now changed to DHCP, and it's working (so far), so this bit of advise only applies so much.

The static IP configuration is between the hub and the router. Just setting an IP to a static value on the hub isn't usually enough. It may work for a while, but a router can get unhappy about it at any point.

Best way to reboot a hub with inaccessible interface that otherwise runs is via the hidden reboot button. Turn the hub over and use the point of a pen to press the small button just beneath the surface of the hub casing for at least 7 seconds . It will reboot and reconnect using DHCP.
Hub_DHCP_reset_button

2 Likes
15

The reboot button is well hidden, didn't know the hub had one :slight_smile:

16

More of a network reset than a reboot button.

1 Like
17

I've never needed it myself... But good to know it is there.... I do feel like I am doing a failed aptitude test with various shapes... Hmm... Perhaps I have some scars that need healing... :slight_smile:
Give me an obscure bit of code and support incident any day :wink: I will now remember to look for a circle amongst a forest of squares....