NIBE S-Series (SG Ready)
The NIBE Nibe S-Series (SG Ready) is a ground source and air-to-water heat pump range designed for residential and light-commercial heating and domestic hot water. This ModbusCloud template connects over Modbus TCP and reads the active SG Ready operating state, hot water temperature, instantaneous power consumption, and accumulated energy. It also writes the SG Ready mode setpoint, enabling four operating levels from load blocking to full boost. Installers and energy managers gain direct visibility and demand-response control of NIBE S-Series heat pump operation from a single portal.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 5, read and write
- Brand
- NIBE
- Last updated
Registers (5)
4 read, 1 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| setmode | Write | ||||
| getmode | Read | ||||
| temp | °C | Read | |||
| power | W | Read | |||
| energy | 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 power consumption to verify the heat pump stays within contracted grid capacity limits.
- Track hot water temperature over time to detect degraded heating performance or sensor drift.
- Alert on unexpected SG Ready state mismatches between the setmode command and the getmode readback.
- Report accumulated energy figures weekly to compare heat pump efficiency across seasons or sites.
- Automate SG Ready mode switching to cheap-energy or boost during solar surplus periods and verify the state change via getmode.
Installation
Enable Modbus TCP on the NIBE S-Series unit by navigating to the communication or network settings menu (menu 5.2 on the display) and activating Modbus TCP. Confirm the unit IP address and that port 502 is reachable.
Connect the ModbusCloud Gateway to the same LAN segment as the heat pump via an Ethernet cable, ensuring no firewall blocks TCP port 502 between the Gateway and the heat pump.
In the ModbusCloud portal, add the Gateway, import the NIBE Nibe S-Series (SG Ready) template, and assign Modbus unit ID 1 (the default slave address for NIBE S-Series) to the device.
Verify the connection by checking a live reading on the temp or power register in the portal. A non-zero hot water temperature confirms the TCP session is established and data is flowing correctly.
Things to watch for
The gateway connects but all register values read zero or timeout. What is wrong?
Modbus TCP must be explicitly enabled in the heat pump display under the network or communication settings menu. Also confirm the heat pump firmware is version 2.2.1 or later for basic Modbus TCP support. Without activation, the heat pump will not respond to any Modbus queries even if the TCP connection appears open.
Register 1911 shows a code like 10 or 20. How do I read the SG Ready state?
Register 1911 returns an enumerated value, not a boolean. The values are: 10 = normal, 20 = blocked, 30 = cheap energy, 40 = free energy (boost). Map these in your portal dashboard accordingly. A raw value of 0 usually indicates Modbus TCP is active but SG Ready via API has not been enabled in the unit settings.
Writing to register 6008 has no effect on heat pump behavior. Why?
SG Ready control via Modbus TCP requires firmware version 4.7.5 or later on NIBE S-Series units. Additionally, SG Ready via API must be enabled within the heat pump menu before register 6008 writes take effect. Without that prerequisite, writes will be acknowledged by Modbus but silently ignored by the controller.
Can I freely write any value to register 6008 without risk to the installation?
Use caution when writing to register 6008. Setting mode 0 (blocking) prevents the compressor from running and can affect comfort or hot water availability during peak demand. Setting mode 3 (boost) forces maximum heat output and may run the unit at conditions outside its normal control envelope. Always test setpoint changes in a controlled window and confirm via getmode (register 1911) that the unit accepted the command.
Want to see how it works?
