Posts by Lord-Grey

    Suggest you have a look at the error messages you shared before.


    2025-01-08T22:57:49.328Z [V4L2] (ERROR) Throws error nr: Cannot open '/dev/video14' error code 13, Permission denied


    Try adding the user you are running hyperion with to the „video“ group

    To free WLED from Hyperion you have various options:


    - Quit Hyperion

    - Suspend Hyperion via the Systray, UI or API

    (Resume, if you want to take over again)

    - Lock your Screen


    I aslo wanted to make Hyperion launch automatically when booting my computer. How can I do it ?

    If you are on Windows, just enable it via Systray. On other system create a systemd service.

    PPaul Could you try running the following python script against Hyperion, please?
    (You can also run it on your windows machine; Just change the url in the script)

    It tries to send images with 20fps for 60 seconds (you can change the parameters easily).
    Every 10 images it alternates to another one, so you should see updates in the preview.

    At my test installation the Websocket fails after ~20 seconds.
    It it a know issue that the Websocket has a problem with many updates, but I did not expect it as bad as this...
    This would require further investigations. Happy, if you file an issue....


    Reis Looks like I did not see the web-socket.txt which was provided after I read the initial post.

    I can see that valid images are provided.

    which contains exactly what I'm seeing in the preview: pitch black background, but coherent LEDs output.

    PPaul You see pitch black background, as the middle part of the images is provied with transparent color.
    Reis only creates a frame of color pointes captured, I assume to streamline processing.
    HyperTizien does not send an image of the screen, but a 16 picked colour for each side, i.e. do not expect an image!


    Here is one sample image that was part of your log.



    I am further investigating on the close issue

    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