iotcreators.com web
    • Login
    • Search
    • forum.iotcreators.com
    • docs.iotcreators.com
    • Tags
    • Popular
    • Recent
    • Register

    No device data in GUI

    iotcreators.com portal & API
    gui portal downlink
    4
    10
    340
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • afzal_m
      afzal_m iotcreators.com team last edited by Aleksandra Klinkner

      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.

      afzal_m 1 Reply Last reply Reply Quote 0
      • afzal_m
        afzal_m iotcreators.com team @afzal_m last edited by afzal_m

        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.

        1 Reply Last reply Reply Quote 0
        • A
          allard.potma last edited by

          Any updates? Tried yesterday still no data in the portal.

          1 Reply Last reply Reply Quote 0
          • afzal_m
            afzal_m iotcreators.com team last edited by

            Unfortunately not yet. Still working on a fix.

            1 Reply Last reply Reply Quote 0
            • afzal_m
              afzal_m iotcreators.com team last edited by

              It took some time… But it’s finally fixed!

              Pls be aware that it can take up to 5 minutes before you see your last payload in the GUI. It is just a workaround, we are still working on the final solution.

              1 Reply Last reply Reply Quote 1
              • M
                Michal Szwajdo last edited by

                Hi. Today I have registered two devices with two different SIMs to my first project, but I can not see any data from them (UDP payloads) on the project GUI. I have followed your quite detailed tutorial and I’m sure that devices sends data thought the network. Is the problem mentioned above already solved or not?

                Uta 1 Reply Last reply Reply Quote 0
                • Uta
                  Uta iotcreators.com team @Michal Szwajdo last edited by

                  @Michal-Szwajdo our UDP adapter seems to have received your messages but we need to look closer on that. We’ll come back to you on Monday!

                  1 Reply Last reply Reply Quote 2
                  • afzal_m
                    afzal_m iotcreators.com team last edited by

                    Can you please try again?

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      Michal Szwajdo @afzal_m last edited by

                      @afzal_m Done on both SIMs/devices. No payload on GUI yet…

                      1 Reply Last reply Reply Quote 0
                      • afzal_m
                        afzal_m iotcreators.com team last edited by

                        Thanks. We’re checking again. Get back to you soon…

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post