Should hopefully be addressed by Change unit delimiter from [ ] to | by sjsf · Pull Request #5621 · eclipse-archived/smarthome · GitHub - many thanks to @sjka to deeply dig into this.
There wasn’t any easy solution to the problem, so as a result, the DSL syntax for number with units had to be changed (from 23 [°C] to 23|°C or also (more ugly) 5|"µm"). I will update the openHAB docs accordingly.
I’d guess the same way as you did for switching to the RC: Change the apt repo from testing back to unstable.
That’s the thing. I didn’t do anything. Just sudoku apt get upgtade
And you are sure that you got the RC1? @Benjy is that expected? If so, I guess it will soon be automatically replaced again as a snapshot build is running this minute.
I think it’s due to APT believing that .RC1 should be newer than ~<snapshotdate>. I had missed that our previous release client version was named 2.0.0~RC1.
The snapshots repo also contain the testing packages.
To install the latest snapshot you’ll need to install the version specifically, find the latest using:
sudo apt-cache madison openhab2
Then pick the version in the second line, e.g:
sudo apt install openhab2=2.3.0~20180524170945-1
1 Like
I made a fresh install of RC1 on my Windows 10 test machine. I have an issue with the Sonos binding :
the “zonegroup” channels of my 3 players are never populated, ( == NULL in my rules or when using the REST API or with Karaf console) even when I change the topology with the Sonos app. The other “group” channels (coordinator, localcoordinator, zonegroupid) are correct and the link to zonegroup is added during the startup process. I restarted and cleaned the cache several times and always the same issue.
On my prod machine with 2.3.0 Build 1246 zonegroup channels are correctly populated with the groups structure.
After latest snapshot update the warnings are gone except for the REGEX transform.
Thanks @Kai and team
I’ve successfully retested all issues that I reported and that got fixed with the latest snapshot build. Thanks a lot for fixing them (including the nasty lambda bug)! 
I don’t run snapshot builds myself in production. Though I’ve now tested as much functionality as possible on my development PC. 
Hi all,
For those that have used the APT testing repository. I have changed the name of the APT package version to 2.3.0~RC1 in order to continue the automatic upgrades. (It will still move on fine for the future 2.4.0-SNAPSHOTS)
For those that have already installed the Release client and would like to upgrade to 2.3.0 Stable once it comes out, please use the following command when the time comes:
sudo apt install openhab2=2.3.0-1
Otherwise, to get back to the snapshots right now, use the set of commands in my post above.
Apologies for the (hopefully minor) inconvenience, but please let me know if you run into any problems.
1 Like
The channel zonegroup was suppressed few months ago.
Hi @Benjy
Can you post the instructions for the addons V2 and V1 as well please, I am sure I am not the only one out there. Thanks.
Hi @vzorglub,
It will be similar for any package, following the pattern:
sudo apt install <packagename>=<packageversion>
e.g. from the same snapshot as my example above:
sudo apt install openhab2-addons=2.3.0~20180524170945-1
sudo apt install openhab2-addons-legacy=2.3.0~20180524170945-1
Is there any chance that a HomeKit connectivity/stability issue can get fixed in this release? I’m struggling with it for a year now 
I upgraded to OH2 snapshot 1288. Unfortunately the item linking bug is still present. I filed an issue in ESH.
Yes, that is correct. The issue is that it all works nicely in ESH, it just stops working once you stick the Paper UI into openHAB 
I fear we have to live with that as a known limitation for 2.3.0 and might patch it with a 2.3.1.
At least there is a workaround: As the item is created, you can then click “Cancel” and simply link it then to the created item. Not nice, but it works.
@Kai I’ve just updated to 2.3.0.RC1-1 and after 2 days the astro 2 binding has stopped firing and the beta Nuki Binding has stopped sending commands. The astro binding still has the midnight entry in the log but the sunset event doesn’t happen.
Previously I could go for weeks without any problems so its downgrade time for me
That does not sound good. I assume it is the binding from the distro (not manually added as a jar in addons, right?) Did anyone else see similar effects on a recent snapshot? The astro binding hasn’t changed for a while, so I would expect that if there is a bug, it should be in there since a while already.
All, we now have a 2.3.0 RC2 available here. It is not yet available as a Linux package (@Benjy could you please build them?). All bugs for which I mentioned fixes above should be fixed in it, a few things might be open.
I wouldn’t call anything a blocker, but we might want to do a 2.3.1 this time a few days/weeks after the release, let’s see.
1 Like
The Nuki binding was already installed, and I switched from Astro 1 to Astro 2 when I installed the update with the binding changed using PaperUI.