Switch.turn_on action for zwave switch fails if within an automation after Zwave JS UI 4.0 installed. No problems with 3.24 version. Here is message:
Error while executing automation automation.garage_light_on_when_door_opens: Unable to set value 48-37-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the message after 3 attempts (ZW0202)
I’m seeing the same thing across many devices.
Known issue in Z-Wave JS v15.
For me this only fails in an automation. The same action works perfectly alone or in script. Reverted to 3.24 and all is well.
4.0.1 continues to fail. Back to 3.24.0.
Same issue here. Suddenly experiencing errors that I never had before. Re-interviewing devices seems to make some change.
v4.0.1 did not have any relevant fix for this problem (not even sure why it was released). You’ll have to wait for a potential v4.0.2 that includes driver v15.0.3.
Well, re-interviewing did not make a difference. 
Still saw errors coming in. Downgraded to 3.24.0. Going to keep an eye out if this is the fix for now.
Restoring to 3.24.0 has fixed the automation problem. Everything is running smooth again and no errors anymore.
Haven’t tested the latest upgrades yet as I have not much time to check if it all keeps working. Has anyone else tried the latest updates?
Edit April 5: Finally had time to do a new upgrade and test it. Automations seem to keep working with the new version.
Agree. 4.04 version is OK.
Problem has occurred again. It went ok for a few days and suddenly after yesterday, the errors keep coming again. Back to 3.x it is.
Yeah, seems that this is also the reason of my problem - I have few sirens which act as switches (and the switch is the only control they have, and in automation I have literally no actions available for these devices:
Strange. I do all my automations using yaml manually.
In my case the automation uses the same script for turning on and off a switch. That works most of the time. Except for when more scripts should be executed at the same time.
Before I go for downgrading to version 3.x, I’ll check if using group (I have my sirens grouped) works, or if using action instead of device works in that case.
Edit: groups still works, switching devices from the dashboard as well, only atomations have this broken. But only for certain devices, not all of them
Issue seems to be fixed in 4.1.0 of the addon.
I just did a test and all automations worked fine. No errors when executing the commands at the some time. Hopefully it stays this way. 
It didn’t solve my issue, still can’t select any actions for some devices.
However, they work from dashboard, and i.e when calling an action on group which includes them.
Maybe it is a bug in automation themselves?
Strange
I thought the problem was fixed. It seems that way, but am getting errors again. I’m back at 3.24.
