Start a remote debug session
Open the device in BRICKS Controller
Go to BRICKS Controller and click on the device you want to debug.
Start remote debug
Click Remote Debug on the device detail page. The controller connects to the device and retrieves the list of available properties.
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
Remote debugging vs local debugging
| Feature | Local debugging | Remote debugging |
|---|---|---|
| Network | Same local network required | Works over the internet |
| What you inspect | Full DOM, JavaScript, network, performance | Application property values |
| Setup | Enable DevTools on device, connect via Chrome | Click Remote Debug in BRICKS Controller |
| Best for | Development and deep debugging | Monitoring field-deployed devices |
Next steps
Local debugging
Connect Chrome DevTools directly for full debugging capabilities.
Activity log monitoring
Monitor device events and application behavior over time.