Posts made by Cees Meijer

@afzal_m I have just checked our logs over the last two weeks. They are full of registration messages, and the last one is on February 20.

Unfortunately the problem seems to have re-appeared again. From January 29 I again see regular registratiin messages, again with old time-tags…

@afzal_m I have just checked all my logs from January 1, and have not found a single ‘registration message’. Seems like the problem is solved. Thanks.

@afzal_m Yes, it looks like it is old data in the packet.

@afzal_m Okay. I just sent you some sample records.

Not so much a question as an observation : After registering the second application, no messages arrive. Unlike the first endpoint, which just automatically gets all data from your project, you will have to ‘subscribe’ to the resources of a specific device before the data of that device is sent to the second endpoint.

Most of the time time the messages I receive are in the standard ‘reports’ format as described in the docs. Occasionally however I get messages in the more extended ‘registrations’ format. (I already mentioned that here: https://forum.iotcreators.com/topic/524/different-json-messages-from-the-t-mobile-server?_=1608714233162)
These messages are supposed to be sent only for the first time a station sends data, or after it has been offline for a longer time. Even though all my stations send data every 15 minutes, I get these messages quite often. Now I noticed that the timetag in these messages is always off. I log all incoming messages, and all standard reports have a timetag that is right on , or very close to the time the message is received. The ‘registration’ messages however are always 30 to 40 minutes off.
Also it seems that since a few weeks the data that is contained within these messages seems just old data (sometimes even 2 to 3 weeks old), something that I had not experience before. Anyone knows what is going on here ?

Two questions:

• This method can only be used to set the second URL, there is no way to change the first URL through the API ?
• Can I check if the second URL was already set, and what it’s value is, through the API ?

@Roalnd-Baldin Oops. That may not have been too smart. Thanks for paying attention and removing it. Next time I’ll be a little more careful and address support directly.

I have a device which will not register. Not through the wesite, and not through the API. When using the API I get the response ‘Device already exists’. But when i use the API to get a list of all devices, this specific one is not present.
Now this unit has been transmitting without being registered, and on the forum I found a note saying that if you do that the device gets a automatic registration with the general T- Mobile account and therefore cannot be added to a specific project. But it also mentioned that these registrations are erased every morning around 08:00, so it should be possible to register the next day. But I’ve tried, and that does not work either.
So what next …?

@afzal_m So I’ll have to hold on the community package that I already have. But is there a chance that it will disappear completely in the future ? And would there be any benefit for me to go to one of the ‘paid’ packages ?

@afzal_m We will be deploying our water flow sensing stations at multiple locations. Sometimes they will be moved, so it would be nice to know where they are. Accuracy should be within some 10th of meters, and a daily update would be sufficient.

@eric-barten That would be nice. But what channel to use for this PM then ?

Thanks for the explanation. I see this can be useful. The only thing that worries me now is that I get these messages a few times per day from stations that are sending data every 15 minutes. So I wonder what could cause this then.

Since the network outage of last week I have been logging the raw messages as they are coming in. Most of the time time these messages are in the standard ‘reports’ format as described in the docs. But every once in a while I now also get a much more extended message that contains sections like ‘registrations’ and “location/0/longitude”. And the actual data is also in there, but now as “uplinkMsg/0/data” in the section “deviceprops”. Does anyone has a clue what these messages are, and where they come from ?

Example of long message:

{ "reports": [], "registrations": [ { "deviceType": "device", "serialNumber": "IMEI:354347096127078", "timestamp": 1584082892010, "make": "Generic", "model": "Sensor", "groupName": "TMNL.PROFESSIONAL.CON_0000001419", "imsi": "N/A", "protocol": "N/A", "tags": "N/A", "subscriptionId": "98d1f525-0f34-45cc-80a1-f7617206f064", "deviceProps": { "device/0/imsi": "IMSI:901405700003916", "device/0/model": "Sensor", "uplinkMsg/0/data": "c19906000049c5650400fafd25750008000300000050000000c8000a16052e009f9e02008e8cffff827fe9ff7573ebff6a68c800f8fed9feccfee4fe2fffc800f8feebfedafefffe27ffc80016fffafe08fff9fe20ffc8001afff0fef7fefffe3dffc800", "device/0/manufacturer": "Generic", "connectivity/0/port": "49153", "connectivity/0/mncmcc": "", "location/0/longitude": "", "device/0/endPointClientName": "IMEI:354347096127078", "connectivity/0/cellid": "", "connectivity/0/ip": "10.128.0.100", "location/0/radius": "", "connectivity/0/rat": "", "location/0/latitude": "", "connectivity/0/apn": "" } } ], "deregistrations": [], "updates": [], "expirations": [], "responses": [] }

In an announcement of last year I noticed it was mentioned that the network would support ‘Data packet buffering’ for a maximum of 10 messages. Is that actually available, and if so, how do I get these buffered messages ?
If possible I would propose that T-Mobile actually creates a full day buffer for the messages. This would be very convenient in case of a network outage like the one that happened last week.

Meestal betekend dit dat je nog niet (correct) bent ingelogd. Ik heb dit ook al eens gehad. Ik heb toen in de ‘Account’ pagina alles weg gehaald, en opnieuw de gebruikersnaam en password ingevuld om in te loggen.

Wasted a few hours on trying to debug this issue, before I thought of looking at the forum. I suppose it would be really helpful to have some kind of status page where you can check the network.