Raspberry Pi

All blog posts published under Raspberry Pi tag

Updates to Screenly OSE v0.17
Updates to Screenly OSE v0.17

Screenly originally started as our founders’ side project with the Raspberry Pi, and that project, Screenly OSE, has since grown to become the most popular open source digital signage solution on GitHub. While Screenly has evolved into a commercial digital...

Updates to digital signage software Screenly OSE v0.16
Updates to digital signage software Screenly OSE v0.16

We have some exciting updates for all our Screenly OSE users. If you are unfamiliar with Screenly OSE, it stands for Screenly Open Source Edition. Screenly OSE is Screenly’s free version of digital signage management software. In this post, we’ll...

Troubleshooting with the Raspberry Pi
Troubleshooting with the Raspberry Pi

The Raspberry Pi is a low-cost and energy-efficient mini-computer that can power your digital signage. In fact, Screenly’s digital signage player, the Screenly 2 Player, is built on a Raspberry Pi device. As with all technology, things can go wrong,...

Screenly Pro is now compatible with the Raspberry Pi 3 Model B+
Screenly Pro is now compatible with the Raspberry Pi 3 Model B+

This image is from the Raspberry Pi Foundation. Source. After much work from the Screenly development team, we are very proud to announce that Screenly Pro is now compatible with the Raspberry Pi Model 3 B+. Prior to this announcement,...

DIY digital signage with the Raspberry Pi
DIY digital signage with the Raspberry Pi

You’ve heard about digital signage, and you’re curious to learn more. Perhaps you’re just a techie who loves tinkering. Perhaps you’re considering launching digital signs at your business or organization once you figure out digital signage for yourself. Whatever your...

What even is the Raspberry Pi?
What even is the Raspberry Pi?

At Screenly, it is fair to say that we are obsessed with digital signage. It’s who we are, and we’re proud of it! Something else we are obsessed with is the Raspberry Pi. After some internal discussions, however, we realized...