Call to action - volunteers for openHAB "marketing"

[rlkoshak (Rich Koshak)]

@Saracen

For instance, a Channel is not actually either of the things you describe it to be but is a conduit or pipe through which pieces of information of one particular type can be sent.

That’s the Link which @Udo_Hartmann didn’t list.

@Saracen

I’d be happy, in the first instance, to volunteer to point out what I think is missing and what could be added or changed.

Specific and actionable issues are the best way to do this. “This section isn’t clear, make it better” really isn’t actionable though so be prepared to come with concrete suggestions.

We’ve done the best that we can with the docs and tutorials. “Do better” without details on how is kind of an FU to those who have contributed up to this point.

@Kim_Andersen

But openHAB is not easy to setup. And everytime I see debates like this, its always explained with, (by the knowledged users), thats because smart home isnt easy.

Just to be clear. OH could be made very easy for some smallish subset of users. But if your requirements fall outside that subset

@ubeaut

Well looks like home assistant can make it even easier.

OH as an organization cannot sell preconfigured hardware like that. I imagine some third party could do so if they wanted but care would have to be taken with the trademarks.

openHABian is our answer to a “preconfigured” system.

@Oliver2

By intention I want to create this for our home page and NOT for our documentation.

Expect some pushback on this.

@pmknowles

Process - Ooops

Please elaborate.

@pmknowles

One of my gripes is that I wish we could grasp ladder logic - home automation often time isn’t sequential but all the programming systems are. For instance setting a time window for heating and only turning on the boiler if a sensor requires it is easy in ladder logic but a real pain in OH.

There have been some examples of using a state machine in OH rules. A State Machine Primer with HABlladin, the openHAB Genie is old but still shows the overall approach.

I’ve on my long list of todos to create a rule template to implement a generic state machine. I’m not yet convinced it will make it simpler though.

As for the time window part, in UI rules the “But only if…” section of the rule was made for this. You can define a time range there fairly easily now:

In just text based rules or in a Script Action both JS Scripting and jRuby make time comparisons somewhat easier. For example:

if(time.toZDT().isBetweenTimes("08:00", "22:00")) {

@Kim_Andersen

Ask yourself, if that procedure is better or worse, than what it takes to add Philips Hue or even Homey.

The reason Hue can be that simple is because they only have to worry about Hue as a technology. Homey is that simple because it is limited to only a hand full of technologies, all of which can be auto discovered.

OH has no such limitations.

@Kim_Andersen

The same goes for Homey Bridge, but Homey goes even futher and find almost whatever is on the WiFi network, all by itself.

And there is an issue to figure out how to have OH discover what can be discovered during the first run wizard too.

@Kim_Andersen

And even by then, there is still no results, as a kind of UI is required as well.

This is why the semantic model exists. Could it be better? Yes, but when you add semantic tags to your Items you get a UI for free.

@Kim_Andersen

Why would anyone go through the hassle with openHAB for adding lights in a kind of smart home manner?

Because they want support for a technology that Hue and Homey doesn’t support or they want to do things that Hue and Homey can’t do.

@Kim_Andersen

To change this, developers of openHAB needs to focus on, how to make the startup/setup easier.

I keep seeing this stated as if that isn’t what the developers are already doing.