Global Moderators

@Lauwie007 Can you please send your IMEIs to support@iotcreators.com? I like to analyse the problem in more depth and fix it.
Many many thanks for your support!
Regards, Roland

@herr-bruns , we can’t provide you with a concrete activation timeline yet unfortunately, but we will inform you as soon as possible, tentatively in the coming month.

Dear Mr. Bruns,
The eDRX feature unfortunately isn’t yet available in our German network but its nationwide deployment is in preparation. I will gladly inform you via this post as soon as it is done.
If it can help (for test purpose), eDRX has already been enabled in Austria in our Magenta Telekom network and is being rolled out as we speak in our T-Mobile Netherlands network.
Kind regards,
Ronan Lacroix

@Hans-Liefting: Can you please send me the IMEI of your device to support@iotcreators.com? I will check the logs to understand when uplink and downlink messages are received and when downlink messages are sent by the udp server.

Regards, Roland

@Hans-Liefting Hi,
I am not sure if I understood your process correctly …

Process ?

1. Device wakes up and connects to the network
2. Device send uplink message
3. Application receives the message and response with a downlink acknowledgment
4. Device waits for 10 seconds
5. Device closes the connection and shuts down.
6. After one hour process is repeated at 1.

Problem ?
Downlink message isn’t received by the device reliable.

If you send a non-eDRX downlink message our UDP broker queues the messages until it receives the next uplink message from the device. This means your application acknowledgement message requires an additional uplink messages to let UDP broker deliver the queued downlink message to your device.

In case you send an eDRX downlink message you can try to extend the 10 secs wait to e.g. 30 secs and see what happens. As you know eDRX messages are not queued by the UDP broker. eDRX messages are immediately pushed to your device by the UDP broker. In case you device sleeps the downlink messages are queued by the mobile network. If you are using eDRX downlinks it could be possible that 10 secs not enough for the network to deliver the message and 1 hour of buffering is to long. Maybe this is reason why it works if you wakeup every 5 minutes.

Regards, Roland

@magnatron Did you already send me your account, the project and the imei of the device. I like to check the logs. You can send it to roland.baldin@telekom.de.

Regards, Roland

@magnatron In case you still not able to send downlink messages to your device please provide your account, project and the device imei to our support@iotcreators.com . I will take a look on it.

Regards, Roland

Last comment …

This is valid only for non eDRX downlink messages. eDRX messages are sent directly into the network and will be buffered by the mobile network until the device is available.

Unfortunately I don’t know how long the downlink message is buffered by the mobile Telekom network

Regards, Roland

In case of UDP our middleware manages for each device an out-queue for downlink messages.
The max. size of the queue is 10 messages.
After an uplink messages has been received all queued downlink messages are delivered to the device 1 messages / sec.
If the devices never sends an uplink messages the downlink message stays in the out-queue for ever.
If the device is deleted the out-queue for downlink messages is deleted as well.

Hope this info helps.

Regards, Roland

Hi @magnatron, can you tell us if this solved your issue?

Best
Yassine