Control4: Log Storage Space: Warning
Diagnostics indicates the following
Log Storage Space: Warning
Storage space for Logs is low. This may cause problems with device operation
This indicates that there isn't much space available on the unit for logging. This can be ignored unless you are having issues
Cause
This may happen in normal operation without fault. It can be caused by using older controllers with less logging space, or drivers which do not cycle logs properly
Solution
This may happen in normal operation without fault, and should only be considered if Control4 is misbehaving. Ensure all drivers are up to date or contact Control4 for advice.
Related Articles
Control4: Driver Storage Space: Warning
Diagnostics indicates the following Driver Storage Space: Warning Storage space for Drivers is low. This may cause problems with device operation, or cause driver updates to fail Driver updates may fail when attempted, or, future updates may fail. ...
Control4: Memory Usage: Warning
Diagnostics show the following Memory Usage: Warning Driver Memory Consumption is higher than expected. This may be normal on some drivers. Cause This is for internal troubleshooting only and indicates that the driver may be using more memory than ...
Control4: Driver Anomalies: Warning
Driver Diagnostics shows Driver Anomalies: Warning Driver Anomaly Detected. If undesired behavior is experienced, please Submit Diagnostics (located in the Actions Tab) and reach out to Chowmain Support with the Diagnostics ID and description of the ...
Control4: Driver Versions Mismatch: Warning
Driver Diagnostics Shows Driver Versions Mismatch: Warning One or more driver installed in this package are using a different driver version.This may cause unexpected behaviour. It is recommended to update all drivers to the same version unless ...
Control4: Debugging Enabled: Warning
Diagnostics may show the following warning Debugging Enabled: Warning Driver Debugging is enabled. This may result in greatly increased CPU and memory usage whilst enabled Causes This is caused by the Debug Mode property being not set to off Solution ...