-
Notifications
You must be signed in to change notification settings - Fork 869
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] Bacnet connector stopping - ReportStrategyConfig failling #1603
Comments
I've been investigating and the issue seems to be coming from this like:
So the
Which is pretty normal, as the
I appreciate the effort and really like the Thingsboard platform, so much so that I use it in production in my business and I'm a proud subscriber of the hosted TB Cloud. But I'd like to mention that on every release, some bugs are fixed but then 5 other new bugs appear. The BACnet connector is broken since the version 3.5.2, which is the last version that I managed to make work. But I'd love to upgrade to a newer version so I can use the SQLite storage (which is broken on 3.5.1) but I can't and I'm stuck in this older version. Also, we have lots of open issues and many times we don't get any answer on for them or it takes weeks. I'd love to help but without proper typing or tests, it's hard to get all the codebase context. |
Hi @elgutierrez! |
Hey @samson0v , thanks for the update. I'll see when I have a slot for testing that. Is there an ETA for the new release? |
Hi @elgutierrez, The new release is available, feel free to try it. I’m closing this issue, because it relates to deprecated for now connector. But, please open a new, if you discover some issues with new BACnet connector. |
Describe the bug
I'm running the gateway using Docker and the 3.6.1 version on Bacnet. The config is OK and the device responds to the IAM request. But it won't report the data to the platform because of this error where it can't access the Report Strategy
Connector name (If bug in the some connector):
BACnet
Error traceback (If available):
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: