Reply to thread

Message: <blockquote data-quote="pavke" data-source="post: 1177943" data-attributes="member: 11916">When I learned that my Hue set could be used to provide 'Ambilight' with MP, I set out to test this using the Ambilight/Atmohue plugins.But ... after hours and hours of testing, trying with different parameters, even on another PC, etc, etc I cannot get it to work.Ambilight seems to work as advertised - at least, I can see lots of remote API calls coming into Atmohue, but Atmohue itself fails miserably.Summary of my findings : when setting up Atmohue and doing the 'locate bridge' thing, AH does NOT find my bridge when I check the Windows 8 box (although I'm running Windows 10). It says it cannot find it using SSDP...But when I uncheck the Windows 8 box, it DOES find it, using 'standard discovery method'. Maybe this already explains why things aren't working ?In any case, setting up some Hue Leds is no problem - but testing them does nothing noticeable. Also, using the 'retrieve scenes' in the Experimental tab does nothing, whilst 'get LED Ids' results in 'Not connected to Hue bridge'. Funny thing is that the log shows all sort of 'normal' entries, about Hue being initialized, colors being sent, ... and no error messages whatsoever.One thing though: Status always stays empty, never shows 'Connected'...Oh and by the way: I am using Led strips, but that in itself does not explain the bridge connection problem I guess...All of this stays the same, whether I enable the Windows 8 setting or not - but I guess this setting is only relevant for locating the bridge ?And FYI:1) because I suspected a firewall problem, I also made sure that in my Norton settings Atmohue gets full access2) my set works perfectly with the Autohue app. Finding my bridge (even over the internet) and steering my lamps works without any problem with it...So, I am at a loss as to why things fail to work, and hope you can shed some light on this.</blockquote>

Verification