Protecting Programs from Accidental Changes

[gsownsby]

As with most things, it seems that most home automation control functions fall into "classes" of importance. Functions that are more important should be more carefully approached in design, execution, and change management than less important ones.

 

With that logic in mind, I was wondering if there is a way within the current ISY99i feature set to help make sure that more important things are somewhat protected from changes or accidental "influences" by people, or other ISY programs, RemoteLincs, KPLs, etc.

 

An example would be the light on our mailbox post. It's programmed for dusk to dawn operation (on) with the ISY99i via a SwitchLinc Relay Switch. As everyone in our neighborhood has the same type of mailbox post light, if we accidentally turn it off...no harm done. So for my programming logic, it's a "class 3" nice-to-have working well but not critical if it skips a beat once in a while.

 

There are other functions though that one has to be careful with for instance, if your ISY controlled intrusion detection, electronic locks, or other similar more important functions. I wouldn't want to accidentally change or disable such a program or function.

 

How does one approach that within the ISY/Insteon environment? Some things are obvious like don't program a RemoteLinc with something super important or it might get accidentally turned on or off by someone not aware of what a specific button did.

 

At the program level, I don't see any clearcut ways of controlling this situation other than placing really important programs in their own folder labeled "Important Programs - Be Careful". That doesn't really do anything per se other than a visual reminder/warning that messing with programs in this folder might produce undesirable consequences.

 

Does anyone else have this concern? How do you approach it? Even most cell phones have passcodes to block out accidental changes or use. May be a new ISY feature some day? Thanks.

[MikeB]

What kind of protection would you envision? If you want a button to control whether or not a program runs, then that seems to be your weak point. But it's a choice - do you want an easily accessible button to stop or start this particular function, or not? You could make the button press a bit more difficult to do accidentally, like maybe a FAST ON or FAST OFF.

 

Also, you could setup notifications in the ISY to alert you if something you consider important is no longer in the state you'd like it to be...

[MikeB]

Also, check out this thread I started a while back:

 

http://forum.universal-devices.com/view ... light=kids

 

Maybe the basic idea could be useful to you?

[Sub-Routine]

There are plans for using separate passwords for the HTML interface and the Administration Console, which is why you have to sign in twice to use the AC.

 

In the AdminCon, under Configuration/System you can select from a list of access control for the HTML pages (HTML Role). I have mine set to Basic which allows a user to Run or Stop programs but not to be able to Enable/Disable programs.

 

I have programs that monitor the presses of some switches to call new scenes upon a press and eventually return scenes to the default settings.

 

For example, all my Outside Lights are on a dim state all night. If someone has a reason to turn on any one of these lights all the outside lights come on bright.

 

These are in my Midnight Folder

Folder Conditions for 'When Midnight'
Add conditions to limit when programs in this folder are allowed to run.



If
       From    11:00:00PM
       To       4:44:00AM (next day)
   And Program 'Vacation On' is False
    Or From    11:59:00PM
       To       5:14:00AM (next day)
   And Program 'Vacation On' is True

Then
  Allow the programs in this folder to run.

 

 

Backyard On

If
       Control 'Backyard' is switched Fast On
    Or Control 'Backyard' is switched On

Then
       Set Scene 'Outside Lights' Fast On

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

 

When the switch is pressed Off another program runs which returns the lights to the overnight state.

 

Backyard Off

If
       Control 'Backyard' is switched Off
    Or Control 'Backyard' is switched Fast Off

Then
       Set 'Backyard' 49%
       Run Program 'All Off OL Dark' (Then Path)

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

 

 

All Off OL Dark

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

Then
       Set Scene 'Outside Lights - Evening' On
       Wait  3 minutes 
       Wait  2 minutes  (Random)
       Set Scene 'Outside Lights - Midnight' On

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

 

I have similar programs for other times.

 

Rand