But that’s a home automation problem. It’s not an OH problem.
Everyone’s home automation requirements are unique. Does everyone need to know all that stuff? No, of course not. But some people will need to know X and others will need to know Y and yet a third set will need to know Z even for a simple case. If you want to use zigbee2mqtt, well you’re going to have to go learn how that service works and how to use MQTT with OH including installing and configuring Mosquitto (or other broker of your choice). But not everyone has that requirement. Others will need to learn how to read Modbus or KNX registers or how to pair a device with a Zigbee coordinator.
There isn’t a whole lot we can do to eliminate all that. The technologies work the way they work. There is only so much we can do about that.
And we can’t predict what each and every user needs to know for their specific requirements, particularly when it comes to the stuff outside of OH.
This is the same reason why How to get started (there is no step-by-step tutorial). There is around 350! combinations of add-ons that are possible with OH. I think that’s more than there are atoms that make up the planet. We’d be at this forever if we made a step-by-step for even a fraction of that. But that then means that the end users must be able to go and learn enough about their requirements and the technologies they need to use outside of OH.
Absolutely we can make things simpler and easier and there’s already been at least one issue created from this thread. But we have to do so in ways that fit in the scope of the actual problem at hand and the number of volunteers we have available.