Beiträge von koen

  • Status stopped: Error: hyperion.service: Changing to the requested working directory failed: No such file or directory

    Strangely enough, I'm having the same issue as before with my previous instance of the RPi with an older version of Hyperion.ng installed an with my older, USB/loop grabber.


    From time to time, the image of the TV goes black, LEDs and audio stop and after a few seconds it's back. All via incoming signal from Chromecast, doesn't matter if it's a Disney+ (encrypted?) signal or plain YouTube.


    This is either with the FeinTech and EZCOO splitter and I've set all different copy/4K settings/scaler (4K > 1080 for the grabber)/etc. settings I can to test out on these splitters. HDMI 1 out always goes to the TV, HDMI 2 out goes to the USB grabber.


    Perhaps it's the USB grabber that's too light? It's connected to a USB 3.0 port on the Pi.


    Power for the splitter goes via the USB 2.0 port on the Pi: could that be it? Perhaps better to use USB from the TV for power? Or external? Just thinking out loud here.


    I've also played around with the Hyperion settings via the dashboard. I've set the resolution to it's lowest, changed the frame rate (20 and 10), size decimation (default 8, changed to 16) and frame skip (0 and 1) - all still the same issue. So I don't think it's the Pi's hardware that isn't capable enough for example.


    Any ideas?


    Can't wait for the RULLZ btw, I hope that one solves the issue as the chip is newer (if I'm correct).

  • Status stopped: Error: hyperion.service: Changing to the requested working directory failed: No such file or directory

    Soooo, small update (with major results).


    I have now in use:

    - FeinTech VSP01201 HDMI splitter

    - Papeaso 4K HDMI to USB with MS2109 chip


    And it works fine! Had some issue with my RPi as it didn't appear to connect to WiFi: reboot with LAN cable and I've set 'wait for network to boot' and again the WiFi SSID and password via sudo raspi-config


    That worked out, but now the image was inverted (left/right mirrored), so I had to change the LED layout.

    Then I had the issue that the instance was set to RGB but needed to be set as GRB.


    It's even better now, as there is way less input lag on the LEDs than I had before with my 'old' setup. So I'm very pleased it's working and even better than before.


    Thanks for the help over here!

  • Status stopped: Error: hyperion.service: Changing to the requested working directory failed: No such file or directory

    I've re-installed Raspberry Pi OS and installed Hyperion 2.0.14 on this device. Out of the box, all seems to work. Could set all the parameters the same as before and the LEDs enable fine.


    I still have the issue of my image not being capture (I think?) correctly from the Chromecast or any other input, into the RPi. The colord blobs keep spinning around the TV, but no image gets synced. I'll try with my old capture card and otherwise I'll best go for a USB card (HDMI > USB) and a HDMI splitter. Any suggestions for that one? Budget: 50 EUR in total and it all should be fitting behind the TV (there's some room).


    - edit -

    My old loop capture card has the same issue: moving blobs around as idle, no sync with the image on screen.


    - edit 2 -

    When checking the status of the hyperion service, I still (again?) get this, even with the old capture card with loop that has been working before:



    - edit 3 -

    With the other capture card, I obv. had to re-select the right USB capture input in the Hyperion Web UI. After doing so, I get the LEDs to light up differently, only it's fading in and out/flickering. Also, it's not really a sync: it's more that all the LEDs light up kinda white/purple with some other colors, but they don't change when the image changes on TV. It does not correspond.


    I used the default settings: 640 x 480, 5 FPS, 8x size decimation.

    I just have purchased the following items to test out and hopefully they will resolve the issues I'm encountering:


    Aliexpress (ETA: end of the month):

    - RULLZ HDMI Video Capture with MS2130 chip


    Amazon (ETA: tomorrow):

    - Papeaso 4K HDMI to USB with MS2109 chip

    - EZCOO HDMI Splitter EZ-SP12H2

    - FeinTech VSP01201 HDMI splitter



    Found this information over here: Splitter / Matrix / Grabber Übersicht/Overview

  • Status stopped: Error: hyperion.service: Changing to the requested working directory failed: No such file or directory

    Thanks, I'll check that out.

    If it doesn't work, I'll make a clean install of HyperBian: I have screenshots of each screen just in case, so I should be able to set up via the web interface.


    This time I tried updating, but the update button does not work, so I installed the latest Hyperion instance and then in the web UI it showed the latest version. The update seemed to work fine, but after a powerloss it didn't anymore.


    Would you suggest to use a seperate USB grabber? And then simply use an HDMI splitter instead?

  • Status stopped: Error: hyperion.service: Changing to the requested working directory failed: No such file or directory

    After some looking around on the forum and as I have a FHD TV, I now got this grabber:


    But the grabber should not matter for Hyperion to boot up/load, right? If it's an incompatible grabber, I would have a different issue.


    Anyways: with the command /usr/share/hyperion/bin/hyperiond it workes, only your other commands (run under user root) don't work. I still get the error:


    Code
    root@HyperBian:/home/pi# systemctl start hyperion@pi
Failed to start hyperion@pi.service: Unit hyperion@pi.service not found.

    The video coming out is from a Chromecast and even the default home page (photo) does not work with the LEDs. The standard effect is just being played, meaning - in my case - a few warm blobs are swirling around the TV, slowly.


    Next, I get this live logging from the instance running in my console:


    Code
    pi@HyperBian:~ $ /usr/share/hyperion/bin/hyperiond
2023-01-31T08:16:09.561 |I0| LEDDEVICE         : <WARNING> SPI rate 5000000 outside recommended range (2050000 -> 4000000)
2023-01-31T08:16:11.513 |__| V4L2              : <ERROR> Throws error nr: VIDIOC_DQBUF error code 19, No such device
2023-01-31T08:16:11.513 |__| V4L2              : <ERROR> VIDIOC_STREAMOFF  error code  19, No such device

    What would this error be?


    So, OK. It seems I'm one step further: now I finally can access the UI web interface again, but in here nothing has changed and I've updated the USB grabber:



    It's the only USB grabber in there.


    Any idea?

  • Status stopped: Error: hyperion.service: Changing to the requested working directory failed: No such file or directory


    In an attempt to update my Raspberry Pi with HyperBian to the latest stable (v. 2.0.14) I can't get the Hyperion service to start. Before the update and right after the update, I was perfectly able to use Hyperion and the issue I had was that the LEDs and TV image went black/dark for a second from time to time. I hoped the update would resolve (and, updating should be done once in a while).


    I now do think it's the grabber that was faulty.


    I have had the power of the Raspberry Pi to be turned off and after this, I'm having this issue.


    Weird thing, I stumbled upon this https://docs.hyperion-project.…tml#example-backtrace-log page and I've followed the steps with great luck!


    So:

    Code
    gdb
file /usr/share/hyperion/bin/hyperiond
run


    And suddenly the LEDs turned on (rainbow) and I could access the UI webpage again. Only, I cannot leave this gdb opened and needed to quit. After this, I wasn't able to load the UI webpage anymore.


    Anyone any clue?

  • Android App: Hyperion LED Control

    With a lot of help, I have been able to get my Hyperion instance up and running and I'm enjoying it for a couple of months now. The only thing missing for me was an easy way to enable or disable the LED instance (turn this thing on and off). Both my Chromecast and Nintendo Switch are connected to the HDMI switch and can make use of the visualisation, but it simply does not always make sense to me to have it enabled. Also, I can't really shut down my Chromecast and when my TV is off, Hyperion would keep running.


    I have been enabling and disabling the LEDs via the Hyperion dashboard (via IP address) on my phone, but it's just not easy enough. Next to that, I have had Termux installed on my phone and I have been using shortcuts from this app via my phone's homescreen to start two shell scripts: one to enable and one to disable the LEDs. But with switching to another phone, I wasn't able to get this up and running that easily.


    That's why I decided to create this very simple and easy to use (and setup) Android app. It's called 'Hyperion LED Control' and does just that. Two huge buttons: one to turn the strip on, one to turn it off. The only thing you would need to do is set up the right IP address and port in the Settings section of the app.


    I hope this would be of any use to anyone. My way of trying to give something back to this community.


    No adds, no account, no payments and no information or whatever is stored. Just a simply app that only does 1 thing. Enjoy!


    Link to download: https://play.google.com/store/…ojects.hyperionledcontrol

  • sk6812 (spi?) met enkel de eerste LED groen

    Lijkt helemaal prima te werken zo! Baut Rate wel wat mee gespeeld. 5000000 lijkt de beste optie voor mij.


    Merk wel dat er wat vertraging zit in de beelden op TV en die in de LEDs. Heb de resolutie al verlaagd naar 640x480 en FPS naar 20.

    Verder kan ik niet al teveel tegelijk aanpassen in een webUI sessie: als ik veel dingen aanpas of wijzig, blijft Hyperion/HyperBian hangen en is een reboot via SSH nodig.


    Nu net de RPi 4B aangesloten. Eens zien of deze met USB3.0 en hogere snelheid over het algemeen een beter resultaat geeft, ook met een hogere resolutie. Hopelijk dat dit laatste euvel ook opgelost is met de snellere RPi4.

  • sk6812 (spi?) met enkel de eerste LED groen

    Bedankt voor je reply! Heb opnieuw HyperBian geflasht, root access gegeven, SPI enabled, etc.


    Nu kan ik inderdaad kiezen voor ws281x en sk6812spi en de LEDs gaan allemaal aan, hoewel ze bij sk6812spi knipperen (1 seconde aan, 1 seconde uit). GPIO 10 aangesloten en ingesteld.


    Ik denk wel dat m'n kabeltjes te dun zijn, want er komt een beetje rook van af :) straks even langs de bouwmarkt.


    Is er een specifiek voordeel om juist voor SPI t.o.v. PWM te kiezen (dus controller sk6812spi t.o.v. ws281x)? Mijn sk2612 LED strip natural white LEDs extra. Misschien maakt dat de keuze voor de een of de ander beter?


    - update -

    Als ik ws281x kies als Controller Type, blijven de LEDs wit. Altijd.

    Als ik apa102 kies als Controller Type, blijven de LEDs wit. Altijd.

    Als ik sk6812spi kies als Controller Type, veranderen de kleuren zoals moet (middels RGB Byte Order Wizard, bijv.), maar flikkeren ze contant. Baut Rate stond op 3000000, aangepast naar 1500000. Nu beter, maar ook geen kleur


    Verder: alle kabels vervangen voor 1,5mm2 en met lasklemmen doorverbonden. Stuk veiliger nu.

  • sk6812 (spi?) met enkel de eerste LED groen

    Hoi,


    Ik heb HyperBian op zowel een RPi 3B+ als 4 geïnstalleerd (twee aparte SD kaartjes), maar bij het aansluiten van de LED strip op een aparte adapter met de data pin naar GPIO 18 (ook GPIO 10 geprobeerd), krijg ik enkel de eerste LED aan. Bij GPIO 18 is deze LED groen, bij GPIO 10 is deze wit.


    Allereerst lijk ik nergens te kunnen vinden welke GPIO er standaard gebruikt moet worden bij een sk6812 strip en in de nieuwere Hyperion kan ik deze GPIO ook niet aanpassen via de webUI.


    Voor controller type kies ik sk6812spi, ik heb SPI enabled in raspi-config. Maar nu de settings daar in: ik laat alles op standaard staan en heb tusesn de twee SPI Devices gewisseld: 0.0 en 0.1, maar zonder resultaat.


    Voor LED count heb ik even 200 ingesteld en de verdeling is 60, 60, 40, 40.


    Ook als ik bovenaan de Wizard wil uitvoeren, blijft de LED groen of wit.


    Wat doe ik verkeerd? Welke GPIO moet ik gaan gebruiken?