The VDR binding is an openHAB v1 binding. By default v1 bindings are hidden unless you select the option to show them as well (in PaperUI go to Configuration->System and then in the “Add-on Management” section enable the “Include Legacy 1.x Bindings” option).
2019-07-08 21:15:41.986 [INFO ] [b.core.service.AbstractActiveService] - VDR Monitor Service has been started
2019-07-08 21:30:13.988 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'vdr.items'
2019-07-08 21:31:42.098 [vent.ItemStateChangedEvent] - VDR_LivingroomRecording changed from NULL to OFF
I just know where to find the binding. I don’t know if it still works ok.
I would expect that the items will change state when they receive an updated state from VDR, e.g. when you control the volume or select a different channel that you will then see the new state for the specific item.
Did you install the OH1 Compatibility Layer yet? (Maybe by installing another OH1 Binding which already works as intended)
EDIT: just tried to install and seems to work:
2019-10-16 13:51:27.236 [INFO ] [b.core.service.AbstractActiveService] - VDR Monitor Service has been started
EEDIT2: Yep, working:
2019-10-16 14:07:29.450 [vent.ItemStateChangedEvent] - VDR_FF_Parents_Rec changed from NULL to OFF
2019-10-16 14:07:29.453 [vent.ItemStateChangedEvent] - VDR_GF_Living_Rec changed from NULL to OFF
2019-10-16 14:07:29.936 [vent.ItemStateChangedEvent] - VDR_FF_Server_Rec changed from NULL to ON
Other 1.x bindings work eg. Fritzbox tr064. Ok, if I just copy the file xxx.jar into the openhab\addons folder and do not set in addons.cfg bindings = …, vdr (otherwise the error will appear: Failed installing ‘openhab-binding-vdr’) then i
get in logfile:
“[b.core.service.AbstractActiveService] - VDR Monitor Service has been started”
and in event.log e.g.
…CommandEvent] - Item ‘vdr_wz_VolumeUpDown’ received command ON
…CommandEvent] - Item ‘vdr_wz_VolumeUpDown’ received command OFF
…ItemStateChangedEvent] - vdr_wz_VolumeUpDown changed from OFF to ON
…ItemStateChangedEvent] - vdr_wz_VolumeUpDown changed from ON to OFF
The VDR then reacts in principle to the PowerOff switch and switches off ‘Mute’ if you press the switch ‘VolumeUpDown’. It does not show any volume or channel number. In addition, I do not know how to turn the volume up or down with a switch in sitemap
It is also unclear why the binding can even access the VDR although nowhere (eg. vdr.cfg) a user and password are stored
The function of the binding is unclear to me and I think it should be revised
You can’t install a binding not mentioned as compatible to OH2 with the addons.cfg, so the message is absolutely correct. Don’t touch addons.cfg for manual installation, as it’s … manual…
Did you configure a device in services/vdr.cfg yet? I’m not sure about user/password, as I did not set any user/password in my vdr.
As Volume is a Number, you will have to link to a Number Item or at least to a Dimmer Item.
As Channel is also a Number, you will have to link this to a Number Item (and use setpoint in the sitemap to change the channel).
I will definitely give it a try to do an official submit.
But I use a library (svdrp4j) that is not available in the common maven repositories and the whole process to get the binding ready for a pull request is quite complicated for the hobby programmer I am.
There seems to be a problem, at least with the current version for openHAB 3.4.2
When a thing with vdr addon is active, there is an error Message in the log each time the Items list is loaded (e.g. in VS Code openhAB plugin):
[ERROR] [al.ChannelCommandDescriptionProvider] - Dynamic command description matches original command description. DynamicCommandDescriptionProvider implementations must never return the original command description. class org.openhab.core.internal.types.CommandDescriptionImpl has to be fixed.
If stopping the bundle, the errors are gone immediately.