It would be great to merge the PR to fix the iCloud binding SSL issue (mentioned here).
No problem with Z-wave in snapshot 1650.
1 Like
I can report zwave snapshot binding working for me on 2.5M1 install. I have disabled the nightly heal.
1 Like
Yes, I’m using the latest snapshot versions quite successfully in several installations. I’ve disabled the nightly heal due to this problem that I first reported in January. It’s quite likely that the problem existed before that. The workaround for this issue is easy. Just disable the nightly heal, and then run heal selectively if there’s an issue with your network.
This problem reported by @5iver sounds more severe, but I’ve not experienced it.
Edit: I should add that one network is about 100 nodes. Another is about 20 nodes. The other ones are small and used mostly for testing purposes.
1 Like
Can you point me to the PR? I don’t find it.
Not noticed any problem with snapshots and z-wave. Using 1650 at the moment. Didn’t change any heal settings. 25 nodes, 8 are battery ones from different manufacturers.
2 Likes
hueemulation
I have worked around a hueemulation pax-web problem which happend to users that ran hueemulation in debug log level mode. The affected user reported that he could successfully use hueemulation with Alexa in debug and warn log level.
I do see hueemulation being ready for a 2.5m2 release. A few more compatibility tests with Google Home and different Alexa firmwares would be helpful for the final 2.5 release as well as an https strategy for openHAB, because that is required by newer Hue API versions.
3 Likes
Sorry about that, I forgot to create the PR last night. Here is the link: https://github.com/openhab/openhab2-addons/pull/5895
2 Likes
Ok, thanks everyone for the feedback!
So I would say that the z-wave problem does not seem to be a general one as the binding seems to work well for quite some people. I’d hence stick to @chris decision to not consider it blocking for M2 (while possibly blocking the 2.5 release, but that’s for the future).
Also thanks to @David_Graeff - I understand that hueemulation is also in a state that is ok for M2 (while not for a 2.5 release).
I’ll therefore trigger the M2 build in 30 minutes - let’s touch wood that it succeeds!
11 Likes
Hm, I am afraid, I had no luck.
It might be that the milestone build plan (or rather the checked in Jenkins pipeline) is not up-to-date as the sandbox pipeline is not using the checked in definition, but a different one.
I guess I will need @pfink’s support to figure out what to do - I hope he can quickly come up with a solution that makes the build succeed!
1 Like
It seems to be caused by the Slack plugin (see A JSONObject text must begin with · Issue #594 · jenkinsci/slack-plugin · GitHub). So updating or disabling it will probably fix it.
I’m not so sure. The sandbox build is using the slack plugin as well and the milestone build failed with the message:
groovy.lang.MissingPropertyException: No such property: removeTagIfExists for class: groovy.lang.Binding
which does not seem to be related to Slack…
On the other hand: “removeTagIfExists” sounds like a task AFTER the build, so you might be right that the build is considered to have failed before that. I’ll disable the Slack plugin and try a new run…
It looks like Slack to me as a newbie.All green until here.
From
https://ci.openhab.org/view/all/job/openhab-milestone/5/flowGraphTable/
It looks like Slack to me as a newbie
Well, slack should only be triggered at the very end of the build to inform about the outcome - so if it is triggered, it means the build is over (for some other reason).
Problem is, I cannot even find where Slack is configured in this job. So I tried to update the plugin to version 2.28, where the bug is supposed to be fixed.
But still no luck, so I’ll go to bed now and wait for @pfink’s advice…
Hope he is still around as his last post was some five month ago …
There are other ways to reach hom 
1 Like
- First attempt (build #2) failed because the wrong pipeline script was used (this seems to be corrected in the second attempt)
- Second attempt (build #3) failed due to a syntax error in the pipeline. This is fixed now
8 Likes