hero_radiora3_tab

RadioRA 3

Looking for help? We've got you covered
RadioRA 3 Solución de problemas Lutron Connect Portal - System...

Explore Knowledge Articles

Back

Lutron Connect Portal - System Monitor Tool

Lutron System Monitor Logo

 

System Monitor Tool

The System Monitor tool within the Lutron Connect Portal, is a key benefit of a connected system! With remote services enabled on a project, those with access to the Place will have the ability to monitor system performance through the System Monitor tool.

 

For more information on the Lutron Connect Portal, please see our Lutron Connect Portal Overview

Training

  1. ​System Monitor Training
    • This is hosted on our LCI page; you will need to have a myLutron account to access it.

 

How to access System Monitor?

System Monitor is accessed via the Place within the Lutron Connect Portal. When you select a Place, you will be greeted with the System Monitor screen, showing any Processors in the project, their MAC, Serial Number, Firmware, and Status.

System Monitor within the Connect Places screen. 

What are some of the features in System Monitor?

  1. View System time, location, date, MAC addresses, and networking related information
  2. Viewing Activity Logs
  3. Creating a Support File
  4. Device status table
  5. Remotely Rebooting processors for Ra3/QSX
  6. Starting Debug Logging for integration troubleshooting
  7. Check connection history​

 

​​

View System time, location, date, MAC addresses, and networking related information (Click to Expand)

  1. Select a Place and select a processor
    A list of Processors after selecting a Place 

  2. Processor Details will be displayed.
    The Processor Details Screen  

 

Viewing Activity Logs (Click to Expand)

  1. ​From the Processor Details page, select Activity Logs
    The Activity Logs Button in the Processor Details Screen 

  2. Select View for an existing log, or select Create Activity Log File
    The Activity Log Files menu 

    • Note: The window will display Processor Support Files at the top; this is currently a bug that will be fixed.

  3. View Activity Log in app or Download Table Data

  4. For more details on how to read the Activity Log, please see our System Activity Viewer section of our Troubleshooting within Lutron Designer article

 

​Creating a Support File (Click to Expand)

Note: Support files created this way will not include the Project file for reference.

  1. ​From the Processor Details page, select Support File
    The Support File Window 
  2. Select Create Engineering Support File
    A support File code 
  3. Copy the code and send it into Lutron Support with more details on what we're looking for, including timestamps or loads affected.

 

​

​Device Status Table​ (Click to Expand)
  1. On the Processor Details screen, scroll down to see the Processor's Links
  2. This will show each device connected to the processor's link, what it's device status, battery, and serial number is.
  3. For wired links on QSX/Athena, you will also see any reported Link Noise, Overrun Errors, and Framing Errors. 
    • For more details on what this means, hover your mouse over each for a brief description.
      Checking Link Health within the Device Status section 
  4. For Type-X devices you can also view their Firmware Revision
    • Note: You may need to refresh their status or select Refresh Table to fill this in.

 

Remotely rebooting Processors for Ra3/QSX (Click to Expand)

 

Starting Debug Logging for integration troubleshooting (Click to Expand)
  1. In the Processor Details screen, select Configure Debug Logging

  2. Now select whether you want to enable, or disable, Debug Logging
  3. Debug Logging will allow the Processor to log more information than normal, such as network traffic and integration commands received/sent.

​

Check Connection History (Click to Expand)
  1. Within the Processor Details screen, select Connection History
  2. This will display the processor's connection history to our servers.
    • Note: Seeing disconnects for extremely short amounts of time is normal (Such as the ones pictured above) as the processor checks in for potential firmware upgrades automatically.

​