What it can do — Hanwha SUNAPI CCTV
Feature by feature, as assessed on 2026-07-15. Read the limitation column before you
promise a customer something the hardware cannot do.
Connection, health and audit
| Feature |
Supported |
Limitation |
| Connection & session |
Yes |
— |
| Liveness / keepalive |
Yes |
— |
| Time synchronization |
Partially |
The device clock is read and compared on a schedule, and a device that manages its own clock over NTP is correctly left alone. What has never been exercised on hardware is the correction itself: no verified device was on manual time, so a drifting clock may fail to be corrected and camera timestamps could stay wrong. |
| Offline audit recovery |
No — the hardware cannot do it |
Events that happen while the adapter is disconnected from the device are lost for good. The device keeps no replayable buffer for the live event stream, so after a network outage or an adapter restart there is a hole in the audit trail for exactly that period, with nothing to indicate what was missed. |
| Health & supervision |
Partially |
Connectivity and storage faults are reported, but the recorder's own fault codes for a failing disk have never been seen on hardware — only the healthy and absent-disk cases have. A genuine disk failure may therefore be reported less precisely than the device could describe it. |
| Configuration discovery |
Yes |
— |
| Configuration & reset audit |
Yes |
— |
Access control
| Feature |
Supported |
Limitation |
| Credential management |
Yes |
— |
| Sync mode |
Yes |
— |
| Double-sync safety |
Yes |
— |
| Reset & restore |
Yes |
— |
| Schedules / time profiles |
No — the hardware cannot do it |
A licence plate sent to the camera is granted around the clock — the time profile on the policy that granted it is not enforced at the barrier, and PQ records the camera's decision as a grant even at an hour its own rules would have denied. |
| Access events |
Yes |
— |
| Enrollment |
No — the hardware cannot do it |
A vehicle cannot be enrolled by driving it past the camera — an unknown plate is recorded as an observation, and someone has to type it into PQ before it will open anything. |
| Door control |
No — the hardware cannot do it |
An operator cannot open the barrier from PQ. The camera opens it on its own when it recognises a plate; PQ can change which plates are recognised, but it has no remote-release button. |
| Card formats |
No — the hardware cannot do it |
Cards do not apply to this device. It reads licence plates only, so no card format, facility code or bit length can be configured for it. |
| Access levels / groups |
No — the hardware cannot do it |
The camera holds one undifferentiated list of plates. Access groups and levels are decided in PQ before upload; the device itself cannot tell one group of vehicles from another. |
| Holidays |
No — the hardware cannot do it |
Public holidays cannot be sent to the camera, so a holiday is treated exactly like any other day for vehicles. |
| Antipassback |
No — the hardware cannot do it |
There is nothing to stop the same plate being used to enter twice without leaving in between — the camera does not track which vehicles are currently inside. |
| Reader mode / enable |
No — the hardware cannot do it |
The plate reader cannot be switched off or put into a different mode from PQ. Taking it out of service means emptying its plate list or changing the camera's own settings by hand. |
Video
| Feature |
Supported |
Limitation |
| Channel discovery |
Yes |
— |
| Live / playback / snapshot |
Yes |
— |
| PTZ / presets |
Yes |
— |
| Analytics |
Partially |
Analytics events are carried through with their object class, but the full set of classes a device can report has not been confirmed on hardware. A class this adapter has not seen arrives as a generic detection rather than a named one, so it stays visible and auditable but is less searchable. |
| Faults & teardown |
Yes |
— |
| Feature |
Supported |
Limitation |
| Inputs |
Partially |
A wired alarm input is reported when it activates, but it is not modelled as its own device in the tree. So an input cannot be named, given a location, or used on its own in rules and floorplans — it appears only as a fault on the parent device. |
| Outputs |
Partially |
A relay can be switched on and off, but not pulsed for a set duration — a door-strike-style timed release has to be driven by two separate commands from PQ. No verified device has an alarm relay, so the switching itself has not been seen on hardware. |
| Output schedules |
No — PQ cannot do it yet |
Recorders can be told to switch a relay on a weekly schedule, but PQ cannot configure that. Any scheduled relay behaviour has to be set up in the recorder's own web interface, where PQ can neither see nor audit it. |
vendor
| Feature |
Supported |
Limitation |
| Analytics arm/disarm |
Yes |
— |