FLS-100 constant motion

[RRR]

Are you getting the false motion triggering others have reported? I've been holding off getting one of these because of all the complaints.

Yes, as I reported in this very same thread, when I opened a ticket with HS on my issues with the G2, they told me they thought it was related to the beta Z-wave plugins. So, I switched over to non-beta, excluded and re-included. Gotta say it seems to be working now.

[avpman]

Yes, as I reported in this very same thread, when I opened a ticket with HS on my issues with the G2, they told me they thought it was related to the beta Z-wave plugins. So, I switched over to non-beta, excluded and re-included. Gotta say it seems to be working now.

I'm confused. I asked "Are you [still] getting the false motion triggering others have reported?" and you replied yes, but then said the non-beta plugin fixed it. Anxious to know which particular version of the plugin worked for you.

Thanks!

[rschein]

I had the non-beta zwave plugin and support had me change to it. The continuous (interrupt by parameter 1 time) alerting continued in both. I need more too but will not order until they work.

[avpman]

I had the non-beta zwave plugin and support had me change to it. The continuous (interrupt by parameter 1 time) alerting continued in both. I need more too but will not order until they work.

From the plugin release notes, it looks like they have spent quite a bit of time cleaning up the 3.0.7.0 Zwave plugin. Hopefully, this is only a plugin or firmware issue that can be addressed and not something hardware-related to the FLS-100.

[RRR]

I'm confused. I asked "Are you [still] getting the false motion triggering others have reported?" and you replied yes, but then said the non-beta plugin fixed it. Anxious to know which particular version of the plugin worked for you.

Thanks!

To be clear, after switching to non-beta plugins my issues are gone. Attached is today security events, when I chimed in here originally it was constant. Not sure I understand how or why changing the plugin solved my issue. If the device, G2, is independently sending a notification of a secure zone tripped why does the plugin receiving it matter. I don't know, for the time being mine is working, but I'm not willing to investment in anymore at this time. The idea (G2) is good, but the execution leaves some to desire. Maybe its just inherit to z-wave technology, again I don't know.

[avpman]

To be clear, after switching to non-beta plugins my issues are gone. Attached is today security events, when I chimed in here originally it was constant. Not sure I understand how or why changing the plugin solved my issue. If the device, G2, is independently sending a notification of a secure zone tripped why does the plugin receiving it matter. I don't know, for the time being mine is working, but I'm not willing to investment in anymore at this time. The idea (G2) is good, but the execution leaves some to desire. Maybe its just inherit to z-wave technology, again I don't know.

What is the version number of the plugin you are using, just to be sure? I may try to see if I can get the same positive results.

[clahote]

Had a similar issue with several G2 sensors, work okay for hours then get stuck in a cycle of retriggering constantly, seems to happen more often when units have low neighbor count and poor signal. The 'cycle time' of retrigerring is the sum of the 'On Time' and 'Luminance/Temp Report Interval' settings. Changing Report Interval to 1440 resolved the issue for us.

[Huntler]

New here, first post. Same problem as original poster, constant motion detection with the default timeout as 3 min, sensitivity is set to low. I notice that the problem occurs when the sensor is in direct sunlight and diminishes when out of sunlight or overcast and once the lux level is below 50 it operates normally with very few false triggers. Sensor is on west wall aimed away from moving objects except the area I want to detect, I'm in Phoenix so the sun is very bright and temperature measurements are way high during the day, so not intending to use it for reliable temp measurements.

My intent was to use it at night to trigger other exterior lights so the lack of falses after dark is okay for my original application, but the false triggers during the day eliminate the possibility of using it for daytime notifications/triggers.

It's also annoying that the falses are clogging up the log, I see there is a setting in the Zwave UI to disable notification on motion reporting, does anyone know if that reporting is disabled, any programming triggers wanting motion/no motion would be useless? I suppose I could use the light status since motion is triggering the light. Any help would be appreciated.

[njmopar]

Hello. New user here.
Had same issue with the endless loop of activity at times. I opened a tech support ticket and was told to set the update interval to anything above 120. So far so good at 140 for me. So the 1440 mentioned above would work as well, but if you want somewhat regular device value updates, then try 120+

[Tomgru]

hey all,... think i have similar problem but might be slightly different.

First gen unit... motion was triggered several days ago and never reset. I've cut power to it and it stills shows tripped back on Jan 5. Audits etc also don't work.

there also looks to be condensation in the lens of the motion sensor. Has anyone seen this?

I read this thread but didn't see any way to reset (or missed it). Any thoughts?

Thanks

[clahote]

Changing report interval to 1440 was a temporary fix, issue returned a few days later. We've tried Z-Wave plugins 3.0.10.0, 3.0.11.0 beta, 4.0.3.0 and 4.1.0.3 beta, all with the same result: after some random time (usually days), constant motion is triggered and can continue for hours. Viewing or changing floodlight parameters often triggers this behavior, as sometimes does just testing connectivity.

All are G2 units, some are firmware 1.0, others 1.1, all periodically experience the issue.

As mentioned before, these units are at the edges of Z-Wave range and that appears to be a contributing factor. We've added 700-series Aeotec repeaters, 700-series Leviton outlets and/or WX300 switches within 3 feet of several and that has reduced but not eliminated the issue. Unfortunately we've had to disable motion control and notifications and only use the units to control the lights via Z-wave commands.

Anxiously awaiting a Zooz 800-series LR outdoor sensor to test that is slated for a spring release.

[njmopar]

So far I have been lucky with just changing to "140".
You have tried a full optimize under the zwave menu? May help relearn neighbors.

[socalsharky]

I guess it is good to know that setting the report interval to 140 helps solves the problem, but really, how ridiculous is that? By setting the report interval to 140 you pretty much negate two of the sensor values that the unit is supposed to report - temp and lux. All of my other temperature sensors update at intervals no greater than 10 minutes. 140 minutes is an eternity if you are trying to do anything useful with that data.

The lack of attention to this problem by Homeseer is very disappointing.

[ecetron]

Well I just joined the party. I've set the report time to 1440 with no impact. Interestingly enough, one seems to work, at least for now, with no crazy reporting, but:

3/15/2023 23:06:40 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to ON
3/15/2023 23:06:40 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: Motion Detected
3/15/2023 23:06:39 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to OFF
3/15/2023 23:06:39 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: No Event
3/15/2023 23:03:39 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to ON
3/15/2023 23:03:39 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: Motion Detected
3/15/2023 23:03:38 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to OFF
3/15/2023 23:03:38 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: No Event
3/15/2023 23:00:38 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to ON
3/15/2023 23:00:38 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: Motion Detected
3/15/2023 23:00:37 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to OFF
3/15/2023 23:00:37 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: No Event
3/15/2023 22:57:37 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to ON
3/15/2023 22:57:37 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: Motion Detected
3/15/2023 22:57:36 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Set to OFF
3/15/2023 22:57:36 Legacy-Plugin Z-Wave Device: Main Floor Front Entrance Floodlight Sensor G2 Rt Motion Sensor Set to NOTIFICATION for type Home Security, Event: No Event

Both are brand new with Ver 1.1 firmware. I have set them both back to interval of 10 since 1440 seems to make no difference. Need to get some sort of resolution on this one other wise they are next to useless as when it DOES cycle it also turns on the LEDs themselves.

And neither got the power management child device either so I get these once in a while - even after a rescan and one added secure (which failed and went unsecure) and one unsecure directly.

3/15/2023 23:18:00 Legacy-Plugin Z-Wave Error Notification Report from node 82 for type Power Management Notification received, but the corresponding device Node ID cannot be found. (2, Type=8)

3/15/2023 23:18:00 Legacy-Plugin Z-Wave Error Notification Report from node 81 for type Power Management Notification received, but the corresponding device Node ID cannot be found. (2, Type=8)

Might have to climb up the ladder and replace them with another solution - just don't know of another similar product except the 007 series at some wild almost 200 dollars price...

-ed

[njmopar]

Mine started acting up again out of nowhere. Same exact thing. What does seem to resolve for a few days, is turning off the wall switch power. But a few days later, it comes back again with endless triggering.
I opened another tech support ticket. I suggest that others do as well to push the issue.