Hub going offline, even with weekly reboots

I've got C8s in two homes, one of which is rock solid, while the other seems to go offline frequently. I switch homes once per month and, nearly every time I'm in home #2 and get ready to return to home #1, I find I can't access home #1's hub. Both my router and the C8 are set to reboot weekly, and my router is reachable so, the issue is clearly with the C8. I don't typically access my hubs remotely unless I'm making some changes or when I'm about to leave for that home and want to "turn on" the house. So, I can't say for certain when that hub became unavailable. It could have been since it's last reboot Saturday night, or sometime in the weeks prior.

I realize this is a challenging issue to figure out and I don't expect anyone to have a crystal ball. But I am trying to figure out when it happens. Where can I look to see the hub's reboot history (obviously after I get back to home #1 and manually re-start the hub)? I'm hoping to narrow down at least which week the hub decided to go offline.

The SSID is reserved for both hubs? On the router preferably?

on the problem hub have you tried a reboot with rebuild database.. it is probably corrupt

A few thoughts, but first, what was the reason you decided to reboot the hub? That shouldn't be needed, and can result in connectivity issues, especially if your hub is running an older platform version. Speaking of updates, when you get to your other place, make sure to update the hub to the latest version.

Thanks, all, for the responses. I just returned to home #1 and manually rebooted the hub. Everything is back to normal now.

@tivomaniac - If you mean a reserved IP address, yes. I have reserved IPs for both hubs.

@kahn-hubitat - I have not, but I will. Wouldn't I see other issues with my hub if the database was corrupt. It's otherwise operating perfectly.

@bobbyD - so, I thought it was a generally-accepted good practice to reboot the hub on a regular basis to "clean out the cobwebs" so to speak. I'm using the "Rebooter" app to do that once per week. If I should NOT be doing that, please advise. Why would a reboot cause connectivity problems? I would have thought the exact opposite - that a reboot might resolve any connectivity issues that cropped up during regular usage.

I am disciplined about installing updates as they are released. There have been a couple since I left home #1 about six weeks ago, and I prefer not to do updates remotely so, I was likely 2-3 versions behind on this hub. I just now updated it to the latest. But again, prior to this, the hub was operating fine and, this drop out isn't happening consistently, just intermittently.