# openHAB 2.5.x Patch Releases

**URL:** <https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248>\
**Category:** Announcements\
**Created:** [January 12, 2020, 8:01pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248 "2020-01-12T20:01:04Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![Flippy](https://community.openhab.org/user_avatar/community.openhab.org/flippy/32/36249_2.png) [@Flippy](https://community.openhab.org/u/Flippy)\
**Post date:** [January 13, 2020, 7:28pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/43 "2020-01-13T19:28:32Z")

</div>

Getting error on Tellstick Binding after update. Tryed posting elswhere on forum but no answers.  
Error is:  
UNINITIALIZED - HANDLER\_INITIALIZING\_ERROR

Was working fine before update.

Please help 🙂

---

<div class="post-metadata">

**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 14, 2020, 2:29pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/45 "2020-01-14T14:29:00Z")

</div>

Also the Mail binding doesn’t really want to work as it before…

```php
'sendMail' is not a member of 'org.eclipse.smarthome.core.thing.binding.ThingActions'

```

---

<div class="post-metadata">

**Author:** ![boris03](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/5daacb/32.png) [@boris03](https://community.openhab.org/u/boris03)\
**Post date:** [January 14, 2020, 7:22pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/46 "2020-01-14T19:22:52Z")

</div>

Sorry to ask but I don’t really understand the new update procedure.  
I am on 2.4 stable, do I need to get on 2.5 and after on 2.5.x or how does that work now?

---

<div class="post-metadata">

**Author:** ![rpwong](https://community.openhab.org/user_avatar/community.openhab.org/rpwong/32/36036_2.png) [@rpwong](https://community.openhab.org/u/rpwong)\
**Post date:** [January 15, 2020, 5:17am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/47 "2020-01-15T05:17:32Z")

</div>

Upgrade to the latest stable release and you’ll get 2.5.1.2. The download wasn’t working on Monday, but it worked for me yesterday.

---

<div class="post-metadata">

**Author:** ![sidamos](https://community.openhab.org/letter_avatar_proxy/v4/letter/s/ba9def/32.png) [@sidamos](https://community.openhab.org/u/sidamos)\
**Post date:** [January 22, 2020, 5:52pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/48 "2020-01-22T17:52:20Z")

</div>

When I do a manual upgrade, I have to specify a version number. So I specified 2.5.1. How do I know about newer sub releases like 2.5.1.2, so that I can specify that?

One other thing, which is happening for 2.5.0 and 2.5.1 for me:  
After stop, clear cache and tmp and restart (which is also happening during an upgrade), it does not work. A lot of items are not created and therefore a lot of rules fail. Also, seems like a lot of bindings are not being started.  
Then I shutdown and start a 2nd time, then everything is OK except the Nest binding (unknown/offline things).  
Then I shutdown and start a 3rd time, then everything works.

---

<div class="post-metadata">

**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 22, 2020, 6:09pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/49 "2020-01-22T18:09:36Z")

</div>

> [@sidamos](#):
>
> A lot of items are not created and therefore a lot of rules fail. Also, seems like a lot of bindings are not being started.

That’s a known problem. There is an issue open for it but no fix. I can’t explain the Nest issue though. That seems different.

---

<div class="post-metadata">

**Author:** ![halloween](https://community.openhab.org/user_avatar/community.openhab.org/halloween/32/7493_2.png) [@halloween](https://community.openhab.org/u/halloween)\
**Post date:** [January 29, 2020, 7:11am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/50 "2020-01-29T07:11:59Z")

</div>

I´m on snapshot-update channel and i updated some time ago, now i´m on 2.5.1

I think, when i do an apt-get update & upgrade, i will switch to oh 3 ?

How can i prevent this? I want to stay on the latest snapshots (or latest stable with the updates, which will be provided to 2.5 in the future) - but only on 2.5.x

---

<div class="post-metadata">

**Author:** ![Saracen](https://community.openhab.org/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@Saracen](https://community.openhab.org/u/Saracen)\
**Post date:** [January 29, 2020, 8:11am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/51 "2020-01-29T08:11:39Z")

</div>

> [@sidamos](#):
>
> everything is OK except the Nest binding (unknown/offline things).  
> Then I shutdown and start a 3rd time, then everything works.

I had the same problem with the Nest Binding and Nest things being offline.  
Multiple restarts alone sorting it out.  
My Mihome binding things also behaved in the same way so I decided it was probably nothing specific to the Nest binding but just part of the erratic up-grade restart behaviour.

---

<div class="post-metadata">

**Author:** ![HaKuNa](https://community.openhab.org/letter_avatar_proxy/v4/letter/h/c77e96/32.png) [@HaKuNa](https://community.openhab.org/u/HaKuNa)\
**Post date:** [January 29, 2020, 9:21am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/52 "2020-01-29T09:21:18Z")

</div>

Im not using debian packages (I’m on CentOS) but i guess you can do it a similiar way as I’ve done it,  
I just replaced the content in the repo file.

replace the content in “/etc/apt/sources.list.d/openhab2.list”

```auto
deb https://openhab.jfrog.io/openhab/openhab-linuxpkg unstable main

```

with

```auto
deb https://dl.bintray.com/openhab/apt-repo2 stable main

```

---

<div class="post-metadata">

**Author:** ![Benjy](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/eada6e/32.png) [@Benjy](https://community.openhab.org/u/Benjy)\
**Post date:** [January 29, 2020, 12:49pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/53 "2020-01-29T12:49:31Z")

</div>

For the time-being, you won’t automatically switch. (There aren’t any Linux packages for OH 3.x as of yet).

When the packages are ready, we will be providing `openhab` snapshot packages which will be set to ‘conflict’ with `openhab2` packages. Meaning that you’ll have to specify to install with `apt` or `yum` to move over. This will uninstall `openhab2` (keeping configuration files) and install `openhab` 3.x on top.

---

<div class="post-metadata">

**Author:** ![HaKuNa](https://community.openhab.org/letter_avatar_proxy/v4/letter/h/c77e96/32.png) [@HaKuNa](https://community.openhab.org/u/HaKuNa)\
**Post date:** [January 29, 2020, 1:22pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/54 "2020-01-29T13:22:20Z")

</div>

But if @halloween want’s updates for the current 2.5 release (e.g. 2.5.1-2) then it would make sense to change the URL in the repo file, correct ?

---

<div class="post-metadata">

**Author:** ![Benjy](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/eada6e/32.png) [@Benjy](https://community.openhab.org/u/Benjy)\
**Post date:** [January 29, 2020, 1:32pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/55 "2020-01-29T13:32:20Z")

</div>

Well, the most appropriate URL for stable releases is the repo you mention, but the version is available from the unstable repo too. New releases of `openhab2-addons` will appear as snapshots in `unstable` and as full releases in both `stable` and `unstable`.

---

<div class="post-metadata">

**Author:** ![michel53](https://community.openhab.org/user_avatar/community.openhab.org/michel53/32/10303_2.png) [@michel53](https://community.openhab.org/u/michel53)\
**Post date:** [February 14, 2020, 10:22am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/56 "2020-02-14T10:22:49Z")

</div>

I’m a little bit confused.  
From  
[https://ci.openhab.org/view/Integration%20Builds%20(2.5.x)/job/openHAB-Distribution/](https://ci.openhab.org/view/Integration%20Builds%20(2.5.x)/job/openHAB-Distribution/)  
we already have 2.5.2-snapshot.  
But I am unable to get it via openhabian or via  
sudo apt-get update/upgrade.  
It always tells me I am already on the newest version that is indicated as 2.5.1-2 (Release Build).  
I would especially being interested in the zwave fixes.  
Any ideas?

---

<div class="post-metadata">

**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:** [February 14, 2020, 10:58am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/57 "2020-02-14T10:58:21Z")

</div>

> [@michel53](#):
>
> But I am unable to get it via openhabian or via  
> sudo apt-get update/upgrade

There have been usually 3 different OH versions at any one time.

Stable. The current version is 2.5.1  
Testing or Milestone. There is not a current release now.  
Unstable or Snapshot. There are currently 2.5.2 snapshots sometimes released daily.

Testing snapshots are not expected to be fully functional. They are designed for integrated testing for developers with issues reported to GitHub.

Milestone releases aIm to be fully functional and are designed for wider testing. As a version matures there are sometimes Release Candidates here too.

Stable releases are fully functional designed fir everyday use.

If you need just the zwave binding there is a Zigbee and zwave update script here to make installation easier.

---

<div class="post-metadata">

**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:** [February 20, 2020, 7:34am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/58 "2020-02-20T07:34:20Z")

</div>

All, we have just published the patch release 2.5.2 - see [its release page](https://github.com/openhab/openhab-distro/releases/tag/2.5.2) for details!

In constrast to the original plan stated above, there is again a distro 2.5.2 available, although the distro itself is more or less identical to version 2.5.1 since all changes only concern the add-ons.

This also means that the 2.5.2 patches are directly available to any 2.5.1 distro installation as well without doing a distro update. If you install new add-ons - or you delete the cache and have add-ons reinstalled - the distro will pick the latest patch version of the add-on.

**IMPORTANT NOTICE TO USERS OF THE EXEC BINDING:**  
Due to [this security advisory](https://github.com/openhab/openhab-addons/security/advisories/GHSA-w698-693g-23hv), the exec binding requires to have a whitelist of allowed commands to execute. Note that when updating the exec binding to version 2.5.2, it will stop functioning until you provide such a whitelist. Please see the [binding documentation](https://github.com/openhab/openhab-addons/blob/2.5.x/bundles/org.openhab.binding.exec/README.md#binding-configuration) for details and also check [this post](https://community.openhab.org/t/security-limitations-in-2-5-2-exec-binding/93191/72) for a detailed how to.

---

<div class="post-metadata">

**Author:** ![mstormi](https://community.openhab.org/user_avatar/community.openhab.org/mstormi/32/55857_2.png) [@mstormi](https://community.openhab.org/u/mstormi)\
**Post date:** [February 20, 2020, 10:50am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/59 "2020-02-20T10:50:39Z")

</div>

9 posts were split to a new topic: [Security limitations in 2.5.2 exec binding](https://community.openhab.org/t/security-limitations-in-2-5-2-exec-binding/93191)

---

<div class="post-metadata">

**Author:** ![boris03](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/5daacb/32.png) [@boris03](https://community.openhab.org/u/boris03)\
**Post date:** [February 20, 2020, 12:01pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/61 "2020-02-20T12:01:10Z")

</div>

Because I was a bit confused how to update from 2.4 stable to 2.5 stable I was waiting until 2.5 is really stable. I guess now with 2.5.2 it is.  
How do I get now that 2.5.2 correctly installed, just via the GUI?

---

<div class="post-metadata">

**Author:** ![5iver](https://community.openhab.org/user_avatar/community.openhab.org/5iver/32/21201_2.png) [@5iver](https://community.openhab.org/u/5iver)\
**Post date:** [February 20, 2020, 1:26pm UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/62 "2020-02-20T13:26:12Z")

</div>

Thank you, Kai! Will there be a separate announcement for 1.x addons? (nudge)

---

<div class="post-metadata">

**Author:** ![mstormi](https://community.openhab.org/user_avatar/community.openhab.org/mstormi/32/55857_2.png) [@mstormi](https://community.openhab.org/u/mstormi)\
**Post date:** [February 21, 2020, 8:27am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/63 "2020-02-21T08:27:20Z")

</div>

3 posts were merged into an existing topic: [Security limitations in 2.5.2 exec binding](https://community.openhab.org/t/security-limitations-in-2-5-2-exec-binding/93191/29)

---

<div class="post-metadata">

**Author:** ![ysc](https://community.openhab.org/letter_avatar_proxy/v4/letter/y/e480ec/32.png) [@ysc](https://community.openhab.org/u/ysc)\
**Post date:** [February 21, 2020, 5:01am UTC](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248/65 "2020-02-21T05:01:11Z")

</div>

Regarding the security vulnerability: it might be interesting to mention that following an initative by the architecture council, openHAB now has a [Security Policy](https://github.com/openhab/.github/security/policy) and participates in the Common Vulnerabilities and Exposures (CVE) program. You can report vulnerabilities to [security@openhab.org](mailto:security@openhab.org) and they will be discussed privately until a security advisory and CVE are eventually published.

This remote code execution vulnerability ([CVE-2020-5242](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5242)) involving the exec addons is actually pretty nasty so now that it’s out there, all users are strongly advised to upgrade to 2.5.2 whenever possible, even if you don’t use the exec binding or transformation.

[Previous page](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248.md?page=2)

[Next page](https://community.openhab.org/t/openhab-2-5-x-patch-releases/90248.md?page=4)
