How could I publish to 2 topics with only one item. The objective is like on the image [Sin%20t%C3%ADtulo] I have a rollershutter and I would like to up and down with only that item and not to use 2 different items. Is it possible? How could I program it? The item declaration (.item file): Roll…

You can archive this with MQTT1. MQTT2 does not support this broken MQTT topic design though. An MQTT topic represents one state and that’s what MQTT2 supports :slight_smile: I recommend some additional logic on your µController to software emulate a H-Bridge and have one MQTT topic only. Cheers,…

One approach would be to define your Item as a Proxy item and trigger a rule to send the command to the right topic using the publishMQTT Action.

How could I do that? I don’t know :frowning:

[image] rlkoshak: define your Item as a Proxy item [image] Design Pattern: Proxy Item Tutorials & Examples Edit: Updates for OH 4 Please see Design Pattern: What is a Design Pattern and How Do I Use Them for information on what a DP is and how to use t…

And in the case of a rollershutter, the received command is a number? rule “Roller Shutter” when Item Shutter_GF_Living received command then if (receivedCommand == 100) { mqttActions.publishMQTT(“out/P_Prueba/state”,“ON”) } else (receivedCommand == 0) { mqttActions.publishMQTT(“out/P_Pru…

[image] rafa: And in the case of a rollershutter, the received command is a number? Not necessarily. As documented [here] ( Items | openHAB ), Rollershutter can accept OnOff, IncreaseDecrease, and Percent as commands. But it stores is state only as a percent.

And how could I receive the same message from different topic? I mean, for example, I have 2 sensor, first “in/F_Garage_Door_Opened/state” send OPEN/CLOSE and second “in/F_Garage_Door_Closed/state” send OPEN/CLOSE too, but I’m only interested in the command OPEN from the two topic, and I would like …

Please How to use code fences . [image] rafa: I would like to program a contact item that is OPEN when it is OPEN from “in/F_Garage_Door_Opened/state” and is CLOSE when it is OPEN from “in/F_Garage_Door_Closed/state”. There is a bug in the binding right now that makes this not possible using …

Is this still not supported? There are cases, like for example with a Rollershutter, where it makes sense to split the topics: One topic for position commands and a seperated one for up and down commands as those are something completely different. As far as I can see this is not supported at the m…