Ebus binding

Hi,
I’m trying to hookup my Weisshaupt WTC-25 heater via the eBus.
I build the ebus USB interface from Helmut and hooked it up. It looks some values are coming in and testing with the windows realterm serial port debugger indicates that the hardware interface is working.

I see no entries for owners of Weisshaupt systems in the openhab forum using the ebus integration.
I started with the sample binding item file and pruned it down.
I see there is are a few *.map files referenced, but can not find them. Can someone share these?
hu_heat_prog_de.map, hu_status_request1_de.map and hu_status_request2_de.map

currently only values show up for hotwater min temp and boiler temp (target) that seem correct and further values for status request 1 and 2 that would need the maps to turn into some sensible data.

any suggestions welcome.
–Paul–

Hello @pauljanssens,

you are right, we have no configurations for Weisshaupt heating units. Nobody worked with this manufacture yet. So I have no information about the encoding of the telegrams. I had the same problem with Wolf telegrams, nearly no information. So I started to analyze the telegrams and extract value by value. But this was easy with Wolf because the heating unit sends many infirmation by themself.

The value you can receive are the eBus standard telegrams, this should work on any heating unit with eBus. But you are right, I should update the wiki with the map files.

Hi,
I have found some details of the Weisshaupt commands in the below discussion
https://www.symcon.de/forum/threads/20578-User-mit-Weishaupt-Heizung-mit-eBus-Lust-auf-Weishaupt-Codes-zu-entschlüsseln
There is an xls file with some details. ebus parameter 01-13
aktuell.xls
https://www.symcon.de/forum/attachment.php?attachmentid=20387&d=1362383550
I’ll see if I can make some sense of them and modify an existing json to
use them.
To the looks of it have then not completed an integration for it there
as well.
I’m no programmer though, so it will be trial and error…

Hi,

I just started to play around with the binding and the Ebus koppler ethernet, but I’m stuck right at the beginning, I can’t make it connect to OpenHab.
I can ping it’s IP, but the host is unreachable if I put in:

ebus:hostname=jagoebus
ebus:port=5000

If I put in this (its ip) then it comes with an IO error in Openhab.
ebus:hostname=192.168.0.202
ebus:port=5000

The device is set to TCP server.
Any ideas?
Thank you!
Jago

Can you send the error log? You could try to use a program like hterm or realterm to check the connection. If it work you should see many sync symbols (0xAA). If not, you should adjust your adapter.

Btw: Which openHAB version?

Thanks!
It seems like I worked that out, at least I get no more errors on the connection. I have adjusted the screw as well on the ebus ethernet koppler (from eservice.de), but…

This is what I have right now:
I have downloaded From Nikoraes
From this page and copied it in.

ebus:hostname=192.168.0.202
ebus:port=5000
ebus:parserUrl=/opt/openhab/configurations/scripts/vaillant-vrc470-configuration.json
ebus:parsers=custom, vaillant
ebus:senderId=FF

Items:
Number ebus “Temp. outdoor [%.1f °C]” (All) { ebus=“id:controller.temp_outside.temp_outside, cmd:controller.temp_outside, dst:15, refresh:10”}

Error log:
2016-06-10 15:12:04.349 [WARN ] [.o.b.ebus.internal.EBusBinding] - eBus connector still not started, started it yet!
2016-06-10 15:12:04.351 [INFO ] [.o.b.ebus.internal.EBusBinding] - Update eBus Binding configuration …
2016-06-10 15:12:04.354 [ERROR] [.o.b.ebus.internal.EBusBinding] - java.net.MalformedURLException: no protocol: /opt/openhab/configurations/scripts/vaillant-vrc470-configuration.json
java.net.MalformedURLException: no protocol: /opt/openhab/configurations/scripts/vaillant-vrc470-configuration.json
at java.net.URL.(URL.java:586) ~[na:1.8.0]
at java.net.URL.(URL.java:483) ~[na:1.8.0]
at java.net.URL.(URL.java:432) ~[na:1.8.0]
at org.openhab.binding.ebus.internal.EBusBinding.updated(EBusBinding.java:186) ~[bundlefile:na]
at org.openhab.binding.ebus.internal.EBusBinding$1.run(EBusBinding.java:305) [bundlefile:na]

During running there’s nothing, only this during startup.
OpenHAB 1

.8.1.

Thanks a lot!

Your url should start with file:/// for local filesystem

I think the configurations from @nikoraes are already included

Did that, thanks, it started working to some extent.
Item:
Number ebus “Temp. outdoor [%.1f °C]” (All) { ebus=“id:controller.temp_outside, cmd:controller.temp_outside, refresh:10”}

I have set the logging on and have the following stuff - no value in my Item yet. Any idea why?
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;36 36 70 18 35 37 00 00 FF;“7B”;
2016-06-10 17:29:36;“01”;“10”;“FE”;B5 16;“08”;00 33 28 17 10 06 05 16;“07”;;;;;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 12;“02”;00 64;“AE”;“00”;“00”;;“00”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 04;“01”;00;“3D”;“00”;“0A”;03 44 28 17 10 06 05 16 70 18;“64”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;36 36 70 18 35 37 00 00 FF;“7B”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;36 36 70 18 35 37 00 00 FF;“7B”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;02;“8A”;“00”;“06”;01 3C 96 46 82 76;“DF”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:29:36;“01”;“10”;“FE”;B5 16;“03”;01 F0 17;“5E”;;;;;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;36 36 70 18 35 37 00 00 FF;“7B”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;02;“8A”;“00”;“06”;01 3C 96 46 82 76;“DF”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;35 36 70 18 35 37 00 00 FF;“47”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 10;“03”;05 FF 01;“98”;“00”;“01”;01;“9A”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 04;“01”;00;“3D”;“00”;“0A”;03 12 29 17 10 06 05 16 70 18;“4B”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:29:36;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;35 36 70 18 35 37 00 00 FF;“47”;
2016-06-10 17:29:40;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;35 36 70 18 35 37 00 00 FF;“47”;
2016-06-10 17:29:40;“02”;“10”;“08”;B5 12;“02”;00 64;“AE”;“00”;“00”;;“00”;
2016-06-10 17:29:40;“01”;“10”;“FE”;B5 16;“08”;00 32 29 17 10 06 05 16;“1F”;;;;;
2016-06-10 17:29:44;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:29:51;“02”;“10”;“08”;B5 04;“01”;00;“3D”;“00”;“0A”;03 42 29 17 10 06 05 16 70 18;“CA”;
2016-06-10 17:29:51;“02”;“10”;“08”;B5 11;“01”;02;“8A”;“00”;“06”;01 3C 96 46 82 76;“DF”;
2016-06-10 17:29:51;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;35 36 70 18 35 37 00 00 FF;“47”;
2016-06-10 17:29:55;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:30:01;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;36 36 70 18 35 37 00 00 FF;“7B”;
2016-06-10 17:30:01;“01”;“10”;“FE”;B5 16;“03”;01 F0 17;“5E”;;;;;
2016-06-10 17:30:05;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:30:11;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;35 36 70 18 35 37 00 00 FF;“47”;
2016-06-10 17:30:11;“02”;“10”;“08”;B5 11;“01”;02;“8A”;“00”;“06”;01 3C 96 46 82 76;“DF”;
2016-06-10 17:30:15;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:30:17;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;35 36 70 18 35 37 00 00 FF;“47”;
2016-06-10 17:30:21;“02”;“10”;“08”;B5 04;“01”;00;“3D”;“00”;“0A”;03 13 30 17 10 06 05 16 70 18;“FF”;
2016-06-10 17:30:25;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-10 17:30:27;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;35 36 70 18 35 37 00 00 FF;“47”;

I got it half-working with the following config:
ebus:parserUrl=platform:/base/…/configurations/ebus-config.json
ebus:parsers=custom
I have renamed the vaillant-vrc470 to ebus-config.

My item:
Number ebus “Temp. outdoor [%.1f °C]” { ebus=“id:controller.temp_outside.temp_outside, cmd:controller.temp_outside, dst:08, refresh:30”}

Unfortunately it doesn’t display anything at all, and my ebus log is like this:

2016-06-11 07:54:17;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-11 07:54:22;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;44 45 30 10 3E 42 00 00 FF;“CE”;
2016-06-11 07:54:22;“02”;“10”;“08”;B5 11;“01”;02;“8A”;“00”;“06”;01 3C 96 46 82 76;“DF”;
2016-06-11 07:54:26;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-11 07:54:32;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;44 45 30 10 3E 42 00 00 FF;“CE”;
2016-06-11 07:54:32;“02”;“10”;“08”;B5 04;“01”;00;“3D”;“00”;“0A”;03 02 54 07 11 06 06 16 30 10;“6D”;
2016-06-11 07:54:36;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-11 07:54:38;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;44 45 30 10 3E 42 00 00 FF;“CE”;
2016-06-11 07:54:42;“02”;“10”;“08”;B5 10;“03”;05 FF 01;“98”;“00”;“01”;01;“9A”;
2016-06-11 07:54:46;“02”;“10”;“08”;B5 10;“09”;00 00 00 FF FF FF 01 FF 00;“5D”;“00”;“01”;01;“9A”;
2016-06-11 07:54:52;“02”;“10”;“08”;B5 11;“01”;01;“89”;“00”;“09”;44 45 30 10 3E 42 00 00 FF;“CE”;
2016-06-11 07:54:52;“02”;“10”;“08”;B5 12;“02”;00 64;“AE”;“00”;“00”;;“00”;
2016-06-11 07:54:52;“01”;“10”;“FE”;B5 16;“08”;00 24 54 07 11 06 06 16;“60”;;;;;

So there is communication, but I don’t know what is “10” and “08” - I suppose 10 is the VRC470, but in the json and every example everyone set dst as 15, which confuses me.
Even though if I change the dst-s in the json from 15 to 10 or 08 it doesn’t make any difference.
Also, do I need the cmd part in the item or not really?
On top of that I don’t see anything happening in the events…

Thanks a lot!

Made it work. Turns out the problem was the setting on the koppler’s serial setting “C” was set to FF instead of 00 and in openhab both vrc470 and bai00 had to be set.

For the reference of newcomers:
Ebus Koppler Ethernet (eservice.de) with Vaillant VRC470 and Ecotec Plus, connected to the boiler’s Ebus pins.
Network settings: TCP server
Serial:
Enable debug message output. Leave the fields unchange (2400/8/none/1/none). Time/Size/Character: 0/0/00
Serial command switch mode enable 01 02 03
Options: leave alone

Openhab:

Warning: Only use ebus.hostname or ebus.serialPort

ebus:hostname=192.168.0.202 (or your coupler’s ip)
ebus:port=5000
no custom ebus parser set
ebus:parsers=vaillant-vrc470,vaillant-bai00

Items:
Number Ebus “Temperature outside [%.1f °C]” (All, gGroundFloor) { ebus=“id:controller.temp_outside.temp_outside, dst:15, refresh:60” }
Number Ebusb “Temperature room [%.1f °C]” (All, gGroundFloor) { ebus=“id:controller.temp_room_disp, refresh:10”}

This works.

I have the Ecotec plus 637 system boiler too. You’re getting the overshoot because with Vaillant eBus controls (vrt 350, vrc 470, with a vr65 or vr66 wiring center (for your 2 or 3 port valves), the boiler knows via ebus what the current room temperature reported by your controller is and the current temperature is in your hot water cylinder (via the NTC module for the Vaillant cylinder or for a normal non-Vaillant pressurised cylinder there is a cylinder thermostat that ‘clicks on’) and automatically adjusts the flow temperature to suit the temperature being reported so that it only burns the minimal amount of gas that’s needed.

With just a relay, it ramps up to 100% of the flow temperature set in the boiler because it’s not being told what the current temperature is which it normally can use to decide what to do (by default this is 75 degrees and recommended you stick to it). With eBus it’s more efficient and burns less gas and saves your bills, if it knows what the current temp is it will automatically reduce the target flow temperature.

For central heating 75 degrees is fine, for water you probably want it quite a bit less as target water temp in the cylinder tends to be ~60 degrees (to stop the perfect conditions for legionella bacteria and legionnaires disease growing inside your system and causing you to get sick), any more is too hot for most people as you will probably waste it by mixing it with cold water at your tap and shower anyway.

Now with ebusd and openhab, you could build a controller via openhab to handle it all, openhab 2 allows you to take action based on the information, i.e if cylinder temp drops a certain threshold, tell the boiler to switch on and give it a flow temp to hit, if the room temperature drops by a certain threshold to set the boiler flow temp etc.

However, you are better off with Vaillant controls. They’re not hard to wire up and the instructions are included (I did it all by myself). This is because the boiler has a heat curve already set inside by Vaillant engineers to allow it to be most efficient, which is better than trying to tell the boiler what to do when it already knows how, it just needs to know target temps and when you want it to come on.

What I use (or trying to use again as I haven’t touched it in a year) openhab for is to simply monitor what is going on via my phone or web browser and I can get email alerts for things such as error codes (when it gets a fault) or if the pressure goes up to the red (My heat exchanger failed due to overpressure recently so I had to have the boiler replaced :sweat: )

You can’t use both however, there is a bridged ebus terminal behind the boiler PCB that you remove if you use ebus or the 24v bridge for 24v controllers, or 240v controllers, you can only run one or the other otherwise the boiler won’t respond.

Do you have the wiring center connected (vr65/vr66) or is it just a normal 240v junction box that wires the port valve(s) at your cylinder to the boiler? you would probably want a vr66 (vr65 is now replaced by a vr66) to control the valves, then via ebus you can tell the boiler what you want and it will tell the wiring center to open the valves. Having a controller too is much better as a fall back option if your openhab setup fails.

I’ll try porting my old config to openhab 2, I started writing a blog about it so I’m trying to set up a full guide.

Hi Christian! This is Harpinder from the Google Groups that existed before the Openhab community page. I’m trying to update my openhab installation. I installed openhab 2 via the official repository and then via the paper UI installed the ebus binding. I noticed above the syntax has changed for the items file but I can’t click on the link as it says page not found on Gibhub, is there an updated link for this somewhere?

Also I tried using the ebus parserurl for my custon ebus-config.json which is in /etc/openhab2 (the new openhab2 configuration location) but I am getting this error:

2016-10-31 02:12:56.254 [INFO ] [ab.binding.ebus.internal.EBusBinding] - Update eBus Binding configuration …
2016-10-31 02:12:57.716 [ERROR] [ab.binding.ebus.internal.EBusBinding] - Unable to load file testing-configuration.json …
2016-10-31 02:12:57.721 [ERROR] [org.apache.felix.configadmin ] - [org.osgi.service.cm.ManagedService, org.osgi.service.event.EventHandler, id=337, bundle=199/mvn:org.openhab.binding/org.openhab.binding.ebus/1.9.0-SNAPSHOT]: Updating property general of configuration org.openhab.ebus caused a problem: java.io.FileNotFoundException: /usr/share/openhab2/runtime/karaf/system/org/eclipse/birt/runtime/org.eclipse.osgi/configurations/ebus-config.json (No such file or directory)

So I take it the location “parserUrl=platform:/base/…/configurations/ebus-config.json” in my /etc/openhab2/services/ebus.cfg is no longer correct?

EDIT I tried using this:
“parserUrl=file:///etc/openhab2/ebus-config.json” which seemed to work but then my items file that was for version 1.7.0 wouldn’t work because the syntax has changed for the new openhab2 beta.

Ok, I stopped using openhab2 since I just can’t get it to work with the ebus binding, it’s still in beta!

Back to openhab 1.8.0!

I’ve used my old configuration I used with 1.7.0 using my ebus-custom.json file and I get this:

2016-10-31 15:55:47.950 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d13CirPump! Check your item configuration.
2016-10-31 15:55:48.937 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d47OutsideTemperature! Check your item configuration.
2016-10-31 15:55:48.962 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 10 09 00 00 00 78 FF FF 01 FF 00 F8 00 01 01 9A 00 AA
2016-10-31 15:55:48.963 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-10-31 15:55:49.916 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d10WP! Check your item configuration.
2016-10-31 15:55:49.967 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d44IonisationVoltageLevel! Check your item configuration.
2016-10-31 15:55:50.249 [DEBUG] [.ebus.internal.parser.Analyses] - 03 64 B5 12 02 02 FE 98 00 06 FE 00 00 80 FF FF 6C 00 AA
2016-10-31 15:55:50.250 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-10-31 15:55:51.004 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d3HWCTemp! Check your item configuration.
2016-10-31 15:55:51.956 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d23SummerWinter! Check your item configuration.
2016-10-31 15:55:52.969 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 11 01 01 89 00 09 70 6B 00 80 FF FF 00 00 FF 6B 00 AA
2016-10-31 15:55:52.970 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-10-31 15:55:54.276 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d90EBusHeatControl! Check your item configuration.
2016-10-31 15:55:54.283 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item HC1NightTemp! Check your item configuration.
2016-10-31 15:55:54.958 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d36HWCWaterFlow! Check your item configuration.
2016-10-31 15:55:54.998 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 04 01 00 3D 00 0A 00 FF FF FF FF FF FF FF 00 80 3B 00 AA
2016-10-31 15:55:54.999 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-10-31 15:55:55.625 [DEBUG] [.ebus.internal.parser.Analyses] - 03 64 B5 12 02 02 FE 98 00 06 FE 00 00 80 FF FF 6C 00 AA
2016-10-31 15:55:55.626 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-10-31 15:55:56.048 [ERROR] [o.b.e.i.c.EBusCommandProcessor] - Error while running runnable …
java.lang.NullPointerException: null
at org.openhab.binding.ebus.internal.parser.EBusConfigurationProvider.getCommandById(EBusConfigurationProvider.java:259) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeEBusTelegram(EBusCommandProcessor.java:170) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeSendData(EBusCommandProcessor.java:311) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor$1.run(EBusCommandProcessor.java:102) ~[na:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]

Any ideas what could be causing this? My site loads but the values are blank so it’s not taking any values. Running ebusd and checking the ebusd log I get plenty of output which seems to be ok so the coupler is working fine:

2016-10-31 16:01:17.365 [main notice] ebusd 2.2.65328e5 started
2016-10-31 16:01:17.380 [main notice] found messages: 11 (0 conditional on 0 conditions, 0 poll, 4 update)
2016-10-31 16:01:17.495 [bus notice] signal acquired
2016-10-31 16:01:17.979 [bus notice] new master 03, master count 2
2016-10-31 16:01:18.025 [update notice] unknown MS cmd: 0364b5120202fe / 06fe000080ffff
2016-10-31 16:01:23.422 [update notice] unknown MS cmd: 0364b5120202fe / 06fe000080ffff
2016-10-31 16:01:23.457 [bus notice] new master 10, master count 3
2016-10-31 16:01:23.520 [update notice] unknown MS cmd: 1008b5110101 / 096d680080ffff0000ff
2016-10-31 16:01:25.434 [update notice] unknown BC cmd: 10feb516080017011631100116
2016-10-31 16:01:25.675 [update notice] unknown MS cmd: 1008b512020064 / 00
2016-10-31 16:01:27.383 [main notice] starting initial scan for fe
2016-10-31 16:01:27.743 [main notice] read common config file /etc/ebusd/vaillant/broadcast.csv
2016-10-31 16:01:27.745 [main notice] read common config file /etc/ebusd/vaillant/scan.csv
2016-10-31 16:01:27.750 [main notice] read scan config file /etc/ebusd/vaillant/08.bai.csv for ID “bai00”, SW0609, HW5502
2016-10-31 16:01:27.795 [main notice] found messages: 209 (3 conditional on 23 conditions, 1 poll, 8 update)
2016-10-31 16:01:28.430 [bus notice] poll scan.08 id:
2016-10-31 16:01:28.780 [update notice] unknown MS cmd: 0364b5120202fe / 06fe000080ffff
2016-10-31 16:01:29.939 [main notice] read scan config file /etc/ebusd/vaillant/15.350.csv for ID “35000”, SW0109, HW7102
2016-10-31 16:01:29.939 [main notice] found messages: 408 (7 conditional on 26 conditions, 1 poll, 8 update)
2016-10-31 16:01:32.083 [main error] unable to load scan config 64: no file from /etc/ebusd/vaillant with prefix 64. found
2016-10-31 16:01:33.666 [bus notice] poll scan.08 id:
2016-10-31 16:01:34.024 [bus notice] max. symbols per second: 115
2016-10-31 16:01:34.147 [update notice] unknown MS cmd: 0364b5120202fe / 06fe000080ffff
2016-10-31 16:01:35.524 [update error] unable to parse bai DateTime from 1008b5040100 / 0a00ffffffffffffff0080: ERR: argument value out of valid range
2016-10-31 16:01:35.782 [update notice] update bai Status02 QQ=10: auto;60;75.0;70;70.0
2016-10-31 16:01:37.506 [update notice] update bai Mode QQ=10: standby
2016-10-31 16:01:39.641 [bus notice] poll scan.08 id:
2016-10-31 16:01:43.521 [update notice] update bai Status01 QQ=10: 54.5;52.0;-;-;-;off
2016-10-31 16:01:44.921 [update notice] unknown MS cmd: 0364b5120202fe / 06fe000080ffff
2016-10-31 16:01:45.615 [bus notice] poll scan.08 id:
2016-10-31 16:01:47.518 [update notice] update bai Mode QQ=10: standby
2016-10-31 16:01:50.279 [update notice] unknown MS cmd: 0364b5120202fe / 06fe000080ffff
2016-10-31 16:01:51.636 [bus notice] poll scan.08 id:
2016-10-31 16:01:53.536 [update notice] update bai Status01 QQ=10: 54.5;52.0;-;-;-;off
2016-10-31 16:01:55.509 [update notice] update bai Status02 QQ=10: auto;60;75.0;70;70.0

The unknown ones are for my VR66 wiring center (device id 64) (TimeClocks Archives | UK Plumbing) which is unknown at the moment so ignore those as I haven’t figured out what they are otherwise I could have created my own json file to guess what it’s doing. The ebusd creator hasn’t got the commands for it and itss a common device in the UK but doesn’t seem to be in Germany which uses the vrc controllers and their wiring centers.

So,

I checked the wiki page and I’ve corrected a wrong link. But in general the binding is compatible to oh2 and should work in 1.8 and 2.0. It looks like you are using wrong ids. Could you attach you items configuration for the ebus items.

Here an example og the new ids (since oh 1.8)

ebus="id:controller.temp_outside, refresh:60"

Ah, my items is from 1.7.0.

I’m using a custom ebus-config.json so I didn’t think I needed to use the controller. prefix.

Here is a snippet of my ebus-config.json:

{
“comment”: “VRT 350 current room temperature”,
“id”: “displayedroomtemp”,
“class”: “350”,
“command”: “B5 09”,
“data”: “0D 80 00”,
“dst”: “15”,
“values”: {
“displayedroomtemp”: {“type”: “data2c”, “pos”: 12, “label”: “Room temperature displayed on vrt350”},
“displayedroomtemp_s”: {“type”: “byte”, “pos”: 14, “label”: “Room temperature status”}
}
},

And then the item in my ebus.items:

Number DisplayedRoomTemp “Current room temperature:[%.2f]” { ebus=“id:displayedroomtemp, class:350, cmd:displayedroomtemp, dst:15, refresh:60” }

Would this now be different? i.e. ebus="id:350.displayedroomtemp

Yes, class and id now combined with a dot.

Thanks, I’ve now changed my items file like this:

Number DisplayedRoomTemp “Current room temperature:[%.2f]” { ebus=“id:350.displayedroomtemp, cmd:displayedroomtemp, dst:15, refresh:60” }

Number HC1OpMode “CH operating mode(0=off;1=manual;2=auto):[%.0f]” { ebus=“id:350.hc1opmode, cmd:hc1opmode, dst:15, refresh:60” }

Number HWCOpMode “DHW operation mode(0=off;1=manual;2=auto):[%.0f]” { ebus=“id:350.hwcopmode, cmd:hwcopmode, dst:15, refresh:60” }

Number HWCCircuitActive “Is DHW active?[%.0f]” { ebus=“id:350.hwccircuitactive, cmd:hwccircuitactive, dst:15, refresh:60” }

However I get this in the logs:

2016-11-01 16:21:23.410 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d23SummerWinter! Check your item configuration.
2016-11-01 16:21:23.411 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d5FlowTempDesired! Check your item configuration.
2016-11-01 16:21:23.521 [WARN ] [i.c.AbstractEBusWriteConnector] - Slave CRC wrong, resend!
2016-11-01 16:21:23.525 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision detected! 0x00
2016-11-01 16:21:23.530 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 08 B5 09 03 0D 17 00 52 00 03 00 00 A9 01 00 AA
2016-11-01 16:21:23.532 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 16:21:24.343 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d10WP! Check your item configuration.
2016-11-01 16:21:24.395 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item HC1NightTemp! Check your item configuration.
2016-11-01 16:21:25.360 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d47OutsideTemperature! Check your item configuration.
2016-11-01 16:21:25.393 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d13CirPump! Check your item configuration.
2016-11-01 16:21:25.424 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d34ActualFanSpeed! Check your item configuration.
2016-11-01 16:21:26.532 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 11 01 01 89 00 09 3E 3C 00 80 FF FF 00 00 FF C9 00 AA
2016-11-01 16:21:26.533 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-11-01 16:21:26.972 [DEBUG] [.ebus.internal.parser.Analyses] - 03 64 B5 12 02 02 00 66 00 06 00 00 00 80 FF FF 08 00 AA
2016-11-01 16:21:26.980 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-11-01 16:21:27.413 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d44IonisationVoltageLevel! Check your item configuration.
2016-11-01 16:21:28.563 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 04 01 00 3D 00 0A 00 FF FF FF FF FF FF FF 00 80 3B 00 AA
2016-11-01 16:21:28.564 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-11-01 16:21:30.405 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d91DCFState! Check your item configuration.

Remove the cmd part, this is now only required if you set values not for polling.