close-issue-app[bot]
commented
2 years ago Hi there. Thank you for filing this issue. Unfortunately, we cannot help you, as you haven't sticked to the provided template and/or have not provided all information requested. Consequently, this issue has been closed. We're more than happy to help out where we can once you raise a new issue containing all requested information in the requested format. In this regard, please take note that: - read the template thoroughly - all given header lines (starting with ###) must not be deleted - everything enclosed by <!-- --> is intended to give you guidance and should be replaced by your input specific to the issue - Listings regarding your environment must be filled out completely where applicable (bug reports and user questions). - Not following the template or providing insufficient information can still implicate manual closure. - Anything that is not clearly a bug can still implicate manual closure. For support we recommend the forum: https://forum.phoscon.de So please, first help us a bit to help you!
Describe the bug
Setting hue through REST API is not working for those RGB candles:
Setting hue using the following command does not work (Even though "success" is being replied)
PUT <DECONZ_IP>:<DECONZ_PORT>/api/<username>/lights/8/state { "hue": 12345 }Return value:[{"success":{"/lights/8/state/hue":12345}}]Lamp status: Color is not being changed.Setting hue in deConz directly using the
MOVE TO HUE \<value\>works fine however.Setting the color using XY in REST API works perfectly.
Steps to reproduce the behavior
PUT <DECONZ_IP>:<DECONZ_PORT>/api/<username>/lights/8/state { "hue": 12345 }Expected behavior
Color changed exactly as with MOVE TO \<value> in Deconz
Environment
deConz Version: 2.13.02 / 10.11.2021 Conbee II Firmware: 26720700