Weishaupt WPM (SG Ready)
The Weishaupt WPM is a heat pump manager that controls Weishaupt heat pump systems for space heating and domestic hot water. This template connects over Modbus TCP and reads the configured SG Ready states for both input contacts A and B, plus the domestic hot water temperature. It also writes SG Ready mode setpoints to contacts A and B, allowing a building energy management system or PV inverter to switch the heat pump into boosted or blocked operation. Integrators gain a direct, auditable view of SG Ready state and hot water temperature in one portal.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 5, read and write
- Brand
- Weishaupt
- Last updated
Registers (5)
3 read, 2 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| getmode_in_config_a | Read | ||||
| getmode_in_config_b | Read | ||||
| setmode_a | Write | ||||
| setmode_b | Write | ||||
| temp | °C | 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 the active SG Ready configuration on contacts A and B to verify correct PV-surplus control signals are reaching the WPM.
- Track domestic hot water temperature over time to confirm the heat pump meets setpoint after an SG Ready boost event.
- Alert on unexpected SG Ready mode changes that could indicate external interference or a misconfigured energy management system.
- Write contact A or B mode setpoints from the portal to test SG Ready integration before commissioning a full PV control workflow.
- Compare SG Ready contact states against solar generation logs to verify that boost commands align with actual surplus periods.
Installation
Enable Modbus TCP on the WPM by navigating to the communication or Modbus section in the expert menu, setting access to 'On', and entering the IP address or subnet of the ModbusCloud Gateway as the permitted client.
Connect the WPM to the same LAN segment as the ModbusCloud Gateway using a standard Ethernet cable and confirm the WPM responds on port 502 using a port scan or ping before proceeding.
In the ModbusCloud portal, add your Gateway, import the Weishaupt WPM (SG Ready) template, and assign Modbus unit ID 1 (the WPM default) along with the WPM's IP address and port 502.
Verify the connection by spot-checking register 32102 in the portal and confirming the displayed domestic hot water temperature matches the value shown on the WPM display, applying a scale factor of 0.1 to the raw value.
Things to watch for
The gateway connects but all registers return errors. What is wrong?
The WPM whitelist only allows the specific client IP or subnet entered in its Modbus TCP settings. Confirm that the ModbusCloud Gateway's IP address matches the network address configured in the WPM expert menu under the Modbus TCP section. A mismatch causes the WPM to refuse all connections silently.
Register 32102 shows a value that looks too large. How do I interpret it?
The WPM returns raw int16 values scaled by a factor of 0.1. A raw reading of 523, for example, represents 52.3 degrees Celsius. Apply scale 0.1 in the portal channel configuration. Without this scaling the displayed value will be ten times the actual temperature.
Why do registers 35101 and 35102 not change after I write to 45101 or 45102?
Registers 35101 and 35102 reflect the configured SG Ready behaviour for each contact, not necessarily the live commanded state. Allow a polling cycle to complete after writing. Also note that the WPM may have minimum reaction times of several minutes before the operating mode visibly changes.
Is it safe to write any value to the SG Ready setpoint registers?
Use write registers 45101 and 45102 with caution. Writing an unintended mode can force the heat pump into a boosted or blocked state that overrides normal heating schedules, potentially causing thermal discomfort or increasing grid consumption unexpectedly. Always test writes during low-demand periods and revert to the neutral mode (0) after testing.
Want to see how it works?
