| T O P I C R E V I E W |
| mbonaccors |
Posted - 04/03/2012 : 1:44:27 PM
Hello,
I've set up a very simple event for this example:
Using:
1 MotionLinc
1 DimmerLinc in Bathroom
Houselinc Software
If directly link the MotionLinc to the DimmerLinc, then I can get the bathroom light to turn on almost instantly when I enter the bathroom.
However, If I create an event that looks for tiger "Motion Detected" and then as an Action turns on the Dimmer Linc. There is often a 8-10 second delay. The reason I would like to use events vs. directly linking is that I have some more complicated scenarios I would like to create. Having the light turn on 8-10 seconds after you walk into a room kind of kills the convenience.
Any suggestions for reducing the delay that I am experiencing? When I create actions that use a keypadlinc button press as a trigger, there is minimal/no delay. Not sure if it's due to the motionlinc being RF (I have mostly Dual-Type devices in my setup
Thanks in advance!
-Matt B.
|
| 7 L A T E S T R E P L I E S (Newest First) |
| Tfitzpatri8 |
Posted - 04/04/2012 : 3:34:22 PM
(If an Event's Conditions include the status of an Insteon device, that'll also add to the delay since it adds additional status request and response traffic.) |
| stusviews |
Posted - 04/04/2012 : 2:40:33 PM
An event can cause a delay if there are several actions as they are processed sequentially of if several events have the same trigger.
What event condition(s) do you have? What is the more complicated scenario? |
| mbonaccors |
Posted - 04/04/2012 : 12:59:33 PM
I feel as though the delay is more caused by Houselinc having to cycle through all of the events in my list before refreshing (I have about 45 events programmed). The motion detector is RF, but the dimmer switch responder is powerline only. So maybe the delay is being caused by the signal having to go through the Powerline on the way back to the responder? I have three motion detectors and all event with them seem to have similar performance. |
| stusviews |
Posted - 04/04/2012 : 12:36:30 PM
Even 5-6 seconds is a long time. Recheck the event to ensure that the ramp rate is set to instant.
RF travels at the speed of light, literally. It's unlikely to cause a delay. The likely culprit involving a delay is the powerline. Or the motion sensor. Do you another that you can try?
Another test is to move the sensor to a different location and time the delay. |
| mbonaccors |
Posted - 04/04/2012 : 10:09:02 AM
stuviews, I've timed it out and the fastest I've gotten it to respond is ~5-6 seconds. Usually, it's 7-8 seconds or more. Not sure if this is because my bathroom is a few "hops" away from the PLM, or if there's something else I could try doing to increase the response speed. Would modifying any of the "settings" in Houselinc (retry time, etc.) make a difference?
jdate - not a bad idea.. I might try directly linking the motion detector to at least come on at the lowest level and then have the events just brighten it further. |
| jdale |
Posted - 04/03/2012 : 6:55:26 PM
Are you trying to turn the light on at different brightness levels during the time of day? If that's the issue, you could always link the light directly to come on to the lowest level, and then have the event brighten it if needed. That way you get some response (and light) instantly, and can still change the level based on context |
| stusviews |
Posted - 04/03/2012 : 5:41:21 PM
A 1-3 second delay is expected. Is 8-10 seconds an estimate or did you actually time it? |
