thingsboard / thingsboard-edge

Apache License 2.0
101 stars 77 forks source link

Thingsboard Edge PE displays duplicates of the same device created by the IoT Gateway #4

Closed apadEnlace closed 2 years ago

apadEnlace commented 2 years ago

Hi!

Thingsboard Edge PE

Note: I'll refer to Thingsboard as "TB" in the rest of the message

Description I have a TB IoT Gateway collecting data from CAN devices. I'm testing sending this data to a TB Edge PE instance running in a different computer in same network. When a CAN device generates a value, TB Edge, correctly, shows the device with the corresponding telemetry value. However, when the device doesn't get a new telemetry value before the device disconnects ("lastDisconnectTime" attribute updates), TB Edge creates a new device showing the newly received telemetry value; and it does this every time the device disconnects:

image

Where is that string at the end of the Device Name coming from? How can I set up TB Edge to not add that string, so it doesn't creates new devices?

I suspect TB Edge is the one adding this string to the name, as previously I had tested the TB IoT gateway connected directly to an instance of TB Server PE, and the name do not show that string that TB edge is showing. Screenshot of name of device configured in TB Gateway:

image

OS: Ubuntu 20.04 ThingsBoard: TB Edge PE (3.3.4pe), TB IoT Gateway (latest - installed a couple of weeks ago) and TB Server PE 3.3.2 Browser: Chrome Version 100.0.4896.60

volodymyr-babak commented 2 years ago

@apadEnlace

this string is added to the device on the Edge in case the device name conflicts with the one, that is already created on the TB cloud. Do you have a device with the same name on the TB cloud?

apadEnlace commented 2 years ago

@apadEnlace

this string is added to the device on the Edge in case the device name conflicts with the one, that is already created on the TB cloud. Do you have a device with the same name on the TB cloud?

That's correct. I had a device with the same name in the TB cloud instance from a previous testing. I removed it, and it works perfectly now!

Thanks for the help @volodymyr-babak!