Overview
H60 are supporting the entering of a few custom registers as an expansion of the pre-programmed. Data from custom registry data can then be pulled out using the H60 RestAPI, Modbus TCP or MQTT interfaces.
This feature is intended for advanced users as wrongly entered parameters could disturb the operations of your heating system. Use at own risk!
Custom registry’s will be polled and read from heat pump every 15 second in an sequential order.
As heat pump controllers are having different variable standards, please follow the individually instructions in this document for each supported model.
Husdata will not supply lists of registry IDs for heat pumps.
You can always ask us for a specific registry you need and we will try to find it for you.
When asking Husdata for an ID, please include your heat pump controller version as registry numbers differs between revisions.
Warning! Do not randomly try registry numbers as it could cause a registry writing with unpredictable effects on the heat pump operations.
Limitations
The custom registry implementation only support registries for which output is a value of maximum 2 bytes, 0xFFFF (65535), Unsigned Int. This means for example that some statistical registries returning huge data are unsupported.
Custom registries cannot be used in the Husdata Online system
Only reading registries are supported, not writing data to heat pump.
The scaling factor of return data can appear wrong in the H60 web interface as it varies between heat pumps.
Limited numbers of registers can be added, at the moment 10.
Instructions
Custom registries are appearing last in the registry list in the Home page of H60.
At the end of the Home page you will also find the “Manage custom registers” page link to access the configuration page as below.
From the Dropdown, select register to edit, or select ADD NEW to add a new one.
The edit box has three settings:
Register: Enter the 4-digit HEX register in format described for specific pump controller
Name: Give it a name, up to 25 characters.
Type: Select how value is presented. Temperature with decimals, State 1/0, etc..
To delete a register, select the last one and check the Delete box.
IVT / Bosch Rego600 registry format
ABCD
A 0 = HW, 2=APPVAR, 4=SEKTIMER, 6=MINTIMER
BCD Variable number in HEX
Example: ROOM_TEMP variable 525 which is of APPVAR(2) type.
525 in HEX is 0x20D
The Registry to enter in H60 is “220D”
IVT Rego 800 / 1000 registry format
ABCD
A Number of bytes in response for registry 1=Byte, 2=Integer
BCD Variable number in HEX
Example Rego 800: Clock Second in controller is variable 46 for ver. 3.20.2.
46 in HEX is 0x2E.
Response data for registry 46 is of type signed char (1 byte)
The Registry to enter in H60 is “102E”
Example Rego 1000: Clock Second in controller is variable 314 for ver. 3.6.0.
314 in HEX is 0x13A.
Response data for registry 314 is of type signed char (1 byte)
The Registry to enter in H60 is “113A”
IVT Rego 2000 / 3000 registry format
ABCD
A Always 0
B Telegram ID
CD Data pointer
Example/test: Air Intake temperature is “030C”
These specially compiled Registry numbers has to be provided by Husdata
Because of the protocol structure, additional custom parameters to access are very limited.
NIBE EB100 registry format
ABCD
ABCD Variable number in HEX
Example: Indoor temp registry 40033.
40033 in HEX is 0x9C61
The Registry to enter in H60 is “9C61”
NIBE STYR2002 registry format
ABCD
A Number of bytes in response for registry 1=Byte, 2=Integer, 4=Byte raw for Bit registers
B Always 0
CD Registry number in HEX
Example: Winter mode temp registry 41.
41 in HEX is 0x29
Response data for registry 41 is of type signed char (1 byte)
The Registry to enter in H60 is “1029”
Thermia Diplomat registry format
ABCD
AB Always 0
CD Registry number in HEX
Example: Winter mode ”Curve at +5” registry 55.
55 in HEX is 0x37
The Registry to enter in H60 is “0037”