Feature request - change response codes RWL

[Mariusthvdb]

Since the remotes.py is being rewritten at the moment, this might be a good time to restore the native events the Hue Api passes along, see https://developers.meethue.com/develop/hue-api/supported-devices/#supportred-sensors for the official documentation.

I've changed my local file to follow the api docs, which is like this:

    responsecodes = {"0": "_initial_press", "1": "_hold", "2": "_short_released", "3": "_long_released"}

Since the response codes were changed to:

def parse_rwl(response):
    """Parse the json response for a RWL Hue remote."""

    """
        I know it should be _released not _up
        but _hold_up is too good to miss isn't it
    """
    responsecodes = {"0": "_click", "1": "_hold", "2": "_click_up", "3": "_hold_up"}

my system (and I...) have always been confused about the difference between a click (initial_press), and click_up (short_released)

having the combos click/click_up and hold/hold_up would suggest there's only 2 kinds of clicks,
using the official button events makes the HA frontend clearer as to what really happend, and one can easily follow the action. Waiting for the second green led flicker initiates the hold or long_released

[Mariusthvdb]

just adding images to the above

this is what it looks like with the changes (btw I changed 'click' to 'tap' on the ZGP Hue tap, and adapted the icons to the most striking mdi representations I could find):

compared to the original using hold_up etc