Moved your post to the thread that was at the top of the list so we don’t have two of the same.
The forum is entirely run by volunteers so we ask people to use the forum search to see if something has been answered already - or multiple times.
In this case, something, somehow, has got in to the database that the web front end can’t cope with. The simplest solution, given there is no SLA or support for the free service, is to use the CLI tool to delete the devices and re-enter them from either the CLI (preferable) or via the web console which works 99% of the time for me, but just occasionally I manage to confuse the browser enough that I break it all. That said, the CLI is more of an atomic commit to the database, so if I’m doing a fair number of devices I use that.
Sometimes editing a setting can cause this issue.
If I get any form of detail (both EUIs) that can help the TTI developers trace such situations I do pass it on.
I have been using the CLI with command ttn-lw-cli end-devices create to make new devices with the TTN V3 stack, and it is generally working well. However, the devices I create show in the “End devices” list in the Console, but when I try to click on the devices created through the CLI, I get the error An unknown error occurred. Please try again later. If the error persists, please contact support.
Have anyone else encountered this? Are there some properties on the device I need to set for it to display properly in the console? I have tried with the --lorawan-version flag, and had problems with the --frequency-plan-id if with for US_902_928_FSB_2.
Excellent, it works now! Seems that --frequency-plan-id and --lorawan-phy-version both must be specified at the same time for the command to complete if any of them are used. For others with the same issue, this command worked for me in the end: