Closed ghost closed 7 years ago
Openzwave uses the index for values, not the actual value, so if you check your zwcfg for this node, you will see that valueindex 0 has value 1 and valueindex 1 has value 2.
Openzwave wil crash if you send it wrong valueindex, and takes HASS with it.
Meaning you must use: {"node_id": 95, "parameter": 5, "value": 1 }
Clarification: If the parameter is a list, openzwave uses the valueindex(Order of list, starting with 0 at the top) Other parameters uses actual values.
Ah ok I see. But surely using the wrong number shouldn't cause HA to bomb out completely?
You are totally correct, I need to ask around to see if there is a way to prevent this.
Ok cool. Btw, wouldn't it be good if the logs where to print out the full available index value
I normally just tail the openzwave log when running these kind of commands to check its being sent
Cheers!
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
): 0.35.2Python release (
python3 --version
): 3.4.2Component/platform: Pi 3
Description of problem: HA crashes in 0.35.2 when trying to use zwave set_config_parameter service
Expected:
Problem-relevant
configuration.yaml
entries and steps to reproduce:Trying to set a value via zwave / set_config_parameter on aeotec sensor zw074 causes HA to crash, ie:
Set to binary switch reporting:
{ "node_id": 95, "parameter": 5, "value": 2 }
however this value works fine (on time to 60 secs):
{ "node_id": 95, "parameter": 3, "value": 60 }
NOTE: this gets written to the zwave log when it crashes:
"2016-12-25 15:43:04.433 Warning, Invalid Index Set on ValueList"
Manual: http://www.vesternet.com/index.php/downloads/dl/file/id/450/product/0/z_wave_aeon_labs_multisensor_gen5_engineering_specification.pdf