[CLOSED] MQTT binding version 2.4 (Pre-release !)

[rlkoshak (Rich Koshak)]

@David_Graeff

And it will allow to publish to a topic based on the rule action inputs

@David_Graeff

You can. Create a trigger channel on the MQTT broker, subscribed to “myfirstinstance/#”.
The trigger payload at the moment is the value only, but I will extend the payload to contain the topic name as well separated with a custom character.

OK, then this isn’t so bad. A couple of Rules that I can later distribute as a library or a template isn’t so bad at all.

@David_Graeff

There should be no reason to need the mqtt-eventbus binding anymore or did I overlook a use-case?

Nothing I can think of. I think as long as we can subscribe to a tree of topics using # and get the topic as well as the message itself and we have a way to publish to arbitrary topics from a Rule (using event.topic as the MQTT topic will probably be the most natural) I think we have all the bases covered.