Giraffe CCTV
  • What is Giraffe?
  • Architecture
  • Giraffe Cloud
    • Getting started
      • Logging in
      • First steps
      • Giraffe terminology
      • Managing your account
    • View and control
      • Live talkdown
      • PTZ presets
      • Quick sounds
      • Custom views
      • Strobes
      • Floodlights
    • Alarm handling
    • Recording
      • Recording configuration
      • Recording playback
      • Exporting footage
    • Schedules
    • Active threat deterrence
      • Arming and disarming
      • Alarm states and configuration
    • System monitoring
      • Overview
      • Graphs
      • Events
      • Error states
    • Notification system
      • Person / vehicle alerts
      • Rate limits
    • Camera setup
      • Artificial intelligence
      • Masking
      • Camera configuration
      • Camera guides
        • Pelco
        • Hanwha
        • Axis
        • Dahua
        • Hikvision
        • Milesight
    • Router integration
      • Peplink
      • Teltonika
      • Advanced
    • Team management
      • Team hierarchy
      • Inviting users
      • Permissions
    • ARC integration
      • Sentinel Native
      • Generic Integration
      • Immix
      • Sentinel - Deprecated
    • Reseller teams
      • Team management
    • Troubleshooting
      • MTU Configuration
    • Advanced
      • Firewall whitelisting
      • White label
    • API
      • RTSP Service
      • HTTP API
  • Mobile App
    • Installing
    • Signing in
    • Live view
    • Recording
    • Updating
    • Privacy policy
  • Edge Controller
    • Edge Controller versions
    • Hardware overview
      • Edge Controller V2
      • Edge Controller V1
        • Status lights
    • Configuration
      • Device definitions
      • Camera power
    • Battery Calibration
    • Mobile routers
      • Router guides
        • Teltonika
          • Unblocking WebUI access
        • Peplink
    • Victron integration
    • SMTP Alarm Receiver
    • PIR sensors
      • Luminite Genesis PIR integration
      • Wired PIR sensors
    • Power consumption
    • Boot / shutdown procedure
    • GPS
    • EFOY integration
    • Advanced
      • Internal queue system
      • Self healing
      • Recording storage
  • Hub Controller
    • Overview
    • Installation
    • Troubleshooting
  • Mobile Security Unit
    • Overview
    • MSU Generations
    • Battery
  • Network Node
    • Overview
  • Mini Tower
    • Overview
    • Transporting the tower
    • Deployment steps
    • On site setup checklist
    • Pack away steps
    • Battery management
    • Solar performance
    • Maintenance
    • Branding
    • Troubleshooting
    • Safety
  • Battery Box
    • Overview
  • Giraffe Battteries
    • Charging
    • Safety
  • Solar Frame
    • Page 1
  • Terms and conditions
Powered by GitBook
On this page
  1. Giraffe Cloud
  2. System monitoring

Error states

PreviousEventsNextNotification system

Last updated 4 months ago

The error states history page can be accessed from the tab on a system settings page:

Error states will be generated for many events such as

  • system online / offline

  • cameras online / offline

  • doors opened

  • queues too large

  • hard drive error

  • AI processor error

  • mains power connected / disconnected

  • aux power connected / disconnected

  • battery shunt error

  • solar charger error

  • temperature thresholds exceeded

  • internet speed threshold exceeded

  • router signal threshold exceeded

  • cpu load exceeded

Manually closing error states

Error states can be manually closed using the 'Close' button. However, be aware that this is only useful if the error state has got 'stuck' and hasn't automatically closed itself.

Examples of when this might happen are if the system's definition was changed, and the door sensors were removed. If the system last reported that the doors were open, there will never be a close event and you would need to manualyl close it.

If you try and close an error state that is still active, a new error state will be generated a couple of minutes later for the same error. Therefore it is necessary to fix the cause of the error to make it go away.