ZW 3.0, go for it or wait?

[JcBorgs 52]

I have a system with almost only Fibaro devices (all in all +100 physical devices) and all should be ZW5 version if I recall correctly. But there are a lot of battery powered devices (motion sensors, door sensors, flood sensors, smoke detectors) and read in one post that better implementation for battery devices will come during Q4.

 

So would it be recommended to wait until that release, or would it be good to go already now as devices are of the latest version?

[A.Socha 133]

stay on z-wave 2.0

[Bodyart 231]

18 minutes ago, A.Socha said:

stay on z-wave 2.0

Please Mr. @A.Socha,

 

could you elaborate a little?

thanks in advance.

 

Z góry dziękuję

[akatar 208]

@Bodyart zwave 2.0 is almost done on hc3, zwave 3 needs a lot of finetuning and templates that needs to be added

(so not all functions and devices will work on zwave 3)

[Bodyart 231]

5 minutes ago, akatar said:

@Bodyart zwave 2.0 is almost done on hc3, zwave 3 needs a lot of finetuning and templates that needs to be added

(so not all functions and devices will work on zwave 3)

Understood that, but really like to hear @A.Socha his story, motivation, Fibaro's vision.

[akatar 208]

story? long story

motivation> there is none

vision> lost for ever

[Bodyart 231]

Just now, akatar said:

story? long story

motivation> there is none

vision> lost for ever

heheheh

 

[tinman 1,070]

3 hours ago, JcBorgs said:

I have a system with almost only Fibaro devices (all in all +100 physical devices)

 

currently there is no migration path / tool to switch from z-wave 2.0 to z-wave 3.0. That means you will have to exclude all devices, do factory reset on HC3, include all devices, write all scenes, import all QAs ... day of work, best case.

 

Additionally z-wave 3.0 is in beta stage, so when something will not work as expected, you will have to wait (weeks --> months) till it will get fixed, or switch back to z-wave 2.0 (which again means everything from scratch).

 

[JcBorgs 52]

On 8/8/2021 at 12:26 AM, tinman said:

 

currently there is no migration path / tool to switch from z-wave 2.0 to z-wave 3.0. That means you will have to exclude all devices, do factory reset on HC3, include all devices, write all scenes, import all QAs ... day of work, best case.

 

Additionally z-wave 3.0 is in beta stage, so when something will not work as expected, you will have to wait (weeks --> months) till it will get fixed, or switch back to z-wave 2.0 (which again means everything from scratch).

 

 

Good input tinman! Will definately wait to do the move to 3.0