Nope, you need at least 2.4 stable for recent zwave snapshots. Recommendation is 2.5M1 (Milestone 1)
The zwave database changes fast and 2.4 stable is quite old already (in terms of zwave), so you should go with the latest 2.5 zwave snapshot.
In either case, you need to perform the steps written down here if coming from 2.3:
1 Like
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
744
I was on OH 2.3 and I upgraded to Chris zWave binding 2.5 many months w/o any issues at all. You do need to follow his instructions for upgrading though.
When I did upgraded to OH 2.4 later; the zWave stuff worked w/o any changes.
Hey all,
I upgraded from 2.3 to 2.5M1 two days ago. In 2.3 all my 33 node were working fine. After the upgrade most of the stuff started working flawlessly after following the best practice procedure.
I just have a few devices that are not recognized properly. Even after few hours as well as a nightly heal.
E.g. I have 2 identical Fibaro flood sensors. One is detected properly like this:
I have a new version of the config for a Fibaro Smart FDBS 222 Implant with 4 of the 6 optional temperature endpoints connected. I know there is a thread somewhere that explains how to submit and update database but I can’t find it. I am not very used to the forum yet.
I have registered and raised a ticket on the devices site. Very happy to help by adding or editing and not expecting anything fast as Fibaro would take months to add a template for a third party if ever.
Please could someone point me to the thread that explains how to add and test templates.
I also have one that while it had no extra temperature sensors attached was not recognised. Possibly a new firmware version?
Correct, for that you need to login
But you won’t be able to add an xml as it already is present in the database.
Just upgrade your zwave binding to the latest 2.5 snapshot
I am having trouble with setting the lifeline to controller for this node. I have a couple of other nodes that behave like this. Do you think this is one of those remove and add stuations?
Thanks @sihui,
Indeed, I removed all things already. Since its also for a dimmer 2 which is mains connected, this is quite strange. Will give the manual waking another try with the flood & motion sensors.
I guess it will be working fine in future versions then. Do you think that there’s any way I can fix it keeping 2.5M1 Z-Wave binding without upgrading? (I can’t go higher due to that I’m still on OH 2.3 for several reasons)
You’d have to edit the JAR file to add the new XML - it’s doable, but not for the faint hearted.
I’m not sure why there should be a big difference between 2.5M1 and 2.5 SNAPSHOT though. If the M1 version works, I would have thought the SNAPSHOT would also work, but I could be wrong.
Thanks. I tried the snapshot version first but gave it up after a few hours of fiddeling with it. I got into trouble with serial port communication and there was a message in the logs about a missing command or somthing similar. As a result, the Z-Wave controller never came online. After installing 2.5M1 things started to work.
I have installed the latest zwave binding snapshot running on a 2.5.0.M1
I am having issues with the setup of FGBS222 Smart Implant using the version of template in the snapshot.
The device is detected but the initial setup of associations is odd and I can not set to the lifeline. Is this an issue with the snapshot, the template or just my install.