Registers list

[ludovic-steinbach]

@ced2git, thanks a lot for sharing your code, it has been very helpfuI. I've set it with homeassistant on a raspberry pi and it's perfect.

I have been able to identify a lot more registers. I am happy to add it to this repo for others to see. Would you have a preferred format?

[ced2git]

Hello, Please feel free to share or amend the code Format in a csv ? Envoyé d un smartphone...

…

Le 20 févr. 2021 à 18:28, ludovic-steinbach ***@***.***> a écrit :  @ced2git, thanks a lot for sharing your code, it has been very helpfuI. I've set it with homeassistant on a raspberry pi and it's prefect. I have been able to identify a lot more registers. I am happy to add it to this repo for others to see. Would you have a preferred format? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[ludovic-steinbach]

@ced2git; I got my hands on the Software provided by OEG and used a serial port monitor to check which registers the software is reading/writing.
Unfortunately the software does not actually do much, so there is not a lot more than what had been identified in the past, but happy to share the logs with you if you want

[ced2git]

Hello ludovic, I've been late to reply. Do you still have the logs ? I was really into looking on how to turn on/off the hot water circuit regards Cedric

…

On Fri, Nov 5, 2021 at 2:11 PM ludovic-steinbach ***@***.***> wrote: @ced2git <https://github.com/ced2git>; I got my hands on the Software provided by OEG and used a serial port monitor to check which registers the software is reading/writing. Unfortunately the software does not actually do much, so there is not a lot more than what had been identified in the past, but happy to share the logs with you if you want — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ4LNROZBJ4FSTDE6DG6GDUKPJYJANCNFSM4X6CJ2FA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[BasHJPeters]

Hi @ludovic-steinbach @ced2git,

First of all, thanks for the code!

Did one of you find extra sensors for the oeg_dict?
I'm searching for the value of the three-way valve.

Regards,
Bas

[ludovic-steinbach]

@ced2git, all I learned from monitoring the software is that it write to multiple registers simultaneously to operate it.

For example, switching everything off:

[04/11/2021 19:44:16] 
Modbus Request (COM5) 
Address: 128 
Function: 16 (0x10) - Write Multiple Registers 
    Starting Address: 6 
    Quantity: 18 
    Byte Count: 36 
    Values: 00 01 00 00 00 00 00 00 00 00 00 78 01 f4 02 bc 01 f4 01 f4 01 f4 01 f4 ff ff ff ff ff ff ff ff ff ff ff ff  
        Register6: 1 
        Register7: 0 
        Register8: 0 
        Register9: 0 
        Register10: 0 
        Register11: 120 
        Register12: 500 
        Register13: 700 
        Register14: 500 
        Register15: 500 
        Register16: 500 
        Register17: 500 
        Register18: 65535 
        Register19: 65535 
        Register20: 65535 
        Register21: 65535 
        Register22: 65535 
        Register23: 65535 
Checksum: 0x0040 - OK 
---------------------------------------------------------------------------------- 
[04/11/2021 19:44:17] 
Modbus Response (COM5) 
Address: 128 
Function: 16 (0x10) - Write Multiple Registers 
    Starting Address: 6 
    Quantity: 18 
Checksum: 0x0058 - OK 

When turning back on:

[04/11/2021 19:44:57] 
Modbus Request (COM5) 
Address: 128 
Function: 16 (0x10) - Write Multiple Registers 
    Starting Address: 6 
    Quantity: 18 
    Byte Count: 36 
    Values: 00 09 00 00 00 00 00 00 00 00 00 78 01 f4 02 bc 01 f4 01 f4 01 f4 01 f4 ff ff ff ff ff ff ff ff ff ff ff ff  
        Register6: 9 
        Register7: 0 
        Register8: 0 
        Register9: 0 
        Register10: 0 
        Register11: 120 
        Register12: 500 
        Register13: 700 
        Register14: 500 
        Register15: 500 
        Register16: 500 
        Register17: 500 
        Register18: 65535 
        Register19: 65535 
        Register20: 65535 
        Register21: 65535 
        Register22: 65535 
        Register23: 65535 
Checksum: 0x0038 - OK 
---------------------------------------------------------------------------------- 
[04/11/2021 19:44:58] 
Modbus Response (COM5) 
Address: 128 
Function: 16 (0x10) - Write Multiple Registers 
    Starting Address: 6 
    Quantity: 18 
Checksum: 0x0058 - OK 

The Software isn't particularly useful (if you're already monitoring temperatures)
I'll attache the full logs, where it also queries all of the parameters. It confirms the register ranges I had identified and added to the README in #3.
I've added rows to highlight where in the logs I did certain actions: search for "//COMMENT".
MonitoringOEG.txt

[ludovic-steinbach]

@BasHJPeters, from my experience, registers can represent different values, depending on your model and current hydraulic scheme. It is therefore a bit difficult to provide you with an useful answer.

Is the three-way valve controlled by the OEG controller? Can you manually turn it on/off via the screen? If that's the case, I suggest the following steps:

• plug the USB in the controller and your computer
• run a script that gets all the values for some registers (say 0-1000) and save it to file
• manually turn on/off via the controller interface
• rerun the script and save to file
• Compare the files

You might be able to identify which register represent the behavior you're trying to reproduce

[RobertDeserranno]

Is it possible to change 1 value in the register by using a py file? If so can you give me a example of changing register 12 (preset temp ) from 60 degrees tot 65 degrees;
thanks
robert

[ced2git]

Hello, yes it's possible with the command write_register.

`#!/usr/bin/env python3

x=12
value=65

import minimalmodbus
import serial
import csv
import time
import paho.mqtt.client as mqtt

from minimalmodbus import ModbusException
from minimalmodbus import NoResponseError

instrument = minimalmodbus.Instrument('/dev/ttyACM0', 128, minimalmodbus.MODE_ASCII) # port name, slave address (in decimal)
instrument.serial.baudrate = 9600 # Baud
instrument.serial.parity = serial.PARITY_EVEN
instrument.serial.bytesize = 7
instrument.serial.stopbits = 1
instrument.serial.timeout = 0.05 # seconds

localtime=time.asctime(time.localtime(time.time()))
file=open('chaudiere.csv', 'a')
writer= csv.writer(file)
print ("Register %d" %(x) , instrument.read_register (x, 1,3))
print localtime
writer.writerow( (x, instrument.read_register (x,0,3),localtime))

#instrument.write_register(x,value)

writer.writerow( (x, instrument.read_register (x,0,3),localtime))

print ("Register %d" %(x), "TimeOut")
file.close()`

unfortunately, i cannot test it anymore. I've replaced my heating with another system.

Try first to read the register and validate the value currently set then uncomment the instrument.write_register.

[Lota23]

Hello
it is possible to query this with Esphome Modbus. As in this .yaml
Thank you
Lorenz
esphome:
name: esphome-web-3e5f4c
friendly_name: ESPHomeHeizung
min_version: 2024.11.0
name_add_mac_suffix: false

esp32:
board: esp32dev
framework:
type: esp-idf

Enable logging

logger:

Enable Home Assistant API

api:

Allow Over-The-Air updates

ota:

• platform: esphome

wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password

uart:
id: mod_bus
tx_pin: 16
rx_pin: 17
baud_rate: 9600
stop_bits: 1
parity: even

modbus:
id: modbus_heidelberg_wallbox
#flow_control_pin: 4
send_wait_time: 200ms

modbus_controller:

• id: heidelberg_wallbox_id01
  address: 0x80
  modbus_id: modbus_heidelberg_wallbox
  command_throttle: 200ms
  setup_priority: -10
  update_interval: 10s

sensor:

• platform: wifi_signal
  name: "WiFi Signal ${devicename}"
  update_interval: 300s

• platform: modbus_controller
  modbus_controller_id: heidelberg_wallbox_id01
  id: version
  name: "Temperatur 1"
  address: 40
  register_type: read
  value_type: U_WORD

• platform: modbus_controller
  modbus_controller_id: heidelberg_wallbox_id01
  id: charg_state
  name: "Temperatur 2"
  address: 41
  register_type: read
  value_type: U_WORD