Author |
|
RichardL Senior Member
Joined: December 29 2008 Location: United States
Online Status: Offline Posts: 165
|
Posted: March 19 2012 at 11:04 | IP Logged
|
|
|
I have set up a new v2 Motion Sensor 2420M, however I seem to get 2 triggers for each time motion is sensed.
I am running PowerHome v2.1.4. Jumpers 1, 2, 3 are off, 4, 5 are on. I have configured the moton sensor for Occupancy=On - thank you Lee for the utility to program the device! The device is setup as "I2" and disabled in the devices section. The trigger is set for "Insteon Group In", ID #: 1, "On (0x11)", Boolean=1. It runs a simple vbs (TR_MS-2_On) to turn off a light (address 06.C7.FC) for 1 second. I did a factory reset of the 2420M, and started over, same problem.
As you can see in the attached event log, Powerhome is getting 2 incoming Insteon signals. The address of the motion sensor is 14.9A.17, I am not sure what the address "00.00.01" is... I have been very careful to be sure that I am only giving the motion sensor one "motion". I have the motion sensor on my desk facing away from me, and I simply pass my hand from left to right, once, in front of it.
(I cannot seem to upload the image file over the past day, I'm getting HTTP-500 errors. Wanted to get this out anyway - will keep trying)
Any thoughts or assistance is appreciated.
Richard
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: March 19 2012 at 13:22 | IP Logged
|
|
|
That is normal for an RF device. Many send 3 Group Broadcast messages. The 00.00.01 is Group 1 which is the Motion Group. Group 2 is used for Dusk/Dawn messages and Group 3 is used for low battery. There is a post somewhere from Pete that describes what to code in the Boolean field so that only the first Group Broadcast message triggers.
The same thing will be seen with TriggerLincs, RemoteLinc2, and so on.
I found this from Pete in another post dealing with TriggerLincs.
Without going into a lot of detail. It is probably from Group Cleanup commands. You might try putting TRIGDISABLE in the Boolean field of the trigger and see what happens. Trigdisable can be found here on the 1st page.
http://www.myx10.com/forum/forum_posts.asp?TID=2132&KW=trigd isable&TPN=1
Scroll down this link. It has the original post from Dave on TrigDisable
http://www.myx10.com/forum/forum_posts.asp?TID=2132&PN=23
Edited by grif091 - March 19 2012 at 13:32
__________________ Lee G
|
Back to Top |
|
|
RichardL Senior Member
Joined: December 29 2008 Location: United States
Online Status: Offline Posts: 165
|
Posted: March 20 2012 at 00:40 | IP Logged
|
|
|
Interesting. As usual, thanks for the good info. I'll post how things go. Due to scheduling it may be a few days.
|
Back to Top |
|
|
RichardL Senior Member
Joined: December 29 2008 Location: United States
Online Status: Offline Posts: 165
|
Posted: March 25 2012 at 13:30 | IP Logged
|
|
|
Success! Simple - In my test routine, I added a PH.DisableTrigger command as the first line (in the VBS code), then a PH.EnableTrigger at the end. Works like a charm.
I figure I need 1 to 2 seconds before the PH.EnableTrigger. Since some routines can have PH.Delay commands in them, I will be paying attention as to how long the routine runs before I hit the 1 to 2 second mark, then add the PH.EnableTrigger command midstream.
Thank you for the help!
Richard
|
Back to Top |
|
|
|
|