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

tomsluyts's profile - activity

2018-03-05 12:41:21 +0100 received badge  Popular Question (source)
2018-03-05 12:41:21 +0100 received badge  Notable Question (source)
2018-03-05 12:41:21 +0100 received badge  Famous Question (source)
2018-01-24 14:19:23 +0100 answered a question Fiware Data Model Usage - Device Functioning Messages

Thanks for the answer.

Alerts look like the way to go, I'll see if I can get the required time for the required changes to make it work and do the Pull Request.

2018-01-23 08:25:00 +0100 asked a question Fiware Data Model Usage - Device Functioning Messages

Hi there,

We are currently looking into the implementation of the Fiware data model. First trial would be waste baskets that send data.

They have two types of messages at source.

One is related to fillingLevel, etc -- that one is easy and nicely fits into the WasteContainer data model.

The second type are "alert" and are related to the functioning of the device itself, stuff like batterylevellow, or no_network or something like that.

Our idea is to put that data in a "device" entity with a pointer to it's WasteContainer entity, but is that the right way to go about it? WasteContainer itself doesn't look like the right fit, on the other hand we're also not describing device in the sense of sensors either...

So config, status and alarms would go into the device, measurement from a more business perspective into the entity.

We want to get our model right from in the beginning, so alle help is appreciated!