I can’t speak to Cellar. But I can speak to the MqTT Event Bus. The equivalent of the MQTT Event Bus for the 2.5 version of the MQTT binding can be found at Marketplace MQTT Event Bus. My understanding is the access to the Items required to implement this in the binding is not allowed for 2.x bindings which is why the author did not include it in the binding itself.
I’m exploring options to convert this to a Rule Template using JavaScript instead of Python and other options to make installation and use of it easier (i.e. just import a Rule template). For now, I’ve a Rules DSL and Python version that works quite nicely and is surprising little code:
- reports online/offline status of OH instances through a retained LWT message
- publishes updates and events separately and individually controllable
- All that is required on the receiving OH instance is to have an Item of the same type and name
- state updates are published retained, commands are not
- can control which Items publish what events through Group membership
And I’ve a backlog of improvements including:
- automatic creation of Items on the subscribing side (optional)
- automatic discovery of the remote OH instances and creation of Things/Channels (not sure if it’s possible yet)
- option to publish all Items (right now you have to add them to a Group)
- better error handling
- have a better way to import and use the Rule but that depends on what the NGRE will look like so I can’t make any changes there yet
All I can say is that the vote by the AC to remove support for OH 1.x bindings pointed to this post and the option to run an older OH instance with OH 3 to retain the ability to use 1.x binding as justification for removing the support in OH 3.