First of all, thanks for a great Custom Component, works great!
I wonder if its possible to get the “Notifications” information from the Nibe Uplink API.
If you log in to Nibe Uplink, and go to History->Information Messages, you can se all alarms and warnings from the system.
It looks like you can retrieve this information from the API with an GET on " api/v1/systems/{systemId}/notifications", https://api.nibeuplink.com/docs/v1/Api/GET-api-v1-systems-systemId-notifications_type_active_page_itemsPerPage
Is there any config option already implemented in Configuration.yaml to get the latest notification message as an entity?
It would be good to have this, as you could send an push notice from homeassistant whenever the heating system gets an alarm.
Well. Some notification should be hooked up to normal ha notifications. But the available notifications seem quite limited. I don’t seem to be getting any sadly.
Is there anyway to get the code from github to paste in Lovelace raw config editor to have all sensors added? I mean in neat groups like on first install.
I have re-installed this integration and re-building all cards and groups in Lovelace is not the most fun.
Any one else that got nibe killed by last HA update?
Log Details (ERROR)
Thu Nov 21 2019 15:47:35 GMT+0100 (Central European Standard Time)
Error while setting up platform nibe
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 150, 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 66, in load_categories
data = await uplink.get_categories(system_id, True, unit_id)
File "/usr/local/lib/python3.7/site-packages/nibeuplink/uplink.py", line 207, in get_categories
{"parameters": str(parameters), "systemUnitId": unit_id},
File "/usr/local/lib/python3.7/site-packages/nibeuplink/uplink.py", line 74, in get
"GET", f"{self.base}/api/v1/{url}", *args, **kwargs
File "/usr/local/lib/python3.7/site-packages/nibeuplink/session.py", line 168, in request
response = await self.session.request(*args, auth=await self._get_auth(), **kw)
TypeError: request() takes 3 positional arguments but 4 were given
Do you need anything more from me? I could not find anything else in the logs. Unfortunately I can’t downgrade the component as I can with most of the other one in HACS to verify this for you either.
I think the last update via HACS crashed some sensors, like outside temp and other sensors. Are anyone else have the same problem?
And one more thing. I saw that I use my (old) duck dns adress as callback url but nowadays I use NAbu Casa to get remote access. Shall I put that adress as callback? It don’t have a port in the URL just a long https adress.
You can’t use nabucasa callback now. You must use a callback directly to the hass system. You don’t need any ports open thou. Just as long as it’s accessible from the webbrowser you use when you link the accounts. After that it’s not needed anymore.
So if I understand I set callback to the same as my local ip has.io?
But I only need this when setting up - if the integration is set up then it don’t matter. Mine is set up so… just need to copy paste the new master files, or shall I wait for hacs update?