Which firmware is your hub at and which browser are you using? Mines working as expected, I'm currently at firmware 2.1.3.128 and using iOS Chrome browser.
Well it looks like the button controller is v 3.0 now so it's possible your button rule was originally created on v 1.0 or something and there is a bug between the two?
I would suggest that you use Rule Machine instead of Button Controller 3.0.
In a new rule, select 'Button device' as the trigger event, and it will bring up the same UI you have for Button Controller, but with more options. Also, Button Controller 3.0 is due for retirement, so bug fixes will be happening in the RM version of it. Old Button Controller instances will continue to work indefinitely.
In summary it wasn't a big deal to convert over to RM 4.0 from Button Controller. Conceptually having a separate Button Controller may be more simplistic, but obviously RM 4.0 is way more flexible and powerful.
Question: In the following screenshot, isn't it more intuitive the put the action AFTER the condition on the screen? (instead of the way it is, before)? This is just a question, I'm not suggesting it as a change.
What condition? The Manage or Create Conditions at the bottom is a helper section. The text above "Select Action Type to add" is the list of the actions that have been created.