chris
November 16, 2018, 11:39pm
41
I’ve kicked off a build with the updates, so hopefully it will be ready in an hour or so…
mhilbush
November 17, 2018, 12:28am
42
The build is done. However… I would recommend against installing a snapshot release after and including build 1427.
See this post. Depending on what DateTime methods you use in your rules, those rules could be badly broken by a recent ESH change.
Guessing that this change broke things.
https://github.com/eclipse/smarthome/pull/6492
now.plusMillis(150)
now.getHourOfDay
now.withTimeAtStartOfDay
@Kai I realize this is a breaking change. However, the above methods, which are commonly used in rules, no longer exist.
If you want to pick up a new zwave binding, and don’t want to install a snapshot for the above reason, use the method explained in this post.
Now that dev is merged into master, I wanted to revisit how I upgrade to the latest version of the zwave binding without updating the rest of openHAB.
Simply using bundle:update org.openhab.binding.zwave from the karaf console is not working for me.
The only thing I found to work is to explicitly provide the exact location of the jar in the bundle:update command. Like this.
openhab> list -s | grep zwave
227 │ Active │ 80 │ 2.x.0.old-date │ org.openhab.binding.zwave
openhab> bundle:upd…
mhilbush
November 17, 2018, 9:52pm
43
FYI, the issue with the DateTime methods in rules was fixed in build 1430.
jgrundvig
November 18, 2018, 12:34am
44
I updated the binding and everything is working perfectly! After setting up the new channels and writing some new rules, my ZCombo alarms now send my phone the correct notifications based on what triggered the alarm (CO, Smoke, Test button).
Thank you!
