[Bug] Rules for chain return data problem

[WingedKitten]

Describe the bug In the Rule Chain used in the originator telemetry data query, the returned data set with escape characters backslash, difficult to parse data into a json string； like this { "deviceName": "WarpKnittingMachine-1103", "deviceType": "default", "lowerClothMeter": "[{\"ts\":1677633586516,\"value\":41.3},{\"ts\":1677633571525,\"value\":41.2}]", "manufacturer": "[{\"ts\":1677633591508,\"value\":\"KarlMayer\"},{\"ts\":1677633586516,\"value\":\"KarlMayer\"}]", "ts": "1677633321540" }

or

{ "deviceName": "WarpKnittingMachine-46", "deviceType": "default", "manufacturer": "\"General\"", "ts": "1677634841111" }

Your Server Environment

• ThingsBoard Version 3.4.3
• ThingsBoard EDGE Version 3.4.3

Your Client Environment

Desktop (please complete the following information):

• centos 7.9

[WingedKitten]

If the data returned is a String type, the data will be additional have a double quotation marks

[WingedKitten]

Even the numeric types will also be combined with double quotation marks

[WingedKitten]

Article query multiple data in json string is normal, is my mistake. But a single data redundant double quotation marks

[volodymyr-babak]

@WingedKitten

rule chain functionality is the same on TB cloud and TB edge. There should be no difference is terms of processing messages on these two products. Could you please let me know if the same issue is reproducible on TB cloud? Or it's only reproducible on TB edge?

[WingedKitten]

I didn't pay attention to TB cloud, it was found on the edge, I need to compare. This is just a small problem. @volodymyr-babak But now I'm more concerned about the message queue accumulation