Sending a downlink to an end device suddenly fails. Calling
curl --location \ --header 'Authorization: Bearer NNSXS.XXXXXXXXX' \ --header 'Content-Type: application/json' \ --header 'User-Agent: my-integration/my-integration-version' \ --request POST \ --data '{"downlinks":[{"frm_payload":"8QEDHjw=","f_port":1,"priority":"NORMAL"}]}' \ https://eu1.cloud.thethings.network/api/v3/as/applications/myapp/webhooks/myhook/devices/eui-XXX/down/push'
results in
{ "code": 5, "message": "error:pkg/redis:not_found (entity not found)", "details": [ { "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails", "namespace": "pkg/redis", "name": "not_found", "message_format": "entity not found", "correlation_id": "db444ea993834e0586ede446844531bb", "code": 5 } ] }
The call was working last week. Now it seems to fail for any device.
1 Like
descartes
(Nick McCloud)
November 7, 2022, 11:10am
2
Maybe due to doing it whilst Redis is being updated:
Completed: Upgrade to The Things Network v3.22.2
This is a cross-post of an incident on our The Things Network status page .
It will be updated automatically.
Scheduled: Mon, 07 Nov 2022 12:00:00 +0100 until 14:30:00 +0100
Resolved: Mon, 07 Nov 2022 14:30:38 +0100
Affected Components
Europe 1 (eu1.cloud.thethings.network): Operational
North America 1 (nam1.cloud.thethings.network): Operational
Australia 1 (au1.cloud.thethings.network): Operational
Scheduled
Posted: Fri, 04 Nov 2022 17…
Missed that. Good hint. Will try afterwards.
While I find the error message error:pkg/redis:not_found (entity not found) highly misleading it had some truth to it: the webhook name had changed in our configuration. So not_found referred to the old hook name which was indeed deleted.
Case closed.