Nibe Integration

[Simon-004]

The problem

I havent been able to communicate with my Nibe S1255 heat pump for several months. Thers was a bug in March, it got fixed quickly. But about a month later it broke again.

I don't know if the issue is local or with the integation. sometimes a bit of data leeks through, but in general nothing works. can't read or adjust anything.

I have tried removing and reconfiguring. I can find and set up my heat pump but can't pull any sensor data. everything is unavailable.

What version of Home Assistant Core has the issue?

2023.9.3

What was the last working version of Home Assistant Core?

2023.3.4 / 2023.3.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Nibe Heat Pump

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nibe_heatpump

Diagnostics information

home-assistant_nibe_heatpump_2023-09-25T12-47-06.041Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration (nibe_heatpump) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `nibe_heatpump` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign nibe_heatpump` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

nibe_heatpump documentation nibe_heatpump source _{^{(message by IssueLinks)}}

[jafhueppe]

Same problem for me with a Nibe VVM S320. It stopped working a while ago. I tried to readd it via the device panel, but the overlay throws an error with no further information what error occured.

The protocol view within home assistant shows no also no errors.

I run the same ha version as @Simon-004, but it stopped working with HA 2023.9.1

I can reach the heatpump by modbus - tested it with a desktop client

[jafhueppe]

I have some new information on this: I'm using HA with the docker container. I can't ping oder access the heatpump via ping or modbus_cli (installed via pip).

If i use the mac Terminal with the same tools, I can get an answer from the heatpump

[elupus]

@Simon-004 Can you check on your pump what the temperature settings are for hot water production? It seems your pump is responding with 2 degrees, which is out of range. So either we are reading the wrong field or something else is going wrong.

You can likely disable the water heater entity + any enabled hot water production entities to get it run again.

[Simon-004]

@elupus, Strange. Hot water temperature is currently about 22 degrees. I am only using the heat pump for central heating. Two degrees is way out of range. Can't see how it would be possible for any sensor to give a reading this low at this time of year. Tried disabling any entity associated with "hot water". Seems to solve the problem, I am getting readings from my heat pump again. Thanks a lot! :)

[elupus]

The value I was looking for was start temperature set for HW production. Would be nice if you could check those settings on your pump.

[Simon-004]

@elupus You are correct! It has a set value of 2 deg. (same value for low, medium and high demand)

[elupus]

Ok.. weird :). That is less than expected minimum value. Will have to check how to handle.

[Auke78]

When i install the intergration i only get the buffer temp, all athor entities are disabled by the integration. Is there anyone who knows what my problem is? I've got an S2125 in my LAN network. With NodeRed on Hass i can get info by modbus. But the entities of this Integration won't give values.

[elupus]

Most are disabled by default. Only specific climate zones and heater entities are enabled by default. There are just too many to enable them all.

[Auke78]

Ik had only 2 enabled.. before I had modbus connection by my own in the config file. This connection is also not working at the moment. And with Node red i can get the info.. so strange. Could it be an Hass problem?

Op do 19 okt. 2023 om 21:02 schreef Joakim Plate @.***>

Most are disabled by default. Only specific climate zones and heater entities are enabled by default. There are just too many to enable them all.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/100852#issuecomment-1771551069, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT7UW7Y3K6ZFU7THR4FONWTYAF2K3AVCNFSM6AAAAAA5GBH5KSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZRGU2TCMBWHE . You are receiving this because you commented.Message ID: @.***>

[elupus]

Its not a problem. Just enable the ones you need.

[KlausHans]

Its not a problem. Just enable the ones you need.

How do i do this? And maybe this should be mentioned on the integration documentation. :) I have the same problem like @Auke78.

[KlausHans]

Ah, found it. You have to click on the entities link in the the main screen of the integration. Then tick the ones needed an acivate them.

[Auke78]

Yes, I found it also at that way, you need to activate them. This action isn't discribed by the Integration..

[elupus]

I'm going to close this issue. The problem seen have been found. I don't think we can do much about the strange range values for sensors. They should not break other sensors now.