Using JointSpace API to control Ambilight

aphex
2012-05-18
2013-05-28
  • aphex

    aphex - 2012-05-18

    I'm trying to set custom ambilight input to the tv, but works only for the left side on the tv. The right side doesn't get changed. At first I set the tv to manual mode and then I try to put this input:

    {
    "layer1": {
    "left": {
    "0": {
    "r": 0,
    "g": 0,
    "b": 80
    },
    "1": {
    "r": 0,
    "g": 0,
    "b": 0
    },
    "2": {
    "r": 0,
    "g": 0,
    "b": 0
    }
    },
    "top": {
    },
    "right": {
    "0": {
    "r": 0,
    "g": 80,
    "b": 0
    },
    "1": {
    "r": 0,
    "g": 0,
    "b": 0
    },
    "2": {
    "r": 0,
    "g": 0,
    "b": 0
    }
    },
    "bottom": {
    }
    }
    }

    There is some information about the TV:
    "softwareversion": "Q5551-0.14.96.0",
    "model": "42PFL7606K/02"

    What am I doing wrong ?

     
  • Matthias Ihmig

    Matthias Ihmig - 2012-05-18

    I have the same problem on my 32PFL7606K.
    Already have reported this on a different thread, but without success.

    I think, it's a firmware bug on the 7606K, which has not yet been corrected unfortunately.
    So, you're most probably do nothing wrong. But I don't know what's the best way to actually get it fixed. I've tried here and the Philips support forums, but no answer.

     
  • aphex

    aphex - 2012-05-18

    Can you send me the link of the bug report ? How long do you know about the bug ?

     
  • aphex

    aphex - 2012-05-20

    Do you know if the JointSpace API (not the JSON one) is also broken? And are there some ambilight examples ?

     
  • Matthias Ihmig

    Matthias Ihmig - 2012-05-21

    Sorry, I don't know. I'm also not aware of any examples.
    But please let me know if you find something out.

     
  • Jean-Marc Harvengt

    JointgSPACE API was never officlally supported in TV product.
    It got replaced by JSON variant which seems to have a bug on some sets (however reported as resolved in more recent firmware…)

     
  • aphex

    aphex - 2012-05-21

    I've tested it with the latest firmware version from 15-16.05 and the bug still exists. Where did you saw, that it is reported as resolved ?

    Tested with:Q5551-0.14.96.0,Q5551-0.14.98.0

     
  • Jean-Marc Harvengt

    Was reported by a Philips colleage directly…
    I will raise the issue.  I assume it is not set type dependent..

     
  • aphex

    aphex - 2012-05-21

    Thank you very much! I hope the bug will be resolved as soon as possible :)

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks