Z2-Z3 Migration bug

[Neo Andersson 230]

Some major bugs found

1. Thermostat heads (Fibaro) doesn't follow the climate schedule panel setpoints. / i didnt test with other thermostats yet

2. Fibaro radiator head's "heatRequired" never changes, so we can not drive heatpumps according to this property value. 

 

note: both were working flawlessly in engine 2. We have it in many many installations..

[Neo Andersson 230]

Another bug
Inclusion process stuck in loading screen

Please login or register to see this image.

/monthly_2026_03/image.png.1b359eb24e5502326f842a5a499b257c.png" />

[Ini 0]

W dniu 7.03.2026 o 09:57, Neo Andersson napisał:

Some major bugs found

1. Thermostat heads (Fibaro) doesn't follow the climate schedule panel setpoints. / i didnt test with other thermostats yet

2. Fibaro radiator head's "heatRequired" never changes, so we can not drive heatpumps according to this property value. 

 

note: both were working flawlessly in engine 2. We have it in many many installations..

 

Hi Neo!

 

We are currently investigating the issue you reported regarding the thermostatic heads. This issue is not related to the migration.
As for the “heatRequired” value of the radiator head, we are already working on a solution. 

 

Kind regards,
Ini

[Ini 0]

W dniu 7.03.2026 o 11:09, Neo Andersson napisał:

Another bug
Inclusion process stuck in loading screen

Please login or register to see this link.

 

Neo,

 

could you try adding the devices again and generate the logs while doing so? This will help us check exactly what’s going on.
By the way - which devices were you trying to add?

 

Best regards,

Ini

 

[Neo Andersson 230]

Hello, i am in contact with mr @D.Karczewski
It was a Aeotec Sirene 6 device
We had an issue wth forst migration. then i have sent logs to him. He found that some tone names have unsuppreted chatracters that might cause the problem.

To proove this, i have exlcluded the device and tried the migration again. It worked. So i tried to re-add the device again, but it failed again.

I think this is still caused by some tone names, but i can try it once again. So at which point shoul i download the logs? After the failed inclusion ?

Becuase the inclusion never ends. Or should i donload the logs during th inclusion while the loading screen is shown?

[Ini 0]

If the process gets stuck, please download the logs and send them to me - I’ll pass them on to Damian

 

Ini

[Neo Andersson 230]

4 hours ago, Ini said:

If the process gets stuck, please download the logs and send them to me - I’ll pass them on to Damian

 

Ini

I tried again..The process never ends. Here is the logs

Please login or register to see this attachment.

[Ini 0]

The issue has been submitted for analysis, and I’ve already passed the logs to Damian.

 

Best regards,

Ini

[Neo Andersson 230]

Here i have some other problems
System shows me available FW updates for devices..
I started the update and it finished with "Completed" notification

Please login or register to see this attachment.

 

 

However, i see some warnings about reconfiguration see the picture

Please login or register to see this attachment.

also i noticed that even the process says its finished, in the device swagger i can still see that device is on 5.1 and 5.3 is still avaiable for it..
What to do?? Do we need to manually reconfigure devices after FW updates??

[Neo Andersson 230]

I tried manually reconfigure the device 237
It ended up with all the childrens got new IDs !!!!!!!!! (parent stayed 237)
 

[Neo Andersson 230]

Another issue
Device stuck in FW update

Please login or register to see this attachment.

[Neo Andersson 230]

Another issue
Reconfiguration runs forever for some devices.. and never ends..i can not cancel it, so i can not do anything about it

This below is running more than 30 minutes

Please login or register to see this image.

/monthly_2026_03/image.png.dc9cc67f9c6d3069e132534c2e960e95.png" />

[Ini 0]

W dniu 9.03.2026 o 17:03, Neo Andersson napisał:

Here i have some other problems
System shows me available FW updates for devices..
I started the update and it finished with "Completed" notification

Please login or register to see this attachment.

 

 

However, i see some warnings about reconfiguration see the picture

Please login or register to see this attachment.

also i noticed that even the process says its finished, in the device swagger i can still see that device is on 5.1 and 5.3 is still avaiable for it..
What to do?? Do we need to manually reconfigure devices after FW updates??

 

Hi Neo,

 

Could you please specify exactly which devices these were and whether they were mains-powered or battery-powered devices. I would also appreciate it if you could send the logs from the moment when the issue occurred.

 

 

Best regards,

Ini

[Ini 0]

W dniu 9.03.2026 o 17:12, Neo Andersson napisał:

I tried manually reconfigure the device 237
It ended up with all the childrens got new IDs !!!!!!!!! (parent stayed 237)
 

 

Yes - device IDs may change if something in the model changes. In practice, this is more likely for devices after migration. We are working on reducing the number of such cases in the next version of the system.
This information that devices may receive new IDs is indicated:

• on the Device reconfiguration tab, above the "Reconfigure device" button (it is also visible in the screenshot you attached),
• and in the modal window with the warning message, which appears after clicking the Reconfigure device button.

[Ini 0]

W dniu 9.03.2026 o 18:52, Neo Andersson napisał:

Another issue
Reconfiguration runs forever for some devices.. and never ends..i can not cancel it, so i can not do anything about it

This below is running more than 30 minutes

Please login or register to see this link.

 

Here we also need some clarification – please let me know exactly which devices these were. If there are battery-powered devices, they will almost certainly need to be woken up.

[Neo Andersson 230]

1 hour ago, Ini said:

 

Here we also need some clarification – please let me know exactly which devices these were. If there are battery-powered devices, they will almost certainly need to be woken up.

What do you mean by "Which devices there were" ??? You can clearly see on the picture. Its the device 142. Reconfiguration stuck. Its not a battery device, its an implant.
 

[Neo Andersson 230]

3 hours ago, Ini said:

 

Hi Neo,

 

Could you please specify exactly which devices these were and whether they were mains-powered or battery-powered devices. I would also appreciate it if you could send the logs from the moment when the issue occurred.

 

 

Best regards,

Ini

Again, its on the picture..ID is 237
You colleague have responded to this. Device shows Completed status but the update is still not yet applied until the reconfiguration happens..You also have the logs. I had to manually reconfigure the device and only after that the available update dissapiered (so the update actually got applied)
I think in large system migration is a horror. We will not do it. We will use engine 3 only on new systems. Having a system with 150 moduls, and all the migration requires reconfiguration of all devices ..wll this is not a path we can afford. Its not only that its such a time consuming task (that it would need days to complete), but also our plugins all across the system are using already some IDs of devices. Reconfiguring every single device means they got all new IDs so our all plugins will crash. I have discussed this with your colleagues. This is not the way we want to go on existing large systems. Thanks

[m.roszak 763]

So, the reconfiguration after the OTA is a Z-Wave protocol requirement according to the specification.
As 3.0 is fully certified, its something mandated unfortunatelly.

At the end, as @Ini stated - we are working on bulletproofing the reinterview (reconfiguration) of the migrated devices to keep the IDs if possible. 
Its not an easy job as migrating everything from one model to another (with filling the gaps from old model) is not an easy task.