Is it because the sensor’s state reports the same value as its action attribute? If that’s true then why does the State Trigger use “attribute: action”?
I have tried both ways you suggested and it seems to work (by removing the “action” attribute from the state trigger and also changing the command variable). I did not think too much about that, I have used the other Ikea (Tradfri) switch blueprint which does not have a dimmer as my starting point. So maybe someone who has some deeper knowledge about the internals can give you the explanation.
I’m trying to use this and it mostly works. On/off is fine. The main issue is that the repeat doesn’t work dimming up or down. I just get one step up or down. I have to release and then hold again and it does one step up or down as appropriate.
I gave up on this blueprint. It seemed fundamentally flawed - I don’t remember the specifics but holding down wouldn’t dim up or down as per my last comment I think was the main thing. The repeat sequence was getting interrupted.
I ended up using this one with better success with some hacky modifications using ideas from this one just for the specific switch I’m using
Main problem is that it doesn’t stop at minimum dim level and just turns off. Also on the one Ikea ZigBee light I have, it’s quite slow to update the light but I expect that’s more the light than the script. My Wifi lights work much better at dimming.
Hi Guys,
thanks a lot for the information and great work above.
I made with my beginner knowledge a version that is running and is able to have smooth dimming and also steps. But probably there is room for improvement.