1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

FIXED Color correction not taken into account

Discussion in 'Bug Reports' started by patlajan, 7 May 2016.

  1. patlajan

    patlajan New Member

    Messages:
    13
    Guys, the color correction seems to be missed on boot, for some reason.
    When I calibrate the colors from HyperCon and SSH, everything is great.
    As soon as I save the config, and restart the service, the colors are all back to the original ones.
    The only way I've found to be working is to open up HyperCon, connect to SSH and send the settings once again.
     
  2. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Hello patlajan,
    could you upload your hyperion.conf.json and your hypercon.dat?
    Thank you
     
  3. patlajan

    patlajan New Member

    Messages:
    13
    I think these are the last ones I used.
    I am not sure that the *.dat file is up to date, since it doesn't load properly for me.

    Another thing I noticed is the daemon starts up and reads the config from /etc/hyperion.config.json.
    At the same time, HyperCon sends the config to /opt/hyperion/config/hyperion.config.json.
     

    Attached Files:

    • Like Like x 1
  4. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    190
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    What might be happening is that the symlink for /etc/hyperion.config.json which points to /opt/hyperion/config/hyperion.config.json was overwritten with an actual file, could you run this command in an SSH session and post the output (only the .json line there):

    Code:
    ls -lha /etc
    If it isn't a symlink anymore can recreate it manually:

    Code:
    ln -sf /opt/hyperion/config/hyperion.config.json /etc/hyperion.config.json
    
     
    Last edited: 7 May 2016
  5. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    This is also possible yes, thank you :)
    i removed the symlinks for "new installs" to prevent this problem :)
     
    • Like Like x 1
  6. patlajan

    patlajan New Member

    Messages:
    13
    I created the symlink myself, once I found that out.
    I checked the file multiple times, to make sure it is the correct one, so that shouldn't be the issue.
    Another thing is that for my strip, the sequence is rGb, not rbG and when it boots, the correct sequence is used.
    The only thing that seems to not be taken into account is the color correction - whiteballance, temperature, etc..

    I tried one more time, same result.
    Boot the Pi, white is blueish (default state)
    Open HyperCon, Load settings, load the same config file as in the Pi, click "Send Trans." and everything is exactly how it's supposed to be.
     
  7. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    190
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Just to be sure if you manually restart Hyperion after "Send Trans." you get the old config right?
     
  8. patlajan

    patlajan New Member

    Messages:
    13
  9. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    190
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Could you run it manually and post the results :) :

    Code:
    sudo service hyperion stop
    
    hyperiond /opt/hyperion/config/hyperion.config.json
    
    for Openelec you need a different command but not sure which distro you are using atm :)
     
  10. patlajan

    patlajan New Member

    Messages:
    13
    I ran:
    /opt/hyperion/bin/hyperiond /opt/hyperion/config/hyperion.config.json


    No luck, it still starts with the blueish white.
    It is the correct config, though:

    cat
    /opt/hyperion/config/hyperion.config.json
    "temperature" :
    [
    {
    "id" : "default",
    "leds" : "*",
    "temperatureValues" :
    {
    "red" : 255,
    "green" : 110,
    "blue" : 70
    }
    }
    ],
     
    • Like Like x 1
  11. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    I could confirm that the colors change a little bit. This is no issue of HyperCon, the values that are send through hyperion-remote are the same (of your config file). I need to contact the developer for help here.
     
    • Like Like x 1
  12. patlajan

    patlajan New Member

    Messages:
    13
    Yes, I don't think that HyperCon is the problem, as well.

    Also can you think of any workaround to that, I don't want to startup HyperCon everytime?
    Can I somehow easily mimick it and inject the config runtime?

    Edit: I gues I can just run this after boot?

    hyperion-remote -u 1.0 -m 1.0 -g "2.0 2.0 2.0" -t "0.0 0.0 0.0" -R "255 0 0" -G "0 225 0" -B "0 0 205" -Z "255 110 70"
     
  13. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    190
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Pretty weird that the color calibrations don't get applied on startup but are via remote, wondering if the developer missed something or that it's formatted wrong in the final config created by HyperCon for some reason :)
     
  14. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    i checked everything, the config looks good. There is something other weird going on :)
    If i raise up the temperatue values - no color changes

    Something at the temperatur is "damaged"
     
  15. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    I will ask the dev :)
     
    • Like Like x 1
  16. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Last edited: 7 May 2016
  17. patlajan

    patlajan New Member

    Messages:
    13
    Can you just me hint me on which script should I edit to run the remote command after the service starts.
    Tried .sh's in /opt/hyperion/init.d with no luck
     
  18. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    this depends on your system, which device and distribution are you running?
     
  19. patlajan

    patlajan New Member

    Messages:
    13
    Ah, yeah,

    Pi 3
    Linux osmc 4.4.6-3-osmc armv7l GNU/Linux
     
  20. Brindosch

    Brindosch Administrator Administrator

    Messages:
    679
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266