Pairing links each power optimizer to its inverter and starts optimizer operation. Optimizers produce no power until they are paired. If pairing fails, the inverter shows an error, and the system does not start producing power. The usual cause listed is shaded optimizers. Optimizers need power to pair, so pair only in good light, and check for snow cover in winter. If the inverter is connected to the monitoring platform, retry pairing remotely in daylight. Leave the inverter ON/OFF switch on and check that S_OK appears on the status screen. Remote pairing needs the right permissions on the installer account. It takes about 15 to 20 minutes, and you should wait for the next reporting period to confirm that all optimizers show production. Pairing has to be repeated after the string length changes or an optimizer is replaced. Check for earlier replacements and update the serial number in the portal logical layout. If repeated pairing still fails, follow the power optimizer troubleshooting steps and then contact manufacturer support.
<!-- review notes
observed_asc1 verified · fact Inverter fault code display
When the pairing process fails, the inverter shows an error on its display; repeat pairing and follow the power optimizer troubleshooting section.
sec=h112 h=80d4e6a24f8fverified by: review-workflowverified on: 2026-10-24
c2 drafted · lead Low reporting optimizer count proposed
The pairing status shows a POK count of paired optimizers. Optimizers do not produce power until they are paired, and after a remote pairing you wait for the next reporting period to confirm that every optimizer shows production.
sec=h4 h=6a1a2e5ff47fsec=h33 h=accc809b1283sec=h1 h=53f71e0804f4sec=h112 h=80d4e6a24f8freview note: support check: partial - The passages support that optimizers don't produce power until paired, the POK ##/## count, and waiting for the next reporting period. They don't state a low reporting count as the observable, or the specific W signals, such as AC power staying at zero.; review: partial - The passages support the POK ##/## count, that optimizers produce no power until paired, and waiting for the next reporting period after remote pairing, but none says a low count is what a pairing failure looks like.