PurdueGuy

I haven't done this yet, but I would probably have a program (ProgramA) that triggers off the variable (VariableA) being set to 1 by the camera. ProgramA immediately sets the variable back to 0, and starts another program, ProgramB. ProgramB immediately sets VariableB to 1, then waits some set amount of time, and then sets VariableB back to 0. Then you can key other programs off VariableB. If motion happens and keeps happening, VariableB will be set to 1 and remain 1. When motion stops, after say 60 seconds, VariableB will go back to 0. In the meantime, the camera may set VariableA some number of times, but motion programs will only trip once.

I would create a scene (or scenes) that does what you want. Put the lights themselves and the KPL buttons in as both Controllers (which are then inherently Responders). Then I would change the program to call the scene(s) instead of the devices directly. That would keep the buttons and lights in sync, and no double-taps required.

Michael, Sounds interesting...I have been debating doing something like that too, since the router won't be here for a while. I have a recent Mac Mini running full time for my HTPC/Media Server, so I can run it on that. Any pointers for tutorials?

Locally, I just use standard http://IP_ADDRESS:80 I access my cameras in a number of ways, if I am remote. 1) I typically SSH/VPN back to a computer at my home, and look at them that way. 2) I connect to my Vera remotely, which does 1-second image updates for the camera. 3) I (reluctantly) port-forward via my router to each camera, from a random port to the camera port. Once I get my new router than supports VPN from my iPhone, I will no longer need to do #3.

I don't manage the presets via ISY, I do those via the standard camera webpage. I then use HTTP calls from ISY to set the camera to certain presets. For example, to set my camera to Preset2, I use the command: http://CAMERA_IP:PORT/decoder_control.cgi?command=33 To enable the automatic IR: http://CAMERA_IP:PORT/decoder_control.cgi?command=95 When doing this from ISY Network Resource: Protocol Information: - HTTP - GET - Host = IP address of Camera - Port = Port of camera (default is 80) - Path = /decoder_control.cgi?command=XX (replace XX with your command number) - Details -> Headers -> Click Add, choose "Authorization" and fill in the name/password for an "Admin" or "Operator" user (a "Visitor" user shouldn't be able to move the camera, etc) More info here: http://www.zoneminder.com/wiki/index.php/Foscam

If memory serves, the Insteon cameras are rebranded Foscams? If so, read on. I have my ISY controlling one my Foscam cameras. Based on my alarm status and such, the camera is pointed in certain directions (at the front door, rear door, privacy mode, etc) via presets. ISY also turns the enables and disables the automatic IR light. I can then view the cameras via MobiLinc HD. Is that what you are looking for? I leave the motion activation up to the Foscam. It uploads immediately on motion to a remote location.

For the most part, my Airport Extreme can handle coming back in to the network. I use a random external port, and forward that to 443 on the ISY. So even when I am at home, I can connect to the following: https://11.22.33.44:1234/ (replace 11.22.33.44 with your real internet IP, and replace 1234 with your port number, 443, in your case). and my router will forward that to 443 on my ISY. I can do this with ISY and my Foscams. I assign each a random external port, and forward as appropriate.

Glad you got it working! I have had more intermittent communications issues with the newer dual-band KPLs than I ever did my non-dual-band. The dual-band mostly works, then occasionally don't for a bit, then work again. I haven't been able to narrow down specifics (certain lights, refrigerator, etc). I have added some FilterLincs and it helped, but not completely. The older ones either didn't work and I remedied it (either moving an access point, new another device in between, etc), and they they would be flawless. I'm working to relocate ISY for both Insteon and Z-Wave range, hoping that will improve things. I simply haven't had a chance lately.

Building on what LeeG said, if you're firmware is a bit older one, there was a bug in the "Copy Scene Attributes" button. You might need to set the levels manually as LeeG mentioned.

If it is any consolation, I was raised in Ohio!!(born in Indian though...but not a Hoosier!)

Define 4 scenes - High - Medium - Low - Off Each scene will have 5 members, and *only* the appropriate button will be a Controller for a given scene, the rest are Responderes: - Button A (Controller in "High" scene, Responder elsewhere) - Button B (Controller in "Medium" scene, Responder elsewhere) - Button C (Controller in "Low" scene, Responder elsewhere) - Button D (Controller in "Off" scene, Responder elsewhere) - Fan motor (Responder) For each scene, set the fan motor as desired, and set the state of each button as desired. (So for High, the fan motor should be set to high, Button A should be On, and Buttons B-D off). Be sure to define things in the main scene, then click the additional Controller for that scene (Button A, B C, or D) and click "Copy Scene Attributes" to that the Controller programming matches the ISY programming). Then use these scenes in the programs I described above, so you can call them from a Program in ISY, that is triggered via the RemoteLinc.

Would a SynchroLinc (Item# 2423A5) work for this? It can sense when the pump turns on and off, which notifies ISY. If it's on too long, kill power via an appliance module?

I do this already. Unfortunately I can't access my ISY right now, so this is from memory, and the formatting/exact syntax is not right. I have 4 programs: Off: if (Control RemoteLinc.D is turned Off AND Fan is Low) OR (Control RemoteLinc.D is turned Fast Off) Then Set scene FanOff to On Else -none- Low: if (Control RemoteLinc.D is turned On AND Fan is Off) OR (Control RemoteLinc.D is turned Off AND Fan is Medium) Then Set scene FanLow to On Else -none- Medium: if (Control RemoteLinc.D is turned On AND Fan is Low) OR (Control RemoteLinc.D is turned Off AND Fan is High) Then Set scene FanMedium to On Else -none- High: if (Control RemoteLinc.D is turned On AND Fan is Medium) OR (Control RemoteLinc.D is turned Fast On) Then Set scene FanHigh to On Else -none-

I believe you could run into the same issues running a Revolv/ISY combo you might have running a HouseLinc/ISY combo. Each might think it is the sole master, and if you have to reset a device, only part of the configuration gets written to it when you restore. That being said, they might get along just fine, so long as you don't have them walking all over each other. However, anything that the Revolv would do the ISY won't know about. Since ISY watches Insteon commands (and it knows how things are set up), when it sees a switch toggled, it knows what effect that has on other devices, and adjusts state internally. That potentially triggers programs, etc. If Revolv sets up a scene, and a user toggles a controller, ISY won't know/understand what's happening, and not update, since it doesn't know about that scene in the first place.

Use a different scene for each. viewtopic.php?f=27&t=14087

If the motion sensor is built into the light, there probably isn't enough power going to the unit to power it up. When the microswitch is off, the motion detector essentially isn't getting any power, so it is essentially off. Since the motion detector is off, it can't engage the relay to turn the light on, which the Micro module would sense and then provide full power.

I have been battling this same issue since I got new dual-band dimmer KPLs. They simply don't work right. I resorted to creating special scenes to turn them off, and run a program a few seconds after any button is pressed that turns them off. It's rather annoying.

Many people (myself included) use DSC security systems, with an Ensvisalink 3DS for monitoring. I then run DSCLink on a Raspberry Pi as the go-between for ISY and the DSC system. DSC is a popular brand, often resold by ADT. You can do it yourself wired or wireless. A great resource is: http://www.diyalarmforum.com

You're welcome! As far as the response, I haven't even looked at it in so long, I don't remember. I will have to check. Can you try setting the timeout longer? Maybe the blaster takes too long to send the command, and the ISY gives up waiting for a response?

I have mine setup. Here is how to send an "Off" to my Samsung TV. Configuration -> Networking -> Network Resources HTTP POST Host = IP of blaster Port = 80 Path = /docmnd.xml Body = <?xml version="1.0" encoding="utf-8"?> How I got the "ir_data" is tougher. I found a spreadsheet to convert Samsung HEX codes into pronto codes. It can be found via Google, but I know some people are wary of opening Excel files. I also found codes on RemoteCentral: http://www.remotecentral.com/cgi-bin/fi ... br=samsung It was a trial and error process to get them to work. You can go to http://BLASTER_IP/api.html and test things out. Be sure you are getting the lights on the blaster to blink first, so you know you are sending at least valid commands (then work on the IR data). Also, this is with a Gen 1 (wooden) blaster. The Gen 2 blasters have addressable IR emitters and are probably a little different.

A friend that uses an e-cigarette can set my smoke detector off easily.

I've done it in by my bedroom KPLs to make 6 button KPLs, but in the following configuration: -BUTTON1- -BUTTON2- BTN3 BTN4 BTN5 BTN6

Try excluding the lock first. It could be in an old Z-Wave network you had, or in an old Z-Wave network from being tested at the factory.

Did you make any programming updates lately? Sounds to me like you might have a program that fires based not status of some device. That device is then updated by the program, causing the program to re-trigger. Check Programs -> Summary and click "Last Run Time" twice to sort by most recent date.

Valencia huh? I am down in Long Beach...it's not often I am out yet way, but I can try to help out some time (gratis)! But as Teken said, post your items here, and someone can help out. As for the KPL button not reflecting actual status, it is probably caused by interacting with the device itself, and not through a scene. Take your fountain...I have one too, connected to an outdoor module. Create a scene, call it "Fountain" and have 2 entries: - Fountain outlet/module (at least as a Responder, and as a Controller if supported) - KPL button as a Controller Add the KPL button as a Responder to the "all lights off" scene. (it sounds like the Fountain module is already a Responder to that scene). Now, whenever you want to turn the fountain on, do not turn the fountain device, but instead, turn on the scene. That will turn on the fountain module and the KPL button. Do the same when turning the fountain off. You can run that scene from the Admin Console, Dashboard, MobiLinc, or a program. Things should stay in sync (assuming there are no communication issues!)