Solar Monitoring App Not Working: When to Call for Service

When solar monitoring is not working, first determine whether the app lost data or the solar system lost production. Check the phone/app session, the manufacturer’s current support notices, the last-good timestamp, account ownership, home internet, and owner-visible gateway or inverter indicators. Compare those observations with utility interval data and any independent approved meter without assuming they measure the same thing.

Call for qualified service when there is a safety concern, a persistent equipment alert, multiple devices missing, conflicting meter/CT flows, an offline gateway that does not recover through the manufacturer’s owner-level steps, or evidence of real production loss. Do not open equipment, climb, test conductors, change commissioning/export settings, or repeatedly reset breakers.

Teamsun offers solar maintenance and repair, but this research found no verified Teamsun monitoring-portal access, supported brands, diagnostic or commissioning capability, response time, service price, or ticket outcomes. Apply this evidence standard to Teamsun and every provider. If the packet below is ready, request a monitoring diagnostic review.

Direct answer: an app flatline does not prove zero solar production, and a normal-looking graph does not prove that production, consumption, import, export, or battery flows are measured correctly. Trace the complete data chain—device → gateway/meter → home network → vendor cloud → account/app—and compare it with a measurement that actually answers the question.

Start with safety, then preserve the monitoring evidence

Most app failures are not emergencies. Smoke, flame, arcing, burning odor, shock/tingling, abnormal heat with another warning, water inside electrical equipment, exposed conductors, severe impact, a displaced module, or a damaged battery is different. Keep people away, call 911 for fire or immediate danger, and contact the utility or appropriate responder as directed. Do not approach equipment for a label photo when doing so is unsafe.

The Occupational Safety and Health Administration lists shock, electrocution, burns, arc flash, and falls among solar electrical hazards (OSHA solar electrical safety). PV conductors can remain energized in daylight. A blank app, off AC breaker, or successful logout never makes roof equipment or electrical enclosures safe for homeowner work.

Before refreshing, signing out, reconnecting Wi-Fi, or following an exact owner-manual step, capture this timestamp packet:

Evidence	Exact return	Why it matters
App screen	full screenshot, product/site selected, phone time/time zone, exact message, app version	distinguishes stale data, wrong site, alert, and display issue
Last good data	last complete interval/day and first missing interval	narrows cloud, router, gateway, work, storm, and grid events
Account	owner email identifier, ownership type, installer/maintainer, recent transfer or password/MFA change	account access can fail while hardware works
Home network	ISP/router change, SSID/password change, outage times, working devices, gateway connection type	isolates household connectivity without touching solar wiring
Visible equipment	exact model/serial and status lights/display observed from a safe position	routes to the correct manufacturer instructions
System context	solar-only, battery, gateway/controller, third-party inverter, meters/CTs, export control	determines which app measurements should exist
Utility context	serving utility, grid outage/status, interval import/export, meter read dates	tests grid events and net flow, not total PV by itself
Recent changes	roof/electrical work, battery/inverter update, firmware/app update, router, storm, tree work	locates the likely transition
Actions already taken	exact step, source, time, repetitions, result	prevents repeated resets and lost evidence

Do not share passwords, multi-factor codes, router credentials, raw account-recovery links, or screenshots containing unnecessary utility/account identifiers by ordinary email. Use manufacturer invitations, maintainer access, secure case uploads, or account-transfer workflows. Redact irrelevant personal data while preserving site ID, device model/serial, timestamps, and alert text needed for support.

Trace the seven layers behind a solar app flatline

A monitoring graph is the final display in a longer chain. Move from least invasive to most technical. Do not skip to “bad inverter” because the final screen is empty.

Layer	Common symptom	Safe owner check	Service evidence if unresolved
1. Vendor cloud/app release	many screens fail, login/service error, several owners report same timing	current vendor support notice, in-app notice, official communication; record time	vendor case/incident confirmation and recovery timestamp
2. Phone/app/session	one phone fails, stale cache, wrong site/product, authentication problem	internet on phone, correct official app/account/site, app-store version, sign-in recovery	screenshots, OS/app version, account-support case
3. Account ownership/access	product missing, old owner/installer controls site, maintainer cannot see data	verify registered owner and authorized users in official account workflow	deed/contract or ownership evidence, site ID, transfer/maintainer case
4. Home internet/router	app shows gateway offline after ISP/router/password change	confirm household internet and documented supported connection/status	signal/network review without sharing password; gateway logs/status
5. Gateway/communications	gateway last report is stale, one or all devices not reporting	owner-visible LEDs/status and exact manufacturer app steps only	gateway power/communications, firmware, device link, cellular/Ethernet/Wi-Fi diagnosis
6. Meter/CT configuration	impossible power flow, negative/duplicated consumption, app disagrees persistently	capture flows under known load/solar conditions; do not move CTs	one-line, CT/meter model/orientation/location/configuration and calibrated comparison
7. Power equipment/grid/control	persistent device alert, whole or partial production loss, curtailment/export cap	utility outage check and exterior indicators only	inverter/device logs, electrical tests, grid/export settings, production-meter and one-line review

The U.S. Department of Energy’s PV monitoring-platform guidance separates cloud/software, instrumentation, inverters, strings/modules, weather, alarms, curtailment, and utility interfaces. That layered model is for larger monitored assets, but the measurement principle applies to homes: a dashboard is an interpretation of particular sensors and communications, not the electricity itself.

Build a last-good-data timeline

Use one chronology rather than separate calls to the internet provider, manufacturer, installer, and utility with different facts.

Time/date	App/cloud	Gateway/device	Router/internet	Utility/grid	Work/weather	Meaning—not diagnosis
___	last complete interval ___	visible status ___	normal/change ___	import/export/outage ___	___	last known aligned data
___	first gap/message ___	___	___	___	___	earliest transition
___	account/app action ___	___	___	___	___	action and result
___	data resumed or remained stale ___	___	___	___	___	recovery/escalation evidence

If all users and devices failed at the same minute, a platform or site-wide communications cause deserves attention. If one phone fails while the vendor web/app on another authorized device is current, start with the phone/session. If one module-level device drops while gateway and other devices report, do not blame the router. These are routing clues, not component diagnoses.

Compare the app with utility and device evidence correctly

The app, utility meter, inverter, production meter, and battery gateway may each measure a different boundary. Two accurate numbers can disagree because they answer different questions. Conversely, matching totals can hide reversed CTs or missing equipment.

Evidence source	What it may measure	What it cannot prove alone	Best use
Manufacturer app PV tile	inverter/gateway-reported PV production	CT accuracy, utility billing, complete devices, cloud freshness	device status, timestamps, production trend
App home/consumption tile	CT-derived home flow, sometimes calculated	accuracy when CTs are absent, reversed, misplaced, or misconfigured	flow-pattern screen after configuration is verified
Utility revenue meter/interval portal	net import/export at utility meter	solar consumed instantly behind the meter; module/device health	grid outage and billed net-flow corroboration
Dedicated PV production meter	production at its defined point	household load, every portal mapping, or module cause	independent PV-energy total when installed/configured correctly
Inverter display/local status	inverter output/state and events	vendor cloud/account or whole-home CT accuracy	distinguish reporting path from inverter operation
Battery gateway/controller	measured flows at installed CTs and system devices	third-party generation omitted from its sensors/configuration	battery/solar/grid interaction when one-line and CTs are known
Bill	net billed energy, dates, tariff charges/credits	exact production, short gaps, app correctness	long-period reconciliation after rates/read dates are normalized

Tesla explains that a utility meter generally records energy entering or leaving the grid and cannot see solar consumed immediately in the home (Tesla performance guidance). Therefore, utility export is not total solar production. A sunny period with utility export can prove energy crossed the meter, but zero export does not prove zero PV: the home or battery may have consumed production.

Enphase explains that its gateway gathers microinverter data while production and consumption CTs enable additional flow views; CT errors can create abnormal production/consumption readings that require professional correction (Enphase device guide, Enphase troubleshooting). A normal green health screen cannot validate CT direction, phase association, multiplier, meter location, or inclusion of third-party equipment.

App-versus-meter decision matrix

App observation	Utility/dedicated evidence	Likely next category	Do not conclude
App stale; inverter/production meter advances	utility/export or production evidence continues	internet/gateway/cloud/account path	panels stopped producing
App stale; no independent production evidence	utility shows imports but no useful export	communications or production	bad gateway or bad inverter without tests
App current; impossible negative/duplicate flows	utility/battery behavior conflicts	CT/meter/configuration or omitted equipment	app math is accurate because it updates
One device missing; total production plausible	gateway and rest of system current	device communication/local fault/map	failed panel or microinverter from tile alone
App and device show zero during grid outage	official utility outage confirms event	grid/islanding/operating-mode route	equipment failure
App current but production lower than expected	utility and weather-normalized evidence agrees	real performance diagnostic	cleaning, inverter, or module cause without diagnosis

For a verified production concern rather than a display failure, use the solar low-production diagnostic framework. B167 stops at proving which evidence and service scope are needed.

Follow only the exact manufacturer’s safe owner route

App names, gateways, update intervals, indicators, transfer tools, and support thresholds differ. Use the exact North American product documentation visible for the installed model. The table below is routing guidance as of August 10, 2026, not permission to reset equipment.

Platform	What “offline” may mean	Safe evidence/route	When professional service becomes the next step
Enphase App / IQ Gateway or Envoy	Gateway Not Reporting means the gateway lost internet/cloud reporting; microinverter-not-reporting is a different link	capture alert, gateway/device page, last report, router change, owner-visible LED; follow the in-app gateway instructions	gateway will not reconnect, device alerts persist, CT flows are abnormal, or manufacturer directs a technician
mySolarEdge / inverter communications	app data can be stale while inverter communication status differs	capture Last Updated, site/model/serial, blue communication LED or supported display status, router history	data was never commissioned, remains stale after official router/app checks, red/error state appears, or meter/optimizer evidence conflicts
Tesla app / Solar Inverter or Gateway	Tesla Solar Inverter connects directly; a third-party inverter system may use Gateway 1/2	confirm correct Tesla Account/product, app view, internet, gateway/inverter exterior status, exact system type	connectivity remains absent, alert/service route appears, registration/ownership is unresolved, or production evidence conflicts
Other inverter/gateway	terms and LED meanings vary by exact model/region/firmware	model/serial, exact app, last update, full message, official manual/support	no current owner-level path, repeated event, hardware/network boundary unclear, or electrical/production evidence is needed

Enphase says Gateway Not Reporting means the IQ Gateway is not sending system data to the cloud; it does not necessarily mean solar stopped producing. Its current support page tells owners to check home internet and changed Wi-Fi details, then use the app’s exact gateway workflow. It also says a microinverter-not-reporting condition may not always mean lost production and recommends further action when it persists beyond 24 hours. Abnormal CT data belongs with a certified solar professional, not homeowner wiring work (Enphase troubleshooting).

SolarEdge says mySolarEdge data normally updates about every 15 minutes, exposes a Last Updated field, and uses the blue LED as a communications indicator on covered inverter types. Its current missing-production-data route starts with whether data ever appeared, then checks documented communication and router changes before installer escalation. Do not interpret another SolarEdge model’s display/LED procedure as applicable.

Tesla distinguishes systems with a Tesla Solar Inverter from third-party inverters using a Gateway 1 or 2. Its solar monitoring guide says loss of gateway/inverter connectivity prevents app monitoring. Its system troubleshooting guide notes that visible inverter production with stale app data indicates a communications path problem. Follow Tesla’s exact in-app route for that registered product; do not import a Powerwall, Gateway, or Solar Inverter reset procedure into another architecture.

Reset boundary

A homeowner may close/reopen an app, use official password recovery, restart a phone, verify ordinary household internet, or follow a clearly identified manufacturer owner-level app/network step for the exact product. Do not:

• open an inverter, gateway/combiner, disconnect, panel, battery, meter, or electrical enclosure;
• climb onto a roof or handle modules, optimizers, microinverters, wiring, or connectors;
• test voltage/current/insulation, move CTs, or change meter multipliers/orientation;
• change grid profile, export limit, battery commissioning, protection, or utility settings;
• cycle breakers or disconnects unless the exact manufacturer/installer has authorized that owner action for this exact condition; or
• repeat resets after the condition returns, especially after an error or protective trip.

The solar inverter error-code guide owns fault-code, repair, warranty, and RMA routing. The Enphase microinverter replacement guide starts only after a device-level failure is supported; “not reporting” alone is not that proof.

Check the vendor, home network, and grid before buying a truck roll

A cloud outage, phone problem, router issue, gateway issue, and grid outage can create similar app symptoms. Run this least-invasive sequence once and record the result.

1. Check the time. Overnight zero, reporting cadence, time zone, selected date, and stale “last updated” are different states.
2. Confirm the right site/product/account. Verify the official app and registered email without exposing credentials.
3. Check official vendor communication. Use in-app notices, manufacturer support, release notes, or a manufacturer-confirmed incident if available. Crowd outage reports are leads, not proof.
4. Test ordinary home internet. Confirm other devices can reach the internet; record ISP/router/SSID/password/firewall/guest-network changes. Do not reconfigure solar equipment from a generic video.
5. Observe supported exterior indicators. Use only the exact manufacturer page for the model. Record—not reinterpret—LEDs, display, and last report.
6. Check the serving utility’s official outage route. A grid-tied inverter normally stops during a grid outage unless an approved islanding/backup system supports operation.
7. Compare measurement boundaries. App, inverter, dedicated production meter, utility net meter, and battery CTs are not interchangeable.
8. Escalate with one packet. Send the chronology, not repeated unrecorded resets.

Service area	Official grid-outage route	Monitoring implication
Connecticut	Eversource CT outages or the actual utility’s official route, including UI where applicable	confirm the customer/utility and event time; no mapped outage does not prove normal voltage at the site
Massachusetts	The DPU’s Massachusetts power-outage directory routes Eversource, National Grid, Unitil, and municipal customers	use the actual serving company; municipal utilities may not appear in a statewide view
Rhode Island	RIEMA’s official outage-map directory routes Rhode Island Energy and municipal/island providers	match the address and event; utility restoration does not prove the monitoring chain recovered

An official map can confirm a broader event but not diagnose the inverter, gateway, service voltage, or a single-property outage. Record when grid service returned and when app/device data returned. A delay between those times is useful evidence.

Decide between urgent, same-day, and scheduled service

Response priority should follow safety, operating impact, and evidence—not frustration with a blank graph. This article publishes no Teamsun response SLA or universal time because none was verified.

Priority	Trigger	Immediate action	Service packet
Emergency/urgent safety	smoke, flame, arcing, burning odor, shock, water inside equipment, exposed conductors, severe impact/displacement, battery damage/abnormal heat	keep away; call 911 for immediate danger; utility/manufacturer/system owner as directed	evidence only from a safe distance
Same-day qualified routing	repeated protection/error event, whole-system production apparently absent after grid returns, backup/islanding failure affecting needed loads, abnormal noise/heat/odor without immediate emergency, multiple devices missing plus equipment alert	stop resets; contact manufacturer/installer/qualified provider	exact event, model/serial, timeline, grid status, ownership, safe indicators
Prompt manufacturer/installer case	gateway offline after official owner network steps, several devices not reporting, impossible CT flows, account transfer blocks service, monitoring required for a program/warranty, persistent data conflict	preserve state and open one supported case	timestamp packet, network changes, screenshots, one-line, access roles
Scheduled diagnostic	intermittent/stale data recovered but repeats, app-vs-meter reconciliation needed, one device missing without safety alert, historical gaps, suspected commissioning/map issue	export data and establish baseline	last-good timeline, raw data, support cases, acceptance criteria
Observe with a dated check	known vendor/cloud event confirmed, short reporting delay within documented cadence, overnight state, gateway uploading stored data after reconnection	do not reset repeatedly; recheck at documented time	incident/support notice and before/after timestamps

Enphase notes its gateway may store data and upload the backlog after reconnection, so a recovering graph can lag. SolarEdge publishes an expected update cadence for its platform. Use those exact platform facts rather than a universal “wait 24 hours” rule. A missing-device condition and a missing-gateway condition deserve different thresholds.

Fix ownership and data access before authorizing diagnostics

Remote diagnosis can fail because the wrong owner, installer, or maintainer controls the site—not because the hardware is unsupported. Resolve authority without giving a contractor the homeowner’s password.

Role/access field	Required return
Legal/system owner	owner, lease/PPA provider, lender constraints, estate/trust/association as applicable
Monitoring owner	registered vendor account and verified current email
Installer/maintainer	original installer, active maintainer, proposed service provider, permissions granted
Data visible	production, consumption, import/export, device view, battery, alerts, settings, history
Control permitted	view-only, service diagnostics, settings, warranty case; least privilege needed
Transfer evidence	site ID, model/serial, address, proof required by vendor, case/reference number
Privacy handoff	secure method, data fields shared, retention/deletion, access revocation date

Enphase’s ownership-transfer route gives the new owner access to the system account and monitoring (Enphase transfer of ownership). Its homeowner updates describe adding a new company as system maintainer rather than sharing credentials. SolarEdge’s site transfer and new-user route separates ownership, additional-user, and new-installation-company access. Tesla’s solar ownership-transfer guidance distinguishes cash, third-party loan, and Tesla/third-party-owned arrangements.

For third-party apps, read the requested permissions and privacy policy. Tesla’s third-party access guidance says energy permissions can include energy-flow history, tariff, grid import, site status, ownership, and settings, and that access can be revoked. Do not authorize control permissions when a read-only export answers the diagnostic question.

Require a service return schedule, not “monitoring fixed”

A service quote should separate remote intake, account recovery, network/gateway work, meter/CT diagnosis, equipment diagnostics, manufacturer support, and electrical repair. No-number fields prevent an app problem from becoming an open-ended electrical authorization.

Scope item	Included/amount	Responsible party	Deliverable	Change trigger
Records, timestamps, remote portal review	$___	___	data-chain hypothesis and missing items	no portal access ___
Ownership/maintainer/account transfer	$___	___	correct owner/users/roles	vendor evidence/fee ___
Home network/gateway communications	$___	___	connection type, signal/status, last report, recovery	gateway hardware/ISP issue ___
Meter/CT/map/configuration review	$___	___	one-line-to-sensor map and measurement test	intrusive electrical work ___
Inverter/device/battery diagnosis	$___	___	events, manufacturer case, measured findings	fault moves to B168/repair scope ___
Utility/grid/export coordination	$___	___	event/setting/approval finding	utility response or study ___
Repair/parts/permit/commissioning	separate $___	___	written authorization and acceptance	exact failed component ___
Data export, privacy and closeout	$___	___	owner access, raw files, revoked temporary access	platform limitation ___

The return-to-service report should include:

1. original symptom, first missing and last-good timestamps;
2. root cause supported by evidence—or unresolved hypotheses clearly labeled;
3. cloud/app/account, network, gateway, device, meter/CT, grid/export, and production findings;
4. exact settings or equipment changed by authorized personnel and why;
5. manufacturer/installer/utility case numbers and warranty status;
6. before/after screenshots plus raw-data interval and time zone;
7. app, gateway/device, dedicated production meter if present, and utility-boundary reconciliation;
8. device/map/meter/CT/one-line updates and serial list;
9. monitoring owner, maintainer, permissions, alerts, privacy retention, and revoked access;
10. acceptance period, expected update cadence, next review date, and service/warranty owner.

Proceed to closeout only when the correct site/account works, data is current through a stated timestamp, sensor boundaries are documented, the app agrees with an appropriate independent measurement within a justified method, alerts are resolved or assigned, and the owner can export data.

Pause when the graph returns but backlog, CT direction, third-party equipment, missing devices, ownership, warranty, grid/export event, or production reconciliation remains unresolved. A green app can hide incomplete closeout.

Stop the current proposal when it recommends an inverter, gateway, CT, microinverter, battery, or panel replacement solely from an app screenshot; asks for passwords; uses repeated resets; changes protected settings without authority; or bundles unknown repair work into an unlimited authorization.

If a provider can accept this evidence packet and define the return schedule, request solar diagnostics from Teamsun. Teamsun must still confirm brand/platform access, licensed scope, site safety, service territory, ownership authorization, warranty route, and availability before accepting the work.

Frequently asked questions about solar monitoring problems

Does an offline solar app mean my panels stopped producing?

No. It can mean the phone, account, vendor cloud, home network, gateway, or device-to-gateway link stopped reporting. Compare timestamps, owner-visible device status, and an appropriate meter/utility record before deciding whether production stopped.

Why is my solar app not updating after I changed routers?

The gateway or inverter may still have the old SSID, password, security, or connection. Confirm ordinary internet first, then use the exact manufacturer’s owner app instructions for the installed model. Do not follow a generic reset video or open equipment.

How long should I wait for missing data?

Use the platform’s documented cadence, message, and recovery state. SolarEdge normally updates more frequently than a cellular Enphase gateway, and an Enphase gateway can upload stored backlog after reconnecting. Persistent device alerts, safety issues, or true production evidence should not wait on a generic interval.

Can the utility meter prove my solar is working?

It can show net imports/exports at the grid boundary, not solar used immediately by the home or battery. Export during sunlight supports that generation crossed the meter, but no export does not prove zero PV. A dedicated production meter or inverter evidence answers a different question.

Why does my app show negative or impossible home consumption?

CT orientation, phase association, location, configuration, omitted equipment, or mapping can be wrong. Capture known-load and solar conditions, one-line, meter/CT models, and screenshots. A qualified professional should diagnose wiring/configuration; homeowners should not move CTs or open panels.

Why does one panel say “not reporting”?

That status can reflect module-electronics communication, gateway/powerline communication, branch/electrical condition, mapping, or device failure. Compare its last timestamp with gateway and neighboring devices. Do not order a panel or microinverter from one tile.

Should I reset the inverter or solar breaker?

Only when the exact manufacturer or installer authorizes that owner-level step for the exact product and current condition. Never repeat resets after a protective event, and never open equipment or change grid/export/protection settings. Preserve the alert first.

What if the solar app looks normal but my bill increased?

A normal graph can coexist with higher load, rate/billing changes, incomplete CT data, lower production, or different self-consumption/export. Rebuild bills and utility intervals, validate the app measurement boundary, and compare weather-normalized production before assuming equipment failure.

Can a new solar company access my old monitoring system?

Sometimes, after the legal owner uses the manufacturer’s transfer or maintainer workflow and the provider confirms brand/platform support. Use delegated access rather than sharing passwords, define visible/control permissions, and revoke access at closeout.

Will monitoring work during a grid or internet outage?

It depends on system architecture. A grid-tied PV system normally stops during a grid outage unless approved backup/islanding supports it. Loss of internet can stop remote app data while local equipment continues operating or storing data. Phone notifications also need connectivity.

Does fixing Wi-Fi restore missing historical data?

It may. Some gateways store data and upload it after reconnecting, but duration, cadence, completeness, and device behavior are platform-specific. Record the missing interval and verify the backlog rather than assuming every point returned.

How much does a solar monitoring service call cost?

There is no verified Teamsun or universal price in this guide. Scope can include remote account review, ownership transfer, network/gateway work, CT/meter diagnosis, electrical testing, manufacturer cases, parts, permits, and commissioning. Compare a written service return rather than a truck-roll total alone.

Research method and intent boundary

Research was frozen August 10, 2026 using current DOE, OSHA, Enphase, SolarEdge, Tesla, CT/MA/RI utility and emergency-management sources, representative first-page repair/monitoring pages, and homeowner discussions. Manufacturer sources control platform terminology and owner steps; utilities control outage status. Forum and competitor pages informed objections about stale apps, router changes, cloud outages, wrong CT flows, and installer access; no anonymous safety, diagnosis, price, support, or outcome claim was adopted.

B167 owns the monitoring-data-chain triage and service threshold: cloud/app/account, router, gateway, CT/meter, device/grid/production separation; timestamp packet; app-versus-meter matrix; manufacturer safe route; access/privacy handoff; urgency; service return; and acceptance. B168 owns exact inverter codes and repair/warranty claims. B160 owns confirmed Enphase microinverter replacement. Bill/rate pages own charge reconciliation, and B157 owns planned maintenance. No Teamsun portal access, brand support, response SLA, diagnostic ability, service price, ticket result, or monitoring outcome is implied.