Sorry to ‘bark back’ but I think to quite some extent your experiences are because you did not properly invest enough into reading the docs and understanding OH concepts before you started.
No offense taken. I suppose this thread is for discussion purposes. All in all I think you are doing great job if I think that everything here is for free.
Check out this page of the docs. Did you ever even get to see that ?
This is exactly my point. How much time do I need to invest in order to understand basic concept of openHab. In today’s word applications are written to be easily picked up. Just like OH application on Android. It automatically discovered my instance and showed things - that was suberb! Before I picked openHab I looked at Vera/Fibaro/Domoticz. OH seemed to be most promising when it comes to support of new things.
In the same time I think that all competitors have one UI for configuring everything.
You pointed me to documentation that is creating confusion. There are 5 columns describing 5 different approaches. What is the future? Where should I invest my time in configuration? Will the .items files be migrated to jsondb and marked as depreciated? This is my point - provide guidance for newbies like me what should I pick or pick it for me because I’m newbie.
There is stated “Do not autocreate Items” while in some places in the forum I read - “I don’t understand why people aren’t using simple binding”
Everything around ease of configuration (things/bindings) should be in core of the system. I don’t even know “PaperUI” is core or it’s only “Textual Configuration”?
Plus your approach was too risky, why did you go for snapshots as a beginner?
“Winter is coming” - I suppose multiple users will come here for “simple” automation of the heaters. On forum of my housing estate community multiple people were asking “have anyone has experience with heater automation” and they are buying danfoss/bluettooth devices to control it. I came here for same reason. Problem was like I stated - proper support of my device is only in snapshot version. I used nightly builds a lot on early android devices and right now I cured out of it - I want simple stability.
Now read that statement again please and tell me what you think yourself where the error was…
Again going back to question what is OH future. I hoped that new rules will be something that I might use when stable version will come out. I immediately thought that migrating from rules files to json will be paintfull. I’m not long here so it’s hard to asses what Experimental means sometimes:
- not everything is working but we are getting it done
or
- this might be rewritten few times till we make it working - don’t use it for core automation
Looking at it from time perspective for sure was my bad choice.
It is meant for making the core better, not usability problems that we clearly still have in OH
Isn’t usability also core of the system? Imagine using Linux with lynx instead of “proper” browser. If that’s not the case then for sure I don’t what core you had in mind. Especially when in the first post I clearly see Logview/Notifications about errors/multi user support. For me those are clearly usability items.
One of the applications I heard in my company was named superb app but what was killing it was hundreds of small issues that at the end was killing user experience.
home automation is something that doesn’t have conventions yet that we can build on
I disagree - some of you do it for over 4 years - that is plenty of time. You have ton of experience how to do certain tasks and what is improper way of doing things.
Imagine that I came to openHab install it to SD card and I’m asked what do you want to do? Heating automation → discovery process - what is your heater ? → how you would like to set up heating hours? Now wait few seconds I’m doing it for you.
For me core would be template engine of such story. Thing/bindings/rules. Everything out of the box > now when I need to modify it for sure I need to learn way less pieces of system at once but I can assume that it was done properly by engine out of the box.
Enough from me - I just hope some of those will be addressed in future so new comers will have easier start.