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

jmcantera's profile - activity

2018-12-03 09:06:29 +0100 answered a question Fiware slack - community

Hi Rafael,

We have not set up yet a Slack channel but it is our intention to do it very soon. In the meantime you can use this channel, Stackoverflow or Github.


2018-10-05 08:31:24 +0100 answered a question IDAS and IOT broker differences

IoT Broker is not needed. Actually IoT Broker is just an alternative implementation of the OMA NGSI 9 interfaces.

2018-07-17 08:27:19 +0100 answered a question Connecting Cepheus to Orion

could you please send us details about how Cepheus is subscribed to Orion?

For instance, the HTTP REST request and payload being used


2018-06-11 10:26:52 +0100 answered a question Strange Comet issues

A v2 subscription can also be used you just need to set attrsFormat to legacy. Example:

{ "description": "Notify me of all product price changes", "subject": { "entities": [{"idPattern": ".*", "type": "Product"}], "condition": { "attrs": [ "price" ] } }, "notification": { "http": { "url": "http://context-provider:3000/subscription/price-change" }, "attrsFormat" : "legacy" } }

2018-05-15 15:04:40 +0100 answered a question REST API - Past values of an entity

other options are STH Comet (unfortunately it only supports a flavour of NGSIv1 ... ). See http://fiwaretourguide.readthedocs.io...

here a tutorial for Cygnus and MySQL


and another component Quantum Leap (more aligned with NGSIv2, using Crate as DB) is an alternative


2018-02-27 09:45:03 +0100 answered a question There is some route optimization module for waste collection

maybe some of the companies of the FIWARE Consortium own a module like that but there is no open source project in the community dealing with such problems. There are some data models on waste management, please check https://schema.fiware.org


2018-01-31 15:57:07 +0100 answered a question Can't update value in entity
2018-01-31 15:56:00 +0100 answered a question Asset Management in Smart City

You can do asset management using the Orion Context Broker as a backend. All the assets can be entities and you can create, update, delete or query them. You can provide geospatial properties using GeoJSON.

As front-end you would need to implement your own application.

2018-01-31 15:52:48 +0100 answered a question How to fix links on fiware.org Data Models page?

We are currently updating the fiware.org website. Sorry for any inconvenience. If you have any questions, or would like to report a bug, please contact us at fiware-website@lists.fiware.org.

2018-01-23 11:44:38 +0100 answered a question video Analytics

as far as I know there are so specific components to deal with that. If you develop them as open source they can be welcome to ecosystem


2018-01-23 11:43:10 +0100 answered a question Fiware Data Model Usage - Device Functioning Messages


Good question. You can certainly use a Device entity linked to a WasteContainer entity and use the Device entity to store battery level, configurations and the like.

For certain device conditions that should be alerted, why don't you use the Alert entity type?. The Alert entity type could be extended to cover new Alert categories and subcategories. If you opt for that approach a Pull Request that extends the current Alert data model (with categories and subcategories for alerts originated in devices) will be more than welcome.

Thanks, best

2018-01-23 11:29:35 +0100 answered a question Workflow Engine in Fiware


I think you would need to have a look at Perseo, a Complex Event Processing implementation that integrates with the Orion Broker

see https://github.com/telefonicaid/perse...




2018-01-16 15:00:03 +0100 answered a question Mobility as a Service efforts and standards?

Currently we don't have specific APIs for Mobility as a Service. You can always create new APIs on top of the NGSI APIs.

2018-01-02 11:02:34 +0100 answered a question Smart Cities Help Reuiqred

Which are the main logical layers of the architecture and what are their main functionalities?

Infrastructure layer. Provides all the computational resources needed to run a smart city platform instance. It is based on Docker and OpenStack technologies. So, cities can deploy their own infrastructures on premise.

Data acquisition & actuation layer. It allows acquiring and ingesting smart city data from different sources including diverse IoT devices and protocols, existing IT systems, or extra private or public data sources. In addition, it exposes mechanisms to actuate over devices or systems, so that a more efficient and smart behaviour is exhibited by a city.

Context brokering layer. The main component of this layer is a data hub (performing the functional role of a context broker) which integrates all the data coming from different sources. In fact, it offers developers an open API (FIWARE NGSI) intended to publish, consume and subscribe to context information. Context information is modelled using entities and properties which represent what is happening in real (or right) time in a city, integrating and aggregating information from multiple sources as described above. Context information is usually harmonised as per the rules dictated by the FIWARE schemas (FIWARE Data Models). The Context brokering layer enables the creation of multiple and related vertical applications portable at data level and easily replicable in multiple cities. The context brokering layer typically exposes the last value of each data item. However, there is also a short term historical database which allows applications to make use of historical time series for the different properties. This layer also provide plugins which offer the capability to automatically generate long term historical data and populate it to big data stores.

Data processing, Analytics & Visualization layer. It allows processing all the city data so that new information can be derived or useful insights can be obtained. As a result processes can be optimized or better decisions can be taken. Data processing can be performed in real time (using a Complex Event Processing component) or deferred by using long term historical data stored in Big Data systems. Once data has been processed, the platform offers plugins and components for its visualization in a dashboard. Besides, there are graphical tools intended to perform advanced data analyses such as those related to location or business intelligence. Last but not least, some advanced interaction components are offered to deal with 3D representations or augmented reality.

Economy of data layer. This layer incorporates all the components needed to run an economy of data, so that context information from a city is properly published, secured and accounted. It allows data providers to publish, expose and charge for their data, data consumers to acquire data sets and pay for their consumption. As a result a data marketplace is enabled, moving forward from the concept of open data to the economy of data. This layer is powered by the corresponding TM Forum APIs.

How does the reference architecture handle southbound integration? How is integration with legacy systems managed ... (more)

2017-12-18 15:41:25 +0100 answered a question How to control access to Orion using oauth 2.0?

You can check API Umbrella


soon it will be integrated with OAuth token management

2017-12-18 15:39:50 +0100 answered a question IoT Ready program / for free or for a fee?

The FIWARE Marketplace is playing the promotion role, please check


2017-12-18 10:01:48 +0100 answered a question problems with android IDAS for contextBroker use.

please can you refine this question a bit more, particularly the specific issues you may have with Fiware technologies?

Thanks, best

2017-12-18 09:58:09 +0100 received badge  Associate Editor (source)
2017-12-18 09:57:31 +0100 answered a question How to upload images to Orion Context Broker


You cannot do that and should not do that. Even though there is a workaround, using data URIs, I would not recommend it if images are going to be bigger.

For storing images my recommendation is to use an object storage service such as S3 or Swift. The latter can be used from the Fiware Lab. Then, Orion entities can have an attribute (a URL) that will point to the object storage and in particular to the referenced image, such as

{ "id": "MyBuilding", "type": "Building", "photo": { "type": "URL", "value": "http://object.storage.org/objId" } }

2017-12-12 18:20:08 +0100 answered a question Help me to clarify some points


Easy way, publish your CKAN data as Orion Broker entities.

Some existing data models are at http://schema.fiware.org

and the Orion Broker APIs Summary are at


2017-11-30 09:43:15 +0100 commented answer CCTV Software company, want to apply for IMPACT(SmartCities, Ph2). Which APIs to use?

josemanuel.cantera at fiware dot org

2017-11-30 09:39:48 +0100 answered a question Need help regarding fiware iot

have you read this resource?


2017-11-30 09:36:50 +0100 answered a question CCTV Software company, want to apply for IMPACT(SmartCities, Ph2). Which APIs to use?


Sounds like a nice project. I think you should be using Kurento and Orion, but nonetheless I would like to have a conversation with you


2017-10-20 09:14:00 +0100 answered a question I need to make Rest calls from an external server

please check the public IP of your instance under https://cloud.lab.fiware.org

2017-10-20 09:02:41 +0100 answered a question I have a problems please help me I need

you need to connect to the Cloud portal (http://cloud.lab.fiware.org) in order to know what is the public IP address of the virtual machine on which Orion is running (under the instances section). Then, probably you need to check your security groups so that the 1026 port is open. I think you don't need to manage it directly through the firewall command, it can be done through the portal.

I cannot find now a tutorial of the FIWARE Lab, please someone from the community can complement this response?


2017-10-11 17:45:45 +0100 answered a question hello please help

this seems to be a network connectivity problem. please check that you get access to any other external service or address


2017-10-11 17:39:38 +0100 answered a question Communication between Orion or Cepheus Broker and Android
2017-10-11 17:36:59 +0100 answered a question xamarin studio y fiware

Please have a look at



2017-04-08 13:53:20 +0100 answered a question Raspberry Pi and Fiware


As the Raspberry Pi is a device that can speak FIWARE NGSI directly, the easiest way would be to use a Python script to obtain the data coming from the Raspberry Pi Sensors and then use the NGSIv2 API to publish the data offered by the sensors connected to the Raspberry on a Orion Context Broker.

You can deploy your own Orion Context Broker instance, on your laptop, for instance using Docker

docker run fiware/orion

You can pre-create the entity you are going to use to store the sensor data, for instance:

POST /v2/entities

{ "id": "MyObservation-RaspberryPi-890", "type": "Observation" }

Then every time a new sensor measurement is obtained from the Raspberry Pi you can

POST /v2/entities/MyObservation-RaspberryPi-890/attrs

{ "temperature": { "value": 23.5 } }

You can get the temperature value by getting your entity data as follows:

GET /v2/entities/MyObservation-RaspberryPi-890?options=keyValues and you will get something like

{ "id": "MyObservation-RaspberryPi-890", "type": "Observation", "temperature": 23.5 }

Of course, your laptop and the Raspberry Pi have to be on the same network.

Other architectures more complicated could make use of IoT Agents but in this case it is not even needed.

I hope this helps


2017-04-07 12:36:53 +0100 answered a question Seeking Expert Consultation for Fiware use in our startup

we have got in touch with you through email


2017-01-25 09:37:52 +0100 commented answer How your FIWARE integrated with different other SW, that already used city government?

yes, indeed

2017-01-20 08:56:37 +0100 answered a question How your FIWARE integrated with different other SW, that already used city government?

FIWARE based architectures are open, modular and scalable. This means that integrating existing systems can be quite easy thanks to this characteristic inherent to FIWARE. As a result FIWARE can coexist with legacy architectures, Furthermore FIWARE does not preclude operating systems or programming environments.

Having said that, and with regards to Context Data managed by the city, the NGSI9 context providers are a nice mechanism to integrate existing data sources and expose them as NGSI entities. For more information, please check


2017-01-20 08:49:05 +0100 answered a question How you organize the support of partners, which develop project on base of FIWARE?


There can be two kinds of support:

  • Community given support. It is the support we provide through this portal or through askbot. It depends on the voluntary work of the Community

  • Professional support. There are varios companies and universities knowledgeable with FIWARE and you can ask them paid support services. You can get in touch with the FIWARE Foundation to know more about this option.

I hope this helps

2017-01-20 08:42:46 +0100 answered a question Tourguide App: problem sending data to sensor


you cannot have in your entity any property measured by sensors if you don't POST IoT data to an IoT Agent. You have only registered your service and your device ... i.e. you have finished the configuration phase and now you need to actually send data.

Please check http://fiwaretourguide.readthedocs.io... and the point entitled "Send Observations related to your IoT device".

That can be done manually as described by the guide above or you can use the CLI provided by the Tour Guide Application, see


Wrt to the error you get when do not provide the type parameter maybe there are other entities with the same id, that by mistake you created. As Orion Context Broker uses type and id as the entity key if you don't specify the type explicitly more than one entity will match, and as a result, you get that error

I hope this helps


2017-01-12 11:41:51 +0100 answered a question Ultralight Evolution

to the best of my knowledge there is no a UL version 1.0 .


2017-01-06 11:28:39 +0100 answered a question Ultralight Protocol Documentation


The UL2.0 protocol is a simple text-based protocol which allows IoT devices to provide data or receive commands. UL2.0 has been defined by the FIWARE Community and its evolution is community-driven. You can find more information about the protocol at http://fiware-iotagent-ul.readthedocs... , which corresponds to the readthedocs documentation of the FIWARE IoT Agent for UL 2.0.

I hope this helps


2016-12-19 09:47:02 +0100 answered a question Do we have to install FIWARE GE ourselves?

The options are:

A/ you can install any FIWARE GE yourself, following installation procedures (for instance from a yum package) or using a Docker container,

B/ you can use a FIWARE Lab Image which already has embedded and configured a GE

C/ or you can use a public instance, ex. orion.lab.fiware.org. The latter should only be used for early experimentation purposes.

I hope this helps

2016-12-07 10:52:52 +0100 answered a question FIware IoT Ready / benefits for agricultural applications

of course

See this article published this year, http://www.sustainablecitiescollectiv...


"For instance, let’s consider a smart water solution that could be developed to optimize water supplies to farms. If a farm has a soil sensing system built on proprietary technologies it will not be able to interoperate, at a data level, with the smart water solution and as a result the farm will be isolated, and will have to spend additional time and money to connect to the water management solution. The main point here is that vertical, proprietary solutions might work initially but might have scalability problems in the end affecting both the end customer and the solution provider.”

2016-11-15 21:04:05 +0100 edited answer Get entities (geo:point) ordered by distance

This kind of technical question about Orion and its API is better asked at StackOverflow, so it has been moved to http://stackoverflow.com/questions/40....

Have a look to this Q&A post regarding when to ask using Askbot and when to ask using StackOverflow.

2016-11-15 21:01:16 +0100 answered a question Starting the tour-guide application

please follow the steps from this page on and let us know if it works for you and what the problems are



2016-10-27 22:12:38 +0100 received badge  Nice Answer (source)
2016-10-26 10:03:37 +0100 edited answer At DataModels, What's the difference between 'timestamp' and 'dateModified'?

Be careful the semantics of timestamp and dateModified are different.

timestamp captures as an ISO8601 timestamp when the associated measurement (represented as attribute value) was observed.

dateModified captures the last modification date and time of an attribute.

Typically dateModified will be >= than timestamp particularly on IoT networks such as SIGfox or Lora that only transmit data at certain time slots.

literally from the guidelines:

Use a metadata attribute named timestamp for capturing the last update timestamp of a dynamic attribute. Please note that this is the actual date at which the measured value was obtained (from a sensor, by visual observation, etc.), and that date might be different than the date (metadata attribute named dateModified as per NGSIv2) at which the attribute of the digital entity was updated, as typically there might be delay, specially on IoT networks which deliver data only at specific timeslots.

With regards to the particular example of this question, batteryLevel is an observed value, so a timestamp makes sense, even though the attribute may have a dateModified metadata as well.

On the other hand it has been considered that configuration is a kind of semi-static attribute which, informatively, conveys the device's current configuration. As it is not bounded to any measurement, it is only used the dateModified attribute. If it happens that you want to capture the date and time on which such configuration was made effective on the device, (provided there is some kind of automatic configuration procedure) then it would make sense to add another metadata representing such instant of time. But, we have assumed that in this case this distinction might not very relevant, and as a result we only propose to use the dateModified attribute.

I hope this clarifies.