Is there any chance of this being added to the Hardware tab when using the ws281x driver so a manual update is not needed?
Ken
I don’t know but it’s like that in Hyperion NG.
Is there any chance of this being added to the Hardware tab when using the ws281x driver so a manual update is not needed?
Ken
I don’t know but it’s like that in Hyperion NG.
Thanks man, will try it when I get home and let you all know about my findings. In the first case where we add the dmanum:10 parameter in the configuration do we have to change GPIO pin? You don't mention something like that, but just to be on the safe side.
No, no. If you try the first solution, you remain on the same GPIO pin. DMA is, as I understand, some kind of a channel of communication only to make devices, controllers etc. not interfere each other.
Thanks a lot for that info but I am having difficulty understanding what I should do. Could you please explain? (Sorry for my total noooooooooobness)
do total reinstall (as assumed – file system is corrupted) and then while creating hyperion.config.json, add (before launch!) to the "device" configuration therein additional parameter:
"dmanum" : 10
I didn't try it but it seems to work because on my machine the issues were strongly connected so I think it was actually one issue.
However, for your safety, backup your working SD card.
If it doesn't work, you can try with ws2812spi device type but it voids RPi warranty (as you need to add force_turbo=1 parameter to the /boot/config.txt file to make it work properly, at least it was needed in my case) and changing data GPIO pin to 19 (GPIO 10 as I remember).
Sorry to be a pain in the ass but could someone more experienced give us a hand with this issue?
Thanks in advance!
I did it with ws2812spi (but lost warranty) trick mentioned before but it looks this one solves it as well and is safer (no warranty voiding): https://hyperion-project.org/t…ds-to-ext4-fs-errors.967/
Hey guys, thanks for your input. Unfortunately no progress has been made. Tried all of your suggestions and nothing still the same problem. I have no issue with blinking lights and the setup is done like this:
https://www.instructables.com/…perion-on-Raspberry-Pi-w/
apart from the fact that I was using Libreelec and not OSMC. It is working fine with Libreelec 7 and before that with Openelec of the same kodi version (16.x) so I can speculate it has somehing to do with the new kodi base and possible configuration changes. I have to say that last night I tried to update the working hyperion installation using HyperCon and also manually using the script. I was getting an SSL errror when it would download the latest release. Not sure which version I have to be frank... How can we check the hyperion version we have installed?
I would hope someone from the developers team to give us some help but I think everyone is on vacation...LOL
Since you ask, then you are on a stable version However you can check your version by typing in command line (or SSH) hyperion-remote and it just prints out.
Do you have a resistor on the data line? A resistor on the data line usually fix that.
I'm running out of ideas how to help.
I have a Rpi3 with libreelec 8.0.2 and the release version of Hyperion, with ws2812b's led's. However I'm using a aurdino nano clone to drive the led's. I completed that setup about two weeks ago. It works. I downloaded a fresh copy of Libreelec and Hyperion/Hypercon then. *Shrug* However, I like a good puzzle.
Yes I do have a resistor. There was no problem with blinking on ws2801x led device set. So I think it may be config-related or something like that.
Maybe @FilthX will come to a solution.
Nevertheless, thanks for help!
Have you tried "ws2812spi" as a devise type instead of "ws281x"?
What pins are the leds attached to on the RPI? If the above is not the remedy it for you.
I've tried this method now.
So, at first my LEDs were connected to GPIO 18 (PIN 12) and after change to ws2812spi nothing worked (of course). So I switched pin to GPIO 10 (PIN 19) and then LEDs were working but not properly because it started blinking white every few seconds. So I switched back.
However, I don't know if it resolves this lag/boot issue because I am still on the not on the updated machine.
EDIT: I tried it with stable hyperion, not NG.
Alles anzeigenOK, spent the last couple of days trying to resolve this issue. Tried with the Libreelec SD creator and with a clean NOOBS installation but it will not work. After I install Hyperion using HyperCon and the first reboot, I will try to send my configuration file but it will not transfer it to /storage/.config. I can copy the file manually using WinSCP and Hyperion will work. After a reboot it will stop working and it will be just stuck on the Libreelec logo. I can ping the machine but SSH is not up yet..
The link contains the SSH output
[MEDIA=pastebin]S37FcAwq[/MEDIA]
The link contains my hyperion.config.json
[MEDIA=pastebin]ygbpaReZ[/MEDIA]
Thanks in advance
Edit: If I comment out the loading of hyperion in autostart.sh, libreelec boots fine. If I start it manually by typing
/storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config.json > /storage/logfiles/hyperion.log 2>&1 &
hyperion shows the rainbow splash and works ok but I am experiencing severe lag on kodi.
What could it be?
I have the same exact issue on OSMC (since the may update, I guess). It persists on hyperion.NG as well as the stable one. If hyperion is off – everything works. If on – it doesn't boot or (if started after boot) the lag is huge and it makes machine completely unusable.
Unfortunately, I have no idea for a fix.
As for troubleshooting, my config is: RPi 3 with WS2812 LEDs (3-wire PWM ones).
Since the ERROR says ’No valid config found’, then do you have hyperion.config.json placed in /etc/hyperion?
I think you should install sshpass and then the following command should work:
sshpass -p 'YourPassword' ssh user@host `/storage/hyperion/bin/hyperion-remote.sh -e "Goal" -d "40000"`
However I've never used sshpass by myself, so can't guarantee it's ok.
You can also add --print to your hyperion-remote command and the JSON result sent to the hyperion RPi via TCP should execute the desired effect.
Fushicai USBTV007 works properly (included USB cable was broken but it's not a big problem)
Is there any ETA of ng beta?
No-signal rainbow detection sounds great but the current stage of development is too unstable for me so I'd love to know when some easy to install version will be released.
Unfortunately no success. Spend a few hours today and still errors. I couldn't make ffmpeg output as v4l2. Tried luck with GStreamer but still nothing (btw during my tries CPU usage raised significantly so it may be a bad idea even if works).
I guess I'm gonna give up and just buy other grabber – this time a proper one.
I have a similar issue, did you solve it?