Hello @csowada, thanks for your quick debugging. Sorry, issue with file download was my mistake, the links work only if the user is logged in to Github.
My esera Ethernet eBus coupler is now “online”. Thanks!
nothing to do:
2020-12-27 10:56:03.338 [INFO ] [internal.things.EBusTypeProviderImpl] - Load custom ‘url’ configuration file ‘file:///etc/openhab2/ebus-configuration-1.0.7-20200517.192845-1/index-configuration.json’ …
2020-12-27 10:56:03.349 [ERROR] [org.openhab.binding.ebus ] - bundle org.openhab.binding.ebus:2.50.10.202012262120 (286)[org.openhab.binding.ebus.internal.things.EBusTypeProviderImpl(293)] : The activate method has thrown an exception
java.lang.NullPointerException: null
at java.util.Objects.requireNonNull(Objects.java:203) ~[?:1.8.0_265]
at de.csdev.ebus.command.EBusCommandCollection.<init>(EBusCommandCollection.java:48) ~[?:?]
at de.csdev.ebus.cfg.std.EBusConfigurationReader.loadConfigurationCollection(EBusConfigurationReader.java:141) ~[?:?]
at de.csdev.ebus.cfg.std.EBusConfigurationReader.loadConfigurationCollection(EBusConfigurationReader.java:127) ~[?:?]
at de.csdev.ebus.command.EBusCommandRegistry.loadCommandCollection(EBusCommandRegistry.java:105) ~[?:?]
at org.openhab.binding.ebus.internal.things.EBusTypeProviderImpl.loadConfigurationByUrl(EBusTypeProviderImpl.java:405) ~[?:?]
at org.openhab.binding.ebus.internal.things.EBusTypeProviderImpl.updateConfiguration(EBusTypeProviderImpl.java:580) ~[?:?]
at org.openhab.binding.ebus.internal.things.EBusTypeProviderImpl.activate(EBusTypeProviderImpl.java:113) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_265]
…
after reboot:
openhab> bundle:list|grep eBUS
284 │ Active │ 80 │ 1.1.3 │ eBUS library configuration
285 │ Active │ 80 │ 1.1.4.SNAPSHOT │ eBUS core library
286 │ Waiting │ 80 │ 2.50.10.202012262120 │ openHAB Add-ons :: Bundles :: eBUS Binding
Hello @dk8pn,
Yes, unfortunately that is currently the case with GitHub. I will revise this again for snapshots releases. But it’s good that the bug is fixed now. Strange that it ran at all 
Hello @modenet,
The error is correct overall, but not particularly helpful. Your own configuration has no id property? Could that be?
The new version is now much stricter to avoid possible errors in the code. But I would have to revise the message.
If this is not the case, it would be good if you could send me your configuration.
Hello All,
now it is time for two new releases. The fixed 2.5 release and now the untested 3.0 release.
Since I spent too much time on the release yesterday and today, I won’t adjust this thread until the next few days.
yes, I tested 2.50.10 and now is working fine! no needs to restart openhab
thanks
Only for information as you wrote the V3 binding is untested. I could install the AddOn in OH3 and it seems to work. Thanks for your work on this.
Hi there,
i have so far with version “org.openhab.binding.ebus-2.5.1-8.kar” worked and it worked.
When I 2.50.10 start, the following errors appear:
2020-12-28 19:44:20.911 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle:
file:/C:/openhab/addons/org.openhab.binding.ebus-2.50.10.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.ebus [282]
Unresolved requirement: Import-Package: de.csdev.ebus.cfg; version="[1.1.0,2.0.0)"
bundle:list
282 │ Installed │ 80 │ 2.50.10 │ openHAB Add-ons :: Bundles :: eBUS Binding
OpenHab 2.5.10 runs on Windows 10
I can see your error is about .jar file, but I think we shall install .kar file?
I am also planning to change from 2.5.1-8 to 2.50.10.
Shall I delete/uninstall 3 ebus bundles related to 2.5.1-8 first, then install new .kar?
Normally it is enough to delete/move the file in the addon folder and wait until the bundle is uninstalled. Afterwards you can copy the new kar file to the addons folder and wait again. In some situations a server restart is required.
Hello @Tallman,
As @RafalO already mentioned, you must use the .kar file not the .jar file. In the .kar file are the missing bundles included.
Hello @vbier,
Thank you for the feedback. I’ve just tested if the binding is able to install on a fresh oh3.0 Windows environment. So there was no connection to a real heating device. It is good to know that it works in real environments 
If I correctly understand the errros below, there are some templates changes between 2.5.1-8 and 2.50.10? or it is something else?
2020-12-28 20:07:56.943 [ERROR] [org.openhab.binding.ebus ] - bundle org.openhab.binding.ebus:2.50.10 (280)[org.openhab.binding.ebus.internal.EBusHandlerFactory(282)] : The typeProvider field has thrown an exception
2020-12-28 20:07:58.101 [ERROR] [internal.things.EBusTypeProviderImpl] - Error on loading configuration by url: The property 'label' is missing for the configuration! [ URL: file:/etc/openhab2/eBUS/vaillant_template2.json ]
2020-12-28 20:07:58.127 [ERROR] [internal.things.EBusTypeProviderImpl] - Error on loading configuration by url: Unable to find a template for id vaillant.templ.temp1! [ URL: file:/etc/openhab2/eBUS/VR61_2RO.json ]
2020-12-28 20:07:58.193 [WARN ] [internal.things.EBusTypeProviderImpl] - eBUS command boiler.control.setopdata only contains a setter channel!
2020-12-28 20:07:58.340 [ERROR] [org.openhab.binding.ebus ] - bundle org.openhab.binding.ebus:2.50.10 (280)[org.openhab.binding.ebus.internal.utils.EBusConsoleCommandExtension(284)] : The typeProvider field has thrown an exception
2020-12-28 20:08:21.133 [WARN ] [dev.ebus.core.EBusLowLevelController] - Received byte 0x08 is not equal to send byte 0x09! Stop send attempt ...
Yes, the new version is more strict. Please add a label, description and id property to your json file. It is on top of the json file. In your case it is the file vaillant_template2.json, the next error is because the not loaded previous file.
Have a new heat pump VWL 105/6 and the VRC 720 controller. Can this work together with the integrated VRC 700 things? Use PaperUI.
It works with the .kar file, thanks. 
I have changed vaillant_template2.json
{
"id": "vaillant",
"label": "RO label",
"description": "this is template",
"templates": [
{
"name": "templ",
"template": [
{"name":"cntstarts","type":"bcd","label":"start counter","length":3},
{"name":"cntminutes","type":"bcd","label":"operation minutes","format":"%.1fmin"},
.......
But seems there is something else to change as well?:
2020-12-29 11:04:12.820 [hingStatusInfoChangedEvent] - 'ebus:V6100:58c13b58:50' changed from INITIALIZING to ONLINE
2020-12-29 11:04:12.818 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.initialize()' on 'org.openhab.binding.ebus.internal.handler.EBusHandler@b36e8f': can't parse argument number:
java.lang.IllegalArgumentException: can't parse argument number:
at java.text.MessageFormat.makeFormat(MessageFormat.java:1429) ~[?:1.8.0_252]
at java.text.MessageFormat.applyPattern(MessageFormat.java:479) ~[?:1.8.0_252]
at java.text.MessageFormat.<init>(MessageFormat.java:362) ~[?:1.8.0_252]
at java.text.MessageFormat.format(MessageFormat.java:840) ~[?:1.8.0_252]
This release has been heavily refactored. Could you send me please your configuration files. I’ll analyse the issue.
Please find attached both files:
This file was like a “standard” (not created by me)
vaillant_template2.json (13.8 KB)
This file was reduced by me from the “standard VR61” one
VR61_2RO.json (19.2 KB)
Hello @RafalO,
you should remove following section from vaillant_template2.json for the moment as it’s causing an exception.
{
"name": "phase",
"template": [
{"name":"phase1","type":"template","id":"vaillant.templ.phase1"},
{"name":"phase2","type":"template","id":"vaillant.templ.phase2"},
{"name":"phase3","type":"template","id":"vaillant.templ.phase3"}
]
},