Symptoms
Charging works in sunlight but repeatedly pauses at dusk under a solar-following rule.
The useful clue here is what still works: Charging works in sunlight but repeatedly pauses at dusk under a solar-following rule. That narrows the test to the point where the two paths diverge.
- The failing path: Charging works in sunlight but repeatedly pauses at dusk under a solar-following rule.
- Control test: Compare exported power logs and minimum current threshold during a daylight-to-evening transition.
- A successful outcome: A planned test charges or pauses according to the explicitly selected policy without rapid cycling.
Why It Happens
A connected vehicle, charger and cloud app may operate on different schedules or permissions. Use parked, supervised, low-risk checks.
There are three genuinely different layers worth checking; use the observation in the table to decide which one is implicated. None of these is proven merely by the symptoms.
- Solar-only mode active. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Current minimum unmet. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Export telemetry oscillates. This explanation predicts a different result in the comparison test or the more advanced inspection.
Before Making Changes
Do not alter breaker protection, meter wiring, or grid interconnection settings yourself.
Save the current configuration or capture screenshots of the exact option values; where a file or recording is involved, work on a disposable duplicate. If this is shared equipment, ask the owner or administrator before changing it. Prefer a safe test item over real customers, medical decisions, paid transactions or irreplaceable data.
Write down the device model, platform, observed time of failure, and which action still works. These details will distinguish an unsupported feature from a malfunction and will be useful if escalation is required.
Problem-Specific Diagnosis
Use the following route rather than guessing based on a product name. The expected differences are designed for this particular failure.
| Action or observation | Meaning of the result | Decision |
|---|---|---|
| Compare exported power logs and minimum current threshold during a daylight-to-evening transition. | Does the failure follow the affected file, profile, connection or location? | Keep this result as the baseline; do not alter two systems at once. |
| Select the supported minimum grid-assist or pause threshold matching the intended charging policy. | Does the low-impact correction restore the exact failure without altering the control case? | Re-test; reverse the change if the original symptom is unchanged. |
| Examine smart-meter telemetry delay, charger current floor and anti-flapping hysteresis. | Does this separate current minimum unmet from export telemetry oscillates? | Use documented diagnostic views rather than blind replacement. |
| A planned test charges or pauses according to the explicitly selected policy without rapid cycling. | Is the same original symptom gone after a normal repeat? | Record the pass condition and preserve the working settings. |
If the control case fails as well, the fault may be broader than this guide. Stop at that point and check the shared power, account, access or media path before applying the narrow fix.
Beginner and Advanced Paths
Start with the reversible Beginner path. The Advanced path examines a different layer when the first route fails; it is not a repetition of the same restart or setting.
Step-by-Step Troubleshooting
Choose the simple reversible checks first, then investigate the deeper system layer only if necessary.
Record the exact failure
Confirm the behavior without guessing: Charging works in sunlight but repeatedly pauses at dusk under a solar-following rule. Note the affected account, file, connection or physical control and record the current settings. Do not alter breaker protection, meter wiring, or grid interconnection settings yourself.
Run the passing comparison
Compare exported power logs and minimum current threshold during a daylight-to-evening transition. Keep the working and failing cases separate. If both fail, stop and investigate the common path instead of forcing a narrow repair.
Apply the least disruptive correction
Select the supported minimum grid-assist or pause threshold matching the intended charging policy. Change only this setting or route; do not reset unrelated profiles, storage or pairing records. Save the previous value so it can be restored.
Retest and keep the result
A planned test charges or pauses according to the explicitly selected policy without rapid cycling. Repeat after a normal reopening or reconnect. If the control case gets worse, undo the last change and write down the difference.
Separate the three underlying layers
Test the hypotheses independently: solar-only mode active; current minimum unmet; export telemetry oscillates. A green status indicator does not distinguish them. Use the recorded control case as evidence.
Inspect the deeper component
Examine smart-meter telemetry delay, charger current floor and anti-flapping hysteresis. Use only read-only diagnostics or documented configuration screens first. Capture logs and timestamps rather than removing the component or reinstalling software blindly.
Cross-check with an independent path
Where possible, repeat “Compare exported power logs and minimum current threshold during a daylight-to-evening transition.” using a second supported account, safe sample file, physical input, known-good cable or alternate compatible application. Change only one variable and note which outcome follows it.
Choose a reversible targeted escalation
If the deeper check isolates a fault, use a vendor-supported fix or authorized service for that layer; otherwise restore original values. Finish only when: A planned test charges or pauses according to the explicitly selected policy without rapid cycling. Do not alter breaker protection, meter wiring, or grid interconnection settings yourself.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Treating solar-only mode active as certain just because the behavior looks familiar.
- Changing several independent settings together, which makes the result impossible to interpret.
- Skipping the safety boundary: Do not alter breaker protection, meter wiring, or grid interconnection settings yourself.
- Calling the issue fixed after one status indicator changes but before repeating the original operation.
- Discarding the working configuration or the only original file before a replacement has been verified.
How to Verify the Fix
A planned test charges or pauses according to the explicitly selected policy without rapid cycling.
Use the same baseline case: Compare exported power logs and minimum current threshold during a daylight-to-evening transition. Then repeat the previously failing operation after a normal close-and-open, reconnect or next scheduled cycle, whichever matches the scenario. Confirm the part of the system that was already working is still unaffected.
Where a result can be measured, retain the test timestamp, file name, screenshot or device state. A temporary success that cannot be repeated is not yet a confirmed repair.
If the Problem Continues
Escalate from the surface symptom to the narrower mechanism: Examine smart-meter telemetry delay, charger current floor and anti-flapping hysteresis. If this identifies a hardware, account-policy or service limitation, use the manufacturer’s authorized support route rather than bypassing controls.
When opening a support case, supply the model, software/firmware version actually installed, the failing operation, the successful comparison, the three possible explanations checked, and the final observed result. Redact account identifiers, access codes, serial-number photos and personal information from public posts.
Prevent Recurrence
Keep a short note of the confirmed working configuration, particularly the setting implicated by solar-only mode active. Repeat the disposable comparison after an app update, device replacement, major account change or new connection only when that change plausibly affects this issue.
Retain a recovery path: spare test material, a saved profile, a restore point, a backup copy or official service information, as appropriate for the device. Do not schedule risky resets as routine maintenance.
FAQ
Is solar-only mode active definitely the reason this happens?
No. The same symptom can come from current minimum unmet or export telemetry oscillates. First compare the affected and unaffected paths: Compare exported power logs and minimum current threshold during a daylight-to-evening transition. Do not assume any cause without a different outcome.
How can I safely rule out current minimum unmet?
Try the reversible correction only after documenting the control: Select the supported minimum grid-assist or pause threshold matching the intended charging policy. If the behavior does not change, restore the old value and use the deeper observation: Examine smart-meter telemetry delay, charger current floor and anti-flapping hysteresis.
What if export telemetry oscillates turns out to be responsible?
Do not force an unsupported setting or a factory reset. Keep the evidence and ask the manufacturer or responsible administrator to investigate the isolated layer. The measurable pass condition remains: A planned test charges or pauses according to the explicitly selected policy without rapid cycling.