thingsboard / thingsboard-gateway

Open-source IoT Gateway - integrates devices connected to legacy and third-party systems with ThingsBoard IoT Platform using Modbus, CAN bus, BACnet, BLE, OPC-UA, MQTT, ODBC and REST protocols

Home Page:https://thingsboard.io/docs/iot-gateway/what-is-iot-gateway/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG] Enabling or disabling the linker through platform gateway configuration causes devices under other linkers to be unable to communicate normally.

ultimate-smile opened this issue · comments

Describe the bug
Different protocol devices are integrated through the platform. When the linker is closed using the platform, the previously controllable devices cannot be operated. In the case, mqtt is used to control the lights, and the opcua simulator simulates acquisition. When the opcua linker is closed, the lights cannot be controlled. Yes. The gateway becomes normal after hot restart.
.In addition, when closing the opcua linker and re-enabling the opcua linker, I found that the linker of the light in the connected_devices.json file under the gateway has been modified to the linker of opcua (normal light should maintain the linker of mqtt)
image
image

Connector name (If bug in the some connector):
[e.g. OPC-UA Connector]

Error traceback (If available):

'deviceName'
Traceback (most recent call last):
  File "<input>", line 2, in <module>
KeyError: 'deviceName'

Versions (please complete the following information):

  • OS: [e.g. Ubuntu 18.04]
  • Thingsboard IoT Gateway version [e.g. 3.6.4]
  • Python version[e.g. 3.10]