Reply to thread

Message

<blockquote data-quote="Rick164" data-source="post: 1107365" data-attributes="member: 17766">After some testing and help of [USER=97876]@Lightning303[/USER] I worked out most of the bugs <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> , also squeezed a bit more performance out of the Hue Bridge so we get faster transitions.To fix the slow multiple devices input the configuration option &quot;Hue Lights to use&quot; as &quot;1,2&quot;, that will enable led id 1 and 2 at the same time but you can use any combination so long as it's comma seperated.This way you will not get the delay anymore , as expected without the list of ids specified the bridge would look those up every time resulting in the added lag.For the multiple devices part I looked a couple of things up and it seems the Hue Bridge can do 30 commands per second in total so if you have 3 led devices it's 10 commands per second etc etc.That would mean with 3 devices you can do 100ms at best which is still good enough but there is also some overhead so for now the sweet spot is in the 200 to 300ms range.Lower than that sometimes flooded my bridge and that was with only 2 blooms, why Philips made these things so low-end is beyond me but I guess it works good for most of their users.The new scheduled AtmoLight release is gonna be soon™ (no exact date yet) which is gonna include Hue support, the setup is gonna look like:- installed AtmoHue and configured it for your bridge same as now, preferable on the same machine as Mediaportal.- Configure Atmolight, enable Hue and change AtmoHue IP only if it's not on the same machine.- AtmoLight will have a couple of checks and drop connections to the Hue if it's not playing any video as to not completely lock up your Bridge device.</blockquote>

[QUOTE="Rick164, post: 1107365, member: 17766"] After some testing and help of [USER=97876]@Lightning303[/USER] I worked out most of the bugs :) , also squeezed a bit more performance out of the Hue Bridge so we get faster transitions. To fix the slow multiple devices input the configuration option "Hue Lights to use" as "1,2", that will enable led id 1 and 2 at the same time but you can use any combination so long as it's comma seperated. This way you will not get the delay anymore , as expected without the list of ids specified the bridge would look those up every time resulting in the added lag. For the multiple devices part I looked a couple of things up and it seems the Hue Bridge can do 30 commands per second [B]in total[/B] so if you have 3 led devices it's 10 commands per second etc etc. That would mean with 3 devices you can do 100ms at best which is still good enough but there is also some overhead so for now the sweet spot is in the 200 to 300ms range. Lower than that sometimes flooded my bridge and that was with only 2 blooms, why Philips made these things so low-end is beyond me but I guess it works good for most of their users. The new scheduled AtmoLight release is gonna be soon[B]™[/B] (no exact date yet) which is gonna include Hue support, the setup is gonna look like: - installed AtmoHue and configured it for your bridge same as now, preferable on the same machine as Mediaportal. - Configure Atmolight, enable Hue and change AtmoHue IP only if it's not on the same machine. - AtmoLight will have a couple of checks and drop connections to the Hue if it's not playing any video as to not completely lock up your Bridge device. [/QUOTE]

Verification