Autoupdate’s rejection of the command is usually an indication that the Item is linked to one or more channels that are broken in some way, and so autoupdate considers the command cannot be carried out.
I thought it was the OFF command you are having trouble with, see any of those? No OFF command to Item, no OFF for binding to process.
EDIT - ah wait, Zigbee binding. This has some unusual behaviour - it vetoes autoupdate for some devices as a fallback mode, which explains the non-prediction.
What should happen later, is a real update comes along from the device.
Worth a read -
Possible circumvention is at end of thread.