Posts made by Bart Abel

@afzal_m Thanks. It works again!

@Eric-Barten We also have a device that did not come back. IMEI 357518080554132, last message at 11 mrt. 2020 04:26.

@Eric-Barten Seems to be resolved by removing and adding subscriptions again.

@Eric-Barten We are receiving all messages twice now.

@eric-barten Can you answer this? We can of course try by trial and error, but it would be nice to have a technical reference.

Hi,

The documentation primarily shows examples on how to set up subscriptions with serialNumber based criteria, but according to the reference other criteria are also possible. Do you have examples of other criteria?

• Wilcard criteria? Is this possible? E.g. serialnumber wildcard.
• No criteria at all? Is this possible? Such that a subscription holds for all devices?
• Model or firmware criteria.

The main reason for asking is to be able to avoid the step to update the subscription each time a new device is registered.

Kind regards,
Bart

@eric-barten Ok, clear, thanks!

@eric-barten One more thing. You wrote “Per user you can manage the serialnumbers of the subscriptions as described here.”, how do I select which user I am editing subscriptions for? I only have one API username to perform API calls with. Or is it such that the web GUI user does not have editable subscriptions and is automatically subscribed to all devices?

PS. Please look at my previous followup as well, on how to add additional projects.

@Eric-Barten @Bob-Mooij On behalf of Ronald, thanks for your answers. This also makes the purpose of multiple applications as described in the documentation clearer. It would be nice if “missing” information like this could be added to the portal as hints (that the application registered through the GUI is linked to user no. 1 and the application registered through the API is linked to user no. 2).

For our needs we will set up multiple projects, how should this be done? Currently I have one project visible and I can only choose to end it.

@bob-mooij Bedankt voor de informatie. Als er base64 encoding wordt gebruikt, wordt dit dan decoded afgeleverd bij het device? Zie ook mijn andere post over de uplink route: https://forum.iot.t-mobile.nl/topic/364/uplink-data-encoding Zou je daar ook antwoord op kunnen geven in de andere post?

How will binary data be encoded when it is delivered to our application by CDP? The data delivery messages seem to be structured as JSON, which will be malformed when it contains pure binary data. So is any encoding applied? (Base64?). I am not able to find much about the actual payload delivery in the documentation.

Ik probeerde net via de documentatie te achterhalen hoe downlink berichten verstuurd moeten worden, daar is helaas nog steeds vrijwel niets over te vinden. De beste beschrijving is nu in het postman screenshot van “VII. Hello device”. Bij deze dus een bump van dit oude bericht, wat meer in depth documentatie zou welkom zijn.

Hoe moet de body er bijvoorbeeld precies uit zien, is er alleen een resourceValue attirbuut of zijn er meer mogelijkheden?
En kan er alleen ASCII data verstuurd worden?