Reply to thread

Message: <blockquote data-quote="Rick164" data-source="post: 1110076" data-attributes="member: 17766">Will look into this, thought it wasn't possible as I didn't see any mention in the Q42 API.The ids should be listed in the Philips Hue App as follows:<img src="http://i.imgur.com/DlkLfLH.png" alt="" class="fr-fic fr-dii fr-draggable " style="" />Gonna see if that is possible as the tabbed layout does have some restrictions but should be able to anchor the output log to a groupbox.The config screenshots look ok and you detailed the steps nice and clear, the initialize mention does mean it was able to connect to the Hue Bridge.You might try to let it register again to make sure it has registered correctly the first time, since the scenes retrieval worked it probably is already registered though.Currently there's no debug option after we send colors as I dropped the callback function of the bridge (slowed down color changes), will see if there's a function to check command status more reliably without slowing down color changes.It might be because they're bulbs as they have different color settings but they should at least turn on, are they the Bulb Lux or Bulb Color?Btw what I did notice about your settings.xml is that it doesn't list the LED ids which probably means AtmoHue hasn't restarted yet or something went wrong during save, could you upload a new copy of your settings.xml?Currently rewriting the save/load parts and cleaning up the code so should have new version this weekend, gonna see if I can include an auto-discover led devices as well as some more debug functions./EDIT: attached a test version that has a "Get LED IDs" button in the experimental tab which will output all found devices in the log window.Also found a <a href="https://www.homegear.eu/index.php/Philips_hue_Device_Support_List" target="_blank">partial device type list</a> so based on that I could automatically add them to the LED id list but needs some more testing.</blockquote>

Verification