openHAB Milestone builds

[sihui]

@fifo

I imagine that I could just dump the binding in the addon folders as I did in the past

Yes.

@fifo

but I can’t find it.

https://ci.openhab.org/job/openHAB2-Bundles/org.openhab.binding$org.openhab.binding.zwave/

[fifo (Hector G)]

@sihui

ould just dump the binding in the addon folders as I did in the past

Sweet thanks a million!

I ran into an issue where the latest .jar wouldn’t work after uninstalling the zwave binding, putting the new .jar in the addons folder and restarting. In case anyone runs into this error in the openhab.log…“Unresolved requirement: Import-Package: com.thoughtworks.xstream;”

Here is the Fix

[Dan (Dan Demento)]

I can understand both maintainers and users…

What I can’t understand are words like “you have to be patient - we don’t get paid”

I worked with @milhouse to debug the squeezebox binding while I was on unstable 2.5.0
after updating I was lucky things work like expected. But after 2.5.0.M1 the complete MQTT Binding stopped working. This is an essentually part of my home automation. So I had switch back to the 2.4.0stable release.

But now I had to get the new binding working again… so I had to deal with karaf to implement only the updated binding to the 2.4.0.

So not everything is working fine with the so called ‘stable’ version…

The point is: I’m able to do stuff like this, but I think a user who is not familar with programming and code or the installation of a single binding gets stuck at this point and is maybe a little confused…

And no one wants to wait months for a fixed release - no matter if the maintainers are paid or not.

So if we want satisfied users, in my eyes we should provide new versions of older releases and add (tested & working) things to provide functioning changes to not so crafty folks.

Just a thought…

[rlkoshak (Rich Koshak)]

@Dan

2.5.0.M1 the complete MQTT Binding stopped working

This is news. I’m using both versions of mqtt binding and have no problems. Did you file an issue?

[xAPPO (Kevin Hawkins)]

Eagerly awaiting M2 … as I think are many others.

With MQTT and homie support uncertainties in M1 it’s all a bit uncertain as to what is fixed and what isn’t.

[Dan (Dan Demento)]

@rlkoshak

This is news. I’m using both versions of mqtt binding and have no problems. Did you file an issue?

Ooops Sorry! I was mistaking it was 2.5.0~S1566-1 (Build #1566) discussed here… my fault…
In my memories it was 2.5.0.M1 …sorry again for my brainsalad

So please ignore my above post…

[David_Graeff]

I have a ton of automated tests for Mqtt to make sure the binding works in all official releases (milestone + point release). I cannot guarantee a working state for snapshots because other gears are shifting too, like the buildsystem as a recent example.

I’m already talking to various people about having bindings with their own release schedule. That cannot happen before 3.0 unfortunately.

[KidSquid (The Squid)]

Just wanted to check in and see if there was an updated ETA on 2.5 M2? I remember seeing a post a couple of weeks ago indicating that the new build system was nearing completion.

I need to make a jump and would like to jump forward to 2.5 M2.

Thanks,

Squid

[Kai (Kai Kreuzer)]

Just track https://github.com/openhab/openhab-distro/issues/866 and you’ll be always up to date!

[gozilla01 (Michele)]

@Kai

Just track https://github.com/openhab/openhab-distro/issues/866 and you’ll be always up to date!

Issue 886 is closed.
It would be nice to know what’s missing to publish a new version.

[5iver (Scott Rushworth)]

I tried to get this going, but there have been very few responses…

Preparation for 2.5M2

The 2.5M2 release has been held up for several reasons. The main one has been the actual ability to build the release, but this has just been resolved (). However, there’s still the question of whether 2.5M2 is ready to be released. There have been many changes since 2.5M1, so I thought it would be good timing to get a post going with a live list of the current major issues that the testers in the community feel should be addressed before the release, as well as a list of new feat…

[dbadia]

@Kai

Note that the update script now also supports the milestones , so if you are not using apt, but the zip distribution, you can easily switch between different versions.

What is the syntax to upgrade to 2.5.0.M1?
I tried passing 2.5.0.M1 and 2.5.0-M1 but the script fails:

openhab@pi-openhab ➜  sudo ./runtime/bin/update 2.5.0.M1

#########################################
       openHAB 2.x.x update script
#########################################

Making Temporary Directory
Downloading openHAB 2.5.0.M1...

curl: (22) The requested URL returned error: 404 Not Found
Download failed, version 2.5.0.M1 does not exist.
If you believe this to be an error, please check the openHAB website. (www.openhab.org)

[sberer (Stephan Berer)]

Can someone estimate the release date for the 2.5 version?

[rlkoshak (Rich Koshak)]

Not at this time. There was a massive change to the build system that didn’t go smoothly. There was also the big merge of ESH back into OH. I believe the developers are currently working down a bunch of bugs that have been discovered to get to a more stable state before they make another milestone release.

Because of the lack of milestone releases, I don’t know if they plan on trying to stick to the roughly every six months release cycle for point releases.

[Bruce_Osborne]

@rlkoshak

Because of the lack of milestone releases, I don’t know if they plan on trying to stick to the roughly every six months release cycle for point releases.

I personally would rather they keep working toward a stable release rather than rushing to meet an artificial deadline.

[sihui]

@dbadia

What is the syntax to upgrade to 2.5.0.M1?

You need to switch to the testing repo:

openHAB on Linux

For manual installation just dl, unzip and put your config back in.

[Kai (Kai Kreuzer)]

I don’t know if they plan on trying to stick to the roughly every six months release cycle for point releases.

I would have liked to, but we already missed that - so it’s rather gonna be late summer. But as others said: Top priority is to get decent milestones build again. After this, we can decide on a release date.

You need to switch to the testing repo

This is only relevant for apt, but @dbadia is asking for the “plain” update script.
@dbadia: sudo ./runtime/bin/update 2.5.0.M1 is the correct version and it works for me. Not sure, why you get a 404… The requested url is https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/distro/openhab/2.5.0.M1/openhab-2.5.0.M1.zip, can you check whether you can reach it manually?

[dbadia]

@Kai

. Not sure, why you get a 404… The requested url is https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/distro/openhab/2.5.0.M1/openhab-2.5.0.M1.zip , can you check whether you can reach it manually?

I am able to access it manually from the server. I downloaded 2.5.0.M1 manually and diffed the update script from the zip to the one in my install. My update script had bintray instead of jfrog. Copied the new script over and the update ran OK

[peterhoeg]

I mentioned point releases over here Development and release process - changes to stable branches (apologies for cross posting if that isn’t allowed), but this seems to be the more relevant thread.

So we have a case now where the much improved mqtt support in 2.4 actually doesn’t work with Homie devices after an OH restart - MQTT 2.4 binding: Items go to UNDEF after reboot. I understand that the whole build system has seen significant changes due to ESH being phased out, but the fix for Homie devices is already in master and seems like probably the most important fix to get out.

Is it realistic to get such changes backported to 2.4.1 and a release cut? I am sure there are plenty of people who would very much prefer to stay on stable but still get fixes in.

[Bruce_Osborne]

Couldn’t people just use the newer binding?
I am running 2.5M1 with a couple of snapshot version bindings.
I think 2.5M2 (or 2.5 Release?) is pretty close anyway.