We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question

Jason Fox's profile - activity

2018-10-16 23:07:26 +0200 received badge  Enthusiast
2018-10-10 15:44:00 +0200 answered a question Error at Cygnus when receives a Notification from "Orion context Broker" : 'fiware-servicepath' header value does not match the number of notified context responses

When setting up the subscription, Cygnus currently only accepts notifications in the older NGSI v1 format- the attrsFormat=legacy is therefore needed.

see this : Stack Overflow Answer for more details

2018-06-27 15:00:19 +0200 answered a question Strange Comet issues

In your demo I’ve checked - you are connecting to a mongo DB - you are aggregating

docker run -it --network comet_demo_fiware_network --entrypoint /bin/bash mongo

mongo --host mongo_sth --port 27018

show dbs

admin 0.000GB config 0.000GB local 0.000GB sth_sensei_service 0.000GB

use sth_sensei_service

It looks the that your subscription is incorrect: { "entities": [ { "type": "PersonDetection", "isPattern": "false", "id": "PersonDetection" } ], "attributes": [ "ts" ], "reference": "http://sth:8666/notify" }

This means you are storing the ts attribute only.

Your request to comet is reading positionX and which has not been aggregated.


I hope this helps - you will need to alter your subscription - the attributes should be:

"attributes": [ “ts”, “posistionX” “positionY" ]

2018-06-21 09:31:05 +0200 commented answer Cygnus tutorial - not working

There is a simple "how to connect Cygnus" tutorial on GitHub - https://github.com/fiware/tutorials.Historic-Context

2018-06-21 09:29:32 +0200 commented answer Cygnus tutorial - not working

Ensure that you are running with logging to the max -I use the `CYGNUS_LOG_LEVEL=DEBUG` environment variable. Check that you are sending your notification to the right port - e.g. `CYGNUS_SERVICE_PORT=5050` would listen on "notification": {"http": { "url": "http://cygnus:5050/notify }}.

2018-06-11 09:31:59 +0200 answered a question Mobility as a Service efforts and standards?

It looks like things have changed since the previous answer to this question. Standardization of a set of Urban Mobility data Models based on the GTFS transit feed is now being discussed with the following Pull Request

2018-06-11 09:31:58 +0200 answered a question Cygnus tutorial - not working

The notification.sh appears to be a simulation of the result of an Orion Subscription - and therefore needs to be posted to the port Cygnus is listening on - which is usually localhost:5050 - assuming you are running Cygnus on localhost.

Your couldn't connect to host message indicates that either you have not started Cygnus on localhost or you have configured an alternate port. Ensure you have used the environment variable CYGNUS_API_PORT=5080 somewhere or the agent.conf file holds a line cygnus-ngsi.sources.http-source.port = 5050

The subscription it is simulating is supposed to be something along the lines of When X occurs send a notification to cygnus - Therefore I'm guessing that localhost:5050 is the location where Cygnus is supposed to be listening.

When setting up a REAL subscription and running Orion it needs to be something like:

curl -X POST \ 'http://{{orion:port}}/v2/subscriptions/' \ -H 'Content-Type: application/json' \ -d '{ "description": "Notify Cygnus of all context changes", "subject": { "entities": [ { "idPattern": ".*" } ] }, "notification": { "http": { "url": "http://{{cygnus:port}}/notify" }, "attrsFormat": "legacy" }, "throttling": 5 }'

Replace {{orion:port}} and {{cyngnus:port}} as necessary (this assumes you are not using a fiware-header or fiware-servicepath yet...)

You can then update an existing entity with the PATCH command:

curl -X PATCH \ 'http://{{orion}}/v2/entities/<entity-id>/attrs' \ -H 'Content-Type: application/json' \ -d ' { "price":{"type":"Integer", "value": 89} }'

Obviously replace <entity-id> and the -d payload with your data.