Is RPI 4 + LibreELEC Possible?
- damjandim
- Erledigt
-
-
Also pretty weird, in the hyperion web config:
-
i am going out now, you guys have fun with codes
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
-
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.
-
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
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.
thats totally diffrent > you have now diffrent hardware and software so its a new installation >>> so we begin from the start.
did you update the whole library to make the GPIO's work?
if not then
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install libraspberrypi-dev -
Also pretty weird, in the hyperion web config:
turn off dispmanx grabber and your effects in idle, its at effects tab
-
Weird how all of a sudden there are at least 3 people struggling to get their setups running aint it?
yes it is, like strange saturday or something o_O
-
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 ToolsInstall and reboot - see what happens
-
as outlined by @davieboy in https://hyperion-project.org/t…ossible.11338/#post-34017
There is no need to install something extra.. -
Also, when I go into hyperion dashboard the led device status is off.
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? -
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 ToolsInstall and reboot - see what happens
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:
Code
Alles anzeigen2021-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.
-
-
I don't have it, no.
-
Support for Pi 4 Model B - 2GB v1.4 will come with the next release, see
-
Support for Pi 4 Model B - 2GB v1.4 will come with the next release, see
So the answer to my original question at the moment is actually: "No, it's not possible"
-
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.
thanks mate, now i understand much more why things can not happen on this OS
i played with it before with this OS, but KODI didn't show any movies although it was the same build ( krypton) i believe than i had on my pc.
so after a few days played with it ( movies just weren't going to run) but the same kodi in my pc performed beautifully! then i decided quits :singing:
-
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'
this is all you need to know, its not supported
-
So the answer to my original question at the moment is actually: "No, it's not possible"
Well it runs beautifully on Pi 4 Model B - 8GB v1.4 - Even with WS2812B's
-
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.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!