This is true. As a generic button controller you could control pretty much anything. It would be less intuitive to use the 4-way for buttons, but it would be doable. The problem is in the way the remote handles those presses.
The color control (left/right) sends a hue and saturation along a sliding scale from 0x0000 to 0xFFFF (or whatever the sane limits are). So we’d have to determine which direction the remote is moving and determine which button is being pressed from that. This would rely on a reliable “last state” value, which has proven to be a very unreliable thing to get from the platform lately. This could result in unexpected behavior.
The level control (up/down) sends repeated move level commands while held and a stop move command when released. The stop move command is probably what we’d want to trigger the action on (just using the move command would likely result in a lot of repeated button presses and would require some debouncing) Again, this depends on reliable “last state” and reliable message sequencing to know what button was just released and could be… unreliable.
So this is not really the ideal remote to use as a button controller, but it is doable. I’d be willing to help either way, just wanted to put that out there for the community in case anyone else had some input.
I’m now leaning toward the virtual dimmer/hue concept for my own uses. Would be good for the non-techies in the family to control Hues/Gardenspots/Lightstrips