Question about Z-Wave 3 migration stability and Fibaro device compatibility

[Łukasz997 117]

This is the question to @m.roszak. But I appreciate any info from users.

I would like to ask for clarification regarding the current state of Z-Wave 3 support in the Fibaro ecosystem.

Is the migration from Z-Wave 2 to Z-Wave 3 now considered safe and fully functional, or is it still in a beta stage?
In particular, I’m interested in how well Fibaro devices - especially the Fibaro Heat Controllers - perform when connected through Z-Wave 3.

The migration process requires a considerable amount of work on my side, so I’d like to make sure that the new implementation is stable and reliable before proceeding.

 

Below I’m quoting part of Fibaro Support’s response regarding Z-Wave 3 and Heat Controller. At that time, it was true.
Now, perhaps this information is already outdated?

 

Info from ticket dated 10.01.2024

Ticket ID: 288045

Chcę też zauważyć, że używa Pan centrali Z wersją silnika Z-wave 3.0, który jest obecnie w wersji beta. System z takim Z-wave'em należy traktować jak środowisko testowe. Wersja Z-wave 2.0 jest w wersji stabilnej.
 

[m.roszak 763]

So, the migration process will be avaialable as an automatic process, we are working on it.

ZW3.0 is already mature and works better with 3rd party products than the old one.
One downside, as its fully Z-Wave certified very old products which was developed in not very "specification compliant way" may misbehave - I mean very old ZW300 (not Z-Wave+) devices.
We did make a supprot for the most popular ones so there should not be much issues.

I would recommend to wait for official migration and do not make the configuration from the scrach as it is very time consuming.
Also, if something won't work due incomplatibilty with those "old" devices it will be possible to revert the migration with one click.
 

 

[Łukasz997 117]

@m.roszak One more timid question: when do you expect this migration method to be available? I promise I won’t hold you to it, but please, tell me something…

[m.roszak 763]

Beta version for it is planned for this year.

[m.roszak 763]

More precise info, release of the beta is more likely to be in Q1 2026 than in Q4 2025.

[Jeff91 0]

I've been running version 5.070.42 since March 18, 2021, with over 40 Z-Wave modules (90% Fibaro) on my HC3. I've been waiting for a stable firmware that allows smooth migration with minimal disruption.
If a stable version is about to be released, that's great news.

[rraptorr 4]

I have three systems that I have migrated to Z-Wave 3 engine. Obviously the hard way, with factory reset, right now on 5.190.38.

All of them are 100% Fibaro devices only. Two HC3Ls with some heat controllers and door/windows sensors. One HC3 with 130 z-wave devices (heat controllers, door/windows sensors, motion sensors, roller shutters and a ton of walli switches/outlets).

My main motivation was switching to S2 authentication, as Z-Wave 3 supports this mode, while Z-Wave 2 doesn't.

 

My observations:

• no major issues, everything works stable right now, even on the big HC3 system
• HC3 did throw some errors once or twice when trying to enter z-wave learning mode, but reboot helped
• the big system is on S2 where possible and it works basically as snappy as in unauthenticated mode when using Z-Wave 2 (I did try to use S0 on Z-Wave 2, but everything was slow and unreliable then, this is obviously a problem of S0, not Z-Wave 2)
• even the heat controllers seems to work ok with S2 - on S0 they were not only slow, but basically always having some problems
• main pain for me were the wallis, original installer didn't think about writing down PIN numbers for them, so I had to dismantle all of them - I did find some outlets without ground wire though, this is now fixed

 

[Łukasz997 117]

@rraptorr, thanks for sharing, valuable.

[Fyase 11]

@m.roszak 

 

Whenever the automatic migration will became available,  during the migration will be possible to switch between S0 to S2?

 

Now I have all my 50 devices in S0 but sometimes network is a bit slow.

 

Best regards

Raffaele

[rraptorr 4]

The way I understand Z-Wave protocol, automatic migration from S0 to S2 is not possible. Device needs to be excluded and included again in S2 mode. But I might be missing something.

[Fyase 11]

17 hours ago, rraptorr said:

The way I understand Z-Wave protocol, automatic migration from S0 to S2 is not possible. Device needs to be excluded and included again in S2 mode. But I might be missing something.

 

I have 50 Z-Wave device device... and around 30 automation...

 

It will drive me mad....

[SmartHomeEddy 1,005]

50 devices, depends on how hidden they are. 

[Fyase 11]

3 hours ago, SmartHomeEddy said:

50 devices, depends on how hidden they are. 

 

They are highly interconnected. So basically most of the work needs to be re-done.

 

I saw that I can get scene config with swagger. Then with some powershell script and l lot API call I'll change all the ID.

 

I guess that Fibaro, to simplify the experience, should implement a native function to "replace" device without incurring in such a situation.

 

Raffaele

[SmartHomeEddy 1,005]

15 minutes ago, Fyase said:

I guess that Fibaro, to simplify the experience, should implement a native function to "replace" device without incurring in such a situation.

I don’t think it is possible with the z-wave framework. 
 

 

 

Edited November 30, 2025 by SmartHomeEddy

[rraptorr 4]

4 godziny temu, Fyase napisał:

I guess that Fibaro, to simplify the experience, should implement a native function to "replace" device without incurring in such a situation.

I just redid a system with 130 devices

I'm afraid this is simply not possible due to the way Z-Wave protocol works. Devices do proper authentication during inclusion to the network (in S2 you need to give PIN number of the device during inclusion). So automatic upgrade from unauthenticated/S0 to S2 is not possible.

Fibaro did promise a migration from Z-Wave engine 2 to Z-Wave engine 3, but not authentication upgrade.

[Fyase 11]

17 hours ago, SmartHomeEddy said:

I don’t think it is possible with the z-wave framework. 
 

 

 

What I mean is this.

 

If user have to change a broken switch or, in my case, change the security mode have today you have only one option. Delete the device from HC3 and insert same device again. After this he have to go on every scene and update the new ID.

 

An automatic feature could be to choose between:  

 

1. Standard delete --> go same way as today
2. Replace device --> system remember the actual ID of the "replaceable device", then delete the device and ask to join the new one. I f the new one have same capability it records the new ID and automatically change this on the scene to match the actual one. It will be a great feature for lot of people. 

 

It quite easy I guess.

 

Raffaele

13 hours ago, rraptorr said:

I just redid a system with 130 devices

I'm afraid this is simply not possible due to the way Z-Wave protocol works. Devices do proper authentication during inclusion to the network (in S2 you need to give PIN number of the device during inclusion). So automatic upgrade from unauthenticated/S0 to S2 is not possible.

Fibaro did promise a migration from Z-Wave engine 2 to Z-Wave engine 3, but not authentication upgrade.

I guess you're right.... I'll do one by one replacing ID with powershell once migration will be available.....

[SmartHomeEddy 1,005]

2 hours ago, Fyase said:

An automatic feature could be to choose between:  

 

1. Standard delete --> go same way as today
2. Replace device --> system remember the actual ID of the "replaceable device", then delete the device and ask to join the new one. I f the new one have same capability it records the new ID and automatically change this on the scene to match the actual one. It will be a great feature for lot of people. 

 

I understand. It has been asked before, somewhere on the forum, but it has some nasty side efects.