I wouldn't use that classification. If the "hassle" is huge enough for any given user, they can throw enough money at it to get some type of solution working.
Our (my) problem is we (I) want "mission critical" reliability and functionality at a hobbyist price point and consumer "set-and-forget" deployment.
Interesting but way too complex.
My two approaches at the moment are:
When the UPS is supplying, measure the Hub current draw. I know the C7 power down is about 60 ma. If the hub current is below 60 ma, shut off the UPS output until mains return.
Assume some timing related operation. (would be able to be disabled). After loss of power for xxx minutes the UPS output would be shut off, to return on resumption of mains.
Both have drawbacks.
You could not run more than one hub (probably). Internal circuitry is more complex (but doable).
A minimum UPS hold up time would have to be predefined. Unfortunately this depends on the battery capacity ( a variable).
As it turns out, My wife and I live on a 56-acre island in a lake, in rural Maine. You can drive onto the island but t's about 2 miles down a private road that my only neighbor and I maintain. He's not at all technology-savvy, so not very helpful for restarting things. It was our vacation home before we moved here full time, 500 miles from our then home, so I've had to deal with a bit of "how to access and reset stuff", in years past. Back then I used an ISY-994 and also Homeseer on a RPi (the ISY was much more reliable than Homeseer, but not more reliable than my HE hubs, which have been rock solid). Anyway...
With Hubitat, once you restore power it just comes back online. To verify that before writing this, I shut down one of my hubs remotely and then went about the morning doing chores, then pulled the plug on that device, and then restored power. Sure enough, it came right back online. So, it would seem to me that if you had a UPS that turned itself back on once the battery reached a certain level, and you had your router and HE hub plugged into that, you'd probably be in pretty good shape.
Agreed.
Make it so 
I don’t think the single hub per UPS is a drawback, I think it’s better for reliability.
I’m also thinking we should add a restore power delay timer to give the battery time to get above our minimum DoD, before restoring hub power.
The major downside to not including a Zigbee radio is the lack of visibility of SoC. So if we have multiple power outages over a short period of time, the hub won’t know how much runtime it has available.
My HE hub is powered by a 32000 mAh power bank. If grid power is lost, this is one of the few pass through power banks that continue supplying power during the transfer, averting a corrupted database.
I fully expect the power bank to keep the hub powered for 4-5 days.
The major issue with using a power bank, is the constant charging to 100% will kill the batteries after roughly a year. Assuming they are LiOn and not LFP.
Huh, my HE loses power somewhat often when I mess around in my rack putting in new gear or redoing cables or whatnot. I didn't realize there was any risk in just unplugging it..
Yep, database corruption leading to a soft reset and restore from backup is a very common outcome, ask me how I know….
So here is the scenero I'm trying to find a simple solution for:
Now at this point "hopefully" user had written a rule that has shutdown the hub.
Tbh, the only way I see us meeting our goals without a Zigbee module as the brains, is with a microcontroller.
Arduino Nano boards are about $5 AUD, as are ESP32’s, but considering a Zigbee board is double the price and offers direct integration to the hub, it’s looking like the better option.
Ah, compromise, it’s so much fun! 
Why not try this:
Seems the only real challenge is finding a UPS that will turn itself on when recharged, and not require a manual restart.
And the only thing I'd add/modify to this is -
when you pull a new HE out of the box the start up instructions, either printed or guided, explain how to set this up and what BUILT-IN RULE/FEATURE to use.
This should not be something new users have to discover from a bad experience down the road.
If the database or any other software aspect of HE has the potential to be corrupted by a power loss (or a pulled plug) then the prophylactic protection to avert this SHOULD BE FULLY EXPLAINED and encouraged.
I only somewhat agree with this. PC's, Laptops, raid's, servers do not have this warning anywhere yet when you have bad power, bad writes, or even a jarring of a system with a mechanical drive in it is not warned against or even talked about until the corruption or even hard drive failure occurs. I mean at what point to we stop hand holding or warning people against something that should be common sense. EG. Please don't put this toaster underwater while plugged in. Sincerely yours, the manufacturer.
How about if the power bank is connected to a smart outlet of some variety with an RM rule that toggles the power so that it's not constantly charging?
Just do a search on "Warning Label Lawsuits" every year 100s of cases of "I wasn't warned" are out there.
I was being slightly hyperbolic but my statements about computers, raids, etc still stands. No warnings for corruption.
Our USB UPS already does this to a limited extent.
That could help for sure. It’s just hard to say how much.
The reason the UPS I built for folks uses the 80/20 rule is because this ensures the batteries run in their sweet spot for longevity.
It’s not quite true. Have you been in a PC bios lately and looked at Drive cache settings? Heck even my Synolgy NAS’s have warnings in the drive cache settings because if data is in ram and not yet written to disk, it will be lost if there is a power failure.
My HP servers raid controller actually has a battery backup for the write cache to prevent raid corruption in the event of an unexpected power outage.
I get what you're saying...and as long as "HA is just a hobby* it doesn't and won't matter.
There are a whole HEAP of things that have evolved beyond-the-mindfullness we all were required to have in order to keep technologically slick stuff working.... say, hummm. ...as far back as 1985...nah, let's pull it up to 1995 for the younger folk in here.
Apple, for one, carved a HUGE niche outta the mountain of "oh-but-you-gotta-remember-to-do-this" that existed in computing and consumer electronics.
We can nay say the hand holding all we want, this stuff is some people's hobby....but stuff is not Everyday Consumer Consumable Electronics until A LOT of the preventable hassles are ironed out of products. Apple proved this over and over.
Download the Hubitat app
