I have a shade project that was initially programmed by someone else. Keypad buttons are "Blackout" and "Sunshade". Programming attached to each button are Manual Sequences. Raise | Stop (R) | Lower | Stop (L).
Majority of the shades are in the up position during the day when we upload to the Lutron processor. Each time we upload we have to go around the house and tap each Shade button 3 times to get it back in sync with the button sequence.
I assume this is because the sequence gets "reset" when we upload.
The shade is at RAISE so sending Raise (first tap) does nothing.
The shade is stopped so STOP (second tap) does nothing.
Third tap finally sends a command that the shade can do which is LOWER. Now the shade is back in sync and keypad buttons work like they should.
If my assumption here is correct...Can i just reverse the order of the sequence to eliminate this issue? So Lower | Stop (L) | Raise | Stop (R) ? This would allow shades that are in the RAISEd position to be in sync after the upload.
Any reason why i can't do it this way? Trying to determine why the programming wasn't done this way in the first place.