As I was in the same boat a few days back I will try to help from a newbie perspective.
There are Things, which are the physical things that OH recognises, for instance the physical switches.
Then there are Items, which are Software-based items that can do certain things, for instance switch.
A Thing can have multiple items. For instance A sensor thing that shows both temperature and humidity. Or a multi-switch.
So if you log into Paper UI and OH2 recognised the thing it will show up in the “inbox” where you can add it quite easily. Under COnfiguration->Things you dhan have to add items to the thing you want to control.
If that seems to complicated OH2 can help. Go to Configuration -> System and set “Simple Mode” under the point “Item Linking” to enabled, then OH2 will create the Items for you when you add a new thing.
If you have already added the thing just delete it and go to inbox->find to re-find it.
The Items will show up under the point “Control” where you can then control them.
So far no config file touched. You will (only) need the config files as soon as you want to do slightly advanced things.
I must say I feel for the OP.
His issues are real. He’s not a computer illiterate. And still…
Several answers are in the form of “You need to do this also …” and the classical " you must understand it is a beta"
The big risk is that threads like this doesn’t escalate into problem records or issue to address the underlying causes for his frustration.
If this is not handled it will be the death of OH. Or it will never leave Beta phase.
When I’ve been looking for solutions to issues in my installations , I’ve seen plenty of answers like “Try this” or “Try that” but many of the underlying causes never gets addressed or escalated.
This year only, several people (including me) have reported issues where OH doesn’t start.
No real help on the issue, no roadmap/tips for fault analysis, nothing.
What I’ve seen is “I did a fresh install and now it works”. (And I’ll try the same)
( I still don’t know how to debug if karaf doesn’t start)
In my view , these issues are extremely dangerous for OH.
I understand your frustration and struggles. the community is working furiously to try to address the deficiencies in the documentation but it is slow going and OH itself is growing and changing so quickly that it is hard to keep up. That coupled with the sheer complexity of home automation in general presents a huge barrier that newcomers need to overcome.
I will admit I only scanned the rest of the replies in this thread and reading them more closely as I write this so this posting may be a bit disjoint.
It takes one change. Open services/addons.cfg from your config folder and change package to demo.
Wait a bit and all the bindings and configs that work with the demo will be downloaded and installed.
Now when you open your URL you should see a BasicUI, in addition to PaperUI. when you click on BasicUI you will see the demo sitemap. The file that defines that sitemap is located in sitemaps/demo.sitemap.
The rest of the config that makes that sitemap work are in the other config folders.
SmartThings does have a REST API that can be used to integrate OH with the SmartThings Hub. But there is no SmartThings binding at this time. Also, Zigbee support will be added to OH soon which should allow OH to control those other bulbs.
That is generally true. It is much easier to answer more specific questions than generic questions. Particularly when asking for help with something we generally need to know:
versions of OH and addons used
detailed description of the problem
Items, Rules, and other relevant config files
what has already been tried to solve the problem.
“Help it doesn’t work” type questions often do not get much of a response because we don’t have enough information to help and it is no fun playing 20 questions trying to extract all the needed information to even begin to help.
However, in @tdsheppard77’s case, this is one of those generic questions that should be answered and I see several attempts at answers here. The fact the answers were not satisfying is a different thing entirely.
Its a pain and I think there is an issue for this. As @Udo_Hartmann described, click on the type on the tree in the left and press <crtl>n and the new dialog file will come up.
If you created a new file outside of Designer, click on the folder and select your config file again and everything will be reloaded.
It is a pain. It shouldn’t be this way.
So here is one problem you will face that is partially caused by the fact that OH is in transition from version 1 to version 2 right now. Version 2 has a new architecture and a whole new way to write add-ons. But Version 2 has backwards compatibility with 1.x version add-ons. This results in two different ways that Things and Items need to be created and managed.
Version 2 stuff can all be created and managed within PaperUI. For those addons that have not yet been rewritten for OH 2 everything must be managed in the old OH 1.x way in the text files. Hue happens to be one such add-on.
For all 1.x verison addons you need to look at the OH 1.x wiki for documentation on how to configure and create Items bound to that Item.
Now that I have that out of the way, you will only see something in the Control Link on PaperUI for Things that come from 2.0 version bindings.
What is the name of this sitemap file and where is it located? When you start openHAB do you see anything in openhab.log? If you installed using apt-get (preferred) that is located in /var/log/openhab2/openhab.log I think.
Are there Items and Groups defined for all of the Items that appear in that Sitemap?
The fact that nothing came up in BasicUI indicates there is an error somewhere.
A fault that is so severe that you have to resort to reinstalling is pretty serious. And as we do that, all information needed to do an RCA goes out the window.
Reporting issues here is twofolded for me, yes I want them resolved. But first and foremost I want to make the product better. And I think that the process of moving from cases in this forum to code improvements could be strengthened.
As for your specific question on documentation:
I come from OH1 and I would like to throw the Paper UI as far as I can. Or provide an import utility to move all files into the database.
For instance, being a novice in the tools and trying to edit stuff when the UI doesn’t reflect the updates is a nightmare: Did I do something wrong or is the tool at fault, Should I try again? or something else?
If OH should make an impact on the IoT stage, the installation and admin must be rock solid, coherent and hazzle free. Not a lot of jumping between PaperUI, habmin and good old vi combined with guessing.
The documentation should provide one solid way for doing this.
And if needed, the GUI’s should adapt to that one seemless way of working.
I agree and sadly this is a case where PaperUI (nor is Habmin) fully capable. And it is a double problem as PaperUI can’t work with OH 1.9 bindings at all except to install them.
Massive changes are being made to PaperUI even as I type this and it is getting better and better. But for now, especially for people migrating from OH 1, I can’t recommend it as your primary tool. It is just too soon. Personally I currently only use PaperUI for auto-discovered Things and as a place to quickly find the ID of a Channel. I use text files for everything else.
As PaperUI matures I will likely move more over to it but probably not until all of the bindings I currently use have a 2.0 version.
I pretty much wrote the Migration tutorial with this approach in mind.
(As I understand it, cloudbee is being phased out)
I think most would prefer appl maintenance by apt-get or similar.
I also think that all doc should rely on one installation method.
Then doc can be clear on directories and file locations etc.
For a beginner is is a tremendeous difference between place your rules in /etc/openhab2/rules/ compared to place your rules in your rules directory.
The single distro started with the snapshot I used in the tutorial, so no problem there
I agree on your apt approach, but on CentOS that’s not possible (because of yum instead of apt ). But the setup is almost the same after the first installation
That is a challenge because a significant portion of OH users are running on a non-apt based OS (CentOS, Windows, OSX, even some FreeBSD) or containerized (e.g. Docker, Synology). We would be cutting off a third at least of all users if we restricted the docs to just the apt-get Linux installation in the instructions.
Ideas have been floated to make the docs a little dynamic where you check a box at the top with your install type and the paths and some instructions get tailored to that type of install but I think pretty much everyone would agree we should focus more on the content right now than cool features like that.
I think you are absolutely right… I had a similar experience; endless frustration…almost 40 years in IT… e.g. wrote a complete and secure online store software package (ASP), do PHP, C++, a bit of Python, but this openHAB thing has frustrated the hell out of me… arriving at the same point (multiple times) of simply ditching this bloody thing.
… if it weren’t for the help of a few individuals (rlkoshak, Udo, shui, and others) I would have dumped this thing quick smart.
It has always puzzled me (and still does), that I could do so many things in other languages, but could not in OH.
However, I am still here; have overcome my frustrations; like what OH can do (it is brilliant compared to any other HA system), but not the way it needs to be ‘programmed’. I would say, it is like learning other languages; some pick-up a language in months, while others may study them for years and never reach a satisfactory level of proficiency.
When I started out with H(ome) A(utomation) I was in the process of owner-building a house, exploring the option of automating it, ending up with an architecture, where I am building hardware (based on Arduino), messaging (with MQTT), and control and display with OH. I am doing things in concert, which no other current system can do.
When I look at the money side, despite having wasted time ‘en mass’, I am looking at 2,000 AUD (~`1,300 EUR) for something that could have cost me 10s of thousands.
What I suggest to you is:
make sure you have installed OH properly (I started over after discovering that I used a ZIP method rather than apt-get). This solved quite a few issues right there.
start with the demo set-up; play with it, make changes and see what falls over --> learning
add one thing of yours to the demo, and see what happens
once you get an idea, remove things form the demo (sitemap, items, rules,) and see what happens
then build your system, one ting at the time – always observe what happens
What also needs to be remembered and understood: this is a free, open source run by a bunch of volunteers, not a commercial off the shelf product… enthusiasts with a shared goal of producing a wonderful system. If you hate it, just walk away…
There are only two options:
overcome your frustrations and learn, and end up with a system that can do basically anything (look at the number of bindings, and what rules can do)
I couldn’t find the name yum in my head so I wrote “and similar” instead.
But honestly I don’t know if both installs have the same directory structure.
For a beginner I think wget, curl, mkdir and unzips etc should be avoided.
Basically anything that hinders clear documentation.
I think that anyone that writes doc for an addon or binding or such is also greatly
helped if we can nail some things on the wall, like folder structures.
( But also other small things like calling the default sitemap default.sitemap for instance )
Here is an example of less than perfect doc that I see in many places:
If you don't have a Tellstick Duo or the number of device events is less
than 1 every 10 minutes you should increate the max_idle:
Yes I can see that One methods was oversimplified. And I don’t know if yum packages uses the same physical directory structure.
2nd best (or desperate last) option could be to set env variables so doc could refer to $OH_CONF/rules or something like that.
Even if the env variables wasn’t used by the package itself.
Heck, they could probably just be defined in the doc.
I know what you are trying to say, all the more funny I had to google for the quoted sentence. As you can see, writing a text others can follow is not as easy as it seems.
Let me state a few things:
openHAB is best run on a Linux system. Linux systems are great as dedicated servers. That’s why most instructions expect a Linux system. It is possible to run openHAB on Windows! It’s just not as common…
When using a Linux system, you need to know the Linux 101. As a Windows user you know how to do things the Windows way - As a Linux user you need to know about wget, mkdir, ls and find. It’s not pleasant but everyone can do it. Please check the very first paragraph after the table of content here: http://docs.openhab.org/installation/linux.html
Now, does that mean it’s pointless to look into openHAB if you do not want to bother with Linux? Not necessarily. That’s where things like openHABian come into play.
Another big issue seems to be the documentation question. “The documentation is incomplete”, “Following a tutorial didn’t work”, “I read somewhere that I have to set max_idle, now my cat is ill”. Yes of course, the situation on the documentation front is far from perfect. However, most of the time I see questions like these, the answers are repeating and repeating. Often it would just have been a matter of one search. All useful information - including thorough documentation, answered questions, binding usage hints and even hands-on tutorials - can be found en masse under docs and here in the community forum.
Lastly I want to say something without wanting to offend anybody. It’s easy and quick to ask questions but hard and time consuming to give answers. Often this is a one-sided deal and I very seldomly see anybody giving anything back. If the one before you would have improved the Tellstick article, we wouldn’t have this problem. If you were to invest a few minutes to help others here in the forum, the next one could already spend time improving the documentation. That’s what I would be doing right now, if I had not seen this discussion…
openHAB is not an iPhone. It’s a complex diverse framework for home automation covering hundreds of technologies and devices. Dig into it, get to love it, grow on it.
@rlkoshak as for documentation for a beginner: Create a step-by-step guide to setting it up and getting it running. Things like the pressing ctrl+n in the designer, don’t assume the user knows where the config file is, Give a real example of a sitemap and then explain it.
Speaking of which, would anyone be willing to share their sitemap with me so I can learn from it?
I’m working on getting one light working the way I want and learning from that. I have basicui controlling it. with the following:
I think the biggest issue with the current documentation is that it assumes too much. It assumes that a user knows that the default sitemap should be named default.sitemap or that you have to go into the config and tell it to load whatever.sitemap by default. It’s little details like that which cause the most frustration for me. Once, someone answered that for me I was able to get things going. Now i’m just working out proper syntax for controlling things the way I want.
But there is a problem right there. The “default sitemap” does not really matter. You can call your sitemap whatever you want and even create multiple. BasicUI or your smartphone client will prompt you to select the one you want to open. Setting the “default” sitemap in Paper UI is a second step but that’s totally up to you.
Ok, I’ve got it working with 2 lights now. I’m trying to get it to show the percentage the light is at but I can’t get it to do that. I’ve read the docs and tried each one but not sure what i’m doing wrong.
Also, sometimes the icon will update based on the percentage and sometimes it doesn’t.
Concerning the documentation: I found the installation documentation quite good (could be extended or clarified here and there, but generally it was good). But after the installation I was quite left alone. I would add (in the openhab2 configuration documentation) what can be configured where, the relation between OH1 and OH2 configuration, mix-and-match-ability, and what part of the OH1 configuration can be used, should be used and is not outdated.
Also an Example collection would be very helpful, as many of the “old” examples do not work any more, mainly due to minor issues, but for a beginner that can be a deal-breaker.
I am travelling at the moment, but I will write a more comprehensive suggestion as soon as I am back.