Is it possible for me to make a suggestion here as a new user?
It seems to me that while the best part of openhab is it’s flexibility, everyone approaches their installation with a blank slate and seems to start from scratch. There are people who post their rules around and examples exist scattered about to cut and paste. As a system administrator and not a programmer it feels a lot like coding still.
I know OH2 plans include approachability for newer and more novice users. Here are some of my thoughts to achieve that:
What about finding a way to incorporate some of the better implementation rules into the addons release? The divided efforts could become collaborative and in the end everyone benefits.
Example: I was surprised to see thermostat functionality (which to me is likely to exist in almost all installs) actually missing from release. I thought for sure there would be some kind of binding or similar which gave nest/ecobee like functionality (or greater) right in the addons package.
Common and basic functionality built collaboratively and modularly. These could maybe called “rule modules”? If these rule modules were designed in such a way that they were driven by seperate configuration files then they could be easily upgraded with new releases without reconfiguration. These files could basically be a list of device aliases and yes/no questions on functionality desiredExample (I’ll keep referencing thermostat control for continuity): .cfg could contain number of zones, item identification for thermstat, if presense is desired, if temp should be in “real feel”, do you have dual stage heating, is there cooling, etc.
A repository exists for code branches but rules aren’t really built off a repository in the same way which is a shame. These could be uploaded to a repository right off the openhab website (or better in the web interface) where popular rule sets could be voted on. As a new user I might look at this to see what the top 10 rated/downloaded rule modules are to see if I could use them. an INI style file is a lot more approachable than coding rules and could be filled in by a form wizard in the web interface for even easier novice use.
Please don’t see this as begging or complaining. I’m not a programmer so I really can’t contribute by means of code, but I hope that maybe I can share some thoughts and ideas which someone with more skill could use to better the project if anyone found value in it. I understand every configuration is unique and making some rules generic is highly complex, but I think the value in approachability & new user appeal could pay off on common tasks.