And combinations ... I have one bloom and one stripe at the moment connected.
Support for Philips Hue System (3 Viewers)
- Thread starter boldie
- Start date
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
Combinations should be easy to do as well 
, one thing I noticed about the bridge is that if you use one destination device( led 1 for instance) its near instant but multiple causes a slight delay even when I group the commands so best to test with one led device atm.
Only issue might be to figure out which color corrections to use for the strips as they aren't listed here:
https://github.com/PhilipsHue/Phili...tionDesignNotes/RGB to xy Color conversion.md
Even with 2 identical blooms in the kit I'm already seeing a color difference, so much for Philips quality
, one thing I noticed about the bridge is that if you use one destination device( led 1 for instance) its near instant but multiple causes a slight delay even when I group the commands so best to test with one led device atm.Only issue might be to figure out which color corrections to use for the strips as they aren't listed here:
https://github.com/PhilipsHue/Phili...tionDesignNotes/RGB to xy Color conversion.md
Even with 2 identical blooms in the kit I'm already seeing a color difference, so much for Philips quality
Last edited:
Autsch - really - same device differnt coloring? That's bad ...
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
The Atmowin monitoring is still too slow and don't think that will work for now, new version below which has the color calibration and also fixed the color rotation.
Gonna be adding it to AtmoLight this week and see how well it runs there but so far its far from ideal as with fast scenes it will never be able to keep up and might ruin the experience.
Will let you guys know if it works better there
Changelog
- Added color calibration based on http://stackoverflow.com/questions/22564187/rgb-to-philips-hue-hsb/22649803#22649803
- Fixed color rotation
Download AtmoHue 0.0018
http://1drv.ms/1rSDcxw
Gonna be adding it to AtmoLight this week and see how well it runs there but so far its far from ideal as with fast scenes it will never be able to keep up and might ruin the experience.
Will let you guys know if it works better there
Changelog
- Added color calibration based on http://stackoverflow.com/questions/22564187/rgb-to-philips-hue-hsb/22649803#22649803
- Fixed color rotation
Download AtmoHue 0.0018
http://1drv.ms/1rSDcxw
wow - significant faster - but only when using 1 light - as soon I select all the speed drops to ~2000ms. Question - when selectin "All" is it using Lamps 1 to xxx even if there is only 1 and 2 availible? I have seen in the Android apps that you need to select the lights to be used.
But - over all - a big step in th right direction - THX.
But - over all - a big step in th right direction - THX.
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
Just finished the first rough version of AtmoLight with Hue support and its working great so far even with fast scenes , very little lag and set it up so new data is delayed 300ms and transistion speed is also 300ms (will be configureable)
Made it so that AtmoLight parses the commands to AtmoHue as .NET 4.5 was required so had to come up with a workaround but this actually works very well already.
Only got to figure out why it's so much slower with multiple devices, also in the UI there are gonna be select boxes for the leds you want to enable with the specific types per led
When "All" is selected it pushes it to all leds and not specific leds that exist on the bridge, which might be reason its slower but will have to check.
, very little lag and set it up so new data is delayed 300ms and transistion speed is also 300ms (will be configureable)Made it so that AtmoLight parses the commands to AtmoHue as .NET 4.5 was required so had to come up with a workaround but this actually works very well already.
Only got to figure out why it's so much slower with multiple devices, also in the UI there are gonna be select boxes for the leds you want to enable with the specific types per led
When "All" is selected it pushes it to all leds and not specific leds that exist on the bridge, which might be reason its slower but will have to check.
Last edited:
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
After some testing and help of @Lightning303 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 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.
, 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 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.
Last edited:
A hard working man you are (and lightning too of course). Thx for your effort... Looking forward to test it.
Would be interesting to see how good this system works in combination with their own Ambilight...
Would be interesting to see how good this system works in combination with their own Ambilight...
Doesn't work with the last provided version - it only takes the first one set - so using 1,2 results in 1 used 2 ignored and 2,1 in 2 used 1 ignored.
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
Thanks, fixed in the below version.
Also looked out how we could handle multiple led types in a single command and that one is gonna be trickier than I thought as we need different color coordinates per command, what is possible is to make a new color command per led type but that might slow down processing on the bridge.
Will be adding that a bit later on but need to think about how we can best handle that.
Changelog
- Fixed multiple led destinations
- Additional changes to support AtmoLight but more on that later
Download AtmoHue 0.0019
http://1drv.ms/1tUHcn0
Also looked out how we could handle multiple led types in a single command and that one is gonna be trickier than I thought as we need different color coordinates per command, what is possible is to make a new color command per led type but that might slow down processing on the bridge.
Will be adding that a bit later on but need to think about how we can best handle that.
Changelog
- Fixed multiple led destinations
- Additional changes to support AtmoLight but more on that later
Download AtmoHue 0.0019
http://1drv.ms/1tUHcn0
Last edited: