Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:IoT
-
HD-Enabler:IDAS
Description
Hi,
I have been trying to get UL2.0 via IDAS to the CB working:
- using latest GitHub
https://github.com/telefonicaid/fiware-figway/tree/master/python-IDAS4
scripts - following the tutorials in particular
http://www.slideshare.net/FI-WARE/fiware-iotidasintroul20v2
I have a FI-WARE Lab account with token generated. Changed the
config.ini file:
[user]
- Please, configure here your username at FIWARE Cloud and a valid
Oauth2.0 TOKEN for your user (you can use get_token.py to obtain a valid
TOKEN).
username=MY_USERNAME
token=MY_TOKEN
[contextbroker]
host=130.206.80.40
port=1026
OAuth=no
- Here you need to specify the ContextBroker database you are querying.
- Leave it blank if you want the general database or the IDAS service if
you are looking for IoT devices connected by you. - fiware_service=
fiware_service=bus_auto
fiware-service-path=/
[idas]
host=130.206.80.40
adminport=5371
ul20port=5371
OAuth=no
- Here you need to configure the IDAS service your devices will be
sending data to. - By default the OpenIoT service is provided.
- fiware-service=fiwareiot
fiware-service=bus_auto
fiware-service-path=/
#apikey=4jggokgpepnvsb2uv4s40d59ov
apikey=4jggokgpepnvsb2uv4s40d59ov
[local]
#Choose here your System type. Examples: RaspberryPI, MACOSX, Linux, ...
host_type=MACOSX
- Here please add a unique identifier for you. Suggestion: the 3 lower
hexa bytes of your Ethernet MAC. E.g. 79:ed:af - Also you may use your e-mail address.
host_id=a0:11:00
I used the SENSOR_TEMP template, including the 'protocol' field
(PDI-IoTA-UltraLight which as the first problem I stumbled upon):
{
"devices": [
{ "device_id": "DEV_ID",
"entity_name": "ENTITY_ID",
"entity_type": "thing",
"protocol": "PDI-IoTA-UltraLight",
"timezone": "Europe/Amsterdam",
"attributes": [
],
"static_attributes": [
]
}
]
}
Now I can Register the device ok. Like
python RegisterDevice.py SENSOR_TEMP NexusPro Temp-Otterlo
and see it in Device List:
python ListDevices.py
I can send Observations like
python SendObservation.py Temp-Otterlo 'otemp|17'
But in the ContextBroker I see the Entity but never the measurements, e.g.
python GetEntity.py Temp-Otterlo
- Asking to http://130.206.80.40:1026/ngsi10/queryContext
- Headers: {'Fiware-Service': 'bus_auto', 'content-type': 'application/json', 'accept': 'application/json', 'X-Auth-Token': 'NULL'}
- Sending PAYLOAD:
{
"entities": [ { "type": "", "id": "Temp-Otterlo", "isPattern": "false" }],
"attributes": []
}
...
- Status Code: 200
- Response:
{
"contextResponses" : [
{
"contextElement" : {
"type" : "thing",
"isPattern" : "false",
"id" : "Temp-Otterlo",
"attributes" : [
{ "name" : "TimeInstant", "type" : "ISO8601", "value" : "2015-10-03T14:04:44.663133Z" },
Unknown macro: { "name" }]
{ "code" : "200", "reasonPhrase" : "OK" }
},
"statusCode" :}
]
}
I get an TimeInstant attribute strangely. I tried playing with settings
of the .ini like fiware-service=fiwareiot, but to no avail. I am out of
ideas. The documentation at
http://catalogue.fiware.org/enablers/backend-device-management-idas/instances/global-instance-ul20http-iot-agent-release-4
is talking about observations to be sent to port 8002 and setting
"OpenIoT" service, but that failed.
Any help is appreciated.
–
kind regards / met vriendelijke groet,
--Just
Just van den Broecke
The Netherlands
www.justobjects.nl
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Just van den Broecke <just@justobjects.nl>]
Activity
- All
- Comments
- History
- Activity
- Transitions
Answered in Stackoverflow.