Control4 Driver Logs

Whilst cases may vary, below covers a few options for sending us logs from the Control4 Rithum Driver.

If there are issues with the server running in Control4:

• Select the primary Rithum driver (this will be the first one added, and can be identified as it has Server Configuration properties)
• Set the following property values
• Debug Mode = Print
• Debug Level = 5
• Debug Subsystems = Rithum.Comms.Server
• Replicate the issue
• Copy the logs from the Lua Output

If there are issues with the client connection from Control4 to Rithum:

• Select the Rithum driver which is experiencing the issue
• Set the following property values
• Debug Mode = Print
• Debug Level = 5
• Debug Subsystems = Rithum.Comms.Client
• Replicate the issue
• Copy the logs from the Lua Output

If there is an issue and you’re not sure of the source:

• Select the Rithum driver which is experiencing the issue
• Set the following property values
• Debug Mode = Print
• Debug Level = 5
• Debug Subsystems = *
• Replicate the issue
• Copy the logs from the Lua Output