I’m afraid you have the wrong idea. Any type of button like this doesn’t give device triggers if connected through ZHA. It’s confusing, I know, but this is not how it works. The button presses give ZHA events, which you have to enter as manual events if you want to trigger on them. Which events go with which button is often poorly documented and you have to go to the developer tools to snoop them. It’s definitely a “what the heck” for many, and it works like that for all the zigbee buttons. Fortunately, most buttons have some early adopter that does the work for you and writes a blueprint.
Apparently my knowledge is outdated. I checked, and some of my other brand buttons do have the triggers listed with the device. I don’t know exactly know where that is coded. I guess the problem with this device is that it does not send unique codes per button, without knowing the history the event will not tell you if the left or right button was pressed.
Anyway, the device can definitely work with HA, you just need to trigger on the events and decode them. The blueprint will do that for you.
I guess it send, because we can see on the “Activities”:
innr RC 250 - Remote Control Off event was fired
13:12:18 - 11 seconds ago
innr RC 250 - Remote Control Step event was fired with parameters: {'step_mode': <StepMode.Down: 1>, 'step_size': 51, 'transition_time': 3, 'options_mask': <OptionsMask: 0>, 'options_override': <Options: 0>}
13:12:22 - 7 seconds ago
innr RC 250 - Remote Control Step event was fired with parameters: {'step_mode': <StepMode.Up: 0>, 'step_size': 51, 'transition_time': 3, 'options_mask': <OptionsMask: 0>, 'options_override': <Options: 0>}
13:12:20 - 9 seconds ago
If HA recognize the ON/OFF, StepUp and StepDown, it should trigger any event based on them, nativelly, as it’s happening on buttons from Sonoff, Philips, etc.
Well yes, that would be great if someone would fix that. But nobody has stepped up to volunteer for the task, unfortunately. That’s open source software, you rely on volunteers fixing things. There are 290 open issues in the device handlers section alone right now.
Edit: I think what is needed is a quirk that implements the device automation triggers. I added a comment to the github issue.