I created a button controller rule that initiates a bedtime routine.
The rule is supposed to turn of the main light (_HB_Lotte Plafond), and turn on a night light at 10% (_HB_Lotte balon) and dim that light to 0% over 15 minutes. When initiating the rule, it should send me a message on my phone.
What I see is that if I push the button, I get three messages, the main light goes off, but the nightlight does not go to 10%. Instead it remains at current lvl, and starts dimming by 1% every 10 seconds.
That would make some sense given the three triggers of the rule. The setLevel error would still need to some investigation though.
Is there any debug logging available for the device?
You may also want to look at the Zigbee Details page for the number of messages from the device, to see if it is the device sending 3 or something else in the driver.
Think its the driver somehow.
Replaced the button with another Ikea shortcut button, same issue.
Replaced the button with another brand button, issue is gone.
Ah, got it. I know with some of the other Ikea stuff the firmware version was important for some of the community drivers, so hopefully it is something like that here.
Still, weird for it to only report one event when not included in a rule....
Have you tried updating the firmware? Also, there was discusion over the multitap issue on the driver thread as well (specifically for the 4 button press events from a single press). It turned out to be a Strybar and not an E1812. But, the issue was resovled with firmware if I recall. In the firmware release notes, they aren't too descriptive. Just "stability improvements"
Just checking, as a few users had issues updating. Did you try changing the divide driver for the updates?
I had no issues with mine using the Ikea driver (once I realized the update takes a really long time to update). But, most had to switch to the "device" driver to run the update. Also, as I recall, the second biggest issue was walking the device up then IMMEDIATELY clicking the update button while the device is close to the hub.
I want to say it took something like ten minutes before the logs showed that the update was starting. You might try posting on that firmware thread. The developer is pretty darn responsive to those with questions.
