Thank you for having posted the solution!
Amusingly enough, I was bitten myself by the `as`/`at` clause of the execute command yesterday. And despite that, I didn't pinpoint a similar issue in your command. I definitively need a lot more practice with Minecraft commands!
Actually, in your case, I suspect the following commands would do the trick too:execute as @a[x=-160,y=75,z=164,distance=..1] run setblock -153 75 165 redstone_block execute if entity @a[x=-160,y=75,z=164,distance=..1] run setblock -153 75 165 redstone_block
According to my (very recent) knowledge in that matter, I would favor the `if entity` version: I think the `as`/`at` versions may be less efficient, since they may potentially run the `setblock` command several times, once for each matching entity. Or am I wrong?
I don't know about this.
But in my case, it doesn't matter, since my setblock command sets a redstone block that triggers a fill clock to another system.
I will keep that in mind though for other uses. Thanks for sharing this!