You will never get a guarantee that updating wont break anything.
but the update from 1.5.3 (from 18 Sep 2017) to 1.5.12 as latest Stable should normal give no issues and bring a lot of Fixes and good.
Updating the App depends on the developer.
If it is the same App you installed using CLI that was once first in the store it could update without problems.
I don’t see Issues in the version History that you should re-pair so try it…
Installing from Store OVER the CLI installed version will keep all devices and Settings (and they function if the new devices still match the old one’s)
For New capabilities on existing devices You often have to remove and repair.
WARNING:
If you remove the App or downgrade / upgrade from:
Alpha to a Beta or Stable
Beta to a Stable All devices and settings are removed
Installed Aeotec beta 2.0 from store, that overwrote old CLI installed app.
Then I pressed install 1.5.12, waited to download 245.4 MB and BOOM!
dark screen, please wait do not turn off the power said homey
waited, some purple light rolling
after few long minutes, maybe more than 5
then looong yellow light but all went well
new FW new Aeotec app
me happy
all good
I have a lot of fibaro devices
should I go with beta fibaro app?
As Dijker mentioned, once you go to beta, to go back to ‘stable’ you will need to remove all your devices and re-add them. This can be particular painful with Fibaro in-wall switches and dimmers.
As someone who is currently running the Fibaro beta, (which is very good) I would just wait it to become stable and you will automatically get updated. Unless you are having issues with Fibaro already.
well … fast forward … updating homey fw made me a lot of anoying problems …
never had anyproblems before on old fw
now … flows are not executed on some devices … when using mobile app for devices I have to press few or many times to get something working … most of my devices are fibaro …
something is not good …
and now, while I am thinking/writing this, it comes to mind that those devices not working are using neo devices in route/path … hmmm maybe that could be … I will try to turn off all neo power plugs