What happened
If local requests to your PVS6 used to work and now return 403 unauthorized, your setup did not break. The gateway changed underneath it.
Two changes matter, and most people who hit this wall have run into one or both:
- March 2025 — the reporting URLs changed. PVS5 and PVS6 units were updated to the new addresses; legacy PVS2 units were not, which is why PVS2 owners saw "bad communications" errors while every light on the equipment looked normal.
- September 2025 — the local interface gained authentication. Calls that previously worked with no credentials started returning 403. This is the one that broke the DIY setups, and it is what most people are hitting today.
Neither is a fault on your side. There is no public explanation of intent, so treat anyone's account of why as speculation — but the sequence itself is well documented by owners who lived through it.
What this means practically
The important thing to understand is that the data is still there. Your gateway still reads every microinverter and still holds production and per-panel output locally. It did not stop collecting; it stopped handing it over to anonymous requests.
So this is an access problem, not a data-loss problem — which is why the maintained projects were able to adapt rather than give up.
What still works
The maintained open-source integrations. smcneece/ha-esunpower and krbaker/hass-sunpower are the two most widely used with Home Assistant, and pypvs is the library if you would rather build your own. Owners in the community threads report the actively maintained ones keeping pace with the firmware changes.
⚠️ Check the commit history before you spend an evening on any of them. This is the single most useful piece of advice on this page. Several PVS projects were written before the 2025 changes and abandoned; they look fine on the README and fail immediately in practice. Recent commits are the signal.
Expect the usual caveats regardless of route: an isolated network segment (the gateway runs its own DHCP server), polling gently rather than hard, and whole-home consumption only if CT clamps were fitted at installation.
The bigger point: this will happen again
The lesson owners took from the last two years is not "here is the workaround for the September 2025 build". It is that the local interface is a moving target, controlled by a company with no obligation to keep your setup working, and it has already shifted twice.
Whatever route you pick, pick one that someone is actively maintaining — a project with recent commits, or a product whose job it is to track the changes. A setup that works today and is nobody's responsibility to fix is a setup with an expiry date.
Where WattHacker fits
The WattHacker monitor is a small box that plugs into your existing SunPower PVS6 gateway on your own home network and reads it directly. It doesn't rely on SunPower's or SunStrong's servers, because for owners like you those are either gone or behind a paywall. No technician, no electrician, no rewiring — you plug it in yourself.
- The monitor is $50 once (list $100), with a 30-day money-back guarantee.
- Free to see your panel data, forever — every panel, live, no subscription and no card on file.
- An optional premium plan at $6/mo (billed annually) adds the memory: full history kept for good, year-over-year comparison, and alerts told to you in dollars.
- Built by an electrification superfan who wants to help others use their solar smarter, lower their utility bills, and clean up the planet. Who's behind it.
Common questions
Why does my PVS6 return 403 unauthorized now?
Because the gateway firmware changed. A September 2025 firmware update added authentication to the local interface, and requests that previously worked unauthenticated now return 403. Nothing is wrong with your gateway or your network — the endpoint simply stopped accepting anonymous requests.
Did SunStrong break local monitoring on purpose?
There is no public statement of intent, so anyone telling you the reason is guessing. What is documented is the sequence: in March 2025 the reporting URLs changed, which updated PVS5 and PVS6 units but left legacy PVS2 units unable to report; and in September 2025 a firmware update added authentication to the local interface. The effect on local monitoring was the same either way.
Can I stop my gateway updating its firmware?
Not reliably, and it is not a good idea to try. The gateway pulls firmware as part of normal operation, and blocking it can leave you on an old build with its own problems. Plan for the interface changing again instead of trying to freeze it.
Which local monitoring tools still work?
The actively maintained open-source projects have adapted to the change — smcneece/ha-esunpower and krbaker/hass-sunpower are the two most commonly used with Home Assistant, and pypvs is the library to build on. Check each project's recent commits before you invest an evening: the ones that are maintained track firmware changes, and the ones that are not have stopped working.
See your own panels, live.
See plans Back to home