Legacy bindings for openHAB3, esp: ekey, FritzboxTR064 and mqqteventbus

[binderth (Thomas Binder)]

As I’m playing around a bit with openHAB3 M1, I did come across some bindings, I’d like to use with OH3 also - and as the polling in Poll: Which OH1.x addons do you use? - #103 by Wikibear was something I missed, perhaps someone has an idea for the following I use:

• ekey
• Fritzbox TR064
• MQTT - Eventbus

I know, there’s some discussion around

• serial
• expire
• http
• gpio

is there a chance to use these with OH3?
and also: If there was a replacement or an useable Eventbus in OH3, I can setup a second openHAB2.x with access to the legacy bindings and just push the items to the main OH3… I know, I could use the REST API, but that’s just a pain in the a$%, if I had to write a rule on the legacy-items for use in OH3.

[hafniumzinc (T)]

In case you weren’t aware: this issue tracks the status of existing bindings, and what will happen in v3

[rossko57]

@binderth

If there was a replacement or an useable Eventbus in OH3

Have another look around for this. While there are grand plans for OH3, the OH2 version is useable under OH3.

Marketplace MQTT Event Bus

Update: Complete rewrite to use the rule templates published to the Marketplace. There is no need to code this or copy/paste code to make this work. There is a Remote openHAB binding which replaces this capability in most cases. See openhab-addons/bundles/org.openhab.binding.remoteopenhab at main · openhab/openhab-addons · GitHub . However there may be use cases where MQTT is preferred, such as integration with a non-openHAB service. Introduction What’s an Event Bus? There are times when one m…

@binderth

• http

Likewise, another look around

HTTP binding - openHAB 3 version

As some of you might know the http binding is still an openHAB 1-addon and will not be supported in the upcoming openHAB3. Therefore I developed a new openHAB 3-version. This is still work-in-progress, but I would like to here your thoughts (especially on missing or unclear features), bugs and everything related. The documentation can be found on Github: (edited: binding included in distribution).http and the latest and greatest JAR is available at (edited; binding included in distribution). Y…

@binderth

• expire

I do not think any ‘native’ solution is ready, however this is available now

Jython Drop-in Replacement for Expire 1.x Binding

Edit: I’ve reimplemented this and am hosting it on my own repo instead of as a submission to the helper libraries. As a challenge to myself I wanted to see if I could replace the Expire binding using Rules. The answer appears to be yes. See GitHub - rkoshak/openhab-rules-tools: Library functions, classes, and examples to reuse in the development of new Rules. for a drop in replacement to the Expire binding. You don’t even need to change your Item configs. The rules will pick up your existing …

[binderth (Thomas Binder)]

@hafniumzinc

In case you weren’t aware: this issue tracks the status of existing bindings, and what will happen in v3

for example: I saw, ekey was not voted on (but I do know, there are a bunch of users here in the forum besides me) and if it says “supported”, it’s worked on for OH3? that would be fabulous!

[binderth (Thomas Binder)]

Thanks for the heads up!

[Bruce_Osborne]

@binderth

expire

@kai is working on a solution for that, I believe. Personally I am experimenting with moving to HABApp which can have similar functionality.

Introduce "expire" functionality for item states

[rlkoshak (Rich Koshak)]

@rossko57

I do not think any ‘native’ solution is ready, however this is available now

A native version of both Expire (part of core) and the Event Bus (will be a separate plugin) are in work for OH 3. I can’t say where they are in terms of implementation but I think there has been activity on both.