Solakon ONE (pv)
The Solakon ONE is a compact hybrid inverter and balcony power station, sold under the same hardware platform as the FoxESS MQ2200, targeting residential plug-in PV installations. This Modbus TCP template reads two core PV registers: instantaneous total PV power at address 39118 and cumulative PV energy generation at address 39149. With these two registers polled via the ModbusCloud Gateway, installers and building owners can track live solar output and long-term yield from the Solakon ONE, Avocado, Avocado Pro, and MQ2200 variants in a single portal view.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 2, read only
- Brand
- Solakon
- Compatible models
- Avocado · MQ2200 · ONE · Avocado Pro
- Last updated
Registers (2)
2 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | kWh | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Monitor real-time PV power output to verify the Solakon ONE is generating at expected levels during daylight hours.
- Track cumulative energy yield over weeks and months to detect gradual performance degradation.
- Alert on zero power readings during peak irradiance hours to catch inverter faults or disconnected panels quickly.
- Compare daily PV generation across multiple Solakon ONE sites to identify underperforming installations.
- Report monthly kWh totals from the energy register to support grid-operator feed-in documentation.
Installation
Connect the Solakon ONE to your local LAN or WLAN. The device obtains an IP address via DHCP; check your router's client list or use a network scanner to find it, as no static IP configuration is available on the device.
Verify Modbus TCP is active by opening a telnet connection to the device's IP on port 502. A successful connection confirms the Modbus server is running. The default Unit-ID is 1.
In the ModbusCloud portal, add a new ModbusCloud Gateway, then import the Solakon ONE (pv) template. Set the target IP to the inverter's address, port 502, and Unit-ID 1 under the communication settings.
After saving, open the live register view and confirm that address 39118 returns a non-zero power value during daylight and address 39149 shows a plausible cumulative count. Divide the raw energy value by 100 to verify it matches the kWh figure in the Solakon app.
Things to watch for
The gateway connects to port 502 but power reads zero at night.
This is expected behaviour. The Solakon ONE's Modbus server remains active, but the PV power register reports zero when there is no solar irradiance. Cumulative energy at 39149 holds its last value and does not reset. If you see zero during daytime, check that the inverter is not in standby or error state via the Solakon app.
Modbus TCP connection times out and no data appears in the portal.
The device uses DHCP, so its IP address may change after a router reboot. Confirm the current IP in your router's client list and update the gateway target address in the ModbusCloud portal accordingly. Also verify that port 502 is not blocked by a firewall or VLAN rule between the Gateway and the inverter.
The energy register value looks unrealistically large. What is the scaling?
Register 39149 stores cumulative generation as a raw uint32 where the actual kWh value equals the raw reading divided by 100. For example, a raw value of 150000 equals 1500 kWh. The ModbusCloud template applies this scaling automatically, but if you are cross-checking with a Modbus tool directly, apply the 0.01 factor manually.
Function code 3 returns an exception code 1 (illegal function) on first poll.
Some firmware builds on the FoxESS MQ2200 platform reject function code 3 on certain addresses and require the device to have fully completed its startup sequence before accepting Modbus requests. Wait 60 seconds after the inverter powers up, then retry. If the error persists, confirm Unit-ID is set to 1 in the portal, as a mismatched Unit-ID also produces exception code 1.
More Solakon templates
Want to see how it works?
