NIBE Uplink API component (non S-series)

foxlees · July 23, 2019, 6:43am

I am using the standard as below

nibe:
** systems:**
** - system: ef98a60eccc34dd69ba1e53e5353c529**
** units:**
** - unit: 0**
** climates: True**
** water_heaters: True**

Also getting this in my notifications:

Invalid nibe config
No systems selected, please configure one system id of:

[
** {**
** “systemId”: 74534,**
** “name”: “SMO 20”,**
** “productName”: “NIBE SMO 20”,**
** “productImage”: {**
** “name”: “NIBE_SMO_20multi”,**
** “sizes”: [**
** {**
** “width”: 75,**
** “height”: 100,**
** “url”: “/Content/Products/SMO20_75x100.png”**
** }**
** ]**
** },**
** “securityLevel”: “ADMIN”,**
** “serialNumber”: “06722419036271”,**
** “lastActivityDate”: “2019-07-22T23:07:51Z”,**
** “connectionStatus”: “ONLINE”,**
** “address”: {**
** “addressLine1”: null,**
** “addressLine2”: null,**
** “postalCode”: null,**
** “city”: null,**
** “region”: null,**
** “country”: “UNKNOWN”**
** },**
** “hasAlarmed”: false**
** }**
]

elupus · July 23, 2019, 7:26am

Change the system tag to: 74534. It should be the id, not a guid.

foxlees · July 23, 2019, 8:10am

Thankyou, that is working now, so where does the tag come from is tis in the NIBE website when adding the application?

are there any other tricks I need to know for adding the other sensors and controls do I just add the script as per the sample in the readme file

elupus · July 23, 2019, 8:52am

“tag”?? I don’t know what that is.

No real tricks.

foxlees · July 23, 2019, 9:05am

sorry meant system Tag ie in my case 74534, reading through the forum above I see that out is in the URL once logged into NIBE Uplink site.

still trying to work out what units and categories I can use, I have also now paid for the subscription so should be able to control the unit via hA , just need to work out how to configure it.

Vennerberg · August 16, 2019, 8:52am

24 days since last post… is this still up to date and worked on?

elupus · August 16, 2019, 9:37am

Not much new work. Not fully sure what to do . But it is up to date.

Vennerberg · August 16, 2019, 1:48pm

Maybe make it an official component of Home Assistant?

elupus · August 16, 2019, 2:19pm

Yup. That is planned. I got my simpler component in (arcam mediaplayer). So I might dare now :). Likely some functionality will be lost. Like grouping of sensors.

rabbadab · August 26, 2019, 7:30am

If it’s hard to add as a official component maybe it could be added to the HACS so it’s easy to install and update?

elupus · August 26, 2019, 8:04am

In regards to HACS. I’m awaiting this: https://github.com/custom-components/hacs/issues/402

But I’m at least starting the process of getting it mainline.

delabrava · September 8, 2019, 6:52pm

Is there any one else having problems with NIBE uplink at the moment?

Neither my Home Assistant or NIBE Uplink phone app can connect right now.

Or is it just me?

elupus · September 8, 2019, 7:07pm

They were doing maintenance earlier today. Always check www.nibeuplink.com. Usually there is a red small text before logging in about maintenance.

delabrava · September 14, 2019, 2:57pm

Finally it got cold outside this night, enough for the heat pump to kick in to start producing some hot water for the radiators.

Unfortunately I woke up to a very hot house which seem to be related to the smart thermostat enabled through the Nibe integration. The hotter it got inside, the hotter the water supply(EB100-BT61) for the radiator got.

Seems like the smart thermostat adjustment of the heat curve were working the opposite way. When the supply water had reached 49 degrees celcius(which is equivalent to a outside temperature of -27c according to heat curve) I disabled the smart thermostat in the heatpump and it immediately stopped producing hot water for the radiators.

Have any one else had this problem and could it be related to the HA integration and/or some settings in the heatpump?

elupus · September 14, 2019, 7:50pm

Did your smart termostat actual temperature fail to rise when it got hot inside? Your smart temp actual temp will be the one controlling heating.

delabrava · September 14, 2019, 8:30pm

Don’t think so, that’s BT50 right?

The set value was 20.5 degrees.

At 07:05 the thermostat reported 20.9 degrees.
At 09:06 it reported 22.4 degrees and hot water supply was at that point 47.8, and that’s point where I decided to deactivate the smart thermostat adjustment.

The allowed compressor frequency also kept on raising the hotter it got.

elupus · September 14, 2019, 8:48pm

Bt50 would be your real temp sensor. I’m talking about the one you linked to your smart termostat. Bt50 will be ignored when a smart termostat is active.

delabrava · September 15, 2019, 8:11am

I have no “real” indoor temp sensor, BT50 is the smart thermostat. If I disable the smart home option on the heatpump then BT50 gets unavaliable.

Another thing I noticed is that calculated flow temp. goes up to 57 degrees and lies flat there when the temperature adjustement is enabled. This behaviour started on the 9th of sept, the same time as I upgraded to latest hass.io and latest Nibe component.

elupus · September 15, 2019, 9:46am

Odd. Can you log into nibeuplink.com when smart temperature sensor is active and check what values it shows for your smart temperature?

delabrava · September 15, 2019, 10:16am

The values at nibeuplink.com is(currently) OK, and also the calculated flow temp.

I disabled the climate entity for the smart thermostat and did a service call(nibe.set_thermostat) from the developers options, just to verify the readings on the heat pump(which where OK then).
After that I enabled the entity again and also the thermostat adjustment on the heat pump, and now the calculated flow temp is more reasonable and doesn’t stay flat at 57 degrees.
Don’t know why it looks better now.

What are the differences between the operating modes?
I noticed that in “Automatisk” the set values doesn’t update at nibeuplink when it’s changed in HA, only on reboot, but in “Värme/Kyla” it works.