Button + (Release 0.7.21, Test 0.7.22)

Hi @Adrian_Rockall

I‘ve tried to update. It seems they have also change again something in the configuration because it reconfiguration with app was ok but was not working correct. I didn‘t see the configured buttons. Only for your information, I reloaded 2.0.1.

I have just updated one of my panels to V3 and it also doesn’t work. I see no errors when sending the config and even if I export the config from the app and import it via the Button+ web page it doesn’t work.
So I have messaged Ronald to get some help.

3 Likes

FYI: I have updated the Button Plus to 3.0beta6 and currently it is working. I will inform you if it is not running after a while

Good. I have been feeding back to Ronald and he has been fixing, so hopefully it should be all working.

Any news on the app in combination with the new v3 firmware, @Adrian_Rockall?

According to the latest newslette/blog Ronald sent out today, the new firmware is only days away.

Would it still be wise to wait a little before updating, or have thing been improved yet?

The app is working with version 3 beta 3. I haven’t tried the latest one yet though.

My buttons are working fine with v3 beta8

1 Like

Great! Thanks for the response

Hi all. I’ve read through this whole thread, but couldn’t find my current error. I’m reinstalling my Button+ after a few months and a new Wifi network. Button+ connects with the network, but I can’t get it to add to Homey as a device; it gives an error message in red: ‘Error: Missing Parameter: device.data; Probeer opnieuw.’
Button+ is on fw2.0, Homey Pro, Button app v0.7.24
Few months ago this process was super smooth.. :man_shrugging:

Firmware 3.0 stable is out.
Upgrade went without problems - but headings are now blue in the display and yellow on the buttons…

Here also:

Firmware 3.0 on button+ works here without a problem with Homey.

1 Like

Firmware v3.0.1 (also tried v3.0.0) was no success here…

The text on some buttons is misaligned or even absent after sending the same configuration I used before on v2.0.1.:slightly_frowning_face:

When re-installing v2.0.1 firmware again, everything is working as expected again…