Blue Smart Dimmer (2-1) 3-Way with Blue Canopy Module

Switches General Discussion
1

I have one Blue Fan Canopy module VZM36 controlled by two Blue Smart Dimmers (2-1) VZM31-SN. I don’t have a traveler wire available from one box to the other, so I can’t easily set this up with an aux switch which is why I’m using two smart dimmers in this 3-way setup.

I’ve bound both switches to the canopy module. Switch endpoint 2 to canopy endpoint 1 and Switch endpoint 3 to canopy endpoint 2.

I have the Configuration/Favorites button on each dimmer set to Cycle the fan.
Each switch by itself works perfectly, but the two switches do not keep their cycle states in sync.

If I press the favorites button on switch #1, the fan goes to low as it should. Then I press favorites on switch #1 again; the fan goes to medium as it should.
Now I press the favorites on switch #2. The fan turns off. Why? Because the last action the favorites button on switch #2 performed was cycle to High. For switch #2, the next cycle is Off.
Then I press favorites on switch #2 again and it goes to low as it should since it was off at this point.
Now I go back to switch #1 and press the favorites button. The fan goes to High. It does this because the last action performed by switch #1 was to cycle to Medium. Even though the fan was on low, it skips medium and goes directly to high because it is unaware that the other switch had put the fan on low.

The switches don’t allow binding to each other, only identify is available, so there’s no way to bind the Cycle of the two switches together.

For the time being, I’ve changed both switches to multi-tap fan speed control since they don’t need to be aware of each other’s cycle state for that to work.

Honestly, I prefer multi-tap. But my wife prefers cycle, and we all know who wins that argument! LOL

2

No help here, but I was about to post a different form of this same issue.

I don’t have a 3-way setup. I just have a Blue Dimmer and the Blue Canopy Module.

I’ve noticed that when I change the fan speed from my hub, the switch is not aware. So the next press of the config button on the switch changes the fan speed based on the last speed it was aware of, rather than the actual current fan speed.

It’s a small thing, but would be awesome if the canopy module could make the switch aware of speed changes that don’t originate from the switch.

1 Like
3

I noticed that too, but kind of forgot about it when I posted since I’m mainly concerned about it working without the hub in binding mode. I don’t often control this with the hub.

Obviously, the cycle state is stored in the switch and not broadcast on the network. So, the switch keeps track of its own last action and sends a specific value, ie. 33, 66, 99, or 0. It would be much better if the “cycle” was part of the canopy module instead of the switch. That way the fan would always know which speed is next in the cycle no matter which switch or the hub initiated the cycle action.
Thanks for pointing this out.