[Fiware-fractals-coaching] [Fractals][Smarthive] Orion/IDAS issue

[Romero, Javier]

Dear coachers

We have received the following issue from Smarthive

Hello,

We use the public Orion/IDAS instance.
The context of our Config.ini:
                [user]
                # Please, configure here your username at FIWARE Cloud and a valid Oauth2.0 TOKE
                username=gyorgy.fulop at r-key.eu
                #token=d8841e6692834c029d7267830369b95c
                #token=387c2c8eec9f4249a2f052
                token=a47540aaf5f0480284a1b188ffb8c1f9
                [contextbroker]
                host=130.206.80.40
                #host=eidas5.lab.fi-ware.org
                #host=148.6.80.103
                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
                fiware_service=smarthives
                fiware-service-path=/
                [idas]
                host=eidas5.lab.fi-ware.org
                #host=148.6.80.103
                adminport=5371
                ul20port=5371
                OAuth=no
                # Here you need to configure the IDAS service your devices will be sending data
                # By default the OpenIoT service is provided..
                fiware-service=smarthives
                #fiware-service=smarthives
                fiware-service-path=/
                #apikey=4jggokgpepnvsb2uv4s40d59ov
                apikey=4jggokgpepnvsb2uv4s40d59ov
                [local]
                #Choose here your System type. Examples: RaspberryPI, MACOSX, Linux, ...
                host_type=RaspberryPI
                # Here please add a unique identifier for you. Suggestion: the 3 lower hexa byte
                # Also you may use your e-mail address.
                host_id=b8:27:eb

First we did a service, because we have go error message if we used the "OpenIot" and fiwareiot, or the registration of sensor wasn’t possible.
used command:                python CreateService.py smarthives 4jggokgpepnvsb2uv4s40d59ov
After that – with the new smarthives service - the sensor registration was succesfully.
used command:                python RegisterDevice.py SENSOR_TEMP smhive0001 temp001

If we try list devices, it works.
used command:                 python ListDevices.py

As we think, we can send data about sensor status – send observation is possible.
used command:                 python SendObservation.py smhive0001 't|34'

Result:
                               * Asking to http://eidas5.lab.fi-ware.org:5371/iot/d?k=4jggokgpepnvsb2uv4s40d59ov&i=smhive0001
                               * Headers: {'Fiware-Service': 'smarthives', 'content-type': 'application/json', 'Fiware-ServicePath': '/', 'X-Auth-Token': 'NULL'}
                               * Sending PAYLOAD:
                               t|34
                               ...
                               * Status Code: 200
                               * Response:
Buti f I try query the data of that sensor – which was sent uppon:
used command:                python GetEntity.py temp001

Result:                * Status Code: 200
                * Response:
                {
                  "contextResponses" : [
                               {
                                 "contextElement" : {
                                               "type" : "thing",
                                               "isPattern" : "false",
                                               "id" : "temp001",
                                               "attributes" : [
                                                 {
                                                               "name" : "TimeInstant",
                                                               "type" : "ISO8601",
                                                               "value" : "2015-10-04T19:01:11.410965Z"
                                                 },
                                                 {
                                                               "name" : "att_name",
                                                               "type" : "string",
                                                               "value" : "value",
                                                               "metadatas" : [
                                                                 {
                                                                              "name" : "TimeInstant",
                                                                              "type" : "ISO8601",
                                                                              "value" : "2015-10-04T19:01:11.411333Z"
                                                                 }
                                                               ]
                                                 }
                                               ]
                                 },
                                 "statusCode" : {
                                               "code" : "200",
                                               "reasonPhrase" : "OK"
                                 }
                               }
                  ]
                }

And nowhere is the sent 't|34' data…

I think we have similar problem like we have find here: http://stackoverflow.com/questions/32933813/fiware-no-observation-attributes-in-orion-cb-when-registered-sent-via-idas-ultr?answertab=active#tab-top
But I don’t know where is the misconfiguration, or which step wasn’t good.
Can you help us, what is our misconfiguration, or what must us reconfigure?

Thanks for the help

Best Regards
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-fractals-coaching/attachments/20151005/0d7da7ba/attachment.html>