This handler includes some workarounds that make it fully functional with Automations and all the built-in SmartApps, but they shouldn’t be needed once Custom Capabilities are fully supported. The handler also has some quirks that were unavoidable at the time of writing this handler because Custom Capabilities still have a lot of broken features.
Features
Supports all the settings that are meant to be used with this model.
Indicator Light Sensor no light | light | color change
Button pushed: no light | pushed_2x: light | pushed_3x: color change
Temperature
Power Source Shows if it was joined as a DC powered repeater or sleeping battery device
Alarm Makes device beep, but only works if the device was joined on DC power and is still on DC power. The ability to conditionally show tiles is currently broken so it’s displayed even when you can’t use it. The built-in Tone capability is missing from Automations and gets displayed as “find my device” on the device details screen so using the Alarm capability was the best workaround I could think of
Battery If the device was joined on DC power it’s not possible to get the battery level or conditionally hide it at the moment so it will always be 100%
Important
Indicator Light Sensor is a Custom Capability so you won’t be able to use it in Automations so you’ll need to use the Button Actions to trigger automations until they’re supported.
This device shares a fingerprint with the HS-FS100-W so if you have both handlers installed you need to put // in front of the fingerprint line in the other handler before joining the device. If you don’t do that it might get assigned the wrong handler and it might still show the old UI after changing handler due to caching issues with the platform.
When the device is powered by batteries and you change a setting the device won’t receive it until the next time it wakes up which could take 24 hours. You can manually wake the device up by pushing the physical button, but it doesn’t notify the hub that it’s awake so you need to refresh the device details a moment after waking it up. Swiping down when you’re at the top of the device details screen executes the refresh command.
SmartThings now supports custom capabilities in automations so you can probably use the indicator light attribute to trigger automations instead of having to use the button workaround mentioned above.
HomeSeer discontinued the product so I doubt they’ll be providing one and I’m not using this device with SmartThings at the moment. I’m considering moving it back to ST and if I do then I’ll write a driver, but that won’t be for at least a couple of months…
Check here for a specific driver for the LS100+ leak/water sensor. The LS100+ will join using the stock Edge Zwave Water Sensor (available in the Beta Edge drivers) but all the custom parameters are not available with that option.
When I checked HomeSeer’s website the HS-FS100-L is still for sale. But I did contact them and they stated that they are working on official Edge drive for this and their other products. They added me to a list to include me on updates. So when I hear back I will post here.
So this means, If I wait, I will get the default driver, but will probably want to upgrade to the one you are developing, or will the transition be smart enough to find the right driver?
We’re not exactly sure how The Big Transition will work if you have multiple Edge drivers available with the same matching fingerprint. Nor if there is a priority of a “community” edge driver over a “stock” one. At worst if there are multiple highest level of match, it would randomly pick one.
Not sure. I’m setting my world up so that it finds some edge driver match for all my devices. even if its not the right one, I know I can switch drivers later. But as to the detailed specifics of the transition process, some aspects are murky.
I won’t be converting the HomeSeer Indicator Light Sensor DTH into an Edge Driver so the device might stop working once the Groovy platform is retired.
Homeseer still sells this (the FS100+ flex sensor at least), however without Device Handlers you can’t really manage it. Since Groovy is retired, anyone know when the new world will appear and this will work? So confused.
It would help to know for sure if this will be obsolete or not. My understanding is that they are liquidating the last of the lighting ones, but I do think they stopped making them.
Yes, my reference was to the device, not the driver. Any yes, when I inquired, the manufacturer indicated they no longer were manufacturing them. I guess in this case, both the device and soon the driver will become obsolete at least for ST. I found this device to fill a nice niche that competing products did not fulfill.
Mine stopped some time since the weekend (the last time I used the dryer before today). I was only using it to trigger a NotifyMe notification on our Echos that the dryer cycle had ended, so with the Groovy SmartApps ending this week, that’s obsolete as well. I guess this is one more device that will migrate over to the other hub and get me learning about its UI and features…
Thanks for all your help with this in the past, I’ll see you over there!
