Dear support team,

I'm experiencing some strange behavior while working with the IDAS and ContextBroker. I'm using the fiware-figway SDK repo, python version (https://github.com/telefonicaid/fiware-figway/tree/master/python-IDAS4/), on a CentOS 6.7 machine with Python 2.7.11; I've no firewall restrictions since I'm using a Virtual Machine in a dedicated server with a public ip.

Let me reproduce the issues I'm facing:

• First, have a look at the default config.ini. The fiware-service is set to bus_auto, so I made both test with that variable to 'bus_auto' and also with 'OpenIoT' as explained here http://catalogue.fiware.org/enablers/backend-device-management-idas/instances:

o << In order to get straight access to this instance, please use "OpenIoT" service.
The API-Key (shared secret to be known by devices to publish in a service) for "OpenIoT" is:
APIKEY: 4jggokgpepnvsb2uv4s40d59ov >>

o Well, in fact I had to set fiware-service=openiot rather than fiware-service=OpenIoT because of the following:

§ << * Status Code: 400

• Response:

>>

o So, I made this tests in both fiware-service=bus_auto and fiware-service=openiot

o I'm asking for a new token each day using get_token.py

• I'm registering a device using Sensors_UL20/RegisterDevice.py with a model I've defined: SENSOR_MODEL_PI_01 (attached). It contains 2 attributes and 2 static_attributes. I had to add the property "protocol": "PDI-IoTA-UltraLight" so to make things work (the repo is not updated, but that issue remains opened https://github.com/telefonicaid/fiware-figway/issues/3).

o Once registered, I launch ContextBroker/GetEntity.py in order to obtain info about my newly created Entity. However, the response shows a JSON in which only the static_attributes appear, not the non-static ones (in this model, temperature and voltage).

• When it comes to sending measurements (observations), I'm using the script Sensors_UL20/SendObservation.py. If we attend to the default config.ini file, it's using the same port for the IDAS ADMIN REST API and for sending UL2.0 observations (port 5371). As explained here, http://catalogue.fiware.org/enablers/backend-device-management-idas/instances, port 8002 should be used for sending UL2.0 observations. However, that port seems to be closed/filtered in the instance, so no luck sending observations. In fact, it's quite confusing that I can still send observations using port #5371 and the response is a "Status Code 200", so ok.

Basically, I'm experiencing the same issues and applying same solutions as in here: http://stackoverflow.com/questions/32933813/fiware-no-observation-attributes-in-orion-cb-when-registered-sent-via-idas-ultr But still it doesn't work.

Any help would be more that appreciated.

Best Regards,
Juan

Juan Sancho
Internet of Everything Lab
ATOS Research & Innovation

T +34 946 662 065
M +34 697 976 638
Av. Capuchinos Basurto, 6, 3ºB
48013 Bilbao - Spain
atosresearch.eu
[atos_logotype]

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

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-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help
[Created via e-mail received from: "Sancho, Juan" <juan.sancho@atos.net>]