gl200 "type" attribute vs computed attributes
It should work.
I also think it should work but it doesn't work or I don't know something. The following link is a picture from my test - the same simple test for the normal attribute, e.g. "protocol" and for the "type" attribute The function computed attributes cannot see the content of the "type" attribute ...
>It should work.
Anton, I can confirm that it does not.
For some strange reason "type" does not work. Just to confirm I tried sending a message with the OsmAnd protocol for a fake (but valid) device with this "type" attribute set to some value but "type" is not usable as a parameter in setting up custom attributes. If I change it to say typex then it works.
Here are the two examples:
This works (I can use "typex" in custom attributes):
wget -O - "http://172.17.0.2:5055/?id=11223355&lat=44.652587&lon=-88.159977×tamp=20200629152508&hdop=1&altitude=80&speed=50&typex=IGF"This does not work (If I use "type" in custom attributes it fails like it was pointed out in the first post):
wget -O - "http://172.17.0.2:5055/?id=11223355&lat=44.652587&lon=-88.159977×tamp=20200629152508&hdop=1&altitude=80&speed=50&type=IGF"It doesn't seem like it's a keyword, so I don't know why it would be the case:
http://commons.apache.org/proper/commons-jexl/reference/syntax.html#Language_Elements
I guess someone should debug the code and see what happens with type variable.
Is there a way for the gl200 protocol to use the "type" attribute in the computed attributes? and if so what will the name for this variable ?
When using "type", I always get the message "No content" when checking the syntax. Why? Of course, the "type" attribute always has a value and it is visible in the attributes. e.g.
hdop = 1.0 odometer = 74300.0 type = VGL distance = 0.0 totalDistance = 75079.94 motion = false hours = 7272000