Skip to main content
Remote debugging lets you inspect application properties in real time from BRICKS Controller without needing local network access to the device. This is useful for devices deployed in the field, at client sites, or in locations you cannot physically access.

​
Start a remote debug session

1

Open the device in BRICKS Controller

Go to BRICKS Controller and click on the device you want to debug.
2

Start remote debug

Click Remote Debug on the device detail page. The controller connects to the device and retrieves the list of available properties.
3

Select properties to monitor

Choose which properties you want to inspect. Only selected properties are streamed to reduce data volume.
The device must be online and connected to the BRICKS server for remote debugging to work. This feature may not be available on all workspace plans.

​
What you can inspect

The remote debug session displays real-time property values from the running application:
  • Data node values — Current state of data nodes
  • Generator properties — Configuration and outlet values
  • Brick properties — UI component settings and bindings

​
Filtering

Use the filter options to narrow down the property list:
  • Search by name — Filter properties by keyword
  • Hide auto-generated — Show only user-defined properties
  • Hide commands — Filter out command-type nodes
You can copy property values to the clipboard for further analysis.

​
Remote debugging vs local debugging

For full DOM inspection, JavaScript debugging, and performance profiling, use local debugging on the same network. Use remote debugging when you need to check property values on devices you cannot access locally.

​
Next steps

Local debugging

Connect Chrome DevTools directly for full debugging capabilities.

Activity log monitoring

Monitor device events and application behavior over time.