Xathros

Larry- Change the Scene in the "In Scene" drop down to the Motion Sensor (Device) instead. As I said in my example - this is NOT intuitive at all. You need to select the controller (MS) as the scene rather than the Scene itself. What we are saying here is: when the scene is controlled by the MS, then the SLD should respond with xx OnLevel and XX ramp Rate. By selecting the Scene instead of the MS, you are only affecting the outcome when the ISY calls the scene, not the MS. See my second screenshot for an example. -Xathros

Now, back to our regularly scheduled topic... HOWTO: Disable a scene controlled by a motion sensor using Adjust Scene statement in ISY Purpose: To achieve an instant light response via motion trigger yet maintain programmatic control over timeout and ability to disable motion response. A Switchlinc Dimmer and an Insteon Motion Sensor both added as controllers of a scene called 'OfficeMotionLights' Motion sensor is configured: On Only, Sensing Mode, Night Mode Disabled. A program is in place to watch for motion sensed and then turn off the scene after a timeout (15 seconds for testing purposes). And, there is no load connected to the SLD so my office lights do not resemble a Disco while I'm working on this. If Control 'Office / Office Motion-Sensor' is switched On Then Wait 15 seconds Set Scene 'Office / Office MotionSLD' Off Else - No Actions - (To add one, press 'Action') When I trigger the motion sensor, the SLD turns on to 100%. 15 seconds after the last motion triggered, the SLD turns off. So far so good. Next to Enable/Disable the "Lights" on motion, I created another program: Program: OfficeMotionLightsEnable/Disable If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then In Scene 'Office / Office Motion-Sensor' Set 'Office / Office SLD' 0% (On Level) Else In Scene 'Office / Office Motion-Sensor' Set 'Office / Office SLD' 100% (On Level) Here is a screenshot for assistance on this one: Here is the critical and not very obvious part: I selected the Motion sensor as the Scene and set the SLD OnLevel to 0%. I don't want to adjust the Scene, but rather the controller of the scene here - the motion sensor. If I were to adjust the Scene instead, only the scene when controlled from the ISY is affected. This is where is is misleading in a big way. Motion Sensor is NOT a scene but rather a Device. It happens to be a Scene Controller. In fact, there is no scene called 'Office Motion Sensor'. By selecting the device 'Office Motion Sensor' in the "In Scene" drop down list, we are adjusting the responder link record in the SLD that matches the motion sensor's Insteon address. Now to test. I run Then on the Enable/Disable program then trigger motion. The event log shows the motion sensor activity but the SLD stays off. I manually turn on the SLD then move in front of the sensor again and the SLD turns off with the motion. Running else on the Enable/Disable program restores the previous behavior. Thats it in a nutshell. Let me know if you find this useful. -Xathros

I see a few others have chimed in on this already with basically the same answers I would have given. I use program (true/false) status as a control flag in some cases. Running the empty else section sets the program false when I need it to be. Mobilinc sees program status and I use that for feedback on certain items so some programs will set others false for feedback reasons. -Xathros

Yes. You could. Just another aspect to consider though. -Xathros

LeeG- Thanks. So then by utilizing an ISY scene to beep a device, rather than a direct command, I am reducing overall traffic by roughly 50% correct? -Xathros

I use the beep for three functions: 1) Single beep a scene with many devices whenever and exterior door opens. 2) 30 second countdown with a beep every second before an auto off timer expires in a few locations (single device scene) 3) Confirmation beep in places where I trigger a program with a FastOn, FastOff or Fade control. In general these all work just fine. Like others, i see variation in timing with a sequence of beeps. I attribute this to variations in comms quality / other traffic from motion sensors etc. I exclusively use scenes for the beep as I believe there is less traffic involved than when addressing a device directly. (Maybe LeeG can confirm or bust me bubble on that). I completely agree that a variable duration beep and blink capability should be built into certain devices (KPLs and Switchlincs and Toggleincs mostly). -Xathros

Hi smokegrub- I can say that I haven't. I also have 2 ISY's in different locations, power sources and internet connections. First, I don't believe the location or internet connection play into this at all. Power if noisy or unstable could certainly cause issues with Insteon devices. Can you describe in greater detail the failures and the need for a factory reset rather then a simple air gap restart of the devices? -Xathros

No problem. Happy to help. Just take it slow and careful and you shouldn't have much trouble getting everything swapped over. Don't delete the old one till you have the new one all programed. You can look at the old KPL nodes and see what they are controller and responders to as you go along. Fix up one scene at a time then recheck the old nodes to make sure you didn't miss anything. Careful use of search and replace in the programs should resolve everything there for you. -Xathros

There is a find/replace feature when editing programs. This will help a lot with the editing. As for the scenes, they will need to be documented then edited by hand. I suspect the new and old KPL's differ by type (dimmer vs relay) and thus, no replace with... option. -Xathros

Luckily, the ramp rate and On level are in the responder link records - not the controller link record. No changes necessary to the MS only the target responder. If I get some free time this evening, I'm going to build a test setup of this scenario to document and screenshot. I don't have the necessary parts at the office to test with. -Xathros

Then try this, adjust the settings on your computer's network connection to have the same netmask and then try to access the ISY and fix the netmask. Then set your computer's netmask back to 255.255.255.0 -Xathros

Larry- Responses in BLUE above. -Xathros

Do you know what you changed the netmask to? -Xathros Sent from my iPhone using Tapatalk

I suspect what Larry is getting at here is that using a scene with the MS as a controller is faster than triggering with a program. If that is the case then I 100% agree. I'm just unsure of what exactly he means by "Direct Link". -Xathros

Larry- If the scene was defined outside if the ISY this is quite true as the ISY has no idea of the link records. If however, you were to reset the devices and re-add them to the ISY and define your scene using the ISY, then you DO have the ability to do this. In general it is recommended that you don't do "Set Button Linking" outside of the ISY. What we are trying to do here is update a responder link record to set an on level of 0 at certain times. The MS still fires and activates the scene. Only the scene OnLevel is 0 so in effect the lights stay off. Downside - if the lights are turned on manually, motion will turn them off. Kind of a narrow use case but it fit the OP's need. -Xathros

Larry- As the OP did, you need to select the scene controller in the adjust scene statement (the motion sensor) and set the responder on levels to 0% -Xathros

How about when the switch is turned off, have a program issue an adjust scene statement that sets the on level for the scene to 0%. You will need a second program to modify the on level for when you want the light to come on with motion. -Xathros Sent from my iPhone using Tapatalk

Antonio- I am unable to duplicate that behavior here. I highly suspect program involvement. On the Programs Summary tab, sort by last run time. Query your KPL and then look to see if any programs were triggered as a result. Analyze any programs that react to the query to see if they may be turning off the KPL button(s) -Xathros

Anytime. Happy to help. -Xathros

Unless a program Then or Else ends with a Run Program .... statement, execution simply ends at the last statement. Event driven programming in the ISY is not necessarily a linear program flow like a BASIC program. Many things (threads) can run in parallel. Take for example: Program: TestProgram If Then Run Program1 (If Path) Run Program2 (If Path) Run Program3 (If Path) Run Program4 (If Path) Run TestProgram (Else Path) Else Run Program5 (If Path) Run Program6 (If Path Selecting Run Then on TestProgram will result in programs 1 through 6 all running simultaneously. -Xathros

bbconvert- What are you querying? The Primary node (ON/Off for a KPL6 or A for a KPL8) or one of the secondary nodes? I believe when querying a multi-node device, you should always query the primary node and the ISY will update the status for all of the device's nodes at once. -Xathros

John- You need a scene containing only the KPL button as a responder. Then just turn off the scene. Adjusting the backlight levels affects the backlight brightness globally for all of the KPL's buttons and does NOT change the state of the button. -Xathros

naPS- Assuming you are running the current firmware 4.2.18, then the place to report suspected bugs would be in the 4.2.18 Firmware thread at: http://forum.universal-devices.com/topic/14420-release-4218-is-now-official/ Otherwise, look for the announcement thread for the version you are running. If you are more than a few versions behind, I recommend you update to the current version and recheck to see if your problem still exists first. -Xathros

Yep. Didn't scroll far enough up for the name. Sorry. -Xathros

Anytime. Always happy to help. -Xathros