Why it can be hard to tell at a glance

Three things make UNSAFE signals tricky to diagnose without the debug log:

  • Summary data: the user data file shows averaged or final readings, not every individual sensor measurement.
  • Safe-condition delay: CloudWatcher waits a configurable time before switching back to SAFE after an unsafe event, to avoid flapping.
  • Cloud alarm delay: to prevent false alarms from a single passing cloud, the software can be configured to wait before declaring UNSAFE on cloud readings.

The result is that by the time you see SAFE again, the data log no longer shows exactly what triggered the UNSAFE state. The debug log solves this.

Using the debug log in Windows software (v8.1.0 and later)

The CloudWatcher Windows software includes a dedicated debug recording mode that logs detailed information about every sensor reading, every unsafe detection, every safe delay, every cloud alarm delay: the complete sequence of events.

  1. Open the CloudWatcher software and go to Settings.
  2. Find the Debug / Record section and select a writable folder for the log file.
  3. Click Start to begin recording.
  4. Wait for the next UNSAFE event to occur, then stop recording.
  5. The software only saves the debug file after a short delay—if you want to inspect it right away, click Stop then Start again in the record section to force an immediate save.
  6. Open the log file: the entries are interleaved with standard readings and show the exact conditions at the moment each decision was made.

The debug file contains information about every unsafe detection, safe delay, activation, and delayed cloud detection: everything you need to trace exactly what happened and when.

CloudWatcher software debug recording settings
Debug recording—select a folder and click Start to begin logging sensor events

SOLO users: access the debug log directly

If you're using a SOLO CloudWatcher, the debug log is accessible via the device's built-in web interface without any software configuration:

http://aagsolo/cgi-bin/cgiGetDataFile?/tmp/debug.log

Replace aagsolo with your device's hostname or IP address if you've changed it. Open this URL in any browser on the same network as the SOLO.

CloudWatcher user data debug log output
Sample debug log output—each line shows the sensor event, delay state and reason for UNSAFE

Common causes of unexpected UNSAFE signals

  • Passing cloud—a single cloud moving across the sensor can trigger the cloud alarm, even if conditions are generally clear. Adjust the cloud alarm delay to suit your local sky.
  • Rain sensor sensitivity—light dew or moisture from condensation can trigger the rain sensor. Adjust the sensitivity threshold if this is a recurring issue.
  • Wind gusts—if your wind speed threshold is set low, brief gusts will trigger UNSAFE repeatedly.
  • Sensor temperature drift—after sunrise or at dusk, rapid temperature changes can affect cloud temperature differential readings temporarily.
  • USB/serial disconnect—if the CloudWatcher loses communication with the PC, the "UNKNOWN generates UNSAFE" setting will trigger UNSAFE. Check USB connections and drivers.