Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted

What is the best way to upgrade from 3.600 to the 4.070? There is a warning stating that the system can become unresponsive when upgrading from 3.600

 

Regards

 

Posted

Check out this post I made and pre-cautionary measures I adopted. 

 

Please login or register to see this link.

 

That said, v3.600 to v4.070 is a huge leap and there are definitely plentiful of conversion in the background that needs to take place. Furthermore, there will always be a risk that something may break. Here is what I will do if I am in your position and I cannot guarantee there won't be breakage but at least, it minimises the risk/chance of something major breaks.

  1. Schedule a change window of at least 2 hours or more where there will be minimal impact to your household (e.g. when no one else will be around so no one will nag at you or shout at you for something not working),
  2. Perform a configuration backup,
  3. Disable every single scene (uncheck the option 'Active Scene', not just stopping the scenes),
  4. Reboot HC2 (logic: flush out non-visible stuffs such as abnormalities, cache, hung processor threads, etc),
  5. Sanity Check for 5-15 minutes (logic: reboot usually boots up fine but just in case of unforeseeable abnormal behaviour),
  6. Proceed to firmware update,
  7. Clear web browser cache,
  8. Terminate web browser,
  9. Relaunch web browser,
  10. Repeat step 5-7 if firmware update still in progress,
  11. Patience, Plentiful of Patience,
  12. Change freeze for 1 or more hours even after web GUI becomes accessible and even if there are some devices which appear abnormal
    (logic: allows non-visible backend scripts/processes to complete any conversions, system changes, etc that the new firmware has to perform),
  13. Enable scenes one-by-one and observe its functionality, CPU and Memory utilisation, abnormalities if any.
    (logic: most of the potential problems come from badly coded scenes of the past and not properly converted which may result in looping or consuming system resources until slow or hung)

Just chipping in the best I can think of. I cannot stress how much risk this may be and do set your expectations right that something will most likely break.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...