jasoncodes
(Jason Weathered)
April 4, 2019, 6:17am
1
Hi there,
Has anyone else has had problems changing boolean configuration parameters on their Z-Wave devices? I’m running Home Assistant 0.90.2 but this issue has existed for some time.
In particular, I am having troubles disabling parameter 90 (to control 91/92 reporting) on my Aeotec ZW096 Smart Switch 6. Any time I try to disable it the Z-Wave logs show it was being enabled instead. When I try to change it to “False” the following log lines were emitted:
Info, Node011, Value::Set - COMMAND_CLASS_CONFIGURATION - Enables/disables parameter 91/92 - 90 - 1 - True
Info, Node011, Configuration::Set - Parameter=90, Value=1 Size=1
The fix for me was to edit my zwcfg*.xml
file and change the value type from a boolean:
<Value type="bool" genre="config" instance="1" index="90" label="Enables/disables parameter 91/92" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="True">
<Help>Enable/disable Wattage threshold and percent.</Help>
</Value>
to a list:
<Value type="list" genre="config" instance="1" index="90" label="Enables/disables parameter 91/92" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
<Help>Enable/disable Wattage threshold and percent.</Help>
<Item label="Disable" value="0" />
<Item label="Enable" value="1" />
</Value>
This solved the problem for me. Here’s the log output when I enable and then disable:
Node013, Value::Set - COMMAND_CLASS_CONFIGURATION - Enables/disables parameter 91/92 - 90 - 1 - Enable
Node013, Configuration::Set - Parameter=90, Value=1 Size=1
…
Node013, Value::Set - COMMAND_CLASS_CONFIGURATION - Enables/disables parameter 91/92 - 90 - 1 - Disable
Node013, Configuration::Set - Parameter=90, Value=0 Size=1
onkytonk
(Joseph Naim)
July 21, 2020, 2:39am
2
I know this threads a bit old, but I’ve recently tried to get my switches working for power monitoring my washer and dryer.
I’m actually wanting to set this parameter to “true”, but setting it within HA ui does not do anything when I check the xml.
Just curious though, does this setting push the updates, rather than polling using the “sending interval”?
firstof9
(firstof9)
July 21, 2020, 3:57am
3
The XML only gets updated when you shutdown HA, hit the stop network button, or save config button in the zwave control panel.
Correct, this would have the device send the updates on it’s own rather than having to poll them.
onkytonk
(Joseph Naim)
July 21, 2020, 1:00pm
4
I’m hitting Save Config, but its one parameter that won’t update in the xml.
I might have to change my xml with what @jasoncodes has done above and see if that works.
firstof9
(firstof9)
July 21, 2020, 1:28pm
5
That does look like the right config, a list
rather than a bool
onkytonk
(Joseph Naim)
July 21, 2020, 1:33pm
6
It worked perfectly!
Is there anyway of identifying when a parameter should be list rather than a bool, in case I run into this in the future?
Is there anyway of fixing this permanently? Or is it limited by the older Open Z wave implementation in HA?
firstof9
(firstof9)
July 21, 2020, 1:38pm
7
I’m not sure if PRs are being accepted for the older version of openzwave. Any software using version 1.4 will have this same issue. That’s why there’s an updated implementation in the works, OpenZwave Beta.
onkytonk
(Joseph Naim)
July 21, 2020, 1:39pm
8
Yeah, I’m waiting until its out of beta before I make the migration.
Thanks for the help!
firstof9
(firstof9)
July 21, 2020, 1:41pm
9
I’d say once 0.114 rolls out, most device features will be available and it’d be safe to migrate, even if it’s still “beta”.