Describe the issue
I cannot get communication between two EC2 instances in AWS using the Bacnet connector. Communication with MQTT and Modbus connectors are functional but Bacnet is not transmitting anything to the partner instance.
I have Yabe, VTS, and Wireshark running on the slave instance and none of them show any traffic. The destination device is a Room Simulator that's included with Yabe. This is discoverable by VTS and Yabe since they are running on the local instance too. I say that just to show that the breakdown seems to be between the two EC2's.
Additionally, I have tested and confirmed UDP 47808 communication (and other ephemeral UDP ports) work using ncat.
Configuration (Attach your configuration file)
I'm having trouble uploading my config...Github keeps giving me an error. I had to zip it up and attach it that way.
Connector-Config.zip
Connector name (If you need help with some connector/converter):
Bacnet
Error traceback (If it was raised):
No errors are present.
Versions (please complete the following information):
- OS: AWS EC2 Ubuntu 24.04 (running TB and the TB Gateway.)
- OS: AWS EC2 Win 11 (Running the simulator)
- Thingsboard IoT Gateway version: 3.8.0
- Python version: 3.12.3
Describe the issue
I cannot get communication between two EC2 instances in AWS using the Bacnet connector. Communication with MQTT and Modbus connectors are functional but Bacnet is not transmitting anything to the partner instance.
I have Yabe, VTS, and Wireshark running on the slave instance and none of them show any traffic. The destination device is a Room Simulator that's included with Yabe. This is discoverable by VTS and Yabe since they are running on the local instance too. I say that just to show that the breakdown seems to be between the two EC2's.
Additionally, I have tested and confirmed UDP 47808 communication (and other ephemeral UDP ports) work using
ncat.Configuration (Attach your configuration file)
I'm having trouble uploading my config...Github keeps giving me an error. I had to zip it up and attach it that way.
Connector-Config.zip
Connector name (If you need help with some connector/converter):
Bacnet
Error traceback (If it was raised):
No errors are present.
Versions (please complete the following information):