Switchboard (Formerly Indigo Security Script)

1) It appears when any single device is turned on the monitored device group will actually show 2 devices triggered:

Found it. The key was "Turn on". This only occurred if it was a device that had been Turned On via an on button. TriggerLincs, and DS10A's wouldn't cause it.

I will try to bundle up a new release for Friday.

Okay, here's the newest release of Switchboard.

https://dl.dropbox.com/u/241415/Switchb ... 0v0.73.zip

The changes since v0.72 are:

• If a device was turned on via a "Insteon command", the Number_Triggered_Devices count would start at 2 instead of 1. This did not occur with DS10A's, or Triggerlincs.
• The X10 Devices now report the X10 Security code in the Indigo Device List. (The address field in the Device List will show the Security Code)

- Benjamin

Okay, here's the newest release of Switchboard.

https://dl.dropbox.com/u/241415/Switchb ... 0v0.73.zip

The changes since v0.72 are:

• If a device was turned on via a "Insteon command", the Number_Triggered_Devices count would start at 2 instead of 1. This did not occur with DS10A's, or Triggerlincs.
• The X10 Devices now report the X10 Security code in the Indigo Device List. (The address field in the Device List will show the Security Code)

- Benjamin

That resolved it Ben!
Thanks!

The Last Triggered and Last Updated timestamps always seem to be the same for me. What situation would cause the two timestamps to be different? (Just Curious)

Okay, here's the newest release of Switchboard.

https://dl.dropbox.com/u/241415/Switchb ... 0v0.73.zip

The changes since v0.72 are:

• If a device was turned on via a "Insteon command", the Number_Triggered_Devices count would start at 2 instead of 1. This did not occur with DS10A's, or Triggerlincs.
• The X10 Devices now report the X10 Security code in the Indigo Device List. (The address field in the Device List will show the Security Code)

- Benjamin

That resolved it Ben!
Thanks!

The Last Triggered and Last Updated timestamps always seem to be the same for me. What situation would cause the two timestamps to be different? (Just Curious)

The Last Updated, is literally the last update timestamp for the device.

The Last triggered, is typically going to be the same as the Last Updated, since Triggering the device causes it to be updated.
But, it's possible that a 3rd party package could modify a value, and thus the Last Update could be different than a device activation...

That being said, I doubt that they would be different, or if they are probably only by a few moments...

(The two fields are simply there for future expansion....)

- Ben

If you are setting up a control page to show various switchboard device states, the states listed in the drop down box do not have correct names. you have to do trial and error to get the state you want? Can this be changed?

"The device was last triggered at" is actually the device ID

The first (there are 2) "The device that was last triggered" is actually the date and time of last trigger

If you are setting up a control page to show various switchboard device states, the states listed in the drop down box do not have correct names. you have to do trial and error to get the state you want? Can this be changed?

"The device was last triggered at" is actually the device ID

The first (there are 2) "The device that was last triggered" is actually the date and time of last trigger

Thank you for pointing that out. That will be fixed in v0.74, I will probably release it this weekend.

- Ben

Thanks Ben

I'm just getting this set up (moving to it from the prior Security Script). What do I need to do to have the plugin only alert me via email when a heartbeat timer expires?

Also, while it appears to be triggering the _Open action group, it is not triggering the _Closed action group. Any ideas?

Also, while it appears to be triggering the _Open action group, it is not triggering the _Closed action group. Any ideas?

X10,Insteon, or both?

- Ben

Also, while it appears to be triggering the _Open action group, it is not triggering the _Closed action group. Any ideas?

X10,Insteon, or both?

The group consists entirely of X10 DS10A security sensors.

Also, while it appears to be triggering the _Open action group, it is not triggering the _Closed action group. Any ideas?

X10,Insteon, or both?

The group consists entirely of X10 DS10A security sensors.

I just made a change which should fix this. I have tested it, but I would like you to give it a try and ensure that it meets your needs...

Please drop me a line at Benjamin AT schollnick DOT net, and I will forward you a copy of 0.74.

- Benjamin

I'm just getting this set up (moving to it from the prior Security Script). What do I need to do to have the plugin only alert me via email when a heartbeat timer expires?

Right now. It can't...

I can certainly add that in.. Is that a feature that you would want?

I'm just getting this set up (moving to it from the prior Security Script). What do I need to do to have the plugin only alert me via email when a heartbeat timer expires?

Right now. It can't...

I can certainly add that in.. Is that a feature that you would want?

Indeed. I actually don't use any of this for "security". I use the door sensors as another way of detecting activity in the house (for triggering lights) and the window sensors to turn on/off the AC. The only thing I really want to have emailed to me is when I need to change the batteries.

I'm just getting this set up (moving to it from the prior Security Script). What do I need to do to have the plugin only alert me via email when a heartbeat timer expires?

Right now. It can't...

I can certainly add that in.. Is that a feature that you would want?

Indeed. I actually don't use any of this for "security". I use the door sensors as another way of detecting activity in the house (for triggering lights) and the window sensors to turn on/off the AC. The only thing I really want to have emailed to me is when I need to change the batteries.

I'll add it in.

I actually don't use any of this for "security".

And that's a perfectly valid point...

That's one reason the plugin was renamed. Switchboard has outgrown the Security ONLY aspect.
It's now ideal for many different uses....

- Ben