Most people think of a BrightSign player as a thing that plays - you load it with content, point it at a screen, and it pushes pixels. And yeah, if you’ve ever wired an RTSP camera feed into one, you know it’s a perfectly nice way to throw a live camera (or a few) on a wall. But that’s selling the box way short. There’s an NPU sitting in there, idle, and it can watch the room back.
I disable the cloud on every Shelly plug in my house. And that is exactly why I love Shelly.
Stay with me, because that sounds backwards. A friend called me on a different version of it: “You’re the local-LAN guy, but you use Ubiquiti’s UniFi cloud API to run your networks. Pick a lane.” Fair hit. It looks inconsistent. It isn’t — I was just naming the principle wrong.
I’ve written before about what a BrightSign extension actually is and about why edge AI has to run locally on signage. This post is the “show, don’t tell” follow-up. If you want to see what all that theory looks like as a running, watchable thing, there’s exactly one place to start: Argus.
Here’s a tiny, stupid problem that has stolen an embarrassing amount of my life: I plug a BrightSign player into my network, it grabs whatever dynamic IP the UniFi controller feels like handing out, and now I have to go find that IP before I can SSH in and do actual work. Claude skills and a new tool to the rescue!
Most people think of a BrightSign player as the little box behind a screen that loops a video. That’s true right up until you realize the thing is a full ARM64 Linux computer with an NPU sitting idle most of the day. And you can run your own code on it. Natively. That’s what an extension is, and once you grok it, a whole world opens up.
In recent years, digital signage has become a solved problem: push content to screens reliably, at scale, on schedule. That’s not enough anymore. The market is now demanding screens that perceive — that understand what’s in front of them and respond in real time. Most of the hardware deployed in the field today will fail at that job because the foundational assumptions are wrong. Here’s what’s actually required and why the infrastructure choices you make now will define your deployment for the next decade.