Cooper Aspire Master and Auxilliary switches


#1

1) Give a description of the problem
I have many Cooper (Eaton) Aspire 3-way switches with Aux switches . They should, but don’t sync.

2) What is the expected behavior?
I need them to sync with or without a button press or when I tell Alexa to change them. If I change the Main switch, I want the Aux to reflect the change. Vice-versa. Also, if I use Alexa to change them, I want the physical switches (both) to reflect the change. Currently, only the main switch does.

3) What is happening/not happening?
Currently, only the ‘main’ switch in each situation works. I can change the dimmers on them, but the ‘aux’ switches don’t refelct what’s done with the main. Also, when the Aux switches are pressed, they turn on the lights, but won’t reflect the level or state of the main switch, nor will they turn off the lights. Only on.


#2

You could group them in Alexa so one voice command turns them all on or off…

… but if you want the wall switches to also be in sync, I would try this instead:

If Switch A changes to on
  Then turn on Switch B
End If

If Switch B changes to on
  Then turn on Switch A
End If

If Switch A changes to off
  Then turn off Switch B
End If

If Switch B changes to off
  Then turn off Switch A
End If

#3

Just curious… Are you trying to sync the switches because sometimes you have to toggle three times to get the light to do what you want?


#4

I have Cooper Aspire RF9540 Z-Wave Dimmer Switches and RF9542-Z Accessory switches all over my house.

The problem is that while the RF9540’s all work well, the accessory switches don’t. They don’t follow the state of the RF9540, nor do they operate correctly. Most will turn ‘on’ a light, but none will properly dim lights or turn them off.

I’m wanting to set up statements so that the accessory switches ‘follow’ either button presses or voice control of the main switches, and also set the accessories to properly control the main switches if they are pressed or changed.

So it’s not just the state of on or off, but the dimmer level as well.

Does that make sense?


#5

This is what logically seems like should work, at least with displaying the state on the accessory, but it doesn’t work. The accessory switch doesn’t follow the main switch.


#6

I have not used that brand before. I scanned Amazon and found this tidbit of info:

If you’re adding this accessory switch to dim lights on a 3 way circuit you’ll need 1 master and the rest need to be the accessory switches… Regular toggle switches cannot be on the same circuit as these


#7

Hmmm… That piston you posted looks solid.

If that is not working, it might be a Device Handler issue. Did these work outside the box? Or did you have to install a DTH to get it working back in the day?


#8

I didn’t catch it earlier, but your level was overwriting your switch.
(since changing the level also turns on the bulbs)

I imported your previous piston, and made a few changes:

  • Added Log commands (so you can see the results)
  • Split up the Level & Switch into two sections. (this stops repeat commands from being sent)
  • Disabled Command Optimization (so the command is sent to the Accessory no matter what)
  • Added a short delay after the action (so the variables are set correctly)

Please pause your previous piston, and import and test this one:

Here are my log results from my test (100% success):

By the way, if this works well for you, the actual code in use is very tiny.
Most of the bulk above is just my extra log commands.


One thing to watch for with syncing a Dim Level is that most devices will send a level change no matter how small. So for example, turning the dial on most dimmers actually sends MANY commands to the hub. (ie: when going from 50 to 75, it might send up to 25 commands: 50, 51, 52 … 73, 74, 75) This would cause excess traffic on your network.

Ideally, when using the master to dim, make a jump to the desired level. (do not adjust slowly, if possible)


#9

So I’m new to webCoRE, and when I tried to import your piston, I got this:

Am I missing something?


#10

Try again with the Green button instead:

temp