Some background, if you care: Hubitat’s button capabilities don’t technically require implementing
released() commands, but most devices, apparently by convention, do. (There was some debate about this in when the capabilities were debuted, so this could also be leftover from that.) What they do is simulate a “digital”/virtual press so that you can, for example, trigger an automation that would ordinarily require a “real” button press by way of these commands instead. More for Inovelli than for you, in case they aren’t familiar.
Looking at Inovelli’s drivers for the products I assume you might be talking about, the Red Series switches and dimmers, I seem to remember their drivers doing this at one point. And it looks like all the code is still there, just commented out — and it’s also implemented a bit differently, but again, the above is just a convention and not a requirement of any “standard” Hubitat capability (e.g.,
PushableButton). It appears that you could get this functionality back if you uncommented this block of code towards the beginning of the file (this is from Inovelli’s LZW31-SN driver, but I imagine the others are similar):
(and by “uncomment,” I just mean "remove the enclosing
Again, at least as of the current version of their driver code, this will still work simply because these methods are still defined later on in their code. And you’ll have to use the commands as written, like
pressUpX1() instead of
push(1) or RM’s built-in action that does the same, which means you’ll also need to use Rule Machine’s “Custom Action” type to execute these methods. The “mapping” should otherwise be straightforward from the custom command names.
So while Inovelli will have to comment on whether they want to implement this in their driver by either un-commenting the above or switching to Hubitat’s conventional-but-not-standard commands like
hold(), the above should work either way with very little modification on your part.
(PS - I also wrote a new-ish custom driver that implements these commands and I think is as Hubitat-ty as possible while still giving “access” to all device features, but the button-number mapping is different from Inovelli’s. I could share that with you if you were interested, or I might post about it sometime here…)