Jump to content
  • 0
jack.daniels

Module firmware update 3.3

Question

Hi, happy fibaro users!

 

Quote

 

The changelog:

  • Fixed inputs issue when bistable switches are used
  • Synchronization of switching in zero-cross - reducing the possibility of welded relay contacts
  • SDK updated to 6.51.07

 

 

 

Does enyone applied this new v3.3 update to the Signle Switch 2 loaded with toggle (bistable) switch ?

The same version for Dowble Switch 2 has issue (cant turn off the light when use switch), so better to ask here first:) Because still no support reaction on the problem and the only know workaround is to use momentary switches instead of.

 

Thanks forward for a feedback

Share this post


Link to post
Share on other sites

11 answers to this question

Recommended Posts

  • 0

Did anyone update FGS-213 successfully ? It stucks in downloading with no progress.

Share this post


Link to post
Share on other sites
  • 0

Hi @karolek75 , the fgd update went well with my hcl after I did the 4.501 firmware update, but i’m also stuck with a never ending download with my hc2 running under 4.170. I suppose it’s due to the boxe firmware version, but it’s just a assumption, maybe others users will have a different feedback.

Share this post


Link to post
Share on other sites
  • 0

I tried. Pass the downloading state, stuck at approx 75% of updating state and that's it - stuck there and had to abort. Ended up HC2 became weird though scenes still working. This morning perform backup stuck, reboot HC2 resulted in stuck at 'starting services' screen after booting up. Had to recover entire HC2 and restore previous backup (weeks ago when 4.170 release).

 

I am keen to see anyone success with update before trying again. Took me almost 6 hours to recover my HC2 to useable state.

Share this post


Link to post
Share on other sites
  • 0

@chaicka, not cool :( I did maybe 10 tries or , but it did not cause me any issues nor strange behavior, just the dowload was stuck. As I said just before it was ok on my hcl, it has to have something related to the boxe firmware version. 

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, chaicka said:

Took me almost 6 hours to recover my HC2 to useable state.

 

Was the HC slow, or did something not go as planned? My last attempt took about 1/2- 1 hour (not telling that to brag about it) and I usually tell new users (you are not one of them) to keep breathing and reserve 2 hours the first time. So 6 hours seems odd. If it was really that slow, I wonder if you have a hardware issue, like a failing (or almost failing) internal drive. That would explain your other issues as well.

Share this post


Link to post
Share on other sites
  • 0

My HC2 is still running on 4.120. Trying to update FGS-213 firmware it says downloading but no progress bar appears (should be there ?). More then 24 hrs and I aborted. HC2 is running with no issues since I fixed z-wave network being very busy. 

Share this post


Link to post
Share on other sites
  • 0

I have two FGS-213 and updated to firmware V3.3 without problems. My HC2 runs on V4.170. I use one with bistable and one with momentary switch. Both worked before and after without problems.

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
Posted (edited)
14 hours ago, petergebruers said:

 

Was the HC slow, or did something not go as planned? My last attempt took about 1/2- 1 hour (not telling that to brag about it) and I usually tell new users (you are not one of them) to keep breathing and reserve 2 hours the first time. So 6 hours seems odd. If it was really that slow, I wonder if you have a hardware issue, like a failing (or almost failing) internal drive. That would explain your other issues as well.

 

The recoveries (2 recoveries done) itself is not that slow. It is the few challenges that was slow.

  • First Recovery: It was easy to trigger the recovery mode. Selected to retain z-wave devices at first prompt which was a big mistake and caused lots of problems down the road of this first recovery. First boot up to factory version which was 3.564 (or something around that), then update to 3.600. Thereafter, lots of reconfiguration process stuck and had to abort each of them manually. Unable to get into recovery mode despite several attempts. Update to 4.170 and even more headaches with all the conversions, etc happening in the background. Interrupting does not help as HC2 simply refuse to get to recovery mode despite trying so many times. Even gotten locked out with error saying credential is not valid. As well as 403 error and other problems. It was a nightmare. Not remembering what I did in the end in normal mode, that finally allowed me to get to the recovery mode and I restart the entire recovery again.
  • Second Recovery: Now it is smooth sailing and fast after selecting to wipe all z-wave devices at first prompt. One oddity is that it update from 3.564 to 3.600, then from 3.600 to 4.070, followed by from 4.070 to 4.170. Make sure to check all respective warnings and make changes to credential and other stuffs which is part of the new setup wizard along each jump. Restored from a known good backup and walah...system up and running fine again. This second attempt was rather quick, approximately 1.5 hours.

Well, I have not done a great deal of recovery. This is only the 2nd time doing it while the 1st time was with a HCL. Not complaining but it definitely is not a fun thing to have to do.

 

Note: I doubt there is any hardware issue. It was all related to software and the choice I made during the first recovery attempt which screwed myself big time.

13 hours ago, rappenze said:

I have two FGS-213 and updated to firmware V3.3 without problems. My HC2 runs on V4.170. I use one with bistable and one with momentary switch. Both worked before and after without problems.

 

Just some questions to help me gauge/set expectation when I try again.

 

Does the progress bar moves very slowly during update? Is there an estimation of how long each update took? More than 30mins?

Edited by chaicka

Share this post


Link to post
Share on other sites
  • 0

In my system the firmware update took about 10-15 minutes per device. One of the device was about 7 meter away from HC2 without walls between, the other is on a different floor and has walls between, so I guess the second device is not in direct communication with HC2. Anyway both deviced took similar time to do firmware update.

Share this post


Link to post
Share on other sites
  • 0

Thanks rappenze. Guess will find a time that I can spare buffering for recovery should it goes wrong again.

Share this post


Link to post
Share on other sites
  • 0

Upgraded FGS-213 to v 3.3 and both energy reporting and CentralSceneEvents stopped working. Anyone with same experience? 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×