Button + (Release 0.5.5, Test 0.5.9)

[Alexander_Adam1]

This is the picture of the device

[Torch1969]

@Alexander_Adam1

I’ve also notice when I have German umlauts e.g. in the information field, they are not shown correctly on the device but are correct in the web-app.

Add your request’s for special characters on button plus site at issue #71, Ronald will add them.

[Torch1969]

@Alexander_Adam1

The label is shown in the web-app of the device but it is empty on the device. I was not able to set any label so far via your app.

Toplabels show up after restart of device (short press on button right of usb-connector)

[Alexander_Adam1]

Gotcha, thank you.

[Adrian_Rockall]

@Alexander_Adam1

2nd question/enhancement : is it somehow possbile to show different LED color for On and Off state ?
E.g. green when the garage is locked and red when it is open ?

The device doesn’t support that, so can you add a request in the same place as @Torch1969 mentioned above.

@Alexander_Adam1

and a 3rd cosmetic one. Is it possible to set the Alignment of the fields in the display config via the App?

The display doesn’t support the alignment options. The web interface still shows them from an earlier firmware version, but the core was changed.

[Torch1969]

@Adrian_Rockall

Have you tried to factory reset the panel?

Thx, factory reset was enough to bring the device back to live. It even wasn’t necessary to remove and re-add the device in homey, the device picked up the configuration as if nothing happened

But my ip config page an device itself is still empty

[Adrian_Rockall]

@Torch1969

But my ip config page an device itself is still empty

Could you show a screenshot of that page so I can see what you mean?

[Cor_De_Rooij]

@Adrian_Rockall Is it possilbe what I want to do her: change the button and labels based on another button?

Button + (Release 0.2.7, Test 0.3.0)

Hi Adrian, The update is working much better, thanks for that. I have now configured my first complete use-case, the idea was to switch to another usage with the right display button and which that switch to different button configurations. Now I have the problem that this seems to work, but the Button+ is not updating the buttons. But the functions are changing in the background. → this was because a flow was activating the blinds as well, so you can forget that last part. [Screenshot 2024…

[Torch1969]

@Adrian_Rockall

Could you show a screenshot of that page so I can see what you mean?

This is the device in “bricked” mode:

After factory reset I can reach config page on ip-address
After resending configuration from homey app, the device looks ok, but config page on ip-address looks like this:

After a while the device is stuck again.
Only strange thing I can see is an incorrect toplabel on one of the buttons. The toplabel shows the label instead of “Zijraam” (like button on right for “Voorraam”).

This started when configuring the buttons on the fouth connector. From that moment on the trouble started. Even if I set a different button bar configuration. All labels are changed, but toplabel of connector 2 stays on “Open”.
Should I send you something? Diagnostic report? Button bar config?

On ip/config is see that this faulty button has the wrong toplabel:
{“id”:4,“label”:“Closed”,“toplabel”:“Open”,“ledcolorfront”:16711680,“ledcolorwall”:16711680,“longdelay”:75,“longrepeat”:15,“topics”:
Also in Mqtt explorer is see this button (with id 4) is the only one getting a topic for the toplabel (with value “Open”).
(Even after changing the label value’s of that button to something else this faulty toplabel value is hanging around somewhere and messing up my configuration…).

Edit, when powering off, the device is “bricked” again. I discovered that sending configuration to device is enough to bring it back alive. Still the faulty “toplabel” is back. Strange thing when restarting or when changing button configuration, first the labels are wrong (wrong value), but toplables are ok. After 1-2 seconds the labels are correct, but this faulty toplabel is back again. This behaviour is for all buttons of device type " App button" .

9be43abe-172a-4756-8b19-2556afe1d387

[Remy]

Can someone tell me how secure the mqtt broker is in Homey? Is the broker completely local, or send it also some information to mqtt.button.plus? On the tweakers forum someone mentioned that the temperature value send to that broker. But don’t know if that’s also the case with the default broker in homey. I’m not that technical with mqtt brokers

[Adrian_Rockall]

If you set Homey as the Default broker in the Homey app Configuration page, then everything is local. You can even define a username and password to secure it further it you want.

[Adrian_Rockall]

If you setup a Flow that triggers when the button is pressed, you can then send a new configuration to the connector.
In the test version you can also set the trigger to happen when a button is pressed for a specific configuration. For example:

[Adrian_Rockall]

@Alexander_Adam1

The label is shown in the web-app of the device but it is empty on the device.

This is a Button + issue, but I have fixed it and submitted the pull request to Ronald so hopefully he will include it in the next update.

[Torch1969]

@Torch1969

All labels are changed, but toplabel of connector 2 stays on “Open”.
Should I send you something? Diagnostic report? Button bar config?

On ip/config is see that this faulty button has the wrong toplabel:
{“id”:4,“label”:“Closed”,“toplabel”:“Open”,“ledcolorfront”:16711680,“ledcolorwall”:16711680,“longdelay”:75,“longrepeat”:15,“topics”:
Also in Mqtt explorer is see this button (with id 4) is the only one getting a topic for the toplabel (with value “Open”).
(Even after changing the label value’s of that button to something else this faulty toplabel value is hanging around somewhere and messing up my configuration…).

I solved this problem. Somehow this label was send to device through mqtt. There it was a retained item on topic button_12345/button/4. So every time the config of the device was reset or changed, this retained item was picked up again. I removed this item with MQTT explorer and this problem is solved.

[Cor_De_Rooij]

But this is also what i have tried, see screenshot, but the button configuration is not changing on the Button+

[Adrian_Rockall]

It seems I have overlooked the need to remove items that are deselected from configurations.
I have set the items to be retained as the Button + doesn’t update the value stored in the configuration when the MQTT value is changed. Therefore, when the Button + is reset it wouldn’t know the state of the latest update if they weren’t retained.
If you use the Homey broker then it resets when the app restarts, so I hadn’t noticed stale items. However, when the app runs for a long time (doesn’t happen much when I’m debugging / adding things) or using an external broker then it becomes noticeable.

I will endeavour to address that issue ASAP.

[Adrian_Rockall]

I don’t see a screen shot

[Cor_De_Rooij]

Sorry, but I meant the screenshot form my original post.

What I want to do her is when with a button on the display is clicked you choose the next display configuration (now only 1 and 2) and based on the button configuration should change
When first screen (in my case lights)

when second screen (in my case Luxaflex)

By testing this flow it “works” but doesn’t make the expected changes on my Button+

@Adrian_Rockall Do you any idea why this not working by me?

[TKroon]

Hi all! I received my Button+ last week, and I’m very happy with it! I created two display pages, which are switching nicely on a button press.

I’m stuck on one thing though:
On the middle bar, I’m trying to display the current state of the washing machine (like personal text sent by Homey). However, it seems I can only display a label for the ON-state, and one for the OFF-state.

The Homey flow card does succeed, but no change is visible on the device.

Edit: Homey app 0.3.1, button+ 1.07

[Adrian_Rockall]

@TKroon

On the middle bar, I’m trying to display the current state of the washing machine (like personal text sent by Homey). However, it seems I can only display a label for the ON-state, and one for the OFF-state.

I have added a Flow action card to set the button text in the next version.