openHAB 1 addon compatibility overview with openHAB 3 #6179
Comments
Hilbrand
added
the
oh1 migration
|
squeezeserver is covered by squeezebox. I'm not aware of a special squeezebox2 action but only squeezebox1 action. |
|
@udo1toni Thanks for reporting. I've updated the table and moved squeeseserver to the 2nd table.
Do you mean the action is supported in the squeezebox2 binding or if there is still some functionality missing in the squeezebox2 binding? |
|
For v1 [bticino], a new openHAB 2 version is being finalized, called [openwebnet]. See #5195 |
|
That's an impressive table! I don't think the poll result can be mapped directly to user value. Otherwise we would know what migrations would yield the most value given the complexity. ;-) It does give some sort of idea though. |
afaik there is no action with squeezebox2. But there is a squeezebox1 action. There are 3 oh1 jar files, action.squeezebox binding.squeezebox and io.squeezeserver. |
|
@mvalla Thanks for reporting. I've updated the table and also added
@udo1toni I checked to documentation of both 1 and 2 and it seems the actions of 1 are covered by the 2 version. By using item directly and an AudioSink implementation. So I assume the OH2 version is feature compatible. |
|
What is missing in MQTTv2? |
|
@J-N-K I thought I'd seen something about not being able to use mqtt binding connect to openHAB instances as an eventbus: https://www.openhab.org/v2.3/addons/bindings/mqtt1/#event-bus-binding-configuration. But I might be wrong about this. |
|
At least mqtt2 has some restrictions to mqtt1, for example there is no option to send different topics for different commands of the same channel (you'll need this to control tasmota 6.6.015+ roller shutter feature) |
|
espeasy has adapted its mqtt usage. I remember that I have talked to the tasmota guys as well. mqttv2 should not support broken mqtt usage patterns imo. |
|
I'm completely on your side ;) @davidgraeff |
|
Guys, Ecobee has an action 1.x binding also; not seeing it in the Action section/column. Best, Jay |
|
There's a replacement for IPX800 v1 binding : PR 5457 |
|
@jaywiseman1971 The Ecobee action is mentioned in the first table. Did I miss anything? @clinique Thanks for mention it. I've updated the table and added the oh1 label to the pr. |
|
Hi @Hilbrand, I thought the 2 tables were broken out as addon and addon action bindings. Just wanted to make clear that ecobee has 2 different bindings. Sorry for the confusion. Best, Jay. |
|
XMPPClient Binding (https://github.com/openhab/openhab2-addons/tree/master/bundles/org.openhab.binding.xmppclient) is replacement for OH1 xmpp action. |
|
Please don't press the X on these issues because it will unpin them and then no one will see them @markus7017. They aren't dismissable like cookie popups. 😉 |
|
FYI I updated the table to include PR #6823 for the Ecobee binding. |
|
Could someone include PR #7052 for the ComfoAir binding? |
|
Updated table to add new PRs for comfoair and alarmdecoder. |
|
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/oh2-oh3-older-bindings-no-longer-supported/116084/7 |
|
Regarding 'davis' binding: Meteostick is not an alternative because it requires a special hardware dongle and is not able to connect to a Davis data logger directly via RS-232 or USB. |
|
why souliss pr 10034 result as closed ? |
|
Because it used to refer to PR #4945 which was closed and most likely when the new PR was added it was simply forgotten to remove that. |
Ok, i must rebase due to errors with git commands. So now it's ready to continue approval flow. Thanks ! |
|
Added new ekey binding contribution (PR #10996) to the list in the first post. |
|
benqprojector can be moved to the migrated list |
|
@Hilbrand many thanks for the issue, and the work behind it. On a point of order, I am not sure that the table |
|
@andrewfg The migrated list contains only add-ons that were available as openHAB 1 add-on. Initially it was to track if a migrated add-on was feature compatible with the then openHAB 2 add-on. Later, when other openHAB 1 add-ons were migrated and moved to the list, the original PR link was added. That way people could easily track back where the migrated add-on came from or it contains additional background information related that might be relevant for the migrated add-on with regards to the original openHAB 1 add-on. (P.s. I've added 'openHAB 1' to the title of the table to make it more clear this is a list of openHAB 1 add-ons). |
|
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/openhab-3-fs20-binding/146285/3 |
|
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/is-the-max-system-still-usable-in-2023/150615/3 |
|
As openHAB 1 and later on openhab 2 with the compatibility layer is long time history, i propose to close this issue. If there are still addons not migrated, i suppose there is no need for it or no one is willing to do so. |
and others
This issue contains an overview of all openHAB 1 add-ons and how/if there is an openHAB 3 version.
Disclaimer: This list is not a planning or to do list. It just gives an overview of the status of migrations or known other new versions bindings.
If you want to know if a binding will be available in openHAB 3 and it's not mentioned on the list ask on the openHAB forum. Use the comments to report new or changed entries to the list.
There are 3 tables. The first table contains the openHAB 1 add-ons with no (official) openHAB 3 version, but have been voted on in the poll or are being worked on. The table contains the links to the work-in-progress if known. The second table is with unsupported openHAB 1 bindings that have not be voted on. These bindings have potential very few users and therefor the chance someone will migrate it to openHAB 3 is very low. The third table is with openHAB 1 add-ons that have a known openHAB 3 replacement. When an openHAB 1 binding from the first 2 tables has been migrated it's moved to third table.
In the lists the persistence add-ons are not included because separate work has been done: PR #5275.
The column
supportedin the table means if the add-on was officially supported in openHAB 2. This means it's included in the feature file and known to work with openHAB 2 and show up in PaperUI when legacy mode is activated. If not supported it still might work, but it needs to be installed manually.The poll results are from the (closed) poll from the openHAB forum: poll-which-oh1-x-addons-do-you-use. Some add-ons have no poll results because those have an openHAB 2 variant and were not in the poll.
The column
Java LOCis the number of Lines of Code of the add-on. This can give an indication on the complexity of the binding.The column
Feature Compatiblein the last table mentions if the openHAB 3 bindings lacks some features that where part of the openHAB 1 binding.This information is compiled to have an overview of the differences and compatibility of different openHAB add-on versions. If something is missing or changed please comment or update this list. If you have or use an openHAB 3 binding but it doesn't have the same features as the openHAB 1 version please also report.
Add-ons to Migrate
PR #2283PR #2283PR closed
PR #2756PR #3483PR #9154.freetts
.speechdispatcher
Unused Add-ons
This is the table with all openHAB 1 add-ons that have no openHAB 3 replacement, are not part of legacy and had zero votes. It's uncertain if these bindings are still used. If they are used they belong in the table above.
Migrated Add-ons
This is the table with all openHAB 1 add-ons that have an official openHAB 3 version.
PR #6823PR #10967PR #10790PR #5677PR #10241PR #7189PR #6213PR #10341PR #6453PR #6453PR #7052PR #6823PR #10010PR #10996PR #6461PR #7514PR #9883PR #9021PR #8523PR #1334PR #8521PR #6911PR #5457PR #7509PR #7870PR #9347PR #5952PR #6192PR #6021PR #9669PR #8922PR #9744PR #8586PR #4754PR #8851PR #11083PR #7768PR #9302PR #6742PR #9947PR #2531PR #8336PR openhab/openhab-core/pull/1803The text was updated successfully, but these errors were encountered: