Nibe integration: can't enable "SG Ready requested operating mode" entity

I've been using the Nibe integration with my S1256 and it's working great. Now I wanted to make use of the SG READY function which recently became writable through modbus instead of just aux inputs. As far as I can tell, this involves enabling the "SG ready via API" switch in holding register 3032 and then setting the actual mode using register 6008.

Both these entities are available but disabled in my integration. I could enable 3032 and also write to it, and its status is confirmed on the display on the unit. However, when I attempt to enable register 6008, it immediately flips back to disabled.

Both of the registers exist in the export of the modbus registers I get from the unit.

Do you have sg ready working? I activated the entities in ha and activated the api but sg ready input a and b are unavailable and operating mode I can’t switch:

My heat pump just updated its firmware and now I’m happy to say that if I do not configure any physical inputs for the SG_READY functions, I now appear to be able to toggle the “activate sg ready via API” switch from home assistant and then set “requested operating mode SG ready” to change the mode. It did not work previously.

Good to hear, but how do you set the mode precisely? And what is the firmware version of your nibe?

The entity for me is number.requested_operating_mode_sg_ready_46009. You set that to 0-3 for high price/normal/low price/free electricity modes. I think you need “activate via api” enabled, but it looks like you already have that.

The firmware is 4.12.8, it’s an S1256.

I have the same version on my s1155 heat pump but I have no entity with the name number.requested_operating_mode_sg_ready_46009 that I can enable in the integration.
I am running ha 2026.8.3, if I search on the number I find these:

I’m not sure if those numbers are persistent or random. If you search the entities named “SG” for the nibe integration, what do you see?

Only these:

Interesting, I guess yours doesn’t support this functionality then.

As far as I know it should but I will create a ticket, maybe the entity should be added for the s1155