After removing the * and switching from state to command, the rollershutter will follow the given command over MQTT.
The last thing is, that inside the sitemap the percentage value at the “Default” Item for the Rollershutter wont be updated (only after a page refresh) instead of a switch, that will change the state automatically without a page refresh.
Thanks for the link to the node red approach. I’m following an alternative path:
I’m a software developer with a huge focus at process automation using BPM platforms. Concrete Camunda which provides three different engines for BPMN (structured processes), CMMN (cases)and DMN(business rules). At the first time I have written a simple API to communicate with homematic components, but this costs to much time. So there I’m interested in OpenHAB2 to easily control smart home components and can create simply some UI using sitemaps for manual mode. OpenHAB s own rule engine is not my preferred way. So here for me the easiest way is to use Mqtt as communication between the components. If someone is interested in, have a closer look to https://github.com/Chris81T/camunda-bpm-iot
This project allows using the Camunda engines as embedded engines without a jee container or spring. Also a MqttService is integrated to give options to bind inbound Mqtt messages with BPMN message receive events or so. It is still under development. After resolving this mqtt problem here I can concentrate finishing a first working version.
In my approach I will integrate this in a wildfly swarm project to create a small Uber jar, that will run as a Linux service on my pi and will hold my smart home business logic like a microservice.