SmartHome/J Viessmann Binding for 4.0.x

Some channels or features (as called by Viessmann) are included in the Advanced package.
However, I don’t know if this feature is provided by the API.
Here is the list from viessmann with the features provided:

Channels in the Basic (free) package:

heating.compressors → Shows the list of enabled compressors.

heating.compressors.N → Shows whether compressor N is active

heating.compressors.N.statistics → Shows the statistics of the compressor, i.e. number of working hours and number of starts

Channels in the Advanced package:

heating.fuelCell.statistics → Shows the statistics of the compressor, i.e. operating hours, production hours & number of starts

heating.compressors.N.heat.production.cooling → Shows the thermal energy production per day, week, month and the last year (cumulated value over the last 52 weeks) per compressor for the cooling process

heating.compressors.N.heat.production.cooling.week → Shows the heat production of the compressor for cooling during the current week

heating.compressors.N.heat.production.current → Shows the current heat generation of the compressor

heating.compressors.N.heat.production.dhw → Shows the thermal energy production per day, week, month and the last year (cumulated value over the last 52 weeks) per compressor for DHW process

heating.compressors.N.heat.production.dhw.week → Shows the heat production of the compressor for DHW during the current week

heating.compressors.N.heat.production.heating → Shows the thermal energy production per day, week, month and the last year (cumulated value over the last 52 weeks) per compressor for heating process

heating.compressors.N.heat.production.heating.week → Shows the heat production of the compressor for heating during the current week

heating.compressors.N.heatTarget → Shows what the compressor is currently heating (e.g. “dhw”)

heating.compressors.N.power.consumption.cooling → Shows statistics of power usage for cooling down rooms by the compressor. It is shown in kWh

heating.compressors.N.power.consumption.cooling.week → Shows the power consumption of the compressor for cooling during the current week

heating.compressors.N.power.consumption.current → Shows the current power consumption of the compressor

heating.compressors.N.power.consumption.dhw → Shows statistics of power usage for heating up DHW by the compressor. It is shown in kWh

heating.compressors.N.power.consumption.dhw.week → Shows the power consumption of the compressor for DHW during the current week

heating.compressors.N.power.consumption.heating → Shows statistics of power usage for cooling up rooms by the compressor. It is shown in kWh

heating.compressors.N.power.consumption.heating.week → Shows the power consumption of the compressor for heating during the current week

heating.compressors.N.power.consumption.total → Shows statistics of total power usage by the compressor. It is shown in kWh

Since the other openhab binding does also use my credentials, i.e. the free account, the info is included. I will search the code to find some info. It should be a status string.

1 Like

I think it is: heating.compressors.0.phase. I got “preparing”, “heating” and “pause”.

@sven1234 I have sent you a pm.

Got your message and replaced the 4.3.0 kar by the 4.3.1. Restarted the openhab docker image and the phase property seems to work. I got all states, i.e. preparing, heating, pause and off.

Thanks a lot for the improvement!

I would still like to see the binding in the normal marketplace. It deserves more attention and you should be able to release whenever you want and not depend on somebody else. Imagine you had a severe bug which needs fixing but cannot release the update to the users.

Not new, but maybe worth mentioning is that the controller serial is displayed only as a string of unknown characters.

grafik

Does somebody else also have the issue, that the gateway always stays in the state “initializing”? Does not seem to cause any issues.

grafik

In the logs I see the following every few seconds.

grafik

Any chance that this binding will be ported to the “normal” marketplace add-ons?

Is it available/tested for OH 5.0 already?

I’m working on a new version with support for 5.0 and some changes to the installed gateway selection.

I expect to make it available for testing in the next few days.

I’m not sure if I’m allowed to publish my version on the Marketplace. A similar binding already exists there. Nevertheless, I don’t want to abandon my project and will continue developing it.

@rlkoshak, you seem familiar with the forum and its rules. Is there a rule that forbids to have two bindings for the same purpose? I am not sure which Viessmann binding exists longer, but this one has some differences in detail. For example does it not patronise regarding the slope and level, i.e. lets the user change them via the API, as allowed by Viessmann.

To limit confusion caused by a proliferation of bindings that all dot he same thing, the policy is that the marketplace can be used to publish a testing version of a binding with the intention that once it’s tested the changes will be merged with the official add-on.

But this binding is not an official add-on as far as I can tell. It comes from the third party SmartHome/J marketplace. As far as I can tell, there is no official Viessmann add-on. So there shouldn’t be any problem posting a Viessmann add-on to the OH marketplace.

However, the developer of the original add-on on the Smarthom/J repo may take issue with that so it’s best to check with them first.

Ideally, the add-on would eventually be submitted as an official add-on but that’s not required.

Thanks, AFAIK @rogrun is the original author, so that should not be a problem. :slightly_smiling_face:

isnt it @J-N-K ?

I might be wrong but I understood that there is the “3rd party platform” and then there are the add-ons. Both do not necessarily have the same maintainer or author.

I’m the original author of the binding. I published it in the SmartHome/J project.

1 Like

Hi everyone, I’m working on a new version with some improvements, including gateway selection, and other fixes for OH5. I plan to release it on the Marketplace in the next few days. I hope to have it finished by Friday. I’ll be on vacation for two weeks after that.

1 Like

Hi everyone, I’ve published the binding for OH5 here on the Marketplace: Viessmann Binding [5.0.0;5.9.0)

If a version for 4.x is needed, please let me know. However, I need some time to backport it.

1 Like