open-zwave off delay timer doesnt work

[tjabas]

Hi!

im still using open-zwave on a aeotech gen 5 stick, i havent migrated yet to the new Z-wave js format.
i really dont have the time to do it, i guess i need alot of time to fix it since i have over 100nodes.
anyway, i have on some swithes set a off delay, but for some time these timers doesnt work anymore, i also get "a dns error has occured"

any sugestion how to fix this without migrating to the new js,
im on the latest stable version, but im thinking of installing the beta to see if it will work with the timers, or do i loose open-zwave?

best regards

[waltervl]

Off delay should work in stable. No need to go to beta for this.
Is it not working at all, so for every switch or only for zwave switches? What kind of delay do you have (seconds, minutes or hours)?

DNS error is internet access related so seems unrelated to zwave. What gateway is reporting this error?

[tjabas]

i think its just for my z-wave switches where the timer doesnt work, it has been working , but lately it has stopped working, it seems like if i restart domoticz it will work for a while, and also some z-wave switches doesnt change state if i push the pysical wall button, if i push the wall button to on, the switch in domoticz doesnt change to on, but still if i push the switch in domoticz it works, so its strange, maybee i should activate polling for these switches that doesnt work properly?

[waltervl]

I do not use Zwave so unfortunately I cannot assist here...

[lost]

also some z-wave switches doesnt change state if i push the pysical wall button, (...) maybee i should activate polling for these switches that doesnt work properly?

IMO, you have a general reliability issue in your zwave mesh network. Activating pooling will increase traffic so may even make it worse.
I'm on one of latest 2023.1 betas, still on OZW as you are, without issues.

You may monitor your logs for timeout concerning zwave devices, and for each node that shows heavy timeout figures go to OZW panel & do some neighbor node update on closest working nodes, wait a bit (let's say 1 or 2mn), proceed with next & finish with the heavy timeouts one. That's less stressful than a full network heal TBD only if targeted neighbor updates does not solve issues.