Security cameras are one of the most commonly installed smart home devices in Polish apartments and houses. The range of products available — from simple Wi-Fi cameras with proprietary cloud apps to ONVIF-compliant network cameras integrating into enterprise NVR systems — reflects very different use cases, price points, and data storage models.
This article focuses on how cameras connect to other smart home components and what determines interoperability.
Types of IP cameras
Modern security cameras used in residential installations are network devices that transmit video as a digital stream over a local network (LAN) or the internet. Key hardware categories:
- Indoor fixed cameras — ceiling or wall mounted, typically 2–5 MP resolution, used for monitoring entry points and living areas
- Outdoor cameras — weatherproof (IP65 or higher), often with IR night vision, PoE or Wi-Fi power
- PTZ cameras — pan-tilt-zoom, motorised pointing; less common in residential use due to cost
- Doorbell cameras — integrated into intercom systems or replacing doorbell buttons; common in Polish apartment buildings with videophone systems (wideofon)
Communication protocols
ONVIF
ONVIF (Open Network Video Interface Forum) is a standard for IP camera interoperability, developed by a consortium including Axis, Bosch, and Sony. An ONVIF-compliant camera exposes a standard API for discovery, video streaming, PTZ control, event notification, and configuration. NVRs and VMS (video management software) that support ONVIF can connect to ONVIF cameras regardless of manufacturer.
The ONVIF standard is published at onvif.org. Profiles define feature sets:
- Profile S — Basic streaming, PTZ, and event handling
- Profile G — On-board recording and playback
- Profile T — H.264/H.265 streaming, metadata for analytics
In practice, ONVIF compliance varies. Budget cameras from Chinese manufacturers may be nominally ONVIF-compliant but implement only a subset of the standard. Testing a camera with the ONVIF Device Manager (free Windows application) before purchasing in bulk is a common practice among Polish system integrators.
RTSP
RTSP (Real-Time Streaming Protocol) is a network control protocol for streaming media. Virtually all IP cameras expose an RTSP URL that provides the raw H.264 or H.265 video stream. RTSP does not provide camera configuration or event notification — it is stream-only.
RTSP URLs typically follow the format:
Home Assistant's Generic Camera integration uses RTSP URLs, making any RTSP-capable camera accessible within a Home Assistant dashboard without requiring ONVIF support. Frigate NVR, an open-source NVR designed for Home Assistant integration, also uses RTSP streams as its input source.
Proprietary protocols and cloud apps
Many consumer cameras — including widely distributed Polish-market products from TP-Link Tapo, Reolink, Ezviz (Hikvision consumer brand), and Xiaomi — use proprietary protocols between the camera and the manufacturer's cloud. Local access may still be available via ONVIF or RTSP, but feature parity with the manufacturer app (push notifications, AI detection alerts, remote playback) often requires cloud connectivity.
Cameras that route video through manufacturer cloud servers in China or the United States raise GDPR considerations when recording footage of areas accessible to others (stairwells, shared outdoor spaces). Under GDPR Article 6, a legal basis for processing is required. Recording only private areas of an owned property is generally permissible; recording shared or public areas requires documented justification.
Hub integration
Smart home hubs integrate security cameras in several ways:
| Integration method | What it enables | Limitations |
|---|---|---|
| ONVIF integration | Camera discovery, stream display, motion event triggers | Feature set depends on camera's ONVIF profile; recording handled separately |
| RTSP stream in dashboard | Live view in hub UI | No event triggers from camera; hub does not process video |
| Manufacturer API integration | Full feature access if supported (Reolink, Hikvision integrations for Home Assistant) | Dependent on API availability and maintenance by integration developer |
| Frigate NVR + MQTT | Local AI object detection (person, vehicle, animal); events published to Home Assistant via MQTT | Requires dedicated hardware for inference (Coral USB accelerator for best performance) |
Recording and storage
Video storage options for residential installations:
- MicroSD card in camera — simplest; capacity limited to 256 GB or less; no redundancy
- NVR with HDD — dedicated network video recorder; Hikvision, Dahua, and Reolink NVRs are available in Poland. Supports scheduled and event-triggered recording across multiple cameras
- NAS with NVR software — Synology Surveillance Station and QNAP Surveillance Center run on NAS devices, supporting ONVIF cameras; cost-effective if a NAS is already in use for file storage
- Manufacturer cloud — subscription-based; recording stored on manufacturer servers; simplest for non-technical users
- Self-hosted Frigate NVR — open-source, runs on a Raspberry Pi or low-power PC, stores recordings locally; requires technical setup
Automation triggers from cameras
When cameras integrate with a smart home hub, motion events or AI detection results can trigger automations. Examples relevant to a Polish home:
- Outdoor camera detects person at gate at night → turn on driveway lights (Z-Wave or Zigbee fixture)
- Doorbell camera pressed → announce on smart speakers throughout house
- Camera detects motion while thermostat schedule shows "away" → send notification (unexpected presence)
- No motion detected in any room for over 2 hours during scheduled home time → reduce heating setpoint (possible occupancy state error in schedule)
Network considerations
Each camera generates continuous video data. At 1080p/H.264, a typical camera uses 500 kbps–2 Mbps depending on scene complexity and compression settings. Ten cameras at 1 Mbps average would consume 10 Mbps of LAN bandwidth and generate approximately 108 GB of data per day if recording continuously.
Polish internet connections typically have asymmetric speeds (high download, lower upload). Remote viewing of camera streams from outside the home uses upload bandwidth. CGNAT (carrier-grade NAT) — common among Polish mobile and some cable operators — prevents direct inbound connections to a home network; solutions include VPN, reverse proxy with a VPS, or relying on manufacturer cloud relay.
Legal notes for Poland
Recording video in Poland is subject to GDPR and Polish implementing legislation. Key points for residential camera installations:
- Recording entirely within a private residence (interior rooms) for personal security purposes generally falls within the GDPR household exemption (Article 2(2)(c)).
- Recording areas visible to third parties (shared corridors, streets, neighbours' property) requires a legal basis and, in most cases, signage informing people they are being recorded.
- Recordings stored on cloud servers outside the EU/EEA are subject to the data transfer rules under GDPR Chapter V.
- The supervisory authority is the Urząd Ochrony Danych Osobowych (UODO).
This section contains general orientation only and is not legal advice. For installations in shared buildings or commercial properties, consult a legal professional familiar with Polish data protection law.
