I can confirm that is not data from another node. We have some problems on a VPN tunnel in our network. And we’re looking for a solution.
Posts made by afzal_m
-
RE: Data from another node
-
RE: Data from another node
That’s annoying!
How often do you expect data from this device?
And are you using coap or UDP? -
RE: Where is the free community edition?
Yes and no. :smiling_face_with_open_mouth_cold_sweat:
The community package was a Dutch proposition based on a promise that T-Mobile Netherlands made. And it is not something that we can offer in other countries.
It’s still available in our back-end. If you or anyone else in NL needs the package, pls just drop me a direct message here or via hello@iotcreators.com!
-
RE: Graag downlink voorbeeld door rechtstreeks de api te gebruiken
Does it also work for @trick2011 now?
-
RE: Add subscriptions via api
Thanks a lot @JeroenD. Maybe you are not aware of it but last month with did a major update on the document library after two years. But we only focused on the devices part.
In August we will update the API part as well
@Roalnd-Baldin is already working on it. -
RE: Graag downlink voorbeeld door rechtstreeks de api te gebruiken
I just tested the downlink and it works. But I have to admit, for it it was just clicking a button on a GUI.
But now I am sure that it is probably an issue with our explanation.
I am going to translate the threads here and @Yassine-Amraue will come with a response tomorrow.
-
RE: Add subscriptions via api
I just talked to @Yassine-Amraue , he will get back to your question not later than tomorrow @JeroenD
-
RE: Add subscriptions via api
Nevertheless, if it works find in the back-end I think the issue is related to this one:
https://forum.iotcreators.com/topic/583/no-device-data-in-gui -
RE: Add subscriptions via api
But you said: 'if I go to my account and look at ‘Projects’…
-
RE: Add subscriptions via api
Hmm thats odd, maybe because we’re migrating from iot.t-mobile.nl to iotcreators.com.
Can you please log out, delete cookies, clear cache, log-in and try again?
-
RE: No device data in GUI
To give a good explanation of what exactly is going on, I also have to give some context.
Each project is connected to a tenant on our Service Capability Server.
After registering an IMEI in our GUI you usually switch your device on and it will send its first uplink message. The Service Capability Servers considers the first uplink message as a registration message. So on top of the payload it will add some additional information: to which tenant the sending device belongs.
This registration message is very important to our GUI. It tells our GUI that it belongs to your tenant. This way, our GUI will know that we can show the payload in your project (since you are the owner of the tenant).
So what’s the problem?
Our Service Capability Server has a separate queue for registration messages. And this queue is overloaded. The registration messages are arriving with a delay of hours/days. Our team is still trying to find out why it is overloaded and how we can fix it.
The good thing: it is a separate queue. For non-registration messages (your regular uplink messages) there is no delay. If you configure the callback URL of your own application server/IoT platform, you will receive your device data right away.
Unlike our GUI, your application doesn’t care about this registration message.
Hope to have more news tomorrow in the afternoon.
-
RE: Quectel BC66 sending messages but not received in the T-mobile NL Portal
Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.
-
RE: Not able to connect BG96
Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.
-
RE: Bericht komt niet aan
Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.
-
RE: message not arriving
Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.
-
No device data in GUI
As some of you have already experienced, we have problems displaying the latest device payload in the project GUI.
Our colleagues have been investigating for some time and unfortunately we haven’t found a solution yet.
In the meantime:
This doesn’t mean you can’t get your device data. When you register the callback URL of your application (server), your device data will still be forwarded to the destination you specified.
If you don’t have an application server and only use our GUI to see if your messages are coming in properly, use beeceptor for the time being.
As soon as we have an update, we’ll let you know here.
-
RE: Quectel BC66 sending messages but not received in the T-mobile NL Portal
Our lead devops guy just gave me heads up that the errors should be gone right now…
But on the other heard I just also heard that the initial problem is still there
-
RE: Quectel BC66 sending messages but not received in the T-mobile NL Portal
That has maybe something to do with the domain migration which we are doing now…
Pls
- go to portal.iot.t-mobile.nl and log-out
- go to portal.iotcreators.com and log-in
-
RE: Quectel BC66 sending messages but not received in the T-mobile NL Portal
That’s strange… you can not login… but you’re online at the forum?
-
RE: Quectel BC66 sending messages but not received in the T-mobile NL Portal
Unfortunately still no root cause. But we have enough logs for further troubleshooting.
We just restarted the affected component. As of now, you should be able to see the payloads again. Maybe you need to delete and register the device before you see result.
-
RE: message not arriving
Unfortunately still no root cause. But we have enough logs for further troubleshooting.
We just restarted the affected component. As of now, you should be able to see the payloads again. Maybe you need to delete and register the device before you see result.
-
RE: Bericht komt niet aan
Unfortunately still no root cause. But we have enough logs for further troubleshooting.
We just restarted the affected component. As of now, you should be able to see the payloads again. Maybe you need to delete and register the device before you see result.