It will only work if you are transmitting the parameter change at exactly the same time that the sensor has woken up to receive hub communications.
The biggest engineering challenge for devices of this type is getting the batteries to last about 12 months. So these devices are designed as “sleepy“ devices which means they sleep most of the time. They wake up for only a millisecond or two at a set interval and evaluate the environment to see if motion is happening. If it is, they send a message to the hub. If not they go back to sleep.
Configuring the parameters requires that the sensor listen for transmissions from the hub, which is a different kind of activity, and then process them. This is quite a battery intensive action, much more so than just The regular check for motion. This is why in this particular case the manufacturer has set the device to only listen for hub transmissions twice a day. And you have to catch it right at that time.
If you have an important reason to set the parameters, you can also manually wake it up by pushing the button on the side five times, but that doesn’t fit your particular use case.
Battery operated Z wave devices are normally only configured at the time that they join the network, unless it’s some other one time event like setting up an association, which is what the manual button is for.
So… I’m not really sure what you’re trying to accomplish here. Doing a full reconfiguration twice a day is likely to run your batteries through, my guess would be they will only last three or four months if you have that setup. So it’s not something most people would choose. But it’s your sensor so if you want to do that, you can.
However, you have to get the timing exactly right so that you are sending the reconfiguration request during the little tiny time window that happens every 12 hours. If you send it at any other time, the sensor is going to be sleeping and it won’t hear the configurations request.
@krlaframboise has done a lot with this model and should know better if there is any way programmatically to synchronize this other than just trial and error.
But I think it’s going to be tricky to set up and it’s going to dramatically shorten the battery life compared to just putting a time filter on the automation.