# Button + (Release 1.0.9, Test 1.0.17) **URL:** \ **Category:** Apps\ **Tags:** app\ **Created:** [September 21, 2023, 9:54pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931 "2023-09-21T21:54:31Z")\ **Posts on this page:** 14\ **Page:** 58
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [October 21, 2026, 1:37pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1160 "2026-10-21T13:37:59Z")
That behaviour is intended. The first click shows the current value and then following clicks while the value is on display changes it. It works for both click and long press. I will try your new configuration this evening. ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [October 22, 2026, 6:09am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1161 "2026-10-22T06:09:20Z")
I have published a new test version that should hopefully fix the stalled configuration loading. ---
**Author:** ![Swedownhill](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/swedownhill/32/121042_2.png) [@Swedownhill](https://community.homey.app/u/Swedownhill)\ **Post date:** [October 24, 2026, 7:41pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1162 "2026-10-24T19:41:09Z")
I don’t know why, but since the introduction of the AI based stuff my setup has started working unreliably. I haven’t changed the configuration myself, but issues have started to appear such as buttons remain on when they are supposed to be off, flows related to managing my TV causes it to turn back on when I turn it off, and I have to immediately turn it off a second time to leave it off, and so on.. I’m going to stand in line with another member in this thread who recently suggested a second app with the new experimental features separated from the old way of managing the Button+. I find it so buggy, the interface is so confusing, and the flows we have to create to make rather basic functionality work become ridiculously complex, all in such a way that I’m no longer motivated to use the product going forward. Such a shame because it’s got a lot of potential but you lost me half way. ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [October 25, 2026, 5:59am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1163 "2026-10-25T05:59:49Z")
> [@Swedownhill](#): > > but issues have started to appear such as buttons remain on when they are supposed to be off, flows related to managing my TV causes it to turn back on when I turn it off, and I have to immediately turn it off a second time to leave it off, and so on.. Could you send the configuration so I can investigate. > [@Swedownhill](#): > > I’m going to stand in line with another member in this thread who recently suggested a second app with the new experimental features separated from the old way of managing the Button+. The problem is Athom don’t like to have multiple apps for the same product as it then become confusing for user to know which app they should install. > [@Swedownhill](#): > > I find it so buggy If you can describe the bugs individually, I will fix them ASAP. Also, which version are you using? > [@Swedownhill](#): > > the interface is so confusing, The redesign was intended to make the configuration easier as you can see what your setting will produce before sending it to the panel and you click on the part you want to change rather than navigate a long list of setting. Can you let me know which bits you find confusing so I can help. > [@Swedownhill](#): > > and the flows we have to create to make rather basic functionality work become ridiculously complex The Flows should still work the same as before and all I have done is deprecate a lot of duplicates as the list was becoming rather large, so they should be less complex. > [@Swedownhill](#): > > all in such a way that I’m no longer motivated to use the product going forward. I’m sorry that the changes have made you feel this way as my goal is to make it as easy as possible to use while providing as much flexibility as possible. I have tried to add the new advanced features behind a second layer so that the basic setup can still be done with as few settings and clicks as possible. ---
**Author:** ![Swedownhill](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/swedownhill/32/121042_2.png) [@Swedownhill](https://community.homey.app/u/Swedownhill)\ **Post date:** [October 25, 2026, 8:22am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1164 "2026-10-25T08:22:54Z")
I’ve sent a DM to continue the conversation. ---
**Author:** ![1xe](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/1xe/32/17154_2.png) [@1xe](https://community.homey.app/u/1xe)\ **Post date:** [October 25, 2026, 10:03pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1165 "2026-10-25T22:03:31Z")
Please, share your findings. I am quite a new user for Button+ as I started with Hardware V2. I am very interested in bringing in the best UX as possible, Along side to Homey that allows like three-four different ways to do exact same thing is overlayed with Button+ app that also has other three ways to configure, makes it 12 different approaches that are very hard to maintain in the regular way. I yet voting to tighten up overengienerd functionality. As set the reasonable restrictions of what can be configured and what can be restricted right away. Otherwise it is becomes a “10-in1 useless kitchen processor” hanging on the wall ---
**Author:** ![Swedownhill](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/swedownhill/32/121042_2.png) [@Swedownhill](https://community.homey.app/u/Swedownhill)\ **Post date:** [October 26, 2026, 8:32pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1166 "2026-10-26T20:32:10Z")
Not sure if your comment was directed towards me/my recent posts. But I’ve been using an advanced flow where I change the On and Off-state of different buttons depending on other conditions outside of the Button+ ecosystem, such as different HDMI sources on a TV (one Button+ button for each source). So if the TV HDMI Source is set to X, then the Button+ button for X would turn on as well. Adrian helped me discover that changing the On/Off-state of the buttons triggered flow cards as if the button was pressed, which it was not. So the current test version (1.0.16) was adjusted to remove this behaviour, and so far I think it helps. 🙂 ---
**Author:** ![1xe](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/1xe/32/17154_2.png) [@1xe](https://community.homey.app/u/1xe)\ **Post date:** [October 27, 2026, 10:08am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1167 "2026-10-27T10:08:31Z")
Actually it was towards you, as only the community can test the entire app throughout and suggest enchantments inplement. ---
**Author:** ![1xe](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/1xe/32/17154_2.png) [@1xe](https://community.homey.app/u/1xe)\ **Post date:** [October 27, 2026, 8:30pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1168 "2026-10-27T20:30:48Z")
Catched another bug. Left Button, First Row - double click doesn’t work in the advanced flow flow ![Screenshot 2026-10-27 at 23.13.53](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/9/29dbb656b3fe1763f4f36fe2883939324f5dd356.png) Can you check this block throughout. Looks like as functionality was broken for entire commands of Left Button at some point, and you you are fixing in by one by one basics, it yet may not work somewhere else. And I have a question about the pupore of the new “Pressed” function? “Pressed” reacts on everything: Click, Double Click and Long Press and this means that it is functions exactly as “Release”. ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [October 27, 2026, 10:45pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1169 "2026-10-27T22:45:15Z")
> [@1xe](#): > > Catched another bug. Left Button, First Row - double click doesn’t work in the advanced flow flow The double click only works if the button is set to ADV mode as that was a new feature. I could add it for the STD mode but it would require the delay of the click event which changes the old behaviour. > [@1xe](#): > > And I have a question about the pupore of the new “Pressed” function? “Pressed” reacts on everything: Click, Double Click and Long Press and this means that it is functions exactly as “Release”. The Pressed event triggers as soon as the button is pressed, so it will always occur without any delays required to detect double click or long press. I will also publish a new test version. I checked the shared event path for **both buttons** , not just the reported left-button case, and fixed four issues locally: - **Flow-only double-clicks could be ignored** when a target device remained selected without an action capability. - **Long presses could leave stale state** , blocking subsequent single/double-click handling. - Connector long-press events always reported **repeat count 0**. - The deprecated configuration trigger shared a mutable state object with the newer trigger, potentially breaking configuration matching. ---
**Author:** ![1xe](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/1xe/32/17154_2.png) [@1xe](https://community.homey.app/u/1xe)\ **Post date:** [October 28, 2026, 7:14am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1170 "2026-10-28T07:14:33Z")
> The double click only works if the button is set to ADV mode as that was a new feature. I could add it for the STD mode but it would require the delay of the click event which changes the old behaviour. Better keep it on ADV settings. But add an informational block to the flow card that will describe the reaction behavior. - > 1. **Flow-only double-clicks could be ignored** when a target device remained selected without an action capability. > 2. **Long presses could leave stale state** , blocking subsequent single/double-click handling. > 3. Connector long-press events always reported **repeat count 0**. > 4. The deprecated configuration trigger shared a mutable state object with the newer trigger, potentially breaking configuration matching. This looks like response from an AI on a code fragmanet, as barely understand the meaning about it. And yet I still think that “Pressed” = “Release” that is just happening 100 ms elier in just a case of Single Click. ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [October 28, 2026, 7:22am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1171 "2026-10-28T07:22:30Z")
> [@1xe](#): > > And yet I still think that “Pressed” = “Release” that is just happening 100 ms elier in just a case of Single Click. Correct in the std case, but for adv it could be up to 500ms later due to the double click delay. As soon as the button is pressed a pressed event is triggered. The release event will only fire when the button is released, so the time between them is as long as the button is pressed. ---
**Author:** ![1xe](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/1xe/32/17154_2.png) [@1xe](https://community.homey.app/u/1xe)\ **Post date:** [October 28, 2026, 11:53am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1172 "2026-10-28T11:53:07Z")
Can you please add Long Press Release event if this is possble ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [October 28, 2026, 6:38pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931/1173 "2026-10-28T18:38:59Z")
That is already there. The release event only fires after a long press. [Previous page](https://community.homey.app/t/button-release-1-0-9-test-1-0-17/89931.md?page=57)