Tested each sensor twice and each reported wet or dry. If anyone needs the Homeseer LS100+ manual here you go:
Thanks Corey/Phil for your time and help on the Homeseer leak sensor Edge driver.
3 Likes
Note that the manual (both the v1 manual on the zwave alliance and the manual on HomeSeerâs site) has a bunch of errors for the actual behaviour of the LS100+.
The most notable are:
Secure Inclusion:
Press the button on the device once. The LED will flash indicating its starting secure inclusion.
Normal (insecure) inclusion:
Press and hold the button for 4.5 to 5 seconds. I count âone one thousandâ while doing it, if you go too short it does a secure inclusion. If you go just over 5 seconds it does a reset or nothing. So release right on 5 seconds.
Exclusion:
Press the button 3 times quickly to exclude. The manual is correct.
2 Likes
Does anyone need native support for the HomeSeer HS-MS100+ motion sensor? I can add that one to the TODO queue if needed.
1 Like
The only two instructions I needed to use was the following:
Exclusion 1. Put your home automation controller into Z-Wave âexclusionâ mode. 2. Quickly triple-press the Z-Wave network button. Wait for the exclusion process to finish.
Secure Inclusion (recommended if your home controller supports âS0â or âS2â Z-Wave encryption) 1. Put your home controller into Z-Wave âinclusionâ mode. 2. Press and hold the Z-Wave network button for 5 seconds, then release it. Wait for the inclusion process to finish.
I found this to be incorrect (after including/excluding the device 50 times during driver testing). If you press and hold for 4.5 - 5 seconds it will do an insecure inclusion. Pressing once (or not holding to 4.5 seconds) will get you secure S2 inclusion. Check your actual inclusion level with the CLI:
smartthings devices <num> -y
if youâre curious. This also may be firmware dependent, but all my LS100âs (12+ in use) are the same, V1.04.
1 Like
Hello, can you add this fingerprint to Edge driver Z-wave sensor?
fingerprint mfr: "0154", prod: "0004", model: "0007", deviceJoinName: "POPP Open/Closed Sensor" //EU //POPP Door Window Sensor
@Mariano_Colmenarejo
This worked perfectly⌠thank you very much!! 
2 Likes
Is there an edge driver that would work with the GoControl Multifunction Siren? The stock Z wave siren device handler doesnât control the strobe.
I am currently using this custom device handler: [OBSOLETE] GoControl Siren / Linear Siren / Vision Siren. The Raw Description is: zw:F type:1000 mfr:014F prod:2005 model:0503 ver:1.65 zwv:3.42 lib:06 cc:25,80,70,72,86
Any help would be appreciated, Thank you
@Mariano_Colmenarejo can you add the fingerprint for the Intermatic CA3650 to your Z-wave Switch Mc driver?
raw description:
zw:L type:1001 mfr:0005 prod:4341 model:3750 ver:1.101 zwv:2.09 lib:06 cc:91,73,72,86,60,25,27
Thanks!
Can you add driver for Leviton switch
MSR: 001D-1706-0334
manufacturer: Leviton
mfr:001D
prod:1706
model:0334
Need driver for Leviton Switch
mfr: 001D
prod: 3201
model: 0001
manufacturer: Leviton
These should both be joinable as generic switch devices from the Beta Edge Zwave Switch driver.
1 Like
Is this possible?
Theyâre not a match by MSR fingerprint, they will likely match by zwave device type or cluster. The Beta Edge Zwave Switch driver includes:
zwaveGeneric:
- id: "GenericSwitch/1"
deviceLabel: Switch
commandClasses:
supported:
- 0x25 # binary switch
deviceProfileName: switch-binary
- id: "GenericSwitch/2"
deviceLabel: Switch
genericType: 0x10 # GENERIC_TYPE_SWITCH_BINARY
deviceProfileName: switch-binary
- id: "GenericSwitch/3"
deviceLabel: Dimmer Switch
genericType: 0x02 # GENERIC_TYPE_SWITCH_BINARY
deviceProfileName: switch-binary
- id: "GenericDimmerSwitch/1"
deviceLabel: Dimmer Switch
commandClasses:
supported:
- 0x26 # switch multilevel
deviceProfileName: switch-level
- id: "GenericDimmerSwitch/2"
deviceLabel: Dimmer Switch
genericType: 0x11 # GENERIC_TYPE_SWITCH_MULTILEVEL
deviceProfileName: switch-level
Those devices are bound to match one of these.
People really should be installing the base beta drivers before looking for a more specific driver. Consider it the same as the built in drivers from before. Install all Beta drivers for the types of devices you have. Have a zwave smoke alarm? Install the Beta Zwave Smoke Alarm driver first before going fishing for a more specific driver.
2 Likes
Just qurious if anyone working on edge driver for zemismart roller shades? I will be appreciative dont want loose functionality of my smart roller shades⌠thanks âŚ
It appears this device is a clone of the Aeotec NanoMote Quad, so it would need a fingerprint added to the stock Zwave Button driver.
Original DTH fingerprints, has no custom logic for the Hank vs the aoetec
fingerprint mfr:"0371", prod:"0102", model:"0003", deviceJoinName: "Aeotec NanoMote Quad"// ZWA003-
fingerprint mfr: "0208", prod:"0201", model: "000B", deviceJoinName: "Hank Four-Key Scene Controller" // HKZW-SCN04
And the existing stock zwave-button driver fingerprint for the Aeotec.
- id: Aeotec/button/quad
deviceLabel: Aeotec NanoMote Quad
manufacturerId: 0x0371
productId: 0x0003
deviceProfileName: multi-button-4
1 Like
Is that this one? POPP Z-Wave Door/Window Sensor w. Gyro and external sensor
1 Like
Definitely not a clone.
https://products.z-wavealliance.org/products/1968
.
https://products.z-wavealliance.org/products/2820
The Hank is an older device, with support for central Scene V2 and S0 security.
The Aeotec supports central Scene V3 and S2 security.
And the configurable parameters are completely different. Hank just has a couple used for network management while the Aeotec lets you disable the buzzer and configure a low battery notification. They are also using different Z wave stacks.
But they are both 4 button handheld remotes, so itâs not surprising if they can use the same basic driver.
I meant a clone from the basic button handling only, just by looking at Kevinâs DTH. My fault.
1 Like