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

SOLVED No connection to host after update

Discussion in 'Software Support' started by the_stig, 2 May 2016.

  1. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Hi,

    first thanks for the great stuff around hyperion here!

    Unfortunately I get after updating HyperCon and Hyperion through HyperCon the following:

    <code>
    ssh in: ---> Installing systemd script
    ssh in: ---> Starting Hyperion
    ssh in: *******************************************************************************
    ssh in: Hyperion Installation/Update finished!
    ssh in: Please download the latest HyperCon version to benefit from new features!
    ssh in: To create a config, follow the HyperCon Guide at our Wiki (EN/DE)!
    ssh in: Wiki: wiki.hyperion-project.org Webpage: www.hyperion-project.org
    ssh in: *******************************************************************************
    ssh out: sudo systemctl stop hyperion.service 2>/dev/null; sudo /etc/init.d/hyperion stop 2>/dev/null ; sudo /sbin/initctl stop hyperion 2>/dev/null
    ssh out: sudo systemctl start hyperion.service 2>/dev/null ; sudo /etc/init.d/hyperion start 2>/dev/null ; sudo /sbin/initctl start hyperion 2>/dev/null
    ssh out: hyperion-remote -c ffac01
    ssh in: hyperion-remote:
    ssh in: version : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
    ssh in: build time: Apr 29 2016 12:48:41
    ssh out: Unable to connect to host
    ssh out: hyperion-remote -c 3857ff

    </code>

    Any hints for a linux newbie? Rick164 helped me a lot while installing all stuff, but I think its here more appropriate.

    Thanks!
     
  2. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Hi,
    You installed Hyperion on a Raspbian Jessie (?) or which hardware are you using currently? Please post a: Hyperion Log
     
    Last edited: 2 May 2016
  3. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    192
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Hi @the_stig

    Should be Raspbian Jessie if I recall correctly from the last time we set it up, can you try installing it via the command line (SSH session) like listed here:

    https://hyperion-project.org/wiki/Installation-with-command-line

    afterwards it will start automatically, otherwise best to post the hyperion.config.json located in /opt/hyperion/conf so we can double check that :)
    Your old config should be fine as that will get placed back after the update.

    Also can try running it manually from the SSH session like so:

    Code:
    /opt/hyperion/bin/hyperiond /opt/hyperion/config/hyperion.config.json
    
    And post the output here or use the log output method @Brindosch posted as that is easier.
     
    Last edited: 2 May 2016
    • Thank you Thank you x 1
  4. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Yeah, provide a log - easy for everyone :)
    no long explanations or command line fiddling :D
     
    • Like Like x 1
  5. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Thanks! Didn't know how to get the log...was too easy for me ;)
    RPi2 with Raspian Jessie, yes!

    Here we go:
    Code:
    SSH Traffic:
    ssh connected
    ssh out:    sudo journalctl -u hyperion.service 2>/dev/null
    ssh in:    -- Logs begin at Mo 2016-05-02 19:15:04 UTC, end at Di 2016-05-03 07:11:50 UTC. --
    ssh in:    Mai 02 19:15:06 hyperion systemd[1]: Starting Hyperion Systemd service...
    ssh in:    Mai 02 19:15:06 hyperion systemd[1]: Started Hyperion Systemd service.
    ssh in:    Mai 02 19:15:07 hyperion hyperiond[343]: Hyperion Ambilight Deamon
    ssh in:    Mai 02 19:15:07 hyperion hyperiond[343]: Version  : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
    ssh in:    Mai 02 19:15:07 hyperion hyperiond[343]: Build Time: Apr 29 2016 12:49:00
    ssh in:    Mai 02 19:15:07 hyperion hyperiond[343]: INFO: Selected configuration file: /opt/hyperion/config/hyperion.config.json
    ssh in:    Mai 02 19:15:07 hyperion hyperiond[343]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in:    Mai 02 19:15:07 hyperion hyperiond[343]: what():  Failed to parse configuration: * Line 124, Column 1
    ssh in:    Mai 02 19:15:07 hyperion hyperiond[343]: Missing '}' or object member name
    ssh in:    Mai 02 19:15:07 hyperion systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
    ssh in:    Mai 02 19:15:07 hyperion systemd[1]: Unit hyperion.service entered failed state.
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: hyperion.service holdoff time over, scheduling restart.
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Stopping Hyperion Systemd service...
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Starting Hyperion Systemd service...
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Started Hyperion Systemd service.
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[512]: Hyperion Ambilight Deamon
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[512]: Version  : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[512]: Build Time: Apr 29 2016 12:49:00
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[512]: INFO: Selected configuration file: /opt/hyperion/config/hyperion.config.json
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[512]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[512]: what():  Failed to parse configuration: * Line 124, Column 1
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[512]: Missing '}' or object member name
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Unit hyperion.service entered failed state.
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: hyperion.service holdoff time over, scheduling restart.
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Stopping Hyperion Systemd service...
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Starting Hyperion Systemd service...
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Started Hyperion Systemd service.
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[536]: Hyperion Ambilight Deamon
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[536]: Version  : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[536]: Build Time: Apr 29 2016 12:49:00
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[536]: INFO: Selected configuration file: /opt/hyperion/config/hyperion.config.json
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[536]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[536]: what():  Failed to parse configuration: * Line 124, Column 1
    ssh in:    Mai 02 19:15:08 hyperion hyperiond[536]: Missing '}' or object member name
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
    ssh in:    Mai 02 19:15:08 hyperion systemd[1]: Unit hyperion.service entered failed state.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: hyperion.service holdoff time over, scheduling restart.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Stopping Hyperion Systemd service...
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Starting Hyperion Systemd service...
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Started Hyperion Systemd service.
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[573]: Hyperion Ambilight Deamon
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[573]: Version  : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[573]: Build Time: Apr 29 2016 12:49:00
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[573]: INFO: Selected configuration file: /opt/hyperion/config/hyperion.config.json
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[573]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[573]: what():  Failed to parse configuration: * Line 124, Column 1
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[573]: Missing '}' or object member name
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Unit hyperion.service entered failed state.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: hyperion.service holdoff time over, scheduling restart.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Stopping Hyperion Systemd service...
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Starting Hyperion Systemd service...
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Started Hyperion Systemd service.
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[575]: Hyperion Ambilight Deamon
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[575]: Version  : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[575]: Build Time: Apr 29 2016 12:49:00
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[575]: INFO: Selected configuration file: /opt/hyperion/config/hyperion.config.json
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[575]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[575]: what():  Failed to parse configuration: * Line 124, Column 1
    ssh in:    Mai 02 19:15:09 hyperion hyperiond[575]: Missing '}' or object member name
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Unit hyperion.service entered failed state.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: hyperion.service holdoff time over, scheduling restart.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Stopping Hyperion Systemd service...
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Starting Hyperion Systemd service...
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: hyperion.service start request repeated too quickly, refusing to start.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Failed to start Hyperion Systemd service.
    ssh in:    Mai 02 19:15:09 hyperion systemd[1]: Unit hyperion.service entered failed state.
    ssh in:    Mai 02 19:22:03 hyperion systemd[1]: Stopped Hyperion Systemd service.
    ssh in:    Mai 02 19:24:52 hyperion systemd[1]: Stopped Hyperion Systemd service.
    
    SSHing gives me:

    [email protected]:~ $ /opt/hyperion/bin/hyperiond /opt/hyperion/config/hyperion.config.json
    Hyperion Ambilight Deamon
    Version : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
    Build Time: Apr 29 2016 12:49:00
    INFO: Selected configuration file: /opt/hyperion/config/hyperion.config.json
    terminate called after throwing an instance of 'std::runtime_error'
    what(): Failed to parse configuration: * Line 124, Column 1
    Missing '}' or object member name

    Abgebrochen

    hyperion.json.config (deleted the LEDs section):
    Code:
    // Automatically generated configuration file for 'Hyperion daemon'
    // Generated by: HyperCon (The Hyperion deamon configuration file builder)
    // Created with HyperCon V1.02.0 (30.04.2016)
    
    {
       /// Device configuration contains the following fields:
       /// * 'name'  : The user friendly name of the device (only used for display purposes)
       /// * 'type'  : The type of the device or leds (known types for now are
       /// ---------SPI---------, APA102, WS2801, P9813, LPD6803, LPD8806, ---------PWM---------, WS2812b (just RPi1), WS281X (RPi1, RPi2, RPi3), --------OTHER--------, PhilipsHUE, AtmoOrb, PiBlaster, Tinkerforge, FadeCandy, UDP, RawHID (USB), SEDU, Adalight, AdalightAPA102, TPM2, USBASP-WS2801, USBASP-WS2812, ------3rd PARTY------, AmbiLed, Atmo, Lightpack, Multi-Lightpack, Paintpack, Test (file), None)
       /// * [device type specific configuration]
       /// * 'colorOrder' : The order of the color bytes ('rgb', 'rbg', 'bgr', etc.).
       "device" :
       {
         "name"  : "MyPi",
         "type"  : "apa102",
         "output"  : "/dev/spidev0.0",
         "rate"  : 1000000,
         "colorOrder" : "bgr"
       },
    
       /// Color manipulation configuration used to tune the output colors to specific surroundings.
       /// The configuration contains a list of color-transforms. Each transform contains the
       /// following fields:
       ///  * 'channelAdjustment'
       ///  * 'id'  : The unique identifier of the channel adjustments (eg 'device_1')
       ///  * 'leds'  : The indices (or index ranges) of the leds to which this channel adjustment applies
       ///  (eg '0-5, 9, 11, 12-17'). The indices are zero based.
       ///  * 'pureRed'/'pureGreen'/'pureBlue' : The manipulation in the Red-Green-Blue color domain with the
       ///  following tuning parameters for each channel:
       ///  * 'temperature'
       ///  * 'id'  : The unique identifier of the temperature (eg 'device_1')
       ///  * 'leds'  : The indices (or index ranges) of the leds to which this temperature applies
       ///  (eg '0-5, 9, 11, 12-17'). The indices are zero based.
       ///  * 'red'/'green'/'blue' : The temperature manipulation in the Red-Green-Blue color domain with the
       ///  following tuning parameters for each channel:
       ///  * 'transform'
       ///  * 'id'  : The unique identifier of the color transformation (eg 'device_1')
       ///  * 'leds' : The indices (or index ranges) of the leds to which this color transform applies
       ///  (eg '0-5, 9, 11, 12-17'). The indices are zero based.
       ///  * 'hsv' : The manipulation in the Hue-Saturation-Value color domain with the following
       ///  tuning parameters:
       ///  - 'saturationGain'  The gain adjustement of the saturation
       ///  - 'luminanceGain'  The gain adjustement of the luminance
       ///  * 'red'/'green'/'blue' : The manipulation in the Red-Green-Blue color domain with the
       ///  following tuning parameters for each channel:
       ///  - 'threshold'  The minimum required input value for the channel to be on
       ///  (else zero)
       ///  - 'gamma'  The gamma-curve correction factor
       ///
       /// Next to the list with color transforms there is also a smoothing option.
       ///  * 'smoothing' : Smoothing of the colors in the time-domain with the following tuning
       ///  parameters:
       ///  - 'type'  The type of smoothing algorithm ('linear' or 'none')
       ///  - 'time_ms'  The time constant for smoothing algorithm in milliseconds
       ///  - 'updateFrequency' The update frequency of the leds in Hz
       ///  - 'updateDelay'  The delay of the output to leds (in periods of smoothing)
       "color" :
       {
         "channelAdjustment" :
         [
           {
             "id"  : "default",
             "leds" : "*",
             "pureRed" :
             {
               "redChannel"     : 255,
               "greenChannel"     : 0,
               "blueChannel"     : 0
             },
             "pureGreen" :
             {
               "redChannel"     : 0,
               "greenChannel"     : 255,
               "blueChannel"     : 0
             },
             "pureBlue" :
             {
               "redChannel"     : 0,
               "greenChannel"     : 0,
               "blueChannel"     : 255
             }
           }
         ],
         "temperature" :
         [
           {
             "id"  : "default",
             "leds" : "*",
             "temperatureValues" :
             {
               "red"    : 255,
               "green"   : 255,
               "blue"    : 255
             }
           }
         ],
         "transform" :
         [
           {
             "id"  : "default",
             "leds" : "*",
             "hsl" :
             {
               "saturationGain"   : 1.0000,
               "luminanceGain"     : 1.0000
             },
             "red" :
             {
               "threshold"    : 0.1500,
               "gamma"     : 2.2000
             },
             "green" :
             {
               "threshold"    : 0.1500,
               "gamma"     : 2.2000
             },
             "blue" :
             {
               "threshold"    : 0.1500,
               "gamma"     : 2.2000
             }
           }
         ],
    ,
         "channelAdjustment" :
         [
           {
             "id"  : "htpc",
             "leds" : "*",
             "pureRed" :
             {
               "redChannel"     : 255,
               "greenChannel"     : 0,
               "blueChannel"     : 0
             },
             "pureGreen" :
             {
               "redChannel"     : 0,
               "greenChannel"     : 255,
               "blueChannel"     : 0
             },
             "pureBlue" :
             {
               "redChannel"     : 0,
               "greenChannel"     : 0,
               "blueChannel"     : 255
             }
           }
         ],
         "temperature" :
         [
           {
             "id"  : "htpc",
             "leds" : "*",
             "temperatureValues" :
             {
               "red"    : 255,
               "green"   : 255,
               "blue"    : 255
             }
           }
         ],
         "transform" :
         [
           {
             "id"  : "htpc",
             "leds" : "*",
             "hsl" :
             {
               "saturationGain"   : 1.0000,
               "luminanceGain"     : 1.6000
             },
             "red" :
             {
               "threshold"    : 0.1500,
               "gamma"     : 2.5000
             },
             "green" :
             {
               "threshold"    : 0.1500,
               "gamma"     : 2.5000
             },
             "blue" :
             {
               "threshold"    : 0.1500,
               "gamma"     : 2.5000
             }
           }
         ],
    
         "smoothing" :
         {
           "type"  : "linear",
           "time_ms"  : 150,
           "updateFrequency" : 35.0000,
           "updateDelay"  : 0
         }
       },
    
       /// The black border configuration, contains the following items:
       ///  * enable         : true if the detector should be activated
       ///  * threshold        : Value below which a pixel is regarded as black (value between 0.0 and 1.0)
       ///  * unknownFrameCnt     : Number of frames without any detection before the border is set to 0 (default 600)
       ///  * borderFrameCnt     : Number of frames before a consistent detected border gets set (default 50)
       ///  * maxInconsistentCnt    : Number of inconsistent frames that are ignored before a new border gets a chance to proof consistency
       ///  * blurRemoveCnt     : Number of pixels that get removed from the detected border to cut away blur (default 1)
       ///  * mode          : Border detection mode (values=default,classic,osd)
       "blackborderdetector" :
       {
         "enable" : false,
         "threshold" : 0.0,
         "unknownFrameCnt" : 600,
         "borderFrameCnt" : 50,
         "maxInconsistentCnt" : 10,
         "blurRemoveCnt" : 1,
         "mode" : "default"
       },
    
       /// The configuration of the effect engine, contains the following items:
       ///  * paths     : An array with absolute location(s) of directories with effects
       ///  * color      : Set static color after boot -> set effect to "" (empty) and input the values [R,G,B] and set duration_ms NOT to 0 (use 1) instead
       ///  * effect      : The effect selected as 'boot sequence'
       ///  * duration_ms   : The duration of the selected effect (0=endless)
       ///  * priority    : The priority of the selected effect/static color (default=990) HINT: lower value result in HIGHER priority!
       "effects" :
       {
         "paths" :
         [
           "/opt/hyperion/effects"
         ]
       },
    
       "bootsequence" :
       {
         "color" : [0,0,0],
         "effect" : "Rainbow swirl fast",
         "duration_ms" : 10000,
         "priority" : 990
       },
    
       /// The configuration of the Json/Proto forwarder. Forward messages to multiple instances of Hyperion on same and/or other hosts
       /// 'proto' is mostly used for video streams and 'json' for effects
       ///  * proto   : Proto server adress and port of your target. Syntax:[IP:pORT] -> ["127.0.0.1:19447"] or more instances to forward ["127.0.0.1:19447","192.168.0.24:19449"]
       ///  * json   : Json server adress and port of your target. Syntax:[IP:pORT] -> ["127.0.0.1:19446"] or more instances to forward ["127.0.0.1:19446","192.168.0.24:19448"]
       ///  HINT:   If you redirect to "127.0.0.1" (localhost) you could start a second hyperion with another device/led config!
       ///      Be sure your client(s) is/are listening on the configured ports. The second Hyperion (if used) also needs to be configured! (HyperCon -> External -> Json Server/Proto Server)
    //    "forwarder" :
    //    {
    //      "proto" : ["127.0.0.1:19447"],
    //      "json" : ["127.0.0.1:19446"]
    //    },
    
       ///  The configuration for the frame-grabber, contains the following items:
       ///  * width  : The width of the grabbed frames [pixels]
       ///  * height  : The height of the grabbed frames [pixels]
       ///  * frequency_Hz : The frequency of the frame grab [Hz]
       ///  * priority  : The priority of the frame-gabber (Default=890) HINT: lower value result in HIGHER priority!
       ///  * ATTENTION  : Power-of-Two resolution is not supported and leads to unexpected behaviour!
    //    "framegrabber" :
    //    {
    //      "width" : 80,
    //      "height" : 45,
    //      "frequency_Hz" : 10.0,
    //      "priority" : 900
    //    },
    
       /// The configuration of the Kodi connection used to enable and disable the frame-grabber. Contains the following fields:
       ///  * xbmcAddress  : The IP address of the Kodi-host
       ///  * xbmcTcpPort  : The TCP-port of the Kodi-server
       ///  * grabVideo  : Flag indicating that the frame-grabber is on(true) during video playback
       ///  * grabPictures  : Flag indicating that the frame-grabber is on(true) during picture show
       ///  * grabAudio  : Flag indicating that the frame-grabber is on(true) during audio playback
       ///  * grabMenu  : Flag indicating that the frame-grabber is on(true) at the Kodi menu
       ///  * grabScreensaver  : Flag indicating that the frame-grabber is on(true) when Kodi is on screensaver
       ///  * enable3DDetection : Flag indicating that the frame-grabber should switch to a 3D compatible modus if a 3D video is playing
    //    "xbmcVideoChecker" :
    //    {
    //      "xbmcAddress" : "127.0.0.1",
    //      "xbmcTcpPort" : 9090,
    //      "grabVideo" : true,
    //      "grabPictures" : true,
    //      "grabAudio" : true,
    //      "grabMenu" : false,
    //      "grabScreensaver" : true,
    //      "enable3DDetection" : true
    //    },
    
       /// The configuration of the Json server which enables the json remote interface
       ///  * port : Port at which the json server is started
       "jsonServer" :
       {
         "port" : 19444
       },
    
       /// The configuration of the Proto server which enables the protobuffer remote interface
       ///  * port : Port at which the protobuffer server is started
       "protoServer" :
       {
         "port" : 19445
       },
    
       /// The configuration of the boblight server which enables the boblight remote interface
       ///  * port    : Port at which the boblight server is started
       ///  * priority: Priority of the boblight server (Default=900) HINT: lower value result in HIGHER priority!
    //    "boblightServer" :
    //    {
    //      "port" : 19333,
    //      "priority" : 900
    //    },
    
       /// Configuration for the embedded V4L2 grabber
       ///  * device  : V4L2 Device to use [default="/dev/video0"]
       ///  * input  : V4L2 input to use [default=0]
       ///  * standard  : Video standard (no-change/PAL/NTSC) [default="no-change"]
       ///  * width  : V4L2 width to set [default=-1]
       ///  * height  : V4L2 height to set [default=-1]
       ///  * frameDecimation  : Frame decimation factor [default=2]
       ///  * sizeDecimation  : Size decimation factor [default=8]
       ///  * priority  : Hyperion priority channel [default=900]
       ///  * mode  : 3D mode to use 2D/3DSBS/3DTAB (note: no autodetection) [default="2D"]
       ///  * cropLeft  : Cropping from the left [default=0]
       ///  * cropRight  : Cropping from the right [default=0]
       ///  * cropTop  : Cropping from the top [default=0]
       ///  * cropBottom  : Cropping from the bottom [default=0]
       ///  * redSignalThreshold  : Signal threshold for the red channel between 0.0 and 1.0 [default=0.0]
       ///  * greenSignalThreshold : Signal threshold for the green channel between 0.0 and 1.0 [default=0.0]
       ///  * blueSignalThreshold  : Signal threshold for the blue channel between 0.0 and 1.0 [default=0.0]
    //    "grabber-v4l2" :
    //    {
    //      "device" : "/dev/video0",
    //      "input" : 0,
    //      "standard" : "no-change",
    //      "width" : -1,
    //      "height" : -1,
    //      "frameDecimation" : 2,
    //      "sizeDecimation" : 8,
    //      "priority" : 800,
    //      "mode" : "2D",
    //      "cropLeft" : 0,
    //      "cropRight" : 0,
    //      "cropTop" : 0,
    //      "cropBottom" : 0,
    //      "redSignalThreshold" : 0.0,
    //      "greenSignalThreshold" : 0.0,
    //      "blueSignalThreshold" : 0.0
    //    },
    
       ///  The configuration for each individual led. This contains the specification of the area
       ///  averaged of an input image for each led to determine its color. Each item in the list
       ///  contains the following fields:
       ///  * index: The index of the led. This determines its location in the string of leds; zero
       ///  being the first led.
       ///  * hscan: The fractional part of the image along the horizontal used for the averaging
       ///  (minimum and maximum inclusive)
       ///  * vscan: The fractional part of the image along the vertical used for the averaging
       ///  (minimum and maximum inclusive)
       "leds" :
       [
         {
           "index" : 0,
           "hscan" : { "minimum" : 0.0000, "maximum" : 0.0500 },
           "vscan" : { "minimum" : 0.9200, "maximum" : 1.0000 }
         },
         {
    
    
       "endOfJson" : "endOfJson"
    }
    
     
    Last edited by a moderator: 3 May 2016
    • Like Like x 1
  6. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Looks like your hyperion.config.json is broken (json syntax), please recreate your config
    or you do it by hand
    Code:
    what(): Failed to parse configuration: * Line 124, Column 1
    Missing '}' or object member name
    edited your post with code tags
     
    • Thank you Thank you x 1
  7. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Thanks Brindosch. I edited my old config.json in now. Sorry for the mess. Will try to recreate a totally fresh hyperion.config.json now.
     
  8. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Please use code tags! There is a "insert" button and paste your code in this field. Thank you
     
  9. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Something is really going wrong with the new HyperCon for me. Maybe it's the root of my problems. I can ssh into my Pi, but all the commands via Hypercon aren't working properly for me. Sometimes its not reacting for >30 Minutes. Now I get pretty often a error:

    EDIT: Old HyperCon 1.0.0 is working properly here.

    upload_2016-5-3_9-49-50.png
     
  10. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Which java version are you running?
    I can´t reproduce this issue. Are you using a wifi connection between your desktop and the device?
     
  11. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Java 1.8.0_71 and wifi between notebook and router, but lan from router to Pi. But currently only via VPN from away. Maybe this is the problem?
     
  12. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Hrm, recreated hyperion.config.json via HyperCon and I still get

    Code:
    [email protected]:~ $ /opt/hyperion/bin/hyperiond /opt/hyperion/config/hyperion.config.json
    Hyperion Ambilight Deamon
            Version   : V1.02.0 (brindosch-2828c78/95e4d4e-1461938433
            Build Time: Apr 29 2016 12:49:00
    INFO: Selected configuration file: /opt/hyperion/config/hyperion.config.json
    terminate called after throwing an instance of 'std::runtime_error'
      what():  Failed to parse configuration: * Line 124, Column 1
      Missing '}' or object member name
    
    Full hyperion.config.json, Line 124 is a "," above "channel adjustment":

     
    Last edited by a moderator: 3 May 2016
  13. TPmodding

    TPmodding Administrator Staff Member Administrator

    Messages:
    1,582
    Hardware:
    RPi1/Zero, RPi2, RPi3, +Arduino, +nodeMCU/ESP8266
    just remove the "," in Line 124, then it should work
     
  14. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Nope, unfortunately not. But I know think there is a bigger problem with my Pi since SSHing in takes around 3 minutes, even if I try via a local LAN connection. Guess I have to reinstall whole raspian. Should now all prerequisites for running hyperion be installed via HyperCon?
     
  15. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Aaaah! sorry, could you delete your second profile: "htpc" and try again with just one color profile
     
  16. TPmodding

    TPmodding Administrator Staff Member Administrator

    Messages:
    1,582
    Hardware:
    RPi1/Zero, RPi2, RPi3, +Arduino, +nodeMCU/ESP8266
    Just try it yes...

    Bei mir gings auf anhieb ohne das ","
     
  17. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    We are still investigating if more than one profile is working with hyperion.
     
  18. the_stig

    the_stig New Member

    Messages:
    23
    Hardware:
    RPi2
    Ok, but currently I seem to have broken my raspian. As SSHing took too long I tried to add "UseDNS no" to ssh_config and fiddled with permissions...now I cannot even login:

    Code:
    -bash: /etc/profile: Keine Berechtigung
    Ich habe keinen [email protected]:~ $
    Anyone with first help for me?
     
  19. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    A Raspbian Jessie has a idle time of around 5 seconds for login. But not more by default. Not sure about your ssh problem now. If you just use hyperion on this raspbian, maybe you should try again with a new image (faster?)
     
  20. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    192
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    @the_stig Would do a clean Raspbian install as when we did the install together there were already some weird raspberry issues like missing perms and libs not being at the right location :) , afterwards you can do the install via HyperCon again.
    If that fails can pm me and will do a teamviewer session.
     
    • Thank you Thank you x 1