Hi,
If i can add that it is a little more complex for those who do not have a good command of english like me ! With the technical situations described in the documentation, it is sometimes difficult. It could be more simple with draw or video. For example, i am not sure openHAB work alone. I mean if i have things (relay for ex), bindings (shelly), items (convectors) do i need mosquitto, red-node etc ???
Jean Luc
I donāt know inconvenient and adventage with mosquitto. Is Open HAB work alone ?
I spoke about video or picture to show some concret example that each other can adapt. For me with my shelly 1, shelly 2.5 and H&T sensors i need to āleaveā app cloud for a local network, make rules āfriendly lookingā like line on relay 1 and 2 of the shelly 2.5 at 8h00, line on relay 1 if sensor temperature < 18Ā°C etc
write your questions in your bative language and then just use google-translate to translate to english.
The grammar wonāt be brilliant but it will be easy to understand.
As far as I have understood it: OpenHAB offers a ācenterā which can āplug-inā many many āadaptersā to connect all kinds of IoT-devices with a lot of different protocols. OpenHAB is able to use rule on its own.
So Yes OpenHAB can work āaloneā
Your description is not very clear yet. So please use google-translate
Stuff like Mosquitto and Node-Red are not something that you choose to use just because. Itās not an extra. Either you need it or you donāt.
You need it when the technology or device you want to use with openHAB requires MQTT. While Shelly supports MQTT, there is also a Shelly binding. So use that. It doesnāt work through the cloud, itās a local control. But if you donāt trust the binding, then switch the devices over to use MQTT in which case Mosquitto (or some other MQTT Broker) is required.
It depends on what devices and technology you want to integrate with it. Sometimes there isnāt a binding but there is a Python script or Node program on GitHub that integrates with that technology. You could use that to make the technology or device work in openHAB.
One reason why there isnāt really an end-to-end tutorial is because, as you are seeing, the answers to all of your questions are almost always going to be āit depends.ā
Home automation is hopelessly fragmented and full of hundreds of technologies and devices that canāt talk to each other. So often the answers and the steps and the approach is going to depend on your specifics.
For your specifics with Shelly, use the Shelly binding. Save MQTT for a time when you really need it.
what made it possible that you are able to use openHAB in many and versatile ways?
The answer is: experience
That is something that you collect. You collect experience.
Now there are a lot of ways to collect experience
doing a lot of try and error
asking in forums
reading a lot in documentation
but last but not least
following example-tutorials to get at least a rough picture of how it works.
analogon:
If you start learning welding you start with
Inert gas welding
or
electrode rod-welding
of course there are specialties like
Electron beam welding
Roll welding, Friction welding and a lot of more
All welding-methods have still some basic things in common. And for these basics things learning
Inert gas welding
or
electrode rod-welding
is useful
This is the reason why I insist on example-tutorials are useful!
best regards Stefan
Then you need to write them. Iāve been working with openHAB for near on a decade. In that entire time Iāve dedicated myself to helping new users get started with openHAB. Iāve written scores of tutorials. Iāve written more than half of the Getting Started tutorial.
Yes, I have lots of experience with OH. But I have even more experience helping new users get started with OH.
Iāve even written end-to-end tutorials. Heck, the Getting Started tutorial is an end-to-end tutorial. Here are some more:
Dozens of users have written hundreds of other tutorials and posted examples. Some are point and some are end-to-end too. Solutions - openHAB Community
Examples we have coming out of our ears. What we donāt have is an end-to-end show me everything using my specific technologies X, Y and Z. Thatās not feasible. There would be 350! (thatās factorial) different tutorials just to cover the different combinations of add-ons alone. That wouldnāt even touch Items, the UI, Persistence, etc.
So what we do have are point examples. We have examples that document, as @StefanL38 called it, āthe patternā for how to do something in OH. But you have to be able to take that tutorial, extract the pattern, and apply it to your specific bespoke situation and goals.
And if that isnāt good enough, anyone can step up and see if they can do better. Demanding that other people donate their time to document things exactly how you want isnāt going to get you anywhere. Weāve all already done the best we can. If itās not good enough, step up and show us a better way.