Symptoms
One PV string registers no output at dawn but produces normally after sunlight increases. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: One PV string registers no output at dawn but produces normally after sunlight increases.
- Control test: Compare string measurements on a clear midday versus early morning without accessing rooftop hardware.
- A confirmed correction must meet this outcome: String begins producing when above specified operating thresholds.
A working state in another app or device is a useful control only when the account, source material and operating conditions are comparable. If they differ, that comparison may produce a misleading conclusion.
Why It Happens
Energy dashboards display interpreted measurements. Sign conventions, sensor mapping, billing intervals and actual electrical behavior can differ; compare independent evidence before concluding that a physical circuit is faulty.
The symptom alone cannot distinguish inverter minimum voltage from shade on one string. Evidence related to faulty string sensor changes the next action, so record the comparison before applying a fix.
Three competing explanations
- Inverter minimum voltage.
- Shade on one string.
- Faulty string sensor.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports inverter minimum voltage does not automatically exclude shade on one string; the comparison needs to separate them.
Before Making Changes
Do not open panels, meters or high-voltage enclosures. Electrical measurements beyond the user interface require a qualified professional. Never disconnect DC solar connectors under load.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare string measurements on a clear midday versus early morning without accessing rooftop hardware. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Inverter minimum voltage | If the failing state changes under the comparison, inverter minimum voltage is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Shade on one string | If the first change has no effect but a supported configuration differs, shade on one string moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Faulty string sensor | If both earlier paths are contradicted, investigate whether faulty string sensor accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Review documented voltage thresholds and shading history in app graphs. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Identify the exact failure
One PV string registers no output at dawn but produces normally after sunlight increases. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare string measurements on a clear midday versus early morning without accessing rooftop hardware. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Apply a targeted reversible correction
Review documented voltage thresholds and shading history in app graphs. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
String begins producing when above specified operating thresholds. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for inverter minimum voltage, shade on one string and faulty string sensor separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Inspect supported diagnostic records
Provide qualified installer with timestamped DC data for safe inspection. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Test the alternative explanation
Revisit the comparison: Compare string measurements on a clear midday versus early morning without accessing rooftop hardware. If the first suspected cause is not supported, compare the behavior predicted by shade on one string with the behavior predicted by faulty string sensor. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: String begins producing when above specified operating thresholds. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the equipment manufacturer, utility or a licensed electrician. Safety boundary: Never disconnect DC solar connectors under load.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming inverter minimum voltage is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare string measurements on a clear midday versus early morning without accessing rooftop hardware.
- Skipping this safety boundary: Never disconnect DC solar connectors under load.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: String begins producing when above specified operating thresholds. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare string measurements on a clear midday versus early morning without accessing rooftop hardware.
- Check the stated pass result: String begins producing when above specified operating thresholds.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Provide qualified installer with timestamped DC data for safe inspection. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the equipment manufacturer, utility or a licensed electrician, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether inverter minimum voltage, shade on one string and faulty string sensor were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: String begins producing when above specified operating thresholds. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: One PV string registers no output at dawn but produces normally after sunlight increases. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
FAQ
How can I tell whether inverter minimum voltage is responsible?
Run the controlled comparison: Compare string measurements on a clear midday versus early morning without accessing rooftop hardware. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is shade on one string rather than inverter minimum voltage?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Provide qualified installer with timestamped DC data for safe inspection. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: String begins producing when above specified operating thresholds. If it fails after the normal workflow is repeated, document whether faulty string sensor still explains the remaining behavior and escalate with non-sensitive observations.