MikeB

Glad to hear you're all set. I was about to pull out my IRLinc and see if I could duplicate your issue. FYI, I make it a habit to factory reset all Insteon devices before installation.

You're right, their docs are a bit vague about it - but yeah, that's how it works. You can set the timeout period via the ISY as well. Simply highlight the Motion Sensor in your device list, then click the Set Options button and follow the on-screen instructions.

The Motion Sensor's "ON ONLY" mode actually behaves just like the default "ON/OFF" mode as far as the timeout is concerned. You still need to have the timeout period pass with no motion before another ON command will be sent from it. The ONLY difference is that it will never send an OFF command. The difference between STATUS and CONTROL is that a STATUS program will trigger whenever the status of a device (or anything else in your IF statement) changes. For example, if your motion sensor is in ON only mode and you use this program: If Status 'Motion' is On Then Set Scene 'Kitchen' On Else - No Actions - (To add one, press 'Action') ..it will only work the first time motion is triggered. Since the motion sensor never sends an OFF command, the ISY's status won't change to OFF and thus will never change to ON again. The CONTROL statement, however, will trigger any time a command is received - not just when the status changes. So, even if the status of a device is already ON, subsequent ON commands received will still trigger a CONTROL program. So, in ON only mode, a program like this would be better suited: If Control 'Motion' is switched On Then Set Scene 'Kitchen' On Else - No Actions - (To add one, press 'Action') EDIT: Thanks Rand! Seems we keep criss-crossing today.

Hi Wayne - I sent you an email.

The initial programs are definitely contradicting eachother. Based on the situation you're describing, I think what Rand suggests is far, far better. Why not just create a scene called "Motion Inhibitor" or whatever and drag both KPL secondaries into the scene as controllers?

Wayne - Under the Configuration tab, assuming your ISY is set to sync with the time server "pool.ntp.org", do you get any error when you hit the "Synchronize Now" button? This test might help us determine if your ISY is able to access the internet at all. Is your ISY set to a static IP address? Have you tried rebooting your ISY? How about your router?

Hey Wayne - 50001 indicates that the ISY was unable to communicate with your mail server (timed out). Are you using the default ISY notification server, or a different server? What settings are you using?

Hey Wayne - I apologize. I meant to ask if you had any errors in your Event Log (TOOLS, LOG).

Hi Wayne - Notifications are still working here on 2.6.15 using either a custom SMTP server or the default UDI server. Can you provide any more details? Are you getting an error when hitting the TEST button? Any errors in your event viewer?

Hey Jason - Two suggestions. 1 - Are you using 60000 for the SSL port? If so, try HTTPS://... instead. 2 - Many routers will not forward correctly if you try to access your external IP from inside your LAN. Can you try to access your ISY from an outside location?

How about something like this: If Control 'Motion Sensor' is Off And Control 'Motion Sensor' is not On Then Wait 30 seconds Set Scene 'Lights' Off Else No Actions I haven't tested this, but I believe this would turn the lights OFF 30 seconds after receiving the Motion Sensor's OFF command UNLESS more motion is detected during that 30 seconds.

Hey John - You want to make sure you clear your cache AFTER you upgrade, and be sure ALL browser windows are closed. If you clear your cache before, you still need to run the Admin Console to perform the upgrade which loads it back into the cache. So the procedure would be: - run Admin Console and install upgrade - close all browser windows - clear Java cache - launch browser/new Admin Console

Hey Gregory - ELSE will run when something in the IF statement is specifically not true. For example this program: If IR '1' is Pressed And IR '2' is not Pressed Then Set Scene 'TheaterMain' On Else Set Scene 'TheaterMain' Off The THEN statement will run if the program is TRUE (IR 1 is pressed), and the ELSE statement will run if the program becomes FALSE (IR 2 is pressed).

Glad to hear you're all set!

We have released a new firmware version "2.6.0" to fix the issue upgrading the ISY-26 to this latest firmware release. Please follow the steps detailed in the 1st post of this thread. In short: - download/install firmware 2.6.0 (do not use a previously saved copy) - download/install firmware 2.6.15 Sorry for the inconvenience!

I believe you will find that the Motion Sensor will send additional ON commands after the timeout period (1 minute I believe). It will not send the command at every motion. The only difference in this mode is that an OFF command will never be sent (so the ISY will always show a state of ON). I believe you would have to block light to the Motion Sensor for 3-6 minutes before it will trigger the 'dusk' command. I'll let someone else answer this.

There is currently an issue upgrading the ISY-26 to this firmware (release 2.6.15). For the ISY-26, please stay with release 2.6.14 until further notice. Thanks, and sorry for the inconvenience.

You're right, there is no way to "air gap" an OutletLinc. If they are on a different circuit than your PLM, you could try powering down the breaker they are on and testing communications to some other device. If you have an ApplianceLinc or LampLinc, you could plug it in right to the back of the PLM and see if you are able to communicate with it. But, based on your description it honestly does sound like a failed PLM to me. You have a very old rev firmware (4A) as far as I can tell, so an upgrade is probably for the better anyway. Please keep me posted.

Have you tried rebooting both the ISY and PLM, or are you just rebooting the ISY? Did everything stop working right after the electrician? If so, and if it's possible, I would unplug/airgap/disable everything he added to see if the problem goes away. If it does, you can add things back in to see what's causing your issue. Otherwise it sounds to me like you may have a bad PLM.

Personally I'd do it like my examples. I'd check the status of 1 of the status buttons, and if its not correct, then send the command to the entire group.

Right, except that you have the potential of sending redundant OFF commands. If the button is already off, there's no logic in your program to stop it from sending additional OFF commands every time the program is re-evaluated as TRUE.

Sorry, maybe I'm not being clear with what I'm saying. The problem isn't that it's querying the other devices - it's not. Like you said, the ISY already knows the status of those devices. The ISY simply re-evaluates the program if the state of ANY of the devices in the IF statement changes. If the program is once again true, it runs the THEN part. If the program becomes false, it runs the ELSE part.

Correct. The problem is that the ISY re-evaluates every time something in the IF condition changes. So, in your example here: If ( Status 'Dining' is not Off Or Status 'Dining.Table' is not Off Or Status 'Dining.Wall' is not Off Or Status 'Down.Land.Slave' is not Off Or Status 'Down.Land.Wall' is not Off Or Status 'Entry' is not Off Or Status 'Entry.Wall' is not Off Or Status 'Entry.Down.Land' is not Off Or Status 'Entry.Up.Land' is not Off Or Status 'Livingroom' is not 20% Or Status 'Livingroom.Wall' is not Off Or Status 'Livingroom.Mantle' is not Off Or Status 'Up.Land.Heart' is not Off Or Status 'Up.Land.Slave' is not Off ) Then Set Scene '-Living.Movie.C.State' Off Else Set Scene '-Living.Movie.C.State' On Let's say that your program becomes TRUE because, say, the 'Dining' room light gets turned on. Your program then sends an OFF command to the '-Living.Movie.C.State' button. Then, let's say the 'Dining.Table' light gets turned on as well. The ISY sees this, the program is re-evaluated, and the OFF command is once again sent to the '-Living.Movie.C.State' button. By checking the status of the KPL button in the IF statement, you can reduce that redundant traffic.

Definitely like Rand said, create a scene and add the lights you want to control to that scene. Then, in your IR programs, control the single scene (and not the individual devices). Good luck!

Hey Greg - My programs will only do it once either way (on to off or off to on). 1 - With powerline protocols, and specifically Insteon, there are potential problems any time there is simultaneous powerline traffic. Like, for example, pressing 2 switches at precisely the same time. 2 - The delay is more to separate the traffic rather than decrease it. But, it does save traffic if, for instance, my entire 1st floor is off but I turn a single light on for only 2 seconds - the ISY won't bother turning on the 1st floor status LED (because of the WAIT command).