NIBE Uplink API component (non S-series)

Feature Requests
565

I have my pool heated by the NIBE system, and I wanted to control the temperature and compressor frequency based on weather and electricity price. However, those values appears to not be possible to change in the current integration (parameters 48090, 48092 and 48287). Is this not possible to do through the API, or has it just not been considered?

566

I doubt it’s possible. Some parameters are changeable, but most aren’t. You can check on api.nibeuplink.com in the docs section. There it lists some controllable parameters, but might be others.

567

I think you are right. I played around with postman, and it doesn’t seem to be possible to set those parameters. That’s a bummer.

568

I contacted Nibe support and they were quite helpfull. They shared an updated modbus parameter list (pm me if interested) containing register 116: Average temp. klim. system room 1 (BT50). This register holds the current temperature of the RMU S40 thermostat. :tada:

569

Haha, I did the same lately - contacted support in NL and they gave the same register. Didn’t have the time yet to post it in here.

However they couldn’t tell me the humidity register. Did you maybe got that?

570

Does anyone else have slow startup times with hass_nibe?
Mine is over 120 seconds (2 minutes) on a RPi3

image
image1229×122 32.3 KB

571

It is as expected. I suppose i should not update on startup.

572

Hi, I saw there was an update of the NIBE component to align with the new update and sensor attributes. Many thanks for all the efforts on this component!
I see that one of my Nibe sensor (outside temperature) apparently is not yet converted? Some are available to use in the new Statistical Chart, however the Nibe outside temperature isn’t for me.
Many thanks

573

It needs a device class set too. I have not figured out a good way to set that yet.

You can use customize feature of home assistant to set it’s device class to temperature for now.

574

That’s an easy workaround and it works now.
Many thanks!

575

Another rookie here trying to get this integration to work.
I have an SMO20 & F2040. I’ve managed to successfully install the integration and authenticate etc.
On the integration page I get just 3 entities. ‘Hot Water’, ‘S1 Room’, ‘S1 Supply’
I have read all of the thread above and have added the following into my configuration.yaml

nibe:
  systems:
    - system: XXXXX
      climates: True
      water_heaters: True
      sensors: True
      units:
        - unit: 0
          categories: True
          statuses: True
        - unit: 1
          categories: True
          statuses: True

I have tried re-booting, however I only ever seem to get the 3 entities, and no other sensors.
In addition, if I add a thermostat card to this and I change a setting it reverts to previous after a few seconds. (I have paid for NIBE Uplink)

Where am I going wrong, I’m sure I’m missing something simple!

576

And that XXXXX is your real system identifier, ie a number?

577

Yes correct a 5 digit number that I have taken from the URL from NIBEUplink.com

579

Any errors in log?

580

Your config is not correct according to current docs. There should be no climates:, water_heaters:, sensors:, see: GitHub - elupus/hass_nibe: Home Assistant Nibe Uplink Integration

581

I`ve got the same problem, did you find a solution to this?

582

Thanks Elupus.
I updated my config yesterday. Nothing changed immediately however today I opened up Home Assistant to see I now have 47 entities!

583

Since update rates are limited. It takes a long time to get all sensors after a restart.

584

That makes sense thanks for all your efforts on this integration! Its way beyond my technical ability.

Do you think you’ll be able to update the component so that the new statistics graph card can pull the history in the future?

585

At some point yes. You can fix it using customize feature of home assistance and setting a state_class for the variables you want statistics for.

2 Likes