Poll: Which OH1.x addons do you use?

The OH1.x compatibility layer could potentially be removed in OH3, but even if that does not happen, it would be a good thing to be actively getting these addons migrated to OH2.x. The intent of this poll is to get information into the hands of developers to help in making a decision on which migrations would be most beneficial to the community.

I’ve not included persistence, since work is already underway (thank you, @Kai!) to have these migrated after OH2.5, in preparation for OH3.

If you use OH1.x addons, which ones do you use? This poll will end on September 5th.

  • 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

0 voters

  • 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

0 voters

  • 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

0 voters

  • 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

0 voters

  • 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

0 voters

  • org.openhab.binding.ucprelayboard
  • org.openhab.binding.upb
  • org.openhab.binding.velux
  • org.openhab.binding.weather
  • org.openhab.binding.wol
  • org.openhab.binding.xbmc

0 voters

  • 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

0 voters

  • org.openhab.io.transport.cul
  • org.openhab.io.transport.mqtt
  • org.openhab.io.caldav
  • org.openhab.io.gcal
  • org.openhab.io.gpio

0 voters

  • org.openhab.action.astro
  • org.openhab.action.ciscospark
  • org.openhab.action.dscalarm
  • org.openhab.action.harmonyhub
  • org.openhab.action.homematic
  • org.openhab.action.openwebif
  • org.openhab.action.squeezebox
  • org.openhab.action.tinkerforge
  • org.openhab.action.weather
  • org.openhab.action.xpl
  • org.openhab.binding.akm868
  • org.openhab.binding.asterisk

0 voters

  • org.openhab.binding.autelis
  • org.openhab.binding.benqprojector
  • org.openhab.binding.bluetooth
  • org.openhab.binding.configadmin
  • org.openhab.binding.cups
  • org.openhab.binding.daikin
  • org.openhab.binding.davis
  • org.openhab.binding.ddwrt
  • org.openhab.binding.digitalstrom
  • org.openhab.binding.diyonxbee
  • org.openhab.binding.dmx.artnet
  • org.openhab.binding.dmx.lib485

0 voters

  • org.openhab.binding.dscalarm
  • org.openhab.binding.ehealth
  • org.openhab.binding.em
  • org.openhab.binding.enigma2
  • org.openhab.binding.fht
  • org.openhab.binding.freebox
  • org.openhab.binding.fritzaha
  • org.openhab.binding.frontiersiliconradio
  • org.openhab.binding.harmonyhub
  • org.openhab.binding.hdanywhere
  • org.openhab.binding.hms
  • org.openhab.binding.hue

0 voters

  • org.openhab.binding.insteonhub
  • org.openhab.binding.isy
  • org.openhab.binding.k8055
  • org.openhab.binding.lightwaverf
  • org.openhab.binding.mailcontrol
  • org.openhab.binding.maxcube
  • org.openhab.binding.mcp23017
  • org.openhab.binding.mcp3424
  • org.openhab.binding.mpd
  • org.openhab.binding.ntp
  • org.openhab.binding.oceanic
  • org.openhab.binding.octoller

0 voters

  • org.openhab.binding.omnilink
  • org.openhab.binding.openpaths
  • org.openhab.binding.opensprinkler
  • org.openhab.binding.panstamp
  • org.openhab.binding.pioneeravr
  • org.openhab.binding.plcbus
  • org.openhab.binding.plclogo
  • org.openhab.binding.powerdoglocalapi
  • org.openhab.binding.primare
  • org.openhab.binding.pulseaudio
  • org.openhab.binding.rfxcom
  • org.openhab.binding.rme

0 voters

  • org.openhab.binding.rpircswitch
  • org.openhab.binding.s300th
  • org.openhab.binding.sagercaster
  • org.openhab.binding.sallegra
  • org.openhab.binding.samsungtv
  • org.openhab.binding.smarthomatic
  • org.openhab.binding.sonos
  • org.openhab.binding.squeezebox
  • org.openhab.binding.stiebelheatpump
  • org.openhab.binding.tacmi
  • org.openhab.binding.tivo
  • org.openhab.binding.vdr

0 voters

  • org.openhab.binding.wago
  • org.openhab.binding.wemo
  • org.openhab.binding.withings
  • org.openhab.binding.wr3223
  • org.openhab.binding.xpl
  • org.openhab.binding.yamahareceiver
  • org.openhab.binding.zibase
  • org.openhab.io.harmonyhub
  • org.openhab.io.multimedia.tts.freetts
  • org.openhab.io.multimedia.tts.googletts
  • org.openhab.io.multimedia.tts.macintalk
  • org.openhab.io.multimedia.tts.marytts

0 voters

  • org.openhab.io.multimedia.tts.speechdispatcher
  • org.openhab.io.squeezeserver
  • org.openhab.io.transport.xpl

0 voters

Since polls are limited to 12 options, I’ll compile the results when the poll has ended. Moderators… is this a limitation of Discourse, or is there a setting that could be adjusted to allow for larger polling sets?

EDIT: I’ve included 87 additional addons that were not included in the original post.

8 Likes

I think this poll is a great idea.

I use the FHT addon to control my wireless radiator valves but I don’t see it listed here. Does that mean it’s been migrated to OH2 or that it’s been missed off the list?

For the Tinkerforge binding there is a WIP for a 2.5 version from @theo.

I’ve only included OH1.x addons included in this feature.xml. If it’s not listed in the OP, then it has not an “officially” supported or has already been migrated. If their mentioned, I’ll add them to the final results.

It is listed here as a v1 binding.

1 Like

A PR for a 2.5 version of Telegram is allready available and not that far from merging.

2 Likes

It’s in the repo too… https://github.com/openhab/openhab1-addons/tree/master/bundles/binding/org.openhab.binding.fht. Hmmm. I’ll do a comparison of the repo and the feature.xml to see if there are any others. I’m not the best to answer questions about why this was done or how it was not included… but I don’t think this is normal. Maybe an OH1 maintainer could help out here?

1 Like

I understand the MQTT has a newer version but I still use the old 1.x version and I could not see that in the list. The new one still has capability gaps AFAIK and will involve some serious effort for me to migrate and I am currently not on my planned list of changes.

Regards

Paul

3 Likes

I feel a lesson approaching… there are 96 addons in the feature.xml and 217 addons in the repo. So there are a LOT of addons missing from the poll. I don’t know what the difference is between the addons in the feature.xml and the ones that are not. @kai, could you please explain why some OH1.x addons are not in the feature.xml?

The 1.x mqtt binding was marked as legacy after it was migrated to 2.x. I did not include any of the legacy addons in the poll, as they already have 2.x versions. If there there are gaps in functionality between a 1.x and 2.x addon, you should open issues so that they can be addressed. If you feel a need to discuss this, the first link in the OP is a good topic for it, or please open your own. This topic is merely to get an idea of which 1.x addons are getting the most use.

If SNMP doesn’t make the cut to OH 3; I will be very busy trying to find another solution to track phones connecting to my wireless. And before anyone asks about arping, it will not work for my infrastructure as my OH sits in a different subnet from my wireless clients

Happy to test any new developments for a SNMP OH 3 SNMP binding!

1 Like

There’s a recently merged 2.x snmp binding that you could test.

@kai, could you please explain why some OH1.x addons are not in the feature.xml?

That’s very simple: Nobody ever has tested it and confirmed that it is working with OH2 (while it is available as a bundle for OH1) and thus it has not been added to the 2.x distro. See https://www.openhab.org/docs/developer/legacy/compatibilitylayer.html#how-to-add-a-successfully-tested-1-x-add-on-to-the-distribution for details.

2 Likes

Thank you, Kai! I’ve included them in the poll now.

It’s in there now!

1 Like

EDIT:

Link to discussion with my opinion.

Vote here, discuss there…

3 Likes

This is fantastic, however I have no idea what to do/how to proceed with these; nothing that needs to go into detail here. I’m gong to do some reading and see if I can figure it out.

Excellent, thanks! The FHT binding now has at least one vote :slight_smile:

1 Like

Anybody who votes on one of these should make a PR that adds it to the distro!

1 Like

These could be getting votes from people who are still using them in OH1 though. So, only people using them in OH2 should follow the steps to get them into the distribution.

Would be nice to have a feature to create those statistics from openHAB. Either as a feature to activate or on purpose.
Of course there should be a unique id to be sent with, to prevent miscounting.
But this would mean that data is collected. It’s like the old feature “show openHAB installations on google maps” which disappeared some years ago.

2 Likes