Posts by Bub4

    Hi All,

    Is it possible to edit a v. 2.0.16 config to enable the migration to v2.2.1?
    I want to move and update the hyperion installation to a new LXC in proxmox but the migration is only possible with backups coming from v2.0.17 and newer.
    I haven't seen something in the breaking changes on github.

    Brave AI mentions this workaround:
    Based on the available context, the recommended workaround for transferring configurations between incompatible versions is:

    • Database File Replacement: If you have access to the old system running 2.0.16, stop Hyperion on both machines, locate the configuration database file (typically named hyperion.db on Windows/Linux), and copy it from the old system to the new system running 2.2.1.
    • Export/Import via Intermediate Version: Alternatively, install version 2.1.1 on the old system, export the configuration from there, and then import it into the new system. Note that even this method may not preserve all settings perfectly, as users have reported issues with LED device stability (such as flickering WLED strips) after migration.
    • Manual Reconfiguration: For complex setups involving multiple LED devices (e.g., WLED), manual reconfiguration may be necessary to ensure stability, as known issues with grabbers and LED devices in newer versions can cause devices to fail to initialize correctly after a migration.

    I have attached the config backup of both instances.
    I use PiCap and WLED devices.

    Or is it recommended to re-config from scratch?

    I'd be glad if, someone could point me to the right post/article. Don't need a step-by-step guide. I don't want to waste anybodies time!!

    Thank you

    I made it with WLED:

    Bub4
    November 16, 2020 at 3:35 PM

    Have fun

    If would rather go with WLED installed on a Wemos D1 mini, or better a ESP32 with copper ethernet.

    I run mine over WiFi which turns out in flickering when there is heavy load on the network. RJ-45 and hardwired should do the job sufficiently.

    Hyperion is going to be configured with WLED as LED hardware.

    good luck

    If you go with ESP32 or ESP8266 you are going to run WLED as "translator" on the ESP. No need for arduino anymore. The ESP gets powered by the same power supply as the LEDs

    I assume you like to run LE11?

    If yes, then you will need Hyperion (Server) running in a Docker container within LE11.

    You have to configure the WLED instance in the hyperion.ng server. After this is setup you have to configure the IP of the Hyperion server in Picap. If all is done right, you are enlighted :)

    My setup is based on Wemos D1 Mini over WiFi. Hyperion Server runs on a Proxmox container.

    With WiFi based boards you will introduce some more latency as you can imagine. For me it works however...

    Hi All,

    this might be clear for most of the experienced Proxmox users already -> for me it was tricky to setup hyperion in a container.

    In case there are other Proxmox n00bs out there wanting hyperion to run as a container instead of a VM:

    1:

    - unprivileged container - set name and password

    - pick the Debian 11 Standard Template

    - 8 GB disk size (Standard)

    - 1 Core

    - 1024GB RAM, 512 Swap

    - network depending on your needs

    - DNS same as host

    When the container is setup and running, head into the console through the proxmox webUI and login as root user with the password you've set

    2:

    type into the console:

    Code
    apt-get update && apt-get install -y wget gpg sudo && wget -qO /tmp/hyperion.pub.key https://apt.hyperion-project.org/hyperion.pub.key && gpg --dearmor -o - /tmp/hyperion.pub.key > /usr/share/keyrings/hyperion.pub.gpg && echo \deb [signed-by=/usr/share/keyrings/hyperion.pub.gpg] https://apt.hyperion-project.org/ bullseye main\ > /etc/apt/sources.list.d/hyperion.list && apt-get update && apt-get install -y hyperion

    Everything should install automatically and Hyperion.NG should be accessible via "the.IP.you.chose:8090"

    Thanks Lord-Grey for pointing me to psychowood who basically made all the work.

    I am n00b and wrote this one down just for google :)

    ich habe das jetzt auch nochmal mit dem Ubuntu 18.04 versucht.

    Nachdem ich gqg installiert habe und die drei Schitte aus der Doku befolgt habe, bekomme ich das:

    E: The repository 'https://apt.hyperion-project.org bionic Release' does not have a Release file.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.


    wie hast Du das gelöst potti86 ?

    ich finde im container auch keine apt.conf, bei der ich

    Code
    allow-insecure=yes

    setzen könnte.

    Das habe ich mir hier ergooglet:

    Ubuntu Manpage: apt-secure - Archivauthentifizierungsunterstützung für APT

    In der VM habe ich zwar keine Probleme - würde dennoch gerne im Container haben

    grüße

    Quote

    Wo liegt der Unterschied die leds per wled anzusteuern.

    Der Unterschied liegt darin, dass WLED ein eigeständiges, von Hyperion unabhängig steuerbares, Produkt ist. Damit ist man in den meisten Fällen flexibler. Ich bin bspw. gerade dabei einen proxmox hypervisor aufzubauen. Dann wird Hyperion künftig in einem Container laufen - die LED hardware bleibt davon unberührt. Aktuell läuft Hyperion bei mir nicht immer - nur wenn LibreELEC an ist - und ich will auch Licht, wenn der HTPC aus ist. Und das geht dann per WLED. Für die Zukunft möchte ich auch LEDfx zur Lichtsteuerung bei Musik einbauen. Dafür kommt mir WLED dann auch gelegen. Außerdem können über WLED auch mehrere Hyperion Instanzen angelegt werden.

    Grüße und viel Spass mit Hyperion