LK Systems Floor heating (ongoing) (help wouldn’t hurt)

Background (short: I am buthurt)
I have bought a product from one of those providers that really REALLY annoys you, and that I’ve decided to try to work around.

LK Systems is a pretty expensive provider of water carried floor heating, in at least the Nordic countries. My system cost me 15,000 USD for just one floor. They got a thermostat in each room which sends out a temp with 433mhz to a central that adjust the waterflow. I paid the contractor like 800 USD for the central and 70 USD for each thermostat.

The central got a USB port. IF I buy their LK Systems Mem Stick for 80 USD I can download information from the central.

I can also get LK WEB Server for around 400 USD — that will do the magic trick of getting the information from the central to the World Wide Web (if I hook it up with an Ethernet cable)… This wasn’t standard and enough is enough.

In this project I will try to get the data from the darn thing and into Home Assistant, I am not paying them a cent more…

What do we have to work with?
I got (1) the USB port and (2) a BUS port, which possibly is the best bet I got to work with, or maybe that is just for steering the darn thing.


I’ve found information that their BUS port is compatible with Modbus protocol RS485/RTU for commercial properties. This could be my fortune. I’ve also found this info for commercial properties:

If I just can get the BUS port to HA, there is — THANK GOD — this integration that can communicate with the RTU protocol referred to above.

Progress?
None so far, but I will go to work on it.

Any thoughts, tips etc would be greatly appreciated!

1 Like

Hi
Did you manage to get any progress with this?
I have a excel file with modbus addresses in order to control and monitor the complete LK ICS.2.

2 Likes

I am not sure why the modbus home assistant integration hasn’t worked for @Messier1994 but I saw today a post pointing to an esphome fork which had modbus support. Read modbus with ESP32 and ESPHome - #19 by nikito7

1 Like

That sounds awesome!

Spring came and I’ve been occupied in the garden. Have been snoozing this project for a while.

Have you managed to get it to work with HA? I have the components at home.

1 Like

Hi all,

Building a new house and are installing LK togheter with Nibe. Would love to see some progress with this!

Am I right in telling the installer company to get this instead of the basic? ICS.2 Trådförbunden/Trådlös - LK Systems

1 Like

Yeah that is the right order, and we should definitely get this project going again.

2 Likes

So what’s the difference between LK and Uponor comparing their hardware?
There is a integration in HA for Uponor, link: dave-code-ruiz/uhomeuponor: Custom Component to connect Home Assistant with Uhome Uponor Smatrix App (github.com)
It seems that that connects locally to Uponor R-167 gateway. I assume R-167 is something like LK Webserver ICS.2. I am also using LK Webserver ICS.2 and it just feels like an easier way of pulling data from that then trying to integrate it with modbus RTU. You can also login to the LK webserver locally but where to start :slight_smile:

1 Like

Homey har en app för LK Webserver. LK Systems App för Homey | Homey

1 Like

English please.

1 Like

So winter is fast approaching and I’m curious if anyone have made any progress with this? I have two LK ICS.2 units (one master and one slave) but I don’t have the web server unit.

Do we think it’s possible to send data from the Lk unit to home assistant with modbus or something else?

1 Like

I’ve not prioritized this project, but during the summer I did a similar thing with BMS for a solar battery and it was straight forward. Unless I am missing something it’s possible to just piggyback of something like this project with the above data for the LK communication:

I think you are the same person that I just answered at byggahus.se but I’ll just type it in here to :smiley:
I emailed LK systems and got their dokumentation about the modbus interface, was planning to run it with a ESPHome setup since they have native modbus support.

LK docs: LK Modbus - Google Drive
ESPHome: Modbus Controller — ESPHome

I have a setup with a USB to RS485 adapter from Amazon. Works fine with the Modbus integration. I can control the thermostats and read room temperatures etc.

Can you show how you do it. Hardware, code, pictures och more. Med vänlig hälsning, Kenneth

Sure, work in progress here: GitHub - astrandb/lk-systems-floor: How to setup Home Assistant with modbus integration for LK Systems ICS.2

Åke S

1 Like

Thanks, do you have a picture how you wire it to ics 2.

No, not hand. But there is a socket in the ICS.2 labeled BUS, I don’t remember which pin is which. Connect A-A and B-B

Thanks for the good work :slight_smile:
But i have problems! Hope you can help!
After setup i have this issues:

Sensor info:

climate.sovrum_o

Sovrum Ö unavailable hvac_modes: auto min_temp: 7 max_temp: 35 target_temp_step: 0.5 friendly_name: Sovrum Ö supported_features: 1

Log:

Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:391
Integration: Modbus (documentation, issues)
First occurred: 12.32.52 (1 occurrences)
Last logged: 12.32.52

Pymodbus: lk_gulvvarme_modbus_dongel: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)

Hardware info:

ttyUSB0
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0
Subsystem:
tty
Sti til enhed:
/dev/ttyUSB0
ID:
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0
Attributter:
DEVLINKS: >-
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0
/dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: >-
/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: FT232R_USB_UART
ID_MODEL_ENC: FT232R\x20USB\x20UART
ID_MODEL_ID: ‘6001’
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_3_1_0
ID_REVISION: ‘0600’
ID_SERIAL: FTDI_FT232R_USB_UART_A50285BI
ID_SERIAL_SHORT: A50285BI
ID_TYPE: generic
ID_USB_DRIVER: ftdi_sio
ID_USB_INTERFACES: ‘:ffffff:’
ID_USB_INTERFACE_NUM: ‘00’
ID_VENDOR: FTDI
ID_VENDOR_ENC: FTDI
ID_VENDOR_ID: ‘0403’
MAJOR: ‘188’
MINOR: ‘0’
SUBSYSTEM: tty
TAGS: ‘:systemd:’
USEC_INITIALIZED: ‘80787331347’

My yaml:

modbus:

name: lk_gulvvarme_modbus_dongel

type: serial

method: rtu

port: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0

baudrate: 38400

stopbits: 1

bytesize: 8

parity: N

climates:

- name: Sovrum V

  unique_id: climate_sov_v

  slave: 1

  # zon 1

  address: 1001

  input_type: input

  target_temp_register: 1002

  data_type: int16

  precision: 1

  scale: 0.01

  max_temp: 35

  min_temp: 7

  temperature_unit: C

- name: Sovrum Ö

  unique_id: climate_sov_o

  slave: 1

  # zon 1

  address: 1201

  input_type: input

  target_temp_register: 1202

  data_type: int16

  precision: 1

  scale: 0.01

  max_temp: 35

  min_temp: 7

  temperature_unit: C

sensors:

- name: Sovrum V

  unique_id: temp_sov_v

  slave: 1

  # Zon 1

  address: 1001

  input_type: input

  device_class: temperature

  state_class: measurement

  unit_of_measurement: °C

  scale: 0.01

  precision: 1

  data_type: int16

binary_sensors:

- name: Heating Sov V

  unique_id: heating_1

  slave: 1

  address: 1003

  input_type: discrete_input

Pymodbus: lk_gulvvarme_modbus_dongel: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)

This error indicates that no data is received on the modbus. It can also be that nothing is sent so the LK controller doesn’t send a response. It is probably a cabling or connection issue. Your settings look OK even if they are difficult to verify because the leading whitespace is removed. You can avoid that by selecting the code part and pressing </> or ctrl+e

1 Like

I’m working on a Node-red flow that publish data to MQTT and uses auto discovery in Home Assistant. Currently it is work in progress, will post here when I have something ready for testing.

The NR flow communicates over modbus and tries to map values for sections and zones defined in the system. The goal is to only publish defined sections and zones to MQTT but in the current version everything is published to MQTT and discovery will mark the entities as available if they are defined. So currently you end upp with a lot of entities in HA. :wink:

My LK setup is two 8 channel ICS.2 paired wirelessly within my house. I’m running modbus to the master central unit (called Section 1) and get data from the other one called Section 2.