The problem here is that most have a different approach to anything… a different drive, a different skill set, etc.
The background for my post was a blown power supply on my PC at 21:30 Wednesday night. I live in the country, got onto a 24/7 IT service, had a placement power supply in 30 minutes, and was up and running in 1 hour; all systems go an hour later.
This event shook me to the core, still feeling the stress today – entirely a mental thing – and rang home how vulnerable life is, given the technology (literally) creeping up on us.
thinking about this earlier in the week, I started a wiki (based on DokuWiki), documenting systems that go beyond the obvious; e.g. say a light switch.
It turned out that the task will cost me many weeks/months to get to a basic documentation.
Here a snapshot after a week of writing…
Apart from being the easiest and most efficient software I have used in decades (really), it revealed how much there is in systems, which cannot be “fixed” by the average trade, let alone my wife, if I am not around.
What I am thinking of is: two rPis, in a fault-tolerant failover set-up. If one dies, the other takes over; the dead one is replaced; happy to put a sort of boot/reconnect file on it, fire it up and its fixed. My wife can do this!
So even if one were to say OH only augments existing systems, let’s look at your rules, what gets triggered based on systems states and a mix thereof, and would hurt you in some way, if OH dies.
So, I’d say keep it coming guys… I am sure there is a serious solution forthcoming.