I would be interested to know why you have given up with it so i know if I can improve things.
@Adrian_Rockall, test 7.11 i introduced a non working buttonbar on fw2, but only on my newer configurations.
You’e got mail ;-). I sent you an working configuration to check against the previously one you got (with some additional info).
I can’t activate flows anymore with button’s, only direct commando’s are working
sent a log file when pushing the button where a flow is connected
V0.7.11 / FW 2.0
Seems like page functionality is broken for me.
No working buttons if assigned to a page. Button config on default page (0) works.
2025-01-26T11:37:53.350Z triggerFlow (config_button_change) Error: Could not trigger Flow card with id “config_button_change”: Invalid value for token page. Expected number but got undefined
I have published a new test version. Hopefully this one will work.
Thx! Page-buttons are working with v0.7.12 
1 Like
New test version fixes an issue with buttons defined on the ‘Default’ page.
1 Like
Hi @Adrian_Rockall,
Until know the updates did’t break my old configuration (running on button+ with firmware 1.13), but as off this new app test version 0.7.13 the button connector #4 cannot be configured. Not with reapplying of config and not with assigning a button configuration to that connector. It just shows “Label” with “Btn 6” and “Btn 7” (btw strange numbering shouldn’t that be 5&6 or 7&8?).
Anything I should do or can help with (send log’s)?
On me, the buttons no longer work as they should either.
Everything always worked until update 0.7.x and
Firmware was always 1.13
Now the flows referring to a button and to an action no longer work? Directly controlling a device via the buttons does work.
Button + updated to firmware version 2.0, but this does not work either.
Could you send me your configuration.
The buttons are numbered from 0 at the top left. So, the sequence is:
0 - 1
2 - 3
4 - 5
6 - 7
Those labels are the defaults from the firmware, so it looks like the configuration for the last row hasn’t been applied.
I’m still running one of each firmware in my test setup and I apply the same configuration to both, except row 4. I send config 3 to row 4 on the old firmware, which just has the old default page setup and config 5 to row 4 on the new firmware, which has 3 pages defined. Both are still working for me.
Edit:
Just out of interest, have you viewed and saved the configurations in the app settings of the new version?
The new config format has the ‘PageNum’ entry in the button configuration and that is added when the app settings are saved. I have just notice I hadn’t added that ‘upgrade’ to my app init function, so maybe it is missing and causing an exception when it is checked. I’m trying to figure out how I can test that theory on my configurations as they have all been updated.
2 Likes
I have replied to the diagnostic report, but just in case you don’t get that, it seems your Button + is offline as it is not reachable from the app.
Thanks and received it!
No idea what is going wrong. I can just reach the button+ (on ip address) and it also has a fixed ip address. App reboot, button+ reboot, nothing helped. To my surprise after a reboot of homey it suddenly did it again.
Fingers crossed that it continues to work!
Thanks again for your time and great work!
It was with “old” saved configurations. But because of your remark I did save the configurations again and re-applied (also after restart of app). But behaviour is the same. I can assign all defined button configurations to connector 2 and 3, but none to connector 4 (it’s not shown).
Debug log: e65da669-817e-40b8-b9a1-a6c0a070f101
Works again here! thank you very much. Will send you a beer/coffee for al the work your doing!
Hi, can someone explain what “page number” means in the flow card?
I updated from 0.60 and now some stuff isn’t working well anymore 
normally when I press connector left / right page 1. I get other configuration on my B+. That is still working also the buttons/action behind this button. But the label text disappeared after a few sec. After the press … when I press/test the card in the homey congratulation the label text stays in the screen. So no idea what the difference is now, and howto fix it.
The page number relates to the new page features of the version 2 firmware. If you haven’t updated the button + firmware then just use page 0.
I must confess I don’t quite understand what you are saying is happening, sorry.
Could you share your Flows?
With me, everything works again as it should.
After updating all button+ to firmware version 2.0 and the latest software version, I resaved all programmed buttons and uploaded them to the button+, which resulted in everything working properly.
Thanks Adrian for all the effort
1 Like
At first, thank you for the great work on this app.
FW 2.0.0, App: 0.7.14
I try to switch a yes/no variable but that is not working. When I push the button the Led turns on, the label changes to On but the variable does not change. When pressing the button again nothing changes, the led stays on and the label stays at on. When I change the variable manual from no to yes nothing hapens but after that any manual changing toggles led and label.
I don’t think this has anything to do with this problem, but when I go to the web page and click on button 8 (right connector 4) I get a warning that there are multiple configurations found for position 8 page 0.
Unfortunately, Athom doesn’t allow apps to alter variables, so they are read only. Therefore you will need to define a Flow with a trigger from the button pressed that toggles the variable.
Great Scott!! I think I’ve the same problem! I use also variables to change my label text in de B+, but nothing changes!
