I’ve also implemented the ebus 2.0 (Alpha 15) binding with success. We use a Vaillant Ecotec plus heater a VR61 module, a VRC470 (HC2) and a VR80 (HC1) thermostate. I saw 5 ebus things appearing in the list : ebus bridge, ebus standard, ebus standard(8), ebus standard(15) and ebus standard(50).
Does it mean that address 50 is used for the VR61 module?
In the control tab of the paperUI i see a set of parameters, but not all the data is coming thru (NaN). I suppose the mapping is not correct? Do i need to adapt some settings in the config.json file?
@csowada thank you for developing this binding and for kindly support!
I am new to OpenHAB, bindings, configurations etc, but somehow got my setup to work. (OpenHAB2 on OrangePI, eBUS 2.0 Alpha 15, Vaillant 306-5/5, eRelax controller, homemade eBUS adapter https://www.mikrocontroller.net/topic/346833)
My problem is many failed telegrams and I couldn’t find any solution in other topics.
First problem is master CRC when polling my boiler. How there could be master CRC error if in this case master is eBUS binding itself??? Why is sixth byte from error log (09) different than sent one(0D)?
The bus is a shared medium, so if another device sends a byte while the binding is sending it causes wrong bytes. But this is not unusual, this is the reason why this is only available on log level debug.
Yes, definitely a bug. I will fix this with the next release.
Thank you for quick response. I will reply with 3 more questions
Currently there is 20-30 parameters for polling in 20 sec time slots. Beside boiler and room controller there is no other devices. Is it too frequent?
My boiler is occasionally sending command B5 12 to address 64
14:35:26.817 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 03 64 B5 12 02 02 FE 98]
It is sending internal pump status to external pump and that command doesn’t need slave response, ACK only.
I tried to make custom configuration to solve those telegrams, but binding is seeking for slave response (data?). Is it possible to configure binding to send slave ACK only?
This is my custom .json:
I can add a thing, but there is no telegram handling. There is “there is no slave response” error.
ebus-wiki.org is down last several days. Is there another source of information about aplication layer of protocol? I would like to contribute and make a configuration file for Vaillant E-Relax controller.
Sorry, but I’m new in OH2 and Bindings.
I have OH2, with ebus2.0 Binding on a Vaillant VR630 Heating-System.
When I added the ebus-Things in simple Mode there are no values in the items.
The Log shows me a lot of unhandled telegrams.
What can I do, that I get the values in OH?
2018-01-04 18:19:41.546 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 26 with command boiler.control.datetime
2018-01-04 18:19:41.547 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.datetime from 10 to 26 …
2018-01-04 18:19:41.912 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 26 with command boiler.temp_d_cylinder
2018-01-04 18:19:41.914 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.temp_d_cylinder from 10 to 26 …
2018-01-04 18:19:43.529 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-01-04 18:19:43.532 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 …
2018-01-04 18:19:52.026 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 26 with command boiler.temp_d_cylinder
2018-01-04 18:19:52.028 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.temp_d_cylinder from 10 to 26 …
2018-01-04 18:19:53.579 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-01-04 18:19:53.583 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 …
This a not really a problem, the ebus parser was able to resolve a telegram but there was no openhab ebus thing registered to use this result. This is not a really a INFO message, more a TRACE message.
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 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.
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)?
