I use expiry
1 Like
expire binding has several replacements talked of but nothing concrete. Obviously this is important to everyone but I’m sure retiring the compat layer would find expire with a replacement along with the persistance services which I think run on OH1 tech
http 2 binding in production almost sure and nearing release
1 Like
Expire never should have been a binding on the first place. In so far as a replacement is developed, it will be a part of the core and not a separate binding.
Those are in the process of being moved I believe. They definitely will be moved and REST API endpoints created.
3 Likes
oh yes good news indeed
Homematic exists in OH2.
Mqttitude was replaced by gpstracker.
Weather was replaced by several others but support of few weather services could be missing in OH2.
Isn’t lgtvserial a replacement of lgtv ?
One OH2 http binding is in progress (PR).
Working from the legacy and non-legacy feature.xmls, I get…
Legacy (have an OH2 version): 35
org.openhab.action.mail
org.openhab.io.transport.mqtt
org.openhab.action.mqtt
org.openhab.action.satel
org.openhab.binding.astro
org.openhab.binding.dmx
org.openhab.binding.dmx.ola
org.openhab.binding.dsmr
org.openhab.binding.enocean
org.openhab.binding.exec
org.openhab.binding.homematic
org.openhab.binding.ihc
org.openhab.binding.irtrans
org.openhab.binding.knx
org.openhab.binding.milight
org.openhab.binding.modbus
org.openhab.io.transport.mqtt
org.openhab.binding.mqtt
org.openhab.io.transport.mqtt
org.openhab.binding.mqttitude
org.openhab.binding.nest
org.openhab.binding.netatmo
org.openhab.binding.networkhealth
org.openhab.binding.nibeheatpump
org.openhab.binding.onewire
org.openhab.binding.onkyo
org.openhab.binding.plugwise
org.openhab.binding.powermax
org.openhab.action.pushbullet
org.openhab.binding.rwesmarthome
org.openhab.binding.satel
org.openhab.binding.systeminfo
org.openhab.binding.tellstick
org.openhab.binding.urtsi
org.openhab.binding.zwave
Non-legacy: 96
org.openhab.action.ecobee
org.openhab.action.mios
org.openhab.action.pebble
org.openhab.action.prowl
org.openhab.action.pushover
org.openhab.action.pushsafer
org.openhab.action.telegram
org.openhab.action.twitter
org.openhab.action.xbmc
org.openhab.action.xmpp
org.openhab.binding.alarmdecoder
org.openhab.binding.anel
org.openhab.binding.bticino
org.openhab.binding.caldav-command
org.openhab.binding.caldav-personal
org.openhab.binding.cardio2e
org.openhab.binding.comfoair
org.openhab.binding.denon
org.openhab.binding.ebus
org.openhab.binding.ecobee
org.openhab.binding.ecotouch
org.openhab.binding.ekey
org.openhab.binding.energenie
org.openhab.binding.enphaseenergy
org.openhab.binding.epsonprojector
org.openhab.binding.expire
org.openhab.binding.fatekplc
org.openhab.binding.freeswitch
org.openhab.binding.fritzbox
org.openhab.binding.fritzboxtr064
org.openhab.binding.fs20
org.openhab.binding.garadget
org.openhab.binding.gc100ir
org.openhab.binding.gpio
org.openhab.binding.heatmiser
org.openhab.binding.horizon
org.openhab.binding.http
org.openhab.binding.iec6205621meter
org.openhab.binding.insteonplm
org.openhab.binding.intertechno
org.openhab.binding.ipx800
org.openhab.binding.jointspace
org.openhab.binding.km200
org.openhab.binding.koubachi
org.openhab.binding.lcn
org.openhab.binding.lgtv
org.openhab.binding.maxcul
org.openhab.binding.mochadx10
org.openhab.binding.mios
org.openhab.binding.mystromecopower
org.openhab.binding.myq
org.openhab.binding.neohub
org.openhab.binding.networkupstools
org.openhab.binding.nikobus
org.openhab.binding.novelanheatpump
org.openhab.binding.openenergymonitor
org.openhab.binding.owserver
org.openhab.binding.panasonictv
org.openhab.binding.plex
org.openhab.binding.piface
org.openhab.binding.pilight
org.openhab.binding.samsungac
org.openhab.binding.sapp
org.openhab.binding.serial
org.openhab.binding.snmp
org.openhab.binding.sonance
org.openhab.binding.souliss
org.openhab.binding.swegonventilation
org.openhab.binding.tcp
org.openhab.binding.tinkerforge
org.openhab.binding.ucprelayboard
org.openhab.binding.upb
org.openhab.binding.velux
org.openhab.binding.weather
org.openhab.binding.wol
org.openhab.binding.xbmc
org.openhab.persistence.influxdb
org.openhab.persistence.dynamodb
org.openhab.persistence.gcal
org.openhab.persistence.jdbc
org.openhab.persistence.jdbc
org.openhab.persistence.jdbc
org.openhab.persistence.jdbc
org.openhab.persistence.jdbc
org.openhab.persistence.jdbc
org.openhab.persistence.jdbc
org.openhab.persistence.jpa
org.openhab.persistence.mapdb
org.openhab.io.transport.mqtt
org.openhab.persistence.mqtt
org.openhab.persistence.mysql
org.openhab.persistence.rrd4j
org.openhab.io.gcal
org.openhab.io.gpio
org.openhab.io.transport.cul
org.openhab.io.caldav
2 Likes
Thanks, I will update the lists and compare the result with your findings.
I know some people manually install 1x bindings because they cannot be installed via PaperUI. The VDR binding is one of them. I think the non-legacy list only contains bindings that are confirmed that they work in 2.x. I could be wrong though.
Enocean already exists in OH2.
A PR exists in OH2 for neohub but not yet merged.
And none of the new OH2 weather bindings provides this feature: html-layout for webview
This is the main reason why I’m still using weather1.
1 Like
@t1m, @lolodomo Thanks for your updates. I have updated the tables.
I have attached the Libre Calc spreadsheet I used. Simply strip the .txt extension from the filename.
OH 1.x and 2.x bindings.ods.txt (36.4 KB)
There is a PR in openhab-core to replace expire binding with a profile.
I also initiated a binding to replace ipx1 binding (PR opened).
I know I also saw PRs for Telegram and SNMP.
1 Like
SNMP is merged. Just forgot to move the old one to legacy.
1 Like
The same seems true for the org.openhab.binding.denon v1.x binding. There is a org.openhab.binding.denonmarantz v2.x binding available.
For BTicino, there is a work for a OpenWebnet binding that would replace the 1.x binding. But no opened PR.
I went through the “Only 1.x” column and compared it to PRs with the “new binding” tag in openhab2-addons. I found the following PRs that may apply:
benqprojector #4063 WIP
bticino (Work in progress. No PR.)
energenie #3890
enigma2 #1706
gpio #1334
http #4342
mystromecopower #2756
neohub #5688
networkupstools #5493 WIP? (apcupsd)
panasonictv #4407
souliss #4945
stiebelheatpump #3483 WIP
velux #2531 & #4416
More importantly, do all of these 1.x bindings use the 1.x compatibility layer? From the original messages in this thread, I thought only some of them did.
Yes… all 1.x bindings use compat1x.
Assuming that 50 or more OH1 bindings are “in heavy use”, would it not be easier to program one single compatibility layer than porting each obsolete binding individually to OH2?
2 Likes
Alex
Thanks for moving your question to the discussion thread
@5iver great poll, great research tool to find out how much these old bindings are being used. From my observations at this early time in the poll running, it seems most the bindings that have more then 1or 2 people using them already have a replacement in the works.
Alex, qualify ‘heavy use’ because I only saw a few that had more then 4 or 5 users and all of those have a replacement planned or in process of being created.
To me, one or two users doesn’t constitute ‘heavy use’
Perhaps but no one wants to do that. No one is stopping anyone who has java programming skills from doing so and so far no one has stepped forward.