Posts by freiherrvw

    You're welcome ^^ btw I tested the export/import and all instances have been restored correctly.

    I formated my sd to be sure to have a clean installation. I used latest HyperBian version and used RaspPi Imager with custom settings (user=pi) to write the image.

    After installation, the service starts and is available over http. But after a reboot the service is deactive.

    Fortunatelly there was a unsaved notepad++ tab since my last installation (january this year xD ) I picked following two commands and executed
    sudo systemctl disable --now hyperion@pi

    sudo systemctl enable --now hyperion@root

    so that after a reboot the service starts running

    regarding the instance handling: when I switch the wled state from on to off, then hyperion crashes immediately (not after the seccond try like described above)

    ah ok, didn't expect that the current needs to be removed, thank you :)

    I'm going to test the new version regarding the export and one bug that I am experiencing in my current version...

    I figured out that using the deactivate button on page ...#conf_general for my WLED instances 2/3/4 (1 = tv ambi) causes the Hyperion service to crash, requiring the Pi to be rebooted via SSL.

    When the lights are enabled, I deactivate instance 2 (first WLED) (ok), activate it (ok), deactivate it (crash)

    when I switch to ...#dashbaord and select the seccond instance (first WLED) I'm smashing the enable/disable button like a maniac, lights react as expected and the service crash does not happen.

    I would like to test it with the new version before I open a new bug report

    I executed this command

    Code
    curl -sSL https://releases.hyperion-project.org/install | bash -s -- --nightly

    and following messages appear:

    INFO : Identified distribution "debian"

    INFO : Hyperion 2.0.16 is already installed.


    then I tried these variants (I am not familiar with linux, apt etc.... )

    sudo apt-get update && sudo apt-get install hyperion --nightly

    sudo apt-get update && sudo apt-get install hyperion -- --nightly

    but as I expected it didn't work.

    I'm using this version:

    hyperiond --version

    Hyperion Ambilight Deamon

    Version : 2.0.16 ((HEAD detached at a93d79b) (Paulchen-Panther-cb85d2d/a93d79b-1705568419))

    Build Time: Jan 28 2024 10:21:59

    The site .../#conf_general provides a config export but having multiple instances like me (main = ambilight tv, 2,3,4 = WLED (esp8266 + ws2812b) ) only the first instance is being exported to the config file.

    servus, dieser link hat mir damals sehr geholfen https://digitalewelt.at/hyperion-ambil…tt-ohne-loeten/

    ich habe allerdings die günstigere alternative der wago-klemme bei aliexpress bestellt ^^

    sowie er hier

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    stromversorgung des pi's ist bei mir über usb, gerichtet habe ich mich nach der schaltung aus (1) und für das verlegen des stripes hat der kollege aus (2) eine gute herangehensweise :) ohne das band zerschnibbeln zu müssen

    viel erfolg :)

    Having the same problem loading custom effects...


    using the same version, my config path is

    Code
    - Config path:       /root/.hyperion

    I intend to create a custom effect to turn off extra leds because sometimes they are off, sometimes not. Most of the time I can turn off the extra leds by clicking like crazy on the instance on/off button and after a (shorter or longer) while it happens that all leds are turned off and only the relevant leds (124, led stripe has about 150 leds...) are active.

    But since a few days I have no luck using this method ^^ so my idea was to create a custom effect that turns off all leds

    These are briefly my steps:

    cd /usr/share/hyperion/effects

    sudo nano TurnOffExtraLeds.py

    import hyperion

    import time

    # led area

    total_leds = 150

    leds = [(0, 0, 0)] * total_leds

    hyperion.setColor(leds)


    sudo chmod 755 TurnOffExtraLeds.py

    sudo nano TurnOffExtraLeds.json

    {

    "name": "TurnOffExtraLeds",

    "script": "TurnOffExtraLeds.py",

    "args": {}

    }



    after doing so, I rebooted the pi but the effect was not listed up.

    within the logs I saw a folder and tried:

    sudo mv /usr/share/hyperion/effects/TurnOffExtraLeds.* /root/.hyperion/custom-effects/

    after rebooting the pi, the effect was listed up under..#remote and #effects_configurator

    but selecting the scrpit under #remote produces this log:

    2024-12-19T14:17:16.871Z [EFFECTENGINE] (ERROR) ###### PYTHON EXCEPTION ######
    2024-12-19T14:17:16.871Z [EFFECTENGINE] (ERROR) ## In effect 'TurnOffExtraLeds'
    2024-12-19T14:17:16.872Z [EFFECTENGINE] (ERROR) ## RuntimeError: Argument is not a bytearray
    2024-12-19T14:17:16.922Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:359:updatePriorities()) Removed source priority 1
    2024-12-19T14:17:17.564Z [EFFECTENGINE] (ERROR) ## Traceback (most recent call last):
    2024-12-19T14:17:17.565Z [EFFECTENGINE] (ERROR) ## File "<string>", line 8, in <module>
    2024-12-19T14:17:17.565Z [EFFECTENGINE] (ERROR) ## RuntimeError: Argument is not a bytearray
    2024-12-19T14:17:17.565Z [EFFECTENGINE] (ERROR) ###### EXCEPTION END ######

    and under #effects_configurator the effect can be loaded but is not editable/testable.

    I'll continue try and error... x)


    I fixed the python script as follows:

    import hyperion

    import time

    hyperion.setColor(0,0,0)

    while not hyperion.abort():

    time.sleep(1)


    and it worked, the script is being executed.

    but I solved my problem regarding the additional leds on another way....
    just needed to change controller led count from 124 to 159 xD

    seems that I misunderstood something regarding total count, layount count, blacklist led etc .... ^^

    Hi zusammen,

    lt. Dokumentation heißt es: "Jeder n-te Frame wird übersprungen um Ressourcen zu sparen." => Also würden bei n Frames (mit n mod 5 = 0) und dem Wert 5 die X markierten wegfallen 1 2 3 4 X 6 7 8 9 X 11 12 13 14 X 16 17 18 19 X ..... n-2 n-1 X

    Sprich 20 Frames würden dann auf 16 reduziert werden (mit dem Setting-Wert "5" hätte man dann 20fps auf 16fps reduziert) etc pp.

    Dann verstehe ich aber das angegebene Beispiel nicht: "Ein Wert von 5 resultiert bei einem Aufnahmegerät mit 30fps in einer neuen Framerate von 6 fps."

    Dann müsste doch die Beschreibung eher lauten: Jeder n-te Frame wird "berücksichtigt".


    Deshalb würde ich gerne wissen wie es jetzt genau implmementiert ist :)

    Danke und VG


    Scheint ein Übersetzungsfehler zu sein / seems to be a translation error

    Software frame skippingTo save resources every n'th frame will be processed only. For ex. if grabber is set to 30fps with this option set to 5 the final result will be around 6fps