Home Center Firmware Update Process

[chaicka 195]

Hi Fibaro,

 

For many firmware updates since the journey of version 4.x, I have started practicing a process (posted in a few HC2 version threads) which minimise risk of something going wrong. One of the steps in the process is to restart the HC2 prior to any firmware update so as to flush out abnormalities such as caching, hung processor thread, dead z-wave command in queue, etc.

 

I have practiced this 'restart device' step on QNAP NAS (testing betas and official releases) for several years. And QNAP finally adopted it and added mechanism to remind or recommend to restart NAS if it has been up and running for too many days. Below is the warning/recommendation pop-up whenever attempting to update new firmware if the NAS has been running for a long time. I am not exactly sure how many days do QNAP consider as long running time.

 

Please login or register to see this attachment.

 

I would sincerely suggest that Fibaro give it some thought.

[Mr Jack 10]

Hi Fibaro,

 

For many firmware updates since the journey of version 4.x, I have started practicing a process (posted in a few HC2 version threads) which minimise risk of something going wrong. One of the steps in the process is to restart the HC2 prior to any firmware update so as to flush out abnormalities such as caching, hung processor thread, dead z-wave command in queue, etc.

 

I have practiced this 'restart device' step on QNAP NAS (testing betas and official releases) for several years. And QNAP finally adopted it and added mechanism to remind or recommend to restart NAS if it has been up and running for too many days. Below is the warning/recommendation pop-up whenever attempting to update new firmware if the NAS has been running for a long time. I am not exactly sure how many days do QNAP consider as long running time.

 

Please login or register to see this image.

/public/style_images/master/attachicon.gif" alt="attachicon.gif" />

Please login or register to see this link.

 

I would sincerely suggest that Fibaro give it some thought.

Good suggestion for all of us. Thanks

[T.Konopka 8]

Hi Fibaro,

 

For many firmware updates since the journey of version 4.x, I have started practicing a process (posted in a few HC2 version threads) which minimise risk of something going wrong. One of the steps in the process is to restart the HC2 prior to any firmware update so as to flush out abnormalities such as caching, hung processor thread, dead z-wave command in queue, etc.

 

I have practiced this 'restart device' step on QNAP NAS (testing betas and official releases) for several years. And QNAP finally adopted it and added mechanism to remind or recommend to restart NAS if it has been up and running for too many days. Below is the warning/recommendation pop-up whenever attempting to update new firmware if the NAS has been running for a long time. I am not exactly sure how many days do QNAP consider as long running time.

 

Please login or register to see this image.

/public/style_images/master/attachicon.gif" alt="attachicon.gif">

Please login or register to see this link.

 

I would sincerely suggest that Fibaro give it some thought.

 

Hello,

 

Thank you for this suggestion. I am forwarding it to the appropriate team

[chaicka 195]

Bump...

 

How is the response from appropriate team?

[chaicka 195]

Bump...