Rego 6xx based heat pumps

Hi everyone,

I’m a new HA user currently in the process of migrating from OpenHAB, which I’ve used for many years.

One of the key components in my setup is a heat pump based on the Rego 6xx controller. These heat pumps have been around for many years and are used in many installations, so many integrations already exist. Originally, since there was no native support available in OpenHAB (in 2016!), I developed my own binding for it. That project eventually became an official OpenHAB binding and is still being used today.

During my migration to HA and based on my previous experience developing the OH binding, I decided to implement a HA integration as well.

GitHub repository:

Example of some readouts:

I’ve been using it in my own setup for a couple of weeks, and it seems stable so far, so I’ve shared it on GitHub in case anyone would like to test it and provide feedback - in my setup I’m using an ESP module with ser2net in my HP since I don’t have a cable connection to the HP, but that should work too.

If anyone here is using a Rego 6xx based heat pump and is interested in testing or contributing, feedback is very welcome.

Original OpenHAB binding thread (contains a lot of information on how to connect to the heat pump) for reference:

Any feedback or suggestions would be greatly appreciated.

Hi,
I have an IVT Heatpump using the Rego637 controller. I’ve been using a old RPi with a USB<->Serial TLL cable, and then forwaring though MQTT, but it is very cumbersome, so i would like to check out your solution. What hardware are you using for the ethernet-serial brigde that supports the 5V TTL?

Best Regards
Chriswein

Hi Chriswein,

I’m using a solution similar to the one shown here:


(from https://rago600.sourceforge.io/)

It uses an optocoupler to provide galvanic isolation between the heat pump and my hardware, and at the same time performs the required level conversion.

This interface is connected to an ESP8266, running ESPEasy together with ser2net, which provides the ethernet-to-serial bridge functionality. I’m planning to migrate to esphome for better HA integration, but since this has been working flawlessly for years, I haven’t changed it yet.

ESPEasy ser2net settings:

And from my custom component in HA I use socket://<IP:PORT>, i.e. socket://192.168.1.100:9265 to connect to my HP through ser2net.

Since you already have rpi connected to HP maybe try running ser2net on rpi?

Best regards,
Boris

P.S. Adding my initial HP setup for reference.

More info New binding - Rego 6xx based heat pumps - #132 by crnjan - Bindings - openHAB Community

Hi Boris

What a great idea!
And it works!!!
I just went with the most basic settings of “ser2net”:
connection: &con00
accepter: tcp,9500
connector: serialdev,/dev/ttyUSB0,19200n81,local

I will keep you posted with my experiences and suggestions

Great to hear you got it working!

I noticed in your screenshot that the operating hours value was negative. This has been corrected in release 0.0.2, so if you update to the latest version, it should now display the correct positive values.

You might also consider adding the following options to your ser2net configuration to avoid potential conflicts if multiple clients try to connect at the same time:

options:
  max-connections: 1
  kickolduser: true

This ensures that only one client can access the serial interface at a time, and if a new client connects, it cleanly replaces the existing one.

Thanks again for testing — looking forward to your feedback!

Hi Boris,

Thanks for the tip with ser2net.

Regarding the values, there were no error. When they installed the system they had a date misconfiguration and when i corrected it 9 years later when i bought the house it messed up the counters, but i haven’t figured out how to reset them. They are also messed up on the Rego user panel.

I was referring to


which should never be negative (heat pump operating hours).

The issue was caused by the values being processed as signed 16-bit integers. I didn’t notice it during testing since my heat pump currently has “only” 29,679 hours, which still fits within the int16 range. Once the value exceeds that range it would be displayed as negative.

This is now fixed — operating hours are handled as unsigned 16-bit integers.