if i change the item Zigbee_Dimmer01_Kueche_Brightness the wall dimmer is responding immediately and is dimming the light just fine.
item->mqtt
but in the opposite if i change with wall Dimmer mqtt sends the dimming steps to the item and the item changes. So far so good but when the item changes it sends changes back to the mqtt.
mqtt->item->mqtt
This behaves strangely - while i dim physical on the walldimmer, dimmer changes the mqtt:brightness in multiple steps and the delay between physical change and dimmer:item change lets the light flicker back to where i started.
how to not loop mqtt->item->mqtt? just only mqtt->item and good
This light supports the following features: state, brightness.
state: To control the state publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"state": "ON"}, {"state": "OFF"} or {"state": "TOGGLE"}. To read the state send a message to zigbee2mqtt/FRIENDLY_NAME/get with payload {"state": ""}.
brightness: To control the brightness publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"brightness": VALUE} where VALUE is a number between 0 and 254. To read the brightness send a message to zigbee2mqtt/FRIENDLY_NAME/get with payload {"brightness": ""}.
@apella12 - Yes i have Mqtt Explorer and can see topics in action, I mean i can change the dimmer from ui and vice versa
@03chris - your stateTopic is stateTopic=“zigbee2mqtt/LED_Kueche” for state(schalter) and brightness(dimmer), so changes you make at the wall dimmer are not represented in UI.
If you rotate the dimmer knob can you see the dimmer changing in ui? i don´t think so.
if you change switch to stateTopic=“zigbee2mqtt/LED_Kueche/state” and dimmer to stateTopic=“zigbee2mqtt/LED_Kueche/brightness(or brightness_percent)” you have the same effect like me.