However I run into a initialization issue with this device. The enocean-AddOn seems to start the initialization but at some point it stops with ESP3Packet malformed.
Configured is the device as rfc2217 with IP-address and Port.
11:37:20.308 [DEBUG] [internal.handler.EnOceanBridgeHandler] - request base id
11:37:20.309 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'enocean:bridge:enocean_lan_gw_02' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_PENDING): starting rx thread...
11:37:20.309 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'enocean:bridge:enocean_lan_gw_02' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
11:37:20.309 [DEBUG] [ternal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
11:37:20.310 [DEBUG] [ternal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 08
11:37:20.310 [TRACE] [ternal.transceiver.EnOceanTransceiver] - Sending raw data: 5500010005700838
11:37:20.310 [DEBUG] [internal.handler.EnOceanBridgeHandler] - set postmaster mailboxes
11:37:20.310 [DEBUG] [ternal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type SMART_ACK_COMMAND with callback
11:37:20.312 [DEBUG] [internal.handler.EnOceanBridgeHandler] - request version info
11:37:20.313 [DEBUG] [ternal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
11:37:20.538 [TRACE] [ternal.transceiver.EnOceanTransceiver] - Received Sync Byte
11:37:20.539 [TRACE] [ternal.transceiver.EnOceanTransceiver] - >> Received header, data length 5 optional length 1 packet type 2
11:37:20.561 [DEBUG] [ternal.transceiver.EnOceanTransceiver] - Sending data, type SMART_ACK_COMMAND, payload 0814
11:37:20.561 [TRACE] [ternal.transceiver.EnOceanTransceiver] - Sending raw data: 5500020006C40814C4
11:37:20.578 [TRACE] [ternal.transceiver.EnOceanTransceiver] - ESP3Packet malformed: 00E980550001
11:37:20.814 [DEBUG] [ternal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 03
11:37:20.815 [TRACE] [ternal.transceiver.EnOceanTransceiver] - Sending raw data: 5500010005700309
11:37:20.838 [TRACE] [ternal.transceiver.EnOceanTransceiver] - Received Sync Byte
11:37:20.839 [TRACE] [ternal.transceiver.EnOceanTransceiver] - >> Received header, data length 33 optional length 0 packet type 2
11:37:20.839 [DEBUG] [ternal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 0001060100010501E7042189D3454F010354434D35313500000000000000000000 received
11:37:20.839 [TRACE] [ternal.transceiver.EnOceanTransceiver] - Response handled
Is this a configuration problem, a limitation of the add-on or a bug in the BSC-Tiny?