Shelly's First Camera, Judged From the Documentation

This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases. Disclosure.

Quick take: Shelly's first camera is a 1080p indoor unit at $49.99 that records to a microSD card, streams RTSP, and needs no subscription. Home Assistant 2026.9 added native support for it. The specs are modest, the openness is the point, and ONVIF is not part of the deal.

Let me start with what I don't have. There's no Shelly Camera on my desk, nobody shipped me one, and this site says plainly when a product hasn't passed through our hands. What I do have is a house whose automations run on Home Assistant OS on a Raspberry Pi 5 bolted to a DIN rail in the electrical cabinet, with Google Home as the layer the rest of the household actually touches. The cameras on this build are Reolink, and the reason had nothing to do with image quality. They hand over an RTSP stream and an official integration, so the footage belongs to the machine in the utility room instead of to an account. When a 40 euro camera turned up claiming the same trick, I spent an evening reading its documentation. So this product gets judged the only honest way available to me: on what its own paperwork commits to. Here's what's in there.

What Shelly Actually Put in the Box

Every figure below comes from the Shelly knowledge base entry rather than a press release summary:

• Model S1CM-0DXW00, 1920 x 1080 resolution, 110 degree horizontal and 70 degree vertical field of view
• Black and white infrared night vision, with no illuminator range published
• microSD support up to 512 GB, FAT32 formatted, card not included
• Two-way audio, plus motion detection across up to 10 configurable zones
• Power in at 5 VDC over USB-C, 1 A, with no battery and no PoE option
• Wi-Fi 802.11 b/g/n on 2.4 GHz and 5 GHz, plus Bluetooth 4.2
• 60 x 53 x 53 mm, 60 g, rated for minus 20 to 40 degrees Celsius, classified as a Gen3 device

Launch coverage puts the price at $49.99 in the US and 39.90 EUR in the eurozone, with TechRadar framing it as a Ring alternative you can run without paying monthly. Three months of Shelly Cloud come with the camera, and after that the paid tier, Shelly Premium, runs 3.99 EUR per month for a single camera. That tier is where the object detection lives, the part that separates people from pets and vehicles. Cloud only. Nothing on the device does it.

RTSP Is the Whole Story Here

Strip away the marketing and one line decides whether this camera belongs in a local stack. Does it give you a raw stream you can point your own software at? It does.

Shelly's documentation lists two protocols for video: WebRTC for peer-to-peer viewing, and RTSP for local streaming to a DVR or NVR. The device publishes two simultaneous H.264 streams, and the API documentation's own examples describe them as 1920x1080 at 25 frames and 1280x720 at 25 frames, with a bitrate range of 512 to 2048 kbps. If you've ever watched a dashboard chew through CPU because six tiles were each decoding a full-resolution feed, you'll understand why that second, lighter stream matters more than any AI feature on the box.

One catch, and it's stated plainly in Shelly's own text: the RTSP server is available and disabled by default. There's a config key, rtsp.enable, and until you flip it you get nothing.

How Home Assistant Sees the Camera

I checked this against the source rather than trusting a forum post. Camera support landed in Home Assistant 2026.9, released on 2 September 2026, contributed by the maintainer who already looks after the Shelly integration: a camera platform, a motion sensor, and a switch that toggles the camera's privacy mode. This is core, not a community add-on.

The official Home Assistant Shelly integration documentation then explains the mechanism. It uses RTSP streams, which you enable in the device's web panel under Camera and then Settings, and it creates one camera entity for each available stream. It also notes that Stream 1 is disabled by default.

That last sentence is the kind of thing that costs people an hour. You add the device, you see one entity where you expected two, and you assume the integration is broken. It isn't. Go and enable the disabled entity. For anything else that refuses to appear, the usual suspects are covered in our guide to Home Assistant not discovering devices, and the broader Shelly setup path is in the Shelly and Home Assistant integration guide.

What RTSP Does Not Promise

Here's my complaint, and it's a real one. RTSP is a stream, not a standard for everything else a camera does. The word ONVIF appears nowhere in Shelly's knowledge base entry, nowhere in the API documentation, and nowhere in the Home Assistant integration page. It does appear in the pre-launch write-ups from February, which expected both protocols, and those pieces have been quoted ever since as though the expectation was a fact. It wasn't. So discovery, PTZ conventions and standardized event handling are off the table until Shelly says otherwise, and if your recorder enumerates devices through ONVIF, plan on hand-configuring stream URLs instead.

The Cloud Is Still in the Setup Path

Subscription-free is not the same as cloud-free, and the difference deserves saying out loud. The documented setup path runs through the Shelly app, and nothing I read states whether the camera can be provisioned end to end without ever creating an account. It exposes a local web panel and its own access point, so local-only setup looks plausible. Plausible isn't documented. What is clear is what happens afterwards: the stream, the card and the local API all live on your LAN, so the camera keeps working when the internet doesn't.

That distinction has a price tag people forget. A camera you can reach from a browser on your own network is a camera you now have to secure yourself, with a real password, a segmented network and no port forwarding. Our notes on hardening a Home Assistant install apply to the camera as much as to the server, because a video device with a weak password is worse than no video device at all.

Photo by Jordan Harrison on Unsplash.

A microSD Card Is Not a Recording System

Local storage is the feature every headline led with, and it's genuinely good at this price. It is also the feature most likely to disappoint. A 512 GB card in a camera solves one problem: clips exist without a subscription. It does not solve the problems an actual recorder solves.

Consider what a card can't do. It can't survive the camera being unscrewed and carried off, which is the exact scenario the camera was bought for. It can't give you one searchable timeline across four devices. And flash under continuous write load has a finite life, which is why proper surveillance cards are sold as a separate category. My honest recommendation, and plenty of people will disagree: treat the card as a buffer for when the network drops, and let Frigate or a similar recorder on your own hardware pull the RTSP stream and hold the archive. Shelly names Frigate itself as a supported target, so this isn't a workaround anyone is being clever about.

Buried in the API documentation is the detail that made me sit up. Recordings can be written to an NFS share as well as to the card, managed through a Storage component. That's a network drive as a first-class recording target, in a camera at this price, and it appears nowhere in the marketing.

USB-C and Wi-Fi Are the Real Compromises

Two design choices tell you what this camera is for, and neither is a flaw so much as a boundary.

The first is power. USB-C at 5 VDC and 1 A means a socket nearby, or an adapter, or a run of cable that was never meant to carry power. Power over Ethernet, one cable doing both jobs, is the thing I keep coming back to on permanent installs, and it isn't on offer here. The second is Wi-Fi. Dual band is welcome and 5 GHz helps with the bitrate, but every camera on Wi-Fi is one router reboot away from a gap in your footage. If you're building a Wi-Fi heavy setup anyway, the trade-offs are laid out in our roundup of WiFi devices that behave well with Home Assistant.

There's no IP rating published either, which is telling given that Shelly rated a door sensor announced the same week at IP55. Read the camera as indoor until Shelly says otherwise. An AI outdoor model does appear in the company's own half-year investor update as something planned, with no name, no price and no specification attached, so treat it as a line in a slide rather than a product.

Photo by Jarrod Reed on Unsplash.

How It Stacks Up Against What Is Already on This House

The comparison that matters to me isn't Shelly against Ring. It's Shelly against the wired cameras already on the wall. Those cost two to three times as much, run on PoE, survive a router reboot without blinking, and record 4K to a machine indoors. The Shelly Camera does none of that.

The resolution deserves its own sentence, because every reviewer landed on it. 1080p in late 2026 is behind the market, and cheaper cameras from Wyze already ship 2K sensors. Shelly's answer is implicitly that the pixels aren't the product, the openness is. I think that's a defensible trade at this price, but it's a trade, and anyone hoping to read a licence plate at the end of a drive should stop reading here.

So why is it interesting at all? Because it lands the one property that decides everything else at a quarter of the price. It hands you a stream. A cheap camera that speaks RTSP is more useful in five years than an expensive one that speaks only to its vendor's app, and the second kind gets quietly discontinued while the first keeps feeding whatever recorder you happen to run.

Where it fits this build is obvious once you frame it that way. Not the driveway. A garage corner, a utility room, a spot where you want a stream and don't want to run Ethernet.

What Nobody Has Measured Yet

A specification sheet says what a device is, never how it behaves at 3 am with a moth on the lens. These numbers don't exist publicly yet, and any of them would make a better article than this one:

• Actual RTSP latency into Home Assistant, and whether the low-bandwidth stream holds up on a wall tablet
• Bitrate of each stream, which decides how many days a 512 GB card really covers
• Night vision usable range, since the documentation gives none
• Power draw at the wall over 24 hours, for a device that never sleeps
• Whether motion events reach Home Assistant locally, or only through the cloud

Would This Get Wired Into the Build?

My assessment is of the information, not the hardware, because I haven't held the hardware. The information is unusually good for a launch. Shelly publishes real specs in a knowledge base instead of a marketing page, the API documentation for Gen3 devices is public at shelly-api-docs.shelly.cloud, and Home Assistant's own documentation already describes the integration path in enough detail to include a default that will confuse people. That combination is rarer than it should be.

The gaps are equally clear. No ONVIF, no IP rating, no independent measurements of latency or night performance, no named firmware version anywhere, and a storage story that reads better in a headline than in a break-in. There isn't even a community complaint to weigh yet, because the thing is days old and the US listing still says coming soon. Before ordering, check three things yourself: current stock and firmware notes on the product page, that your Home Assistant install is on 2026.9 or later, and whether motion reaches your automations as a local event rather than a cloud push. That's what the documentation supports as of early September 2026, and when someone publishes real measurements, this page gets updated rather than replaced.