Button + (Release 1.0.0, Test 1.0.7)

[1xe]

After about hour of stress test didn’t find any noticable bugs. Despite still looks like your App’s internal broker breaks the render of WebUI.

When button is completely reset to factory defaults WebUI loads normally, but as soon the configuration pushed from the App it flicks with the interface for a second and stays with white page. My Button was added manually via IP (if this makes sense)

But I actually want to ask for a feature request. (What is “Target Button+” by the way?)

Right now Display module have [Items], each of them have [Top Label] and Capability.

Is it possible to add an option to change them with flow cards, and add an option for “Capability” to be text (or even svg)

So new flow cards could be:

Set the [Item #] Display Label on [Configuration #] page [Page #] to [Label]

Set the [Item #] Display Top Label on [Configuration #] page [Page #] to [Label]

The reason I am requesting has two purposes

1. Using Homey’s internally stored Variables set in the capabilities are not always a good idea. For Example for controlling AC I would have to create Variables for Fan, Mode, Temp, Swing for all four AC Units just to have the correct numbers displayed on 4 Button+ devices - totaling 16 variables. (Yeh, I understand that with new capability engine you did it is easily possible, the example is not really good, but explaining that I am about to use Name Tags on the output made by vibe coded HomeyScript for HUE lights, won’t be easy)

2. This will allow to draw “Virtual” 1 Row of Buttons who want to trigger flows by them.

[1xe]

Aha! I found a bug. Single click always reports Off State and only off. Used such flow to debug

[Adrian_Rockall]

@1xe

(What is “Target Button+” by the way?)

That specifically uses the Button + device the configurguration is sent to. If you have more than one Button + and you selected say the Lounge Button +, then the capability of the Lounge button + will be used even when sent to the Kitchen Button +. However, if you select Target Button+, the capability will be from the Button+ that is using the configuration.

@1xe

Right now Display module have [Items], each of them have [Top Label] and Capability.

Is it possible to add an option to change them with flow cards, and add an option for “Capability” to be text (or even svg)

So new flow cards could be:

Set the [Item #] Display Label on [Configuration #] page [Page #] to [Label]

Set the [Item #] Display Top Label on [Configuration #] page [Page #] to [Label]

I will need to think about how to define the items and reliably reference them as item numbers tend to be fluid as they need to be defined from to left to bottom right and therefore, moving them changes the order they are defined.

@1xe

Aha! I found a bug. Single click always reports Off State and only off. Used such flow to debug

Fixed in 1.0.4

[Peter_Stern]

Hi Adrian

I have updated to 1.0.0 and afterwards to 1.0.4, but in both cases the Flow Card for reconfiguration will not work. If I make this via card with maintenance it works.

[1xe]

The idea about [Items] came from the “Like” button and “Counter” that is in the Factory default configuration.

Probably assigning [Items] to Display Configuration Page 0 (Defaults) will be enough, otherwise it may be to complicated to operate. You can output them in the same way as you did [Configuration] on the preview Tab the same way you assign configuration to the Button Rows.

[Swedownhill]

I have noticed that after upgrading Button+ to version 1.0.0, the pages on the device itself no longer include page 1.

I have the current page shown on the display, and it used to be 1, 2, 3 etc. But after the update the exact same setup now shows 2, 3, 4 etc instead..

[Adrian_Rockall]

Could you try the 1.0.4 test version as I think I have fixed that.

[Swedownhill]

Awesome! I can confirm that it is fixed in 1.0.4

[Venxir]

I’ve been rebuilding the firmware from button+ with help of the latest esphome libraries and already got your app to interface with it.

I’m hoping to include some more features like led blinking and fading and better overall speeds. Also combined with your app and my firmware i’m hoping on improving the integration further. I really like your display designer in homey. Currently have all bars working and paging too.

[1xe]

@1xe

Aha! I found a bug. Single click always reports Off State and only off. Used such flow to debug

Looks like Single click still doesn’t work right just yet, still always show Off state on 1.0.4

Futhermore, looks like the functionality is broken no in the State Tag. But rather a button itself. I previously dimmed out the LEDs on the button device (they annoyed me to much.)

Now I reapplied the Red Color and added text “On” / “Off” via App’s Configuration. Single clicking never lids the LED On or renders “On” to the display. Just in case Double Click and Long Press works fine on the button. The logs look wired for me, they do not have State at all.

These are sequential Off and On commands:

• 2026-09-29T21:30:27.132Z
  TIMING click ts=2026-09-29T21:30:27.131Z ms=1790717427131 key=1_left_1 configNo=0 page=1

• 2026-09-29T21:30:27.132Z
  Click: queued first click for 1_left_1 long=true double=true

• 2026-09-29T21:30:27.320Z
  TIMING release ts=2026-09-29T21:30:27.319Z ms=1790717427319 key=1_left_1 configNo=0 page=1

• 2026-09-29T21:30:29.538Z
  TIMING click ts=2026-09-29T21:30:29.537Z ms=1790717429537 key=1_left_1 configNo=0 page=1

• 2026-09-29T21:30:29.539Z
  Click: queued first click for 1_left_1 long=true double=true

• 2026-09-29T21:30:29.693Z
  TIMING release ts=2026-09-29T21:30:29.692Z ms=1790717429692 key=1_left_1 configNo=0 page=1

[Adrian_Rockall]

What is your Advanced single click is set to (device/capability or Trigger Flow Only)?
Also, is it a Display or LED device?

[Gunther_Potters]

Hello, Ever since the update to version 1.0…, I’ve been having recurring problems with my Button+. Usually, I only see the text on the screen without the corresponding values; the button displays also only appear intermittently. When it does become active, I can only press a button once before the Button+ goes into “freeze mode.” The only way to get it working again is to reset it—not just once, but several times—using the button at the bottom. Personally, I don’t mind it that much, but it’s driving my wife and children crazy. Is there anything that can be done about this? I don’t have any other switches besides this button, so it’s really frustrating. My button’s are V1. I use SVS’s for the button’s

[1xe]

In the Advanced Single/double/long press it is set for Trigger Flow Only. I am trying to avoid using Capabilities.

It is for LED indicator and Label on the Button Row. (NOT a Display module)

[Adrian_Rockall]

Could you open the app settings page and select the import / export tab. Then click on Send Export so I can check the configuration to see if that provides any clues.

[Gunther_Potters]

send you te report.

[Adrian_Rockall]

@1xe

In the Advanced Single/double/long press it is set for Trigger Flow Only.

@Gunther_Potters

Hello, Ever since the update to version 1.0…, I’ve been having recurring problems with my Button+. Usually, I only see the text on the screen without the corresponding values; the button displays also only appear intermittently.

Both fixed in 1.0.5

[Gunther_Potters]

thanks for the update, i will try tomorrow.

[Arie_J_Godschalk]

Hai @Adrian_Rockall ,

I have a question, which i cannot seem to figure out.
(I have installed the current test version.)

I have the Button+ with 3 button bars (so 4x2 buttons including the display).
Today i chnaged from manually updating everything with flows, to a Group and setup all 3 buttonbars to a configuration.
Now, the Toptitles all go correct.

To keep it simple, ill keep my question to just 1 button: The left top-button-bar button (not the display one).

In the configuration i have set that, when On, the button will light up red.
When i press the physical button on the device (with no flows behind it whatsoever), it does work: The light switches from off to red.

But how can i, through a flow, set the button to on/off?
There are two flowcards: Turn x Button on connector x page x On/Off.
That flowcard does not seem to switch the button On/Off?
Before updating to the test version, activating that flowcard did show on the Device-Button-Tab because the ButtonBar Connector 2 Left would change to On/Off. However, since the update to the testversion, this doesn’t happen.
But with the live version and the testversion, in both cases, using that flowcard will not change the light to red/off.

Also, using that flowcard really doesnt do anything for the physical button:

1. If i press the physical button, the light turns on (meaning the button was off).
2. Pressing it again turns the light off (meaning the button was on).
3. Using the flowcard to say “turn it on” (it doesnt seem to do anything).
4. Then pressing the physical button and the light turns on (which means step 2 worked obv. but step 3 indeed didn’t do anything.

So, how can i, with a flowcard, set the physical button to On/Off when using Group/Configuration (with pages)?
Or is the use of variables required? Does the device remember the state of its buttons on reset etc.?

EDIT:
Also, when the device is set to Connector mode, this is how my buttontab looks like:

When i switch to Group Mode, it looked different: the left side were all showing the same name, but without Connector, but the right side showed the names with Connector (just like the above image).
Right now i switched back and forth, thought that it might have gone wrong while changing the capabilities. However, all buttons now keep the names just like the above image, even though i am in Group mode.

EDIT2:
Switching the complete group, shows the wrong group.
I just created a second group (copied from my first).
The first group has 3 button rows, while group 2 only has 1 buttonrow.
Switching to group1 shows group2 on the device, and switching to group2 shows group1 on the device.

EDIT3:
For one button, i have selected a alarm (doorsensor) capability.
It reacts correctly, only thing is, i can still click the physical button and the status will change. While the tooltip says that if its read-only (like an alarm), this should not be possible.
To be sure, i just checked the device in HS, and it truelly is the default alarm_contact (with setable:false).

[Adrian_Rockall]

Can you check the new test version to see if it fixes the issues?

[Arie_J_Godschalk]

Yeah ill check that hopefully tomorrow.
And: happy birthday