Changed Asset Value Not Set Due To "Enabled" Not Set In Kura

[LeoNerdoG]

One of the settings in Kura Assets is also "Enabled" parameter, which tells if new values can be stored or not (if the asset is Read-write). The problem is, that is end-user does not know if this setting is enabled or not, can still change the values in Kapua but they do not get stored, which can be confusing.

There is also issue on Kura project regarding this matter, so I am linking it here: eclipse/kura#1904

Testflow:

1. Login as kapua-sys or any other user that has proper permissions
2. Connect a live Kura device (e.g. device0) that has some assets (some should be enabled and some should be disabled).
3. In Kapua go to Devices and select this device0 and go to its Assets - try to change value of the enabled and disable ones. Assets that are not disabled should not be modifidable by user in kapua.

Expected behavior If there is a possibility, I suggest we add additional option/flag/anything that would give end-user information about the field (if it is enabled or not) as this can be a problem if he does not have access to the device directly.

Screenshot No. 1:

Screenshot No. 2 (no additional parameters beside field's value is there, so field looks it is normally modifiable):

Screenshot No. 3 (User can "change" the settings's value):

Version of Kapua 1.1.0-SNAPSHOT

Type of deployment [ ] Local Vagrant deployment [x] Docker [ ] Openshift (in its variants) [ ] Others

Main component affected [x] Console (in case of console please report info on which browser you encountered the problem) [ ] REST API [ ] Message Broker [ ] - Others

Browsers used:

• Google Chrome (Version 71.0.3578.98 (Official Build) (64-bit))
• Safari (Version 12.0 (14606.3.4))
• Mozilla Firefox (64.0 (64-bit))
• Opera (Version 57.0.3098.110)

[ct-goranpalibrk]

Hi @lorthirk About this issue, properties for Device channels are retrieved through Kura, but that isn't case with enabled/disabled property. Do you maybe have some proposal?

[lorthirk]

As @LeoNerdoG says, this issue depends on eclipse/kura#1904. We cannot fix our own without that one, because we have no other way to recognize a disabled channel.