OpenZwave administration

What tools do you use to manage your OpenZWave network and devices?
I use the OpenZWave add-in, of course, but sometimes I need to do things that can’t be done there.
This includes operations like

  • Check a node to see if it’s ok or failed
  • Remove node entries that don’t exist anymore or that have failed
  • Make a backup of the zwave stick, to another stick or to a file.
  • And probably more

I use Aeotec’s own utility, but that means that I have to stop zwave, move the usb plug to my windows pc, do what I have to do, and move it back again.
I’d really like to do this from the HA add-in, or at least, do everything from one tool.
Am I missing something obvious or do I have to wait for a long time for this to be possible?

2 Likes

Which tools do you use?

None. I never could get the OpenZWave add-in to work.

I’ve chosen to replace all my ZWave devices with Zigbee devices as their batteries run out and am very happy with this choice…Zigbee devices are much, much cheaper so that the price of a new battery + whatever I get for selling the ZWave device online pretty much covers the cost of the upgrade to a Zigbee device.

And make no mistake, it really is an upgrade, mainly due to DeConz. In DeConz, if I want to eliminate a node I click on a red X and it’s gone from everywhere - DeConz, HA, etc. It also has a network map which makes troubleshooting any placement issues very easy. This functionality in OpenZWave is either non-existent or extremely buggy.

Since the control panel is still being worked on, you can use mqtt commands listed here.

Once the control panel is done, you should be able to do everything in that list from Home Assistant.

Also a nice visualization card is available:

1 Like

Thanks, I’ll look into the mqtt stuff for waiting-time urgent functionality.
I’m already using the visualization panel. It’s very nice.

I know about deConz and that stuff, and I really like it.I have some 60 zigbee devices (at last count) connected to it.
But I have twice that many (maybe more) in zwave, so moving everything to zigbee is too much.
And I like the way OpenZWave integrates with HA.
The only real zwave problems I’ve had are with the old HA integration.
OpenZWave is very stable for a beta. But there are a few things I still need.

Problem in OpenZWave admin:
I’m trying to configure a send interval for an aeotec smart plug.
Now it’s impossible to set it to anything other than 0!
Trying to input 300 gives 00, which isn’t what I wanted…
The other parameters can be set to any value.

There’s a bug for that. https://github.com/OpenZWave/ozw-admin/issues/33

Have you tried using the ozw.set_config_parameter service call in HA instead?

Ok. I should have checked, of course.
Using ozw.set_config_parameter with parameters
node_id: 14
parameter: 111
value: 600
instance_id: 2
gives this message: “ozw/set_config_parameter ‘NoneType’ object has no attribute ‘type’”
What’s missing?

The message means that HA could not find the config parameter value based on the node, parameter id and instance id. Instance id 2 is the correct ozwdaemon instance?

Can you post the MQTT (to a pastebin) for that node or value? You can get a dump from HA, or use MQTT Explorer and find the value.

mqtt.dump

topic: OpenZWave/2/node/14/instance/1/commandclass/112/value/#

Here it is.

After doing the mqtt.dump, does the service call do anything different?

Just to add, I am getting exactly the same issues as @helgemor

Can’t set the interval via UI or service call with same error. I have also tried excluding, resetting and adding the node again with no joy

I believe there is a bug in the upstream module that handles the commands.

You can use the setvalue MQTT command for now. Use MQTT Explorer or similar and navigate to find the ValueIDKey for the config parameter. Then publish the setvalue command with the desired value.

Do you have an example on how to use that command please?

May I ask what the progress is looking like? Any ETA?

No idea, I just know cgarwood’s working diligently on getting it going as his free time permits.

3 Likes

No idea, I just know cgarwood’s working diligently on getting it going as his free time permits.

To be clear, he’s the maintainer of the integration, not the qt-openzwave backend. The development of qt-openzwave has been stalled for some time as the maintainer deals with some personal things, apparently, so there is no ETA on anything past the integration being fixed. cgarwood can improve the integration but he can’t do anything about the upstream bug mentioned, as an example.