Nope, nothing in the log. If only one time boost is allowed is it possible to change so that the option boost_one_time is the one you should chose? Because today Boost_three_hours gives one time boost, all the other just turns it off/does nothing.
The other options work from a display perspective. At least on my system.
The only value allowed is 1. That should indicate 3 hour boost, not one time boost as per the docs. Are you saying you select 3 hour boost, but you pump switches to one time boost?
Hello, I just found out this component for home assistant and I’m also getting only 3 entities. Did you figure out what to do? I have no errors on the logs but on home assistant restart I get:
Invalid nibe config
No systems selected, please configure one system id of:
[
{
"systemId": xxxxx,
"name": "Koti",
"productName": "NIBE F1245",
"productImage": {
"name": "NIBE_F1245",
"sizes": [
{
"width": 75,
"height": 100,
"url": "/Content/Products/F1245_75x100.png"
}
]
},
"securityLevel": "ADMIN",
"serialNumber": "xxxxx",
"lastActivityDate": "2020-02-13T09:56:06Z",
"connectionStatus": "ONLINE",
"address": {
"addressLine1": null,
"addressLine2": null,
"postalCode": null,
"city": null,
"region": null,
"country": "UNKNOWN"
},
"hasAlarmed": false
}
]
you need to expand your configuration.yaml nibe: component further. For example see what i’ve put below, this gives me a LOT of sensros. change it pending on how many units you have.
nibe:
systems:
- system: YOUR_SYSTEM_ID
units:
- unit: 0
categories: True
statuses: True
- unit: 1
categories: True
statuses: True
climates: True
water_heaters: True
Just set my integration back up after being away for a while, a few bits have changed since I’ve last been here so trying to find my feet!
Hope this helps.
EDIT:
Just to further expand on understanding how many units you have in your system, you can login to your https://nibeuplink.com/ account then:
- Under Status go to Service Info
- In service info, you will see something like SMO20 / slave 1 etc. These are you units.(see image below).
- The
unit: 0andunit: 1actually refer to the units themselves, and you can see that if you click one and check your browser address bar:
http://nibeuplink.com/System/XXXX/Status/ServiceInfo/0 -- This is SMO 20
http://nibeuplink.com/System/XXXX/Status/ServiceInfo/1 -- This is slave 1
Hi,
The installation went well, but when I try to do the config i get this message in the logs
"Invalid config for [nibe]: expected int for dictionary value @ data[‘nibe’][‘systems’][0][‘system’]. Got ‘xxxxx(Identifier)’. (See /config/configuration.yaml, line 86). "
my config 
Is it just a indentation error?
If you read the error message. You should be able to understand. Xxxxxxx is not your system identifier.
Hi,
Ofc, its a placeholder for my real indentifier…didn’t want to show it of here 
Well it doesn’t seem to be a integral number which it should be.
Hi,
Hmm ok, because my identifier consists of both numbers and letters. But you say it has to be an integral number? Im new to this so bear with me :).
Ok, I found it, thx!
When I updated HA from 0.106 -> 0.107 all my NIBE entities became unavaliable, can’t figure out why and I do not see there should be any breaking changes in this version, or have I missed something?
Update the component. There was an API change on groups causing error in component
For some reason I cannot install/integrate the Nibe component. I have had it before, but had to reinstall hassio (now on version 0.107.5). All other intergrations work flawlessly. I deleted the Nibe in the custom_components folder and alse the “Nibe:” in the configuration.yaml. After many attempts with manual installations I finally got the NibeUplink on the intergration page. When I click the NibeUplink a white empty dialog box shows and a spinning circle. Then it disappears. If I press again, the dialog box shows for a second and then disappears. I removed the installation again and used HACS to install the Nibe component as described by Elupus. Again I only get the spinning circle in a white empty dialog box when I click the NibeUplink. Anyone who knows how to fix this?
Here is the log:
Logger: aiohttp.server
Source: custom_components/nibe/config_flow.py:64
First occurred: 11.18.31 (2 occurrences)
Last logged: 11.18.39
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py”, line 418, in start
resp = await task
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py”, line 458, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py”, line 119, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/real_ip.py”, line 39, in real_ip_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 72, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 127, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 123, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/config/config_entries.py”, line 130, in post
return await super().post(request)
File “/usr/src/homeassistant/homeassistant/components/http/data_validator.py”, line 50, in wrapper
result = await method(view, request, *args, **kwargs)
File “/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py”, line 62, in post
handler, context={“source”: config_entries.SOURCE_USER}
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 109, in async_init
result = await self._async_handle_step(flow, flow.init_step, data)
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 172, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File “/config/custom_components/nibe/config_flow.py”, line 64, in async_step_user
config = self.hass.data[DATA_NIBE].config
KeyError: ‘nibe’
So i’ve made an updated version. It should now allow selection on system in config flow to get the standard components. If you need categories you still need the stuff in config.
I’ve removed groups in this version since that is what broke with 0.107. I’ve added devices for each service category instead. So you should at least be able to get some help in grouping sensors.
1 Like
You still need a nibe: section in your config.
1 Like
Wow, you are fast to answer.
Yes, but everythime I put a Nibe: in config the config is not valid.
Used a backup config. Found the reason. I typed in Nibe: (capital N) and not nibe:
Thank you so much for you help. Now the integration works.
Since a couple of days my sensors are unavailable, I’ve tried removing and re-adding the integration but that didn’t help. Any ideas?
2020-03-22 17:21:52 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up nibe platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 179, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/config/custom_components/nibe/sensor.py", line 107, in async_setup_entry
sensors = await async_load(hass, uplink)
File "/config/custom_components/nibe/sensor.py", line 97, in async_load
await load_categories(system.system_id, unit[CONF_UNIT])
File "/config/custom_components/nibe/sensor.py", line 76, in load_categories
await asyncio.gather(*tasks)
File "/config/custom_components/nibe/sensor.py", line 51, in load_parameter_group
object_id="{}_{}_{}".format(DOMAIN_NIBE, system_id, object_id),
TypeError: async_create_group() got an unexpected keyword argument 'control'