Hi,
Having some trouble getting set up and hope someone can help.
I’m running OH2 and have installed the latest binding. This is running ok and is talking with my ebus interface (ESERA RS232) though FTDI on /dev/ttyUSB0, which is connected to a Vaillant VRC 470f directly to the boiler unit. The problem I have is that I cannot for the life of me get it to recognise any telegrams - everything is marked as failed.
I have been through the hardware setup instructions for ebusd and tried adjusting the potentiometer for hours. I am not able to get a stable AA heartbeat, just a few blocks every now and then. The stable signal position gives the results seen below.
In the logs, the most common error is “Telegram starts with an invalid source address!” which happens 3/4 times a second. Each time the source address listed is different. Log snippet at bottom.
I suspected it might have been a bad connection but have since replaced the cable with solid core, twisted pair CAT6 (ebus spec compliant) which made no difference.
Update - 24th Feb
I have a strong suspicion that the ESERA coupler is at fault and am following in ChrisPe’s footsteps by ordering the new v2.1 ebus interface from John30 et al on the FHEM forums. They are putting it together and testing it beforehand so hopefully everything will be good soon. Shall update again once it arrives.
Update - 12th March
It has arrived and it works! Very disappointed in ESERA - the coupler was not cheap and their support was non-existant. I can only recommend you don’t buy from them and instead get something from FHEM instead. Now onto the next issue of unidentified telegrams…
Log
18:44:39.824 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data -12
18:44:39.869 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data -13
18:44:39.909 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data -14
18:44:39.953 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data -15
18:44:39.997 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data -16
18:44:40.125 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data -17
18:44:40.168 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from LENGTH1 to UNKNOWN
18:44:40.168 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA]
18:44:40.648 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:40.694 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:40.694 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! FD [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
^Z [1] suspended log:tail
openhab> 18:44:41.816 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:41.860 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:41.860 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! D5 [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
18:44:42.033 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:42.073 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:42.073 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! AE [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
18:44:42.684 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:42.727 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:42.727 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! F5 [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
18:44:42.816 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:42.857 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:42.857 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! BE [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
18:44:43.419 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:43.461 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:43.461 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! AB [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
18:44:43.718 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:43.763 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:43.763 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! AE [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
18:44:43.893 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:43.978 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:43.978 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! DF [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
18:44:44.023 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
18:44:44.109 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
18:44:44.110 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! F5 [ERROR: INVALID_SOURCE_ADDRESS, DATA: FF DD F5 FD F5 FD FD F5 FE DD F5 AA FD AA AA F5 F5 FD AE D5 FF AF FE F5 FD FD F7 EE D5 EE AA EA AA FF AA FF FA AA 60 D8 DF F2 72 6C 13 67 7A 05 AD D2]
Hex Dump
0000000 fdee fbd7 aaaf f5eb d7d5 defd aaf5 d5ab
0000010 ebd5 fdf7 fdd5 fffd aad5 d7d5 12ab f5ca
0000020 6871 69f0 8e5f 4012 5a14 a2fc d7f5 ddf7
0000030 aafa faab f5aa ae86 baf5 d5fd f5d5 baaa
0000040 ead5 aaab eafd d7df d5dd abff aafe d5d5
0000050 bafd fe98 8336 c1c4 d7ff fddd abab aad6
0000060 aaf5 d5ea f5aa d5bf cb82 c1d5 82aa c0aa
0000070 bed5 d5af abff aafd abab fdd5 bad5 aaae
0000080 aaff baab baaa d7ee aaea d5fc d5ba ffd5
0000090 d7aa bfff fdab bbba aeaa bed5 ddff d5d5
00000a0 aad5 f7ea acd5 6398 3071 c971 a997 0ece
00000b0 d54d aaab dfbf abba faea d5df d5fc f5fd
00000c0 f7aa aaaa ebfd ebc1 ffaa d7d7 ddab fdef
00000d0 fdbf d5d5 abab aaaa f585 d5f5 afd5 aadd
00000e0 d7fd abf7 ddd7 fdaa aaf7 f5aa bbf5 aed7
00000f0 d5ab f5d7 aaab aaf4 ffeb beaa fdf5 ea8b
0000100 eaeb d3c5 f1bb 8deb 4244 3ad5 2b94 4746
0000110 f5e2 abaa d5aa 8bff abd5 aaea d5dd bbaa
0000120 d5d5 abf4 aafa c0ba ddf7 aeab f5f5 aad5
0000130 d5ff ffaa abae baae ddd5 97c2 6f2d 3ee7
0000140 40e0 4691 67a6 64f9 eaae caee d587 d7f5
0000150 d5dd aef5 f7fd fde8 87ba baaa fafd ebf5
0000160 c8aa d5ab f5d7 f5ab f5c9 ddbf d5df fdeb
0000170 baeb aa8b ffff dcf5 aed5 bfdd eaea aaaa
0000180 fef5 aaff abae aaba eaba d5ea eaae ddff
0000190 f5ba f5e5 eaa0 d4d5 c75a a491 ffc4 ffff
00001a0 ffcd f889 01a0 c2dd f5f5 d5aa d5ae 86c2