Setup guides → LuxPower

LuxPower

Sunplug reads your inverter through the Wi-Fi dongle already fitted to it, on your own network: production, grid, house load, battery power and charge. LuxCloud keeps working as before.

Nothing to switch on

The dongle serves its local port from the factory: no setting, no installer menu, nothing to touch on the inverter. It is not Modbus — a generic Modbus tool pointed at the dongle gets no answer.

Sunplug only reads

The connection cannot write. The agent can only build a read request. Sunplug cannot change a charge schedule, an operating mode or any other inverter setting, and never asks for your LuxCloud account.

LuxCloud monitoring keeps working: the dongle holds its own connection to LuxPower.

Connecting

Sunplug Agent sweeps your network, and the dongle usually announces itself with both serial numbers filled in. If it does not, pick LuxPower inverter (Wi-Fi dongle) from the manual list, type its address and the two serials — one on the dongle's label, one on the inverter's. Or leave both boxes empty and the agent keeps listening for them.

1. Run the agent and open http://<machine>:8787
2. It finds the dongle — or pick LuxPower and type the address
3. Connect and test, and check the four figures against your inverter
4. Enter the six-character code from the app, and you are done

One local client at a time

The dongle's local server takes a single client. If Home Assistant, SolarAssistant or lxp-bridge already reads this dongle, Sunplug reports the port as taken. Keep that integration and send Sunplug its readings through the push API — Home Assistant can post them in a few lines.

When it does not work

"Nothing is listening on port 8000 there"

Usually the wrong address: use the Wi-Fi dongle's, which your router lists separately. Check the dongle is powered and on the same network as the agent — an IoT VLAN or guest network will hide it.

"…another client already has its local port"

Another integration holds the one local slot. Close it, or keep it and use the push API.

"Could not reach … — 2 tries over 6s"

The dongle did not answer, usually because it is busy with LuxPower's cloud — most often just after a power cut. Nothing to change: the agent retries on its own, waiting longer each time. A tool like nc may still connect, because it keeps trying for a minute where the agent stops after a few seconds.

"The dongle sent 1 block(s) of other data"

The dongle is answering its own cloud session or another app reading it. If Sunplug has read this dongle before, it says so and there is nothing to do; otherwise check the serials.

"No reply to the reading request"

A busy dongle and a mistyped serial look the same, so the agent reports only what it has evidence for. If it says the dongle was working earlier, the serials are right.

"The dongle answered for a different inverter"

The inverter serial is wrong: the dongle answered for another inverter on its bus. Check it against the label, character for character, or clear both boxes and let the agent wait for the dongle to announce them.

Restarting the agent will not speed any of this up

After failures the agent waits longer between attempts, up to five minutes, and a restart keeps that wait. The status page shows how long it has been failing and when the next attempt is due.

"That dongle is an E-WIFI ENC"

This encrypted variant refuses the local protocol, so there is nothing to retry. Use the push API, and please tell us — we are keeping count of these dongles.

Running one of these? Tell me how it goes — [email protected].