Posts made by magnatron

Would it be possible to not have 2 separate users for Portal and API?

It is confusing to me to have “some” magic but not all:

• Devices added are visible for both
• But subscriptions are separate
• The application added through portal will NOT be subscribed to devices added through API
• The application added through API seems tp be subscribed to devices added through portal (or is it?)
• It’s not possible to verify through portal what you did through API

Being a platform for creators this seems cumbersome to me. I’m unaware of the benefits of this separation so probably I’m missing some needed insights. But maybe it is architected this way from a vision which is no longer applicable?

Is it possible to explain the reasoning behind this separation and indicate if this is something that might (not) change in the (near) future?

Thanks

Hi,
On page https://docs.iotcreators.com/docs/whitelisting-the-cdp it is mentioned that CDP has 2 outgoing IP addresses’s.
However: these 2 addresses never hit our application where a couple of hundred other s do. All AWS addresses.

The mentioned page was last updated about a year ago. Did something change? Is there another way to whitelist the CDP?

Thanks

@Yassine-Amraue thnx, I’ll check.
But devices added by API user are also displayed in GUI and vv, right?
So is there some “magic” happening linking the two together on some processes but not on others?

Also, the downlink works via the portal. Just not via the API.

Oh, and the application is receiving them and handling them returning 200 status

@Uta, yes. I read that. It’s a running project that has been sending uplink messages for some time now.

Hello,
I cannot get the downlinkMsg endpoint to work using these instructions:
https://docs.iotcreators.com/docs/6-send-downlink-message-to-devkit

What ever I try, I get a status 403 with { "msg": "Unauthorized", "code": 1001 }

The application is set, tried with/without IMEI: prefix, tried both regular and HEX message.

Any advice?

@afzal_m
Got my phone here. I see your messages now.
Thanks

It would be nice if you could expose a status-page so I can first check if you are already aware and don’t have to start these threads when we notice things going wrong on our end.

Any chance of getting something like that up any time soon?

Do you mean that this was not so much an issue of the API but of the whole platform?

Several calls to the API are timed out with status 504.

It’s a lot faster as well! It never crossed 5 seconds. So I’m not sure what will happen when one is set to import hundreds and crosses a time limit.

NOICE!

Only thing left is some descriptive labels in the English locale

(And what are those mysterious crossroads DELETEing?)

@Kolja-Vornholt The problem was as summarized:

• I’ve set our modem to band 20-only.
• I want to use auto-attach (at+cops=0) but it did not find a network
• However, manual attach (with selecting Vodafone’s network) did work

Doing something else for about 30 minutes around the time @Kolja-Vornholt left the reply about searching the network.
Trying the search only gave me seemingly non-related info (“90104”),
But trying the auto-COPS suddenly did the trick and attached in no time.

So, it doesn’t really seem like a solution yet…

@Kolja-Vornholt
Maybe some things had to settle. The auto-COPS is working now. About as fast as on band 8. But I have to check if it is just this modem or if it also works for others now.
I’ll get back to you about it.

@Florian-Duecker I suggest to put the instructions from https://forum.iotcreators.com/topic/715/batch-import-excel-csv into the docs.

In regards to the subscription: It will probably be fixed with the update but this is what I mean:
When importing devices, one device was successfully added to “all devices” as I could see by polling the API.
But it was not added to the subscription as I could see by polling the subscription API endpoint.
So I guess somewhere between adding and subscribing, things went haywire.

Looking forward to the update!

@Florian-Duecker another request/suggestion:
Can you make the registration in the portal so that if registration is successful but subscription is not the registration is discarded?

I’m having to manually check the imported devices for subscription because some of them are successfully registered but were not added to the application.

Hi @Florian-Duecker, Great to hear that!
I’m not seeing the suggestion about a row for headers in the import dialog. I’ve really looked for it. So it’s great to hear you will be doing auto detect.
Can I make some other suggestions?

• The feedback now disappears after a couple of seconds. It would be great to leave this so there’s no need to wait for it when importing a large list. Maybe even e-mail the results?
• The import procedure now halts on a single-IMEI-import-error (e.g. the IMEI is already known) but it’s not clear what the error is or which IMEI’s were succesfully imported. This could (should) be made clear in the feedback.
• Be clear about which labels are allowed for the protocols. Because of the errors I was not sure if it should be CoAP or COAP or NEUL or ? Are they required anyway? Because when entering a single device (after the very first device) there is no option to choose a protocol.

It might just be a ‘regular’ 30 seconds script timeout. (Because it errs around 30 seconds after clicking the IMPORT DEVICES button)

This is the error message:

Only happens with more than 1 device

The import-via-CSV function in the portal is not totally clear to me.

• The IMEI in the first row is ignored. I think it might be good to state that somewhere.
• Only the first 3 rows (after the ignored initial) are imported.

More rows make the process end with an unclear error stating the devices could not be imported. But the first 3 are imported anyway.
I checked but I was able to import the IMEI in row 4 without problems.

@Kolja-Vornholt haven’t really measured it. What time period should I take into account?

Hi @Kolja-Vornholt,

Yes, that’s completely correct. Any tips?