No idea what happened,but somehow my Dragino LPS8 has stopped connecting to TTN after more than 2 years of good work. I have been struggling for a few days now to get it back online. I have deleted the configuration of the first gateway and reinstalled everything. Especially the cups authorization part was new compared to 2023.
The gateway helps me to develop Lorawan-TTN applications and ofcourse supports the network.
Now the console has adviced me to get support, if you click that you come to this place in the forum. So here I am. I have replaced most of the IDs with “x”-es. I know this is sensitive.
Hopefully this triggers some help? I read that I have no rights for a gateway? Please tell me this is not true!
Please help.
Thanks in advance.
{
“code”: 7,
“message”: “error:pkg/auth/rights:no_gateway_rights (no rights for gateway eui-a840xxxxxxxx)”,
“details”: [
{
“@type”: “type.googleapis.com/ttn.lorawan.v3.ErrorDetails”,
“namespace”: “pkg/auth/rights”,
“name”: “no_gateway_rights”,
“message_format”: “no rights for gateway {uid}”,
“attributes”: {
“uid”: “eui-a84041xxxxxxxx”
},
“correlation_id”: “69934010ce70xxxxxxxx”,
“code”: 7
}
]
}
It’s public information and the only way we can check the online database to see the LNS side is by knowing what the registered gateway id is …
The correlation_id’s help developers trace the path of messages through the stack, which aren’t kept, so are of no use.
If you can tell us what the gateway EUI is as well, that will enable us to determine if you don’t have rights on your old deleted gateway. Also, never delete a gateway, now you know why.
Thank you for your fast reply and your answer, very clear. The device more and more started to behave weird and finally stopped functioning. Will need to invest to continue my journey in Lorawan and TTN. I will surely do this enjoying this technology! No further action needed.
Installed a brand new gateway LPS8-V2, all went well, all is green,
if I check the log I can see traffic from my lora devices,
in the log I cannot detect any errors.
If I check from within my network,I can reach: eu1.cloud.thethings.network both port 443 and port 8887.
from the LPS log : Internet Access: reachable via Dev:eth0, draginofwd is running and iot is online.
But if I check the TTN console I still first get the error: no_gateway_rights and get support. If I then click on gateway tab it says the status is : Disconnected.
My new gateway is : a84041fdfe27eab8
Normally I start to looking for errors in my own settings.But could it be possible that the error in the console (caused by me deleting the defect gateway, apologies for that). Is hampering the correct representation and overview of the new gateway?
That may be a legacy link stored in your browser - they try to remember to be helpful except for the times you really do need to find an old link!
The acid test is always to have a device nearby to show entries in the console log - which should at least show the keep-alive handshake messages. The status is not updated in real-time so isn’t useful for immediate debugging.
No, not if you’ve got a whole new gateway - can you confirm that you have a new gateway id and what it might be as the EUI isn’t showing in the online API at present.
contrary to what is stated in the notes for TTN instruction from Dragino (I use the LPS8-V2 now). Do not enter the LNS key authentication key, than it will not work.
My understanding was that CUPS would have a higher priority and overrule these LNS settings. But you have to keep this absolutely blank and then save.
And then it works again…
Thanks Nick for your patience and fast responses. If ever possible I’l buy you a drink.