Screenly Forum

Does Screenly work on the Raspberry Pi 4?

I was on the verge of ordering 4 pi 3B+'s for the project I am working on with 3 synchronised screens running screenly.

  1. I read the Pi4 has some issues. Do any of these issues hinder Screenly? (ie, can I just run a screenly image for these pi4’s?)
  2. As the Pi4 has dual screen support, can I run 2 screenly instances, 1 for each screen?
  3. If either of the above is answered with a ‘no’, is there a timescale when support can be expected. Expecially for 1) I am willing to wait 1 or 2 weeks, otherwise I have to get the old 3B+'s anyway.

I read the Pi4 has some issues. Do any of these issues hinder Screenly? (ie, can I just run a screenly image for these pi4’s?)

There’s no built-in support for synchronized play. We’ve seen some people trying this with various hacks, but we have no official support for it.

As the Pi4 has dual screen support, can I run 2 screenly instances, 1 for each screen?

That’s not supported yet. Maybe in the future.

If either of the above is answered with a ‘no’, is there a timescale when support can be expected. Expecially for 1) I am willing to wait 1 or 2 weeks, otherwise I have to get the old 3B+'s anyway.

It’s a community project. Hence it really comes down to if someone writes the support for it.

My new Raspberry Pi 4 (2GB version) has just arrived today . One word first impression: faaasssst! :smile:

I installed Raspbian Buster Lite on it and tried the to install Screenly with the
bash <(curl -sL https://www.screenly.io/install-ose.sh) command, it went thru it seemingly without any problem, however I did not catch all the colored warnings. (We have them with RPi 3 also)

Unfortunaly this out-of-the-box install of Screenly does not start on reboot. I would appreciate any clue what to look at to make it run.

(Of course I am not looking for dual screen support, the same operation as on RPi 3 but on a faster hardware would be fine for now.)

Sorry that my question apears to be unclear. I already have the synchronisation in place (API calls from Screenly or other software (screen synchronising)) but mainly does it work. I see the answer of Matrix, and I conclude it does not run on boot (answer to my 1st question) and I gather from you that there are no options to have 2 instances of screenly running at this time, nor are they currently planned.

Thanks you for your answers.

Thank you for the quick review. I will hold back for a little while to see if you can get it to run on boot. Please advice us if it is solved.

I gather from you that there are no options to have 2 instances of screenly running at this time, nor are they currently planned.

It’s not on the immediate roadmap, but it partially comes down to support in upstream software (such as omxplayer). Without that, we won’t be able to add support for it. That said, we will experiment with it, but we will commit to any timeline.

Here’s the ticket for adopting Raspberry Pi 4 support: https://github.com/Screenly/screenly-ose/issues/1187

I have been able to get Screenly running reasonably well on a Pi4. It definitely was a challenge but it is doable.

@miosam. How were you able to do so? I’m new to RPi and ordered 4 RPi 4b’s for a video menu board project for a client and have not been able to get it to work. Just like @matrix above. I tried installing using the bash and it would not boot :disappointed:

Hi John,

It was a month ago and I recall that it was definitely a battle to get it to run.
Definitely not a rPi newbie task.

I believe I broke apart the bash installer script running it line by line in order to troubleshoot each step and see exactly where the failures lay.

I remember that I eventually had to disable all management of the wifi from within screenly and then setup wpa_supplicant manually.

Once I pulled out the screenly wifi management pieces from the script and met all the dependencies manually I could start up screenly manually just fine. I believe I might have auto-started it using rc.local instead of the installer’s method but that is probably just my old roots showing through. Hacking in rc.local is taboo of course but is an effective lazy-man’s method to get the job done.

I remember that I had to get creative and backport Buster manually on a few packages in order to meet some of the broken dependencies thereby really just breaking the system enough so it could function without grinding it all to a halt. It was a real Big Kludge the whole way but they do seem to be running just fine a month later. I doubt they could ever be updated though without pulling out my hair again. I only did it because I was buying time for an expected new version to come out that supported the rPi4.

One problem I never worked too hard to fix is that for some reason they like to recycle the wifi connection frequently after their daily reboots (Which I do with all rPi Screenly deployments) and when they get flaky like that they pull a new ip each time they cycle, sometimes every few minutes. A manual IP or reservation (in my case) fixed the problem. I am sure it can be fixed but it is something to think about, I was just happy they worked so I left well enough alone and got on with other things.

The first gen rPi4 has a defect in the boards which unless you are using the genuine rPi power supply is going to cause problems. I don’t know if I would really want to deploy such a kludged-up config and hardware bomb to a client site unless I was in real dire-straits and even then I would vlan them very far off the network to somewhere safe so they couldn’t become a security risk.

If you have a 3d printer and some smaller low voltage fans I would definitely print a case and install a fan to cool them, these rPi 4’s seem to run a lot hotter than the 3’s ever did.

M.

Thanks. This is a tad disheartening, knowing all that had to be done to get it to work… :disappointed:

Version jumps are not always simple in Linux Land.

I’m sure they will come out with a 4 version one day.

If you are in a bad way I could give you a copy of my anonymized image to download it’s 32gb though.

No promises, no warranties.

Sadly, I’m likely going to be looking at other RPi solutions other than Screenly… Thanks everyone for your help. :+1:

I have the same problem too. Testing Screenplay OSE on a Raspberry 3B works…but I need more browser functionality and perhaps a 4K resolution. Now the Model 4 is waiting for a test but I could not get it running. The help on GitHub for generating a new image is not easy for me and so I don’t know if I should ditch to another solution.

Why a Rasp 4 ALPHA version is not available for download?

Could someone who understands Github slang please clarify us what goes on here regarding the Pi4 support:
https://github.com/Screenly/screenly-ose/pull/1189

What does the “we can close it without merging” and “Thus this PR makes no sense :)” verdict 4 days ago means in plain English?
Is the problem solved ? ie. Screenly OSE runs on Pi4? If yes why is it not ‘merged’? If not solved, then why is the case ‘closed’. If the issue is ‘solved’, where is, what is the solution so we can all implement it on our Pi4s?
Excuse me my ignorance if it is obvious, but it seems to me many of us can also not figure it out.

1 Like