Hi all
I am on build 2.2 and everything is stable and working.
There is an old saying “If it’s not broken don’t fix it”.
That is why I have held of updating to build 2.3.
My question is:
Can I go straight from build 2.2 to 2.4/2.5/2.6 when it is available?
Kindest Regards
Mark
Theoretically you should be able to jump from 2.2 to 2.4. in practice the number of small breaking changes will be larger so it might be a bit more work on your part to adjust to those changes than it would be for someone only moving to the next version.
Be sure to review the changes in all the versions in-between with particular attention paid to breaking changes.
Thank you for your reply.
I think the new milestone builds are great! Many Thanks!
Would it be possible to provide maven artifacts as well? I would be particularly interested in the ESH artifacts.
I develop my OpenHab rules in Groovy and use the ESH sources in my IDE for auto & code completion.
I have good news for you - all Maven artifacts are already available on https://openhab.jfrog.io/openhab/libs-milestone-local/
A new milestone 2.4.0.M4 is now available!
It is available for direct download as well as published in the linux testing repos.
Major technical changes are the Karaf upgrade to 4.2.1 and the Xtext upgrade to 2.14. For the functional changes please see the change log.
If you haven’t already upgraded to the new z-wave binding, it’s included in this milestone, right? (If I read the changelog correctly) Will be a breaking change in that case.
Yep, that is correct.
Works like a charm! Cheers!
I just upgraded to M4 (from a snapshot around the time of M3) and I’ve got a strange new problem, just like to know (before I file a bug) if I’m the only one. All output in the Karaf console is kinda screwed up. It looks like it there are no line breaks, no matter what command I run I get the output as one great blob, making it very hard to read.
Just pasting some lines to show you what I mean:
openhab> log:tail
11:00:10.872 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'Mysbelysning_allmanutrymmen' received command OFF
11:00:10.879 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'FonsterlamporVardagsrum' received command OFF
11:00:10.893 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'EllasFonsterlampa' received command OFF
(although it really looks much better when pasted here than it actually does in the console)
Unfortunately a known issue, but only for ssh connections, see https://github.com/openhab/openhab-distro/issues/764.
To work around this, you can SSH in your terminal and run the client script. Second bullet here…
Ah, nice! Thought I would have to live with trying to read all that mashed stuff until next Karaf 
Is anyone else seeing an issue with charts? All my historical series appears to be gone after the upgrade, extending the current value “backwards” (I.e. the current value is updated correctly, but “drags” a flatline up/down, rather than generating a trend over time). I’m using the mapdb persistence if that makes a difference.
According to this commit it seems adding a new milestone to openhab-docker is not done automatically.
I still hope somebody finds the time. 
Typo? Mapdb only stores the last value, how do you generate charts with that?
The mapdb Persistence Service is based on simple key-value store that only saves the last value.
OS: Debian 9.5 Stretch
Die folgenden Pakete werden aktualisiert (Upgrade):
openhab2
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Es müssen noch 0 B von 74,8 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 6.419 kB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
(Lese Datenbank ... 154397 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../openhab2_2.4.0~M4-1_all.deb ...
: not foundkg/info/openhab2.prerm: 2: /etc/default/openhab2:
dpkg: Warnung: Unterprozess altes pre-removal-Skript gab den Fehlerwert 127 zurück
dpkg: stattdessen wird Skript aus dem neuen Paket probiert ...
: not foundkg/tmp.ci/prerm: 2: /etc/default/openhab2:
dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/openhab2_2.4.0~M4-1_all.deb (--unpack):
Unterprozess neues pre-removal-Skript gab den Fehlerwert 127 zurück
: not foundkg/info/openhab2.postinst: 2: /etc/default/openhab2:
dpkg: Fehler beim Aufräumen:
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück
Fehler traten auf beim Bearbeiten von:
/var/cache/apt/archives/openhab2_2.4.0~M4-1_all.deb
I think I know the answer, but just in case… Is jumping between milestones and releases easy as long as I only go forward? As easy as a few apt or dpkg commands? Or are caveats and gotchas likely to arise?
I’m struggling to imagine that upgrade scripts could handle the complications of varying repos, versions, and trains. I feel like I have something to learn here.
I figured my charting problem out - since I’m using both mapDB and rrd4j persistence, and my “Default Persistence” setting in PaperUI was set to mapDB, that’s what caused the problem. As soon as I changed it to rrd4j, the charts reappeared.