Enocean Binding raw TCP instead of RFC2217

Add-ons Bindings
1

Hello,
I would like to connect my Eltako system to openHAB. Since my server and the Eltako system are quite far away from each other I would like to do this via TCP connection.
For a test I used the hub4com application with RFC2217 on a laptop and it worked fine.
For this I entered “rfc2217://192.168.15.115:5050” as connection parameter at the binding and everything worked fine.
Now I bought a simple RS232 ↔ TCP converter and would like to use it.
Unfortunately it does not support RFC2217.
when I set the debug level to TRACE on the Eltako binding I always see “ESP2Packetmalformed”:

2023-09-12 08:50:20.060 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received First Sync Byte
2023-09-12 08:50:20.060 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Second Sync Byte
2023-09-12 08:50:20.060 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 11 packet type 0
2023-09-12 08:50:20.060 [DEBUG] [nternal.messages.ESP2PacketConverter] - Received ESP2 radio telegram: 0B078E5B000D059A82A900
2023-09-12 08:50:20.060 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Converted to: RADIO_ERP1 with RORG _4BS for 059A82A9
2023-09-12 08:50:20.060 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for 059A82A9 payload A58E5B000D059A82A900 received
2023-09-12 08:50:20.060 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload A58E5B000D059A82A900 for 059A82A9 received
2023-09-12 08:50:20.061 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload A58E5B000D059A82A900 for 059A82A9 received
2023-09-12 08:50:20.061 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload A58E5B000D059A82A900 for 059A82A9 received
2023-09-12 08:50:20.061 [INFO ] [e.model.script.Bewegungsmelder.rules] - Movement deteced in OG2, BrigthnesOutside: 30196.07843137 → do nothing
2023-09-12 08:50:39.804 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received First Sync Byte
2023-09-12 08:50:39.804 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Second Sync Byte
2023-09-12 08:50:39.804 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 11 packet type 0
2023-09-12 08:50:50.854 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - ESP2Packet malformed: 0B0748320048D4880001A5
2023-09-12 08:50:51.750 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received First Sync Byte
2023-09-12 08:50:51.750 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Second Sync Byte
2023-09-12 08:50:51.750 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 11 packet type 0
2023-09-12 08:50:53.430 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - ESP2Packet malformed: 0B07483200482D88003EA5

Now my question: is there any possibility that I can enter “RAW TCP” in the connection parameter instead of RFC2217?

Greetings
Florian

2

Hey there,
i do not understad much about what you are writing, but there might be another way:
Setup a secont OH instance close to your Eltako-System and integrate your actuators. Then you can connect your main OH with your remote OH via the remote OH binding.
I use this for another use-case but it works like a charm. I cant see any lag or something. All the items and things just pop up in your main OH. So sweet.
But you need to run a second Pi for this, sure :wink:

3

Hello Sebastian,
thanks for your suggested solution.
In the meantime, I have installed ser2net on a Raspberry Pi. That works pretty well.
My problem is now solved :slight_smile: