Modbus mapping according documentation?

[MathieuDmbc]

Hello, I am trying to integrate the Stiebel eltron component into Home assistant, which is based -if I am right- on the pystiebeleltron library.
Looking into the file "pystiebeleltron.py" and comparing the parameters mapping against the Stiebel documentationn it seems to me that the Modbus addresses are not aligned, could you please check and confirm @fucm ?

Thanks a lot for your support and feedback!

Stiebel Modbus Manual

Example to illustrate

Parameter "OPERATING MODE" is acc to the documentation at address 1501.
But in the source code I see that it seems to be mapped differently: OPERATING_MODE': {'addr': 1000, 'type': 8, 'value': 0}

Note

It could be I have overseen something, so please check and advice me :)

[fucm]

The address mapping should actually be correct for the type "Lüftungsintegralgerät" / "integral ventilation units", see page 13/34: BETRIEBSART/OPERATING MODE. The address is shifted by 1. So, 1001 address in the manual relates to 1000 in the module.

Do you have a different device?

I can't maintain the module anymore (checkout the reason here: https://community.home-assistant.io/t/is-there-any-interest-in-a-stiebel-eltron-climate-platform/65628/34). It would actually be great, if someone else can take over the maintenance of the python-stiebel-eltron library. Any interests?

[MathieuDmbc]

Hello Martin, Thanks a lot for your quick answer!
Yes I do actually have a different device (HPA-O family) and I have tested the Modbus TCP communication with a Modbus Master. This device answers to the parameters from the section described as "Heat pumps with WPM".

As far as I see, there is no way foreseen to handle this second variant of devices.

Regarding update/maintenance of the lib, since I am beginner in Python, I would be ok to fill/maintain this different parameter mapping, but it would be great if you could help/advice me to create the skeleton to handle the two types of devices without breaking the compatibilty for existing users?

Another way could be that I create a non generic custom version on my side and also a custom Home Asssitant Stiebel Eltron integration .

[fucm]

It is not required to create a copy or a non generic custom version to support further models. All what you would need to do is adding an additional paramater to the constructor of the StiebelEltronAPI (see how it is used for the tests). It would default to the current binding and if provided, would select your binding. The address definitions could be moved into a new file, just to keep the structure clean. This would allow extension with further types (if there are more).

You could create a fork of my repo, integrate the changes and create a pull request. Before merging I would need to fix the unit tests, which are not green since a while. If you want to try it, I will fix the unit test. Please let me know.

[fucm]

Just asking back, are you working to get your WPM system integrated? Should I fix the unit tests?

I did spot register 5002, which seems to define the "Reglerkennung". It could potentially be used to differentiate the two sets of register automatically (to avoid a manual selection required by the user).

[LinusHoppe]

To continue this: I could offer help by mapping/testing at least my device. I have a "Heat pump with WPM" like @MathieuDmbc (WPL-A 07 HK 230 Premium).

Would love to see the binding seperation implemented and the unit tests fixed. According to the Modbus Manual, there are only two different types of mappings (Heat pump with WPM and Ventilation integral unit), so a mapping should not be necessary for every new device.
Register 5002 "Reglerkennung" seems indeed to be a good approach to deal with these two different types without any configuration needed.

[Nippey]

Hey, for other coming here with the same issue:
I checked the available forks and I think @cool2bdave did already all the work:
https://github.com/cool2bdave/python-stiebel-eltron

I have a "Tecalor THZ 5.5 eco" and it does fit my registers.

--Nippey

[fucm]

@Nippey Thanks for the comment!

@cool2bdave (not sure, if you get this message) Would you be willing to take over the ownership of this python module and integrate an update into home assistant?

[brechtvhb]

Hi guys,

I would also like to control my WPF4 with home assistant. How can I use the branch of cool2bdave to make this possible?

[Padanian]

Hi, guys, this is Alex from Stiebel Eltron, I am the after sales manager in Italy. I'd like to get hold of all of your efforts and get at the end of this implementation. Is there anything I can do to help or how to manage the project?

[fucm]

@Padanian I did respond via mail.