Closed Hilbrand closed 9 months ago
@delid4ve the binding is unsupported as mentioned above, and explained what it means that its unsupported.
@delid4ve the binding is unsupported as mentioned above, and explained what it means that its unsupported.
Apologies, just remember seeing it in the Ui in 2.something when I first started my journey so didn’t even realise it had actually been marked as unsupported
There is a migrated version of the wr3223 binding. It is in a separate repository https://github.com/frami/org.openhab.binding.wr3223 Is it possible to add a link in the notes of the migration list? The reason for the separate repository is, for more flexibility and I think there are not so many users which using this binding.
No List has no Addon FATEK_PLC is there any chance that it will be in OpenHab3
@mrudowicz based on the current information on this list: No. The openHAB forum is a better place to ask this question.
Actually: Yes there is a chance, if you develop the binding and it follows all the guidelines then it will most likely make it in. Chances are actually pretty high that it will make it in. ;)
Hi @mrudowicz I'm author of FatekPLC binding, I thinking about migrate it. Lets start topic on forum to track progress.
Hi @mrudowicz I'm author of FatekPLC binding, I thinking about migrate it. Lets start topic on forum to track progress.
Super Mam nadzieje ze uda Ci sięszybko ogarnac dodatek do v3. sporo ludzi ma Fateka :)
For your information, Matthias Klocke wrote a vdr2 binding. See https://community.openhab.org/t/vdr-binding/10839/24 for details.
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/collection-of-binding-requests/113854/2
Further details to vdr2/vdr3 Binding:
LightwaveRF will shortly be supported in 2.5x and 3.x. I'm currently adding in gen1 local support (openhab-v1 addon - although a new api) to my working gen2 (cloud) binding. Should be ready to submit in a couple of weeks. Thread can be monitored here:
https://community.openhab.org/t/lightwaverf-new-lightwaverf-binding/92264
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: Is it possible to move the binding davis from Unused Add-ons to Add-ons to Migrate?
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.
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 Migrated Add-ons: table with all add-ons that have an official openHAB 3 version
is strictly necessary. (??) As the list of OH 3 addons is self evident.
@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.
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
supported
in 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 LOC
is the number of Lines of Code of the add-on. This can give an indication on the complexity of the binding.The column
Feature Compatible
in 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 closed
.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.