Xathros

I have run 25' with no problems. I don't think I'd want to push it any further than that though. My Current install is 1.5' -Xathros

I don't think re-flashing 3.3.10 on top of 3.3.10 would have any downside. I considered doing it myself last week but realizing there was not difference from when it was called RC7, I just removed "Beta RC7" from my signature instead... There have been many posts from people whose ISY's did not reboot after a firmware upgrade and required a power cycle. I would be surprised if it needed anything more than that. Mine has never done that but I don't use UPNP or DHCP for my ISY so that may have saved me from this issue. My ISY has only locked up twice that I can recall (once last week) but I attribute both to PLM problems. -Xathros

Other than the fact that the ISY will respond to a ping sent from a computer or other network device. -Xathros

kstock- Relay, Yes - It is a responder type device. Sensor, No - It is a controller only device. It cannot be turned on/off via a command. It Sends On/Off commands to responders/ISY PLM. -Xathros

That sounds more like a scene failure to me. A direct command failure usually results in a "Can't Communicate" popup in the admin console. -Xath

Hi. I've been lurking in the background watching this thread. This makes the most sense to me. Both the remove and re-add to get all the nodes and On=Wet/Off=Dry. -Xathros

Well, you could tell the program to set the Kitchen SWL On/Off rather than the scene. That would at least give you the built-in retries of a direct command. Probably best to solve the comm issues though. -Xathros

OK this makes more sense now. When operating a scene, the ISY does not verify that the SWL actually turned on/off and so does not retry in the event of a failure. When Operating the SWL with a direct command, the ISY expects a response and if it doesn't get one, it tries two more times before giving up and saying "Unable to communicate with...". You have marginal comms between the PLM and the SWL location based on your above description. It seems the MS and whatever dualband device it is communicating through have good comms to the SWL since it is able to operate the SWL as a scene controller. Run a level 3 event trace and turn on/off the swl (device) a few times from the Admin console. Lets see what we get for comms. -Xathros Edit: Hehe. LeeG beat me to it!

It's currently configured with a 5 minute timeout, sending both ON and OFF commands and set to do it all day, not just at night. I tried setting it to send ON only, but then the ELSE statement never ran.... I guess I could modify the program so it turns the scene on, waits 5 minutes, then turns the scene off all in the THEN statement and tell the motion detector to only send the ON commands. Might that work better? How does everyone else seem to do it? There are a number of variations. A) MS as controller of Scene On/Off with timeout. MS As controller of Scene On Only with a program to delay and turn off. C) MS not in a scene On Only with programs to watch for On and delay for off. A&B offer fast light response on motion but less control over when the light are enabled/disabled on motion. C offers the greatest flexibility but has an inherent 1 - 2 sec delay between detection and response. Now, back to your problem... Are you seeing the MS Status change in the admin console? I assume you are letting the MS timeout and turn off then moving to cause an On correct? -Xathros

How is the MS configured? Is it in occupancy mode? Is it sending On Only? What is the timeout delay? -Xathros

This sounds to me like the ISY is unable to communicate with the switchlinc. Are you able to turn the scene on/off from the admin console? Can you turn on/off the switchlinc directly from the admin console? -Xathros

This is how I got there: viewtopic.php?p=74728#p74728 -Xathros

I do this by scanning the ARP table on my router for specific mac addresses and update variables in the ISY based on the results. Works pretty well but I have found that the iDevices tend to come and go frequently (to conserve battery I'm sure) so I have had to build in delays to prevent actions based on disconnects for 5-10 minutes to ensure a device has actually left (or run out of battery). -Xathros

Mine is damn near identical to Dwight's only I have 2 remotelinc buttons assigned to dim (run Then) or brighten (run Else) from my night stand. Every once in a while a command will get missed and my bedroom kpl or one of my switchlincs won't dim at night. I press my dim button and it's all better. -Xathros

My transition from the 99 to the 994 was much like oberkc's experience. I have A10/X10, Network and Climate modules - all transferred within a few minutes of my email request to UDI. After I restored my backup from the 99, all I had to do was change my static network settings, customized location and reload a few files that I kept on the ISY's web server (not included in the backup). Like oberkc, it was quite painless and only took a few minutes to complete. -Xathros

Anytime. Happy to help. -Xath

drunkwithpower- A normal Fan Light circuit would have power to the switch then 3 wires (red, wht, blk) from the switch to the ceiling Jbox with the red and black switched. For the Keypad and Fanlinc, you won't be switching the power at the switch(KPL) location. You can just cap the red wire at the switch box and the ceiling box and pass the 120V along the black to the ceiling box. The KPL and Fanlinc will both need uninterrupted power. The switching will all be logical (Insteon) between the KPL and the fanlinc. Even the red load wire from the KPL will get capped. Hope this makes sense. -Xathros

All- ISY HOWTO: Copy a Scene 1) Create a new empty scene. 2) Select end expand the scene you want to copy in the left panel (Tree) 3) Click the first entry in the scene to copy, hold Shift and click the last entry in the scene. This selects all entries in the scene. 4) Drag these into the new empty scene. 5) Answer "Yes" to any prompts to add as responders. Anything that is a controller in the original scene will only add as a responder in the new scene as any device can only be a controller for a single scene. HTH -Xathros

Michel- A full shutdown then startup or a simple restart - either way same result. -Xath

There is an outdoor Appliancelinc that could be used to power something noisy. -Xathros

Does the switch controlling the back porch lights support the beep function? If so, send a beep every 5 seconds or so. -Xathros

RichTJ99- When the last sensor switches off, the If re-evaluates to false, the wait is interrupted and the program runs the Else path with no timer etc. Try changing Status MS On to Control MS on and I think you will be fine. Alternatively, you could move the Then section to a separate program but I think just switching to Control in the If will solve your problem. -Xathros

Michel- After every restart. If I just sleep the system and resume the next day, the setting remains just fine. -Xath

Understood. As I said somewhere above, I may be confusing this with another similar thread regarding the requirements. I tend to over think things at times and too often apply a level of "How would I want this to work?" when posting examples here. In this case - probably some of both. Between what we have both posted, I think he's got plenty of ideas to work with. -Xath

Oberkc- While this approach works to dim the lights at the prescribed time, it does not deal with what happens if someone were to operate a controller of the original scene or the load bearing dimmer itself. This is why I took the adjust scene approach using the single scene. For situations were the devices are entirely program controlled, yours seems like an excellent solution. -Xathros