There seems to be a few different issues here. The first error:
I find quite strange, because that channel group type is statically defined in xml-files, so I have no idea why openhab cannot find it. Perhaps a restart of the bundle could be enough to fix it.
The second error:
Should only be possible to get when doing the oauth authorization flow, so it’s strange that it appears several minutes later. It does however indicate that the authorization failed for some reason, which would explain why no things can be discovered.
You could check the file /var/lib/openhab/jsondb/StorageHandler.For.OAuthClientService.json
to see if a valid token has been aquired. It should look something like this (Do NOT post the full contents of the file, it can be used to access your system!):
"nibeuplinkrest:apibridge:apibridge.AccessTokenResponse": {
"class": "java.lang.String",
"value": "{\n \"accessToken\": \"<really long base64 encoded string>\",\n \"tokenType\": \"bearer\",\n \"expiresIn\": 1800,\n \"refreshToken\": \"<long base64 encoded string>\",\n \"scope\": \"READSYSTEM WRITESYSTEM\",\n \"createdOn\": \"2022-07-21T12:24:24.949985\"\n}"
},
"nibeuplinkrest:apibridge:apibridge.LastUsed": {
"class": "java.lang.String",
"value": "\"2022-07-21T12:24:24.951892\""
},
"nibeuplinkrest:apibridge:apibridge.ServiceConfiguration": {
"class": "java.lang.String",
"value": "{\n \"handle\": \"nibeuplinkrest:apibridge:apibridge\",\n \"tokenUrl\": \"https://api.nibeuplink.com/oauth/token\",\n \"authorizationUrl\": \"https://api.nibeuplink.com/oauth/authorize\",\n \"clientId\": \"<your client ID>\",\n \"clientSecret\": \"<your client secret>\",\n \"scope\": \"READSYSTEM WRITESYSTEM\",\n \"supportsBasicAuth\": false,\n \"tokenExpiresInSeconds\": 10\n}"
},
I would suggest to first restart the bundle bundle:restart org.openhab.binding.nibeuplinkrest
to make sure everything gets loaded correctly, but I will experiment a bit when I get home from work. The binding has been stable for over a year for me (except for occasional outages on nibe’s side), but it was also years ago i did the authorization and discovery, so perhaps some bugs have snuck in there in the meantime.
Edit: Just tried with a fresh OH (3.3 stable) and everything worked as expected, so there shouldn’t be any changes in core that have caused the binding to stop working.