Rule Machine and Basic Rules broken-Logs will not open

[JayInPtown]

I'm stumped. Basic rules and Rule Machine kick off OK at the 'certain time" event, but then hang up. Cant get the logs tab to open in OS or iOS.

Logs won't open at main page (left coloum), at app level or at device level. The iOS hangs up and the OS shows the domain numbers in the address bar and won't load logs.

Help?

[Sebastien]

The first thing I would do in this situation is reboot, but with the advanced option to re-build the database on reboot enabled.

[JayInPtown]

I did the reboot with data rebuild. Same results.

I can still control individual devices, but rules are not working, and I can’t make any of the logs load

[Sebastien]

Well, that’s odd then! I was hoping it would have only been a corrupted database…

Might I suggest that you share screenshots showing the issues? That might help us find clues…

[JayInPtown]

These images aren’t much help. They just show that pressing “logs” starts to load but hangs/sticks. iPhone and laptop the same.

I can load Events for devices.

UPDATE: i reverted to a previous version. Tested logs, didn’t work, re-updated to newest version again, logs and time-based rules don’t work.

I can trigger the unresponsive rules by using the “run actions” button, but that only commands the first line of commands (not the following pauses, dimming, more pausing, ect).

The issue seemed to begin on the last software update. Incidentally, it was the first update that I clicked the “create backup” option, so I have that old file.

[Sebastien]

Ok… Maybe someone in the @support_team can help… but I can’t think of anything else to try right now…

[bertabcd1234]

For just the Logs issue:

It looks like you're using the embedded browser in the mobile app to access the admin interface. Does it work if you try this in a "real" browser? Just open the IP address in any browser, use findmyhub.hubitat.com to discover the hub's IP address if you aren't sure (or use hubitat.local if mDNS works on your network and you haven't changed the mDNS name of your hub), or -- in your case -- you could also just hit the little Safari icon in the bottom right to do the same from where you are.

It should work either way, but this would at least rule out this particular possibility. Bonus points if you can also try on a desktop/laptop or other device to rule out that's just something odd with this one.

For the rest:

I see you've tried rebuilding your database. If that doesn't work (maybe try again just to be sure?), can you restore from a known-good backup? Your hub stores the last several, so you may have one available locally; otherwise, it's a good idea to download these from time to time, and it sounds like you have one, so trying one of those from before you had this problem might help. Hub Protect should also have some if you have that service, though again limited to the last few (age will depend on your frequency).

[JayInPtown]

After finding more similar stories in the community, I did a soft reset and then reboot from a week old archive. Everything is back. Logs and all. Thanks.