Closed MedadRufus closed 2 years ago
Issue remains after landing
looks like the icspace26_helium_10 credentials have become invalid. No idea why. All others are OK.
easy way out would be not to use it.
Should I rejoin the network to extract icspace10 credentials?
When I try to do an OTAA join, I see this on the console log of Helium. Quite a few came through:
{
"id": "d3577099-9a77-493f-bce4-f4fe2128550f",
"router_uuid": "4803d98f-9635-4530-ba0e-be1f9122b955",
"category": "uplink_dropped",
"sub_category": "uplink_dropped_device_inactive",
"description": "Device inactive packet dropped",
"reported_at": "1637960697354"
}
With a bit more information:
{
"id": "6a7bccf0-3b49-4cb2-a528-1f84ffd5df8d",
"router_uuid": "78f49169-66fc-4745-9624-6f98a8fe4d3c",
"category": "uplink_dropped",
"sub_category": "uplink_dropped_device_inactive",
"description": "Device inactive packet dropped",
"reported_at": "1637961055107"
}
Device Information
{
"name": "icspace26_helium_10"
}
Hotspot
{
"id": "112JmkqUNZTqrqxxcoL5jkAVQNRWo1eQqSvSHNFANBAPpoasibSG",
"name": "old-wintergreen-flamingo"
}
New keys for helium10:
FNwkSIntKey_SNwkSIntKey_NwkSEncKey:30 14 25 E1 D5 67 BB 5D 4C 14 E2 7D C8 8C 88 93
AppSKey:12 61 DF 54 19 D6 71 F9 5F 8C C5 BE 9B 5A 80 D9
DevAddr:5B 03 00 48
Appears to have reappeared again. helium4 is no longer updating. Possibly helium9 as well.
Perhaps, because it was done with teh lorawan simulator, it is some how forgetting these session keys? Should I do it all manual on the tracker on target?
Its not yet been observed again. Although it could happen again. But now to reduce risk, there are 20 devices registered, up from 10.