Welcome to weishaupt_modbus Discussions!

[OStrama]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[edlestau]

Hi OStrama.
Thanks for sharing this integration!
I will try it next time.

[maddinhome]

Hi OStrama,

thank you for sharing this integration!

I try it and it works fine for me.

keep going.....

[OStrama]

Thanks! What type of heatpump do you use?

[maddinhome]

It is a WSB 8-A-RME-AI that was installed in February 2024.

[maddinhome]

Just for information, in order for the query via Modbus to work, the heat pump must be restarted.

Modbus can be activated in the WEMPortal, but no IP addresses can be entered.
The IP address can only be entered via the control panel of the heat pump in the expert menu.
Of course, Modbus can also be activated in this menu in the control panel.

Edit:

You should perhaps point out that the IP of Homeassistant should be entered for it to work...I don't think that's really clear to everyone. Homeassistant serves as a client and therefore has to be entered in the IP mask.

[maddinhome]

Hello, I have created a small visualization for the heating curve and the dashboard:

`type: history-graph
entities:

• entity: sensor.aussentemperatur
• entity: sensor.vorlaufsolltemperatur
  hours_to_show: 48
  title: Heizkurve
  logarithmic_scale: true
  `

If you have the "mini-graph-card" integration you can also use this:

`type: custom:mini-graph-card
entities:

• entity: sensor.vorlaufsolltemperatur
  name: Vorlaufsolltemperatur
• entity: sensor.vorlauftemperatur
  name: Tatsächliche Vorlauftemperatur
• entity: sensor.aussentemperatur
  name: Außentemperatur
  name: Heizkurve Wärmepumpe
  hours_to_show: 24
  line_width: 2
  show:
  fill: false`

If you change the heating curve, the visualization adapts. But it takes a few minutes. Perhaps you could speed it up so that the effect is immediately visible.

Unfortunately, I don't have an external device and sensors, e.g. in the living room from the heat pump, like you obviously have. Then you could also display the target indoor temperature.

I had to remove your living room sensors from the sample dashboard.

Have a nice day and greetings

[MadOne]

An update of the entity should not take minutes. If you change it in HA it should be insant.
This may be the update time of the chart?!?

[thetschulian]

Hello, thank you for this great integration.
I own a WBB20 since 10 days.

Some of my values / entities do not reflect the real "values" if I check the control panel for example
Betriebsstunden E1 = 76 hour but this "Betriebsstunden" are "Schaltspiele" on the control panel.

I am very new to modbus and even home assistant so I'll maybe ask some dumb questions.

[OStrama]

Done in next Version ;-) I assume that the 2nd. Schaltspiele refers to E2? (It is zero in my heatpump, so I cannot confirm..)

[thetschulian]

yeah this should be E2.

[OStrama]

Thanks for the info! I‘ll update the name in the next release.

Since all the modbus addresses, names and values are collected from different sources, any hints for modifying and adding them are very welcome! This helps all of us to make this more complete..

[thetschulian]

Well, since I dont know how to compare the modbus addresses yet, I will provide some screenshots of my WBB20 control panel and my homeassistant values. hopefully this helps.

[OStrama]

Could you please test the 0.0.8pre5? It contains HK2..

[chriscom2020]

Hi OStrama, thanks for your work. I have the following question: Is Volumenstrom not readable? It shows always the same number (never changing). See attached screenshot.
Thanks for Input!

[john92648]

Another Question to the Volumenstrom. In the WEP Portal Integration Ist_Volumenstrom was availible, is it possible to get it also in this Integration? and maybe the RPM of the Kompressor?
Regards John

[MadOne]

Currently not, as this is not available through modbus. But we are working on integration of the local Webinterface. This provides these values.

[john92648]

Thanks for quick answer. BTW I have the Pump configered to Volumenstrom, but the Entität Volumenstrom Heizen kann not be adjusted. Actuel I have 1400l/h.

and the Entität shows me 2.360 l/h

[OStrama]

It‘s an input value when you use pump control method „Volumenstrom“
I also would need the current value but afaik it‘s not available.
BTW: Some of these entries in principle are writable, but I decided to make them read only to prevent undefined situations..

[MadOne]

Should we rename them to "Sollwert Volumenstrom Heizen) for clarification?

[chriscom2020]

Thanks for the information. A rename to "Sollwert Volumenstrom" is a good idea!

[OStrama]

Yes, makes sense!

[faulesocke85]

Thanks for creating this integration!

Question: Is it possible to get "Vorlauf- und Rücklauftemperatur" of HK1 and HK2? Or is it implemented with e.g. address 31106 which results to value "1?" in my setup?

I am Running an WBB LB 20 AR.

Thanks a lot

[MadOne]

Hi,

we have "Heizkreis Vorlauftemperatur" (31 105). But at least i have no sensor installed for that. It should not show up if you dont have this sensor installed.
The documentation we have shows now register for "Heizkreis Rücklauftemperatur" but we found the undocumented register you metioned. 31106. This one is always 0 for me.

Are you sure you have a sensor for heizkreis vorlauf and rücklauf? Can you see this values anywhere? WEM Portal, at device, web interface?

[OStrama]

If the register only shows values like 0, 1 or so, it‘s perhaps a status or a configuration but no measurement value..
I also do not have this value afaik (not at home currently, so I cannot check)

[chriscom2020]

Hi @OStrama, I have already experimented with the connection and reading of data from the WEM local web server and found that the web server is very slightly overloaded and then no longer reacts or does not release any more data. Did you also have this experience and how do you deal with it? I would be happy about a short exchange...

[MadOne]

Hello everyone.

Just as a note, in case this is not known: erickastel has created an integration “Weishaupt WEM Portal” and currently has big problems to retrieve data from Weishaupt via API and/or web, because Weishaupt blocks the access partially.
Perhaps you should contact him to coordinate with him on this matter?

We are talking about the local Webinterface not the wem portal / api the integration you mentioned is using.

[chriscom2020]

Here is my volumenstrom.py as reference...
volumenstrom_request.py.txt

[MadOne]

You are doing a login every time you run the script (every minute). This is what i suspected to stress the server.

We are creating a session and save the cookie. So we stay loggedin and only have to login once or when the cookie expires.

[chriscom2020]

I think the way you're doing it is definitely better.

[MadOne]

I hope it is enough to not kill the server

[john92648]

Hi all, do you try

to get this value (Volumenstrom) ?

[MadOne]

@john92648 yes.