The display reset is part of the new firmware whenever a new configuration is uploaded. I gusess that’s because the button structure hass to be recreated to allow for multiple pages.
I have reported the issue of some display items not appearing to Ronald as they are being sent as far as I can see.
ooh okay, yeah i understand you always have to make something of it when they shoot another firmware in buttonplus haha. thanks for that!
and the display buttons? from the flow they do work and if i use the flow card: ‘if button right on connector 1 is turned on’ also works however the hardware button on the buttonplus itself does not work. all the buttons below it do work, so both buttons on the display itself do not.
is this software thing or should i report this to Ronald? looks like same problem as
I will look into that one. It could be that Ronald has dedicated them as page buttons, but I thought they had MQTT topic events applied.
sends you a PM with video for more info, maybe to make it more clear
Okay, doesn’t deserve the beauty prize as far as I’m concerned. perhaps I don’t see the point of having even more pages in the already existing 20 confugurable pages on the screen.
i find it a pity that there is now a light show on the buttonplus every time something changes on the screen. this looked much more peaceful before
i also don’t understand how it works with the pages haha but that’s probably just me, earlier you simply created a page as configuration but now you can do extra pages? however, i can’t click or change them in the configuration they stay on default, i can in the buttons, but when i try that my whole buttonplus is upset and i get to see things that have absolutely nothing to do with my modification, for example a totally different configuration or sometimes nothing at all.
i can’t go back to the simplified firmware, can i? then the homey app doesn’t support it right?
@Adrian_Rockall , i don’t use pages yet since i solved it with differtent configurations. I am also not sure if i understand the use of pages.
Is it designed to create multiple items within one configuration and assign them to a specific page so you can set the active page?
If that’s the case i will transform my multiple configurations to multiple pages in one cinfiguration. Especially if this means that it solves the (fw 2.0) initialization phase when change the items on the screen.
The pages are added in the new button configuration settings, so yes, one configuration can now have multiple pages of buttons.
The only strange bit is the display and button pages are linked, so selecting page one, two, three, etc applies to both the screen and all the bars. Therefore, if you have more pages in one section than another, at some point, either the display or button bars will be empty.
You can specify that an item is displayed on every page though and it will be shown regardless of which page is active.
thanks for the explanation, can’t really say I understand it all yet haha
all the buttons already had multiple configurations too right? No offence, but what value does this update add?
if you wanted a certain screen configuration to show something different on the buttons you could set that first via with its own configuration and then via flows. so you can switch between button and display configs when you want in my opinion.
So now you can have multiple total bar configurations with 1 display configuration but they are linked so you might have an empty field sometimes?
The display’s right button not working is not solved in 0.7.9?
I think this is the same problem as I and kringloper said. Adrian is going to look at this, see below
Hey Guys,
I’m struggling with the following idea:
I have set in Homey to show the current Time as per Button Plus MQTT.
Now I would also like to push the Date. In order so save space I wanted to replace the current fixed label (Uhrzeit): with a dynamic label
How do I set todays date as a dynamic Label in the homey Config?
Additionally can I set the time also incl. Seconds?
Thanks for the help
Daniel
Possibly use a Flow card to set the top label once per day and use the date tag from the device as the label text?
First of all, i feel a little sorry for you. New firmware versions of button+ seems to influence your Homey implementation a lot. I think your solution to support multiple configurations has worked out well, without the pages functionality. I also think that Homey users are a little spoiled to heave the option to create lots of different configurations, since button+ only has one. So, i understand why the pages option is added bij Ronald.
On my B+ on FW 2.0/Test 0.7.9 and a configuration with multiple pages (both display and buttons) i experienced the following (but i don’t know if it’s caused bij de FW2 or by the Homey app implementation)
If you need some specific tests to check for you. I have two B+ devices, one on the previous firmware and one on the newer. I also have a test for switching between configurations and switching between pages.
I’ve been reading through most of the posts after version 0.5.x and to be honest, I lost track on how to configure my Button+'s (I have 3).
Maybe when the first public release for the v2 firmware is out, someone can make a short YouTube (or other) movie on how to set it up? I think that would be highly appreciated, at least by me.
Significant improvements here. Thanks and it seems to me that creating a Homey app for the Button+ is one of the more challenging tasks.
Regarding my reported error: As still wasn’t able to update the button labels with test version 0.7.9 I checked the flows and I noticed that the flow cards for setting the button label was still the old one without the page option. After deleting the flow card and adding it again, this time with the option to define the page, the label was updated without an error.
The migration from the old flow cards, without a page defined to the new ones, which require a page to be defined, seems not to work in every case. 
Hmm, I did test that and it worked for me. I add the page as an optional parameter and if it wasn’t defined it assumed it was page 0. I checked that my original test Flow picked up the page parameter and set it to undefined, so I haven’t had to replace any cards so far.
Maybe there is a difference when installing the app via the CLI and via the store.
Sounds like a great idea. Maybe there will a volunteer as I haven’t mastered that skill yet, being an old fart 
But, maybe when I get time I will learn how to do that.
@Kringloper Thanks for the list, I will look into those as soon as I can, but my wife had her first chemo today and it has wiped her out, so I will be a bit busy with domestic stuff.
I’m a relatively old fart as well so I would happily consume but I hope someone else will pick up the gauntlet 
@Adrian_Rockall Do you have a plan when the new version with support for v2 will be released?
family is more important than anything else. I wish you both better times
Once the issue are no longer reported. It was quite a large change to the code so I don’t want to rush it and end up being overwhelmed by hundreds of users complaining 
No worries and no hurries, especially with your home situation. Take care of the important things first. We’ll see it when it’s ready.
