I’m in the early stages of my home automation adventure and just recently added another Blue Series 2-1 with a binding to a Smart Fan/Light Canopy Module to control a ceiling fan/lights.
I have everything working properly locally with the switch where I can control the lights via the up and down paddle and I can cycle through Low, Med, High, and Off fan speeds by pressing the Config button. It looks like cycling through fan speeds via the config button is handled in firmware? As there were no automations to create. I followed this guide:
I wanted to add the ability to also control the lights and fan via an Ikea Rodret button. I set up an automation where when I press “First Button” it activates “Toggle Office Light Switch”. This works great, and the LEDs on the switch act as if I pressed the paddle button on the switch.
However when creating an automation for controlling the fan via the “Second Button” on the Rodret, I didn’t see any actions under my Switch to “Toggle Button 3/Config Button”. This meant I had to setup an automation where I cycle through setting the speed of the fan via the Canopy module based on the current speed. This works, however then the switch is no longer “synced” to the fan speed.
For example: If I use my Rodret to cycle the fan speed to Low from Off (one press of the button), if I then press the config button on the switch it thinks the fan should be set to Low and the LEDs indicate it set the fan to Low when I wanted it to set the fan to Med due to it already being at Low.
Is there a way to have an action that Toggles the config button the same as the paddle so that the switch stays “synced” to the current state of the fan?
I don’t believe it’s currently possible. There’s an open feature request (on the private github) to expose another endpoint for the config button so that the fan speed can be bound to it for state tracking but that hasn’t been implemented yet.
@EricM_Inovelli may be able to talk about how high that is in the priority list.
This is exactly why I set my config buttons to multi-tap. 1=low, 2=mid, 3=hi, hold=off.
That way the config button doesn’t have to stay synced.
My automations control the canopy, not the switch.
I likely have a misunderstanding, but when you have the option to set how the config button controls the fan (cycle between speeds or multi-tap), isn’t that at a firmware level? If so, then what do you mean by your automations control the canopy, do you have a custom automation setup to handle the multi-tap of the config button?
Yes, the cycle vs multi-tap is at firmware level, and it works perfectly whether the hub is online or not.
But I also have automations at the hub level. I like to be able to control this stuff from my pc or phone as well. And since what I’m ultimately controlling is the canopy, that is what I automate rather than automating a switch that indirectly controls the canopy through binding.
Makes sense, which explains the multi-tap approach then as the switch/switch LEDs would be “synced” because you’re discretely calling for a specific speed each time you physically operate the switch as opposed to keeping track of the current state which isn’t being reported back to the switch via the canopy unit automatically when doing the cycle speed approach.
Thanks for your input!