Issue with firmwareUpdate.currentVersion not displaying on Information

I have a few Z-Wave drivers I am maintaining that set the capability firmwareUpdate currentVersion value to a string of the current version reported by the device, so that people can verify what firmware the device is on easily.

This has been working fine on multiple devices until this most recent update I am working on. The only difference I can figure out is this device has a lot more capabilities and events than the others, because it is a power metering plug. I am using the iOS mobile app.

On the metering plug, if I exclude the device and include again (then switch to test driver) the firmware shows on the … > Information page in the mobile app. If I force quit the app and then go back in and check again, the firmware version is gone. Also if the profile gets switched it will also cause the same behavior (there is a setting to change the profile to display more info).

I can verify in the logs and also the advanced interface that the value is properly set.

One other device which uses the SAME driver is working fine, it has a sub-driver and a different profile but the core code is the same. This is just a basic on/off switch. The device has been included for weeks and the currentVersion still displays in the Information page. Two other devices on different drivers are also working fine, a button controller, and a water valve.

Isn’t firmwareUpdate.currentVersion auto-populated by the hub firmware?

Looks like it’s overwritten with an empty value.

Not for zwave devices apparently. I can see the value I set stays there, see my screenshot above.

1 Like

Maybe device:try_update_metadata() clears the currentVersion attribute and you have to pupulate it again? Just a guess.

I can see the value is still there in the advanced web UI.
Also if the device is manually refreshed it will ask for the version and set it again, which does not fix it to come back. Also this is only happening on one device out of 3 tested on the same core driver code. Plus two others working fine on other drivers using the same functions in the code.

I am thinking it has something to do with the number of events coming in, could it be flushing out some cache causing it to not display the firmware version anymore? Seems like some sort of bug with the mobile app to me.

1 Like

Looks like the mobile app was updated and the effected info screen has changed.
I can confirm the issue still remains.

I have found out that when the device is refreshed (swipe down) if I set the currentVersion to a blank string “”, then back to the actual current version it will display on the info page temporarily. If you then back out of the device to the device list and go back in again, it is gone until you refresh again.

This only happens on these 3 power metering devices (total of 11 profiles) and I cannot for the life of my figure out any difference I have in my code that would be causing it. All other devices using the same code it works fine and always displays, as it should.

What is the proper channel to bring up bugs to Samsung?

Since they are obviously not paying any attention my post.

Hi @jtp10181

We’re currently investigating the issue with our engineering team. We’ll update you as soon as we have more information.

We appreciate your patience.