Nibe Heat Pump - modbus TCP connection fails S2125 + VVM S320

Configuration
1

I have tried to use the Nibe Heat Pump integration in my HA. Integration: Nibe Heat Pump
However, when I try to configure the integration it fails with the message “Error on read request from pump. Verify your Remote Read Port or Remote address”.

Here are the details:
Nibe S2125 + VVM S320 (I have seen other users report that this combination works with this integration when selecting S2125 in the configuration in HA.)
The heat pump is connected to our wireless network in the same subnet as my HA installation. In the same room, I have a Huawei Solar system which is connected to the same network and works fine with modbus - hence I believe this is not a network issue but more a question on pump configuration.

Modbus TCP is enabled in menu 7.5.9
Is anything else needed on the pump? e.g. menu 7.5.9.1 Modbus ext. calc. supply or 7.5.9.2 Modbus ext. sensor input ?
While browsing the menus, I also found menu 7.5.12 Modbus PV - should that be enabled?
I am hesitant to blindly enabling or disabling stuff as I have no clue what they are doing.

In the Nibe Heat Pump integration configuration I use the following settings:
Model of Heat Pump: S2125
Modbus URL: tcp://10.20.30.4:502 (HA is running on 10.20.30.11 and I can ping the pump.)
Modbus Unit Identifier: 0 (I have also tried 1 just for the sake of it).

Unfortunately, when clicking the Send button, it fails with the above error message after a few seconds.

As I mentioned, our Huawei Solar system is running on the same network, also connecting to HA using modbus TCP with no issues at all. This makes me believe there is something on the pump that needs to be configured as opposed to a network error.

The guide at Nibe Heat Pump - Home Assistant does not mention any modifications to configuration.yaml to make this work. Are anything needed there to get the connection to work?

When I use the Nibe MyUplink app on my phone, I have full access to the pump. Again, pointing to no network errors.

HA version is:
Core 2023.12.4
Supervisor: 2023.12
Operating System: 11.2
Frontend: 20231208.2

Any help is appreciated. Thank you in advance.

/Simon

2

I have the same hardware, and mine works fine. From what I remember I used the same setup as you. I can verify this, it it might take some time.

Before I used the integration i used the yaml-modbus functions(If the integration does not work you can try this)

modbus:
  - name: Nibe
    type: tcp
    host: 10.0.0.140
    port: 502
    retries: 3
    timeout: 14
    switches:
      - name: "nibe - Extra varmvatten"
        write_type: holding
        address: 697
        slave: 1
        command_on: 3
        command_off: 0

    sensors:
      #1
      - name: "nibe_utetemperatur_bt1"
        #Denna sensor sitter på yttervägg
        unique_id: nibe_utetemperatur_bt1
        device_class: temperature
        unit_of_measurement: "°C"
        state_class: measurement
        data_type: int16
        address: 1
        slave: 1
        precision: 1
        input_type: input
        scale: 0.1
        scan_interval: 60
3

So i have checked my settings on the S320.
7.5.9 modbus enabled
7.5.9.1 off
7.5.9.2 all off

Wifi connected.

Nothing else related is activated, as far as I can judge.

As for Modbus Unit Identifier, I do not know were I can see my installed setting, but I believe I used the defult, as I remember was 0.

1 Like
4

Thank you very much for your reply and for checking your settings. Strange that I cannot get this to work. I will probably have to reach out to Nibe and see if they can assist.
Appreciate your feedback.

6

Hi,

I have a very similar problem. I used to have a working Nibe integration which stopped working. Disable/enable modbus setting in Nibe, restart unit, full power cycle neither brought back connectivity. it looks like modbus service is not listening on Nibe side at all so getting the same error message as you.

did you raise your issue to Nibe? did you receive answer?

thanks

1 Like
7

@grrr2 this is the answer I received from Nibe:
"It is quite correct that the modbus protocol uses port 502 for communication.

For example, if you try to communicate to ID 1, you would like to get back what BT 1 reports (outside temperature) which has a size of s16."

Unfortunately this does not help me at all, but perhaps it means something to you?
If you make any progress I would appreciate if you share results.
Thanks.

/Simon

8

Hello,
last week I get my Nibe S2125 together with the VVM S320.

Implementing in HA I have the same problem like user @sgatke and @grrr2 …
With a hand-implemenation with modbus like OscarHaraldsson reported it worked :slight_smile: [I actual use 13 reasonable registers]
… but finding all registers was little terrible:
not all documented register worked and other register I missed !! → like ‘power consumption’ …
→ so I’m still looking for a good implementation or/and for a good and actual modbus register documentation …
If someone has any hint for that, it would be fine :-).

Thanks, Clemens.

9

Similar issue here. I updated our S1155 heat pump this weekend to version 3.4.11 and all automatisations stopped working. Modbus is activated in the heat pump settings.

10

Don’t have that pump but it seems that the register map is freely available:

https://assetstore.nibe.se/hcms/v2.3/entity/document/878103/storage/ODc4MTAzLzAvbWFzdGVy

11

…yes … document is available … but:
in my setup S2125 + VVM S320: some register does not work :frowning: as described and other important are missing in this document. :frowning:
In beetween I have ‘combined’ multiple documents find in the net and tested with my setup … and now have a resonable setup working …