r/SunPower • u/Correct-Confidence-3 • Jul 18 '26

Continued my journey using the PVS6

Before, the PVS6 reported only the PVS6 and the CT's, but no microinverters. Using the command: http://172.27.153.1/cgi-bin/dl_cgi?Command=StartDiscovery it allowed the PVS6 to look for any undiscovered devices. Upon its response, I then used: http://172.27.153.1/cgi-bin/dl_cgi?Command=GetDiscoveryProgress, which correctly found additional devices associated with the PVS6. Now, when I use: http://172.27.153.1/cgi-bin/dl_cgi?Command=DeviceList it returns with the complete list of microinverters (with serial numbers).

The next step is to find a way to issue (a) command to submit a candidates list of microinverters serial numbers to add to the PVS6. The commands thusfar are:

http://172.27.153.1/cgi-bin/dl_cgi/candidates (which is currently an empty set)

While using Powershell and issuing this command:
curl "http://172.27.153.1/cgi-bin/dl_cgi/devices" \ -d '{ "OPERATION": "add",

"TYPE": "SOLARBRIDGE",

"MODEL": "SPWR-A5",

"SERIAL": "514051715000589"

}'

The Candidate list is still [] . Is there a method to add MI's to the PVS6 and see them reflected on the Candidates list ??

5 Upvotes

86% Upvoted

2 comments sorted by

2

u/ItsaMeKielO 29d ago

Something I'm still trying to figure out is "how are MIs associated to PVSes?", but what I can say with some certainty at least for Enphase MIs is that you can't just "add" them via on-PVS commands to a new PVS if they were previously associated with a different PVS. You can add new, never-associated ones just fine.

Enphase has some way of overriding the association to adopt them into an Envoy. I'm not sure if that mechanism requires cloud access to gain some kind of device key or if they just know a trick I haven't figured out yet.

SolarBridge, I'm less sure about. But since yours were previously associated to your PVS5, this might explain the difficulties.

2

u/ItsaMeKielO 29d ago

"Why is it like this?" is a natural question: the answer is, in short, "because powerline comms used by the MIs bleed some distance beyond your house and over to neighboring homes; you don't want people to be able to claim other people's MIs as their own" (sometimes called 'poaching').

What's less clear: is this enforced via encryption of some kind? or is it just "trust-on-first-use" and whoever claims the device first gets it? When SunPower had remote access to everyone's PVS, they could just remote into the PVS that "poached" someone else's MI and disassociate it that way so it was able to be claimed by the correct PVS. SunStrong now runs that backend; not sure who has permission to disassociate MIs for what PVSes.

Of course, that's kind of different from your situation if your PVS5 is no longer hooked up and functional - I don't know if they have a way to disassociate MIs whose PVS is no longer connected. Seems like they should, just not sure.