1. Home
  2. Docs
  3. H60 Gateway Manual
  4. Modbus TCP Integrations

Modbus TCP Integrations

The H60 gateway support Modbus TCP 2.0 acting as a slave (server).

It means that a Modbus TCP Client connects to H60 on given port and can request registers.

Features and functions.

  • TCP Port can be selected in the config (502 is the official port)
  • If port is set to 0 Modbus Server is disabled (default)
  • Client can request and receive up to 20 registers in one call
  • Uses register type INPUT for all read only parameters.
  • Uses register type HOLDING för writable registers
  • Only one client can be connected at a time

Get started

Access H60 web interface and sett config parameter MODBUS_PORT to your selected port, like 502.
Restart H60. The front web page showing all the heat pump sensors have now got a new column called Modbus. This column shows the Modbus Register ID for each sensor and the type, Input or Holding.

To request registers from H60, configure your Client with the IP address of H60 and the port you configured. Test to let it send a Modbus TCP request for register 0. It should receive the sensor temp value for the heatpumps (see list)

Example config for Home Assistant

Note the extra template section to convert integer number to float. H60 sensor values har to be divided by 10. For example value 385 is 38.5 degrees.

name: H60
type: tcp
port: 502

- platform: modbus
scan_interval: 1
- name: m_0
hub: H60
register_type: input
register: 0
- name: m_1
hub: H60
register_type: input
register: 1
- name: m_2
hub: H60
register_type: input
register: 2
- platform: template
unit_of_measurement: °C
value_template: "{{states('sensor.m_0') | float / 10 }}"
unit_of_measurement: °C
value_template: "{{states('sensor.m_1') | float / 10 }}"
unit_of_measurement: °C
value_template: "{{states('sensor.m_2') | float / 10 }}"

How can we help?