Templates not working properly after the Z-Wave engine update

[L3n 4]

QUBINO 3-PHASE SMART METER - stopped working after the update. 
I went to check the settings and noticed that it had stopped displaying some configuration options. 
Parameters 42 and 43, which control the refresh rate, have disappeared from the settings, but they are still present in the template.
The options to manually add or modify the parameters have also disappeared. 

Please login or register to see this attachment.

[L3n 4]

 changing "hidden": true => "hidden": false and the template update - added hidden settings to GUI . But the device still isn't working properly. It's ignoring the settings. 

[Support FIBARO 11]

Hello,

 

Thank you for your report. To analyze the issue, please send us the logs from the hub in a private message.

 

To download them, enter the following address in your browser:
gateway_IP/api/service/logsDump
Then upload the downloaded file.

 

Thank you and best regards

[L3n 4]

Please login or register to see this attachment.

Please login or register to see this attachment.

[L3n 4]

I managed to fix it. I removed the default association and added a multichannel controller.

In other words, the problem is in the associations and hidden default settings in the template. 

Please login or register to see this image.

/monthly_2026_03/image.thumb.png.19bae4b79670ea57ddc2da11851346f5.png" />

Edited March 17 by L3n

[L3n 4]

UPD. 
My fix still isn't working properly. 😐

Singlechannel association - Only the sensors on endpoint 0 (ROOT) are working
Multichannel association - All other sensors are working except for endpoint 0 

[m.roszak 763]

Yeah, singlechannel setting is a desired one (this setting works reliably on the device side) - this reports all data to endpoint 0 (summary from all phases).
If you use multichannel association then it reports summary on endpoint 1 and phases on endpoints 2, 3 and 4.

I don't recommend multichannel association as device may stop reporting the values at some point and factory resert and adding the device again will be needed - an issue on the Qubino side. 

Could you sum up what is your main problem? Which values are not updating correctly after the migration? Keep in mind what I wrote above - in default setting only root (0) endpoint gets the reports and its "as designed". 

[L3n 4]

1 hour ago, m.roszak said:

Could you sum up what is your main problem? Which values are not updating correctly after the migration?

After migration, only the ROOT endpoint updates the data. Voltage Amperage and other data is not being updated. 
 

1 hour ago, m.roszak said:

Keep in mind what I wrote above - in default setting only root (0) endpoint gets the reports and its "as designed". 

Yeah, I know that, but the device accepts the time interval settings (42/43), but ignores them and doesn't update the data.

Please login or register to see this image.

/monthly_2026_03/image.thumb.png.8106d57bc66cbca79ed21020d44f950e.png" />

[m.roszak 763]

So, we will check what is happening here.

Thanks for the detailed report.

 

Regardless of lifeline association setting it should report the values on root or endpoints for all meter types.

[m.roszak 763]

Have you tried the reconfiguration of the device to check if the device will start working correctly?
It may (probably will) change the ID of the devices.

Still you will be able to restore the backup - just make sure to not remove and add the device again.

[L3n 4]

On 3/18/2026 at 2:33 PM, m.roszak said:

Have you tried the reconfiguration of the device to check if the device will start working correctly?
It may (probably will) change the ID of the devices.

No, I haven't tried that. I really don't want to lose the sensor IDs because I have a lot of integrations that are tracking that.
About restoring the previous version: my last restart ended with an error restoring user data, so I had to perform a recovery. It's strange because I've done the restore twice before and everything went smoothly, but the third time I got an error. I didn't write to you about it, but I decided not to play around with it.

Please login or register to see this attachment.

Edited March 20 by L3n