Precautions before updating to V4

[dawiinci 5]

Fibaro, could you please give us some advice about what we should do before updating to the version 4?

What do we have to expect in terms of reconfiguration?

I just want to be sure not having to reprogram every scene because the update mixes the device ids or something like that. That might be normal for you but it isn't for us.

I really hope V4 will be stable and flawless update from an existing setup.

However I'm not sure if I want to update as one of the first ones after these betas anyway...

[akatar 208]

every version is stable,

somewhere on this board there is explained by fibaro what stable means.

stable means: as is

bugs will not be fixed, so 3.590 is stable (or as is) because known bugs will not be repaired

so 4.xx is also stable, because as is, and the newer version have less bugs

[dawiinci 5]

Ok so forget about "stable" but the update process should work without interferences. This has not been the case in my last experience with their beta software.

[petergebruers 1,268]

Ok so forget about "stable" but the update process should work without interferences. This has not been the case in my last experience with their beta software.

Judging from the bug tracker and my own experience, some devices don't work well with V4. Yet. So that's "The End" for the upgrade I suppose?

My advice: know the recovery procedure at page 91 in the manual. For newbies: recovery is a tad different from what you might expect.

[ Added: 2014-12-26, 13:25 ]

Fibaro, could you please give us some advice about what we should do before updating to the version 4?

Oh sorry... I'm not a Fibaro employee. Just a humble user!

[j.nowacki 5]

dawiinci, migration to v4 should be performed from 3.600 if possible. Make sure you do not have any non-configured or dead devices and you should be ok.

[SDeath 68]

dawiinci, migration to v4 should be performed from 3.600 if possible. Make sure you do not have any non-configured or dead devices and you should be ok.

This remark troubles me a bit, I have a FortrezZ SSA2 z-wave siren in my network and it works fine. I've set both the parameters it can take by hand as there is no template for this device, and it get's send to the siren like it should.

But when I check my zwave network for unconfigured devices using this code:

Please login or register to see this code.

And I get the feedback the siren is the only device that needs configuration.

So as you recommend to not have any unconfigured devices, will I be in trouble when I update from 3.600 to 4.x, without first excluding the siren?

[dhanjel 7]

I don't want to loose all my scenes from beta, what should we do exactly?

[deanrparry 19]

I don't want to loose all my scenes from beta, what should we do exactly?

Please login or register to see this image.

[akatar 208]

en after the update

deanrparry and fibaro

Please login or register to see this attachment.

[Tekvibes 7]

en after the update

deanrparry and fibaro

That leaves only 1 question... who's the black one and who's the ginger?

[Krikroff 199]

akatar, Hopefully!

Please login or register to see this image.

/emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" />

[Lollo72 0]

Hello,

j.nowacki, and if unfrotunately I have some dead nodes or not "correctly powered" some device?

How can I do?

I got Error 9 too.

Please login or register to see this image.

/emoticons/default_icon_redface.gif" alt=":oops:" />

[j.nowacki 5]

Lollo72, in such case you should re-include it before update and make sure is has communication with controller.