Early Access participants

For NB-IoT we have an UDP adapter. So with NB-IoT you’ll need to use APN cdp.iot.t-mobile.nl which will allow you to send device data to 172.27.131.100.

To retrieve the device data in your back-end/cloud server/iot platform, you’ll need to create an HTTP integration.

If you use the sim-card for LTE-M or 2G, you’ll need another APN: m2m.public.nl. By doing this, the device will get a public IP address just like any other device on the open internet. This means that you can send device data directly to your own server while using LTE-M or 2G.

Hope this helps!

You can only send traffic to our server and we can help you with the HTTP integration to your environment.

2G and LTE-M are accessible. Pls use APN m2m.public.nl and you’ll get a public IP address. By doing this, you can send data to any destination.

You can only add users which are already known in our member-db. Apologies for that.

So after Jaap has created his account at https://porta.iotcreators.com, Pieter should be able to add Jaap as project-member

{statusCode: 500, error: “Internal Server Error”, message: “An internal server error occurred”}
error: “Internal Server Error”
message: “An internal server error occurred”
statusCode: 500

I was trying to add project members to a project ( Pilot); because I am logging in using an account from somebody else.
Please advise, thank you.

Jaap Crezee
(jaap@jcz.nl ; Iot Solutions Partner BV)

This is due to agentlifecycle queue being processed too slow, so the lifecycle event (registration) is sent with a delay.

We already prepared a fix for this. Next week we are going to test the fix on our staging environment!

Thanks, just saw it!
Just to be sure: so it’s not only about this gap of 30 or 40 minutes, right? Sometimes these payloads are from 2/3 weeks ago. Is my understanding correct?

@Cees-Meijer

could you please send me an example of such a message and the timestamp that you received this message?

You can send it via PM of via email

Changing the url is not possible afaik. You can only overwrite the URL.

You can set-up the first URL and overwrite the first URL by using the GUI and you can set-up the second URL and overwrite the second URL via the APO.

I’m not sure if you check the value what has been set via the API before.

I’ll ask @Roalnd-Baldin tomorrow

Activated yesterday and finetuning at the moment.

Will update you next week again!

Hi All,

We would like:

• Accuracy of 3 to 5 meters latitude / longitude
• Correct altitude measurement(up to 1 meter, for certain use cases even more important than lat and longitude). This is for height measurements in building so that floor levels can be determined accurately
• We would like secured connections to the service, preferably a VPN
• A process that clients can be checked if they are to be trusted(we don’t want to deliver this sensitiedata to bad people with sinister plans)
• Adjustable frequency of positioning, higher frequency means paying more. High frequency is refresh every second(for emergencies for instance)
• Possibility to cross reference/compare the data with GPS data out of the field
• A way to determine which radio’s on which cell towers are used, this will be important if the target is moving.
• A service which checks the availability of the positioning service and availability of data

Questions

• Is the data available on all networks(2G, 3G, 4G - NB-IoT/LTE-M enabled devices). My / Our assumption is that it is, as long as three cell towers/radio’s can be connected to.
• Are changes necessary in the firmware of cellular modules to use the service?
• Is the data available as a service, so do we receive aggregated data. Or do we receive lang, long and altitude plus data where the data is retrieved from(cell towers and radio’s plus the signal strength data which comes with it?
• Is the service strictly available on the network of T-Mobile? Or is the data still available when roaming takes place to other networks?
• How reliable is the service, especially on moving targets, when roaming is necessary?
• How accurate is the service? Or how accurate can you get?
• To which height is the service still available(we have gone up to 2,5 kilometers on NB-IoT). Ewout Karel has done about 300 - 500 meters on a relatively fast moving target