Which openhab version are you running? Latest update could be 5.0.2 or 4.3.8. Which version of the binding do you run?
I updated to OpenHAB version 5.0.2 today. (packages: openhab, opennhab-addons)
The binding has now this version in karaf console:
328 ā Active ā 80 ā 5.1.0.202510190605 ā openHAB Add-ons :: Bundles :: Viessmann Binding
Eventually its a problem, that I store/maintain my items in a items-File versus storing them in the MainUI. But before this openhab-/addon-Update, there were not such warnings.
Also other bindings like Homematic and MQTT have no problems with item-Files yet.
I updated to the latest Version from 19. Oktober - same problems!
Hi evereyone,
I see there are 2 problems.
- Problems with
ItemChannelLink@AndreasBerz - Problems with:
heating-burners-0-statistics#hours, heating-circuits-0-heating-curve#shift, heating-circuits-0-heating-curve#slope
First problem:
@AndreasBerz The binding tries to change the channel link, because the name convention is changed. But this doesnāt work with hard-coded link in the *.items file. Please try to unlink / remove the item and relink this in the UI.
Second problem:
Iāll take a look in the code and gave a feedback.
1 Like
@dandy24 I fixed this problem. A new version is now available.
Thanks a lot, I tried the new version and it works 
.
1 Like
I also updated the binding. The logs look clean so far. I will report if warnings occur.
Thank you!
1 Like
But why? The āfeature namesā that I use in the channel-Parameter within the items-File are already correct according to the actual name conventions. Best evidence is, that every of the 43 items for the Vitodens 300-W is working correct. To my understanding, the binding tries to change names that are already correct. This behavior seem a bit strange to me, but maybe there is a misunderstanding on my side.
Hi all,
I upgraded to OH 5.0.2 (from 4.3) today. After reinstalling the Viessmann Binding I had to create new things (the old ones were looking for a āvicareā-binding. Unfortunately Iām still not able to finish the configuration of the account binding.
When doing the login via http://localhost:8080/viessmann/authcode/ I get a ā{āerrorā: āinvalid-code-requestā}ā. Deleting the client in the Viessmann Portal did not help.
Any advice how to proceed? Thanks!
If it was looking for vicare you had another Viessmann Binding installed. This one: Viessmann API binding for OpenHAB 4.0 [4.0.0;5.0.0)
If you have the correct URL at the Viessmann Website, without any white spaces or missing the slash at the end, maybe this hint from a comment above helps:
Then Iāve checked the settings in OH (Settings- >Network), and there was a radio button āPrimary IP- Addressā with the local IP-adress of the server. This was unselected. After activating, the Binding worked!!!
2 Likes
Good morning! I saw that post before and selected my OH IP (192.168.1.100/24) as primary address already. Did not help unfortunately.
The address Iām using should be correct: http://192.168.1.100:8080/viessmann/authcode/
Thanks!
Please change this: http://192.168.1.100:8080/viessmann/authcode/
To:
http://localhost:8080/viessmann/authcode/
In the Viessmann developer portal.
After that it should work. The binding supports at this point only localhost and not the IP Address from openHAB
1 Like
Youāre the man! For whatever reason Iām still getting the same error but the thing is now online. Much appreciated!
Thatās strange. The error should disappear once the account is online.
Have you restarted openHAB? Maybe the binding is stuck.
If not, please send me the log in trace mode via private message.
1 Like
Hi,
I installed the binding in replacement of the older ViCare-Binding which also used the Viessmann API on Openhab 5.0.
When trying to create new Viessmann Thing it tells me āNo thing types can be added with this binding.ā - So how do I create the Viessmann Thing?
Maybe Iām missing something?
You have to create the bridge only. after the bridge comes online, it will autodiscover the things which belong to the bridge.
2 Likes
It seems, removing and reinstalling the addon solved the issue.
Thanks.
1 Like
@STSC reported that the āOne Time Chargeā function was not working. I have fixed the bug. A new version is now online.
1 Like
Hi, after installing the Binding, configuring account (online) and discovering gateway (online too) my device (Vitocal 250A) was also discovered. Unfortunately the thing doesnāt go online, it shows an āHandler Errorā hinting āLast segment must not be blank: [viessmann, ]ā. Any help highly appreciated 
Hi @farbenmann , please set the loglevel to TRACE and PM me the full log.
Iāll take a look, asap