These remotes just report “on” press, “on” hold, “off” press, and “off” hold and don’t (natively) have actions on double or triple taps (though you could probably do an automation that counts taps and does timing to kludge this, there are other blueprints here that you can examine to adapt this one to do this)
With the native functionality, you could still control two devices, one would be turned on/off with pressing the appropriate button, and the other turned on/off by holding the appropriate button (that is what I am doing with mine)
Or you could use a toggle action and control 4 devices with these 4 actions…
I made a Blueprint that combines this with the on/off/dimming blueprint referenced in this topic. By default, it will turn a specified light on/off and dim it, but any of the four presses (on/off/hold-on/hold-off) can be overridden and customized. I wanted a light control button that mostly behaved like normal, but could use a long-press to turn the light on to full brightness instead of the last value. It can be found here: ZHA - Ikea Tradfri wireless dimmer with options for custom actions
My experience with this blueprint is that when the light has been off for a while and I turned it back on, it turns on on the lowest brightness. Is there a way to fix that?
The blueprint just calls the service you specify. If it is a light.turn_on service, without further options/service data, that will normally turn the light on at the same brightness it was last left at.
Depending on the integration of your light, if your light dims over time, it may be that the integration read back the light status after it started dimming, but before it turned off so it may have recorded that it was at a low brightness the last time it was “on” (my GE Z-Wave dimmers seem to do this).
If you always want an action in the the blueprint to turn the light on to full (or any specific) brightness, just specify that in the options/service data.
You are not using the blueprint in this thread. Check in that blueprint’s discussion thread.
But likely there will need to be a change to the blueprint itself to add the brightness:100 data to the turn on command.
I’m not sure if it’s related to the ikea outlet not being paired correctly (however I’ve re-paired it already to test). I say this because if I manually toggle the outlet on in the configuration of the device, it works, same when I toggle it off, but then it sets itself to “On” when it physically is still off.
EDIT / UPDATE: I came back to this issue the next day, and everything was working fine. It seems the zigbee network just needed time to settle in after being paired.
I imported this blueprint but my switch isn’t showing up in the device list. I have it among my devices (it’s connected to the IKEA gateway). I tried connecting it directly to deCONZ through the Phoscon web app, but that doesn’t seem possible.
I’m new to HA but I figured this little switch would be the easiest in the world to get working :-/
Hello thank you for this blueprint, it looks very clean. But for some reason I cannot get one use case working. I wanted to turn light on, wait some time and turn it off.
But then I mapped those actions in this blueprint to any button press light never turn off