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 (edited)

Few months ago, after release of FW 3.3 for Window/Door sensors I got stuck being unable to update 28 of my sensors in FGDW-002 version.
With the release of HC 5.170 and information about

Cytat

Support for FGDW-002 in version 3.3 added.


I was hoping I will be able to get huge list of devices solved finally. Ufortunately that's not the case. There's however a difference in the experience. Previously clicking on update was resulting in whole Z-Wave being very busy and unresponsive. And update resulting with an error right after clicking the update the button.

With new HC firmware, the experience is that it tries to update the software - it goes from 0% to 100%. Meanwhile the z-wave is very laggy again (up to couple of minutes to react to opening doors etc). After hitting 100% device disappear from the list and reappear after few minutes, and HC remains laggy.

Please verify this information. To me, release of 5.170.13 did not improve the situation.

Edited by irekk
Posted

Did you made an re-interview (reconfiguration) after the update? 

  • Topic Author
  • Posted (edited)

    I did read configuration - which helped for most of the devices (only a few updated without any problems)
    I did soft reconfiguration for remaining few devices - it helped for some, except for one
    I did hard reconfiguration for the remaining, which eventually shows v3.3 now but it still shows up on the update list and awaits for communication (I did reconfiguration though). (Device keeps the ID!)

    But what I still struggle with, is that updating devices completely shuts down scenes based on door/window sensors but also motion sensors. It requires to restart the controller. For example when I walk through a corridor, motion sensor lights up the lightning 10-15 mins later. Even if there's no device updates. It seems to be related to that one faulty device. Everything is fine until controller will not show the waiting for communication message.

     

     

    Please login or register to see this attachment.

    Edited by irekk
  • Topic Author
  • Posted

    OK, after I managed to reduce number of devices for update to ~10, the HC and the update process become reliable. No lags, no need to read configuration. It looks like 30+ devices is an overkill for the software.

    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...