Configuration export with multiple instances => only first instance configuration is being exported

  • 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.

  • 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

    • Official Post

    INFO : Hyperion 2.0.16 is already installed.

    So you need first the remove the current version


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

    Afterwards install the nightly version

  • 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

  • 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)

    • Official Post

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

    Due security reasons the image is not installed with the default user pi, but the user hyperion.

    The Autostart is configured with that user.

    Therefore the service do not work out of the box, if you change the user.

    You can of course do this, but then you do an updateHyperionUser command.


    I suggest you have a look at the documentation. There you find all the related details. See https://docs.hyperion-project.…/HyperBian.html#hyperbian

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!