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


Firmware update 4.9 release notes


comfix

Recommended Posts

  • 4.9
  • Optimized battery life time.
  • Signalization of battery loading fault added - pulsating magenta color. In this case, the charger or cable should be replaced, as they may be damaged and do not provide a constant power supply.
  • Warning:
  • Update can take up to 30 minutes. It depends on Z-wave traffic,
  • If possible, locate the device in the close nearby (ca. 2m) of the Home Center to avoid failures,
  • Wait few minutes after successful update and check if version of device has changed,
  • The update use the Z-Wave network bandwidth to a large extend. It may result in delays in other network actions even several minutes after update.
  • In case of strange device behaviour there may be need of reconfiguration/reinclusion.
Link to comment
Share on other sites

  • Topic Author
  • What I miss is the option to see who adapted the temperature and if the valve is open or closed.

    I have the feeling that after some time it doesn’t close properly anymore and heating still gets warm.

    Link to comment
    Share on other sites

  • Topic Author
  • 11 hours ago, MacinZ said:
    • 4.9
    • Optimized battery life time.
    • Signalization of battery loading fault added - pulsating magenta color. In this case, the charger or cable should be replaced, as they may be damaged and do not provide a constant power supply.
    • Warning:
    • Update can take up to 30 minutes. It depends on Z-wave traffic,
    • If possible, locate the device in the close nearby (ca. 2m) of the Home Center to avoid failures,
    • Wait few minutes after successful update and check if version of device has changed,
    • The update use the Z-Wave network bandwidth to a large extend. It may result in delays in other network actions even several minutes after update.
    • In case of strange device behaviour there may be need of reconfiguration/reinclusion.

     

    It seems they have removed the update? Cannot update it anymore.

     

    Please login or register to see this attachment.

    Link to comment
    Share on other sites

  • Topic Author
  • 19 minutes ago, MacinZ said:

    Yep, lot of issues. Hopefully I didn't make this update yesterday, ufff

    Happy I did not update it yeterday evening... :)

    Link to comment
    Share on other sites

    The topic has been moved from "

    Please login or register to see this link.

    " to "

    Please login or register to see this link.

    ".

     

    Temat został przeniesiony z "

    Please login or register to see this link.

    " do "

    Please login or register to see this link.

    ".

    Link to comment
    Share on other sites

    Unfortunately, I was not so lucky and confirmed update - 2 of 6 bricked. It looks like it was "standard" FIBARO update as usual :-)

    Edited by vacpav
    Link to comment
    Share on other sites

    Same here. 2 dead, 2 OK and 2 left at 4.7...

     

     

    Edited by petergebruers
    • Like 1
    • Thanks 1
    Link to comment
    Share on other sites

    8 hours ago, petergebruers said:

    Same here. 2 dead, 2 OK and 2 left at 4.7...

     

     

    DNR

    Link to comment
    Share on other sites

    • 1 month later...
  • Topic Author
  • Here we go :)

     

     

    Please login or register to see this attachment.

    [16:16:43] ID xx: OK. The device will initiate the firmware update of the target specified in the meta data.
    [16:20:47] ID xx: New image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.
    [16:22:27] ID xx: OK. The device will initiate the firmware update of the target specified in the meta data.

    Edited by comfix
    Link to comment
    Share on other sites

  • Topic Author
  • [16:39:57] ID XX: New image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.

     SUCCESS 

     

    ?

    Edited by comfix
    Link to comment
    Share on other sites

    [17.01.2022] [16:50:56] [TRACE] [ZWAVE]: ID 487: OK. The device will initiate the firmware update of the target specified in the meta data.

    [17.01.2022] [16:58:10] [TRACE] [ZWAVE]: ID 487: New image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.

    [17.01.2022] [16:59:52] [TRACE] [ZWAVE]: ID 487: OK. The device will initiate the firmware update of the target specified in the meta data.

    [17.01.2022] [17:01:44] [TRACE] [ZWAVE]: ID 487: An error occured. RGBW program writing will not start

    [17.01.2022] [17:03:44] [TRACE] [ZWAVE]: ID 487: The device was unable to receive the requested firmware data.

    Edited by danidani
    Link to comment
    Share on other sites

  • Topic Author
  • 7 minutes ago, danidani said:

    [17.01.2022] [16:50:56] [TRACE] [ZWAVE]: ID 487: OK. The device will initiate the firmware update of the target specified in the meta data.

    [17.01.2022] [16:58:10] [TRACE] [ZWAVE]: ID 487: New image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.

    [17.01.2022] [16:59:52] [TRACE] [ZWAVE]: ID 487: OK. The device will initiate the firmware update of the target specified in the meta data.

    [17.01.2022] [17:01:44] [TRACE] [ZWAVE]: ID 487: An error occured. RGBW program writing will not start

    [17.01.2022] [17:03:44] [TRACE] [ZWAVE]: ID 487: The device was unable to receive the requested firmware data.

    Same here:

     

    [16:46:34] ID 116: OK. The device will initiate the firmware update of the target specified in the meta data.
    [16:50:57] ID 116: New image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.
    [16:52:37] ID 116: OK. The device will initiate the firmware update of the target specified in the meta data.
    [17:03:34] ID 116: New image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.
    [17:05:16] ID 116: OK. The device will initiate the firmware update of the target specified in the meta data.
    [17:05:16] ID 116: An error occured. RGBW program writing will not start
    [17:06:12] ID 116: Application rejected request

     

    Try again and if still fails take it near my controller.

    Link to comment
    Share on other sites

    Same for me after I moved the device in the close nearby (ca. 2m) of the Home Center. I am going to test it now.

     

    I took 23 minutes to update it.

    Edited by danidani
    Link to comment
    Share on other sites

    19 godzin temu, danidani napisał:

    [17.01.2022] [16:50:56] [TRACE] [ZWAVE]: ID 487: OK. The device will initiate the firmware update of the target specified in the meta data.

    [17.01.2022] [16:58:10] [TRACE] [ZWAVE]: ID 487: New image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.

    [17.01.2022] [16:59:52] [TRACE] [ZWAVE]: ID 487: OK. The device will initiate the firmware update of the target specified in the meta data.

    [17.01.2022] [17:01:44] [TRACE] [ZWAVE]: ID 487: An error occured. RGBW program writing will not start

    [17.01.2022] [17:03:44] [TRACE] [ZWAVE]: ID 487: The device was unable to receive the requested firmware data.

     

    same here. RGBW device? @K.Drozynski?

    Link to comment
    Share on other sites

    16/16 successfully updated.

     

    22 hours ago, danidani said:

    Same for me after I moved the device in the close nearby (ca. 2m) of the Home Center

     

    Link to comment
    Share on other sites

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