Different Parameter ID being used for Priority entity

[Tommatheussen]

I've been running ESPHome Nibe for a while, and recently was looking at cleaning up and making my dashboards nicer.
I found that my heatpump is using a different parameter ID for the Priority entity, in Home Assistant I can only see it switching between OFF and HOT WATER. This also has the implication that my climate entity is always in the 'Idle' state, which is actually what I'm wanting to use now.

In Home Assistant, the entity has the entity id as sensor.prio_43086, which also correspond to the JSON/CSV file in this repo (https://github.com/yozik04/nibe/blob/master/nibe/data/f1145_f1245.json#L3944). However, when I look at MyUplink, I see parameter ID 49994 is used for the priority.

For reference, my heatpump is a F1245(PC), running the latest firmware (9714R2). I have it connect to MyUplink (previously NibeUplink, don't remember when I switched over, neither do I remember if it was actually correct or not). Could this have changed with a firmware update of the heatpump (I see no mentions of this in their release notes)?

I can try to grab a new parameter CSV file from the heatpump later and compare it against the one that exists here. Is there any way to override the parameter ID being used for the entities?

[elupus]

It could have changed. We dont have any updates apart from the csv from modbusmanager from nibe. No other docs exist as far as i know for the F series pumps.

[Tommatheussen]

Thanks for the confirmation!

I just went to check back in my history of the Priority sensor, and it seems the HEAT status does come through properly, it's just the cooling that's not recognized. Is there a way to view the raw value from the coil that's returning the data? Maybe it's returning a wrong value and then being mapped to OFF instead.

[Tommatheussen]

I made a quick script to check the values, and I received this (while verifying it was in cooling mode):

DEBUG:nibe.nibe.connection.nibegw:Received 5c00206a064ea80a000a00aa from ('192.168.150.103', 9999)
DEBUG:nibe.nibe.connection.nibegw:Container: 
    address = (enum) MODBUS40 32
    cmd = (enum) MODBUS_READ_RESP 106
    data = Container: 
        coil_address = 43086
        value = b'\n\x00\n\x00' (total 4)

So it seems my heatpump is just reporting it wrong? Maybe it can't report passive cooling or something

[Tommatheussen]

I have done a little bit more digging, and it seems I have another sensor, called binary_sensor.status_cooling_43024, which indicates whether the heatpump is actually cooling or not, this also seems to reflect the status in MyUplink.
I have not clue why the Priority entity does not reflect the cooling status, as mentioned, perhaps this is due to it being passive cooling, and thus the heatpump is not really doing anything, it's just pumping colder water through the pipes...

I will see if I can change the HA component code to take this sensor into account for the Climate entity

[yozik04]

In my F1255 I have installed Passive cooling 4-pipe (PCS) module. Which I am using to cool my ventilation supply air.

• When Cooling is active I think 43086 becomes "Cooling" (60), can't remember for sure. Can't check because temperatures are low and it won't turn on. What heat pump does in cooling mode - it just circulates brine water through ventilation heat exchanger by controlling 3-way valve to ensure target temperature of brine water is supplied.
• 43024 shows if cooling is on at the current moment. I use that for my automations.
• I also use 47372 to control if I enable heatpump to cool the house. I use manual mode to tell what heatpump can do cooling/heating/off.

[Tommatheussen]

Hmm ok, I wanted to continue using the automatic mode of the heatpump to determine if heating/cooling is allowed. It might be easier to go with HA controlled for better fine-grained control in the end.
That being said, I temporarily copied the Nibe integration and made it into a local custom component. In there I've included some logic to check the 43024 status, and apply the cooling status to the climate entity as well. If it's stable in my case I'll make a PR in the near future. Still strange that it's not showing the cooling status in 43086 for me, I guess it's based on configuration.