Can’t think of any @Adrian_Rockall…
Looks already amazing!
Last version firmware, Button+ v2, display and 3 bars.
@Adrian_Rockall: Thank you for the great work!
Showing display and even more the button configurations without Configuration Names is a pain to work with as you already mentioned.
I haven’t been able to work with more than 1 page. Using the Button+ configuration page for that messes with button ids but gives you the possibility to use more pages. Then going back to this app doesn’t really work however.
Did I miss something? I gave up on it for now. Stuck to one page now.
For changing volume it would be great to be able to add 2 devices to 1 button, for both of the labels ON STATUS and OFF STATUS. E.g. 1 volume up and 1 volume down with a “toggle functionality” or a “hold functionality”, not sure how to cal this. I think this needs to be implemented on firmware level?
Thanks, Richard
When using the panels with Homey, it is best to keep away from the Button+ html interface. Instead use the Homey app settings page to define all the pages.
I must confess I don’t understand what you mean.
When using the panels with Homey, it is best to keep away from the Button+ html interface. Instead use the Homey app settings page to define all the pages.
I’m looking for a simple way to use one button for volume up and volume down. I have a device that only knows these actions seprately.
There are labels for “On status” of the button and “Off status” of the button, but these are linked to a single device that toggles between on and off. However, if the functionality were to switch and a long-press action were used, holding the button down could increase the volume, while a subsequent long press (after releasing it) could decrease the volume.
I hope this cleares things up?
There is a new test version of the app with both the button and display simulators in the app settings.
Plus it fixes a few other bugs I found.
Hello Homers!
I installed the Button+ app and added a spanking new Button+ V2 to Homey. One with a display and 3 button bars.
From the onset, there was no temperature nor ‘info’ erm… info (whatever that is supposed to show). (See screenshot) It seems like Homey doesn’t receive this from the device.
When I chose temperature as status indicator it remains empty, also, when I then try to put the temperature measurement on the Button+ display itself (configuration), it remains empty on the screen too.
I did put the time on the display successfully, I assumed it would work the same way with the temperature so I am quite sure I have at least (already) mastered putting an item on the display. 
Is this temperature (and info) missing in Homey something known to anyone and is there a way of determining whether my device is not working correctly or if it’s an app problem? Or both?
Anyway, appreciate suggestions!
Thank you!
V3 firmware changed the format of the temperature reporting. The new test version of the Homey app is now compatible.
The Info is a way to show a notification on the screen. You insert the capability as a display item and then you can set the text via a Flow. There are other ways to accomplish this now, but it was an early method.
Thank you Adrian! I am reassured about the temperature issue. All will be well when the new version becomes active in my Homey!
Your elaboration of the Info data made me really happy! I’ll be able to send a message to the display and it will appear on the Button +. Excellent.This is basically GREAT!
I tested it and it’s a great feature. THANKS!
Thanks thanks thanks, Eric
Thank you for this suggestion to flow around the issue with flows! 
I will try this one.
The multi page issue is caused the fact that this app takes a different approach compared to the Button+ interface. You really should avoid that interface when using the Homey app.
Thanks for the help!
If you want to try the test version just find the app in the Homey store, add test to the end of the URL and then install it over the top of your existing version.
When I first created the Homey app, the Button+ didn’t support pages so I provided that via the option to switch configurations. Also, the v1 Button+ firmware didn’t do a complete reset when new configurations were uploaded like it does now, so it was very smooth. I still prefer that old way as it meant the Button+ didn’t hit memory limits and was more flexible, but HA users led the way to where we are now. But due to the full reset when a configuration changes, I then adapted the Homey app to work with Button+ pages. Unfortunately, that also made the app configuration page more complex as it was added to an existing interface rather than being designed with multiple pages from the start. My goal is to completely redesign the app settings in the future to make it easier and the new simulators are the first step towards that. My professional skills are in C and C++, so HTML / CSS is still relatively new to me, with most of my experience being with Homey, so I am still learning to get beyond the basics, especially with the power of CSS.
I totally agree. I tried to make the Homey app self contained and as much as possible to be plug-n-play. I considered having to setup MQTT topics in the Button+ interface and making Homey publish the correct information to the correct place too complex for a lot of the Homey users. Therefore, the Homey app basically takes control of the Button+ and does all the behind the scenes bit for you. You just tell it what you want display and where and the app works out how to do it. Unfortunately, the simplicity of the Homey interface can also make it more complicated to do things that don’t fit the normal Homey way.
Thanks! I did, and the temperature is now visible everywhere. Tested also the calibration (maybe not relevant but I tend to do so everywhere) and that worked too. GREAT!
Just to let you know Adrian… after a lot of tinkering I managed to get a button to work…(I didn’t know/realise you had to activate the configuration on the device settings first!) but when pressing it (on/off) the test version of the app crashes. It’s not a complaint because I know it’s a test version… but I thought you should know. It seems you are doing a LOT of work on this app for everybody! Which will make Homey really beautifully controllable with the Button+. Thank you!
I have published a new test version.
The app settings for the buttons and the display are now simulator driven.
Click / tap on the items to open a popup to edit them.
The items on the display sim can be selected with one click and then size by dragging the right border or moved by dragging the top border. Click a second time to open the properties editor.
The device list now shows the device icon and the capabilities list show the capability icons to make it easier to find things.
Oh, this is beautiful. So much easier that the old really long list and scrolling up and down.
Thank you for your great work Adrian.
I just received my Button+ V2 (3.1.6-V2) this morning and started to play around with it. Lots to learn and not a lot of information to find so far.
I’ve downloaded the test version and wanted to put items on the screen. But when I press save I get
Can someone point me in the right direction to fix this? Many thanks.
I have published a new test version with some extra checks built in.
I couldn’t reproduce the error, so I not sure if I have caught it, so if you still have problems can you capture the console output. E.g. Open Homey in the web browser https://my.homey.app/ and the open the settings page and repeat the same steps. If the problem happens there, press Ctrl + Shift + i to open the debugger. Then select the Console tab in the lower part of the screen and right click on a line to popup a menu. Select the Copy console command and then paste them in to the reply.
Thanks Adrian for more improvements!
Quick feedback on what I found (7.35)
- switching the top buttons (I have 3) on/off keeps crashing the app as previous. I have defined a button on the 2nd row now, which works, and that one does not cause a crash.
- at some point, can’t reproduce, some of the text assigned to the top buttons appeared in the display and screwed up what is there (time/temperature etc).
Am I understanding rightly that to program/define the 1st, 2nd and 3rd row of buttons I need to assign a configuration to each? That kind of seems to make sense… yet I had a completely different mind map of what configurations were for. Still have to make sense of the pages in that context too. It almost feels like playing multi-dimensional chess.
Right. Still. Great stuff!
I have no crash reports in the developer console so I’m not sure where to look. What exactly happens with the app?
Could you Export the configuration and send it to via a PM so I can try and simulate it?
Correct. A button configuration defines all the parameters for one row of buttons, including the pages that are cycled through with the display panels left and right buttons. That is the way the Button+ works.
So that allows you to assign the same configuration to multiple Button+ units.
Maybe not quite that complicated, more like multi-dimensional chequers
