Extend Command Retry Logic to Valves?

[aaiyar]

@mike.maxwell

Will it be possible to extend command retry logic to valves?

I am currently doing this via repeats in rules to ensure that valves are open or closed, and it would greatly simplify my automations if command retry logic could be used.

Thanks!

[mike.maxwell]

Yup, I can add them, open and close only, ignoring anything switch related. Do they report immediately on receipt of command?, or is there a transition time involved..., and if so what's a safe value.

[aaiyar]

Thank you!

Everything below is for the Zooz Titan Valve Actuator, with the built-in driver for it.

@mike.maxwell

Do they report immediately on receipt of command?, or is there a transition time involved

There is a transition time involved - whether the valve is paired using Z-Wave or Z-Wave LR.

@mike.maxwell

if so what's a safe value.

Based on the event log below, I would suggest that 10 seconds is a safe value between receipt of command and the status changing:

[hydro311]

I'm curious how a retry may play out WRT to the Titan's (optional) self-test... That test just moves the lever ~1/4 open, then back (not full open).

Now I can't recall approx when my self-tests run, so I'm of course not able to find any log activity that would indicate what those commands look like

[aaiyar]

I'm not seeing self-test associated status changes for any of my three Titan actuators. Maybe @agnes.zooz can comment on whether the self-test generates z-wave events.

P.S. Even if it did generate events, the likelihood of the testing time (which occurs once in 14 days) intersecting with a hub-generated command is kinda slim, no?

[mike.maxwell]

Update should be in 2.4.1.168, there was a bug in it in 167

[jtp10181]

I do have on my long to-do list to properly implement supervision in my ZAC36 driver. It actually sends back a supervision reply with "working" status (per z-wave spec) so I would know right away if the device got the command or not. If no timely response I could send a retry. Potentially a little more reliable than the platforms retry.

I fleshed it out better for my universal driver (vs what was in the dimmer/switch drivers) so I should be able to take most of that and use it on other drivers now.

[Ken_Fraleigh]

FYI: the Leaksmart valve driver and @kkossev ’s tuya valve driver both implement a switch on/off as well as valve open/close, so I have been using the command retry with them since it rolled out to beta. Not sure what the change will mean for these devices.