5 second delay before action

[mahatma73]

Hallo again
I do not believe that it should be like that and that you have that problem or that all just get use to that. 3-5 second delay before sensor and light on.
It looks the way that when you going in to the room light is switching on after 3 to 5 seconds so on the staircase the light is on when you already lest the place.
The question is what makes that delay
When I am manually clicking on ON button it switches on instantly in the same second when I am testing the sensor it show movement on the screen in the split of the second?
Do I need separate better PC to run HS? Or RFXCOM should be not LAN only USB but that should not react so fast when I am pressing on button manually?
What to do??

[mahatma73]

I thought it is my SIS chipset problem so I installed HS on my dell laptop and no change
Maybe a beet more reliable but still same delay

Please tell me if your HS has up to 5 sec delay before action?

[rmasonjr]

What hardware are you using? X10, Z-Wave, Insteon, UPB, etc.
I only have X10 and I get maybe a 2-3 sec delay at most, but that is from Motion Sensors, Palmpad, remotes going through a W800 receiver, ACRF-2 plug-in, then on the PLC which is a TI-103.

[mahatma73]

I am using all HomeEasy hardware and RFXCOM transmitter/receiver LAN
It looks odd as it looks like motion sensors shows action on log instantly no delay but after you have wait 3-5 seconds to light on
So it is not sensors
When you manually run the event it start in the same second

[mahatma73]

Today I installed HS on new IBM server with no SIS chipset and I still have that delays
I see that the main problem is in that my motion sensors sends up to 20 information’s per second and HS or RFXCOM just ignoring that so even if you are in the room and if you moving all the time HS is switching the lights off
Is it normal that I have
17/09/2008 22:57:49 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:49 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:49 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) packet received: 20649B58A7
17/09/2008 22:57:50 - RFXCOM - (RecRxChar) duplicate packet ignored: 20649B58A7

[b_weijenberg]

The duplicate packets are ignored of course. If you look in the log you will find the first record of that type being processed.

Can you post (small but readable) pictures of the event you have created.

[mahatma73]

thanks
the problem is that during that ignoring it is switchinh off the lights

[b_weijenberg]

please respond to my question!

[mahatma73]

Sorry
Please find attached

[b_weijenberg]

what happens if you remove the 1st command "Remove delayed action"?
Is the response than fast?

[mahatma73]

Thank you for the answer
I removed 1st line and did not help the same delay look at the log it looks like duplicate packages are taking too much time
19/09/2008 10:51:50 - Database Item - Saving Event Hall GF
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 220450909980
19/09/2008 10:52:02 - Info - Event Trigger "Hall GF"
19/09/2008 10:52:02 - RFXCOM - (display_E_a) Sensor: AC[450902]a Device:[4 Value:249
19/09/2008 10:52:02 - Info - Device: Hall Ground FloorLight Preset Dim Level 29 [95%]
19/09/2008 10:52:02 - RFXCOM - (SetIOEx):A6, Xmit=1, Cmd=10, Brt=29, D1/D2=0/0, Vcmd=, Host=
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (display_E_a) Sensor: AC[450902]a Device:[4 Value:249
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:02 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:03 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) packet received: 2204509099C0
19/09/2008 10:52:04 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509099C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (display_E_a) Sensor: AC[4646B2]a Device:[2 Value:249
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:10 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:11 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:12 - Info - Event Trigger "Light (delayed action)"
19/09/2008 10:52:12 - Info - Device: 1 Hall Ground Floor Light (A6) OFF
19/09/2008 10:52:12 - Info - Deleting event after run: "Delayed Actions Light (delayed action)"
19/09/2008 10:52:12 - RFXCOM - (SetIOEx):A6, Xmit=1, Cmd=3, Brt=0, D1/D2=0/0, Vcmd=, Host=
19/09/2008 10:52:12 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:12 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:12 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:12 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:12 - RFXCOM - (RecRxChar) packet received: 2204646B99C0
19/09/2008 10:52:12 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B99C0
19/09/2008 10:52:16 - RFXCOM - (RecRxChar) packet received: 2204509089C0
19/09/2008 10:52:16 - RFXCOM - (display_E_a) Sensor: AC[450902]a Device:[4 Value:9
19/09/2008 10:52:16 - RFXCOM - (RecRxChar) packet received: 2204509089C0
19/09/2008 10:52:16 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509089C0
19/09/2008 10:52:16 - RFXCOM - (RecRxChar) packet received: 2204509089C0
19/09/2008 10:52:16 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509089C0
19/09/2008 10:52:16 - RFXCOM - (RecRxChar) packet received: 2204509089C0
19/09/2008 10:52:16 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204509089C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) packet received: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (display_E_a) Sensor: AC[4646B2]a Device:[2 Value:9
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) packet received: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) packet received: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) packet received: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) packet received: 2204646B89C0
19/09/2008 10:52:18 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B89C0
19/09/2008 10:52:19 - RFXCOM - (RecRxChar) packet received: 2204646B89C0
19/09/2008 10:52:19 - RFXCOM - (RecRxChar) duplicate packet ignored: 2204646B89C0

[b_weijenberg]

I've analyzed the log and I see the problem.
The motion sensor AC[450902] is received at time seconds 02.
The RF transmitter gets a command to transmit bright A6 95% also at time seconds 02. But the transmitter cannot send the RF signal because the receiver is still receiving RF data from the motion sensor. At the moment that the motion sensor stops transmitting the RF transmitter will send the bright A6 95% signal. This is at about time seconds 04!!!!

The problem is that the motion sensor transmits too long. This cannot be solved. You have sevaral options now.

1) Live with it (looks no option to me)
2) Use another motion sensor that transmits for a shorter period. For example an X10 - MS13
3) Use power line switched lamp modules or Z-Wave for lamps switched by motion sensors.
4) Program the motion sensor also in the HE lamp module. A HE lamp module can have up to 6 remotes programmed to control the unit. Create an event that switches the lamp off if you don't want to have it switched on. Problem is that the lamp will be on for the delay of about 3 seconds. Not so nice solution.

Conclusion:
Don't use HE motion sensors to switch RF lamp or appliance modules under control of Homeseer.

Bert

[mahatma73]

Thanks for the answer
Please in that case could you advise any good reliable but affordable PIR that will work better than my HE
Or is
X10 - MS13
The only choice?
Something that will work correctly with HS and RFXCOM

[b_weijenberg]

I'm using some MS13 sensors and they work OK for me.

[sooty]

I had some similar issues with HomeEasy devices when a HE transmission is required as a direct follow on to a HE received transmission. If the initial transmission is too long then there will be a delay.

I used a solution similar to Bert's suggestion No 4 although it's not perfect.

Assuming you want the light to go ON when motion is detected and then OFF when there has been no motion for XX time, you can use the HE303's inbuilt options. This method won't allow the pre-set dim though, it will be on or off.

Add the PIR to Homeseer / RFXCom as an input device.
Add the lamp module as an output device.
Program the lamp module to respond to the PIR directly and also to Homeseer.
Create a script to trigger on device value change of the PIR.
When the PIR is triggered ON it will switch the light directly and also the script can be set to change the device status of the lamp in Homeseer to on.
When the PIR sends the off signal, the light goes off and the script updates the device status in Homeseer.

Light can also be controlled from Homeseer in the normal way.

Just another thought that Bert will be able to answer I'm sure. What happens regarding handshaking if you use a second transmitter? Could you send the HE transmission over a second transmitter?

Paul..