ZUNO_CONFIG_PARAMETER_INFO can only be run once
Posted: 18 Jul 2023 04:27
I am using Z-Wave JS UI interface to my SL USB controller to monitor and modify my Zwave network.
When I try to create a device parameter on my Zuno (latest generation as of this posting date), I find that Configuration data set at the controller will not work if the Zuno has a call to configure a parameter after it has initially been included to the controller. If the following code is present on the Zuno the controller cannot write back values from the controller to the device:
I have a configuration handler set up such as this:
However, if I remove the ZUNO_CONFIG_PARAMETER_INFO call AFTER the device has been successfully included, the controller can pass values back to the Zuno.
Here is my handler:
The calls to the handler are not transmitted to the Zuno if the setup macro for the configuration parameter is present, post inclusion.
A similar problem occurs with calls to
Seems to me that there is some conflict in writing configuration data from the Zuno back to the controller. The controller can read (load) values at any time, but writing back to the controller from the Zuno seems to cause a controller failure, at least in Z-Wave JS.
Has anyone else seen this strange behavior?
Thank you
When I try to create a device parameter on my Zuno (latest generation as of this posting date), I find that Configuration data set at the controller will not work if the Zuno has a call to configure a parameter after it has initially been included to the controller. If the following code is present on the Zuno the controller cannot write back values from the controller to the device:
Code: Select all
ZUNO_SETUP_CONFIGPARAMETERS (
ZUNO_CONFIG_PARAMETER_INFO("Humidity Offset Value", "Defines humidity threshold tuning value", -10, 10, 3)
);
Code: Select all
ZUNO_SETUP_CFGPARAMETER_HANDLER(config_parameter_changed);
Here is my handler:
Code: Select all
void config_parameter_changed(uint8_t param, int32_t value) {
if (param == OFFSET_PARAM) { // The first user-defined parameter
paramValue = value;
#ifdef DEBUG
Serial.print("New value of the parameter OFFSET CONFIG PARMETER: ");
Serial.println(paramValue);
#endif
}
}
A similar problem occurs with calls to
Code: Select all
zunoSaveCFGParam(64, paramValue);
Has anyone else seen this strange behavior?
Thank you