Force update of zha remotes to make automation easier

[dmulcahey]

Description:

Because these are "remotes" and not true switches each button press should result in a state change. This may not be necessary once zha supports groups.

addresses: zigpy/zigpy#55

[balloob]

This is because a button/remote is represented as a binary sensor, that's wrong to begin with. Those should be converted to just fire events by the zha.py component and not be entities.

[dmulcahey]

@ballob I’m willing to fix the issue. Can you provide any guidance? Or is there a particular platform that has an example of how you expect this to be implemented? I understand that the implementation isn’t correct (I was kinda confused myself when I initially saw it) but I’m unsure of how to have a component that fires events without a backing entity.

[balloob]

I don't know how zha works, so I can only give you global guidance:

The logic should live components/zha.py. Listen to zha to when the button is pressed. When pressed, run hass.bus.fire('zha.button_pressed', { 'node_id': 'some_node_id' })

[dshokouhi]

@dmulcahey I use xiaomi switches with the xiaomi_aqara component. The switch will show up as a binary_sensor but that doesn't serve a purpose. All of my automations are based off the events that are sent to HA. deconz also does things in a similar fashion too.

[dmulcahey]

@balloob can you take a peek at #14902 and let me know if this is headed in the right direction? Thanks!