It’s already there! Check the API Bridge Binding, there you can change the Access Server URI and IoT Service Endpoint. Works like charm!
1 Like
Hello all,
I am a beginner and recently became the owner of a Viessmann heat pump. I’ve integrated the Binding on an openHAB 4.3.4 on an virtual maschine.
Now I’ve set up a mini-PC with UBUNTU and installed openHAB 5.0.0.
But Viessmann’s binding seems to be incompatible with 5.0.0. I can install it, with the option “incampatible Binings”, but I can’t create a thing of it.
Is there, or will there be, a compatible version?
Thx
Kai
Maybe tryout Smarthome/J Viessmann Binding
Go to Settings → 3rd party add-ons and paste the url https://download.smarthomej.org/addons.json to the list of URLs. Then head to the Add-on Store→Bindings→Other Add-ons and install the binding.
Version is 5.0.0.2025010000.
Thx for the info.
I’ve installed the Binding and I could create a Thing. But I could not connect, status is offline with message “Login fails. Please check API Key.”. But I’ve filled the Client ID and the login credentials of the API portal.
I’ve also un- and reinstalled the Thing / Binding and changed the password of the API-portal. Unfortunately, no change…
Hi Torsten, thanks for the hint… I had a look at the binding configuration before, but there was nothing to set… so, configuring the bridge was the helping hint.
thanks again to rtuck99 for this very stable and comfortable binding.
Hi all, first things first: many thx for the Viessmann binding - it worked seamlessly under OH4 - great work! With the upgrade to OH5.0 I run into the same problems as Kai_Huggle. With Udo’s hints I was able to re-establish the binding but got also the same offline-status-message: “Login fails. Please check API Key.” (but I was able to make API calls via a browser)
My guess: I was not able to redirect the URL via http:///vicare/setup. The system comes up with “Requested content not found“. Help would be very much appreciated - many thx
Same here! After upgrade to OH5.0 “please check API key”….
Just a question as I would like to upgrade to OH5 (I rolled back when I saw that the upgrade breaks the OH binding): did you manage to get the API Binding to work under 5.0 or did you switch to the Smarthome/J binding?
Unfortunately I was still not able to get the Viessman binding running under OH5.0. Positive: the Viessmann App shows up under the Marketplace Bindings so Udo Hartmann’s Smarthome/J steps is not necessary anymore. However the setup page: http://your-OH-IP:8080/vicare/setup is still not available and I was not able to get the Viessmann account online. (I reloaded the Viessmann binding now via Marketplace, cleaned cash/tmp and rebooted a couple of times)
While the old Viessmann / vicare community binding was perfectly doing its job on OH4, I cannot manage to successfully run this new one on OH5. After one day, I finally gave up for now and restored the backup of OH4 including the old binding. Being able to control heating and boiler is a key feature of my home for energy saving. With OH5 and the new binding it was not possible to establish a connection to the Viessmann portal, I always immediately got an error saying “Login fails. Please check API Key.”. Also tried the Smarthome/J version without luck and the same error message. I really appreciate your work and I am looking forward to new and fixed version of the binding. Thanks!
Although I would wait for the next release of that binding, you could try Viessmann Binding [5.0.0;5.9.0) if you want to use OH5.
Ah, that is actually the binding I tried without success and the one I was referring to in my post. Thanks Sven for your reply! Now I understand this one (the Viessmann API binding) is actually a different binding than the Viessmann Binding. So I obviously reported an issue for another binding here, sorry for this mistake. Is the Viessmann API binding already available for OH5, I guess I cannot use the version for OH4?
Hi @Udo_Hartmann I do not understand your hint? I still have openHAB 4.3.5 and want to keep it till the rainy days. I also got the message from Viessmann with the change of the api Adresses. The thing for the bridge binding is working. But if i add a heatingdevice as a new thing it will not connect. Can somebody help me.
Hi @rtuck99
just want to report a bug:
when a heating devices is OFFLINE (i.e. powered off/power failure), in the log there is the following message:
2025-09-02 18:14:29.674 [WARN ] [ar.vicare.internal.VicareServiceImpl] - Unable to request features from IoT API, server returned 400, : DEVICE_COMMUNICATION_ERROR
2025-09-02 18:14:29.675 [WARN ] [.vicare.internal.VicareBridgeHandler] - Unable to prefetch features
com.qubular.vicare.VicareServiceException: API returned 400:DEVICE_COMMUNICATION_ERROR - - 404:GATEWAY_OFFLINE
at com.qubular.vicare.internal.VicareServiceImpl.getFeatures(VicareServiceImpl.java:231) ~[?:?]
at com.qubular.openhab.binding.vicare.internal.CachedFeatureService.lambda$getFeatures$2(CachedFeatureService.java:68) ~[?:?]
at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768) [?:?]
at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760) [?:?]
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) [?:?]
at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) [?:?]
at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) [?:?]
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) [?:?]
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) [?:?]
Actually, it should not raise any error message if the device is OFFLINE. It should peacefully remain in OFFLINE state until it comes back ONLINE.
I remember that this error was reported by me some years ago, and it was fixed. But now it has reappeared.
EDIT:
The old thread was: Vicare (viessmann) disconnecting
Hi Sven, many thanks for your support. I’ve tried your jar file today and it unfortunately also failed to get the Viessmann bridges online (tried all bridges manually). I also still was not able to enable the account via http://your-OH-IP:8080/vicare/setup as I’ve described above. In my log file I’ve got this info/warning:
2025-09-03 13:53:35.213 [INFO ] [.viessmann.internal.api.ViessmannApi] - API AuthException: Unable to execute GET: Can not set auth header because access token is null
2025-09-03 13:53:35.258 [WARN ] [viessmann.internal.api.ViessmannAuth] - ViessmannAuth: Login failed. Wrong code response.
Thank you very much!
Ah. Maybe consider to give Smarthome/J a try anyway, it’s also available for 4.3.5.
I’ve experienced problems with the other Viessmann Binding but not with the Smarthome/J type.
The binding I was referring to is from another author. If you want help, I would post in that thread and not here.
Where can I find more Informations about the Smarthome/J and its installation?
Go to MainUI → Administration → Settings → System Settings → JSON third party Add-Ons → set URLs to https://download.smarthomej.org/addons.json, then reload the Add-on Store (maybe ctrl+F5?)
You should find an additional section in MainUI → Administration → Add-on Store → Bindings → Other Add-Ons with the third-party Add-ons.
In question of documentation, there is no extra documentation for versions newer than 4.3.0-SNAPSHOT, so use this:
1 Like