Button + (Release 0.7.17, Test 0.7.17)

Robin_De_Lange · February 27, 2025, 9:25pm

Yes, haha i said it in many words, but thats was what i like to see.

Thank you very much!

Adrian_Rockall · February 27, 2025, 9:41pm

OK, new test version has been published.

Robin_De_Lange · February 28, 2025, 6:42pm

It works, many thanks for the help again!

Ranney · March 4, 2025, 9:05pm

@Adrian_Rockall
I just sent a debug report because I was having problems setting button texts and LED colors (flow chart sets front/rear LED on connector x to color RGB). I found out that coincidentally only connector 4 right (which I always test on) does not work in the latest app version. Is this perhaps known? Thanks!

Edit: Button rows 3 and 4 swapped. Problem remains right on row 4
Motherboard swap done. Also now problem back. Row 4 right led (front and back) does not respond to flow cards to change RGB led color.

Pallieter · March 13, 2025, 11:02am

He, I’m struggling to get the ‘Congfiguration X was Released/Pressed’ card to work. I removed the application and added my button+ to have a clean install. But it still won’t trigger on this card. Any idea why this card won’t trigger?
The card that checks on connector number does work as expected. Tested on firmware 1.13.2 and 2.0.0. Both firmware versions have the same result.

Thank you!

Flow:

Button configuration:

Logs:

* 2025-03-13T10:56:01.907Z
MQTTclient.on message: buttonplus/btn_468678/button/1-0/pushbutton, {
  "event_type": "click"
}

* 2025-03-13T10:56:01.908Z
Panel processing MQTT message: click

* 2025-03-13T10:56:01.938Z
MQTTclient.on message: buttonplus/btn_468678/button/1-0/pushbutton, {
  "event_type": "release"
}

* 2025-03-13T10:56:01.939Z
Panel processing MQTT message: release

* 2025-03-13T10:56:01.940Z
triggerFlow (button_release)
 tokens: {
  "left_right": true,
  "connector": 1,
  "page": 0
},
 state: {
  "left_right": "left",
  "connector": 1
}

* 2025-03-13T10:56:01.942Z
triggerFlow (config_button_change)
 tokens: {
  "state": false,
  "page": 0
},
 state: {
  "left_right": "left",
  "displaybutton": "button",
  "config": 1,
  "state": "released"
}

* 2025-03-13T10:56:02.269Z
Capability changed: Lamp eetkamer, onoff, true

* 2025-03-13T10:56:02.271Z
triggerFlow (button_on)
 tokens: {
  "left_right": true,
  "connector": 1,
  "page": 0
},
 state: {
  "left_right": "left",
  "connector": 1
}

* 2025-03-13T10:56:02.272Z
triggerFlow (button_change)
 tokens: {
  "left_right": true,
  "connector": 1,
  "state": true,
  "page": 0
},
 state: {
  "left_right": "left",
  "connector": 1
}

* 2025-03-13T10:56:02.274Z
publishMQTTMessage: Aan to topic buttonplus/btn_468678/button/1-0/label/set

* 2025-03-13T10:56:02.275Z
publishMQTTMessage: 25600 to topic buttonplus/btn_468678/button/1-0/led/front/rgb/set

* 2025-03-13T10:56:02.277Z
publishMQTTMessage: 25600 to topic buttonplus/btn_468678/button/1-0/led/wall/rgb/set

* 2025-03-13T10:56:02.280Z
triggerFlow (config_button_change)
 tokens: {
  "state": true,
  "page": 0
},
 state: {
  "left_right": "left",
  "displaybutton": "button",
  "config": 1,
  "state": "clicked"
}

* 2025-03-13T10:56:02.282Z
publishMQTTMessage: homey_buttonplus/btn_468678/button/1-0/led/front/rgb/set, 25600, ignored, same as previous value

* 2025-03-13T10:56:02.283Z
publishMQTTMessage: homey_buttonplus/btn_468678/button/1-0/led/wall/rgb/set, 25600, ignored, same as previous value

* 2025-03-13T10:56:02.283Z
publishMQTTMessage: homey_buttonplus/btn_468678/button/1-0/label/set, Aan, ignored, same as previous value

* 2025-03-13T10:56:02.291Z
MQTTclient.on message: buttonplus/btn_468678/button/1-0/label/set, Aan

* 2025-03-13T10:56:02.293Z
MQTTclient.on message: buttonplus/btn_468678/button/1-0/led/front/rgb/set, 25600

* 2025-03-13T10:56:02.295Z
MQTTclient.on message: buttonplus/btn_468678/button/1-0/led/wall/rgb/set, 25600

Ranney · March 23, 2025, 9:24am

I have tested extensively but am still stuck on setting led colors on row 4 right button (front and back).
No matter what I do, row 4 right (if built with 4 modules (display and 3 rows of buttons), I get the bottom row right button no front or back LED on. (Latest 1.x firmware)
New display module, 3x buttons, new motherboard, none of it makes a difference. Do I build it with 1 display and 1 row of buttons then I can control the bottom row on the right. This firmware has worked fine here for an extended period of time. Anyone have any idea what is going wrong? Thanks for everyone’s time and help!
Ps. When I use the flowchart ‘set front and back (both) to a color; then it is not working on any button bar. But front of back individual is working on other button rows.

Firmware: 1.13.3
App: 0.7.19

Torch1969 · March 23, 2025, 9:41am

@Ranney any reason you didn’t upgrade the button+ to firmware 2.0 yet?
I remember similar issue’s on row 4 and right button not working properly when I was on older firmware version and app version was already adapted to the new firmware version. After upgrading button+ to firmware 2.0 it took me some attempts to get it working ok (saving and loading configurations in homey app), but after that the button+ is working ok for almost 2 months now.

Ranney · March 23, 2025, 10:02am

Thanks for your time to replay!

Yes. Multiple reasons

The latest 1.x firmware is really stable here
I don’t like devices as this with direct internet acces. In 1.x I can block this. In 2.x I then get wifi error messages and I saw several times (in 2 days of testing) a screen with time and number of likes. The buttons then became a +like button. I don’t particularly like this. (Especially not after my predecessor, a smpl display, suddenly seemed to show propaganda from Ukraine. (Turned out later to be a hidden future - don’t want to make political statements, but in the house I find it very unpleasant when the whole family/visitors can suddenly see this kind of text and I feel forced to apologize or explain.
The screen has to reload continuously in version 2 (complete refresh). This is not needed in 1.x.

Is the button issue be solved in the 2.x version? If so, I’ll have to test it again… will try it now. Thank

Adrian_Rockall · March 23, 2025, 10:27am

I will check with 1.13.3 later today to see if I can replicate the issue.

Ranney · March 23, 2025, 10:41am

Thanks!!!

I see that the LED can indeed be controlled again in the 2.x software. (Though again the ‘both’ (front and wall side together does not work).
What I saw frequently in the 2.0 firmware (which makes me happy to stay with the 1.x) is this screen.

Torch1969 · March 23, 2025, 11:53am

For me the issue’s were solved in this combination of firmware and app version’s

Torch1969 · March 23, 2025, 11:54am

This is because of the default config connecting to the mqtt server of button+.

Adrian_Rockall · March 23, 2025, 1:05pm

As @Torch1969 says, that is the default configuration that just connects to the Button+ MQTT broker. Once the app takes over it completely overwrites that configuration and is completely local (unless you manually setup an external MQTT broker). I have access to the Button+ source code and I can assure you there is nothing dodgy in there. If you see that screen after setting it up in the Homey app, then there is likely something wrong as it is getting a factory reset.

I agree with you on point 3 and is my only dislike of the new version. However, some of that can be overcome by embracing the new paging feature of the buttons instead of switching configurations.

As for controlling the LED on row 4, I can’t reproduce that, but I can see that the Both option is not setting the wall LED, so I will fix that.

Adrian_Rockall · March 23, 2025, 1:19pm

New test version is now in the store that fixes the Both option.

Ranney · March 23, 2025, 1:21pm

Super thanks for your detailed reply and time!
Very strange that it works for you on the latest 1.x firmware. I have multiple button+ devices in use. If I connect the display to row 3 and the button bar to row 4 it works (I can set the right led to a color on row 4). However, if I engage all the rows I can’t get it to work. Could there be a problem in my button+ configuration perhaps? (Is it of value if I share it?)

Thanks for the feedback on the firmware by the way. Ideally I would just set it to ‘local’. So on wifi but no internet access. This is because homey does need to be able to access this device and and a lot of other devices so I have now introduced an additional ‘vulnerability’.

Anyway, just on 2.x for now. Hopefully not too many more of those like buttons.

Thanks for everyone’s time and have a great Sunday!

vikino · April 4, 2025, 9:15am

Hi all,
just got my Button+…all works fine, just…i havent found how to display actual time…? Thank you, Vitek

Adrian_Rockall · April 4, 2025, 9:22am

The device has date and time capabilities so just add that to the display, e.g. choose the Button + as the device and select the date/ time capability.

vikino · April 4, 2025, 9:29am

Got it Thank you

vikino · April 4, 2025, 9:42am

And got an idea how to control multiple Philips Hue lights with single button?
Thinking about creating flow or some light group…

Adrian_Rockall · April 4, 2025, 10:38am

You could do either. If you create a Flow, the trigger it with a button pressed event.

Topic		Replies	Views
Digital buttons in Homescreen from Homey App Questions & Help	3	806	September 11, 2018
Custom app UI for MQTT based app Developers	12	519	August 20, 2023
Bottoms, symbols e clicking Ideas & Suggestions	2	517	September 29, 2019
Button+: a new display/switch device Devices	71	8623	May 12, 2025
[APP][Pro] Home Assistant - Community App Apps app , tools , homey-pro , home-assistant	1340	30426	July 14, 2025

Button + (Release 0.7.17, Test 0.7.17)

Related topics