[eBUS 2.0] New binding - Release Candidate 7b

witek_1308 · October 11, 2017, 3:19pm

It doesn’t work unfortunately (I put string to hex coded “vr61”), I have the same behaviour as in other non-working things - polling is sent but no info about received telegram.
not sure what’s wrong. What debug here could be helpful? unless address is wrong but in ebusd seems to be 50…

witek_1308 · October 11, 2017, 3:56pm

I checked also other things from my BAI00 e.g. dhw heating runtime d.81 (h) under 22 00. No response, but heating circuit
d.80 (h) under 28 00 works perfectly. it was just copy paste from one to another, so formating should be good, I don’t know why it doesn’t work for me…

fluppie · October 11, 2017, 4:26pm

Here’s a log file from alpha 10 with:
e-service online Ebus Ethernet adapter
Vaillant Ecotec Plus VCW346/5-5
Vaillant Multimatic 700 / VRC 700 (I think this one https://github.com/john30/ebusd-configuration/blob/master/ebusd-2.1.x/en/vaillant/15.700.csv)
Vaillant VR900 Internet module for use with the Multimatic app

eBus bridge address: FF
slave address VRC470: none
master address VRC470: none


tail -F /var/log/openhab2/openhab.log /var/log/openhab2/events.log

2017-10-11 17:23:12.670 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:23:13.146 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:23:13.618 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:23:21.988 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:23:22.115 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:23:22.241 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:23:22.536 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:23:22.738 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:23:22.792 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:23:23.022 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:23:23.118 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:23:23.283 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:23:23.521 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:23:23.730 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:23:23.857 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:23:24.587 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:23:25.062 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:23:25.536 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:23:26.267 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:23:26.744 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:23:27.217 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:23:27.949 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:23:28.423 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:23:28.897 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:23:31.445 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:23:31.500 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:23:31.665 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:23:31.756 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:23:31.811 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:23:32.284 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:23:32.975 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:23:33.448 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:23:33.920 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:27:58.930 [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]

2017-10-11 17:28:04.179 [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]

2017-10-11 17:28:09.399 [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]

2017-10-11 17:28:14.643 [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]

2017-10-11 17:33:27.341 [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]

2017-10-11 17:33:32.588 [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]

2017-10-11 17:33:37.780 [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]

2017-10-11 17:38:16.445 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:38:16.919 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:38:17.394 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:38:24.698 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:38:24.863 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:38:24.920 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:38:25.123 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:38:25.177 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:38:25.382 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:38:25.457 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:38:25.662 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:38:25.831 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:38:26.067 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:38:26.160 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:38:26.363 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:38:26.826 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:38:27.299 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:38:27.774 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:38:28.507 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:38:28.980 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:38:29.453 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:38:30.186 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:38:30.659 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:38:31.132 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:38:31.866 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:38:32.338 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:38:32.811 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:38:34.363 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:38:34.418 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:38:34.778 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:38:35.253 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:38:35.727 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:38:36.199 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:38:55.830 [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]

2017-10-11 17:39:01.033 [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]

2017-10-11 17:39:06.269 [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]

2017-10-11 17:39:11.485 [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]

2017-10-11 17:41:26.822 [INFO ] [ervice.device.EBusDeviceTableService] - DATA TABLE UPDATE EBusDevice [masterAddress=0x10, slaveAddress=0x15, lastActivity=1507736486810, manufacturer=-75(null), deviceId=37 30 30 30 30, softwareVersion=1.1, hardwareVersion=21.03]

2017-10-11 17:41:26.824 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 03 to 15 with command common.identification

2017-10-11 17:44:24.259 [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]

2017-10-11 17:44:29.423 [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]

2017-10-11 17:44:34.679 [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]

2017-10-11 17:44:39.879 [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]

2017-10-11 17:49:52.688 [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]

2017-10-11 17:49:57.885 [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]

2017-10-11 17:50:03.099 [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]

2017-10-11 17:50:08.336 [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]

2017-10-11 17:53:17.995 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:53:18.470 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:53:18.946 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 17:53:27.279 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:53:27.444 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:53:27.532 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 17:53:27.827 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:53:28.031 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:53:28.086 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 17:53:28.314 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:53:28.443 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:53:28.571 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 17:53:28.809 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:53:29.016 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:53:29.182 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 17:53:29.914 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:53:30.388 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:53:30.863 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 17:53:31.596 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:53:32.072 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:53:32.544 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 17:53:33.281 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:53:33.753 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:53:34.225 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 17:53:36.740 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:53:36.795 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:53:37.000 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 17:53:37.050 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:53:37.146 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:53:37.620 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 17:53:38.307 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:53:38.782 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:53:39.256 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 17:55:21.097 [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]

2017-10-11 17:55:26.311 [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]

2017-10-11 17:55:31.560 [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]

2017-10-11 17:55:37.105 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 00 AA]

2017-10-11 17:55:37.411 [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]

2017-10-11 18:00:49.591 [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]

2017-10-11 18:00:54.807 [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]

2017-10-11 18:01:00.055 [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]

2017-10-11 18:01:05.271 [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]

2017-10-11 18:06:18.003 [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]

2017-10-11 18:06:23.247 [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]

2017-10-11 18:06:28.460 [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]

2017-10-11 18:06:33.701 [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]

2017-10-11 18:08:21.176 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 18:08:21.649 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 18:08:22.125 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 18 07 04 00 AD]

2017-10-11 18:08:29.919 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 18:08:29.969 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 18:08:30.175 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 38 07 04 00 42]

2017-10-11 18:08:30.226 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 18:08:30.435 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 18:08:30.489 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]

2017-10-11 18:08:30.713 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 18:08:30.765 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 18:08:30.968 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 75 07 04 00 E7]

2017-10-11 18:08:31.206 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 18:08:31.263 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 18:08:31.467 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 52 07 04 00 09]

2017-10-11 18:08:31.710 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 18:08:32.021 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 18:08:32.495 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 ED 07 04 00 8A]

2017-10-11 18:08:33.231 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 18:08:33.704 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 18:08:34.181 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]

2017-10-11 18:08:34.912 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 18:08:35.388 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 18:08:35.863 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 76 07 04 00 05]

2017-10-11 18:08:36.594 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 18:08:37.067 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 18:08:37.542 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 50 07 04 00 B5]

2017-10-11 18:08:39.473 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 18:08:39.679 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 18:08:39.729 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 EC 07 04 00 D4]

2017-10-11 18:08:39.977 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 18:08:40.452 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 18:08:40.924 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]

2017-10-11 18:11:19.086 [INFO ] [ervice.device.EBusDeviceTableService] - DATA TABLE UPDATE EBusDevice [masterAddress=0x10, slaveAddress=0x15, lastActivity=1507738279073, manufacturer=-75(null), deviceId=37 30 30 30 30, softwareVersion=1.1, hardwareVersion=21.03]

2017-10-11 18:11:19.090 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 03 to 15 with command common.identification

2017-10-11 18:11:30.228 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave CRC invalid! IS:AA SHOULD:A9 [ERROR: SLAVE_CRC_INVALID, DATA: 10 08 B5 04 01 00 3D 00 0A 03 32 10 18 11 10 03 17 60 10 A9]

2017-10-11 18:11:46.439 [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]

2017-10-11 18:11:51.678 [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]

2017-10-11 18:11:56.883 [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]

2017-10-11 18:12:02.119 [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]

Any idea where I should set what master/slave address and how I can read values from the VRC700 module?
DATA TABLE UPDATE EBusDevice [masterAddress=0x10, slaveAddress=0x15, lastActivity=1507738279073, manufacturer=-75(null), deviceId=37 30 30 30 30, softwareVersion=1.1, hardwareVersion=21.03]

So the master address is 10 and slave 15? Right?

csowada · October 11, 2017, 9:02pm

You not set a slave address? This should be set, in you case 15 should be correct.
In your log the device with master address 0x10 try to identify different slaves that are not available in your setup. Can be normal. I have similar ever 12h from my installed Internet interface from Wolf.

csowada · October 11, 2017, 9:05pm

I’m still working on the next version, it’s a bigger update. It should contains all ebusd buildin data types specially for Vaillant. , fix the internal device table etc. But I need more time for this update.

ChrisPe · October 17, 2017, 7:46am

Hi, sorry for the dumb question, but can this binding be installed on a stable oh2 2.1 or is the version 2.2 needed.

The name of the jar file is confusing me a bit.

csowada · October 17, 2017, 2:16pm

Should work, all oh2 builds/ jars are using the next release number.

ChrisPe · October 17, 2017, 3:20pm

Thanks.

So I received my ethernet ebus coupler from esera, and set it as TCP server.
On my previous try it did not install. However since I reinstalled my device from scratch, it installed as intended, and the bridge is now successfully online. However, my first channel tested just report 0 values.

I think I should first validate that the small trigger on the coupler is well position to adjust signal quality. What would be the best method to do that ?

Then I have to activate the debug log and make some test.

ChrisPe · October 17, 2017, 8:28pm

While trying to understand how to configure the Ethernet ebus coupler, I found the full configuration documentation of the WIZ107SR/WIZ108SR configuration tool, so I hope it can be useful for other people. The debug option and Character was completely misleading for me ^^

You can find it there: http://www.wiznet.io/wp-content/uploads/wiznethome/S2E%20Module/WIZ107_108SR/Document/WIZ108SR_UM.pdf

So now I think that ebus binding is communicating with the ebus. I still cannot get any data from Vaillant BAI00 or VRC430/470 things if installed with the recommanded slave/master ids.
Once only the bridge have been configured, I get most of these messages in the log. Can this help me to identify the slave and master id of my system ? I have a VRC470 and an Ecocompact VSC FR 196/2-C 150 boiler:

2017-10-17 22:30:38.421 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:30:42.505 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:30:44.366 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 08 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 00 88 08]
2017-10-17 22:30:48.385 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:30:52.471 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:30:58.350 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:31:04.306 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 0A [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 04 01 00 3D 0A]
2017-10-17 22:31:08.336 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:31:12.430 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:31:18.341 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:31:22.395 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:31:28.293 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:31:32.386 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:31:34.253 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 0A [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 04 01 00 3D 0A]
2017-10-17 22:31:38.279 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:31:42.332 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:31:48.261 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:31:52.341 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:31:58.219 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:32:01.520 [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]
2017-10-17 22:32:02.300 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:32:04.170 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 0A [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 04 01 00 3D 0A]
2017-10-17 22:32:06.833 [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]
2017-10-17 22:32:08.189 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:32:12.181 [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]
2017-10-17 22:32:12.283 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 09 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 11 01 01 89 09]
2017-10-17 22:32:17.509 [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]
2017-10-17 22:32:18.185 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]
2017-10-17 22:32:28.166 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Slave answered with 01 [ERROR: UNEXPECTED_RESPONSE, DATA: 10 08 B5 10 09 00 00 00 64 FF FF 01 00 00 DB 01]

csowada · October 18, 2017, 5:53am

I would try to adjust the adapter, maybe your adjustments are nearly right and some bytes are wrongly interpreted.

ChrisPe · October 18, 2017, 9:46am

I think the adaptor is well adjusted, I double checked and the trimmer is in position just between the position where the ebus activity is off and the position where the ebus activity LED is permanently lit. So the ebus LED activity is blinking like kid’s eyes in front of a christmas tree.

What I’m not 200% sure is the software setting of the coupler. I set it with a static DHCP lease, in TCP server mode, with debug COM disabled and with ‘00’ Character in Serial data packing condition settings. Do you confirm it is the proper settings ?

Using putty in RAW mode I can see continuous data streaming, with mostly unreadeable characters, so I need a Hexadecimal terminal to check the data. Do you have one to recommand please ?

csowada · October 18, 2017, 10:01am

You could use HTerm or Realterm if you use windows. I would set your character property to ‘0’ to disable this feature. But for reading this should not too relevant. You should send/receive any character immediately.

But I would double check the adjustment, I had similar issue with my first installation. Everything looked fine, but I had received to many invalid telegrams. Some bytes where received wrong because the signal was not clear enough.

ChrisPe · October 18, 2017, 11:55am

Regarding the character property, I need to set it with a double 0 otherwise I have an error message. (INVALIDPARAM:PD)

Right now, I get the following raw data from realterm (nice soft, thanks !). What would I look at to determine the reception is optimum or not and if I need to continue to try to adjust the trimmer? For the little I know about ebus protocol, it seems ok for me

Sorry to stay at very basic level, this is very new to me and didn’t find much guideline up to now for this kind of manipulation.

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B5110101
89093A3A901044560000FF4000AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B50401003D0A03424313181003179010ED00AAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAA1008B5100900000064FFFF010000DB01019A00AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B511010189093A3A
901044560000FF4000AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA1008B5100305FF0198000000AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B5100900000064FF
FF010000DB01019A00AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B51101018900093A3A901044560000FF4000AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AA10FEB516080003441318100317C8AAAAAAAAAA1008B512020064AE000000AAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B5100900000064
FFFF010000DB01019A00AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B511010189093A3A901044560000FF4000AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AA1008B50401003D000A03114413181003179010DF00AAAAAAAAAA1008B51101028A05033C96505A
A600AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAA1008B5100900000064FFFF010000DB01019A00AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B511010189093A3A90
1044560000FF4000AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAA1008B51101008808D0010B001F1000800E00AAAAAAAAAA10FEB5160301
9010F5AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAA1008B5100900000064FFFF010000DB01019A00AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B51101018900
093A3A901044560000FF4000AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

ChrisPe · October 18, 2017, 10:03pm

mmmmh, I just installed a fresh Debian vm, installed the last version of ebusd and ebusd-configuration in deb format. I also tried to overwrite with the last version of the configuration file from the git. Then I started ebusd with settings:

ebusd --scanconfig --device=[ebusIP]:5000

Then I logged to the TCP console, and launched a full scan.

Most of the times, the VRC is eventually identified, but only once I got the boiler identified with the config file from the last deb file available (2.10).

The only time I got the boiler identified with the deb file, I got this:

version: ebusd 3.0.595c7c0
signal: acquired
symbol rate: 38
max symbol rate: 113
reconnects: 0
masters: 3
messages: 265
conditional: 0
poll: 0
update: 8
address 03: master #11
address 08: slave #11, scanned “MF=Vaillant;ID=BAI00;SW=0518;HW=7401”
address 10: master #2
address 15: slave #2, scanned “MF=Vaillant;ID=47000;SW=0348;HW=9502”, loaded “vaillant/15.470.csv”
address 26: slave, scanned “MF=Vaillant;ID=47000;SW=0348;HW=9502”
address 31: master #8, ebusd
address 36: slave #8, ebusd

If I try to scan directly the different address, I got:

scan 03
ERR: invalid address

scan 08
ERR: ACK error

scan 10
ERR: invalid address

scan 15
15;Vaillant;47000;0348;9502;21;13;43;0020108128;0082;014542;N8

scan 26
26;Vaillant;47000;0348;9502;21;13;43;0020108128;0082;014542;N8

So apparently something is wrong while trying to communicate with the boiler, which finished to work by pure chance …

FYI, the VRC470 is wired directly to the boiler, and the boiler to the ebus coupler.

csowada · October 19, 2017, 7:42am

I would run the binding and adjust the adapter while watching the console. Now try to reduce the amount of errors.
Another question, his long is your wire from your adapter to your boiler. What type/quality of wire do you use?

ChrisPe · October 19, 2017, 10:54am

I think I will stay to ebusd the time to troubleshoot the issue, which seems somehow to be physical issue. I’ll go back to the binding once this is fixed.

Most, if not all, the messages grabed by ebusd from the ebus coupler starts with 1008B5, so my understanding is that these are messages sent by the VRC470 to the boiler, and I do not see any response. However I know the VRC and boiler are talking together, I can get every data from the boiler on the VRC screen, which compeltly works as intended.

So I agree that something looks messy in the physical communication VRC470 is connected to the boiler with a standard pair of 1.5 mm2 electric wire, with 10 meters long. The wire used between the boiler and the ebus coupler is an old Hifi speaker cable, mayber 0.75 mm2 with 3 or 4 meters long. Both wires are connected to the same plug on the boiler.
It may be an issue but that would not explain why I receive so clearly telegram from the VRC470. Last test I did without success was to switch the ebus cable on the ebus coupler, with no success.

Anyway next tests will be:

Put the coupler close to the boiler with a new cable, maybe it’s impedance related ?
Disconnect the VRC from the boiler and connect only the ebus coupler.

witek_1308 · October 19, 2017, 1:43pm

@csowada,
any chance you have a look why own parsers don’t work (or to be more precise - some of them)

csowada · October 19, 2017, 7:21pm

Hello,

now I’ve release my latest update that is running since this weekend on my productive system. It runs without any issues.

Here is the changelog:

openHAB eBUS 2.0 binding - Alpha 0.0.11 (2017-10-15)

Features:

Update to eBUS library 0.0.11, github
Add new command smarthome:ebus devices to openHAB2 console
Add new logger for unresolved telegrams org.openhab.ebus-ext

eBUS core library - Alpha 0.0.11 (2017-10-15)

Features:

change device table from master address to slave address indexed
complete rewritten internal data types
- simplified class hierarchy
- junit tests for all data types
- property reverseByteorder for nearly all data types
- replaceValue is now available for all data types
new data type date and time, datetime rewritten
enhance data type bcd to support variable length

Bugfixes:

fix a bug where factor was used twice for data type mword
fix all data type to not modify the input byte array
fix data type bcd to only allow value in range of 0-99
fix data type bcd returned as signed value
fix common configuration label, add mappings to status_heat_reqX
fix id in configuration wolf mm
fix manufacture name lookup issue

csowada · October 19, 2017, 7:24pm

Sorry, no. But you should try it with the new version, maybe it is fixed.
You can also use the new command smarthome:ebus devices to identify all your eBUS devices via console.

ChrisPe · October 19, 2017, 10:34pm

Hi,

I can’t download the link in the initial post for this last version (error 404)

Seems it’s a typo, using just https://drive.google.com/uc?export=download&id=0B5Vjy5Qe0CabTVQ2TlZkN3VDeGM works fine.