Hi,

Normally network uplinks include downlink_key, application_id and device_id in every uplink msg. To limit the amount of inputs we filter these out (99.9% of the time these aren't used anyway). As pointed out here though, those variables are needed in case Tago needs to send a downlink...

So, since we want to send an 'unscheduled' downlink to a class-C device, we figured we can use the emulator to set up these variables once, exactly as they are received from the network before sending a downlink.

This seems to work. However... at some point during or after the downlink all 3 of those variables are removed from the device's bucket! As a result the next downlink fails.

Is this the expected behavior?

If so, how would be get past this? I can envision configuring the device_id and application_id as tag or Configuration Parameter and sticking them in the bucket vars. ahead of a downlink, but for the downlink_key that is going to be tricky because it has metadata with the target URL.

Any suggestions will be greatly appreciated.

Erwin