Failures updating Firmware from 3.2 to 3.3

[Dave C 0]

Is anyone having issues updating the firmware on their Door/Window sensor 2's?

Home Centre seems to sit there waiting for connection and when I initiate connection it fails to update.

Is there something I need to do for the firmware to update?

[VascoFilipe 11]

I've updated successfully, although it only worked on the second time...

[SmartHomeEddy 1,005]

It takes some time, but it works. Full battery, hopefully nearby the HC3, etc. 

 

@Dave C You don’t happen to have the devices secure included? 

[Fabir 73]

@Dave C Hello and welcome to the community.

All the above I did. Also I had to exclude / Include the door sensor from the hc.

[Neo Andersson 230]

I falied to update too, and unfortunatelly the device is in a  remote place where it is really hard to uninstall from, so for me it sucks..:-)

[Dave C 0]

On 8/17/2024 at 1:34 AM, SmartHomeEddy said:

You don’t happen to have the devices secure included? 

I think they are.  Is there a special process to update them if they are Security Enabled?

[SmartHomeEddy 1,005]

1 hour ago, Dave C said:

I think they are.  Is there a special process to update them if they are Security Enabled?

Exclude and include them non secure and do the update. If you really want to have them secure included, you have to exclude and include them again. 

[irekk 5]

I stuck with most of my sensors (30 out of 33) on 3.2. What's worse for me, few of them are responsible for activating scenes. When I click update it will error, but also the HC3 stops activating all the scenes with sensors (beside if the actor sensors are updated or not). It requires to restart the HC3 to get back to normal.
My experience with Fibaro is that you just need to wait few months with the updates.

[Sankotronic 2,370]

Successfully updated 5 of my DW sensors FGDW-002

 

After initiating update I had to wake up DW sensor two times. First time is to initiate update and second time when it shows that is waiting for communication. After successful update to show new firmware, I first clicked on [Read Configuration] button and then again wake up DW sensor. After reading configuration HC2 will ask to refresh page and new version 3.3 was visible.

 

I get update failure only for one DW sensor with clear explanation that battery level is not sufficient for update. I installed new battery and update was successful. Since, this DW sensor also didn't want to start with update after few times waking up I move it closer to the HC2. I know how frustrating can be when you have to move some glued or screwed sensors, but it is not like we have to do it on regular basis.

 

Still have to do several more that are too far from HC2 to do firmware update, but will do them too. Easy one by one through the next few days

 

 

[Greenhippo 5]

Hi folks,

I have 21 FGDW002 sensors.  It will be so nice not to have the incessant, inaccurate low battery and replace battery notifications.  I’ve often found that batteries will last comfortably for 6-9 months after the first notification.  I’ve also found that new batteries are often reported as 40% or 60% battery level.  So I hope this 3.3 firmware addresses these frustrations.

 

All devices are connected to an HC3 running firmware 5.160.42, using the newer Z-Wave engine.  All devices are added in secure mode.

 

I have successfully updated all 21 of my FGDW002 sensors.  Here are some observations:

1. The HC3 will only update one sensor at a time.
2. After the firmware update, it’s necessary to “reoonfigure” the device.  This process results in the name and icon being lost, but the device retains the same ID.  Associations and scenes are not affected.  No rebuilding of scenes or associations was needed for any of my 21 FGDW002 sensors.
3. It’s possible to select “Update All” on the Devices / Updates page and the controller goes into a “Waiting for wake up” state for all devices.  When it notices a sensor has woken up (see next point), it begins the update - but only one sensor can be updated at a time.
4. I pressed “Update all” and went to bed.  The next morning, 11/21 sensors had completed the update, 4/21 were still “Waiting for wake up” and 6/21 were in state “Failed”.
5. The sensors wake themselves up occasionally, or maybe when the door/window is open or closed.  This sometimes did not trigger the update.  Even pressing the button on the side of the sensor often did not trigger the update.  I found that a reliable way to manually trigger the update for a sensor was to remove the battery, wait a few seconds and re-insert the battery.  This successfully triggered the update in all cases that I tried it.
6. For the devices that said “Failed” on the Devices/Updates page, I attempted to “Retry” them one by one.  In two cases, the device would not enter a “Queued” state.  For these devices, I ran "reconfigure" device (still with the 3.2 firmware) and, after the reconfigure process finished, the Devices/Updates page would allow the device to enter the “waiting for wake up” state and proceed with the update.
7. Many of my sensors are located far from the HC3 controller but, despite this, all updates were successful regardless of distance from the controller or number of hops over the network.  I did all the updates without having to re-position the HC3.  I also found that the updates took place even for sensors when the battery was reported at 0% level.
8. The further the distance (greater number of hops) between the sensor and the controller, the slower the update was for that sensor.  Typically, in direct range of the controller, the update progressed at about 10% per minute.  For a small number of hops, it was about 5% per minute.  For my most distant sensor, it was about 1% per minute.
9. Unlike @Sankotronic above, I could not find a way to read the new configuration from the device, to get the HC3 controller to reflect the new firmware version 3.3. Instead I had to “Reconfigure device” every time.  But this worked fine.
10. All 21 door/window sensors had been originally added to the HC3 in secure mode from the start and, unlike the comment from @SmartHomeEddy above I did not find it necessary to exclude / re-include them.  The updates worked fine with devices in secure mode.
11. I did not attempt to reconfigure any sensor while another sensor’s firmware update was in progress.  My approach was to do only one update or reconfiguration at a time.
12. A frustrating bug in this version of the HC3 is that, after reconfiguration, the names of the door/window sensor and all devices in its family are lost, reset to default names; so are any icon choices and so is the hidden status of the parent device. After each sensor reconfiguration, I had to manually rename the devices and reselect their icons, and re-hide the unwanted ‘parent’ device.
13. On multiple occasions, the Devices/Updates page in the HC3 web UI either would not reload in the browser or produced an error when either trying to start updating a device or trying to reconfigure a device.  The only solution I found was to reboot the HC3.
14. While any single update was in progress, it seemed as though the whole Z-Wave network was saturated.  Is this to be expected, @Sankotronic?  Seems odd that a device as advanced as the HC3 would be totally overwhelmed by updating one single door sensor.  During the update process, triggering of regular scenes became unreliable, many didn’t trigger at all.  Associations (e.g. between push-buttons and lights) stopped working.  Regular timed scenes (e.g. “all lights off” at midnight) did not run.  The app accurately reported status of devices but most actuators (switches, roller blinds, dimmers) could not be controlled from within the app.  The controller ran scenes that sent notifications (presumably because no Z-Wave is needed for notifications) but basically didn't do anything else.  
15. Rebooting the controller after the updates had finished seemed to restore normal functionality in every way.

 

(Edited for clarity and to adjust ambiguous statements.)

Edited September 2, 2024 by Greenhippo

[Fyase 11]

Hi guys,

 

here my experience on updating.

 

My 3 sensors we're included with security S0.

 

I tried to install software several times with no luck, the I tried with soft reconfiguration then exclusion and re-inclusion ( with security ) without any luck. On my environment it only works flawless without security.

 

@m.roszak Any guess on this behavior?

 

I still have to update one sensor. Do you need any logs?

[Fabir 73]

@Neo Andersson

On 8/17/2024 at 9:53 AM, Neo Andersson said:

I falied to update too, and unfortunatelly the device is in a  remote place where it is really hard to uninstall from, so for me it sucks..:-)

 

In such case I take the HC3, HC3L or Yubii Home close to the Z-wave device I want to update. Connect the hc over the emergency wlan to my handy hotspot and run the firmware update. Maybe also have to run an extension cable 230V to supply the homecenter.

[Neo Andersson 230]

1 hour ago, Fabir said:

@Neo Andersson

 

In such case I take the HC3, HC3L or Yubii Home close to the Z-wave device I want to update. Connect the hc over the emergency wlan to my handy hotspot and run the firmware update. Maybe also have to run an extension cable 230V to supply the homecenter.

Yeah, we did that too, but thanks

[m.roszak 763]

In general S0 Security encapsulation is very network-stressing, with thousands of frames sent it is not ideal for long processes.
If S0 update does not want to work, non-secure is a way to go. 

[kpwoxel 0]

Hey,
I also upgraded my firmware for the sensors some weeks ago and with soft reconfigure all of them are working fine on my HC3.

The battery status was for all devices 100% and now, weeks later, it is still 100% for all the devices.

I fear, that this is not correct and if the time comes, the sensors goes offline because of empty batteries.

How is the battery situation at yours?

[irekk 5]

Hello,

I managed to update all (30+) my window/door sensors to v.3.3 but I started to see strange behaviour after this update. Fresh batteries show >100%, like this:
 

Please login or register to see this attachment.