I have two different gateways, one in the laboratory and another in the field. First I test the new devices in the lab and then I sent it to the field. We tried the migration from v2 to v3 with a single device by registering it in the v3 and changing the appKey in the v2 and it went correctly, so I sent the device to the field and it continues sending data correctly. This was made like two weeks ago.
The problem is when I try to register a new device a few days back, as now we can’t do it in the v2, I did it in the v3. The procedure was exactly as I did with the registration of the migrated device, and the console didn’t show anything, even the message that informs of a device trying to connect. I double checked the credentials and the settings and everything was correct. I registered another device to identify if the problem was the device, and the second device neither connects. I changed the credentials in the v2 console of the migrated device (that still works in v3) to be the credentials of the device I tried to register in the v3. It connected at the first attempt. As it works in v2, we made the corresponding issue to migrate from v2 to v3 and it didn’t work.
The migrated device and the ones we attempted to register were RAK4260. Finally we tried with an Arduino MKRWAN1300 and it neither connects to v3 but it does to v2 correctly. As the devices in the field reboot once a week, I migrated a device that was in the field and when it rebooted it connected correctly to the v3 console. When I try to connect the devices to v3, we see in the gateway transfer that the join requests are sent correctly.
With this information, maybe the problem is in the gateway, but with this gateway i did the migration of the first device correctly, so i don’t think so. This gateway is the “The Things Gateway”, so it should work correctly in the v3 as it did it with the first migrated device.
Thanks in advance for the people that will try to help me and the ones that have read it all.