AtmoHue - BETA - Philips Hue support for AtmoLight & AtmoWin (2 Viewers)

[zekaja]

Option 1 it is , new version of AtmoLight BETA and AtmoHue added to first post.
UI has gotten a little crowded so will combine the cleanup once I get the new listview (with in-line editing) working like it should.

/edit: Forgot to mention that when adding new locations and static colors you need to restart AtmoHue for now for it to show up in AtmoLight, will fix that in the next version.

Changelog

28-11-2014 - AtmoLight BETA & AtmoHue updated

AtmoHue 0.0.75

- Set active groups/locations for liveview via the AtmoLight context menu
- Set static color per group via the AtmoLight context menu

You need to re-add the leds and add locations and static colors (new setting fields) for both features to work, for now only local installations of AtmoHue are supported as it reads the config via xml.
The pull down menu when adding a new led ID will automatically list all the locations you have added to prevent typos.

AtmoLight 1.14.001.0 - BETA version

- Added new UI menu's for Hue, you need to setup the AtmoLight context menu (assign remote color key) for this to work, for troubleshooting the context menu there's a guide located here:

https://forum.team-mediaportal.com/threads/atmolight-1-14-0-0-2014-11-23.125633/#post-1076671

- Hue now has functions to read AtmoHue config (static color / groups)

This Works Really Really Well ..... Thanks Alot

 

[killer8]

I know but errors always look quite bad even when they do not harm. Would be nice to have a version with some more debug code to have a clue why the error appears exactly. Thank you

I agree .
Here is a version with a lot of debug logging in the frame grabbing part. Just copy the dll into plugins/process.
This version will output couple of lines every frame being grabbed. So, there will be a lot of spam, best to just try to reproduce the error with this dll and then use normal one again until its fixed.
You dont have to use watchdog, just have MediaPortal set to debug log verbosity and then i only need the MediaPortal.log when you reproduced the error .

I tried it but the error doesn't show up anymore. I don't get it but it seems to be gone now

I'm going to install the new atmoLight from this thread so I guess I can't use this anymore.

Option 1 it is , new version of AtmoLight BETA and AtmoHue added to first post.
UI has gotten a little crowded so will combine the cleanup once I get the new listview (with in-line editing) working like it should.

/edit: Forgot to mention that when adding new locations and static colors you need to restart AtmoHue for now for it to show up in AtmoLight, will fix that in the next version.

Changelog

28-11-2014 - AtmoLight BETA & AtmoHue updated

AtmoHue 0.0.75

- Set active groups/locations for liveview via the AtmoLight context menu
- Set static color per group via the AtmoLight context menu

You need to re-add the leds and add locations and static colors (new setting fields) for both features to work, for now only local installations of AtmoHue are supported as it reads the config via xml.
The pull down menu when adding a new led ID will automatically list all the locations you have added to prevent typos.

AtmoLight 1.14.001.0 - BETA version

- Added new UI menu's for Hue, you need to setup the AtmoLight context menu (assign remote color key) for this to work, for troubleshooting the context menu there's a guide located here:

https://forum.team-mediaportal.com/threads/atmolight-1-14-0-0-2014-11-23.125633/#post-1076671

- Hue now has functions to read AtmoHue config (static color / groups)

Great job, will give it a try and provide some feedback later[DOUBLEPOST=1417267459][/DOUBLEPOST]Two bugs and a feature request:

An error comes up when I change the config(for example I readded my leds, another time(with a restart in between) I deselected the checkbox for only setting brightness on first use) and click color test(see screenshot), it works when I restart atmoHue in between.

The led locations and static colors are duplicating like the leds did some weeks ago. I've added a config which shows this.

Can you add a set brightness field to the testing tab.

 

[Rick164]

Can confirm the first bug but the second one with duplicate leds I thought was fixed. what are the steps to get the leds to duplicate?
For brightness you mean for the custom color tests or just to test the brightness with the current color already set?

/edit: nevermind found the second bug

 

[killer8]

Just to send a brightness signal from the test tab. Like number field -> fill in 200% -> send and brightness of lights will go to 200%.

 

[Rick164]

Added new versions in the first post, has all the known bugs fixed and the option to set the brightness in the testing tab
Renamed the Hue UI messages in AtmoLight to make it a bit more generic for translating.

Changelog

29-11-2014 - AtmoLight BETA & AtmoHue updated

AtmoHue 0.0.76

- Various bugfixes
- New option in Testing tab to manually set brightness

AtmoLight 1.14.002.0 - BETA version

- Added Dutch translation and made the Hue UI messages a bit more generic

 

[zekaja]

Added new versions in the first post, has all the known bugs fixed and the option to set the brightness in the testing tab
Renamed the Hue UI messages in AtmoLight to make it a bit more generic for translating.

Changelog

29-11-2014 - AtmoLight BETA & AtmoHue updated

AtmoHue 0.0.76

- Various bugfixes
- New option in Testing tab to manually set brightness

AtmoLight 1.14.002.0 - BETA version

- Added Dutch translation and made the Hue UI messages a bit more generic

Very nice... No more duble leds here and the test knop works great!

Two questions I haven't figured out: How does sending colors to individual light work? and when screen turns black, can i get the lights to dim?

 

[Rick164]

When the individual led option is enabled it will apply the specific led options from the led config (different brightness/saturation etc..), there's one downside and that it has to divide up the commands which might introduce a small sync issue like the leds not changing color at the same time.

The black dimming option I looked at but the Hue bridge seems a bit picky about that, even when lowering brightness to 1 it would still light up a bit too much.
What I currently do with AtmoLight is send the Color Black which translates to the TurnOff command for the Hue bridge, however when turning it back on there's a variable delay depending on Hue Bridge activity so that can't be used for live view at least.
Did find out that the HueAPI uses a different way of calculating colors with taking brightness into account, my code needs a lot more changes for that to work but that will be added before 0.1.

 

[zekaja]

When the individual led option is enabled it will apply the specific led options from the led config (different brightness/saturation etc..), there's one downside and that it has to divide up the commands which might introduce a small sync issue like the leds not changing color at the same time.

The black dimming option I looked at but the Hue bridge seems a bit picky about that, even when lowering brightness to 1 it would still light up a bit too much.
What I currently do with AtmoLight is send the Color Black which translates to the TurnOff command for the Hue bridge, however when turning it back on there's a variable delay depending on Hue Bridge activity so that can't be used to live view at least.
Did find out that the HueAPI uses a different way of calculating colors with taking brightness into account, my code needs a lot more changes for that to work but that will be added before 0.1.

Okay I see ... but stil it looks pretty darn good now

 

[zekaja]

Hey you guys. Wich settings brought you most luck in Atmolight.?

 

[killer8]

New version .76 works great. I haven't had any problems till now.