Are you trying to prevent a blinking LED from tripping it?
If you open live logging, change the setting to a different value, and then perform the steps mentioned in post above to force those changes you’ll be able to see if the setting is actually being changed. Once you’ve confirmed that you can change it back to the value you want.
If that setting is being set to the correct value then something is going on with the device and there’s nothing I can do to help so you might want to contact HomeSeer support.
Thanks for the response Kevin! What happens is I am toggling an LED off, and then back on once every half hour. It is not technically blinking, just turns off for about a second or 2, then turns back on and repeats every 30 minutes. Most of the time the light detect delay works, and ignores this toggle, but once and a while it seems to ignore the delay and trigger the button 1 push as soon as the light turns off. I will take a look at the logging. In the meantime, I have written a webcore piston that checks the device status, which returns a “No Light” when the light is off, it then waits X seconds and checks again, and if it is still off it notifies me, which achieves what I need.
TLDR section:
In case anyone is interested, I am using it to monitor a hot tub and make sure the heater stays on. This hot tub has a problem, and ignores the setting I have for what temperature I want it to stay at, but I realized if I toggle the heater off, and then back on, it “realizes” if it should be heating or not. Using a switchbot button pusher I toggle the heater off and back on again every half hour and that “fixes” the problem with the hot tub. Unfortunately the switchbot is not reliable and sometimes ignores one of the button push commands and leaves the hot tub heater off. This is where the Flex Sensor comes in, to let me know if the heater got turned off and not turned back on.
Kevin, just curious, is the Light Detection Delay option in your DTH a feature you added for your DTH , or something built into the Flex Sensor that you simply expose the option to set in the DTH? Really just trying to learn more about DTHs and understand how it all works.
It’s a configuration parameter on the device and if the logs show that the device is being set to the correct value then it’s a hardware setting so there’s nothing I can do to help.
I am also trying to install this sensor. I installed your device handler in Smart Things and added the Flex light sensor. On the phone I get the display you showed on the opening post except that there is only temp and refresh. In Smart Things when I select the device and do edit, the type is showing “HomeSeer Flex Sensor”. When I try doing anything with the sensor in Web Core it only shows battery and temp. What am I doing wrong? The device in Smart Things shows the light sensor and it changes when light is shown on the sensor but I can not get these parameters migrated over to Web Core. Thanks
The UI will be different in the new mobile app. You need to select the device as a button, the button number mapping is explained in the first post of this topic.
I do not see where you select the device as a button. Nor does my display on the screen show the attached sensor type. The device handler is the Home Seer Flex Sensor from the Home Seer web site.
In using the Smartthings app it does trigger when light is on the sensor but when I create a piston in Web Core it only shows battery and Temp.
It looks like the problem is solved. I found your original handler instead of the one posted by Homeseer and in that handler the buttons were listed and now they show up in Webcore.
For future reference, if you’re reporting a problem on a topic for a specific DTH, you should make sure that you’re actually using the latest version of that DTH…
So the classic SmartThings app now has a banner prompting me to migrate to the new app. As long as I keep your DTH as my handler for the Flex Sensor, will it still report status the same after migration? As I mentioned in a previous post I use the Flex Sensor in WebCore. In WebCore I ask what the status is of the device, and it returns “No Light”, etc. As long as that will still work after migration I may rip the band-aid off and go for it, but if not, then ugh, not sure what I will do.
I spoke with my contact at HomeSeer and you’re correct, they’re no longer manufacturing this device.
They’re out of the “HS-FS100-W Water Sensor”, but they have the “HS-FS100-L Light Sensor” in stock so they should still be selling those for a while and they’ve recently lowered the price.
I’m not familiar with them and all I was able to find online was an email so I’m not sure what country they’re located in or if they plan on developing their own products or just selling rebranded devices…
You might be better off looking for a different water sensor to ensure driver support. Were you interested in this device because of the AC power option or the long sensor cable?
Thanks for clarifying WWST! The Zlink appears to be identical (I saw a reference to it on the Homeseer forum). I purchased one (on ebay, but they also were on Amazon, and here is the official link: Water Leak and Freeze Detector – ZLink Products ) to get the sensor, but did not confirm if the linking is the same, although the unit does appear to be the same on the outside. I chose this unit as it has both a USB power supply (I threw my last unit away as it went through $20/ batteries /year, and at least for me, the long sensor is valuable, as leaks don’t always necessarily go where you expect them too.