Variable names issue?

I’m trying to build a blueprint dashboard for visualizing the Dragino IO controller (LT-22222-L).
For some reason I encounter problems for all variables that have an underscore in the name.
In that case I do not see values in the widget and/or no icons.
Examples:
{
“variable”: “AVI2_V”,
“value”: “24.316”,
“serie”: “1632877925019”,
“unit”: “V”
},
{
“variable”: “DO1_status”,
“value”: “H”,
“serie”: “1632877925019”
}

Is this a known issue… or am I missing something?

Thanks!
Vincent

Just FYI.
I applied a decoder in TTN and removed the _ from the variable names. Now the widgets are working perfectly fine. So it kinda confirms the issue with _ in variable names.

Hi @vincent.raaijmakers ,

I’m pretty sure the underscore is not the problem. I’m thinking if the problem could be the upper case letters.

Maybe Tago set everything to lower case once it receives it. Could that be the problem?

I think you have a interesting observation.

If I compare the output of the LoraWAN parsers TTN vs Helium, I see the following differences:

TTN

Raw Payload: \AVI1":11.398,“AVI2”:24.535,“DI1”:“H”
LoraWan parser:
{
“variable”: “avi1”,
“value”: 11.398,
“serie”: “1633110878240”
},
{
“variable”: “avi2”,
“value”: 24.535,
“serie”: “1633110878240”
}

Helium

Raw Payload: “AVI1”:0,“AVI2”:0
LoraWan parser:
{
“variable”: “AVI1”,
“value”: 0,
“serie”: “1633112715617”
},
{
“variable”: “AVI2”,
“value”: 0,
“serie”: “1633112715617”
}

Apparently the TTN parser in Tago makes the variables all lowercase. The Helium parser does not.

What is the best practice? I use the same decoder script in TTN and Helium. Using this script, the variables are all upper case out of the decoder. So using Tago, I guess the best practice to use small case in the decoders? Not a biggie, but good to know.

Vincent

@vincent.raaijmakers thats it. the good practice indeed is not using uppercase in variables name.

-Guilherme