Minecraft command blocks – Detecting powered button/lever

You must add the id:FallingSand tag to each block you want to stack. So, you're command should be:

/summon FallingSand ~ ~1 ~ {Block:redstone_block,Time:100,Riding:{Block:command_block,Time:100,TileEntityData:{Command:/say test},id:FallingSand}}

Explanation

It is like when making any entity riding another entity. When not adding the id tag to the stacked entities (FallingSand blocks), the command block will not know which entity it should summon that the FallingSand is riding on. Like for example, when you want to make a Zombie riding a Bat and do /summon Zombie ~ ~ ~ {Riding:{}}, it will not know that you want the entity that the Zombie is riding must be a Bat, but when you do /summon Zombie ~ ~ ~ {Riding:{id:Bat}}, it will know that the Zombie should ride a Bat. The FallingSand is used in the same way as any other entities when riding each other.

Without the use of redstone and block updates, it can become a bit complicated to replicate it. You will need to check the SuccessCount value of the command block running the initial /testforblock command to determine when the block is no longer there. Image setup:

1. The initial /testforblock command, checking for the stone button.

   /testforblock -89 57 678 minecraft:stone_button 5
   

2. Conditional. If the /testforblock command succeeded, set the impulse command block (#5) to have an auto tag value of 1, which causes it to run its command. Unlike a repeating command block, it will only run its command a single time. auto has to be set back to 0 before it can activate again. Change "X Y Z" to the coordinates of the impulse block.

   /blockdata X Y Z {auto:1b}
   

3. A secondary /testforblock that checks the SuccessCount tag value of the repeating command block. If the value was 0, that means the stone button was not at the location, which means the impulse command block must have auto set back to 0.

   /testforblock X Y Z minecraft:repeating_command_block -1 {SuccessCount:0}
   

4. Conditional. If the SuccessCount value was indeed 0, set the impulse block's auto tag value to 0.

   /blockdata X Y Z {auto:0b}
   

5. This would be the command you want to run a single time when the stone button is at the location, but will be able to run a single time again if the stone button were to be removed and placed back down.

   /say Test
   

The benefit of doing it this way is to reduce the number of block updates occur, as /blockdata does not create block updates. The reduction is good for server performance.