Nibe F1155 via modbus

[panosnl]

I have a Nibe F1155 connected to HA via modbus. This means I have all Nibe parameters available.

I currently only update curve offset based on Temp and Solar forecast + 5 hrs.

Your approach seems very interesting.

However I cannot link all sensors needed for this integration since it seems to take it from somewhere else (I selected S1155)

Happy to try it in NL.

[enoch85]

Nice with some more users! 🚀

I only developed this for myself but made the code base with more models in mind. Would love to integrate more pumps and make it stable. 👍🏼

So what are you missing exactly, and do you have any debug logs?

[panosnl]

SInce I don't use Nibe uplink the integration has none of the Nibe sensors/switches it needs .

Maybe a simple translation table or yaml linking between nibe modbus sensors and Uplink sensors would work.
Maybe it would already work by defining new template sensors that simulate the required uplink sensors. For that I need the list that the integration is trying to fetch.
I have not looked into the code yet to find out myself.

Furthermore the entities that can be specified in the config like degree minutes cannot be entered since it expectect a sensor while I have it as a number. this also can be solved with a template.

I don't have debug logging enabled but I did find this in the loggin:
DHW sensor (BT7) not found - check MyUplink integration has exposed BT7/40013 sensor

[enoch85]

Aah, I missed that detail.

Yeah, MyUplink is needed. But if you can figure out a way to translate to Modbus, or implement an adapter to make it happen - I'm all ears! 👍

[panosnl]

I had a quick look in the code. I see the integration searches for entities using wildcards..

If that is the case it should also detect my entities correctly, eg: sensor.bt1_outdoor_temperature_40004_2

Or is it an AND query where _bt1 failed?

    # Search for NIBE entities
    # Patterns based on NIBE Myuplink integration entity naming
    # Use specific entity names from parameter IDs when possible
    # CRITICAL: Use word boundaries (_btX, btX_) to prevent substring matches
    # e.g., "bt6" would match "bt63", "bt1" would match "bt10", etc.
    # This ensures we match the exact sensor, not similar named sensors
    patterns = {
        "outdoor_temp": ["_bt1", "bt1_", "outdoor_temp", "40004"],  # BT1 / param 40004
        "supply_temp": [
            "_bt25",
            "bt25_",
            "_bt63",
            "bt63_",

[enoch85]

I've been working on a fix for adding Modbus support today.

I think it will be ready tomorrow, maybe.

[panosnl]

That would be great!

With Modbus I assusme you mean the NIBE Integration https://www.home-assistant.io/integrations/nibe_heatpump/

The registers for F1155/1255 are descibed here: https://github.com/yozik04/nibe/blob/master/nibe/data/f1155_f1255.csv

[enoch85]

@panosnl Please test the latest release!

https://github.com/enoch85/EffektGuard/releases/tag/v0.5.0-beta.1

[enoch85]

@panosnl So did it work?

[panosnl]

Thanks for the effort!! Sorry for my late reply.

Below my feedback a summary.

Sensors:

• Current Electricity price seems fixed at 1 eur/kwh.. Nordpool NL region is needed for me.
• Current Offset seems to change over time. Should it also copy the value to Nibe Curve offset? Also my curve ofset is number entity: number.heat_offset_s1_47011
• Estimatie Monthly saving is in SEK

Diagnose:

• degree minutes is 0. heating is off.. when I set DM in NIBE to -100 nothing changes.
  again a number entity: number.degree_minutes_16_bit_43005
• Nibe Power is unknown..

All other sensors seem to load OK!

I have some questions:
I understand that heating optimization can control the curve offset.
How does the thermostat work? I currently only run heating curve + offset.

HW seems to be addressed differently.
My Nibe has 3 HW modes: Economy, Normal and Luxury (and Smart)
Each mode has its own start and end setpoint temperatures.
Direct luxury mode can be triggered for: off, 1x, 3, 6 and 12 hrs
Then there is a High power mode which does try to heat as quick as possible.

Not sure how the intergration will control HW since I saw enties for setpoints and times