NIBE Uplink API component (non S-series)

Feature Requests
211

You are the geatest its working again have a nice day

212

I followed the instructions in the readme to the letter. But I am getting the following error. Can’t figure out how to fix it. Any help / guidance / tips would be greatly appreciated.

I am using HASSIO 0.85.0 on RPi 3

2019-01-12 14:42:56 ERROR (MainThread) [homeassistant.setup] Error during setup of component nibe
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/setup.py", line 145, in _async_setup_component
    hass, processed_config)
  File "/config/custom_components/nibe/__init__.py", line 122, in async_setup
    from nibeuplink import Uplink
ModuleNotFoundError: No module named 'nibeuplink'
2019-01-12 14:42:56 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of sensor.nibe. Setup failed for dependencies: nibe
2019-01-12 14:42:56 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform sensor.nibe: Could not set up all dependencies.
2019-01-12 14:42:56 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of switch.nibe. Setup failed for dependencies: nibe
2019-01-12 14:42:56 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform switch.nibe: Could not set up all dependencies.
213

Must be some error earlier. It has not installed a dependency.

214

Can this component be used with Hass.io?

215

Never tested it. But it should work. I know there was some python version problem at some point. But it was possible to resolve.

216

Yep I’m using it in Hass.io

Its not very obvious in the instructions and unless you read the conversations above you may miss the way it needs to be configured.

So just clone the elupus/hass_nibe repo to your custom_components folder. This alone won’t make the component work. Open the hass_nibe directory and you will notice that all of the directory structures look the same as the custom_components folder (if you have some already).

You need to move those directories out of the hass_nibe and into custom_components.

NOTE: if you are already using some custom components then make sure you don’t overwrite them with these instead you need to basically merge them. For example I had Hue custom component installed within the sensor directory, and hass_nibe also had a sensor directory so you just need to copy those contents into the existing sensor directory. Image attached of how mine looks to help.

06
061100×726 76.6 KB

Then just follow the rest of the instructions https://github.com/elupus/hass_nibe and obtain your NIBE Uplink keys.

I’ve only just had our NIBE F2040-16 with SMO20 uplink installed this week and it works great! The only things I’ve not tested is the remote turn on turn off features because I have not paid 25 Euro for the management charge to Nibe premium service, but I will do later on.

One thing I will say is do not pay for the Premium History service since you can do this from your Home Assistant Influx DB and Grafana based on the sensors you collect :wink:

Hope this helps!

1 Like
217

This is how it should be done for all installs. Not just hassio. This will become easier soon, when all can be contained inside one folder of your custom components folder.

1 Like
218

Ie the cloned folder IS your custom_components folder.

219

Hi guys, I get the same error as rawash when trying to get lastest hass_nibe to work in hassio 0.85.1 on RPI 3:

2019-01-19 12:49:53 ERROR (MainThread) [homeassistant.setup] Error during setup of component nibe
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/setup.py”, line 145, in _async_setup_component
hass, processed_config)
File “/config/custom_components/nibe/init.py”, line 122, in async_setup
from nibeuplink import Uplink
ModuleNotFoundError: No module named ‘nibeuplink’

It seems the dependent library nibeuplink is missing. I guess this is supposed to be installed automatically but fails in hassio for some reason. How did you solve this nickcj?

220

@imist You need to install the component yourself. Follow the instructions here:

221

nibeuplink should install itself automatically as long as you have internet access. Unless hassio does something differently.

222

And this is why I use Hassbian…

223

It seems the dependent library nibeuplink is missing. I guess this is supposed to be installed automatically but fails in hassio for some reason. How did you solve this nickcj?

Hi, could you solve the issue?
I have similar problem.
In case I have to install manually where do I have to put it?

224

I will not look myself att hassio installation issues. I dont use It it. seems it may need to be wrapped in a addon somehow. You can get around it with manual install of nibeuplink component inside docker. Google on custom dep install hassio.

I will accept a pull request for it.

225

One step forward, now I get:

Platform nibe not ready yet. Retrying in 180 seconds.

226

Did you manage to install nibeuplink in Hass.io? If so, how did you do that?

227

I try to give all infos:

  1. installed addon Custom deps deployment
    Config:
    {
    “pypi”: [
    “nibeuplink”
    ],
    “apk”: []
    }

  2. I temporarly redirected 8123 port from outside world to the device where I have installed hassio

  3. I followed the general instructions to activate it

228

You dont need to redirect/publish the port. You can enter a internal local url as redirect url.

229

i’m trying to intergrade my nibe but not sure what to write under system and unit (red marked in your config) Can you please help me?

230

System should be your system id (From the nibe link stated above. Unit should be 0 and of you have more then one unit (I have a vvm325 and a f2120) the next unit should be 1.