Yea, that’s what I mean. I don’t want to have to say “turn” every single time. In the english language there might not be so may ways to say “turn off the lights”, but in the german language there are quite a few (“mach das licht in der küche an”, “schalte das licht in der küche an”, “licht in der küche an”, “küchenlicht anschalten” and many more). In addition to that, I dim my lights, so I will have to add all kinds of applets or trigger phrases.
Also, there are things that Google Home/Assistent itself could be told to turn on (e.g. “turn the music on”), which would not work with your applet/rule, as the command is routed to your openHAB. You would then have to use a different command (“play music” instead of “turn on music”).
I want to have kind of a natural language processing. I don’t want to (and I don’t want to have my wife have to) learn an exact phrase that she has to use to turn on a light. I want it to be as intuitive as possible. That would work if I had the chance to send everything to openHAB first, my rule would then see if the command is anything that should be done via openHAB (like this https://github.com/openhab/openhab1-addons/wiki/Controlling-openHAB-with-your-voice), and if the command is not for openHAB itself, it could then send it “back” to the Home/Assistant.