Allow GET/SET config value of a custom configuration parameter

[AlCalzone]

Allow the user to GET/SET a custom configuration value for a device. The device configuration panel needs to be expanded, as well as the websocket.

[AlCalzone]

Related to this, I tried to use the set_config_parameter service to set an unknown config parameter as part of the certification tests and got this error, which kind of defeats the purpose of this service call UI (and causes the test to fail):

[marcelveldt]

expert UI

[MindFreeze]

In order to remove the error from the service and make custom params possible we need this PR https://github.com/home-assistant-libs/zwave-js-server-python/pull/1080

[AlCalzone]

This is not working correctly. When getting a config parameter, the message sent to zwave-js-server has the parameter number in an options object, when it should be directly on the message:

vs.

[AlCalzone]

Setting a value of 0 fails frontend validation:

And when frontend validation passes, the message also has the incorrect options parameter:

[MindFreeze]

This is not working correctly. When getting a config parameter, the message sent to zwave-js-server has the parameter number in an options object, when it should be directly on the message:

vs.

This should be ok as it is transformed in the zwavejs-server https://github.com/zwave-js/zwave-js-server/blob/1fb161d20a6714489f8e05ad59e7cb66f18ba5cd/src/lib/common.ts#L95-L108

[AlCalzone]

The screenshot shows the actual contents of message (see the options property), which does not adhere to the IncomingCommandNodeGetRawConfigParameterValue interface. The message.parameter in the code you linked does not exist, it is available under message.options.parameter, which should not exist.