I don’t know but Automatic update did not work (yet). I got it from there https://relkai.coreelec.org/?dir=addons/9.2/Amlogic/arm/service.hyperion.ng
1 Like
tested and yes it is fixed for me 2
I don’t know what to say but flickering on paused video is back again on 9.2.106 here. Do you get it too?
I have the same flickering on pause. Even though it’s way better than the versions before.
Is there any setting, to let the LEDs stay on, when a video is paused? I think in older versions of NG, the LEDs did stay on…
unfortunately unchanged. Error is still exist.
Hi. I have installed an arduino kit from aliexpress, I have installed hyperion in the latest version of coreelec and I have entered through the web interface. I have configured it and it has worked fine. I have restarted the tv box and the lights are fixed with random colors and when I enter the configuration web from the browser, I cannot access, it does not load. Do you know what is happening?
Edit: I have reinstalled and it works fine. Anyone know if it is possible to use a usb switch to also connect the arduino to another device?
How exactly would this release end up in coreelec? It was release last year in November but I’m only able to install Alpha 8 (which is shown as latest and greatest in kodi) at this very moment in January 2021 
I actually made a post about this here 
Looks like the addons need to be refreshed…
I currently uploading 9.2.106 and it should be available in the next half hour.
Maybe you need to refresh CE repo once.
2 Likes
I have some WS2811 LED stripe laying around and before I start cutting them into pieces I wanted to ask first: is it possible to directly connect the control line to my odroid N2 or do I need an additional arduino?
On CE-19 there is a option in CE settings/hardware to enable the SPI interface on the gpio header.
I tried it only once as I own a Arduino.
It was not running 100% smooth like with the Arduino, but it was working. Didn’t tested in more detail.
2 Likes
@Portisch Can you please tell me if the issue with Kodi Menu (Picture) capture not respecting “Reverse direction” settings should be reported to the Hyperion.ng guys or somewhere else?
This is the issue I’m talking about (3 photos at the bottom of this post): AMLOGICGRABB stops working after couple hours - Hyperion.ng
Also this reply: AMLOGICGRABB stops working after couple hours - Hyperion.ng
I think more the “Reverse direction” setting helps you to fix a wrong color mode or even a wrong wiring in your setup. or maybe the Ardunio firmware does twist your colors.
only way to prove your setup would be you pack everything in a box and send to a developer that he can check what’s wrong. there are just to many possibilities what could be wrong.
@Portisch I think that the “Reverse Direction” is for how you mount the led strips on your TV - clockwise or counter clockwise. The issue is that it’s proper when you play the video, it’s not proper in the Kodi menu and when displaying pictures. I’ll take it to the Hyperion team.
When I pause a show, Hyperion turns off and on repeatedly, read about it here before but couldn’t find the solution, where is the option to force enable Hyperion led?
2021-03-17T20:53:33.909Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2021-03-17T20:53:39.157Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now inactive
2021-03-17T20:53:39.158Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 255
2021-03-17T20:53:39.158Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[255], previousPriority[250]
2021-03-17T20:53:39.158Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:562:handlePriorityChangedLedDevice()) No source left -> switch LED-Device off
2021-03-17T20:53:58.908Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now active
2021-03-17T20:53:58.908Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 250
2021-03-17T20:53:58.908Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[250], previousPriority[255]
2021-03-17T20:53:58.908Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2021-03-17T20:54:04.157Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now inactive
2021-03-17T20:54:04.157Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 255
2021-03-17T20:54:04.158Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[255], previousPriority[250]
2021-03-17T20:54:04.158Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:562:handlePriorityChangedLedDevice()) No source left -> switch LED-Device off
2021-03-17T20:54:23.910Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now active
2021-03-17T20:54:23.910Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 250
2021-03-17T20:54:23.910Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[250], previousPriority[255]
2021-03-17T20:54:23.910Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2021-03-17T20:54:29.159Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now inactive
2021-03-17T20:54:29.160Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 255
2021-03-17T20:54:29.160Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[255], previousPriority[250]
2021-03-17T20:54:29.161Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:562:handlePriorityChangedLedDevice()) No source left -> switch LED-Device off
2021-03-17T20:54:48.914Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now active
2021-03-17T20:54:48.916Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 250
2021-03-17T20:54:48.916Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[250], previousPriority[255]
2021-03-17T20:54:48.917Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2021-03-17T20:54:54.164Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now inactive
edit: It is happening in Hyperion “Idle mode” and disabling background effect. How can I just ignore idle mode, and show hyperion nonstop? When I Activate background effect without any effect it just turns off hyperion, and start again when resume playing.
This issue is known and there is no solution for it so far.
When I Activate background effect without any effect it just turns off hyperion, and start again when resume playing.
seems like you have found a workaround?
Sadly no, it started to turn on-off with this too. 
I’ve found also Problems with the AMLogic platform grabber in combination with the V4L2 grabber. The AMLogic grabber somehow delays or even stops (when a video is paused) the video processing of the V4L2 grabber.
More details at: https://github.com/hyperion-project/hyperion.ng/issues/1218
This known issue is fixed with tomorrow nightly CE-19. The addon must be manually updated by the user as well the addon version is not changed.
This will be done on beta.10
3 Likes
Great news, thank you!
Do we need Nightly CE19 or we can update manually the addon without switching to nightly?