This really seems like a better automation for Button Controller over Rule Machine.
The Button Controller editor is nearly identical to that of RM, so if you like RM, you’ll like this, too. It just makes using different triggers for different button events – as you are trying to do – easier, while still keeping everything under the same “parent” Button Controller app if organization was your concern with separate RM rules. I would suggest one of these approaches for both the reasons already discussed and the general observation, through years of helping people with Rule Machine myself, that multiple, simpler rules are almost always easier to write and troubleshoot compared to fewer, more complex rules.
It does (a read of the Rule Machine documentation will probably be helpful), but it depends on the driver to set this (optional) value. Apparently, Inovelli’s custom driver does not – assuming you tested after an actual trigger event (like %value%, this does not get set by any other means, as in my original response).
But if you do go back to this approach … no, this really shouldn’t happen unless the driver reports that value for this event. You could try re-creating the rule just in case something else, like maybe a trigger you once had but removed, is causing problems? Or check “Event” history on the device to verify that this isn’t really happening (might have had you do that above, I can’t remember…); if so, that would be a driver problem, though an unusual one…