End-Device Registry in au1

TTN Network and Services The Things Stack v3
1

I have a dozen TTN connected gateways in New Zealand receiving mainly power system telemetry from Victron solar controllers. I’ve started working with some other sensors and lost a few hours today on API issues. I was trying to retrieve device friendly names from the End-Device Registry. Finally I found the note End-Device Registry API requests or other Identity Server API requests to any cluster other than eu1 will fail.

Is there a timeframe for enabling this feature on TTN AU1? We do have a local TTI provider (I host one of their gateways for them) but I’m locked into TTN due to the Victron platform.

(edited for clarity)

2

Probably best asking this on the Things Network Slack #support channel

3

It has always been there - you just use the eu1 endpoint because that is where the data is held next to the identity server which only has eu1 as an endpoint as well - these are one-time setups and replicating the IS is problematic as it provides the source of truth.

So, TL;DR: just use eu1.

PS, all the data is published in the GitHub repro if you want to parse it yourself for local access.

4

Thank you so much! It’s not clear in the API documentation that this is the case. I have now simply substituted eu1 in my query, and it’s running successfully.