Beiträge von damjandim

Just a couple of updates on this thread, since I've been able to make this work even though hyperion.ng hasn't released alpha10 yet, so I had to do a workaround. What I did is get myself a NodeMCU controller, connected my LED strip to that and setup hyperion to work via udpraw. Basically hyperion on the RPi captures the screen and sends it via UDP to the NodeMCU which powers the LEDs. Works like a charm.

Only problem is that the current grabber which hyperion.ng uses on the RPi - DispmanX is broken on the RPi 4, and the team is on it developing a fix to this problem, which causes you to have limit the RPi Video output to Full HD (1080p) as well as the GUI to 1080p and 30Hz refresh rate in order to have a stable image.

Zitat von Lord-Grey

Support for Pi 4 Model B - 2GB v1.4 will come with the next release, see

https://github.com/hyperion-project/hyperion.ng/pull/1111

So the answer to my original question at the moment is actually: "No, it's not possible"

Zitat von davieboy

Code

2021-02-13T16:53:59.613Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: Hardware revision is not supported'

That doesn't look good.

Do by any chance have the LibreELEC Hyperion Addon installed?

I don't have it, no.

Zitat von davieboy

Its LibreELEC @jeroen warmerdam it is a linux distro but stripped back, bare minimum o/s to run Kodi and to keep footprint small, there is no package manager - apt is not installed, any packages required usually need to be compiled or installed in form of a kodi addon, LibreELEC do provide a lot of default packages bundled together for the Pi tho https://libreelec.wiki/installation/add-ons but im nearly 90% certain adding the SPI line to the config is enough to get the GPIO going, but maybe not and you could very well have solved his problem.

Try installing it by going to...
Addons -> Install form Repository -> LibreELEC Addons -> Program Addons -> Raspberry Pi Tools

Install and reboot - see what happens

Zitat von Lord-Grey

What does the System-Log say?
If the LED-Device is off you should find the reason there....

What happens when you enable the LED-Device via the Remote Control again?
Can you share the log after enabling the device?

I removed the Hyperion installation and reinstalled it. I also installed the Pi Tools on LibreELEC. Once I launch the WebUI for the first time the LED Device status is ON. Then I try inputting my hardware config and when I'm done the LED Device status goes off. Here's the log at this point:

2021-02-13T16:53:25.411Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.100.4
2021-02-13T16:53:25.412Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.100.4' switch to Hyperion instance 0
2021-02-13T16:53:25.958Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.100.4
2021-02-13T16:53:25.976Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1063:handleLoggingCommand()) log streaming deactivated for client  ::ffff:192.168.100.4
2021-02-13T16:53:59.605Z [hyperiond LEDDEVICE] (DEBUG) (LedDeviceFile.cpp:85:close()) File: /dev/null
2021-02-13T16:53:59.607Z [hyperiond LEDDEVICE] (INFO)  Stopped LedDevice 'file'
2021-02-13T16:53:59.609Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: disabled
2021-02-13T16:53:59.609Z [hyperiond LEDDEVICE] (INFO) Start LedDevice 'ws281x'.
2021-02-13T16:53:59.610Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:148:init()) deviceConfig: [{"colorOrder":"rgb","currentLedCount":167,"dma":5,"gpio":18,"hardwareLedCount":167,"invert":false,"latchTime":0,"leds":256,"pwmchannel":0,"rewriteTime":1000,"rgbw":false,"type":"ws281x","whiteAlgorithm":"subtract_minimum"}]
2021-02-13T16:53:59.611Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:407:setLatchTime()) LatchTime updated to 0ms
2021-02-13T16:53:59.612Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:428:setRewriteTime()) Refresh interval = 1000ms
2021-02-13T16:53:59.612Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:434:setRewriteTime()) RewriteTime updated to 1000ms
2021-02-13T16:53:59.613Z [hyperiond LEDDEVICE] (DEBUG) (LedDeviceWS281x.cpp:59:init()) ws281x strip type : 1050624
2021-02-13T16:53:59.613Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: Hardware revision is not supported'
2021-02-13T16:56:16.443Z [hyperiond EFFECTENGINE] (INFO) Run effect "Rainbow swirl fast" on channel 0
2021-02-13T16:56:16.443Z [hyperiond EFFECTENGINE] (DEBUG) (EffectEngine.cpp:183:runEffectScript()) Start the effect: name [Rainbow swirl fast], smoothCfg [0]
2021-02-13T16:56:16.443Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:registerInput()) Register new input 'System/EFFECT' with priority 0 as inactive
2021-02-13T16:56:16.466Z [hyperiond EFFECTENGINE] (INFO) effect finished
2021-02-13T16:56:16.478Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 0
2021-02-13T16:56:16.478Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[0], previousPriority[250]
2021-02-13T16:56:16.513Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 0 is now active
2021-02-13T16:56:19.728Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:315:setCurrentTime()) Timeout clear for priority 0
2021-02-13T16:56:19.729Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 0
2021-02-13T16:56:19.729Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[0], previousPriority[0]
2021-02-13T16:56:19.978Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 250
2021-02-13T16:56:19.978Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[250], previousPriority[0]
2021-02-13T16:56:52.259Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.100.4

When I try to turn it on manually it just goes off again and nothing more is logged.

Zitat von davieboy

We are all out of codes now :LOL:

Weird how all of a sudden there are at least 3 people struggling to get their setups running aint it?

1 more code

Code

systemctl status hyperion

Alles anzeigen

● hyperion.service - Hyperion ambient light systemd service
   Loaded: loaded (/storage/.config/system.d/hyperion.service; enabled; vendor p
   Active: active (running) since Sat 2021-02-13 15:35:05 CET; 4min 4s ago
Main PID: 616 (hyperiond)
   Memory: 13.8M
   CGroup: /system.slice/hyperion.service
           └─616 /storage/hyperion/bin/hyperiond --userdata /storage/hyperio


Feb 13 15:35:06 LibreELEC hyperiond[616]: 2021-02-13T15:35:06.189 hyperiond HYPE
Feb 13 15:35:06 LibreELEC hyperiond[616]: 2021-02-13T15:35:06.238 hyperiond HYPE
Feb 13 15:35:06 LibreELEC hyperiond[616]: 2021-02-13T15:35:06.246 hyperiond WEBS
Feb 13 15:35:06 LibreELEC hyperiond[616]: 2021-02-13T15:35:06.246 hyperiond WEBS
Feb 13 15:35:06 LibreELEC hyperiond[616]: 2021-02-13T15:35:06.247 hyperiond WEBS
Feb 13 15:35:09 LibreELEC hyperiond[616]: 2021-02-13T15:35:09.365 hyperiond HYPE
Feb 13 15:35:09 LibreELEC hyperiond[616]: 2021-02-13T15:35:09.365 hyperiond HYPE
Feb 13 15:35:09 LibreELEC hyperiond[616]: 2021-02-13T15:35:09.365 hyperiond HYPE
Feb 13 15:35:09 LibreELEC hyperiond[616]: 2021-02-13T15:35:09.614 hyperiond HYPE
Feb 13 15:35:09 LibreELEC hyperiond[616]: 2021-02-13T15:35:09.614 hyperiond HYPE

I should mention that the setup I had on the Pi3 was with the old hyperion using hypercon, not hyperion.ng and the web ui.

Also pretty weird, in the hyperion web config:

Yeah, the whole setup worked on RPi 3 for months, it's as though the RPi4 is just not outputting anything on the GPIO18 pin. My localIP of the Pi4 is 192.168.100.54

There is no hyperiond file at the path you specified.

I’m using a WS2812 strip, connected through a level shifter with it’s own PSU. I kept all of the connections the same, I just moved the DIN pin from my Pi3 to my Pi4 on the same pin (GPIO18), and also moved the ground from my Pi3 to my Pi4 on the same pin. I’ve now added another common ground from the ledstrip to the Pi per the above instructions, but nothing changed.

Hyperion log shows no errors or warnings. Also, when I go into hyperion dashboard the led device status is off. The controller type I’ve set is ws281x RPi PWM.

No, brand new SD card flashed with LibreELEC, and I'm using an official RPi 4 power supply for the Pi 4, and the leds have their own power supply anyway.

@davieboy I did everything as explained there, I got the playback stable by limiting the menu to 720p, but still nothing shows on the LEDs, not even the solid color tests from the Web GUI. This same setup worked on my RPi 3, I just reconnected the pins to the RPi 4, so there's definitely nothing wrong with connections.

Thanks, I'll give it a try and post back my findings.

@davieboy I tried that one first but it didn't work for me. After I did the setup on the web UI the leds didn't light up and the video on the kodi started cutting off.

After searching for hours and hours on this and other forums it still remains unclear: is there any way to get either hyperion or hyperion.ng up and running currently on RPi 4 running LibreELEC? If so, can anyone provide the appropriate data so we can compile a tutorial.

Hey @dcartron, I want to connect my Yeelight Lighstrip like you described, did you manage to do it?