First of all - I am very happy Hubitat user (even thought Hubitat is not perfect).
I am former X10/Insteon user (also was very happy) but when couple years ago
I permanently moved to Florida I started to look around how to automate my
apartment in Florida. There was/are many different hubs around but basically
all of them are Cloud based. For me Cloud based Home Automation is
ABSOLUTELY no go. Finally I came across Hubitat Elevation and this hub
immediately became my choice for automating my new Florida apartment.
Right now basically everything is already automated and I am running out
of new ideas what to automate next.
Yes, many of next topics was already discussed one or the other way
but let me summarized my experience and provide some thoughts.
Next are only an ideas.
As of now I moved all my automation to RM.
The reason is - neither of other applications 100% satisfied my
specific needs. This is very common and not unusual because every
application is written for somebodies specific needs. And needs for
every user/case is somewhat different. That is why there are many
slightly different applications covering almost the same use cases.
From other side - RM is very powerful universal application.
Many BIG thanks and respect for @bravenel for the RM existence!
So, RM itself is very power tool but the GUI is somewhat overcomplicated
with all these pull-down menus and dynamic pages. But now after reading
many related posts i have an idea what is behind this approach.
Correct me if I am wrong but it looks like everything could be
accomplished by using "custom actions".
One way to optimize GUI will be to start silently right away from
"custom actions" and then pic a "device" and so on.
I saw few posts where some sort of "RM Compiler" was discussed.
The idea was/is - to compile RM Rule into Custom Application.
I really hate Clouds but for this reason (compiling RM into Custom Ap)
one time Cloud interaction will be acceptable.
I am not a SW developer and I have no Idea how difficult it will be to
implement this but my good guess - it is definitely doable.
I think, the compiled RM Rule will be far more efficient vs. RM Rule "as is".
So, If this is doable it will be huge improvement for many (if not all)
ordinary HA enthusiasts and will open a gates for many people who
want to start HA but have no real solid programming skills.
Yes, RM is some sort of pseudo programming language but learning
simple IF-THEN-ELSE logic (some sort of idea behind IFTTT) is far less
complicated (I think) vs. learning whatever real programming language.
The Device Drivers "as is" is an Achilles Hill for the Hubitat and
other hubs. But I think, the creation of the Device Driver could be
(and should be) completely automated. I came across at least one
post/project where somebody attempted to accomplish some
sort of creation of Universal Driver. I don't know, what is a current
state of this project but looks like it did not materialized into something
very solid. Too bad.
So, why not to create some sort of automated Driver Creation Tool?
And I am sure, this could be achieved. How easy - is a question.
Again, in this case Cloud based tool will be acceptable.
(Even MS Windows has a "Jungo" - automated Windows Driver Creator tool.)
Instead of writing a real device driver why not to provide all "capabilities"
for whatever device and tool will create driver automatically.
Driver should/must automatically handle all basic/generic capabilities
such as On, Off, Dim, etc. All device specific capabilities should be added
based on provided info for the driver creation tool.
For instance, every Video Card was/is working with Generic VGA Driver.
But all card specific functions became available after installation
of card specific manufacture driver.