HomeSeer HS-FLS100+ Z-Wave Plus Floodlight Sensor

[Rocketron]

Z-Wave Product Catalog

Has anyone any experience with the these?

Does anyone have one functioning a with ISY?

[Rocketron]

Took a chance and ordered one.

Seems to be a solution to retro-fit any security flood lamps you may wish to automate.

Be sure to turn the manual adjustment knobs on the unit away from the "Test" setting. I'd suggest midway between all on and all off. If you don't do this, changes you make to the parameters through your ISY will not work. That will save you having to get the ladder out again.

Running version 5.0.13D

[danbutter]

Can you set this so that it will control the light hooked to it only when something like a program tells it to?

I'm thinking of this for a detached garage where I don't have reliable zwave signal due to distance and brick and aluminum construction.

This would of course be on the outside of the building though so it should be able to talk to the devices in the house.

So I guess what I'm asking is can you ignore the built in motion sensor and just use it as a zwave module to turn a light on/off?

 

[Rocketron]

Quick answer is not in my experience, can you do this. However I never spent the time to check out that.

https://homeseer.com/wp-content/uploads/2018/08/HS-FLS100-user-manual2b.pdf

To gain the control of the light I added to the circuit an insteon micro module.

https://www.insteon.com/on-off-micro-module/

Now with the controller I can have control of when the light comes on and for how long. Basically for my application I use the sensor to give feedback to the ISY. The lux sensor is handy too, to give feedback to the ISY. But like you I wanted finer control of the lights.

For me it's being used as a wired sensor so no batteries to worry about and it's rated for outdoors.

 

[danbutter]

Thanks for the reply.

Looking at the manual it seems that if you set parameter 2 to zero it should do what I want so I ordered one.

I'll report back how it works when I get it working.

[danbutter]

Well I got it and installed it. It works in my programs as I want it to. I have a double tap from a homeseer switch turn it on or off as well as some other programs depending on a couple statuses.

I didn't feel the need to set the parameter yet though. I left it as is and let it come on when it sees motion. The only thing I haven't specifically tested is if I turn it on and then go trip the sensor what happens? Does it stay on because it was already on when tripped or does it shut off like it should when tripped?  I am happy with it so far and hope to be able to test this over the upcoming weekend.

[danbutter]

Finally got around to updating on this one.  It has worked out great for me and works as I want it to.

It can be left alone and it will turn on when it sees motion after dark, but you can also turn it on via a scene or program or AC or webpage etc.

When it is turned on it won't go off when it sees motion and then times out like some other motion sensors do.  You will have to turn it back off or let a program do it.  I prefer this for times like winter when snowblowing the driveway. I want the light on. Not on and off and on again.  It does still function like a normal motion sensing light though if you want it to.

Only strange thing about it with the ISY is the extra nodes that pop up.  It has the luminescence or lux level that it reports, the motion sensor and the switch of course, but it also shows up with intrusion alarms, tamper alarms, glassbreak, tamper and tamper code alarms.

I may be able to fix these issues if I exclude and re include it, but being up high on the side of the garage means I won't be attempting that until spring at the earliest.

[Bumbershoot]

1 hour ago, danbutter said:

Only strange thing about it with the ISY is the extra nodes that pop up.  It has the luminescence or lux level that it reports, the motion sensor and the switch of course, but it also shows up with intrusion alarms, tamper alarms, glassbreak, tamper and tamper code alarms.

I may be able to fix these issues if I exclude and re include it, but being up high on the side of the garage means I won't be attempting that until spring at the earliest.

If you're on one of the more recent 5.0.x.x firmware builds, you may be able to prevent this by  using the menu item: Z-Wave | Options | Freeze ISY Nodes | Yes

If it works, it beats climbing on a ladder.

[danbutter]

I'm on 5.0.14 so I'll have to try that.

Then I can delete the other nodes that don't really exist and see what happens.

Thanks for the tip!

[jasont]

@danbutter, is this still working well for you?

[danbutter]

It is.

I actually got another one if that says anything. 

 

[infinkc]

On 2/22/2019 at 5:37 PM, danbutter said:

It is.

I actually got another one if that says anything. 

 

I am trying to use this to detect the brightness, ISY only shows 0 or 250 as values for LUX.  Do you know if this is the same what you see?  I was hoping it was smart enough to detect the amount of brightness, not just light or dark.

[danbutter]

Well right now I expected to see a result of zero as it is pretty much dark out, but it is showing the value of 1 lux.

I am using 5.0.14 FYI. 

...as I finished typing this I hit query and now see zero lux so it definitely updates more than 0 or 255.

[lilyoyo1]

10 hours ago, danbutter said:

Well right now I expected to see a result of zero as it is pretty much dark out, but it is showing the value of 1 lux.

I am using 5.0.14 FYI. 

...as I finished typing this I hit query and now see zero lux so it definitely updates more than 0 or 255.

There may be parameters that you have to update for it to report more often than it does. To cut down on traffic which would slow your network, it may only report after a certain amount of time has past

[SetMonkey13]

The sensor does show different values between 0 and 255.  I kept querying it tonight.  It probably went down from 250 to 0 pretty quickly as the sun set.