David_Gilbert

I did try to remove the remote from the scene and it still wouldn't work; of course I can try it again. The setup that worked in the bathroom has the switch as a controller, it then updates per the schedule to either 20% or 100%. The setup that isn't working has the switch as a controller (skip the remote for now) and the lamplincs as responders; the schedule isn't updating the lamplincs as I'd expect.

All, I have my master bathroom light programed to be at 100% unless it's from midnight till sunrise the same day, then it's at 20%. It was a pretty simple program, but now I'd like to do the same thing for my night stands; however, this is where I am finding it complicated. I have a SwitchLinc on the wall coming into the bedroom, and then a Mini Remote on one of the night stands... and each night stand has a lamp controlled by a LampLinc. The Switch and the Remote are 'controllers' and I have the lamplinc's set to responders. I'd like the same program... from midnight to sunrise, the lamplinc's come on at 20%, otherwise they're at 100%. I've tried a few variations of the program and even removed one of the controllers to help isolate the issue. However, I am not able to figure it out; so I thought I'd seek some help if it's even possible with my setup. Really like to know if this is achievable and some pointers if so. Thanks!

Final Update: I replaced the FanLinc today and everything is working... looks like "high" was defective after all. Thanks!

Replacement FanLinc ordered. Thanks everyone!

Maybe it's the FanLinc then, I can replace it... but this is what's happening regardless if I manually set it or not. Correct. If I manually set the FanLinc to high it cuts off too.

I did. Maybe it's the fan. Off, Low & Med work fine... it'll work. I'll just come up with something else for D.

I switched from 1 button to a basic 4 button A,B,C,D configuration... the On/Off is the light. A=off, B=low, C=med, D=high

The programs I have now are just this... D HIGH - [iD 000C][Parent 000F] If Control 'MBR Master Switch - D' is switched On <--- switch is 'on' Then Set Scene 'Interior / MBR Celing Fan / Fan HIGH' On <--- enable this scene Else - No Actions - (To add one, press 'Action') I will review the programs again, but I'm pretty sure I removed every other/previous instance calling FanLinc - Motor

Yes, I confused you. Sorry. I first wanted one button to do it; and Stu helped... I was able to program it so that button B would toggle through the settings, but High wasn't working. I figured I may have screwed something up, so I deleted everything related to the fan motor and started over setting each button A, B, C & D to a setting... Off, Low, Med, High. At this point, every button works; however, like before... all but High. That takes us to now. I had mentioned it and Stu tried to help me do some troubleshooting. The chain pull is, off, high, med, low - so I verified that it was indeed set to high. @Oberkc Springfield Oh huh? I'm originally from Greenville, Oh... but now I live in VA.

The fan turns off. :-/

you have this then?

Update: The same thing happens, Low is low, Med is med and High is Off... off is also off. The Motor says it's High, but the fan is off. I verified the pull switch on the fan is one past off = high. Maybe the fan just can't get High - we usually run it on low/med anyway, so I'll ignore High and maybe set button D for something else... like turn on/off the bathroom light too.

I just removed everything related to my fan motor... the fan light is on the master switch (toggle on/off), it works. Switch buttons a,b,c,d are non-toggle on, four scenes were created with either a,b,c,d as the controller and the others (along with the motor) as responders. I manually adjusted each scene to the settings, e.g. Button A, on 100%, B/C/D on 0%, Motor Off // Button B, on 100%, A/C/D on 0%, Motor Low... I created basic programs for these scenes like.. A OFF - [iD 0012][Parent 000F] If Control 'MBR Master Switch - A' is switched On Then Set Scene 'Interior / MBR Celing Fan / Fan OFF' On Else - No Actions - (To add one, press 'Action') B LOW - [iD 000E][Parent 000F] If Control 'MBR Master Switch - B' is switched On Then Set Scene 'Interior / MBR Celing Fan / Fan LOW' On Else - No Actions - (To add one, press 'Action') I would think by turning on a scene, those settings would take affect; therefore, references other scenes as off shouldn't have any affect. I've had a few miss configurations - like suddenly it just keep cycling through off, low, med, high, off, low... that was exciting :-/

Thanks again Stu. The settings worked except for High; so I am testing it with a single button press i.e.; A = off, B= high, C= med... etc. Again, everything works, but high... it switches to high per the settings, but the fan itself cuts off. I've gotta search the forum for that one. I wanted you; and whomever reads this thread next time, to know that your settings for a multi-press worked though. -David

Awesome Stu! Thanks, I cannot wait to try it out. David

Maybe I can hijack this thread I have a 2487S KeypadLinc (6 button keypad), On/Off toggle controls two lights in the room, button A toggle turns the celing fan light on/off, button B is non-toggle; where I am trying to setup with 4 button press (low, med, high,off) for the celing fan speed. I have gone through the forum and found various examples of setting a separate button for these commands, but only a couple old threads on setting variables etc for multi-press (non-toggle). What I have done was create a State Variable "ID1, MBR_fanSpeed,0" And then I created 4 programs like... 0=off, 1=low, 2=med, 3=high 0 OFF - [iD 0012][Parent 000F] If $MBR_fanSpeed is 0 Then Set 'MBR Celing Fan-Motor' Off In Scene 'MBR Celing Fan Blades' Set 'MBR Celing Fan-Motor' Off Else - No Actions - (To add one, press 'Action') When I run the Then statements in the above program samples, they all work. The hang up is creating a program attached to the button B to call these sub-program variables. Am I all jacked up or close?

What's interesting is that it only runs once; the door opens, if it is during the "If" time frame... after a set time frame it tries to close. If it fails for any reason; obstruction on sensor break the garage door re-opens as expended and the program ends. I'll call this a success.

This is the simplified version that I tested an it works as expected... none of the security features of the door have been modified, if something is breaking the security beam the door wont close... if the door hit something on the way down it'll retract. Under each use case, it will try to shut the door 5 minutes later. Next I will try a 'repeat' statement to see if I can have it fail to close, repeat one attempt and fail the program. Garage Bay2 - [iD 000B][Parent 0007][Not Enabled] If Status 'Garage Doors / Garage Bay2-Sensor' is Off Then Send Notification to 'Default' content 'GarageBay2' Wait 5 minutes Set 'Garage Doors / Garage Bay2-Relay' On Send Notification to 'Default' content 'GarageBayClosed' Else - No Actions - (To add one, press 'Action')

I had a feeling that the wait command is important since you can order which command you run at a time; like bash scripting. It turns out that I was correct, I modified the command as below; the wait 30 seconds pauses this program in place for 30 seconds before moving on. Garage Bay2 - [iD 000B][Parent 0007] If Status 'Garage Doors / Garage Bay2-Sensor' is Off Then Send Notification to 'Default' content 'GarageBay2' Wait 30 seconds Set 'Garage Doors / Garage Bay2-Relay' On Send Notification to 'Default' content 'GarageBayClosed' Else - No Actions - (To add one, press 'Action')

Great, I'll remove the wait statements and give it a test. Thanks.

Since it's a garage door, I added a wait to the Else in order to give the door time to close before it takes another action. The wait at the then gives me time to muck around if I manually opened the door during this time frame - like to take the trash out.

Garage Bay2 Security Check - [iD 000B][Parent 0001] If From 11:00:00PM To 6:00:00AM (next day) And Status 'Garage Doors / Garage Bay2-Sensor' is Off Then Send Notification to 'Default' content 'GarageBay2' Wait 5 minutes Else Set 'Garage Doors / Garage Bay2-Relay' On Wait 30 seconds Improved with the help of @mattavila.

I wrote this and it appears to do the job. However, I was wondering if it could be improved? 1: Check to see if the garage door was left open Garage Bay2 Security Check - [iD 000B][Parent 0001] If From 11:00:00PM To 6:00:00AM (next day) And Status 'Garage Doors / Garage Bay2-Sensor' is Off 2: If it was left open send me a notification and wait 5 minutes; this is in case I opened it manually during this time frame... like to take the trash out. After 5 minutes, close the garage door, give it 30 seconds to close and loop back to the If statement so it continues to monitor the door until 6am. Then Send Notification to 'Default' content 'GarageBay2' Wait 5 minutes Set 'Garage Doors / Garage Bay2-Relay' On Wait 30 seconds Run Program 'Garage Bay2 Security Check' (If) Else - No Actions - (To add one, press 'Action') ** I would like it to check it again after the initial 5 minutes wait and if it remains open, only then close it, if it is closed already, then continue monitoring for the next event. Maybe a variable is in order?

I had the same problem with my two new Craftsman; I posted a video on YouTube doing exactly this with Insteon's hub, now on ISY - both work just fine... https://youtu.be/NBCdo0kANuM It is an easy work around with these new multi-function wall remotes.