Hello everyone!
Dear @drasko @nmarcetic give some advices please.
My question concerns dynamic configuration.
Are there some ways to get data flow from new things which was added after app connection with Mainflux had established?
In more detail:
1) create Mainflux user
2) under created user create things: "a", "b", "c" and application "app" and channels.
3) Things ("a", "b", "c") start to publish data , thing("app") start to subscribe, and it works well.
4) After that user forget to add thing "d", and create it.
So how to get data flow from thing "d" without restarting subscribe thing "app"?
Thanks
they are stateless in order to be clusterable, so we do not change their internal state
What you should do with your app is not to subscribe directly to NATS, but rather go via frontend protocol adapters (MQTT, WS, CoAP, HTTP, ...)
this way you can subsribe/unsubscribe dynamically
NATS is in internal network and is good for internal applications / DB writers
however when building outside applications on the top of Mainflux, better is to treat them like ordinary things and use their API keys for auth
Being in internal network, NATS is not protected by the auth
That being said - you can just use config file to subscribe to all NATS channels (
*)
Hi everybody, I have developed a micro-service to forward message by HTTP. Currently, it is a version for the mainflux release v0.11.0 but I will update the code for the next release (v0.12.0). The source code is available here.
As discuted with @drasko in the PR #1158, I have migrated the PR in an extension of the mainflux platform. Dont' hesitate to open issues if you have comments, ideas, etc.
As discuted with @drasko in the PR #1158, I have migrated the PR in an extension of the mainflux platform. Dont' hesitate to open issues if you have comments, ideas, etc.
I'll take a look
I didn’t know if somebody has already tried to use in Go the upstream components, because I have some trouble to do that. For the next release of http-forwarder (v0.12.0), I try to use components which provide from "master" to anticipate the next release (and also create a CI which are tested the integration of those components into this extension).
The returned error is:
The returned error is:
go: github.com/jonathandreyer/mainflux-httpforwarder/cmd/http-forwarder imports
github.com/mainflux/mainflux/messaging/nats: package provided by github.com/mainflux/mainflux at latest version v0.11.0 but not at required version v0.11.1-0.20210209214404-f0f60e2d2a2c
Hi everybody, I have started testing the provision service with the release v0.11.0, but it returns the error:
mainflux-provision | {"level":"warn","message":"Method provision for token: <TOKEN> and things: [] took 54.290893ms to complete with error: failed to create bootstrap config : failed to create entity : 405 Method Not Allowed.","ts":"2021-02-21T21:38:20.369064276Z"}
mainflux-bootstrap | {"level":"warn","message":"Method bootstrap for thing with external id <EXTERNAL_ID> took 4.531134ms to complete with error: non-existent entity.","ts":"2021-02-21T21:38:20.380319273Z"} Somebody has already had this error? For information, I have also tested with the master version and there is no error.
In reading the documentation, I have found something strange on the page for the provision service (here). The port of two first requests (
8888 and 8091) seems wrong because in the .env it is indicated 8190. If you would like, I can create a PR to fix that in the doc repository.
When I have started to use the provision service (as an add-on) in following the documentation, the example does not work because an error related to certificate generation is returned. I have discovered that it is necessary to start also the certs service or disable his usage in
.env by environment variable MF_PROVISION_X509_PROVISIONING. This issue has been generated by the #1221. To fix that, I propose to disable the usage of certs provisioning as it is indicated in the README.md of the provision service. @MF-Teams, what is your point of view?
I have also discovered two mistakes in the provision service, one in the docker-compose (environment variable
MF_PROVISION_LOG_LEVEL is duplicated) and one in the README.md environment variables MF_PROVISION_HTTP_PORT, MF_PROVISION_SERVER_KEY, MF_PROVISION_PASS & MF_PROVISION_USER is duplicated). As for the documentation repository, I can create a PR to fix that.
@jonathandreyer I've created a PR to sort the different ports and default value for provision https://github.com/mainflux/mainflux/pull/1367/files, for the docs you can make a PR, thanks
MF_PROVISION_BS_SVC_URL set to http://localhost:8202/things
@mteodor I have another question regarding the provision service. When I provision a new device (with the provision service), I have multiple information added into metadata field of the thing (like
'cfg_id': '<THING_ID>', 'ctrl_channel_id': '', 'data_channel_id': '', 'export_channel_id': '', 'type': 'gateway’), which are not useful for a simple device. I understand that in some of your case (e.g. a gateway) that is useful. Is it possible to disable that information? The temporary idea can be to rewrite the content of metadata of things after the provision (without this field) but that seems a bit strange to have a cleaned thing configuration.
@mteodor Thanks for your reply and your support. I have tested the temporary idea and it is working fine. So I will use is.
I have another question/remark (sorry for my many questions). Yesterday, I have tested the get request to see which content is used and it doesn't work. Today, I have tested it again with the full default config (docker & config.toml) and there is really a trouble. The returned code is
Does it another trouble in my configuration or an error in the service?
I have another question/remark (sorry for my many questions). Yesterday, I have tested the get request to see which content is used and it doesn't work. Today, I have tested it again with the full default config (docker & config.toml) and there is really a trouble. The returned code is
500 and the internal error is : mainflux-provision | {"level":"warn","message":"Method mapping for token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2MTQyMzYxNTIsImlhdCI6MTYxNDIwMDE1MiwiaXNzIjoibWFpbmZsdXguYXV0aCIsInN1YiI6ImFkbWluQGxvY2FsaG9zdC5sb2NhbCIsImlzc3Vlcl9pZCI6ImVmODNiZDk2LTY3NDctNGVjZS04ZmFmLTY3YzllMDExMmM2NyIsInR5cGUiOjB9.G8J2yyy47Kd9UaB0FVN7VfJWkeRl_lUo3Sl3rGJtCII took 6.51463ms to complete with error: unauthorized access : failed to fetch entity : 404 Not Found","ts":"2021-02-24T20:55:52.502075499Z"}Does it another trouble in my configuration or an error in the service?
my coap url : coap://" + "54.162.61.126" + ":" + "31739" + "/" +
"channels/cabf1231-7aef-4e70-a780-4a6c69fa212d/messages?authorization=54919bc7-3c6d-4d03-948c-75104ea1eaa5
"channels/cabf1231-7aef-4e70-a780-4a6c69fa212d/messages?authorization=54919bc7-3c6d-4d03-948c-75104ea1eaa5
error on the console ::{"level":"warn","message":"Failed to authorize: bad request","ts":"2021-02-28T14:18:42.837932711Z"}
{"level":"warn","message":"Failed to authorize: bad request","ts":"2021-02-28T14:18:47.868028109Z"}
whats is wrong in this url ??
{"level":"warn","message":"Failed to authorize: bad request","ts":"2021-02-28T14:18:47.868028109Z"}
whats is wrong in this url ??
in coap url authorization will be thing key right?
client.observe(
new CoapHandler() {
@Override
public void onLoad(CoapResponse response) {
String content = response.getResponseText();
log.info("value ::::: {} ",content);
}
@Override
public void onError() {
log.error("OBSERVING FAILED (press enter to exit)");
}
},0);
log.info("End with response ::::::::::::: {}");
};
new CoapHandler() {
@Override
public void onLoad(CoapResponse response) {
String content = response.getResponseText();
log.info("value ::::: {} ",content);
}
@Override
public void onError() {
log.error("OBSERVING FAILED (press enter to exit)");
}
},0);
log.info("End with response ::::::::::::: {}");
};
@krishna70425541_twitter is payload OK? I mean senml
@drasko this is my message post request client.post(message+ LocalDateTime.now().getSecond(), MediaTypeRegistry.TEXT_PLAIN,0);
and now sending with client.post("[{\"bn\":\"some-base-name:\",\"bt\":1.276020076001e+09, \"bu\":\"A\",\"bver\":5, \"n\":\"voltage\",\"u\":\"V\",\"v\":120.1}, {\"n\":\"current\",\"t\":-5,\"v\":1.2}, {\"n\":\"current\",\"t\":-4,\"v\":1.3}]", MediaTypeRegistry.APPLICATION_SENML_JSON,110);
but not able to receive the messages from the coap server ?
clone the repo, deploy, add some logs if needed
Here is a Developer's Guide to get you started: https://mainflux.readthedocs.io/en/latest/dev-guide/
All of the docs I found were for docker compose, so I am not sure how to provision the system
I tried posting directly to the users microservice at port 8180, and was able to create a user, but when I post to the /tokens of the same endpoint with that user, I get: "error "non-existent user"