Viessmann Binding [5.0.0.0;6.0.0.0)

rogrun · March 13, 2026, 3:03pm

Hi @sven1234, I’ve checked your log. All data from Viessmann is correct.

I think there’s a bug in version 5.1.3. I fixed many issues in version 5.2.M2, but it hasn’t been released yet.

However, you can install this version (5.2.0.202602211614) from the Add-ons Marketplace or download it here: https://github.com/rogrun/openhab-addons/releases/download/Release-Viessmann-Binding-5.2.0.202602211614/org.openhab.binding.viessmann-5.2.0.202602211614.jar

Then place it in your addons folder. Please remove the old binding first.

Udo_Hartmann · March 13, 2026, 4:48pm

Well, I’m using 5.1.3 Release Build as well and the Viessmann binding which is shipped with the release version. works flawless here.
Sometimes a uninstall/reinstall of the binding may help (you don’t need to remove any Things or Items, but maybe restart openHAB before reinstalling the binding)

sven1234 · March 13, 2026, 5:25pm

I did so, but it did not help. Removing the distro binding and installing the “beta” binding from the marketplace worked.

BGrosse · March 16, 2026, 8:05pm

Hi Ronny!

Thank you sooo much for this binding!

Unfortunately I got these two errors every 1-2 minutes with my Vitocal 222S:

2026-03-16 20:56:15.031 [WARN ] [smann.internal.handler.DeviceHandler] - Unknown unit. Could not parse unit: seconds of Feature: heating.device.mainECU - Please create an issue on GitHub with this anonymized detailed JSON:

{

  "apiVersion" : 1,

  "isEnabled" : true,

  "isReady" : true,

  "gatewayId" : "{{gatewaySerial}}",

  "feature" : "heating.device.mainECU",

  "uri" : "https://api.viessmann-climatesolutions.com/iot/v2/features/installations/{{installationId}}/gateways/{{gatewaySerial}}/devices/0/features/heating.device.mainECU",

  "deviceId" : "0",

  "timestamp" : "2026-03-16T19:53:57.530Z",

  "properties" : {

    "runtime" : {

      "type" : "number",

      "value" : 113018255,

      "unit" : "seconds"

    }

  },

  "commands" : { }

}

2026-03-16 20:56:15.102 [WARN ] [smann.internal.handler.DeviceHandler] - Unknown unit. Could not parse unit: seconds of Feature: heating.heatingRod.runtime - Please create an issue on GitHub with this anonymized detailed JSON:

{

  "apiVersion" : 1,

  "isEnabled" : true,

  "isReady" : true,

  "gatewayId" : "{{gatewaySerial}}",

  "feature" : "heating.heatingRod.runtime",

  "uri" : "https://api.viessmann-climatesolutions.com/iot/v2/features/installations/{{installationId}}/gateways/{{gatewaySerial}}/devices/0/features/heating.heatingRod.runtime",

  "deviceId" : "0",

  "timestamp" : "2026-03-16T04:48:37.748Z",

  "properties" : {

    "levelOne" : {

      "type" : "number",

      "value" : 8577,

      "unit" : "seconds"

    },

    "levelTwo" : {

      "type" : "number",

      "value" : 9742,

      "unit" : "seconds"

    }

  },

  "commands" : { }

}

Do you experienced this ever on your side? Is there anything I can do? Aside from that, the binding and everything worked “right out of the box”.

My actual system is OH 5.1.3 in a fresh openHABian v1.12.0b installation with your latest binding above.

As I am not familiar with filing an issue on GitHub, I ask here. Sorry for that…

Please let me know if you need further infos or testing.

Thanks!

rogrun · March 17, 2026, 7:19am

Hi @BGrosse

That’s not a problem, it’s fine here too.

No, you can’t do anything here. I need to add the unit “seconds” to the binding.

I will implement it in the next few days.

rogrun · March 20, 2026, 7:22pm

@BGrosse

I published a new release here.

Please remove the old binding and re-install form marketplace.

BGrosse · March 21, 2026, 6:08pm

Hi Ronny!

This one works great - thank you for that

Another thing I noticed is, that the “holiday active” jumps from OFF to ON and immediatley back to OFF again every once in a while:

2026-03-21 19:01:51.276 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Viessmann_Vitocal_222S_Operating_program__holiday_active' changed from OFF to ON (source: org.openhab.core.thing$viessmann:device:8fae8d4ce9:7637415009038218:8fae8d4ce9:heating-operating-programs-holiday#active)

2026-03-21 19:01:51.284 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Viessmann_Vitocal_222S_Operating_program__holiday_active' changed from ON to OFF (source: org.openhab.core.thing$viessmann:device:8fae8d4ce9:7637415009038218:8fae8d4ce9:heating-operating-programs-holiday#active)

2026-03-21 19:03:18.797 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Viessmann_Vitocal_222S_Operating_program__holiday_active' changed from OFF to ON (source: org.openhab.core.thing$viessmann:device:8fae8d4ce9:7637415009038218:8fae8d4ce9:heating-operating-programs-holiday#active)

2026-03-21 19:03:18.819 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Viessmann_Vitocal_222S_Operating_program__holiday_active' changed from ON to OFF (source: org.openhab.core.thing$viessmann:device:8fae8d4ce9:7637415009038218:8fae8d4ce9:heating-operating-programs-holiday#active)

Did you experienced this also? I never saw this on the older ViCare Binding on OH 4.x - it seems to be new with your binding.

Does this come from the Viessmann API or is it a glitch effect in the binding?

Please let me know if you need more specific information or testing.

Thanks

Konfusius · April 17, 2026, 8:10am

Hi,

I’m sorry, but I’m not able to get it working. I removed the binding and reinstalled it from the marketplace. But I don’t get more than the account thing (via file) and the gateway. Is there a step by step guide or a kind of a tutorial available?

TIA
Reinhold

sven1234 · April 17, 2026, 11:57am

Assuming you have already entered the Infos for the account thing, like username etc.: If you check the Inbox in the Things section, there is not Device 0 listed? And you cannot add any device via the “+” button?

Konfusius · April 19, 2026, 9:58am

Account and Gateway things are OK. Devices remain in “INITIALIZING” state and in the log there is an entry “ViError: User does not have access to given feature.” My Viessmann developer account has the basic plan. There is a community thread in the Iobroker forum which mentiones that a token is needed. But the token which can be generated on the Viessman site lives just 1 hour and the binding does not accept a token. On the other hand, when I read this thread her I have the impression that some guys got it working, so I’m wondering what I’m doing wrong.

rogrun · April 19, 2026, 10:20am

@Konfusius Could you please set the logging level for the Viessmann Binding to “TRACE” and send me the complete log via private message? I’ll look into the problem.

sven1234 · April 26, 2026, 7:39am

Does anyone get these warning messages in openHAB 5.1.4?

Message
Failed to normalize configuration for new thing during update 'viessmann:device:xyz:0': {thing/channel=Type description viessmann:duration-minute for viessmann:device:xyz:0:heating-configuration-temperature-outside-damping-factor not found, although we checked the presence before.}

rogrun · April 28, 2026, 5:43pm

@sven1234 which version are you running?

This should be fixed in the last marketplace release.

Konfusius · May 5, 2026, 6:53pm

As of yesterday everything works fine without any activity or setup change on my side. So I assume the problem was at Viessmann. Anyways. it works and I get data via the API. @ Ronny: thanks for your kind support. I appreciated it.

oppo1967p · May 11, 2026, 12:08pm

Hi @rogrun

excellent works! thanks for your effort!!

I am wondering if it would be possible to add a couple of channels that are missing (and were available in the previous vicare binding):

type volume heating.gas.consumption.*
type energy *.power.consumption.*
type boolean heating.dhw.operating.modes .comfort / .eco / .active (=only .active is present)

thanks for your support…