Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define resource path on service group and use it to send measurements #590

Open
thinkingmik opened this issue Mar 23, 2023 · 2 comments
Open

Comments

@thinkingmik
Copy link

Hi,

I'm using docker image fiware/iotagent-ul:1.25.0 and I have a problem with iota service group and sending device measurement to it.

This is my service group (note the resource attribute set as /iot/json/mydevice):

{
    "services": [
        {
            "apikey": "52t4z7url7",
            "cbroker": "http://orion:23626",
            "entity_type": "Device",
            "resource": "/iot/json/mydevice"
        }
   ]
}

If I send a measurement like:

POST /iot/json/mydevice?k=52t4z7url7&i=001
Host: iotagent:23632
Content-Type: text/plain

temp|14

The endpoint respond with 404. It only works with default resource path /iot/d.
Why I can't be able to send measurement to my custom resource path /iot/json/mydevice?

@KeshavSoni2511
Copy link
Contributor

Hi @fgalan, I have investigated the issue and found some fix.
I was able to post and get services when I do changes in config.js file as default resource from iot/d to iot/json/mydevice.
I would like to know if it is possible if we can create multiple services on different resource path as I was unable to do so.

@fgalan
Copy link
Member

fgalan commented May 9, 2023

I would like to know if it is possible if we can create multiple services on different resource path as I was unable to do so.

It would be a nice to have feature. It would be great if somebody in the community (maybe you? ;) could contribute with a pull request implementing it. The issue has been marked with "help wanted" label. Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants