[eBUS 2.0] New binding - Release Candidate 7b

Hello @csowada ,

thank you, for your information.
Is there a standard-thing, what i can use for show the value or a way to build a thing ?

You could try to add a VRC430 thing with source address 0x26, it looks like that some commands are compatible with vrc430. But I will change the log level for this information to debug on release.

I know this problem, but I have not found a good solution to refresh the things. I thing in your case the best is to recreate the thing. Sorry

Yes, this is not unusual. I have the same here with my Wolf unit.

Hi! to everyone here in this great thread.
I’m tried to get this binding running with my configuration:

Vaillant felxoTHERM exclusive  / VWF 117/4 
multiMATIC 700 / VRC700/1
Internetkommunikationsmodul VR900

openhab> smarthome:ebus  devices
MA | SA | Identifier     | Device         | Manufacture               | ID | Firmware   | Hardware   | Last Activity
---+----+----------------+----------------+----------------------+----+------------+------------+---------------------
FF | 04 |                | <interface>    | eBUS Library              |    | null       | null       | ---
10 | 15 | 37 30 30 30 30 | ---            | Joh. Vaillant GmbH & Co.  | B5 | 1.1        | 21.03      | Thu Jan 11 17:39:21 CET 2018
00 | 05 |                | ---            | null                      |    | null       | null       | Thu Jan 11 17:24:10 CET 2018
01 | 06 |                | ---            | null                      |    | null       | null       | Thu Jan 11 17:38:20 CET 2018
   | E1 |                | ---            | null                      |    | null       | null       | Thu Jan 11 17:30:23 CET 2018
   | E0 |                | ---            | null                      |    | null       | null       | Thu Jan 11 17:38:31 CET 2018
----------------------------------------------------------------------------------------------------------------------

I use the esera ebus ethernet interface, with the recommended settings: 2400/8/n/1, no flow control, serial data packing conditions: timer:0 size:0 char: 00

currently with my first steps i only check the broadcasts and don’t poll any values.
i can read the date/time and the outside temperature without any problems:

2018-01-13 20:01:15.987 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.datetime
2018-01-13 20:01:15.994 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) with id ebus:vrc430:a916041f ...
2018-01-13 20:01:16.031 [vent.ItemStateChangedEvent] - ebus_vrc430_a916041f_vrc430_controller_bc_datetime_datetime changed from 2018-01-13T19:59:16.528+0100 to 2018-01-13T20:01:16.986+0100

2018-01-13 20:27:24.973 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.temp_outside
2018-01-13 20:27:24.978 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) with id ebus:vrc430:a916041f ...
2018-01-13 20:27:25.007 [vent.ItemStateChangedEvent] - ebus_vrc430_a916041f_vrc430_controller_bc_temp_outside_temp_outside changed from 2.5625 to 2.75

but i’m getting a lot of errors all the time (failed ratio: 92%; unresolved ratio: 78%)

2018-01-13 19:59:25.323 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 10 76 B5 11 01 01 16 00 AA]
2018-01-13 19:59:25.868 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 10 08 B5 10 09 00 00 38 FF FF FF 06 00 00 19 00 AA]
2018-01-13 19:59:35.065 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 10 08 B5 11 01 01 89 00 AA]
2018-01-13 19:59:35.603 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 10 76 B5 12 03 0F 00 01 FC 00 AA]
2018-01-13 19:59:36.149 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 10 76 B5 10 09 00 00 00 FF FF FF 01 00 00 85 00 AA]
2018-01-13 19:59:45.388 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 10 76 B5 11 01 01 16 00 AA]
2018-01-13 19:59:45.933 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 10 08 B5 10 09 00 00 38 FF FF FF 06 00 00 19 00 AA]

now i’m struggeling since days to clean this errors maybe someone could help. :frowning:

Hello!
Configuration file for VRC 700 will be available in couple days.
You can check for progress here. ([eBUS 2.0] Configuration support/contribution)

great to know there are others with a vrc700!
i will spend some time in learing about creation of jsons files and telegram analysis.
hope to be able to help soon.
if you have anything to test or double check - i will give my best.

Did anyone tried to implement Wolf CWL300/400. I have a running version with ebusd.
How simple is it to move this working version from ebusd to this ebus binding (ebusd config → binding config)?

The first step is the hardest. The rest ist simple. So you can send me the ebusd configuration and I can prepare a skeleton as start point for you.

3c.wolf-cwl-excelent-300.csv.xml (8.1 KB)

Its a csv, had to change extension to xml.

Thanks in advanced

Could you also send me some byte telegrams as example to test the the configuration file?

Hello @lukics,

we should discuss your configuration in this thread

I have dropped your proposed config into json file and configured the bridge to pick it up.
I got the wolf-cwl thing in the inbox, which I accepted.
image


I created intems out of the thing channels.

Number   WolfCWL3C_CwlAcTempInsideTempInside   "Temperature Inside"    {channel="ebus:cwl:46e9051d:3C:cwl_ac_temp-inside#temp-inside"}
Number   WolfCWL3C_CwlAcTempOusideTempOuside   "Temperature Outside"   {channel="ebus:cwl:46e9051d:3C:cwl_ac_temp-ouside#temp-ouside"}

Though the channels do not deliver any value


What did I wrong?

You have to set up polling for getter commands if you haven’t allready.
PaperUI > Configuration > Things > Wolf CWL (3C) > Edit > SHOW MORE > Polling all channels

Works now,
Thanks a lot to you and special to csowada for the great work/support.
I will now move from ebusd in next days.

One question regarding the configuration files. Is it possible to subtract two values. At the moment i’m working on a configuration for the VR90 and the room temperature is represented as the raw value from which the self heating must be subtracted.

Helo,

Why on new binding Alpha 15 not read all values? My heating unit is Vaillant and controller is VRC 450. New binding not read this values:

  • dhw_runtime
  • dhw_starts
  • heating_runtime
  • heating_starts
    Why parameter boiler_state_gas_valve is read as string but data is integer (240 when valve is off and 15 when valve is on)?

Best regards
Pawel

Hello,

In logs ebus binding generate a error like this:

2018-01-19 10:54:49.038 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Poll command “ebus:vrc430:e95bc9f2:vrc430_heating_temp-d-day#temp-d-day” with “FF 15 B5 09 03 0D 27 00 1A” …
2018-01-19 10:54:49.162 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address FF to 15 with command heating.temp_d_day
2018-01-19 10:54:49.166 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) with id ebus:vrc430:e95bc9f2 …
2018-01-19 10:54:49.200 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Poll command “ebus:bai:fcb160b9:08:bai_boiler_temp-d-flow-ext#temp-d-flow-ext” with “FF 08 B5 09 03 0D 6E 04 4A” …
2018-01-19 10:54:49.215 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Poll command “ebus:bai:fcb160b9:08:bai_dhw_state-dhw-demand#state-dhw-demand” with “FF 08 B5 09 03 0D 58 00 74” …
2018-01-19 10:54:49.361 [ERROR] [e.csdev.ebus.core.EBusControllerBase] - Error while firing onTelegramReceived events!
java.lang.ArrayIndexOutOfBoundsException: null
at java.lang.System.arraycopy(Native Method) ~[?:?]
at de.csdev.ebus.command.EBusCommandUtils.decodeValueList(EBusCommandUtils.java:369) [12:org.openhab.binding.ebus:2.2.0.201712041912]
at de.csdev.ebus.command.EBusCommandUtils.decodeTelegram(EBusCommandUtils.java:422) [12:org.openhab.binding.ebus:2.2.0.201712041912]
at de.csdev.ebus.service.parser.EBusParserService.onTelegramReceived(EBusParserService.java:94) [12:org.openhab.binding.ebus:2.2.0.201712041912]
at de.csdev.ebus.core.EBusControllerBase$2.run(EBusControllerBase.java:101) [12:org.openhab.binding.ebus:2.2.0.201712041912]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
2018-01-19 10:54:49.565 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address FF to 08 with command dhw.state_dhw_demand

Hi all,

@csowada, first od all, thank you for your great work.

I would like to implement eBUS in my system. I am owner of Vaillant ecoTEC plus VUW INT I 206/5-5, but nothing else. This gas heater with hot water boiler is equipped with eBUS, and I would like that my current openHAB setup simulate some thermostat control. Is that possible?

My adapter is from FHEM wiki (link). It’s built and tested on table, and now I would like to connect it for some tests, so I have few questions:

  1. If I connect adapter to heater, should I see any output, as there is nothing else on bus?

  2. If not, what do you suggest, how to initiate communication?

  3. Could you give me some clues what is minimum needed on eBus binding configuration to start seeing some data?

branek

Hi @branek,

which version of the bus interface do you have? The 1.6 or the new 2.0 version?

If you connect the device to the heater, you should normally see the “heartbeat” <aa and i think at least a broadcast for the date and time.

To check if your device is working properly, look at the section “Poti abgleichen” in the link you posted. Therefore you need to install the ebusd-service. If you install the latest version, you also need to start the service with the option --raw-bytes (not 100% sure if this is the option, look in the man-page) to see the raw bytes.