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
Describe the bugNote: I have not tested this with ThingsBoard gateway itself, but seeing as the MQTT code is identical to the one found in the Python Client SDK I do not see why it would behave any differently.
Trying to request more than one key over MQTT results in getting no value field. This is due to tb_device_mqtt.py#L305 not assembling correct messages nor spitting out proper errors upon receiving malformed input data. This forces you to have to make a list with only one string attribute, since then the function behaves like advertised and returns a message in the callback with a value field, resulting in numerous extra requests having to be made.
Describe the bug Note: I have not tested this with ThingsBoard gateway itself, but seeing as the MQTT code is identical to the one found in the Python Client SDK I do not see why it would behave any differently.
Trying to request more than one key over MQTT results in getting no
value
field. This is due to tb_device_mqtt.py#L305 not assembling correct messages nor spitting out proper errors upon receiving malformed input data. This forces you to have to make a list with only one string attribute, since then the function behaves like advertised and returns a message in the callback with avalue
field, resulting in numerous extra requests having to be made.This issue has been raised since August last year: https://github.com/thingsboard/thingsboard-python-client-sdk/issues/11
Here is an example of code that would not work as expected:
Connector name (If bug in the some connector):
Error traceback (If available):
Versions (please complete the following information):