2023-03-09 08:57:10.746 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Rome'.
2023-03-09 08:57:10.792 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_IT'.
2023-03-09 08:57:14.244 [WARN ] [.transport.servlet.ServletController] - Can't find the request for http://192.168.1.79:8080/rest/things's Observer
2023-03-09 08:57:14.256 [WARN ] [.transport.servlet.ServletController] - Can't find the request for http://192.168.1.79:8080/rest/inbox's Observer
2023-03-09 08:57:15.428 [WARN ] [org.openhab.core.net.NetUtil ] - Found multiple local interfaces - ignoring 192.168.56.1
2023-03-09 08:57:27.183 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2023-03-09 08:57:29.597 [INFO ] [org.openhab.ui.internal.UIService ] - Started UI on port 8080
2023-03-09 08:57:30.179 [INFO ] [ab.ui.habpanel.internal.HABPanelTile] - Started HABPanel at /habpanel
2023-03-09 08:57:30.315 [WARN ] [care.internal.VicareDiscoveryService] - Authentication problem scanning Viessmann API:Unable to authenticate: No valid access token and no refresh token.
2023-03-09 08:57:36.154 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2023-03-09 09:05:39.161 [WARN ] [care.internal.VicareDiscoveryService] - Authentication problem scanning Viessmann API:Unable to authenticate: No valid access token and no refresh token.
events.log
2023-03-09 09:05:36.835 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vicare:bridge:ac941b4bf9' changed from UNKNOWN to UNINITIALIZED
2023-03-09 09:05:36.844 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vicare:bridge:ac941b4bf9' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2023-03-09 09:05:39.165 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vicare:bridge:ac941b4bf9' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2023-03-09 09:05:39.167 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vicare:bridge:ac941b4bf9' changed from INITIALIZING to UNKNOWN
I don’t have enough info to say why you are having this problem.
You should have the line
Configuring servlet with accessServerUri xxx
In your openhab log file somewhere, if the servlet has started at all. If you don’t have this line, then it’s some kind of weird installation problem with the karaf kar that you might have to fix in the openhab shell. That’s pretty much the only thing that I’ve seen that ever causes it not to start.
The only other reason you wouldn’t get that page to render at all would be some kind of networking problem or your URL is wrong. Check firewalls, proxies, that kind of thing.
However, your page is blank, I would expect some kind of HTTP error at minimum bc the OSGI container will handle the request and reject it if the servlet does not start.
Open the developer tools in your browser and find out what the HTTP response actually is or if there even is one.
If the servlet receives a request it will log
Fetching xxx
If it started and you don’t see that then the request simply is not even getting to it.
@oppo1967p
Just a wild guess, there are two Viessmann binding, the one discussed in here is from the Marketplace, the other one is the Smarthome/J version. Which one do you use?
The log file I have posted is the complete log file.
As I said it’s a brand new installation. So no other bindings are installed. Only vicare.
The binding seems properly installed:
If that is the full log, then the binding is not properly installed - either it hasn’t been discovered, or there is some issue with your karaf install. Go into the openhab shell and do the below, you should get similar output, depending on your installed version of the binding
openhab> feature:list | grep vicare
com.qubular.openhab-binding-vicare-feature │ 3.4.0 │ x │ Started │ com.qubular.openhab-binding-vicare-feature │ com.qubular.openhab-binding-vicare-feature
If they are not showing, then the binding has not been discovered and is not installed correctly.
If they are there but different status, it’s possible you have some kind of karaf issue for whatever reason, you need to diagnose it from there, either there’s conflicting dependencies, an old version of the binding is cached or something similar, you should be able to figure it out from there.
The 3.4 release is now published, see the dedicated topic post for that binding. All new development activity will be there.
As far as support for additional basic-api-values - if you believe there is something missing then please let me know which features they are and send me a capture from your api as detailed in posts elsewhere in this topic - as without a sample json response it’s not possible to support it just on their api documentation alone.
