Triggerlinc question? Driveway alarm?

[RichTJ99]

Hi,

 

I have a driveway alarm & I was thinking of seeing if I can get the triggerlinc working with it.

 

Ideally, i would like an email sent to me when the alarm goes off.

 

I see it has a relay, its a little hard to see in my photo.

 

It has the following (from left to right):

 

12vac, system common, 12v dc, earth ground, 18v dc, NO, Common, NC, FLC, Shield, black, red

 

I would like the triggerlinc, to normally report that it is off, when a car goes over, the triggerlinc should tell me that its on, when the car goes off the alarm, it goes back to off.

 

What would be the right way to wire it?

 

Thanks,

Rich

[LeeG]

Use Common and NC to connect to the TriggerLinc. When the external connection is shorted the TriggerLinc is Off. Open the external connection the TriggerLinc reports On.

[RichTJ99]

So I pulled my triggerlinc (I have 6) out of storage. I moved so I am slowly getting my insteon stuff working.

 

I now have a ISY994i vs my old isy99i which is still in a box somewhere.

 

I added the trigerlinc to the ISY994, however I am not seeing any status updates.

 

If I move the magnet close & away the light flashes indicating that its working but the status does not change on the ISY for either Main: Trigger Open or Main: trigger closed.

 

Any ideas on what is causing the issue?

 

Thanks,

Rich

[LeeG]

What ISY firmware is being used?

 

Try a new battery and moving the TriggerLinc closer to a Dual Band device

 

EDIT: if there is an External connection the magnet will not register a change in state

[RichTJ99]

ISY994IR Pro

3.2.6

 

I am using brand new batteries & it is within 10 feet of 3 dual band switches.

 

These are gen1 (version 00) triggerlincs. They did work fine with my old ISY99. I could grab one of my old plug in access points.

 

The level 3 event viewer shows nothing from the devices.

 

I have two, one with a external magnet, one without. Neither seems to register anything/

 

Any ideas what else I could try?

 

Thanks,

Rich

 

 

EDIT: The current state on both triggerlincs is blank. For open & close on both devices.

[LeeG]

The TriggerLinc is a Controller Only device. Current State will be blank until the ISY receives a command from the TriggerLinc.

 

I would try an Access Point plugged into the same outlet as the ISY PLM with the TriggerLinc close to the Access Point.

 

Insteon RF communication is automatic and autonomous. There is nothing the ISY can do for or against RF communication.

 

The link records in the TriggerLinc can be verified with a Show Device Links Table.

 

Are other RF devices working?

[RichTJ99]

It says:

 

 

Device Links Table: Main: Trigger-opened / 11 bd e7 1

OFF8: E2 01 1B.FD.15 FF 1F 01

OFF0: E2 01 1B.FD.15 FF 1F 02

OFE8: 00 00 00.00.00 00 00 00

 

 

It seems like the ISY is seeing it but somehow its just not working? Any ideas on what to try next?

 

I did take an old access point & plugged it in within 5 feet. I see the light flash when the magnet is moved to & away but the ISY doesnt seem to register the change.

 

Thanks,

Rich

[RichTJ99]

Are other RF devices working?

 

That is a good question, all my devices are a combo of dual band & non dual band devices. I have a few triggerlincs I am now playing with & if I could find a 9v battery, I could try my motion sensor.

 

How do you check communication levels?

[RichTJ99]

One more...

 

I was standing next to my access point & i see that the status light on the access point seems to flash in sync with my triggerlinc magnet movements. Meaning when I move the magnet, the access point seems to respond. The ISY is not seeing the activity though.

 

Is there a possiblity that the devices are still synced with the old ISY?

[LeeG]

Is the Admin Console showing state changes of other devices?

 

The link records in the TriggerLinc are what are expected assuming the PLM address is 1B.FD.15.

 

Run Tools | Diagnostics | PLM Info/Status to verify the PLM address matches that in the TriggerLinc records.

 

The last thing would be a Restore Modem (PLM) to insure the Responder link records for the TriggerLinc exist.

 

Regarding the last post, the TriggerLincs were added to the new ISY as new devices? This is not a situation where an old ISY backup was installed on a new ISY and PLM?

 

There is no means of checking RF levels

[RichTJ99]

Is the Admin Console showing state changes of other devices?

 

Yes, everything else seems to change just fine.

 

The link records in the TriggerLinc are what are expected assuming the PLM address is 1B.FD.15.

Run Tools | Diagnostics | PLM Info/Status to verify the PLM address matches that in the TriggerLinc records.

 

Yes, it says 1B.FD.15 v99 / connected

 

The last thing would be a Restore Modem (PLM) to insure the Responder link records for the TriggerLinc exist.

How do I do that?

 

Regarding the last post, the TriggerLincs were added to the new ISY as new devices? This is not a situation where an old ISY backup was installed on a new ISY and PLM?

 

 

The triggerlincs were added as new devices. I never used anything from the old ISY backup data. I am using a brand new ISY/PLM. From my reciept im May: http://www.smarthome.com/12236DB/ISY994 ... PLM/p.aspx

 

Its all brand new. I guess I could plug my old ISY & PLM in to see if it works.

 

I am adding it by going to new Insteon device, entering the address, giving it a name, then choosing triggerlinc. I also tried rebooting the ISY which didnt help. I am at a loss, the only thing I am wondering if its related to the triggerlincs being generation 1 devices?

 

Thanks,

Rich

[LeeG]

I am not aware of TriggerLinc operational/functional differences based on which version is being used.

 

File | Restore Modem (PLM) to rebuild the PLM link database

[RichTJ99]

So it seems that did the trick. Each time I add a triggerlinc, I need to restore links in order for the ISY to start seeing status updates (what a wierd quirk).

 

Add device, restore PLM links, then it works.

 

Either way it works.

 

For a test, I wanted to make it so when the driveway alarm went off, the front door lights go on for 2 minutes, then turn off.

 

For some reason, they go on, but not off.

 

If
       Status  'Main: Trigger Drive-Opened' is On

Then
       Set 'Outside: Main Front Door' On
       Wait  2 minutes 
       Set 'Outside: Main Front Door' Off

Else
  - No Actions - (To add one, press 'Action')

 

Any idea why?

 

The idea being when opened, it goes on, then will shut itself off. I plan to do that with my all on outside scene & for 20 minutes, only at night. I do want to start playing with email notifications too when someone comes.

[LeeG]

When statements after a Wait are not executed it means the If Condition has changed before the Wait time has expired. The If becomes False, driving the Else clause.

 

EDIT: one solution is to move the Then processing into a second Program. When the If Condition in the first Program changes it will not affect the Wait in the second Program

[RichTJ99]

So the second program should be set to go after the first program has activity?

 

Meaning if the first item is the driveaway alarm changing from closed to open, then it should run program #2?

[oberkc]

So the second program should be set to go after the first program has activity?

 

yes. The second program "then" statements would duplicate those currently in the first. The second program would have no "if" statements.

 

Meaning if the first item is the driveaway alarm changing from closed to open, then it should run program #2?

 

Yes. Typically, the first program "then" statement would be modified to read something like:

 

then
run "program 2" (then path)

[LeeG]

Program 1

If
       Status  'Main: Trigger Drive-Opened' is On

Then
       Run Program 2

Else
  - No Actions - (To add one, press 'Action')

Program 2

If


Then
       Set 'Outside: Main Front Door' On
       Wait  2 minutes
       Set 'Outside: Main Front Door' Off

Else
  - No Actions - (To add one, press 'Action')

[RichTJ99]

So how should this work if either multiple people come, or the same person drives up (sets off alarm), drops off a package, then drives off within 5 minutes?

 

I would need to watch to make sure that the driveway alarm sensor is a single NO command, meaning as the front tires go on, it may go from NC to NO, then the rears could also set off a NC/NO command.

 

Should the program care or get reset each time? Should the 2 minute counter get reset each time someone drives over it?

[LeeG]

Use one Program and change to If Control. Each new On command from the TriggerLinc restarts the process with a new Wait interval.

 

If

Control 'Main: Trigger Drive-Opened' is switched On

 

Then

Set 'Outside: Main Front Door' On

Wait 2 minutes

Set 'Outside: Main Front Door' Off

 

Else

- No Actions - (To add one, press 'Action')

[code]

[RichTJ99]

So I went to do some testing & I have found that it works, but after the 2 minutes when the light goes off, I waited another minute then drove over it again expecting to see the light go back on. It did not.

 

Is there a time limit on it?

[RichTJ99]

This is what I have now - Should it reset the timer to 20 minutes each time someone drives by? Say I drive in at 6pm, & my wife comes in at 615? Will it turn off at 635?

 

If
       Status  'Main: Trigger Drive-Opened' is On
   And From     5:35:00PM
       To       6:35:00AM (next day)

Then
       Run Program 'Driveway Alarm Lights2' (If)

Else
  - No Actions - (To add one, press 'Action')

 

(Driveway 2)

 

If
  - No Conditions - (To add one, press 'Schedule' or 'Condition')

Then
       Set Scene 'Outside' On
       Wait  20 minutes 
       Set Scene 'Outside' Off
       Send Notification to 'Default' content 'Driveway Alarm Alert'

Else
  - No Actions - (To add one, press 'Action')

[LeeG]

"Should it reset the timer to 20 minutes each time someone drives by?"

 

Yes. Assuming the TriggerLinc goes back to Off Status before next vehicle trips. I confirmed with a working example here.

 

If things do not work as expected be sure Program changes have been saved. Also note that the TriggerLinc could be out of reliable RF range. The Event Viewer with Level 3 selected will show by timestamp on TriggerLinc traffic if it has turned Off and then turned back On

 

EDIT: this is the example I used to verify operation.

 

If
       Status  'TriggerLinc1-Opened' is On

Then
       Run Program 'TriggerLinc2' (If)

Else
  - No Actions - (To add one, press 'Action')

If
  - No Conditions - (To add one, press 'Schedule' or 'Condition')

Then
       Set 'ICON Relay 1' On
       Wait  10 minutes 
       Set 'ICON Relay 1' Off

Else
  - No Actions - (To add one, press 'Action')

[RichTJ99]

I will play with this more. I have two more questions:

 

1. How do I add a feature that if the scene: Outside is already on, then it should do nothing?

2. How do I disable the program - say I drive home, see the lights are now turned on for 20 minutes, decide I want to stay outside & keep the lights on? Is there something I can do aside from waiting for the lights to turn off, then manually turn them back on?

 

So far, this program is great!

[LeeG]

“1. How do I add a feature that if the scene: Outside is already on, then it should do nothing?â€

 

This is the condition where the Wait should be extended in previous posts. Not sure what you want here. No longer extend the Wait?

 

If the outside light(s) are turned On with a different switch or KPL button that button/switch being On can be added to the If conditions such that the TriggerLinc On does not do anything when the button/switch is On (manual override if you will).

 

“2. How do I disable the programâ€

 

Another Program can be triggered with the manual override switch/button turning On which in addition to turning On the outside light(s) it can Stop the second Program. That is a variant of the Action statement, like Run Program there is a Stop Program.

[oberkc]

I will play with this more. I have two more questions:

 

Having followed this topic for a while, it seems to me that this has been a case of trying to hit a moving, and sometimes undefined, target. Often times, "adding features" drives a whole different programming approach, necessitating starting from the beginning. I suspect your requested feature is one such example.

 

Now that you have gotten your program to work, my suggestion is to live with it for a bit, then re-evaluate your requirements. Once you have done so, write them down and post them here. For example:

 

a) trigger lights from driveway sensor. If lights are currently off, turn on, wait for 20 minutes, turn off? If lights are currently on, do nothing? (or restart 20 minute countdown?)

manual control of lights? How do you want your driveway trigger program to respond if you had previously manually turned the front lights on? How do you want your driveway trigger program to respond if you manually turn the front lights on during the countdown period?

c) if the front lights are currently on, do you want the response to adriveway trigger to be different based on how the lights were originally turned on? For example, respond one way if the lights are currently on as a result of a manual action, and respond a different way if the lights are currently on as a result of recent driveway incursion?

d) Do you want other insteon devices, besides the sensor and main front door switch involved? For example, do you want (or are you willing) to add a third device (keypad button, switch) to act as a manual override?

 

My experience is that it is best to contemplate WHAT you want do do before determining HOW you want to do it.