LEDs flickering in random colors

Addy_42 · 14. November 2022

Hey everybody,

i am a little frustrated. My LEDs are changing their colors randomly and rapidly, even though i am sending a solid color by:

Code

hyperion-remote -c blue

If i run f.i. that Knight-Rider effect, it is working (goes from one edge to the other and back) but with randomly changing colors.

I have:

- Raspberry PI 3 B

- WS2801 LEDs

- Power supply

- Grabber:

- Converter:

I have attached the Hyperion-Config-file i am using (https://pastebin.com/m9B7Kq54). But i am a newbie and not at all an expert for the configurations. So i am not sure if interference signals or configurations are the issue.

Can someone help me or guide through troubleshooting?

Thank you in advance

Config-file:

pclin · 14. November 2022

Does the RPI and the LED have a common ground.

The Hyperion Debug log says more than your configuration.

regards pclin

Addy_42 · 14. November 2022

Hey pclin,

thank you for your fast reply.

Code

2022-11-14T19:23:39.684Z [WEBSOCKET] (DEBUG) (WebSocketClient.cpp:215:sendClose()) Send close to ::ffff:192.168.2.119: 1000 
2022-11-14T19:23:39.989Z [WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.2.119
2022-11-14T19:23:40.085Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:129:handleInstanceSwitch()) Client '::ffff:192.168.2.119' switch to Hyperion instance 0
2022-11-14T19:23:40.387Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1184:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.2.119
2022-11-14T19:39:02.952Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1193:handleLoggingCommand()) log streaming deactivated for client  ::ffff:192.168.2.119
2022-11-14T19:39:02.958Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1184:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.2.119
2022-11-14T19:39:17.748Z [WEBSOCKET] (DEBUG) (WebSocketClient.cpp:215:sendClose()) Send close to ::ffff:192.168.2.119: 1000 
2022-11-14T19:39:18.050Z [WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.2.119
2022-11-14T19:39:18.143Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:129:handleInstanceSwitch()) Client '::ffff:192.168.2.119' switch to Hyperion instance 0
2022-11-14T19:39:18.453Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1184:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.2.119
2022-11-14T19:39:52.703Z [WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.2.119
2022-11-14T19:39:52.798Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:129:handleInstanceSwitch()) Client '::ffff:192.168.2.119' switch to Hyperion instance 0
2022-11-14T19:39:53.102Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1184:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.2.119
2022-11-14T19:39:57.342Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1530:handleLedDeviceCommand()) message: [{"command":"leddevice","ledDeviceType":"ws2801","params":{"discoverAll":true},"subcommand":"discover","tan":318}]
2022-11-14T19:39:57.347Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1554:handleLedDeviceCommand()) response: [{"devices":[{"deviceName":"0.0","systemLocation":"/dev/spidev0.0"},{"deviceName":"0.1","systemLocation":"/dev/spidev0.1"}],"ledDeviceType":"ws2801"}]
2022-11-14T19:40:01.384Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevice.cpp:135:enable()) Enable device ws2801'
2022-11-14T19:40:01.385Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device ws2801 ON
2022-11-14T19:40:01.385Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevice.cpp:485:powerOn()) Power On: ws2801
2022-11-14T19:40:01.385Z [LEDDEVICE|First LED Hardware instance] (INFO) Device ws2801 is ON
2022-11-14T19:40:01.386Z [LEDDEVICE|First LED Hardware instance] (INFO) LedDevice 'ws2801' enabled
2022-11-14T19:40:01.386Z [COMPONENTREG|First LED Hardware instance] (DEBUG) (ComponentRegister.cpp:82:setNewComponentState()) LED device: enabled
2022-11-14T19:40:02.077Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:178:registerInput()) Register new input 'System/V4L' () with priority 240 as inactive
2022-11-14T19:40:02.078Z [COMPONENTREG|First LED Hardware instance] (DEBUG) (ComponentRegister.cpp:82:setNewComponentState()) V4L capture device: enabled
2022-11-14T19:40:02.084Z [V4L2] (DEBUG) (V4L2Grabber.cpp:151:init()) Set device (path) to: stk1160 (/dev/video0)
2022-11-14T19:40:02.085Z [V4L2] (DEBUG) (V4L2Grabber.cpp:488:init_device()) Set device input to: Composite0
2022-11-14T19:40:02.085Z [V4L2] (DEBUG) (V4L2Grabber.cpp:507:init_device()) Video standard=PAL
2022-11-14T19:40:02.086Z [V4L2] (DEBUG) (V4L2Grabber.cpp:614:init_device()) Set resolution to width=720 height=480
2022-11-14T19:40:02.087Z [V4L2] (DEBUG) (V4L2Grabber.cpp:715:init_device()) Pixel format=UYVY
2022-11-14T19:40:02.116Z [V4L2] (INFO) Started
2022-11-14T19:40:02.118Z [V4L2] (DEBUG) (GrabberWrapper.cpp:62:start()) Grabber start()
2022-11-14T19:40:02.233Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:178:registerInput()) Register new input 'System/V4L' (V4L2) with priority 240 as inactive
2022-11-14T19:40:02.234Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:293:setInputImage()) Priority 240 is now active
2022-11-14T19:40:27.871Z [JSONSERVER] (DEBUG) (JsonServer.cpp:101:newConnection()) New connection from: ::ffff:127.0.0.1
2022-11-14T19:40:27.874Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:182:registerInput()) Reuse input 'hyperion-remote@::ffff:127.0.0.1/COLOR' () with priority 50
2022-11-14T19:40:27.876Z [JSONSERVER] (DEBUG) (JsonServer.cpp:117:closedConnection()) Connection closed for ::ffff:127.0.0.1

Alles anzeigen

pclin · 14. November 2022

Use the Copy Log to Clipboard function and upload as a file attachment.

There is a problem with the grabber.

You also use an analog grabber and converter. Digital grabbers starting at €10 are better and you no longer need the converter.

Beitrag

Splitter / Matrix / Grabber Übersicht/Overview

Übersicht von Splitter und Matrix die mit externen Grabbern funktionieren.
Lest euch die Beschreibungen genau durch und prüft ob Sie für euren Anwendungsfall geeignet sind.
DolbyVision kann nicht Scalliert bzw. umgewandelt werden!
Ausnahme HDFury Diva aber nur mit DolbyVision LLDV, das müssen die Quellen dann aber auch unterstützen.
HDR liefert bis auf HDFury Diva ausgewaschene Farben und muss kompensiert werden.

------

Overview of splitter and matrix that work with external grabbers.
Read the…

pclin

28. Februar 2022

regards pclin

Addy_42 · 14. November 2022

Zitat

Does the RPI and the LED have a common ground.

Yes

Zitat

There is a problem with the grabber.

Can it be fixed?

If i send a solid color and plugged out the grabber, it should work (to show a solid color), shouldnt it?

Zitat

Does the RPI and the LED have a common ground.

Yes, but i should double check all connections. Do you have an 100% correct image/photo with the PI3 Model B pins (how it should be connected) ? ....................................... Don't know if the informations in the web are 100% correct

Zitat

There is a problem with the grabber.

So i have several questions:

- To make all LEDs red (solid one color), i think the grabber does not matter (even if there is a grabber-problem too). If i turn off the USB input in the web-configuration or plugg out the grabber and set a color, its still flickering randomly. So what is the real problem here most probably?

- What is the problem with the grabber ?

- What make the digital one "better"? Will the results be the same (if its working)?

- Is it still possible to make it work with the current setup?

In the attached image you see how i have connected to the raspberry (Blue=DI, Green=CI, Black=Ground).

I have double checked the connections and removed everything else (grabber, keyboard and so on) and disabled USB input in HyperionConfig completely. So its just the raspberry and the led's.

Then i start the Knight Rider effect as you can see here:

Hyperion Knight Rider Problem

www.youtube.com

As you can see, the colors are changing, but they should be red only.

Addy_42 · 15. November 2022

I think it is a bug, as described here https://github.com/hyperion-project/hyperion.ng/issues/897 (solid colors lead to changing patterns).

Don't know how to apply the solution though......can someone help?

I solved the flickering issue. I didnt connect the ground from the raspberry to the stripe properly. I thought it can be connected anywhere at Ground-cables, but it had to be connected to data input of the first stripe. Now its perfectly working.

Now only the issue with the grabber is left. So i need to know what the problem is, if its solvable or if i need to buy a digital wrapper?!

Addy_42 · 18. November 2022

Servus,

danke dir für die Infos!

der Grabber ist da, aber es tut sich noch nichts.

Ich habe die configuration und Log angehängt.

Kannst Dur mir sagen was ich noch tun muss?

Danke Dir

Addy_42 · 19. November 2022

Sorry guys,

i was chatting with pclin and mistaked the windows and typed it in here in german.

I plugged in this digial grabber: https://www.berrybase.de/usb-hdmi-video-grabber-1080p and it ddnt work by plug n play unfortunately, i played with the configs but no luck.

After i cleaned the setup behind the tv this morning, i turned it all on and cleared the hyperion cache by ssh, it started working. I am super happy and enjoying the ambilight. I will post my config later, some of the latest settings made it work. Don't know which one currently......

Thank you so much

LEDs flickering in random colors

Jetzt mitmachen!

Ähnliche Themen

Sudden LED flickering in a perfectly working setup