Orion notification to cygnus

3
votes

I have followed the official guide about entity creation/update and subscribtion in Orion, they are working and I get success responses. But Orion doesnt send notifications to Cygnus.

Am i missing some step here?

These are the basic scripts I am using:

create entity

{
"contextElements": [{
"type": "Room",
"isPattern": "false",
"id": "2FebRoom",
"attributes": [{
    "name": "temperature",
    "type": "float",
    "value": "888"
}]
}],
"updateAction": "APPEND"
}

subscribe entity http://orion.lab.fiware.org:1026/v1/subscribeContext

{
"entities": [
    {
        "type": "Room",
        "isPattern": "false",
        "id": "2FebRoom"
    }
],
"attributes": [
    "temperature"
],
"reference": "http://A.B.C.D:5050/notify",
"duration": "P1M",
"notifyConditions": [
    {
        "type": "ONCHANGE",
        "condValues": [
            "temperature"
        ]
    }
],
"throttling": "PT5S"
}

update entity

{
"contextElements": [
    {
        "type": "Room",
        "isPattern": "false",
        "id": "2FebRoom",
        "attributes": [
            {
                "name": "temperature",
                "type": "float",
                "value": "111"
            }
        ]
    }
],
"updateAction": "UPDATE"
}

I can query the new value in Orion after the update operation but Cygnus doesnt receive any notification, what would be the problem?

Many thanks

1
fiware-orionfiware-cygnus
Just to confirm... I undesrtand that update are using different temperature values each time (i.e. not always 111 as shown in the question post). Is that correct? Thanks! – fgalan
Is "CYGNUS_URL" a literal value or an ofuscation of the actual URL. In the second case, could you edit your question post to include the actual URL, please? If you want to ofuscate you public IP, you can use something like "A.B.C.D.". Thanks! – fgalan
Hello Fermin, yes we send different values each time, we didnt want to post our public cygnus url so i changed it to CYGNUS_URL :) i will change to A.B.C.D now – dmtzz
Next step is to check if Orion is sending notifications. The procedure depends on the Orion version. Could you update your post to include the Orion version you are using in the question (i.e. the one you get with contextBroker --version), please? – fgalan
Increment in timesSent means that Orion is sending (or attempting to send at least) notifications. Is the 5050 port opened (both in security group -if appliable- and local fiwewall) in the A.B.C.B to receive connections from orion.lab.fiware.org? PD. You don't need to use NGSIv2 but probably it is a good ideal, given that is a newer (and improved) version of the API. However, note that NGSIv2 is yet in beta status so some changes could happen in existing functionality. – fgalan

1 Answers

0
votes

Problem was caused by a temporal outage in outgoing notifications from orion.lab.fiware.org. The problem has been solved.