Incomplete / Duplicate Webhooks

[Muzza64]

We have V4 up and running on AWS. We have occasional instances where webhooks are being sent twice. The first webhook is an ‘incomplete’ message and the second one is complete. This is from a single device uplink which looks the same as other uplinks which don’t have this issue. There is only one Gateway in the area.

It looks like wheat the “Device Status Request” fields from the old V3 Service Profile would result in… there doesn’t seem to be a way to address this in V4.

I’m hoping this is something simple. Any ideas?

First Webhook:
{“deduplicationId”:“c9337ef4-d0ff-44c4-9943-3927b2aa1f80”,“time”:“2022-12-29T02:25:00.761852+00:00”,“deviceInfo”:{“tenantId”:“52f14cd4-c6f1-4fbd-8f87-4025e1d49242”,“tenantName”:“RT”,“applicationId”:“e811843b-1ddb-43ef-a324-3901ad9d4fb3”,“applicationName”:“Push”,“deviceProfileId”:“8f955b94-600c-4813-95e0-9e58bb686453”,“deviceProfileName”:“Dragino OTAA Device”,“deviceName”:“TIT0002”,“devEui”:“a8404143518227ba”,“tags”:{}},“margin”:23,“externalPowerSource”:false,“batteryLevelUnavailable”:false,“batteryLevel”:100.0}

Second Webhook:
{“deduplicationId”:“c9337ef4-d0ff-44c4-9943-3927b2aa1f80”,“time”:“2022-12-29T02:25:00.761852+00:00”,“deviceInfo”:{“tenantId”:“52f14cd4-c6f1-4fbd-8f87-4025e1d49242”,“tenantName”:“RT”,“applicationId”:“e811843b-1ddb-43ef-a324-3901ad9d4fb3”,“applicationName”:“Push”,“deviceProfileId”:“8f955b94-600c-4813-95e0-9e58bb686453”,“deviceProfileName”:“Dragino OTAA Device”,“deviceName”:“TIT0002”,“devEui”:“a8404143518227ba”,“tags”:{}},“devAddr”:“01ca402e”,“adr”:true,“dr”:5,“fCnt”:805,“fPort”:2,“confirmed”:false,“data”:“y9oLOAI9AX//f/8=”,“rxInfo”:[{“gatewayId”:“a840411ef3bc4150”,“uplinkId”:21095,“time”:“2022-12-29T02:25:00.761852+00:00”,“rssi”:-103,“snr”:7.0,“channel”:2,“location”:{“latitude”:-27.18939,“longitude”:152.79335,“altitude”:60.0},“context”:“z/kZCw==”,“metadata”:{“region_name”:“au915_5”,“region_common_name”:“AU915”}}],“txInfo”:{“frequency”:923600000,“modulation”:{“lora”:{“bandwidth”:125000,“spreadingFactor”:7,“codeRate”:“CR_4_5”}}}}

Thanks,
Mark

[brocaar]

Have you inspected the event in the URL query? It looks like the first request is posted with ?event=status and the second with ?event=up.

[Muzza64]

This is now sorted - it’s a daily device status request from Chirpstack (I found the selection for that in the Device Profile > General tab.

The margin is handy so I’ve kept left the device status request in place, and have sorted the decoder to differentiate between the webhooks.

Once again, operator error.

Cheers, and thanks Brocaar - the more I get my head around Chirpstack the more I like it.