SmartThings Button pressed/doublePressed events (after the first one) don't seem to trigger rules

[dholbert]

CC @dhylands:

Following up #1416: my SmartThings Button (zigbee) now is detected correctly (with Zigbee Add-on updated to 0.6.1 last night), and the button does generate events when I press or double-press it -- but rules don't seem to be correctly triggered by those events. The first press triggers a rule as I expect, but subsequent presses do not (though they do get reported as "pressed" when I'm viewing the button's page on the gateway).

In particular, I set up two rules as follows:
Rule (1): If button event "pressed" occurs, turn bulb on
Rule (2): If button event "doublePressed" occurs, turn bulb off

If I disable + reenable these rules (with the slider toggle on the rules view), then the first button-press successfully turns on the bulb, and the first double-press successfully turns off the bulb. But subsequent presses don't have any effect on the bulb.

[dholbert]

(I'm hoping you can reproduce, but in case you can't: I'm happy to try things out & gather more diagnostic info etc. later on. This setup is at my home & I'm not near it right now, though I do have access to the web interface of course.)

[dhylands]

There was an update made to the rules engine, which you probably don't have that will correct this.
In particular #1421 is the PR which fixed the problem.

So you can either update your gateway using git, or you'll need to wait until the next point release.

[dhylands]

P.S. I have the exact same rules setup and they've been working fine since PR #1421 landed.

[dholbert]

Thanks! I'll keep an eye out for the next point release.

[mrstegeman]

I'm going to call this fixed. @dholbert please reopen this issue if you have problems after our next release.

[dholbert]

@dhylands BTW I've noticed that my SmartThings motion sensor and sylvana dimming switch have stopped registering activity -- do you know if that's something that'd be fixed by that same gateway PR (i.e. the next dot release)? And/or, does this sound like a known issue, or something I should dig into & investigate/report in more detail?

(In my memory, they both stopped working when I updated my zigbee addon from 0.6.0 to 0.6.1, though I'm not 100% sure of that.)

[dhylands]

I just created another update (0.6.3) that fixed some regressions I introduced. Can you see if that fixes things for you?

I've had issues with the 2016 versions of the SmartThings sensors, and the 2018 versions of the sensors have been working well. See https://github.com/mozilla-iot/wiki/wiki/Supported-Hardware for links to both versions and you should be able to tell from the pictures which ones you have.

[dholbert]

I installed the zigbee addon update (to 0.6.3) and removed & re-paired my motion sensor and switch.

My smartthings motion sensor (2018 version) does seem to register motion correctly now, but my sylvana dimmer switch is still in a broken state. It seems to be permanently "on" at 52%, regardless of short /long presses of either of its buttons.

[dholbert]

There was an update made to the rules engine, which you probably don't have that will correct this.
In particular #1421 is the PR which fixed the problem.

Following up: I can confirm that my SmartThings button is correctly registering pushes & triggering rules, now that I've got iot-gateway release version 0.6.1.