OZW: Need a way to poll nodes like refresh_node from old Z-Wave integration

Hippo · August 10, 2020, 6:45am

I’ve got some Neo Coolcam switches that don’t send an update when operated manually. At the moment I’m polling them every minute 24x7 from a little script using MQTT. I’d prefer to be able to poll them from Home Assistant, so I can trigger the polling on a scene change or automation. I think the old Z-Wave integration had a refresh_node service or something.

Hippo · August 10, 2020, 4:59pm

The script I use publishes to the MQTT topic OpenZWave/1/command/requestnodedynamic/ and the payload is simply ‘{“node”: $node_id}’

firstof9 · August 10, 2020, 5:06pm

Or you could enable polling on those valueIDkeys?

github.com

OpenZWave/qt-openzwave/blob/89cc0d86c983101aacd89c780bae18bb3dffe9b4/docs/MQTT.md#enablepoll

MQTT Client for OpenZWave
=========================

Docker Repo: https://hub.docker.com/r/openzwave/ozwdaemon

Make sure you have create a local folder where ozwdaemon can store the config files etc for your installation. In this example, /home/ozw/config/ is on your local machine. 

If you are using Secure Communications, setup a Docker Secret:
```
printf "0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0A,0x0b,0x0c,0x0d,0x0e,0x0f,0x10" | docker secret create OZW_Network_Key -
```
* replace the Hex String with 16 Bytes to use as your Network Key.

Start a container with the following command line:
```
docker run -it --security-opt seccomp=unconfined --device=/dev/ttyUSB0 -v /home/ozw/config:/opt/ozw/config -e MQTT_SERVER="10.100.200.102" -e USB_PATH=/dev/ttyUSB0 --secret OZW_Network_Key openzwave/ozwdaemon:latest
```

* Update `MQTT_SERVER` with the IP address of the MQTT Server and all `/dev/ttyUSB0` entries with the path to your USB Stick.
* If you are not running with a ZWave Network Key, remove the `--secret OZW_Network_Key` command

This file has been truncated. show original

Hippo · August 11, 2020, 9:26am

Thanks for the pointer. It looks like a simper way of doing polling but I would prefer not to do polling but have some way of querying the node as part of an automation. What happens currently is if I manually switch on a light and it doesn’t update hass then I can’t switch it off from hass because hass still thinks it’s off. If I run polling then hass is up to date after the polling interval and I can switch the light off.

What I would like to do is have my automation for switching the light off do the following:

Switch the light off
Query the node
Wait a bit for the node to refresh
Switch the light off again
That way I get the instant off when hass thinks the light is on, and a delayed off if hass thinks the switch is off but actually on.

I can actually do this now by using a shell_script in the automation but it would be a lot nicer if I could just call ozw.refresh_node

mdamen · October 31, 2020, 3:21pm

Did you find any good solution to this? I am also looking for the old zwave.refresh_node or zwave.refresh_entity functionality with the OpenZwave (Beta) integration to get my fibaro heat controllers to work properly.

firstof9 · October 31, 2020, 6:39pm

Until the service is programmed in you can utilize the mqtt command requestnodestate

Hippo · October 31, 2020, 9:46pm

I wrote a script to talk to the mqtt server directly. It’s a bit heavyweight as it figures out which devices to query just in case they move around. It works by looking for a certain manufacturer and product ID so you should change those to match your device. Or just type in the node ID. It’s at https://corky.co/update-neo-switches

Dayve67 · February 1, 2021, 6:01pm

Would you have a sample on how I can do the command?

firstof9 · February 1, 2021, 6:04pm

topic: OpenZWave/<instance>/command/requestnodestate/
payload: { "node" : <node id to refresh> }