oberkc

I did not confirm on my devices, but I believe you make sure a given device is out of all scenes and folders. Once out, right-click on that device and remove from ISY. Factory restore the device, then add back to ISY. My favorite method is to put ISY into linking mode (add insteon device) then put the to-be-added device into linking mode. This should create a new entry in your "my lighting" tree.

I am still a little fuzzy on the relationship between firewalls and antivirus to the ISY, but anything new here in your setup?

My understanding is that insteon is intended to be "scene" driven. If you already have a scene with button A and a load controller, then, rather than your program turning on individual devices, such as the water heater and button A, have your program turn on the scene which includes button A and the water heater. Same approach for the other buttons/scenes. If Control 'KeypadLinc - HomeAway' is switched On And Control 'KeypadLinc - HomeAway' is not switched Off Then set "water heater scene with button A" on set "audio system scene with button B" on etc.... else set scenes off.... Alternatively (and potentially better), you could simple create a master button scene that has main button as controller and all the other devices and secondary keypad button as responder. Taking this approach would require no program.

I don't recall whether I have used this, but there is a program (true or false) condition which I assume can be used to trigger an email message. I can only assume (without refreshing my memory) that is works similar to a "status" in that it would trigger only when changing status .

andrew67 Unfortunately, when we left the world of dumb switches, I believe we accepted these types of problems as the cost of admission. And it gets worse. What happens if smartlabs goes out of business and takes with it insteon? Until we can convince the rest of the world that insteon is the correct way to go, and until insteon becomes open source, and until we can convince people that new features and capabilities are not needed...this is the world in which we live. It is still worth it to me, but I mitigate this risk by wiring in such a way as to allow reverting back to dumb switches. The biggest benefit of the -994, to me, is the growth potential into protocols other than insteon. I just hope that this potential is realized.

One reason that it may not run is tasker. Watch for your location profile as you near home. Does it become active? Are you using gps? WIFI? Cell towers? I think, too, that there are settings governing the frequency that tasker checks for proximity. It could be that this setting is too long, and it is simply not triggering the mobilinc command quick enough.

To expand upon LeeG response... From tasker, you can specify which program path to run, either IF, THEN, OR ELSE. No need to enable the program. If you want a program to run whenever you enter you specific geographic area, simply run run the THEN path of the program.

You won't have to. After a couple of mornings with the cold water treatment, I expect your daughter will suddenly have the ability to wake herself without further outside stimulus.

Given that it appears to be the same X-10 address, my first reaction is to consider the possibility that one of your insteon devices has an X-10 address assigned somehow. Do you see any relationship of the timing of X-10 commands to that of insteon device activity? Neighbor?

I would expect not, since they are not dual-band. This suggests to me two things. First, if you must move your AP closer for your house AP to respond, then it sounds as if your garage is out of RF range. Second, given that your house AP blinks green, then this suggest that they are on opposite legs. Unfortunately, the second point does not much matter if they are out range from each other. I conclude from this that you have communication across the legs of your electrical system based on the house AP and house switches. Good. I assume this is because only those 5-6 are within RF range of the house AP The specified range is "line of site". If you have obstructions, such as walls, electrical boxes, doors, etc.... then range will be diminished. If you have clear line of site, then neither do I understand the reduced range. The garage light switch is, according to the test, on a different leg. Why do you believe otherwise? I also note that LeeG suggested you post an event trace, to which I have not seen a response.

We are installing computers where we once installed light switches. Sometimes, computers require a reboot. By the way, I believe the same results can be had by simply pulling the little tab along the bottom of the switch, and resetting after a few seconds or a minute.

It probably is a bit cleaner, if this meets your needs. My only observation is that there are times when separating the two programs make sense. Keep this in mind as your needs and desires evolve.

What WILL one be using, if not REST? I have contemplated this same thing for a while, but stopped short, for fear of spending time better spent on other things. Did you find this relatively straight-forward, or requiring much research and trial-and-error? Is it as simple as installing the network module and watching the event viewer for network commands as the camera motion sensor is triggered?

I understand the floorplan feature is dead (at least for now). Check out a discussion on the topic: viewtopic.php?f=7&t=29&start=15

scenes will continue to work, regardless of how created. Obviously, programs would not work.

How about: If Control 'Motion Sensor I2CS-Sensor' is switched On and time is from 6:00pm to 3:00pm, next day Then Wait 30 seconds Set 'SwitchLinc Relay' Off Else Set 'SwitchLinc Relay' Off Light will always go off at 3:00pm, regardless of whether the timer has reached 30 seconds.

An interesting idea. Yes, you could create an X-10 device (no physical device necessary). Yes, they show up in mobilinc (at least the android version of mobilinc). Perhaps, then, you could then trigger a program based upon reciept of an x-10 command. This assumes that the ISY sending out an X-10 command would also trigger a program. I don't think I have ever confirmed this. I like it.

Then locate a button in some secret location. Or send a notification when the button is activated. Or use mobilinc. Or use fast-on (unlikely to be used by unauthorized individual). I would think there are ways to thwart or recognize unathorized use.

I am unsure, and curious, what you mean here. 3rd parties? Are you talking unauthorized individuals? If so, put a switch in a desktop enclosure and hide it somewhere. I don't use mainlobby, or eKeypad, but I don't understand the difficulty in what you describe. One button to trigger run-then (variable = 0 or program = true) if staying home. Another button to trigger run-else (variable = 1 or program = false) if going away. Sorry, I don't understand the issue of aborting or restarting anything. I suspect you are. I liked your initial approach (putting programs in a folder). I don't think it is difficult to change a variable from mobilinc, or by running THEN or ELSE paths of a program. There is no need to abort or restart anything that I can think of.

Indeed, it is. I am as puzzled by this as you. The wait suggestions of others is all I can think of. By chance, are either of these two devices controllers of an insteon scene or triggers of other programs? Definitely strange. I would not have predicted this.

I agree that I have not found a quick way to turn a responder into a controller. However, i dont think you have to create all new scenes. Pull the responders out of the scene. Add them back as controllers. Keep in mind that if the one switch is the only one that you want to control the other eight, only the one switch has to be a controller with the rest responders. If you want every switch to turn on all the others, make them all controllers. Think of switches as controller of a given scene. If a switch is controller, it will turn on/off the other devices in that scene. If a responder, it will not turn other devices in that scece on or off.

I am not sure that I understand your configuration or question, but I will make one point... If you want more than one switch to control a single light, make each switch a "controller" in the scene, regardless of which switch actually powers the light.

The next thing I would start to consider is a device failure, or the possibility that your plm outputs a weaker signal than does the other controller. I am hoping you have an x10 plug in module you can plug directly into the same outlet as your plm. I can tell you that my PLM (an older model) works fine with x-10.

Probably so.

That is my understanding, assuming that they are dual-band (not all are). Certainly, access points do. Battery devices, however, do not re-transmit insteon commands.