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

[Croog]

Hello!

I am getting System.FormatException: Input string was not in a correct when I am trying to change color via AtmoHue.

I bought Hue Bridge 2.0 along with some color bulbs and now I am trying to use your plugin. It seems that I managed to connect AtmoHue with the bridge as I am able to control brightness of one bulb which I added to AtmoHue. However I am unable to do anything else as for changing colors I get the error as above. I get the same error either from "testing" tab in AtmoHue and MediaPortal via AtmoLight. Log included.

Thanks for help

 

[Rick164]

Hi Croog,

According to the log during set color it runs into a conversion error (expects number but gets something else), could you attach your settings.xml (located in AtmoHue.exe directory)?
Also is this with AtmoHue 0.0.87 or 0.0.88 BETA?

Most likely cause is that one of the settings in the first tab is invalid but that way I can double check to make sure , btw the bulb models aren't really that great for ambilight and only useful if you enable theather mode (turn leds off / on during playback) in AtmoLight as they tend to be very slow between color changes (>1s delays).

 

[zekaja]

And by the way... Theater mode is fantastic so happy you got it in there... What could be nice is if theater mode only affects if video is played back and not music.. But thnx again I use the feature every day...

 

[Rick164]

And by the way... Theater mode is fantastic so happy you got it in there... What could be nice is if theater mode only affects if video is played back and not music.. But thnx again I use the feature every day...

Added a quick fix for that which should work and attached beta build, make sure to set it to VU meter or anything except LEDs disabled for music effect like this:

 

[Croog]

According to the log during set color it runs into a conversion error (expects number but gets something else), could you attach your settings.xml (located in AtmoHue.exe directory)?
Also is this with AtmoHue 0.0.87 or 0.0.88 BETA?

Most likely cause is that one of the settings in the first tab is invalid but that way I can double check to make sure , btw the bulb models aren't really that great for ambilight and only useful if you enable theather mode (turn leds off / on during playback) in AtmoLight as they tend to be very slow between color changes (>1s delays).

Hi, XML is attached and I used 0.0.87.

Thanks also about advice with bulb's speed. Thats is exactly what I wanted to test in the first place. The question is whether I will end up with lightstrip+ or the only usable solution will be some arduino/raspberry based light. Previously I thought that I will simply solve ambilight with philips TV, but I want to be able to lit the LEDs even when the TV is off.

 

[Rick164]

Hue setting was empty in config so that might be the cause, would try the attached config with 0.0.88 beta version as that one worked last time with the latest Philips bridge firmware
Their lightstrips+ I haven't played with but the main bottleneck is their protocol because the bridge needs to relay it over WiFi (Zigbee) which has build in limits for epilepsy and/or better fading, there have been other Hue libraries (not in C# sadly) that have improved speed but since Philips never designed them for that in mind to begin with it is always gonna be a workaround or hack.

We have a good alternative for Hue and ambilight if you want to build your own btw, it's called AtmoOrb which is stable and very fast over WiFi (1ms respond times)
The most easiest build option is to to use a Photon like in this tutorial:

https://forum.team-mediaportal.com/...e-photon-with-neopixel-tutorial-added.131901/

Using 2 Orbs daily without issues for months now , the protocol is pretty flexible and currently waiting for a new firmware so we can start expanding to large led arrays (200+ party lights and what not).
You can also connect strips to it so doesn't really need to be a lamp as the ring used can expand to any WS2812 led type as well.

 

[Croog]

Hmm, its still the same with 0.0.88 beta and your config. I also tryied various combination of
<HueSetBrightnessStartup>False</HueSetBrightnessStartup>
<HueRunningWindows8>False</HueRunningWindows8>
<EnableIndividualLightSettings>False</EnableIndividualLightSettings>
but without luck.

Thanks for pointing me to AtmoOrb, will definitely check it out.

 

[Rick164]

Think I spotted the error, it's in the manual color corrections for bulb device type.
Made it so that's a generic color correction for all devices, not perfect but should get rid of the error.

Attached new AtmoHue version and settings.xml which isn't required but has different color corrections, under the experimental tab you can correct the colors if needed.

 

[Croog]

Still no luck. But nevermind, I can try tro debug it by myself later. I connected to IRC.

 

[Rick164]

We had some region / encoding issues with AtmoHue a while back, under some languages it would mess up formatting but thought I corrected all the needed functions.
Could try temporarily changing region settings to US or UK with a fresh AtmoHue config and check if you get the same error , can't reproduce the issue under Dutch or UK region yet.

// Update

Attached debug build which will show the exact color codes in log before it fails.