Hyperion-NG config problem

1. offizieller Beitrag

    hi,


    tried to update to hyperion ng today. Everything works (software) except the leds (so nothing :D). The Leds just randomly blinks and get "stuck" until I reconnect them again to a poweroutlet. (Had this issue before with hypercon, solved it by lowering the maximum brightness and adding the frequency)
    My old config:



    Setting a unique color or anything (in NG) resolves in randomly blinking. It looks like Ng has imported the old settings but not completly.
    The NG config:



    Am I doing something wrong/ something missing? Or is it just because NG is still in alpha?


    [Specs]
    -Rpi 3b+
    -rapsbian
    -hyperionng alpha9 (armv7)


    Cheers
    Dschogo

    Zitat von Dschogo

    Am I doing something wrong/ something missing? Or is it just because NG is still in alpha?


    you can't use your Json from Hypercon to import in Hyperion.NG.
    they are completely diffrent!
    import a clean Json into Hyperion.NG again because you have a Json file that is corrupted now in the new program, it will mallfunction or not run at all.

    I didnt imported anything manually (if I try to i get the incompatible message). It importted/ migrated the existing hypercon setting during the installation of NG. If i enter my values manually it still doenst work. Do I need to reset the config first? How? (wheres the config path)


    What do you menas with import clean json? (empty json or with the correct structure of NG)


    EDIT:
    used the default config: (https://raw.githubusercontent.…erion.config.json.default) (renamed to .json)


    even with all the old working settings (and frequency as rate 800000) it still just blinks, not that fast only randomly sets leds to different colors (no effect selected only unicolor)

    yeah i know its automatically generated by the webui (the rate parameter is not editable in the ui so i put it in via import to see if this was the missing piece.... it wasnt)


    So what I effectively did is: installed NG, put all my settings in (which worked in hypercon) via webui and it doesnt work.


    The rate parameter was present in hyper con as "frequency".

    Zitat von Dschogo

    yeah i know its automatically generated by the webui (the rate parameter is not editable in the ui so i put it in via import to see if this was the missing piece.... it wasnt)


    So what I effectively did is: installed NG, put all my settings in (which worked in hypercon) via webui and it doesnt work.


    The rate parameter was present in hyper con as "frequency".



    okay thanks, now i get it
    sometimes in writing/explaining technics is really hard. If you said this the first time then i understand hahaha


    but anyway, because it worked on same hardware probably the problem is software of Hyperion.NG


    did you install dependencies? like


    sudo apt-get update
    sudo apt-get upgrade


    sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-image0-dev libxcb-util0-dev libxcb-shm0-dev libxcb-render0-dev libxcb-randr0-dev libxrandr-dev libxrender-dev libavahi-core-dev libavahi-compat-libdnssd-dev libjpeg-dev libturbojpeg0-dev libssl-dev zlib1g-dev


    sudo apt-get install libraspberrypi-dev


    and for the new type you need this one


    sudo apt-get -d install libcec4
    sudo apt-get install libcec4

    • Offizieller Beitrag
    Zitat von Dschogo

    not that I am aware of


    Maybe a good time to have a look, now.


    If there is no error after starting, then I would suggest you turn on the Debug log and share the output.

    Zitat von Lord-Grey

    If there is no error after starting, then I would suggest you turn on the Debug log and share the output.


    Hmm debug log doesnt quite fill on its own only if I do something.


    Log of saving the config, changing color so something pink via web remote

    Code
    2021-01-19T18:54:18.008Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.178.79
2021-01-19T18:54:18.021Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1063:handleLoggingCommand()) log streaming deactivated for client  ::ffff:192.168.178.79
2021-01-19T18:54:26.053Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:registerInput()) Register new input 'Web Configuration@::ffff:192.168.178.79/COLOR' with priority 1 as inactive
2021-01-19T18:54:26.053Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:207:setInput()) Priority 1 is now active
2021-01-19T18:54:26.053Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 1
2021-01-19T18:54:26.054Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[1], previousPriority[250]
2021-01-19T18:54:28.402Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.178.79


    Current NG config (color values are all reduced, leds overshooted in the past (stuck at white) with hypercon and this was the fix along with frequency and dmachannel):


    • Offizieller Beitrag

    As you reported the LEDs are not working, I suggest you sort this out first.
    Go to the Remote Control and enable the LED device. If already enabled, disable and then enable it.Then share the log output.

    alll right (Leds kinda work but only flickers around until they get stuck on one color)


    But here the log:

    Nope static colors flickers for a second and gets stuck in weird colors (for each led). Effects constantly updates the strip so endless flickering. Seems to me like a wrong frequency or byteorder, but I used the same settings as for the hypercon. (except the frequency because ther is no option for that)


    Restartet the rpi a few times already. Where can I find the start log?


    PD: Iam starting hyperionNg via "sudo hyeriond &" because of the issue with only read access

    Heres the startup debug-log:


    • Offizieller Beitrag

    I do not know how Hyperion classic worked and not being too familiar with this LED type...
    You might need to set the latch-time.
    Latch time define the time that passes between two updates. So it might correspond to a maximum update frequency you are used to.
    You need to have settings level = expert to see latch-time.

    • Offizieller Beitrag
    Zitat von Dschogo

    Had this issue before with hypercon, solved it by lowering the maximum brightness and adding the frequency)


    This might indicate that the „electrical“ setup is not perfect. Maybe others could have a look here too.
    The log output does not show any problems...

    hmm tried every latch-time between 0 and 30ms (and from 30 to 150 in steps of 5) but nothing seems to help.


    Doubble checked the hardware. No problem there (if i switch back to hypercon everything works just fine)

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden