# Button + (Release 1.0.9, Test 1.0.10) **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-10/89931 "2023-09-21T21:54:31Z")\ **Posts on this page:** 20\ **Page:** 56
**Author:** ![HomeyBram](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeybram/32/17513_2.png) [@HomeyBram](https://community.homey.app/u/HomeyBram)\ **Post date:** [October 5, 2026, 1:33pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1119 "2026-10-05T13:33:32Z")
Hello, I have a Button+ first generation FW 3.0.3. Homey app test 1.0.6. Since Homey app v1.0.x (I think) what is not working anymore is the condition card “Button is on/off”. Do I have to change something in my configurations? ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/e/2ec534a3b1cceb410d2761f974ef98ef146d85bb.png) Update: It is working from the Button+ pane on the web interface but not for the physical button on the device itself. From the LED color I can verify that the physical button is switched on and off. ---
**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 5, 2026, 4:23pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1120 "2026-10-05T16:23:56Z")
I might have found the problem so could you try 1.0.7? ---
**Author:** ![HomeyBram](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeybram/32/17513_2.png) [@HomeyBram](https://community.homey.app/u/HomeyBram)\ **Post date:** [October 5, 2026, 4:37pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1121 "2026-10-05T16:37:29Z")
Yes, v1.0.7 solved the condition card issue, thanks a lot! ---
**Author:** ![Lammy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lammy/32/11436_2.png) [@Lammy](https://community.homey.app/u/Lammy)\ **Post date:** [October 6, 2026, 9:54am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1122 "2026-10-06T09:54:23Z")
Hi Adrian, I had the same problem (couldn’t switch buttons on/off with flows). Version 1.0.7 fixed that. A small new problem though. If I use the trigger “A button was pressed” followed by the action “Switch button off”, button-pressed events are fired in an endless loop. That doesn’t make sense. After the first “Switch button off” action, the button is off and stays off. I have changed the trigger to “A button was released” and that works for me. I have a V1 B+ with FW 3.1.7. Thanks a lot for your efforts! ---
**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 6, 2026, 9:29pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1123 "2026-10-06T21:29:08Z")
Fixe in new test version. ---
**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 8, 2026, 11:18am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1124 "2026-10-08T11:18:38Z")
Hi, Adrian. I am yet trying to find the best way to handle the internal click/double click/long press logic. Please let me know if the button+ firmware allows to send **“long press release”** state. If it does, it would be AWASOME to have such event on the list. I am trying to achieve smoothless Dimming using s"long press" (start) → dimming process → “release button” (stop). “Release button” simultaneously kills the process for Single Click ![Screenshot 2026-10-08 at 14.14.03](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/a/aa8a90ac60f593a1dd826b40abf9c0c98cc6b3ca.png) ( Counting Long Press events also works, but this doesn’t give smooth feeling) Reverse engineering of the behavior of HUE Philips original button I found out that they use this topology: The accessory firmware natively differentiates: initial\_press (finger down) short\_release (finger up within 400ms → → click action) repeat (held down → → dim action) long\_release (finger up after holding → → stop action) “Long Press release” would be also very helpfull for Curtain Operations to stop them in the mid air. Or to confirm action if Long Press is used for listing through modes. ---
**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 9, 2026, 9:54pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1125 "2026-10-09T21:54:24Z")
If you are using the test version 1.0.8, you should see the click event followed by release if the button is pressed and released quickly, long press events while the button is held down and release when the button is released, ---
**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 9, 2026, 11:16pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1126 "2026-10-09T23:16:06Z")
Yep, That was working since 1.0.6 but in both cases this is the very same “release”. I am asking for separate type of “release” that one that is following “long press”. ![Screenshot 2026-10-10 at 02.06.32](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/5/f5254a72a639048612540396ee8b1719b10af015.png) The plain example: I have curtians and what to do the following: 1. “Single click” to go all the way from open to close. 2. “Long Press” to continuously close the curtains till button “release”, on this event they stop. In such case “Release” overrides the “Single click”, the curtains stop before even starting to move. ---
**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 10, 2026, 9:46am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1127 "2026-10-10T09:46:02Z")
> [@1xe](#): > > The plain example: I have curtians and what to do the following: > > 1. “Single click” to go all the way from open to close. > > 2. “Long Press” to continuously close the curtains till button “release”, on this event they stop. > > In such case “Release” overrides the “Single click”, the curtains stop before even starting to move. Thanks for the extra clarification so I understand the problem. The button + actually always send Click - Release, or Click - Long Press - Release events, so I have already debounced the Click so it doesn’t trigger for the Long press. I also generate the Double Clicked event by detecting two Click events within a small window. So, I will look into suppressing the Release event for Clicks. Meanwhile have you considered configuring the button to do the task for you: 1. Set the button to ADV mode, 2. Select the window covering device for a button / page, ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/6/760d7a318a419a3b7096dc458913be80af7005a0.png) 3. Click on the Button options, 4. Select the device and the windowcoverings\_set capability for the Click and Long/Repeat Action / Capability, 5. Set the Click Value Step to +100, 6. Set the Double Click Action to Toggle Direction, 7. Set the Long Repeat Value Step to +1 (or whatever increment you want) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/7/47bcfc3127dc95d44503865a677080dffdca7f21.png) Now each click of the button will alternate between fully open and fully closed, while a long press will increment / decrement the position value and then apply that when you release the button. ---
**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 10, 2026, 2:36pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1128 "2026-10-10T14:36:07Z")
I gave curtains just as the most certain example of the request. The problems here are ( am writing only about Advanced flows. The internal Devices Capabilities configurator you made is juiced to the max!) 1. that curtain motors (unlike the lamps) do not transmit its current position throughout its pass. They all have a polling interval of 2-3 seconds. I own quite a taxi park of them - Aura, Ikea, Zemismart (on Thread), and this is relevant for all of them. 2. it is almost impossible to set them in line with button with Event counter and Value Step. As for example it takes 35 seconds to entirely open or close 3 meter tall window. Button sends events every 500 ms (by default) so it takes 20 seconds of holding to reach either 0% or 100% in 5% increasment per event. So “overpressing” the long click will not give a correct result. Second idea that seems really exiting: that will also work to accomodate “long press release” I have a bunch of different light color scenes. Like “party mode”, “dimmed”, “bright” etc. In most situations, clicking and sequetianly them is not a good idea (Bright and Dimmed are completely opposite). Holding the “long press” changes pushes just scene name to the row’s display without actually applying it. And “release” actually fires the scene. I am not saying “long press release” is a deal breaker but It would be very useful. ---
**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 10, 2026, 2:48pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1129 "2026-10-10T14:48:21Z")
When you setup the buttons as I mentioned, the long press increments /decrements the value on the display and only sends the position value to the device when you release the button. That way you can select the position and then let the device get on with it. Feedback is not required. ---
**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 10, 2026, 9:44pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1130 "2026-10-10T21:44:02Z")
I have published a new test version. This has an option to disable the Released event that follows a Click event. Also there is now a wizard feature for each button where you can select a device type, then a specific device and it will automatically configure the button to control that device. All the settings can still be changed after the wizard has set them up. ---
**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 10, 2026, 10:01pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1131 "2026-10-10T22:01:02Z")
Wow! You are the best! Rolling out to explore how it works, thank you so much! ---
**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 11, 2026, 9:14pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1132 "2026-10-11T21:14:09Z")
Hi, Adrian. Found one and half bugs. 1. The Button+ WebUI doesn’t load on 1.0.9 - it blinks and disappears. 2. I don’t get from where Button is polling the time. Because for my time is one hour early on the button+. I did check the timeline events on homey, they are fine, the do have the proper time. (actually I wanted to take a look in the WebUI to try to change it and found it broken) UPD: Fixed. Looks like it was a bug in the Homey Device location, resolved after reboot ---
**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 12, 2026, 1:52am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1133 "2026-10-12T01:52:41Z")
The web ui is served by the Button + firmware, so I have no control over that. Maybe the configuration is too complex for it. The time is taken from Homey, but maybe it’s not picking up the timezone or the daylight saving. ---
**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\ **Post date:** [October 12, 2026, 2:52am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1134 "2026-10-12T02:52:49Z")
Do you have any SVGs on the display? I have the same that the WebUI of Button+ loads and then reloads to a blank page. Trying to find something before reporting to Button+ support. Do you have the V1 or V2 hardware? ---
**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 12, 2026, 9:43am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1135 "2026-10-12T09:43:55Z")
I have Button+ v2 hardware. No there is no SVGs, and the setup is quite simple as I am doing the most in Advanced flows. The things that are set on actual app are: On the Display module - Time, temperature, page numbers on default Page 0 and 1 Global Variable on the Page 1. On the buttons - it is just Top labels, and the LED lights are turned off. The other thing that I wanted to metion, going with Advanced Flows for configuration is a bit “Hard Core” it took me about an hour to move the setup from one button plus to another despite the configuretions are almost indetintical varying with just single row. So my question to Adrian, if it is possible to create Button indpendedt cards like these ![Screenshot 2026-10-12 at 12.42.09](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/79aedacd2d520e4a952affd851aa5e89bd49b090.png) To decouple the Device and link Configurations and Groups to advanced flows direclty. ---
**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 12, 2026, 11:56am UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1136 "2026-10-12T11:56:35Z")
> [@1xe](#): > > To decouple the Device and link Configurations and Groups to advanced flows direclty. I’m not sure that will be possible as when a button is pressed it sends the device id, connector number and side. So the app uses the device id to lookup the configuration assigned to the connector. ---
**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 12, 2026, 1:30pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1137 "2026-10-12T13:30:44Z")
If it is not possible this is fine, but structurally it looks that is can be possibly implemented. ![Screenshot 2026-10-12 at 16.18.41](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/1/91adbcc99059e9b0106b7c2a6ed3b487a3f4948d.png) If this one can be extended to “**On the [DEVICE]** [left] button on [button] configuration…” Where the [DEVICE] is place holder for available list of Buttons+, it can be IP or dropdown. You could also reference “All buttons+” as it is done for Pages right now or filter out the list to just configurations that are currently applied for this Button+. You already reference Button IDs within the app to push the configuration change to exact device. This will open a possibility to copy/paste the flow card to reuse it for the other Button. In the current allocation, when reusing the very same config on the other button+ device you have to recreate it from scratch - assign, what button, where and how it was pressed. And this for all WHEN, AND and THEN Cards. Alongside to this, there is also a minor tweak that I can suggest (if it is possible), for the very same WHEN card as above: WHEN The [Configurations] show in numbers instead of custom naming, ![Screenshot 2026-10-12 at 16.27.06](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/a/aa4d6f8be06c5ff168869303b7e3717633ec3d6e.png) while THEN card show Configuration number + Custom name. ![Screenshot 2026-10-12 at 16.27.16](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/c/8cc2aac855a6848996737f8562f15e8df846bc7a.png) I think that showing Just Custom name (without long “Configuration number” will look fantastic ---
**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 12, 2026, 11:00pm UTC](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931/1138 "2026-10-12T23:00:03Z")
I have published a new test version with the app cards, etc. [Previous page](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931.md?page=55) [Next page](https://community.homey.app/t/button-release-1-0-9-test-1-0-10/89931.md?page=57)