This is a problem as your device has the same device type and device id.
Your firmware version is 1.1, so I extended the existing database entry from only using 1.2 to 1.1 to 1.2.
But I can’t add your device type and id as this is used by the Electric Strike Lock.
If we knew the firmware versions of the Electric Strike Lock this would be a solution …
Unfortunately you’re right… Without more information on the lock we can’t work out how to differentiate these two devices. If the lock is using 1.4 and 1.5, and the valve is using 1.1 and 1.2, then we could create the device.
I guess we can make that assumption, and see if anyone complains and work out what to do from there. It’s not the nicest approach, but if the manufacturer doesn’t respect the ZWave requirements, it makes life difficult.
@sihui if you update the database with these assumptions, please add a comment to each device as sooner or later we might want to remind ourselves about this discussion
Unfortunately this is even more complicated: the lock is using firmware versions 1.04 (not 1.4) and 1.5, so we need three devices: two entries for the Electric Strike Lock Module, one with firmware 1.0, one with firmware version 1.5 and above and another entry for the Flow Stop with firmware version 1.1 to 1.2.
I’ve just removed the binding from my paperUI, and reinstalled it by the paperUI. But I don’t see much difference in the binding itself (2.5.0.M1) or after exclude/include the node (still Popp 012501). Or should I download the binding manual and put in the addon folder?
ps, I was not able to include it over paperUI. I should really need to understand/study the ‘security’ option in the include. Played for about 2 hours with it, but not 1 correct inclusion of the device. Sometimes it’s been noticed, but then not fully initalized. And sometimes, a lot of other things went offline? I even got 2 now that aren’t reachable anymore? Maybe another story.
But when I add it the hard way (button on stick), it works 1-2-3… Nicely included,and initalized after +/- 2 minutes. Sadly still as electric lock.
I have just created an account for this…
I struggled for 2-3 days to understand why after upgrade from 2.4 to 2.5 my door lock didn’t work anymore… and it was wrongly detected as Flow Stop.
My door lock is a few years old and it has firmware 1.2 !!
I had to modify the database to solve this issue.
I thought the problem was pretty clear.
My lock is firmware 1.2 which got mapped to flow stop after installing 2.5.
I made a copy of the zwave binding, where I removed the flow stop xml (9501)and modified the 12501 xml just with min 1.2 (instead of 1.4).
Then it worked fine as before…
Of course, you will say that we just change the database, and this will fix your problem. However, does it cause someone else a problem? Maybe the manufacturer has used the same codes for two devices? Are you sure this is not the case?
We should investigate this - it might just be a database error where someone has made a mistake, or it might be the manufacturer has made a mistake?
This is why we like to get the XML files - to help with diagnosing issues.