# Development of openHAB 3.0.0 and 2.5.x **URL:** \ **Category:** Announcements\ **Created:** [January 3, 2020, 2:27pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376 "2020-01-03T14:27:13Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Kai](https://community.openhab.org/user_avatar/community.openhab.org/kai/32/116281_2.png) [@Kai](https://community.openhab.org/u/Kai)\ **Post date:** [January 3, 2020, 2:27pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/1 "2020-01-03T14:27:14Z")
All, As already briefly mentioned in my [openHAB 2.5 release post](https://community.openhab.org/t/openhab-2-5-has-been-released/87716/48), I’d like to give you an update on the further development efforts: With the 2.5 release, our master branches have switched to 3.0.0-SNAPSHOT. There are currently multiple bigger initiatives going on, such as the [code refactoring to remove the Eclipse trademark from the code](https://github.com/openhab/openhab-core/issues/1290), the [new default UI](https://github.com/openhab/openhab-webui/issues/24) as a replacement for the Paper UI and others, the [switch to Java 11](https://github.com/openhab/openhab-core/issues/1287), making the next-generation rule engine the main one, etc. As a result of those activities, the current 3.0.0 code base is not yet usable, so please refrain from trying out any 3.0.0-SNAPSHOT distro for the moment. It anyhow [does not include any add-ons](https://github.com/openhab/openhab-addons/pull/6701), so it is rather pointless. We plan to have usable snapshot builds available in a few weeks from now. Meanwhile, there is a lot of activity on the add-on development side by our gorgeous community and in order to not having to maintain two separate branches, we have created a 2.5.x branch in all add-on repos and are [asking all contributors to create their PRs against that one](https://github.com/openhab/openhab-addons/issues/6702) - with the premise that those changes are fully backward compatible. As we have also found a few bugs with the 2.5.0 distro (e.g. when [using the downloaded add-ons](https://github.com/openhab/openhab-distro/issues/1031)), the [@maintainers](https://community.openhab.org/groups/maintainers) decided that we will release a 2.5.1 distro with updated add-ons (everything that is merged in the 2.5.x branches) on January 12. A [snapshot build of 2.5.1 is already available on Jenkins](https://ci.openhab.org/view/Integration%20Builds%20(2.5.x)/job/openHAB2.5.x-Distribution/) as well as in the Artifactory snapshot linux repos for testing. The 2.5.1 distro will most likely be the last 2.5.x distro. But this is now able to always install the most current 2.5.x version of the add-ons. We will therefore continue to regularly release 2.5.2, 2.5.3, etc. releases for the add-ons, so that there is still a chance to get the latest features and fixes as a 2.5.1 distro user. This will most likely happen until summer as we then plan to switch all development (PR and merging) efforts back on master for all add-ons. Hopefully, we have some decent 3.0.0 milestone builds available by then, so that everybody, who cannot wait for any latest code changes has a chance to switch already. I hope this all makes sense to you and that it works out as planned - let’s make it happen together! 🕶 Cheers, Kai ---
**Author:** ![Bruce\_Osborne](https://community.openhab.org/user_avatar/community.openhab.org/bruce_osborne/32/38531_2.png) [@Bruce\_Osborne](https://community.openhab.org/u/Bruce_Osborne)\ **Post date:** [January 3, 2020, 2:44pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/2 "2020-01-03T14:44:44Z")
Thanks all. > [@Kai](#): > > But this is now able to always install the most current 2.5.x version of the add-ons. Is this true also for `2.5.0` or just `2.5.1`? ---
**Author:** ![olialb](https://community.openhab.org/user_avatar/community.openhab.org/olialb/32/114437_2.png) [@olialb](https://community.openhab.org/u/olialb)\ **Post date:** [January 3, 2020, 2:48pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/3 "2020-01-03T14:48:14Z")
@Kai thanks for the great overview. I think many of us look forward for the upcoming releases. Can’t wait for the next gen rule engine with jython support (!!)… Happy new year! ---
**Author:** ![hilbrand](https://community.openhab.org/user_avatar/community.openhab.org/hilbrand/32/72354_2.png) [@hilbrand](https://community.openhab.org/u/hilbrand)\ **Post date:** [January 3, 2020, 2:50pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/4 "2020-01-03T14:50:04Z")
One probably relevant addition worth mentioning: The 1.x compatibility layer has been removed from openHAB 3.0.0. @Bruce_Osborne Only 2.5.1. of the distro. In that version the changes were made to make it possible to add newer versions of the addons. ---
**Author:** ![rkrisi](https://community.openhab.org/user_avatar/community.openhab.org/rkrisi/32/68680_2.png) [@rkrisi](https://community.openhab.org/u/rkrisi)\ **Post date:** [January 3, 2020, 2:56pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/6 "2020-01-03T14:56:04Z")
> [@hilbrand](#): > > The 1.x compatibility layer has been removed from openHAB 3.0.0. I’m not a 1.x power user, I’m only using the HTTP binding. I saw earlier that there is a rather old PR for a 2.x replacement, can we expect that this will be merged when 3.0 will be out (I mean stable)? ---
**Author:** ![Bruce\_Osborne](https://community.openhab.org/user_avatar/community.openhab.org/bruce_osborne/32/38531_2.png) [@Bruce\_Osborne](https://community.openhab.org/u/Bruce_Osborne)\ **Post date:** [January 3, 2020, 3:00pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/7 "2020-01-03T15:00:48Z")
> [@ranielsen](#): > > The 1.X compatibility layer? OpenHAB v1 h=bindings, such as [Expire](https://www.openhab.org/addons/bindings/expire1/) will not function in OH3, at least natively. All the URLs for v1 bindings end in the number 1. ---
**Author:** ![petero](https://community.openhab.org/letter_avatar_proxy/v4/letter/p/d78d45/32.png) [@petero](https://community.openhab.org/u/petero)\ **Post date:** [January 3, 2020, 3:23pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/8 "2020-01-03T15:23:15Z")
Will openHAB 3.x still be built on Java8 or something newer? I.e. for the KNX add-on the underlying calimero project has upgraded to Java11 and it is annoying to have to transpile the jars to Java8 and then build my own KNX add-on. (But it can be done for anyone in the same situation: [GitHub - petero-dk/javacrosscompiler: Cross compile newer versions of Java (i.e. 11) to Java8 (and earlier)](https://github.com/petero-dk/javacrosscompiler)) ---
**Author:** ![rkrisi](https://community.openhab.org/user_avatar/community.openhab.org/rkrisi/32/68680_2.png) [@rkrisi](https://community.openhab.org/u/rkrisi)\ **Post date:** [January 3, 2020, 3:25pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/9 "2020-01-03T15:25:41Z")
> [@petero](#): > > Will openHAB 3.x still be built on Java8 or something newer? See first post by @Kai ---
**Author:** ![petero](https://community.openhab.org/letter_avatar_proxy/v4/letter/p/d78d45/32.png) [@petero](https://community.openhab.org/u/petero)\ **Post date:** [January 3, 2020, 3:31pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/10 "2020-01-03T15:31:07Z")
Thanks!, I read it twice but still missed that one. Now that I read the github issue through I can still not see if there is a definite decision on 3.0, but at least for the end of 2020 it will be Java11. ---
**Author:** ![rkrisi](https://community.openhab.org/user_avatar/community.openhab.org/rkrisi/32/68680_2.png) [@rkrisi](https://community.openhab.org/u/rkrisi)\ **Post date:** [January 3, 2020, 3:35pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/11 "2020-01-03T15:35:02Z")
I think that initial decision by the maintainers is that openHAB 3 will only work with Java 11. ---
**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\ **Post date:** [January 3, 2020, 4:06pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/12 "2020-01-03T16:06:04Z")
I have one question/point of clarification. The core of OH will be frozen at 2.5.1 which makes sense. And I understand that the core has been modified so it will support later versions (e.g. 2.5.2) of add-ons. How will the discovery and installation of these later versions of the add-ons occur? Do they need to be manually installed (i.e. download and copy the jar to the addons folder)? Should users just clear the cache periodically to force a reinstall of the add-ons, picking up the new versions? Click on something in PaperUI? Do we know the answer yet? ---
**Author:** ![ranielsen](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/c5a1d2/32.png) [@ranielsen](https://community.openhab.org/u/ranielsen)\ **Post date:** [January 3, 2020, 4:10pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/13 "2020-01-03T16:10:23Z")
> [@hilbrand](#): > > One probably relevant addition worth mentioning: The 1.x compatibility layer has been removed from openHAB 3.0.0. Is there any documentation on how to migrate 1.x bindings? I’ll try to get started on migrating InsteonPLM when I get a chance. ---
**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\ **Post date:** [January 3, 2020, 4:18pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/14 "2020-01-03T16:18:06Z")
> [@ranielsen](#): > > Is there any documentation on how to migrate 1.x bindings? > [@Tutorial: Migrating OH 1 addon to OH 2/3: preparing (1/x) to](https://community.openhab.org/t/tutorial-migrating-oh-1-addon-to-oh-2-preparing-1-x/81839): > > This tutorial is part of a series of tutorials helping with migrating openHAB 1 bindings to openHAB 2. This first tutorial describes how to get started. Step 1: Installing the IDE To start it’s best to freshly set up your development environment. For development ONLY USE JAVA 811. (openHAB 2 was 8, 3 is 11) Either install Eclipse or if you prefer VisualCode or IntelliJ. See the documentation on how to install:[https://www.openhab.org/docs/developer/#setup-the-development-environment 5](https://www.openhab.org/docs/developer/#setup-the-development-environment). This tu… ---
**Author:** ![hilbrand](https://community.openhab.org/user_avatar/community.openhab.org/hilbrand/32/72354_2.png) [@hilbrand](https://community.openhab.org/u/hilbrand)\ **Post date:** [January 3, 2020, 4:33pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/15 "2020-01-03T16:33:36Z")
Also there is a list to track migrations: > > > 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\](https://community.openhab.org/t/poll-which-oh1-x-addons-do-you-use/79121). 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 > > | Add-on | OH3 Add-on | Supported in OH2 | Poll results | Java LOC | Notes | > |--------------|---------------|-------------|--------------|----------|------------------| > | \*\*Actions\*\* |=====| =====| =====| =====| =====| > | mios | ~PR #2283~ | supported | 7 | 183 | PR closed | > | openwebif | | unsupported | 2 | 479 | | > | pebble | | supported | 4 | 215 | | > | tinkerforge | Issue #85 | unsupported | 1 | 129 | | > | weather | | unsupported | 9 | 73 | | > | \*\*Bindings\*\* | =====| =====| =====| =====| =====| > | asterisk | | unsupported | 5 | 373 | | > | cardio2e | | supported | 1 | 6540 | | > | cups | yes? | unsupported | 1 | 225 | Renamed as ipp? PR #164| > | davis | | unsupported | 0 | 2307 | | > | ddwrt | | unsupported | 1 | 456 | | > | dmx.artnet | ? | unsupported | 1 | 62 | | > | dmx.lib485 | ? | unsupported | 0 | 51 | | > | dmx.ola | ? | unsupported | | 69 | | > | ebus | | supported | 1 | 2876 | | > | fatekplc | | supported | 1 | 1437 | \[Forum topic 113085\](https://community.openhab.org/t/fatek-plc-migration-to-openhab-v3/113085)| > | fht | | unsupported | 2 | 745 | | > | freeswitch | | supported | 0 | 637 | | > | fritzaha | | unsupported | 1 | 1257 | | > | fs20 | | supported | 2 | 343 | Depends on cul transport. Supported via RFXCOM binding? | > | garadget | | supported | 4 | 752 |Can be replaced by MQTT | > | gc100ir | | supported | 0 | 1079 | | > | heatmiser | | supported | 0 | 1053 | | > | horizon | | supported | 1 | 371 | | > | intertechno | Supported via RFXCOM binding? | supported | 1 | 519 | Supported via RFXCOM binding? | > | isy | \[Branch isy-binding-new\](https://github.com/QuailAutomation/openhab2-addons/tree/isy-binding-new) | unsupported | 3 | 1078 | No PR, but this branch seems to contain work on this binding | > | jointspace | | supported | 2 | 445 | | > | k8055 | | supported | 0 | 352 | | > | koubachi | | supported | 0 | 656 | Koubachi service no longer exists. Will not be ported. | > | lightwaverf | | unsupported | 1 | 3717 | \[Forum topic 92264\](https://community.openhab.org/t/lightwaverf-new-lightwaverf-binding/92264) | > | maxcul/transport.cul | PR #9732 | supported | 4/1 | 2396 /1299 | \[Forum topic 112897\](https://community.openhab.org/t/migration-of-maxcul-oh1-binding-to-oh3/112897) > | mios | ~PR #2283~ | supported | 7 | 1923 | PR is named vera. Mios seems to be rebranded to vera?\PR closed | > | mochadx10 | | supported | 1 | 828 | | > | mystromecopower | ~PR #2756~ | supported | 1 | 639 | PR Closed | > | openenergymonitor | | supported | 5 | 791 | | > | openpaths | | unsupported | 1 | 507 | | > | owserver | | supported | 3 | 424 | | > | panasonictv | PR #11559 | supported | 8 | 214 | | > | piface | | supported | 0 | 634 | | > | plex | PR #12135 | supported | 27 | 1804 | Issue #4949, \[Forum topic 111487\](https://community.openhab.org/t/plex-binding-for-oh3-will-it-be-ported/111487/4), \[Branch: plex\](https://github.com/bigbasec/openhab-addons/tree/plex) | > | samsungac | | supported | 0 | 1145 | | > | sapp | | supported | 0 | 1942 | | > | smarthomatic | | unsupported | 1 | 2162 | | > | sonance | | supported | 0 | 444 | | > | stiebelheatpump | ~PR #3483~ | unsupported | 0 | 3228 | PR Closed | > | swegonventilation | | supported | 1 | 804 | | > | tcp | | supported | 25 | 3528 | | > | tinkerforge | \[OH2 repo theoweiss\](https://github.com/theoweiss/openhab2-addons) | unsupported | 4 | 91952 | No PR, See also: \[ThinkerForge Forum\](https://www.tinkerunity.org/forum/index.php/topic,5090.45.html)/(#85). | > | ucprelayboard| | supported | 0 | 543 | | > | wago | Supported via the modbus binding | unsupported | 0 | 626 | Supported via the modbus binding | > | weather | | supported | 31 | 3337 | | > | withings | ~PR #9154~ | unsupported | 2 | 783 | PR Closed | > | \*\*IO\*\* |=====| =====| =====| =====| =====| > | caldav | | supported | 24 | 181 | See the icalendar binding | > | gcal | | supported | 12 | 932 | | > | harmonyhub | | unsupported | 11 | 591 | | > | multimedia.tts\.freetts | | unsupported | 1 | 54 | | > | multimedia.tts\.speechdispatcher | | unsupported | 0 | 134 | | > | transport.xpl| | unsupported | 1 | 73 | This protocol is dead. Will not be ported. | > > \### 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. > > | Add-on | OH3 Add-on | Supported in OH2 | Poll results | Java LOC | Notes | > |--------------|---------------|-------------|--------------|----------|----------------------------------- | > | \*\*Actions\*\* |=====| =====| =====| =====| =====| > | ciscospark | | unsupported | 0 | 189 | | > | xpl | | unsupported | 0 | 118 | | > | \*\*Bindings\*\* |=====| =====| =====| =====| =====| > | akm868 | | unsupported | 0 | 367 | | > | configadmin | | unsupported | 0 | 245 | | > | diyonxbee | | unsupported | 0 | 519 | | > | ehealth | | unsupported | 0 | 432 | | > | em | | unsupported | 0 | 316 | No readme | > | hms | | unsupported | 0 | 198 | | > | mcp3424 | | unsupported | 0 | 342 | | > | octoller | | unsupported | 0 | 243 | | > | panstamp | | unsupported | 0 | 816 | | > | plcbus | | unsupported | 0 | 932 | | > | powerdoglocalapi | | unsupported | 0 | 532 | | > | primare | | unsupported | 0 | 1774 | | > | rpircswitch | | unsupported | 0 | 336 | | > | s300th | | unsupported | 0 | 305 | | > | sallegra | | unsupported | 0 | 377 | | > | wr3223 | \[Code wr32243\](https://github.com/frami/org.openhab.binding.wr3223)| unsupported | 0 | 1776 | frami/org.openhab.binding.wr3223 > | xpl | | unsupported | 0 | 267 | This protocol is dead. Will not be ported.| > | zibase | | unsupported | 0 | 613 | | > > \### \Migrated Add-ons\ > > This is the table with all openHAB 1 add-ons that have an official openHAB 3 version. > > | Add-on | OH3 Add-on | Feature Compatible | Poll results | Java LOC | Notes > |-----------------|------------|---------|--------------|----------|----------------- > | \*\*Actions\*\* |=====| =====| =====| =====| =====| > | astro | yes | | 34 | 131 | > | dscalarm | yes | | 4 | 111 | > | ecobee | ~PR #6823~ | | 8 | 293 | > | harmonyhub | yes | | 15 | 126 | > | homematic | yes | | 4 | 82 | > | mail | yes | | | 187 | > | mqtt | yes | | | 112 | > | prowl | ~PR #10967~ | | 2 | 129 | \[Forum topic 111478\](https://community.openhab.org/t/oh3-prowl-support/111478) > | pushbullet | yes | | | 466 | > | pushsafer | ~PR #10790~ | | 1 | 184 | > | satel | yes | | | 187 | > | squeezebox | yes | | 8 | 434 | > | telegram | ~PR #5677~ | | 47 | 369 | | > | twitter | ~PR #10241~ | | 2 | 319 | | > | xbmc | yes | | 10 | 72 | Replaced by Kodi Binding > | xmpp | yes | | 3 | 443 | > | \*\*Bindings\*\* |=====| =====| =====| =====| =====| > | alarmdecoder | ~PR #7189~ | | 3 |890 | > | anel | yes | | 3 | 907 | | > | astro | yes | | | 2563 | > | autelis | yes | | 0 | 300 | > | bticino | ~PR #6213~ | no | 0 | 2521 | Name: openwebnet, Misses Temperature Control and CEN commands | > | benqprojector| ~PR #10341~ | | 1 | 605 | | > | bluetooth | yes | | 5 | 398 | > | caldav-command | ~PR #6453~ | no | 23 | 469 | Implemented as iCal, which offers similar features, but read-only | > | caldav-personal | ~PR #6453~ | no | 32 | 606 | | > | comfoair | ~PR #7052~ | yes | 9 | 3100 | | > | cups | yes? | | 1 | 377 | Renamed as ipp? PR #164 > | daikin | yes | | 1 | 1553 | > | denon | yes | | 9 | 5233 | > | digitalstrom | yes | | 0 | 1826 | > | dmx | yes | | | 3368 | > | dscalarm | yes | | 3 | 1581 | > | dsmr | yes | | | 2121 | > | ecobee | ~PR #6823~ | |9 |6181 | > | ecotouch | ~PR #10010~ | supported | 2 | 1308 | > | ekey | ~PR #10996~| | 0 | 374 | | > | energenie | ~PR #6461~ | | 2 | 482 | > | enigma2 | ~PR #7514~ | | 3 | 520 | > | enphaseenergy| ~PR #9883~ | | 2 | 438 | Renamed enphase \[Forum topic #44449\](https://community.openhab.org/t/new-binding-enphase-envoy-solar-system-gateway/44449) | > | enocean | yes | | | 509 | > | epsonprojector | ~PR #9021~ | | 5 | 1853 | | > | exec | yes | no | | 745 | > | freebox | yes | | 0 | 625 | > | fritzboxtr064| ~PR #8523~ | | 52 | 1870 | > | gpio (io) | ~PR #1334~ | | 18 | 494 (795) | | > | harmonyhub | yes | | 14 | 786 | > | hdanywhere | yes | | 0 | 360 | > | homematic | yes | | | 450 | > | http | ~PR #8521~ | | 95 | 995 | | > | hue | yes | | 18 | 4651 | > | iec6205621meter | yes | | 1 | 732 | smartmeter binding | > | ihc | yes | | | 878 | > | insteonhub | | | 1 | 1246 | Replaced by OH1 insteonPLM | > | insteonplm | ~PR #6911~ | | 13 | 6637 | New binding is called insteon. PR merged | > | ipx800 | ~PR #5457~ | | 1 | 1397 | Renamed to GCE | > | irtrans | yes | | | 2724 | > | km200 | yes | | 2 | 855 | > | knx | yes | | | 2272 | > | lcn | ~PR #7509~ | | 1 | 6384 | > | lgtv | yes | no | 7 | 3131 | LGWebOs and LG Serial OH3 bindings use a different protocol, so might not be compatible > | mailcontrol | yes | | 3 | 1936 | > | maxcube | yes | | 2 | 634 | > | mcp23017 | yes | | 0 | 2853 | > | milight | yes | | | 342 | > | modbus | yes | | | 892 | > | mpd | ~PR #7870~ | | 2 | 869 | | > | mqtt | yes | no | | 12830 | > | mqttitude | yes | | | 1083 | > | myq | ~PR #9347~ | | 7 | 757 | Fullname is ChamberlainMyQ | > | neohub | ~PR #5952~ | | 0 | 467 | > | nest | yes | | | 415 | > | netatmo | yes | | | 2282 | > | networkhealth | yes | | | 3053 | > | networkupstools | ~PR #6192~ | | 26 | 244 | > | nibeheatpump | yes | | | 190 | > | nikobus | ~PR #6021~ | | 9 | 1109 | > | novelanheatpump | ~PR #9669~ | | 1 | 1060 | Renamed to luktronik \[Forum topic 70743\](https://community.openhab.org/t/migration-of-novelan-luxtronic-binding-to-openhab2/70743) > | ntp | yes | | 12 | 1929 | > | oceanic | yes | | 0 | 179 | > | omnilink | ~PR #8922~ | | 2 | 2293 | | > | onewire | yes | | | 820 | > | onkyo | yes | no | | 1769 | OH3 binding doesn’t support serial connection like in OH1 binding > | opensprinkler | yes | | 5 | 1515 | > | pilight | ~PR #9744~ | | 2 | 1161 | | > | pioneeravr | yes | | 2 | 277 | > | plclogo | yes | | 1 | 1266 | > | plugwise | yes | | | 2189 | > | powermax | yes | | | 3553 | > | pulseaudio | yes | | 2 | 3829 | > | pushover | ~PR #8586~ | | 30 | 669 | > | rfxcom | yes | | 4 | 1281 | > | rme | yes | | 0 | 8382 | > | rwesmarthome | yes | | | 448 | > | sagercaster | ~PR #4754~ | |0 |5542 | > | samsungtv | yes | | 13 | 2094 | > | satel | yes | | | 847 | > | serial | ~PR #8851~ | | 24 | 636 | > | snmp | yes | | 21 | 2979 | > | sonos | yes | | 7 | 668 | > | souliss | ~PR #11083~ | | 1 | 2729 | > | squeezebox | yes | | 8 | 4150 | > | squeezeserver | yes | | 0 | 1168 | Supported by squeezebox > | systeminfo | yes | | | 393 | > | tacmi | ~PR #7768~ | | 1 | 469 | > | tellstick | yes | | | 776 | > | tivo | ~PR #9302~ | | 1 | 120 | | > | upb | ~PR #6742~ | | 0 | 744 | > | urtsi | yes | | | 1658 | > | vdr | ~PR #9947~ | | 1 | 620 | Issue #9931 > | velux | ~PR #2531~ | |9 | 8494 | > | wemo | yes | | 4 | 480 | > | wol | ~PR #8336~ | | 42 | 147 | Part of network binding | > | xbmc | yes | | 11 | 1998 | Replaced by Kodi Binding | > | yamahareceiver | yes | | 5 | 577 | > | zwave | yes | | | 18948 | > | \*\*IO\*\* |=====| =====| =====| =====| =====| > | multimedia.tts.googletts | yes | | 3 | 229 | > | multimedia.tts.macintalk | yes | | 0 | 35 | > | multimedia.tts.marytts | yes | | 2 | 70 | > | transport.mqtt | yes | | 46 | 604 | > | \*\*Other\*\* |=====| =====| =====| =====| =====| > | expire | ~PR openhab/openhab-core/pull/1803~ | | 95 | 239 | Added as core framework feature | ---
**Author:** ![Bruce\_Osborne](https://community.openhab.org/user_avatar/community.openhab.org/bruce_osborne/32/38531_2.png) [@Bruce\_Osborne](https://community.openhab.org/u/Bruce_Osborne)\ **Post date:** [January 3, 2020, 4:43pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/16 "2020-01-03T16:43:04Z")
When things settle down, are there plans to add an OH3 column? ---
**Author:** ![markus7017](https://community.openhab.org/user_avatar/community.openhab.org/markus7017/32/39859_2.png) [@markus7017](https://community.openhab.org/u/markus7017)\ **Post date:** [January 3, 2020, 5:36pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/17 "2020-01-03T17:36:53Z")
I heard that OH3 add-ons will not work on 2.5.x due to namespace issues (fully removing/renaming the Eclipse smarthome components/name spaces). How do we handle that? Will the master somewhen switched to the new namespaces? How to have ongoing support for 2.5.x users? If there anything I could do to have a smooth migration? @Kai would like to see a slightly later release date for 2.5.1 so we could move the PR the 2.5.x branch and do a solid review. Maybe Jan 19 to give all of us the time to work on quality? I doubt there is or will be a good pile for the reviewers, which needs to be processed so everything gets in? ---
**Author:** ![splatch](https://community.openhab.org/user_avatar/community.openhab.org/splatch/32/33925_2.png) [@splatch](https://community.openhab.org/u/splatch)\ **Post date:** [January 3, 2020, 5:41pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/18 "2020-01-03T17:41:20Z")
> [@markus7017](#): > > I heard that OH3 add-ons will not work on 2.5.x due to namespace issues (fully removing/renaming the Eclipse smarthome components/name spaces). > > How do we handle that? Will the master somewhen switched to the new namespaces? How to have ongoing support for 2.5.x users? If there anything I could do to have a smooth migration? Technically speaking it is possible in similar way as it was made for OH1 - by providing compatibility layer. We know what types were in OH2 and what packages are present in OH3. Mapping can be done at the build time or runtime by basic adapter types which will adapt `org.eclipse.smarthome` package to `org.openhab.core`. It can be also semi-automated by basic IDE support falling into category of “migrate package” or “migrate jar”, depending if you are on IntelliJ or Eclipse. ---
**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\ **Post date:** [January 3, 2020, 5:57pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/19 "2020-01-03T17:57:21Z")
> [@splatch](#): > > Mapping can be done at the build time or runtime by basic adapter types which will adapt `org.eclipse.smarthome` package to `org.openhab.core` . My understanding is we are obligated to remove all references to org.eclipse.smarthome. Wouldn’t that obligation also apply to such an adapter? ---
**Author:** ![Bruce\_Osborne](https://community.openhab.org/user_avatar/community.openhab.org/bruce_osborne/32/38531_2.png) [@Bruce\_Osborne](https://community.openhab.org/u/Bruce_Osborne)\ **Post date:** [January 3, 2020, 6:07pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/20 "2020-01-03T18:07:46Z")
> [@rlkoshak](#): > > My understanding is we are obligated to remove all references to org.eclipse.smarthome I would guess that would need to be arranged through the Eclipse Foundation? ---
**Author:** ![hilbrand](https://community.openhab.org/user_avatar/community.openhab.org/hilbrand/32/72354_2.png) [@hilbrand](https://community.openhab.org/u/hilbrand)\ **Post date:** [January 3, 2020, 6:25pm UTC](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376/21 "2020-01-03T18:25:08Z")
> [@Bruce\_Osborne](#): > > When things settle down, are there plans to add an OH3 column? No. The table is only for oh1 addons. > [@markus7017](#): > > I heard that OH3 add-ons will not work on 2.5.x due to namespace issues That is correct. But that has no effect on the configuration. So a user can simply upgrade openHAB and it would still work (not taking into account other changes) > [@markus7017](#): > > Will the master somewhen switched to the new namespaces? Master has already been migrated, see the post. At some point oh2 will be migrated to oh3 most likely with automated scripting. > [@markus7017](#): > > How to have ongoing support for 2.5.x users? This was also addressed in the post. > [@markus7017](#): > > would like to see a slightly later release date for 2.5.1 There will be other releases, see post, so that would not be a reason to postpone the release. > [@splatch](#): > > Technically speaking it is possible in similar way as it was made for OH1 - by providing compatibility layer. Even if technically possible there is no intention to do such thing, and because it’s only the namespace, not a change of interface change like with oh1 it relative easy to migrate a oh2 binding to oh3, unlike with oh1. Actual the code of core has been migrated with simple script. So adding all kinds of ide support is far more work than simply migrating a binding. [Next page](https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376.md?page=2)