Values for custom config parameters only show up after reloading the page

[AlCalzone]

During the CTT tests, a device is tested where existing config parameters cannot be determined automatically (Configuration CC V1 or 2).

I pressed GET VALUE here, the command was sent, but there was not visual feedback.

The highlighted section only showed up after reloading the page:

This should happen automatically, since it is a certification requirement:

Verify that the DUT offers a UI which allows the end user to see the parameter numbers which has been set (parameter number = 1) and their current value according to Requirement Number: CL:0070.03.41.01.1

[AlCalzone]

Also, GET VALUE clears the Value input - I'd at least expect it to show the received value.

[AlCalzone]

The fix for showing the value here after SET does not appear to be working:

If the parameter wasn't known initially, it still only appears after reloading the page.

[MindFreeze]

Could this be caused by delayed reporting of the new param? On the frontend, after a get/set, we call the same "zwave_js/get_config_parameters" WS API as on load.

[AlCalzone]

Might be. The driver sends the command to set it, then verifies the change. There should be a value added (or maybe value updated) event once the change was verified. Maybe it would be better to listen for that.