You might do it with 3 macros, but yes, a toggle action would be much more convenient:
View attachment 94849
View attachment 94850
View attachment 94851
You might have to play with the "parallel" option, or perhaps use slightly different logic, to avoid having both the Enable and Disable actions run at the same time, in which case it probably *won't* do what you want. But I think you get the idea.
That said though, my experience in industrial controls, where a touchscreen button could easily control a motor the size of a house, says that toggle controls should be avoided if at all possible. Always use separate on and off buttons if you can, so that you know exactly what you're doing at all times and don't have to know anything prior to figure that out.
"Knowing nothing, you blindly push that button. You know which button you pushed, but nothing else. Now, based only on the button that you pushed (the button itself, not a label), what state is it in?"
That may seem contrived, but in the heat of the moment, it's surprisingly accurate. You're not reading in the moment, and you're probably not paying a whole lot of attention to the details that are going wrong. All you know is that you want X to be in Y state, and it has to happen NOW! If it already is, and you push a toggle button, you're going to break it even more.