I am using the /testforblock command on a command block to test for a PRESSED button.

The command is able to identify only the block but not able to identify whether or not it has a pressed or non-pressed BUTTON on the block. Last week the command WAS able to identify if there was a BUTTON on the block at a certain location.

For example, the command I put into the command block (repeating, always active) is:

/testforblock 196 68 346 birch_button 12

I put a birch button on a cobblestone block at that location.   The output reads something like:

"The block at 196,68,346 is Cobblestone (expected:Birch Button)."

IF I change the command to /testforblock 196 68 346 cobblestone 0, then the command block triggers a redstone signal through a comparator because it is able to detect just the cobblestone block.

SO, in the past, the TESTFORBLOCK command would be able to test for the BUTTON on the BLOCK in bedrock and check for the corresponding DATA VALUE to see if the birch button was facing up, down, north, south, east, west, AND whether it was PRESSED.

ie.

Not pressed:

East: 1

West: 2
South: 3
North: 4

 
Pressed:

East: 9
West: 10
South: 11
North: 12

HOWEVER, now the TESTFORBLOCK command is only identifying the block but not the BUTTON on the block.

The TESTFORBLOCK command looking for a pressed button literally worked 1 week ago.  Somehow it is no longer working. 

Here is a Youtube link to a video from 2017 showing how to program for a floating button on a block with TESTFORBLOCK command block:

https://www.youtube.com/watch?v=GppLqhVKqx4&list=PLM13skzGjPLHi6IPzdj6ID-RuzvpAAe2O&index=32&t=0s