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

[BUG] ThingsBoard Gateway does not send telemetry #1052

Closed
Steampunkery opened this issue Feb 2, 2023 · 14 comments
Closed

[BUG] ThingsBoard Gateway does not send telemetry #1052

Steampunkery opened this issue Feb 2, 2023 · 14 comments
Assignees
Labels

Comments

@Steampunkery
Copy link

Describe the bug
More recent installations of thingsboard gateway are not sending telemetry from our BLE devices. The gateway will connect to the device. It will print a log saying that it can't find an attribute characteristic (normal), but it will never send any telemetry. Installations installed back in May of 2022 are still functional.

Things we have tried:

  • Copying the thingsboard installation folder from an older working installation to a new machine. Result: no change
  • Trying the latest version 3.2. Result: No change
  • Fresh installing the entire OS: Result: No change
  • Getting another RPI4 to rule out hardware issue: No change

This leads us to believe that this is either a dependency issue or an OS issue. See logs below for more context. We have been working on this issue for many hours, so please don't hesitate to ask if we've tried something.

Connector name (If bug in the some connector):
BLE connector (others untested)

LOGS
https://pastebin.com/meN4yVn6
The issue starts around line 134 and again at 247.

Versions (please complete the following information):

  • OS: Raspberry Pi OS
  • Thingsboard IoT Gateway version 3.1 & 3.2
  • Python 3.9.2
@samson0v
Copy link
Contributor

samson0v commented Feb 3, 2023

Hi @Steampunkery, thanks for your interest in ThingsBoard IoT Gateway.
Send, please, your configuration files.

@Steampunkery
Copy link
Author

Here are my relevant configuration files.

config.zip

@samson0v
Copy link
Contributor

samson0v commented Feb 7, 2023

Hi @Steampunkery, are you sure that you send the right config files? Because there is a difference between logs char and config char.

@Steampunkery
Copy link
Author

Those configuration files are identical to the configurations used with the exception of the characteristic value. The bug appears no matter the value of the characteristic. Even if you use one of the bluetooth standard device information characteristics.

@samson0v
Copy link
Contributor

@Steampunkery, make sure that your Gateway uses the right config files. Because of logs, I can see that you also use MQTT Connector but in the config file, you are using only BLE Connector.
I recommend you delete all Gateway folders and make a clean installation.

@Steampunkery
Copy link
Author

Hi, thanks for the suggestion. We have taken these steps more than 10 times. We are fairly sure it is an issue with dependencies or some other systemic issue because we are able to copy a working version from an older OS installation to a newer OS installation, and the problem still persists.

@samson0v
Copy link
Contributor

@Steampunkery, "clean installation", I mean this instruction: #977 (comment)

@samson0v
Copy link
Contributor

samson0v commented Mar 1, 2023

@Steampunkery, any updates?

@Steampunkery
Copy link
Author

Hi, I haven't had a chance to take those steps yet. Has anyone looked into the bug on your side? I'll try to execute the steps soon.

@Steampunkery
Copy link
Author

One of our team members has run the installation on a completely fresh version of Debian 11 (bullseye), and is experiencing the same error. We have some bullseye machines that are working, and some that aren't. The only discernable difference is that the working machines were set up before the non-working machines. This points to an error in the system or the way that thingsboard gateway is configured.

@samson0v
Copy link
Contributor

Hi @Steampunkery, let's continue our chat on the email. Please, send me a message to [email protected]

@Mannetjie
Copy link

Mannetjie commented Mar 20, 2023

Have this been resolved as I am experiencing exactly the same issue. Clean install, following the getting started guide. The device gets created, clean logs, BUT absolutely no telemetry data. Although I am using Mqtt.

@Steampunkery
Copy link
Author

Steampunkery commented Mar 20, 2023 via email

@Mannetjie
Copy link

Mannetjie commented Mar 20, 2023 via email

@imbeacon imbeacon closed this as completed Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants