Interesting

So the fiber for our internet got cut yesterday. It was out till evening and then again out today for several hours. While it was down everything was working with my hub except I could not open any apps. It just sat and tried to load but never did. As soon as the internet came back up it was fine. I noticed this a few months ago when I had another outage. Not sure why I can load logs, dashboards, and devices but no apps. :man_shrugging:t3:

I did reboot the hub once during the outage too but that made no difference.

In another thread it has become apparent that there is some confusion in what users define as "Apps", "Automations", and "Integrations".

Could you specify what you consider as "Apps" and give an example of which "Apps" didn't work?

That’s only true if the hub is on beta platform version 2.5.0 (for now at least).

2 Likes

The rules work, but you can't look at them.
Interesting. :slight_smile:
How about simulating it by unplugging the modem cable to the wifi router?
I've done this to see if certain stuff works offline.

edit: I just did this on my C8Pro, maybe -1 from latest firmware and it works.

It was interesting that when I simulated a water leak, the rules worked and shut off the water, and announced on the HomePod mini, but naturally I didn't get a Pushover notification. I did get an Apple Home notification.

Also the well pump ran and I should've gotten a verbal notification, like the leak sensor, but that rule didn't work. Perhaps not in mini's memory. Ran command from device page and it worked, so maybe it's there now. Hard to simulate.

Interesting. :slight_smile:

I agree, the new menu categories are only on the beta. (AFAIK).

The OP mentioned that his "apps" did not work when the internet was down. I mentioned the other thread, because it demonstrated that the term "app" could mean different things to different people.

I was hoping the OP would give examples of the "apps" that failed to work for him, to see if there was a possible explanation.

I agree it’s not 100% clear what OP’s seeing based solely on this description.

Some additional details (or screenshots) could probably help clarify a bit.

When it happens again I’ll do screen shots. Basically I could not open or create any new rule with Rule Machine or Basic Rules. Don’t recall trying to open anything in any other module. I know I did, and it also didn’t work, but I don’t recall which module I tried.

The apps page itself loaded though?

You might try simulating an outage by unplugging the ISP cable from your router (which could be significantly different than just unplugging the hub).

1 Like

I did that, anyway. See above. :slight_smile:

1 Like

Simply disconnect the net wan cable from your router and that will simulate a disconnect. (Well actually it will be disconnected). If you are on cellular with your phone and not local wifi then you will not be able to use the Hubitat app to get to your hub. Ensure that your phone is on wifi. Also from a PC go to your hub ip in a web browser to ensure you can see the hub on the local network. One thing I have found in my years of working on networks is that some crappy isp provided routers will block lan when wan is down. Just something to throw around in your noodle.

3 Likes

Just to determine the extent of the problem, were you able to open a device page and actually control that device. For example could you turn on a Zigbee or Z-Wave light from the device page?

I just disconnected the WAN cable to my router, and of course I could still open and edit rules created with rule machine as expected.

Try to unplug the WAN cable from your router as well, and see if you can duplicate the problem, or if you get the same results as the rest of us.

If things work with the cable disconnected, then there may have been other things going on that created your issues.

For example (grasping at straws) , if your DNS server were to have failed, it would make it look like the Internet was down, when in fact it wasn't. The multiple DNS requests may have brought your router to a crawl.

Locking conditions like this can be really hard to sort out because they can have complex interactions.

For potential example, you might have an app or other code installed on your hub that got in a weird state when the Internet went down--and it held a lock that the RM editor needed to open. Without a core dump to tell what was locked up, it can be hard to chase down.

And that would be a reason nobody else could replicate this. And why it might not be easily reproduced.