One last option might also be to delete the existing hyperion configuration database...
Beiträge von Lord-Grey
-
-
Have you tried to remove Browser cookies?
In addition, what rpi OS are you running stretch or buster?Does the armv6l package work?
-
dinvlad Bear in mind that the configuration API is not an officially exposed one. There might be negative side-effects when doing inconsistent updates to the configuration.
I just mention, in case you see unexpected misbehavior…
-
Wenn Dir der Test sagt, die maximale Baudrate ist 500kHz, dann konfiguriere das doch mal in hyperion und nicht 1 MHz.
Hyperion.NG hat eine Konfigurationsdatenbank. Du brauchst kein extra File wie bei Hyperion Classic.
Also Du solltest nicht von alten Logs auf das Verhalten des neuen Systems schließen…
-
Switch to debug mode, save and restart Hyperion. Then try again checking the log output
-
Does a simple color effect started via the Remote Control Screen work?
Suggest you disable smoothing for the moment…
-
[hyperiond LEDDEVICE] (ERROR) Device disabled, device 'sk6812spi' signals error: 'Failed to open device (/dev/spidev0.0). Error message: No such file or directory'
-
An have a look into the hyperion log, if there are any errors reported…
In the Ui: System->Log
-
Four things for investigation
1. It looks like your Grabber is connecting/disconnecting frequently.
Check the USB Kabel (or grabber)
2. The log does not show the start of the LED Device. I suggest you disable the Grabber for now and restart Hyperion.
3. Try a simple Color Effect via the UI. Do the LEDs react?
4. Share the log.
-
Sizo Thanks to Paulchen-Panther. He updated the wx281x library to the latest version in the master.
So you should now be able to just clone the master branch without additional activities.
On the LED topic. The log looks good. You might want first to simplify your configuration, i.e. Smoothing off and start/background effects off, just to sort out side effects.
It is likely that the problem is more hardware setup related.
Here there are many people in the forum who are best placed to help you given their experience with such a set-up.
PS: Note sure, if you mean "not all leds are working" (but some) or "all leds are not working" (none of them) -
You can use long wireless wires
There are multiple network devices supported by Hyperion, e.g. WLED, Philips Hue, Cololight, Yeelight…
-
If you are on a PC linux and have everything cloned on your disk, you can just run in the hyperion home-directory
./bin/create_all_releases.sh
That build hyperion, as well as creates a tar and packages.You then execute hyperion via
./build-x86-64/bin/hyperion -d
You need to check for the real directory name, as I just do not have access to the system.
Alternatively, you can execute the commands per git how-to-compile documentation or per video.Hoping the above gives you an easier start...
Edit: You can also run the same on e.g. an rpi, but than you need to slightly modify the create_all_realeses script and have a different build directory name. -
-
Looks like we need to update the ws281x library in the master again, as new models are now out there...
-
With the next release you can visualize the signal detection area. Hope that will help you finding the correct area which works with your grabber. It is the dotted line in the picture below.
Comparing a whole picture is too resource intensive…and might only work for specific scenarios and is not a generic solution.
I think you still see the problem, as your config is not appropriate…
-
The Master Branch includes the latest updates and is not equal to the Alpha-9 release.
It is ahead alpha-9, but has not been released, yet.
At the time, I wrote the previous answer, PR1164 was not merged.
As you see, I stated "use a development build artifact e.g. from", which means you need to select a different PR now.
You can try #1246.Artifacts you find under "checks"
-
-
-
Maybe you would like to share a Hyperion Log output? Hyperion-UI, System->Log
-