Can someone explain me a little bit, how this MQTT Binding differs from the old (1.0) one?
I have tried installing it, but I couldn’t find later, how could I use it… I thought it follows the same procedure as other OH 2.X bindings, that you will have a bridge (MQTT broker) and then it will “auto-discover” the available topics and you can add each end-topic as a thing.
But I assume this is not how this works. Can someone explain that to me in a few sentences?
Will it worth switching to it from 1.0? I think sooner or later I will have to switch from my 1.X bindings and I have a few (I use MQTT very frequently, almost everything communicates through this protocol), so I would start with this…
Yeah, this is at least what I like to make possible, potentially even only through some workaround/hack. But I see it as an important feature so that the new MQTT binding can really serve as a full replacement for the old one.
Getting the actions accessible from rules is one of my last todos for the 2.4 release - I’ll hurry up to come up with some suggestion .
At the moment you can’t. You would need an outbound MAP transformation to convert UP to “pulse,0,0,100” and so on. OH 2.5 snapshot will support this soon.
Time for me to jump on the bandwagon, I appear to have picked a really bad time to migrate my OH2 onto a new rPi as I have stumbles onto this MQTT issue.
I assume on the old rPi I was on an older version of MQTT (forgive my ignorance here) and the new rPi which is up-to-date via apt, must be on the new one. I installed the MQTT binding via PaperUI and mosquitto via apt.
I can publish and subscribe fine via the CLI using mosquitto_pub and mosquitto_sub, so I know that at least this is working. Integration with OH2 seems to have broken.
If anyone is able to help I would be extremely grateful!
From reading the above I assume that the items need to be changed to something along the lines of mqtt.publish(…) but not quite sure how to integrate the directionality or the item command (e.g. from clicking the respective button in HABPanel).