Unable to Connect Ewon Flexy to ThingWorx using Ewon Flexy Connector

Description of the Issue

We are integrating Ewon Flexy with ThingWorx using the Ewon Flexy Connector but are encountering issues in the setup.

We are following the direct path configuration as mentioned in:
📄 flexy-thingworx-connector-3.3.5-README.pdf

Despite following all the steps, the connector is not generating the required configuration file after restarting the Ewon device. Additionally, we see warnings in the ThingWorx Application Logs, indicating a potential issue with the connection.

Steps Followed

We followed the steps mentioned in the official documentation:
📄 Flexy-ThingWorx Connector Documentation

Steps Performed on Ewon Flexy

1. Cloned the Ewon Flexy Connector Repository

   • Repository URL: https://github.com/hms-networks/flexy-thingworx-connector

2. Modified the Configuration Files

   • Updated the flexy.properties and ThingworxConfiguration.json files inside the /Config/ folder with the required parameters.

3. Built the .jar and JVM Files

   • Ran the following command to build the connector:
     shell

     mvn clean package
   • The build was successful, and the required .jar file was generated.

4. Uploaded the Required Files to Ewon

   • Uploaded the .jar and JVM files to the /usr/ directory of the Ewon device.

5. Rebooted the Ewon Flexy Device

   • Expected Outcome:
     • After reboot, the ThingworxConfiguration.json file should be automatically generated with default values.
     • We would then update the ThingWorx URL and AppKey in the configuration file.
   • Actual Outcome:
     • The ThingworxConfiguration.json file was not generated after reboot.

6. Manually Created the Configuration File

   • Since the configuration file was not auto-generated, we manually placed the ThingworxConfiguration.json file inside the /usr/ directory.
   • Restarted Ewon Flexy from the web interface.

7. Checked for Connection to ThingWorx

   • Expected Outcome:
     • Ewon should connect to ThingWorx successfully.
     • If there is an issue, an error should be displayed under Logs → Real-Time Logs.
   • Actual Outcome:
     • Ewon did not connect to ThingWorx.
     • Observed warnings under the ThingWorx Application Logs after restarting Ewon.

Steps Performed on ThingWorx

1. Imported the ThingWorx Project

   • Imported the EwonThingworxConnector project into ThingWorx 9.3.11.

2. Created an AppKey

   • Created an AppKey with Administrator permissions to authenticate Ewon.

3. Modified the ConnectorHost Entity

   • Set disableTalk2M to true in the ConnectorHost entity.
   • This is to configure direct communication between Ewon and ThingWorx without relying on Talk2M.

4. Checked the Application Logs

   • After restarting the Ewon Flexy device, observed warnings in the ThingWorx Application Logs.
   • This suggests a potential issue with the connection setup.

Issues Observed

1. The ThingworxConfiguration.json file is not auto-generated after reboot.
2. Even after manually adding the ThingworxConfiguration.json file, Ewon does not connect to ThingWorx.
3. Warnings are observed under ThingWorx Application Logs when Ewon is restarted.
4. Direct path configuration does not seem to be working as expected despite setting disableTalk2M = true.

We would appreciate guidance on:

• Why the ThingworxConfiguration.json file is not being generated.
• How to resolve the connectivity issue between Ewon Flexy and ThingWorx.
• Explanation of the warnings appearing in ThingWorx Application Logs.
• Any additional configurations required for direct path communication to work correctly.