Field notes
Guides, comparisons and field notes from the engineers who plan, install and support these systems.
Use indoor cameras only for purposes agreed by the household, frame them away from private spaces, and provide a visible, dependable way to stop recording. Limit live viewing and stored footage to the people who need access, and explain the routine to residents and guests.
DNS failure can stop a camera app from finding the external service used for remote viewing, while the cameras continue sending video to a recorder or storage device over the local network. The two functions share equipment but do not depend on the same network path.
Plan what each alarm, fault and state change should make people and equipment do. Only then should you program the inputs, outputs, delays, notifications and reset behaviour that deliver those responses.
Position the light near the camera’s viewing direction but outside its frame. Aim it evenly across the subject area, with a slight side offset where practical. Avoid backlighting, direct glare, bright reflections and nearby surfaces that bounce infrared into the lens.
Build a practical security risk register by walking the property, pairing each threat with a specific vulnerability, rating likelihood and impact separately, and assigning suitable controls, owners and review points. Record the remaining risk after improvements so the document reflects the property as it actually operates.
A security camera image usually turns pink or purple because infrared light is reaching the image sensor during colour mode. The usual cause is an infrared cut filter that is stuck, interrupted during movement or controlled incorrectly. Settings and unstable power can produce similar symptoms, so test daylight, darkness, live view and recordings before deciding that the camera needs service.
VMS servers separate system and video drives because the operating system and camera archive create different workloads. Physical separation reduces competition for disk access, makes faults easier to identify, and allows either storage role to be repaired, replaced or expanded without treating the whole server as one inseparable unit.
Remote account security cannot fully protect a video system when someone can reach the recorder, local controls, storage, cables or power supply. Secure placement, restricted local accounts, protected connections and clear access responsibility are separate requirements.
If remote viewing works on mobile data but not Wi-Fi, the likely fault is in the local network path. Guest network separation, device isolation, filtering, DNS failure or incorrect local addressing can block viewing even though the security camera and video feed remain available externally.
Use a dedicated zone for each detector when clear identification and easy fault diagnosis matter. Share a zone only when reporting the group is sufficient and the wiring, supervision and future servicing have been deliberately planned.
Mount the camera on a fixed surface outside the full travel path of every door, gate and shutter, then test the view throughout each complete movement cycle.
Give each visitor a separate credential limited to the required route, area and purpose. Coordinate the lock, alarm and entrance view as one process, then remove the permission as soon as the task or recurring arrangement ends.
Answer a few questions and get a scoped quote — or talk to an engineer today.