LogoLogo
OverviewDemos and ResourcesContact
  • What is Engine?
  • Key Concepts
    • Drivers
    • Modules
    • Systems
    • Zones
    • Settings
    • Interfaces
    • Triggers
  • Security
  • Deployment
    • System Architecture
    • Single Sign-On
      • Configuring Engine for SAML2
      • SAML2 with Azure AD
      • SAML2 with ADFS
      • SAML2 with Auth0
      • SAML2 with GSuite
      • OAuth2
  • Integrations
    • Supported Integrations
    • Directory Services
      • Microsoft Office365
    • IoT
      • Device Drivers
      • Node-RED
      • Azure IOT Hub
    • Location Services
      • Locating Users on a Network
      • SVG Map Creation
      • Cisco CMX
      • Cisco Meraki RTLS
      • Desk Sensors
  • Administration
    • Backoffice
      • Systems
      • Devices
      • Drivers
      • Zones
      • Triggers
      • Metrics
      • Users
      • Domains
        • Applications
  • Developer Guide
    • Development Environment
    • Building Drivers
      • Discovery and Metadata
      • State
      • Scheduling Actions
      • Response Tokenisation
      • Device Drivers
      • SSH Drivers
      • Service Drivers
      • Logic Drivers
      • Testing
      • Live Monitoring
      • Logging
      • Security
      • Utilities and Helpers
    • User Interfaces
      • Composer
      • Virtual Systems
      • Widgets
      • Settings.json
  • API
    • Authentication
    • Control
      • Systems
      • Modules
      • Dependencies
      • Zones
      • Websocket
        • Commands
          • bind
          • unbind
          • exec
          • debug
          • ignore
        • Heartbeat
        • Errors
  • Support
    • Service Desk
Powered by GitBook
On this page
  • Viewing Debug Messages
  • Sending Manual Commands

Was this helpful?

  1. Developer Guide
  2. Building Drivers

Live Monitoring

PreviousTestingNextLogging

Last updated 5 years ago

Was this helpful?

Engine features live, in-browser debugging of operational systems via backoffice. All debug messages are outputted to the browser console (F12 or Ctrl+Shift+I, then Console tab).

Ensure that the Console logging is set to enable Verbose messages, as highlighted below:

Viewing Debug Messages

Debugging is done from the Systems section. Select the system to debug and then click the Device tab.

The checkbox (6) on the the left of the Class type enables live debugging output for this Device to the browser console. Pressing the Eye symbol (7) next to the device name will instantly output the device’s current status information to the console to assist in troubleshooting scenarios.

Sending Manual Commands

The About tab of the System page contains a drop down list (9) that allows the selection of a device to send a manual control command to.

The device’s response to these commands will be output to the bottom of right of the window and (if enabled - above) to the browser console.

Some commands will require parameters. When blank, the text field will describe the type of parameter required by the function.

In the event that Engine is not able to send a command to the device, an error message (red instead of blue) will appear at the bottom of the screen with the details.