[Backlogmanager] [FIWARE-JIRA] (HELP-16773) [fiware-stackoverflow] Sending a specific entity to FIWARE QuantumLeap

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Mon Jun 15 11:12:00 CEST 2020


     [ https://jira.fiware.org/browse/HELP-16773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez updated HELP-16773:
----------------------------------
    Description: 
Created question in FIWARE Q/A platform on 08-06-2020 at 14:06
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/62262433/sending-a-specific-entity-to-fiware-quantumleap


+Question:+
Sending a specific entity to FIWARE QuantumLeap

+Description:+
In my application I have a very specific entity format, where one of the attributes' values is a json array of values.

    {
        "id": "Proximity3",
        "type": "SensorAgent",
        "measurementType": {
            "type": "string",
            "value": "boolean",
            "metadata": {}
        },
        "modifiedTime": {
            "type": "string",
            "value": "2020-06-08T12:30:11.091506Z",
            "metadata": {}
        },
        "readings": {
            "type": "array",
            "value": [
                {
                    "type": "SensorReading",
                    "value": {
                        "reading": {
                            "type": "boolean",
                            "value": false
                        }
                    }
                }
            ],
            "metadata": {}
        },
        "sanID": {
            "type": "string",
            "value": "SAN_3",
            "metadata": {}
        },
        "sensorID": {
            "type": "string",
            "value": "Proximity3",
            "metadata": {}
        },
        "sensorManufacturer": {
            "type": "string",
            "value": "Unknown",
            "metadata": {}
        },
        "sensorType": {
            "type": "string",
            "value": "ON_OFF_SENSOR",
            "metadata": {}
        }
    }
] 


As you can see, readings attribute has an array of values stored in it (in this example only one.

Whenever I try to subscribe QuantumLeap to Orion Context Broker, subscription is successful, but there is no data received by QuantumLeap (even querying http://localhost:8668/v2/attrs gives me 'No records were found for such query.'). Tried using attrFormat on subscription, but unsuccessful.

At the same time, this https://quantumleap.readthedocs.io/en/latest/user/ suggests that the QuantumLeap expects a specific entity. 
My question is, is there anything possible to do in order to get this entity to QuantumLeap, or I would need to change the entity?


  was:

Created question in FIWARE Q/A platform on 08-06-2020 at 14:06
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/62262433/sending-a-specific-entity-to-fiware-quantumleap


+Question:+
Sending a specific entity to FIWARE QuantumLeap

+Description:+
In my application I have a very specific entity format, where one of the attributes' values is a json array of values.

    {
        "id": "Proximity3",
        "type": "SensorAgent",
        "measurementType": {
            "type": "string",
            "value": "boolean",
            "metadata": {}
        },
        "modifiedTime": {
            "type": "string",
            "value": "2020-06-08T12:30:11.091506Z",
            "metadata": {}
        },
        "readings": {
            "type": "array",
            "value": [
                {
                    "type": "SensorReading",
                    "value": {
                        "reading": {
                            "type": "boolean",
                            "value": false
                        }
                    }
                }
            ],
            "metadata": {}
        },
        "sanID": {
            "type": "string",
            "value": "SAN_3",
            "metadata": {}
        },
        "sensorID": {
            "type": "string",
            "value": "Proximity3",
            "metadata": {}
        },
        "sensorManufacturer": {
            "type": "string",
            "value": "Unknown",
            "metadata": {}
        },
        "sensorType": {
            "type": "string",
            "value": "ON_OFF_SENSOR",
            "metadata": {}
        }
    }
] 


As you can see, readings attribute has an array of values stored in it (in this example only one.

Whenever I try to subscribe QuantumLeap to Orion Context Broker, subscription is successful, but there is no data received by QuantumLeap (even querying http://localhost:8668/v2/attrs gives me 'No records were found for such query.'). Tried using attrFormat on subscription, but unsuccessful.

At the same time, this https://quantumleap.readthedocs.io/en/latest/user/ suggests that the QuantumLeap expects a specific entity. 
My question is, is there anything possible to do in order to get this entity to QuantumLeap, or I would need to change the entity?


     HD-Enabler: Quantum-Leap

> [fiware-stackoverflow] Sending a specific entity to FIWARE QuantumLeap
> ----------------------------------------------------------------------
>
>                 Key: HELP-16773
>                 URL: https://jira.fiware.org/browse/HELP-16773
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: MARTEL
>              Labels: fiware, fiware-orion, http, json
>
> Created question in FIWARE Q/A platform on 08-06-2020 at 14:06
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/62262433/sending-a-specific-entity-to-fiware-quantumleap
> +Question:+
> Sending a specific entity to FIWARE QuantumLeap
> +Description:+
> In my application I have a very specific entity format, where one of the attributes' values is a json array of values.
>     {
>         "id": "Proximity3",
>         "type": "SensorAgent",
>         "measurementType": {
>             "type": "string",
>             "value": "boolean",
>             "metadata": {}
>         },
>         "modifiedTime": {
>             "type": "string",
>             "value": "2020-06-08T12:30:11.091506Z",
>             "metadata": {}
>         },
>         "readings": {
>             "type": "array",
>             "value": [
>                 {
>                     "type": "SensorReading",
>                     "value": {
>                         "reading": {
>                             "type": "boolean",
>                             "value": false
>                         }
>                     }
>                 }
>             ],
>             "metadata": {}
>         },
>         "sanID": {
>             "type": "string",
>             "value": "SAN_3",
>             "metadata": {}
>         },
>         "sensorID": {
>             "type": "string",
>             "value": "Proximity3",
>             "metadata": {}
>         },
>         "sensorManufacturer": {
>             "type": "string",
>             "value": "Unknown",
>             "metadata": {}
>         },
>         "sensorType": {
>             "type": "string",
>             "value": "ON_OFF_SENSOR",
>             "metadata": {}
>         }
>     }
> ] 
> As you can see, readings attribute has an array of values stored in it (in this example only one.
> Whenever I try to subscribe QuantumLeap to Orion Context Broker, subscription is successful, but there is no data received by QuantumLeap (even querying http://localhost:8668/v2/attrs gives me 'No records were found for such query.'). Tried using attrFormat on subscription, but unsuccessful.
> At the same time, this https://quantumleap.readthedocs.io/en/latest/user/ suggests that the QuantumLeap expects a specific entity. 
> My question is, is there anything possible to do in order to get this entity to QuantumLeap, or I would need to change the entity?



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)


More information about the Backlogmanager mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy