Toddimus

Both, I think. I honestly didn't look that hard at it. I was getting our toddler to bed and got distracted. Nothing stood out to me though. Definitely weren't a bunch of individual device or scenes turned full on in the log. Sorry I'm not more help. Il try to document it better next time. Sent from my iPhone using Tapatalk

I didn't have any All On events for about 14 months ... from the time I did my initial install in our new house until about a month ago. I just had another one last night. Both times, I was opening a door that has a hidden door sensor in it. There also happens to be a wireless motion sensor on the far side of the door that I was opening. Not sure if the motion sensor would have had enough time to "see" me before the All On actually happened. I think the first time, the hidden door sensor had a low battery. Maybe it tried to send out its low battery signal on top of the regular door open signal it was trying to send? The first time, I wasn't able to get to the log to check. Last night, I looked in the ISY log and didn't see anything that looked suspicious.

This is extremely cool! I recently put some extra blank switch locations around the house in preparation for something like this. I had been thinking of using old iPhones or maybe some sort of small tablet, but a RPi with touch screen would be awesome! In fact, I just received two more RPi 2 boards today that I ordered from Makershed. They are having a big sale. They were already half off ($20) and then there was a 20% off coupon code which made them $16 each! Yes, that's for the latest RPi2. Looks like they are out of stock now though.

Well, that answers that question. You even did the math for me Stu, thanks. So I won't worry about it then. Any thoughts on the new feature for automatically populating the permutations of the adjust scene function I suggested for the interface? I did go through and do it manually with all the permutations and it wasn't that bad but it would be nice to be able to automate some of that process if possible.

Follow up question... I assume these adjust scene actions actually write updates to the internal non-volatile (is it EEPROM?) of the devices. Is there any issue with degradation if I write to these say... 5 times per day? I commented about this in one of the Ideascale items where the originator (Jim Searle) wanted to be able to programmatically enable/disable devices from being responders to scenes. By the way, this is a great idea, if it can be done... http://udi.ideascale.com/a/dtd/Allow-disabling-a-device-in-a-program/83037-32911 This would also theoretically require writes to the devices' non-volatile memory. Any thoughts on the longevity of the non-volatile memory's write endurance? 10 years x 365 days x 5 writes per day is almost 20,000 write actions. Thanks, Todd

Makes sense. And I thought that might be the case. It's just a lot of programming. I have 24 (8 scenes x 3 lighting scenarios for each scene) programs so far to address the level changes. And I haven't finished installing all of my devices, or creating scenes. Each of those programs would then need at least 4 adjust scene lines (for single device scenes) and 12 lines (for my dual controller scenes). I know... just buck up and deal with it. That's part of the fun in this home automation stuff. Version 5.X will hopefully make this easier, in that I can use variables instead of hard coded values in the adjust scene drop down lists. Seems like there's an opportunity for a new feature (even without variables driving the levels)... The new GUI feature would allow the user to apply the changes to all of the devices in a scene (and the scene itself) in the adjust scene part of the programming tab. Kind of like the "Copy Scene Attributes from <Scene Name>" button on the scene configuration page. I realize it wouldn't necessarily address my desire to have different ON or RAMP levels for the scene vs. locally applied button presses. But I can envision how that could be implemented too. Thanks for the reply oberkc!

Programming question here. I have searched and read about adjust scene programming, but found nothing regarding a 3 (or more) way switch setup to do what I want. Here's a simplified set of my components involved in the scenario... Devices: Dimmer switch "Hallway - A" (controls actual load with red wire, is also set as a controller for the 3-way scene) Dimmer switch "Hallway - B" (red load line is not connected, it is used only for the 3-way scene as a controller for the scene) Scene: "Hallway - 3 Way" Both "Hallway - A" and "Hallway - B" are controllers for this scene. I would like to set the locally applied (i.e. button pressed on the wall switch) value to a different (higher) value than is assigned to the scene itself. I would also like to be able to programmatically change these levels (and ramp rates) independently, depending upon the time of day. In order to do this, I will set up programs that will trigger an "adjust scene" action. My question relates to the options available in the adjust scene drop-down boxes. In the THEN clause of my program, I have the following options to adjust the scene: In Scene: Hallway - 3 Way (Scene icon), Set: Hallway - A (Device icon) : XXX% (On Level) In Scene: Hallway - 3 Way (Scene icon), Set: Hallway - A (Device icon) : X.X Sec (Ramp Rate) In Scene: Hallway - 3 Way (Scene icon), Set: Hallway - B (Device icon) : XXX% (On Level) In Scene: Hallway - 3 Way (Scene icon), Set: Hallway - B (Device icon) : X.X Sec (Ramp Rate) But I also have the options of: In Scene: Hallway - A (Device icon), Set: Hallway - A (Device icon): XXX% (On Level) In Scene: Hallway - A (Device icon), Set: Hallway - A (Device icon): X.X Sec (Ramp Rate) In Scene: Hallway - B (Device icon), Set: Hallway - B (Device icon): XXX% (On Level) In Scene: Hallway - B (Device icon), Set: Hallway - B (Device icon): X.X Sec (Ramp Rate) In Scene: Hallway - A (Device icon), Set: Hallway - B (Device icon): XXX% (On Level) In Scene: Hallway - A (Device icon), Set: Hallway - B (Device icon): X.X Sec (Ramp Rate) In Scene: Hallway - B (Device icon), Set: Hallway - A (Device icon): XXX% (On Level) In Scene: Hallway - B (Device icon), Set: Hallway - A (Device icon): X.X Sec (Ramp Rate) So I think I understand that if I want to change the scene "Hallway - 3 Way" parameters when the actual scene is triggered, I need to adjust the first set of four values (with "Hallway - 3 Way" selected in the first drop down box after "In Scene". This will not have an effect on the values applied locally (i.e. when I press the actual light switches on the wall). If I want to adjust the locally applied levels (and ramp rates), do I need to set all eight of the second set of values? So for instance at night, I want the scene to trigger on levels of 30% and a ramp rate of 2.0 sec. When the actual wall buttons are pressed, I want the level to go to 60% with a ramp rate of 0.5 sec. I also want the other wall switch to adjust its locally displayed LED level to match. Furthermore, if a locally applied "Fast On" is double clicked on one of the switches, I want the load to come on to 100%. Effectively, this gives me three levels of "ON" at any given time. The scene would be programmatically triggered by motion detectors for the 30% level. If I press a wall switch, the lights come on to 60%. And if I double click the wall switch, the lights come on to 100%. All of this with theoretically different ramp rates for each scenario. I presume I would need to do at least this: In Scene: Hallway - 3 Way, Set: Hallway - A : 30% (On Level) In Scene: Hallway - 3 Way, Set: Hallway - A : 2.0 Sec (Ramp Rate) In Scene: Hallway - 3 Way, Set: Hallway - B : 30% (On Level) In Scene: Hallway - 3 Way, Set: Hallway - B : 2.0 Sec (Ramp Rate) In Scene: Hallway - A, Set: Hallway - A : 60% (On Level) In Scene: Hallway - A, Set: Hallway - A : 0.5 Sec (Ramp Rate) In Scene: Hallway - B, Set: Hallway - B : 60% (On Level) In Scene: Hallway - B, Set: Hallway - B : 0.5 Sec (Ramp Rate) Do I need to do these too? In Scene: Hallway - A, Set: Hallway - B : 60% (On Level) In Scene: Hallway - A, Set: Hallway - B : 0.5 Sec (Ramp Rate) In Scene: Hallway - B, Set: Hallway - A : 60% (On Level) In Scene: Hallway - B, Set: Hallway - A : 0.5 Sec (Ramp Rate) This same question would apply to any "N-Way" switches and presumably gets more convoluted with more controller switches in the scene. I hope this makes sense. Thanks in advance for any help with this question. Cheers, Todd p.s. As an aside... the fact that they call it a 3-Way switch is somewhat misleading to me. There are only two switches and two possible paths for the hot lead (in a conventional switch setup). There are 4 possible permutations of the switch positions: UP-UP, UP-DOWN, DOWN-UP and DOWN-DOWN. Is it because there are usually 3 wires involved? White, red and black? That's the only plausible explanation to me. I do realize that Insteon switches aren't wired this way.

Mike, Awesome! Thanks for the info. I had always thought it was Linux based. I guess my Raspberry Pi would be vulnerable though. I'm not currently using it, but had planned to integrate it into the system. Cheers, Todd

Not to be alarmist... but I just read this article on CNN and it sounds like the Linux based OS of the ISY could be vulnerable to the newest hit amongst the hackers out there: The "Bash Bug"... http://money.cnn.com/2014/09/24/technology/security/bash-bug/index.html?hpt=hp_t2 Just wanted to raise the flag to the powers that be. -Todd

I had this same thing happen to me this weekend. All of the events from my motion sensors stopped being received by the ISY 994 (and 2413S PLM). I noticed that my timers that are triggered by the motion sensors weren't running (so the lights stayed on). I power cycled the ISY and PLM but this didn't fix it. I eventually did a PLM restore which fixed everything, but I will agree that this is weird. Made me wonder if my PLM is going bad. It's an older version (V1.4 I think). Strange stuff started happening when I added a new dimmer switch. Most of my Insteon stuff is the older i1 protocol, and the new dimmer is presumably the newest i2cs protocol. I'm having issues with that too, but haven't had time to track down exactly what's going on. I'll start a new thread on my dimmer scene issue.

Good call Lee. I recently pulled a chunk of paint/texture off of the wall when I removed the double sided tape that comes with the motion sensors. At least I think it came with the sensor. I have some of that stuff lying around so I may have used what I had if it didn't come with the sensor. It's some of the really sticky stuff!

Thanks Michel, I had the extra adjust scene part in there as a "belt and suspenders" kind of entry. I had wondered whether I really needed it or not. It wasn't clear which one I needed so I used both. I'll take it out and I'm sure it will help a bit. Hopefully all of this will help somebody else. I think we have gone over all of the pitfalls in my method and their consequences. It is noticeably faster to use a scene to react to motion and that's just what some folks may want. Thanks to all who have contributed!

For what it's worth, I've also experimented with rotating the sensor by 90 degrees when I'm trying to sense motion down a hallway. Since the sensor is normally meant to detect motion that passes side to side in front of the sensor, if you rotate it 90 degrees and tilt it down a bit, it can help sense motion towards/away from it. The idea is that your body parts appear to move across the sensor during your ingress/egress because the apparent angle to the sensor changes. Don't know if my explanation makes sense but it's worth a try. Have a look at the 2420M manual to see the sensing area in front of the sensor to see if rotating might work for you. I've also found that some white electrical tape works well to block out parts of the sensing area to prevent our small dogs from triggering an ON event. This is similar to flipping the sensor upside down, but may be useful in other orientations. Ultimately, I ended up removing the tape, but it did work to mask areas of the sensor if that's what you want to do. Sounds like you want as much sensitivity as possible so its not for your application, but I thought I'd mention it since others might want to try. Cheers, Todd

Michel, 3. Both, but I understand that they both take time. My previous estimates of 1-2 seconds may be longer than it actually takes but the point is that they're slower than I'd like them to be. It's the scene adjust delay that causes most of my "bugs". The bug occurs when I have manually pressed the hallway dimmer switch. Since it is a locally applied command, the hallway dimmer immediately goes to the preset FAST OFF, OFF, ON, or FAST ON level, which is what I want it to do. The appropriate program for state -1, 0, 4, or 5 is then activated which sends the scene adjust value to the scene and dimmer. If the hall motion sensor sends an "ON" command before the adjust scene commands are finished doing their business, I get into an unknown condition. The light sometimes turns off or to the previously set on level which is not what I want it to do. I know it's too slow (from previous experiments) when I use programs (not links to the motion sensor) to activate the hallway switch. That's where I started in this whole journey in the first place. It's become esoteric now, but since I've gone this far, why not go the full monty. My whole hallway motion scheme is described below in the most explicit way I can think of. I'll sign off here and let the code do the talking from here... Cheers, Todd I created a scene that I call "Hall After Motion". "Dimmer - Hallway" is the responder "Motion - Hall - Sensor" is the controller. When I highlight the "Hall After Motion" scene entry in the MAIN device/scene tree, I see "Dimmer - Hallway" show up in the main panel on the right. -- This is the scene that I'm adjusting in my programs below. When I highlight the "Motion - Hall - Sensor" device under the "Hall After Motion" scene in the tree, I also see "Dimmer - Hallway" show up in the panel in the right. -- This is the second adjust scene value I'm adjusting in the programs below. I then created a state variable called "s_Hall" to keep track of the current state the hallway lighting system. The rest of the post contains all of the programs that run this whole scheme. They aren't perfected, but they do work pretty well, most of the time. I'm trying to minimize the bugs... THESE ARE THE SCHEDULE BASED PROGRAMS WHICH ARE MY "AUTO MODE" VARIABLE VALUES OF 0, 1, 2: Hall_Auto_Sched_1 If From Sunset + 2 hours and 30 minutes To Sunrise + 2 hours (next day) Then In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 30% (On Level) In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 30% (On Level) Set 'Dimmer - Hallway' Off $s_HALL = 1 Else - No Actions - (To add one, press 'Action') Hall_Auto_Sched_2_0 If From Sunset - 45 minutes To Sunrise + 2 hours (next day) Then In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 50% (On Level) In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 50% (On Level) Set 'Dimmer - Hallway' Off $s_HALL = 2 Else In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 0% (On Level) In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 0% (On Level) Set 'Dimmer - Hallway' Off $s_HALL = 0 THIS IS THE TRIGGER THAT STARTS TIMERS WHEN IN "AUTO MODE": Hall_Motion_TRIGGER If Control 'Motion - Hall - Sensor' is switched On And ( $s_HALL is 1 Or $s_HALL is 2 Or $s_HALL is 3 ) And $s_HALL is not 0 And $s_HALL is not 4 And $s_HALL is not 5 And $s_HALL is not -1 Then Wait 2 seconds Run Program 'Timer for Hallway_Short' (Then Path) Else - No Actions - (To add one, press 'Action') THESE TRIGGER THE STATES THAT SUPPRESS OR DISABLE THE SCENE LINK BEHAVIOR BY MATCHING SCENE ON LEVEL TO THE DESIRED LEVEL: Hall_SW_FAST_OFF_neg1 If Control 'Dimmer - Hallway' is switched Fast Off Then In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 0% (On Level) In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 0% (On Level) $s_HALL = -1 Run Program 'Timer for Hallway_Long' (Else Path) Run Program 'Timer for Hallway_Short' (Else Path) Else - No Actions - (To add one, press 'Action') Hall_SW_FAST_ON_5 If Control 'Dimmer - Hallway' is switched Fast On Then In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 100% (On Level) In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 100% (On Level) $s_HALL = 5 Run Program 'Timer for Hallway_Long' (Else Path) Run Program 'Timer for Hallway_Short' (Else Path) Else - No Actions - (To add one, press 'Action') Hall_SW_OFF_0 If Control 'Dimmer - Hallway' is switched Off Then In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 0% (On Level) In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 0% (On Level) $s_HALL = 0 Run Program 'Timer for Hallway_Long' (Else Path) Run Program 'Timer for Hallway_Short' (Else Path) Wait 30 seconds Run Program 'Hall_Auto_Sched_2_0' (If) Run Program 'Hall_Auto_Sched_1' (If) Else - No Actions - (To add one, press 'Action') Hall_SW_ON_4 If Control 'Dimmer - Hallway' is switched On Then In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 50% (On Level) In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 50% (On Level) $s_HALL = 4 Run Program 'Timer for Hallway_Long' (Then Path) Run Program 'Timer for Hallway_Short' (Else Path) Else - No Actions - (To add one, press 'Action') AND FINALLY, THE TIMERS THAT TURN OFF THE LIGHTS AFTER A TIME: Timer for Hallway_Long If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'Timer for Hallway_Short' (Else Path) Wait 2 minutes Set Scene 'Motion Responses / Hall Fade' Off Run Program 'Timer for Hallway_Long' (Else Path) Run Program 'Hall_Auto_Sched_2_0' (If) Run Program 'Hall_Auto_Sched_1' (If) Else - No Actions - (To add one, press 'Action') Timer for Hallway_Short If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'Timer for Hallway_Long' (Else Path) Wait 20 seconds Set Scene 'Motion Responses / Hall Fade' Off Run Program 'Timer for Hallway_Short' (Else Path) Else - No Actions - (To add one, press 'Action') If you were really paying attention, you might wonder where the state for 3 comes from. I'm holding that for another TBD auto mode that might be used for security or a later time at night, etc. There shouldn't be a way for the s_Hall variable to get to 3 yet, but even if it did, it would be reset at the next scheduled auto mode update. If you made it this far, thanks for hearing me out!

Lee, As I mentioned in the above posts, I have tried using programs triggered by the Motion ON to turn on the responder. It works fast enough for all of my other applications, but not for the hallway. I can see why it works for your bathroom, like it does in my other rooms, because when you are going into the bathroom, you typically come in and stop. For my short hallway, you are already through it before the lights turn on when I use a program to turn on the dimmer.

Thanks Lee. That's exactly why I'd like to be able to remove/add the device from the scene programmatically. If I could take it out of the scene, I wouldn't have the problems during the day when I'm trying to suppress the motion response scene by adjusting the on level of the scene.

Michel, I am actually just running one dimmer right now in the scenario. I'd like to add a second, but that's for later. The MS (controller) and the dimmer (responder) are in a scene, so they are linked and respond very quickly. I do not use a program to turn the scene on, the MS activates the scene when motion is sensed. The slow part is when I try to adjust the dimmer on level in the scene when the dimmer button is pressed locally. This is how I suppress the linked scene response. Sometimes it takes too long to adjust the scene's on level using programs and in the interim, the motion sensor sends another ON command which changes the dimmer's light level to the "old" value. I'm using 3.1.16 firmware I have about 20 devices and 50 programs. Thanks

The delay is 1-2 seconds when I just use programs to set the lights on (i.e. without links between the MS and dimmers). The hallway is 10 feet long so you can get most of the way down it before the light turns on when programs are used to turn the dimmer on (again, without links between the MS and dimmer). If I use links between the MS (controller) and the dimmer (responder), there's hardly any delay at all when the MS registers motion. The delay I'm dealing with now is that when I locally turn on the dimmer, it takes a finite amount of time (again 1-2 seconds) for my program to set the new ON level which effectively suppresses the MS ON command for the scene. If an MS ON signal is sent before the new settings take hold, the dimmer abruptly goes to the "old" ON level. Make sense? I want to use the control ON from the motion sensor to turn on two dimmer switches only under certain conditions. Right now, I just have one dimmer (sconce light) as a responder to the scene. I'd like to add a second dimmer when I get things ironed out. That of course would add more states to scenario if the second dimmer switch is turned on locally. I'll get the single dimmer working as best as possible before I go into the second dimmer as a responder. Does that answer your questions? Thanks again, Todd

Thanks Michel, I was afraid you were going to say that. I had to try anyways. Like I said, I almost have things working the way I want and I think I can deal with the self-induced "bug" I created for operation during the day. For nearly all of my other programs, I can deal with the processing delay of the ISY, it's just the hallway that makes it frustrating because I want immediate scene response. Thanks to you and UDI for making this cool tool to use for my home automation! Cheers, Todd

Tim, You are right, I have the MS set to send only ON commands. Because of this, and the way I have worked around the problem of the link persisting, when I am in state 0 or -1, I have the scene set to 0% on level when the scene is turned ON by the MS. This effectively turns the lights OFF when an ON message is sent by the MS because ON = 0% in the scene. So say you are trying to read a label on a bottle in the hallway during the day and you want a bit more light, you turn the lights on manually. If you move, the lights turn back off because the MS activated the 0% ON scene. Like I said, this almost works but the problem lies in the fact that my programs which try to override the 0% ON level by setting the MS scene responders to 70%/100% upon a button press are sometimes too slow to change the scene attributes before a motion is sensed and I end up with the lights going out right after I just turned them on manually at the dimmer switch. I know it's convoluted, but that's how we have to work around Insteon's limitations. I realize it isn't really a limitation of the ISY, but adding the option to programmatically remove/add a device from/to a scene would overcome my problem.

Tim, That's what I'm doing as well. Problem is that you might want the lights to turn on during the day when you press the local dimmer on button. That's works great until you move, then the scene sets the light to off because they are set to go to 0% on when motion is sensed. I've tried to get around this with my state variable of 4 and 5 from the post above, but it doesn't work quite right. In state 4, (triggered by locally pressing the dimmer button to ON) I send an update to the motion response scene such that the on level of the scene matches the locally applied on level of the dimmer (70%). State 5 does the same except that it sets the motion response on level to 100% when the local dimmer button is turned FAST ON. By making the motion response level match the locally applied level, I have in effect, suppressed the motion response. I'm so close to getting it to work the way I want, but my method of suppressing the response to the trigger isn't quite there. The thought is that if I'm in either state 4 or 5, I have the motion response scene match exactly what the local light switch would do anyways. Problem is that it's a bit buggy in the way it works. Being able to remove the dimmers from the scene as responders during the day would likely fix most of my problem.

Lee, Thanks, I realize that. That's why I'd like this to be added as a new feature. I know the ISY can do it when creating/modifying scenes, so why not add it to the programs?

Tim, I realize my post was a bit rambling on and on. To put it short and sweet... Yes the MS is linked to the responders and I am using the "Adjust Scene" action to modify the on level based on schedules. What I'd really like to be able to do is to "Unlink" the responders during the day so they don't turn the lights on automagically. I'd also like to be able to override the motion response link at any time if the local dimmer buttons are pressed. My first post was intended to show my train of thought and how I got where I am, which is almost there. Cheers, Todd

Hi folks, I've never posted here but have been reading many of the great threads over the last year of so since I "geeked out" on home automation. I have a question and a potential feature request if what I want to do can't already be done. Here goes... My requirements: Wireless PIR sensor (2420M) should trigger one or two dimmers to turn on under some conditions (conditions are described below). When in "auto mode", the light(s) turn on upon motion sense and turn off after 30 seconds (off timer program). When "auto mode" is suppressed under certain conditions, the motion scene should not affect the local dimmer(s). Schedule based "auto mode" conditions: Morning, set dimmers to 40% upon motion Daytime, don't turn on lights at all upon motion (ideally, remove from the scene which is part of my FEATURE REQUEST) Evening/Early Night, set dimmers to 40% upon motion Late Night, set dimmers to 20% upon motion Manual override conditions: If dimmer switch is turned "ON", individual light turns on to preset level (i.e. locally applied level) and stay on for 2 minutes, suppressing auto mode while timer is active If dimmer switch is turned "FAST ON", individual light turns on to 100% and disables auto mode off timers If dimmer switch is turned "OFF", individual light turns off and suppresses auto motion response for 2 minutes If dimmer switch is turned "FAST OFF", individual light turns off and disables auto motion response until auto mode is reset the next day (by another reset program) I know that this can be done using programs to trigger dimmers to turn on given other programmable conditions, and I have been able to do this with functioning groups of trigger/schedule/action programs. My problem is that I want the lights to respond ASAP upon the motion trigger event. If I use programs to determine what happens when a motion "ON" event is registered (subject to the conditions), I have to wait at least a second for the response to happen because the ISY is actually receiving/processing/sending the Insteon commands. For most of my demands, this is just fine... I can wait the second or so for the lights to turn on. In my hallway, which is very short in length, I can't bear the second's wait for the lights to turn on... I'm already out of the hallway before the lights turn on. You might then say that I should link the motion sensor to the dimmer(s) so that they turn on immediately when the motion sensor sends the "ON" command. In effect, this would take the ISY out of the action loop and speed things up dramatically. My problem with this is that I don't always want the lights to turn on when motion is sensed. So you might also say that I should set the dusk/dawn threshold to an appropriate level. I have had mixed success with this so I have opted to not use the dusk/dawn (night only) mode of the motion sensor. I'd also like to know about motion during the day for occupancy programs so I always want to get "ON" commands from all of my sensors, so night only mode doesn't work here either. So I've come up with a hybrid solution that mostly works... I set it up such that a scene controls the dimmers (responders) when the motion sensor (controller) sends an "ON" signal. The motion controller is set to send only "ON" commands, always, day or night. I use a variable ($sHALLWAY_STATE) to determine which mode I am in: -1 = Auto mode disabled, dimmers off 0 = Auto mode suppressed for 2 minutes, dimmers off 1 = Schedule based auto mode, Morning/Evening/Early Night => dimmers to 40% upon motion 2 = Schedule based auto mode, Late Night => dimmers to 20% upon motion 3= TBD auto mode --- Reserved for future use (like away-from-home security) 4 = Manual override when local dimmer button is pressed "ON" => turn on to locally applied level (70%) and suppress motion response until 2 minute timer expires (or lights are locally turned off) 5 = Manual override when local dimmer button is pressed "FAST ON" => turn on to 100% and disable motion sense response until reset or turned off locally I have basically achieved what I want by using the action: "In scene - 'Hall after motion response' set 'Dimmer - Hallway' XX% (on level)" in a few programs that are executed depending upon the change of the state variable "$sHALLWAY_STATE". I change the XX% depending upon the schedule and/or manual override mode as described in the numbered list above. Like I said, this basically fulfills my requirements because it's fast and the lights turn on to whatever level I want. The problem I have is that my suppression of the motion sensor activation of the scene doesn't always work correctly because I am constantly adjusting the on level of the scene to achieve most of my requirements. Two example problems: Say I'm set to the LATE NIGHT auto mode (=2) and therefore the 'Hall after motion response' on level is set to 20%. I walk into the hall and the lights turn on to 20% as the motion is sensed. I then turn "ON" the local dimmer switch because I want more light. If I stuck with this, the lights turn on to the locally applied level (70%) but immediately turn down to 20% if I move a muscle because the motion scene takes over. I have dealt with this by creating state (=4), which again uses the "In scene - 'Hall after motion response' set 'Dimmer - Hallway' 70% (on level)", where 70% is equal to the locally applied on level. Ok, works pretty well, but if I turn the lights locally "ON" (not "FAST ON") again it goes to 100% for some reason. I can live with this but it is undesireable. Now say it's daytime, and I want the lights to only turn on when the local dimmer is turned on, but I still want to get motion "ON" events from the sensor. That puts me in the state (=0), where auto mode is suppressed and I will go to mode 4 or 5 if the local dimmer is turned "ON" or "FAST ON" respectively. This is my biggest problem... given my programming/scene setup, I then set the motion response "In scene - 'Hall after motion response' set 'Dimmer - Hallway' 0% (on level)" to prevent the motion sensor from turning on the lights upon motion during the day. In most circumstances this is fine, but what happens when you actually want to turn the lights on? The dimmer is inextricably tied to the motion sensor because of the 'Hall after motion response' scene, so the lights actually turn off when motion is sensed. See the problem? I want to be able to programatically remove the dimmers from the scene under certain circumstances. I haven't been able to find a solution for this. This leads me to my feature request... Give us a way to programatically add/remove devices from a scene. I realize that this would cause a bunch of Insteon traffic, so it probably shouldn't be used all the time, but it would be very, very useful. It is further complicated by the fact that the motion sensors are battery powered and wireless so they can't easily be "spoken to" and therefore we can't easily make/break links. This leads me to the next feature request... Modify how the "Include battery powered devices when automatically writing changes to your devices" works. I know that the battery powered devices need to be put into linking mode before this feature is really useful, or you could try to trigger a motion so that the device wakes up and "listens" for commands, which is kinda tricky. The modified behavior would be that the ISY would wait until it gets a signal from a motion sensor and THEN start sending the new link updating information, after the battery powered device has awakened. This would basically be equivalent to what we try to do manually by triggering a motion event and quickly pressing the "OK" button on the "Write updates to device". It doesn't always work when I try to do it manually. It would be cool if the ISY could wait until it "knows" that the battery powered device is "awake" and then start sending the commands. If you're still here reading this, thanks for listening. It took me a while to get this all to work and it's been fun getting here. I'd just love to get it perfect and that's why I'm asking for help and/or new features. Cheers, Todd