Siemens Junelight Smart Battery (pv)
The Siemens Junelight Smart Battery is a residential lithium-ion battery storage system designed to maximise self-consumption from a connected photovoltaic installation. This Modbus TCP template reads the instantaneous battery power register, giving your ModbusCloud portal real-time visibility into whether the Junelight is charging or discharging and at what rate. Connecting this single register to historical trending and alerting lets installers and homeowners track battery behaviour over time without relying on the Siemens app alone.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 1, read only
- Brand
- Siemens
- Last updated
Registers (1)
1 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | 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 instantaneous battery power to confirm the Junelight is charging during peak PV production hours.
- Alert on sustained discharge at unexpected times to detect overnight grid draw or inverter misconfiguration.
- Track daily charge and discharge cycles over weeks to identify capacity degradation trends.
- Compare battery power readings against PV output to verify self-consumption ratios for energy audits.
- Report battery activity across multiple residential sites from a single ModbusCloud multi-site overview.
Installation
Enable Modbus TCP on the Junelight Smart Battery by contacting Siemens support or your installer to activate the interface; the battery listens on port 502 once enabled.
Connect the Junelight to the same local network as the ModbusCloud Gateway via a standard Ethernet cable or your existing LAN switch.
In the ModbusCloud portal, add a new device, select the Siemens Junelight Smart Battery (pv) template, enter the battery's IP address, and set the unit ID to 1.
Verify the connection by checking that register address 16 returns a live integer value in the portal's register viewer; a value of 0 at rest or a non-zero signed value during charge or discharge confirms success.
Things to watch for
The gateway connects but register 16 always returns zero. Why?
A persistent zero can indicate the battery is idle and neither charging nor discharging, which is valid. However, if zero persists during known solar production, verify that Modbus TCP has been fully activated by Siemens support. Some firmware versions require explicit enablement before the interface responds with live data.
I get a connection timeout every time the gateway polls. What should I check?
Confirm the Junelight's IP address is reachable from the ModbusCloud Gateway on port 502. Check that no local firewall or router rule blocks TCP port 502. Also verify the unit ID is set to 1 in the portal, as the battery does not respond to other unit IDs.
The power value looks correct in magnitude but has the wrong sign. Is this normal?
The power register is a signed int32. A negative value indicates the battery is discharging energy to the home or grid; a positive value indicates charging. If the sign appears inverted relative to your expectations, check whether your PV system inverter is the one changing direction, not the battery itself.
Why do I see large, implausible spikes in the power reading occasionally?
Transient spikes in a signed int32 register can occur if the two 16-bit words are read across a register boundary update. Ensure your polling interval is at least 5 seconds to reduce the chance of mid-update reads. If spikes persist, check network latency between the Gateway and the battery, as high latency can cause partial reads.
Want to see how it works?
