MQTT 1.x Binding vs 2.x

[rlkoshak (Rich Koshak)]

@rmhoutz

So my question is what advantages are their to using the 2.x MQTT binding verses the 1.x?

The MQTT 2 binding will continue to be maintained and receive new features. MQTT 1 will become deprecated at some point I’ve little doubt.

This is more opinion, but the MQTT 2 approach is more OH 2 like in how it works.

MQTT 2 can be configured and managed wholly within PaperUI.

MQTT 2 supports chaining transformations (the first binding to support this as far as I’m aware).

MQTT 2 comes with an Action to publish to arbitrary topics within Rules, MQTT 1 Action needs to be installed separately.

@rmhoutz

So many questions so few guides for this.

• Shelly1 and mqtt 2.4.0 Binding
• Migrating MQTT1 items to MQTT2.4 items
• Set up mqtt2 from scratch on linux
• My MQTT 1.x to 2.x Migration Experiences

@Udo_Hartmann

There may be some downers, e.g. you can’t set more than one topic to a channel, but that is only a little
problem as it’s easy to link more than one channel to an Item so no problem at all.

There is a slight caveat to this. You can have different subscribe and publish topics on a single Thing. But you cannot have more than one subscribe or more than one publish topic. And indeed, linking multiple channels to the same Item and using profiles gives you pretty much all the flexibility of defining multiple mqtt binding configs on one Item.