As @Burningstone said, it’s MUCH easier to help when you post code in a more readable fashion.
That being said, having experience with these devices, I know what the issue is. The way zigbee2mqtt works with these devices is that it sets the state to “button_1_single” and then IMMEDIATELY sets it to an empty string. In the split second it takes to get from the trigger of your automation to the condition in your choose, the state is no longer what you expect it to be.
The work-around is to create a separate automation with the state you expect listed in the trigger instead of using choose. Alternately, you can use the trigger values in the choose conditions, instead of the entity_id, but I don’t know the syntax for that off-hand because I don’t use it. Choose actions are difficult to read so I avoid them whenever possible.