This works fine if a command is received by mqtt or zwave. But if I use a switch manualy connected to the zwave device, there is a update received only on zwave channel - no changes in mqtt.
Following the solution I added the “follow”-profile. But if a command receives now, the connected lamp starts blinking…
To the wrong channel.
If you want “something changed” at the zwave device to cause a command to this Item - which will in turn get passed to the MQTT command topic - then it’s the zwave channel that needs the profile.
You might also want the “normal” zwave status to update the Item, so you’d probably end up with three channels for this Item.
Depending how your end devices respond to commands, you may still get a loop.
Then that’s where your problem possibly is. When you switch a zwave light using the physically connected switch, OH does not know so it cannot apply the follow profile until it receives that info from the actuator. Check your associations.
zwave channel with follow profile - if you have an incoming state update from zwave (which is in doubt) the profile intercepts that and turns it into a command to the linked Item instead.
In other words, the state update is not done.
Item state could still be updated by some other binding or autoupdate responding to that command, so that may not be a problem.
You might want to have a non-follow zwave channel as well in order to get ordinary state updates.
But first, let’s find ot if you get any zwave updates.