Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BACnet Connector #1658

Open
jmorbitzerpke opened this issue Jan 20, 2025 · 7 comments
Open

BACnet Connector #1658

jmorbitzerpke opened this issue Jan 20, 2025 · 7 comments
Assignees
Labels
can be closed Label uses when issue is fixed or feature is added and will be available in the next release. help wanted

Comments

@jmorbitzerpke
Copy link

Good morning!

I have problems connecting to a BACnet device via TB-Gateway. Which configuration is the right one? There is a difference in describing the datapoint.

Configuration shown in Git:

"devices": [
{
"deviceInfo": {
"deviceNameExpressionSource": "expression",
"deviceNameExpression": "BACnet Device ${objectName}",
"deviceProfileExpressionSource": "constant",
"deviceProfileExpression": "default"
},
"address": "192.168.0.102:47808",
"pollPeriod": 10000,
"attributes": [
{
"key": "temperature",
"objectType": "analogInput",
"objectId": "0",
"propertyId": "presentValue"
}
],
"timeseries": [
{
"key": "water_temp",
"objectType": "analogInput",
"objectId": "1",
"propertyId": "presentValue"
},

Configuration in TB-Gateway (auto generated):

"devices": [
{
"deviceName": "BACnet Device ${objectName}",
"deviceType": "default",
"address": "192.168.0.102:47808",
"pollPeriod": 10000,
"attributes": [
{
"key": "temperature",
"type": "string",
"objectId": "analogOutput:1",
"propertyId": "presentValue"
}
],
"timeseries": [
{
"key": "state",
"type": "bool",
"objectId": "binaryValue:1",
"propertyId": "presentValue"
}

@samson0v
Copy link
Contributor

Hi @jmorbitzerpke, thanks for your interest in ThingsBoard IoT Gateway!
The first one is in the right format.
Also, if you have a problem with BACnet connectivity, send us logs with the DEBUG level.

@jmorbitzerpke
Copy link
Author

Here are some screenshots. I got a device at 192.168.0.102 with AV1. Connector doesn't seem to start, because under BACnet connectors there is no entry.

Image

Image

Image

Image

@jmorbitzerpke
Copy link
Author

jmorbitzerpke commented Jan 20, 2025

Could you please supply a working config file? What do you need to know about the BACnet device. ModBus connector stops working when starting BACnet connector.

Some information :

  1. IP-Gateway: 192.168.0.20
  2. IP-BACnet device: 192.168.0.102
  3. Port: 47808
  4. Data: Analog Value, AV1
  5. Installation on a RPi CM4 with version 3.6.1

Thanks

@jmorbitzerpke
Copy link
Author

Hello!

No one facing the same problem?

@jmorbitzerpke
Copy link
Author

Image

@imbeacon
Copy link
Member

Hi @jmorbitzerpke,

This situation is caused, because we cannot discover which docker interface will be used to retrieve response from device.
In order to fix this issue - you can use special parameter - altResponsesAddresses with value from log “Received APDU, from ***. trying to find device…". Your configuration will look like:

"devices": [
{
"deviceInfo": {
"deviceNameExpressionSource": "expression",
"deviceNameExpression": "BACnet Device ${objectName}",
"deviceProfileExpressionSource": "constant",
"deviceProfileExpression": "default"
},
"address": "192.168.0.102:47808”,
"altResponsesAddresses": ["172.18.0.1:51018"],
"pollPeriod": 10000,
"attributes": [
{
"key": "temperature",
"objectType": "analogInput",
"objectId": "0",
"propertyId": "presentValue"
}
],
"timeseries": [
{
"key": "water_temp",
"objectType": "analogInput",
"objectId": "1",
"propertyId": "presentValue"
},

@imbeacon imbeacon added the can be closed Label uses when issue is fixed or feature is added and will be available in the next release. label Jan 29, 2025
@jmorbitzerpke
Copy link
Author

Thank you for your answer. But there is one problem. The port seems to be randomly chosen by the connector when enabled. So when I change the config to the port dispayed, the port changes after the config has changed. Is there a way to bind specific port?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can be closed Label uses when issue is fixed or feature is added and will be available in the next release. help wanted
Projects
None yet
Development

No branches or pull requests

3 participants