SYDNEY ALARMS / SUPPORT
Help with your existing system.
Prepare a useful fault report and find the next safe step for an existing alarm, camera, intercom or access system. Start with the failed function and the exact model, not an assumed cause. Do not send passwords or alarm codes.
CCTV systems: handover and user training
Play back a recorded event from each camera, then export a short clip and open it on another device. Check the timestamp and show each authorised user.
CCTV systems: maintenance and follow-up checks
Check recent playback, camera aim, lens cleanliness and the date on the recorder. Seasonal foliage, spider webs and changed lighting can impair useful.
CCTV systems: how to describe a fault
State whether the problem affects live viewing, saved footage or only the app. Note whether all cameras or one camera is affected. This helps distinguish.
CCTV systems: acceptance testing and sign-off
Record a person walking through each intended target area under realistic lighting. Check live view, playback and export. Confirm the agreed retention.
Home alarms: handover and user training
Practise arming, disarming and any agreed part-arm mode. Demonstrate what the keypad displays after a fault. Confirm how to add and remove a user without.
Home alarms: maintenance and follow-up checks
Use the authorised test mode and arrange monitoring test status first where applicable. Check detectors individually and record their zone names so a.
Home alarms: how to describe a fault
Record the keypad’s exact fault text or indicator and the affected zone. Mention recent outages and when the fault first appeared. Do not send the user.
Home alarms: acceptance testing and sign-off
Test each zone and the agreed siren or notification path under the installer’s procedure. Demonstrate entry and exit delays with normal use. If.
Video intercoms: handover and user training
Place a test call, speak in both directions and try the authorised release function. Confirm what happens when nobody answers and how an indoor user.
Video intercoms: maintenance and follow-up checks
Check call audio, the camera view, button response and each authorised release. Clean the lens and microphone openings only as the manufacturer directs..
Video intercoms: how to describe a fault
Say whether calls fail to ring, audio is one-way, video is missing or the release fails. Mention whether the problem affects an indoor monitor, a phone.
Video intercoms: acceptance testing and sign-off
Make calls from each entry to each intended answering point. Check intelligible audio, face visibility and the agreed release function. Confirm that the.
Access control: handover and user training
Practise creating a user, assigning a schedule and revoking a lost credential. Walk each door with the installer and confirm the authorised entry and.
Access control: maintenance and follow-up checks
Test the relevant door closer, latch, reader and release devices under the service procedure. A controller reporting granted access does not prove that a.
Access control: how to describe a fault
Report the specific door, credential type, time and whether the reader indicated acceptance. Distinguish a rejected credential from an accepted.
Access control: acceptance testing and sign-off
Try an authorised user, a revoked credential and a user outside the allowed schedule. Verify the relevant exit devices and agreed door status reporting.
Alarm monitoring: handover and user training
Confirm the account details, event descriptions and contact order with the provider. Ask how to put the account on test and who is authorised to request.
Alarm monitoring: maintenance and follow-up checks
Review contacts and response instructions periodically. Arrange authorised signal tests with the provider and keep the outcome. A changed phone number.
Alarm monitoring: how to describe a fault
Record the time of the expected signal and the panel message. Ask the provider whether the event was received. Do not repeatedly trigger the alarm.
Alarm monitoring: acceptance testing and sign-off
Coordinate with the provider, send the agreed event types and verify the account and zone descriptions received. Confirm that test mode is ended and the.
Security repairs: handover and user training
Have the technician demonstrate the previously failing function and explain any remaining limitations. Keep the service report, changed-part details and.
Security repairs: maintenance and follow-up checks
Use the repaired function during an agreed follow-up check and record any recurrence. Ask which routine maintenance would help prevent a repeat and which.
Security repairs: how to describe a fault
Report the exact visible message rather than only saying the alarm is broken. Include times, affected devices and whether a restart or power event.
Security repairs: acceptance testing and sign-off
Repeat the task that previously failed and check any associated alerts or playback. Keep the repair result and any outstanding tests in the service.
Wireless alarms: handover and user training
Demonstrate low-battery and lost-device indications using the manufacturer’s procedure. Label device positions and explain how an authorised user.
Wireless alarms: maintenance and follow-up checks
Review device supervision and battery warnings under the manufacturer’s instructions. Record the replacement date and approved battery type. Do not mix.
Wireless alarms: how to describe a fault
Identify the device location, fault type and when it appears. Mention new metal furniture, building work or a changed panel position that might have.
Wireless alarms: acceptance testing and sign-off
Use the authorised walk-test procedure for each enrolled sensor. Check fault reporting and any agreed remote alert route. Record device names so later.
Business security: handover and user training
Train the people who open and close the premises. Demonstrate user removal, incident playback and fault reporting. Keep administrator ownership with the.
Business security: maintenance and follow-up checks
Assign a named person to review recording, alerts and access changes. Keep the task in an operating procedure so maintenance does not disappear when.
Business security: how to describe a fault
Record the affected area, device and business impact. Tell the service team whether the site is trading, whether security coverage is reduced and when.
Business security: acceptance testing and sign-off
Test the agreed opening, closing and after-hours scenarios. Verify event recording and the relevant notification path, then record who has accepted.
Strata security: handover and user training
Provide the building’s authorised manager with equipment records and administration instructions. Explain resident access changes and the process for.
Strata security: maintenance and follow-up checks
Keep a common equipment service log and a current list of authorised administrators. Test shared entry functions under an agreed process and arrange.
Strata security: how to describe a fault
Identify the entrance, unit or answering point affected and whether other residents have the same issue. Report a failed lock release separately from an.
Strata security: acceptance testing and sign-off
Test each agreed entrance and a representative set of unit and remote answering points as scoped. Check resident credential changes and document any.
Remote security access: handover and user training
Test on home Wi-Fi and mobile data, including a notification with the phone locked. Demonstrate adding or removing a shared user and document the.
Remote security access: maintenance and follow-up checks
Review logged-in users, phone notification settings and supported software updates. Test that an intended alert arrives after a phone replacement or a.
Remote security access: how to describe a fault
State whether the app fails on Wi-Fi, mobile data or both. Mention any router or phone change. Distinguish login rejection from a device marked offline.
Remote security access: acceptance testing and sign-off
Test the agreed functions on every intended user role using Wi-Fi and mobile data. Confirm notifications, permissions and recovery ownership rather than.
Security maintenance: handover and user training
Review the test results, fault list and next actions with the technician. Keep the date, affected equipment and responsibility for each outstanding item.
Security maintenance: maintenance and follow-up checks
Use a dated checklist covering detection, alerts, playback, clock settings and account access as relevant. Follow model-specific instructions and assign.
Security maintenance: how to describe a fault
Record a failed maintenance check with the exact device, symptom and date. Keep previous results so the technician can identify whether a fault is new,.
Security maintenance: acceptance testing and sign-off
Test the complete relevant path: detection, signal, action or recording, and review. Record failures specifically and retest affected functions after.
Security upgrades: handover and user training
Demonstrate the new functions as well as the retained ones. Confirm old app access has been handled, configuration records are updated and all authorised.
Security upgrades: maintenance and follow-up checks
Update maintenance instructions for the installed models and remove obsolete checks. Record the new firmware, consumables and test process instead of.
Security upgrades: how to describe a fault
State whether the fault began immediately after migration or affects a retained device. Keep the change list so the technician can distinguish a new.
Security upgrades: acceptance testing and sign-off
Test every agreed new function and the retained functions affected by the migration. Confirm recording or signal continuity, user permissions and the.
Separate the functions before reporting a fault
For CCTV, distinguish live viewing, stored footage, export and remote access. For alarms, distinguish a detector event, a local warning and a reporting failure. For intercom/access, distinguish calling, audio/video, permission and physical door release. Say which other functions still work.
Keep the evidence useful
Record the exact message, affected location, first occurrence and any recent power, internet, building or account change. A safe photo of a display or model label can help. Do not repeatedly clear a fault if doing so removes information needed for diagnosis; follow the relevant instructions.
Arrange the appropriate service
Tell us who can authorise the visit and parts, when equipment is accessible and whether essential coverage is reduced. If a monitoring service is involved, arrange authorised test procedures before any work that can trigger a response.
Questions and answers
Can you diagnose a system from an offline app message alone?
That message is a starting point, not a complete diagnosis. Record whether local equipment still operates and whether the problem differs between Wi-Fi and mobile data.
What should be checked after repair?
Repeat the originally failing task, including its relevant recording, release or notification path. Keep the diagnosis, changed parts and any follow-up instructions.
TAKE THE NEXT STEP