Split out remotes as remote about hue-sensors-hass

[robmarkcole]

OK remotes are treated as sensors by the API, so just keep them as sensors.

https://developers.meethue.com/documentation/sensors-api

[wouterbulten]

Hi @robmarkcole,

Did you solve this in the end in HA itself (as you closed the issue)? I'm now encountering a related issue that I can't run an automation on a state change if the previous button press had the same value.

As example: I would like to change the state of my home based on the hue remote. The 'off' button could for example first start a "going to bed" mode and then with a second press (on the same button) disable all the lights. With the current implementation I was not able to capture this second event (as the state goes from "4_click" to "4_click". Any thoughts?

[robmarkcole]

Hi this ‘issue’ has been discussed on the forums before and resolved so that’s the best place for a solution.

This component can be rewritten and added to HA now the changes to the hue hub have stabilised. It’s a big job so putting it off..!

[Mariusthvdb]

This component can be rewritten and added to HA now the changes to the hue hub have stabilised. It’s a big job so putting it off..!

Hope you postpone some more, since the changes haven't stabilized completely yet (understatement ..)
hue.hue_activate.scene and asyncio.timeouterror are still unresolved issues, which are not tackled yet in the upcoming .70 release... Hope anyone is having this on their list at all.