close-issue-app[bot]
commented
1 year ago This issue was automatically closed because the issue template was not filled out or because you have not confirmed you have read all parts of the checklist. To ensure we are able to properly support you, please make sure that you are posting in the right place and to fill out the issue template so that a bunch of standard questions don't need to be asked again each time. Thank you for taking the time to report a bug/feature/help request, hopefully it can be resolved soon. This issue will not be reviewed, so if you need further assistance, please create a new issue, following the template.
Is your feature request related to a problem? Please describe. Trying to emulate a MiLight remote to pilot a sidoh/esp8266_milight_hub I have found that the specific remote I've been using is not within the list. Currently esp8266_milight_hub supports it, so if I call the API passing FUT091 as remote all is working, but diyHue currently does not permit to choose that remote type.
Describe the feature that you would like to be added It would be great to have within the list of emulated remotes also FUT091/b2.
Describe alternatives you've considered As the difference from a CCT remote is only due to the label passed within the API call, I'm thinking about using nodered in the middle to change that value. I have also the json and json.map chunks where remotes list is, added the FUT091 label as a new choice and launched diyHue (without dockerizing it) and it works like a charm, but I'm not sure directly editing those files is the right way to do the things. In case someone can suggest me the right way to manage webUI changes, I could apply them on a fork and post a Pull request after a full test.
Describe your use case for this feature Using Hue app and Alexa to manage MiLight led strips controllers, maintaining the use of the FUT091 remote already configured and in use in my home
Checklist
Additional context