The new TTN release asks for a JoinEUI during an ABP device registration. It seems a mistake that hopefully will be corrected soon. If it’s not, can someone explain me why we shall need this?
(ttnv3 22.1 , manual registration of 1.0.1 ABP device).
Hey everyone, thanks for reporting. This was indeed a quirk that adventurously made it into the release. I worked on a fix today and yesterday that will resolve this. Obviously, for ABP devices, a JoinEUI and AppKey are not required and the whole JoinEUI check can be skipped.
Indeed, OTAA should be preferred whenever possible but it’s not illegal to use ABP and the device onboarding is also meant to allow doing this in a logical way.
Obviously, we do test before implementation (and the generally smooth roll-out of the new onboarding proves that) but it is nearly impossible to foresee every possible consequence of onboarding changes
for every activation type
for every device class
for every LoRaWAN version
for every Regional Parameters version
for every band and FPs
for every MAC setting
and any of their exponential number of combinations. We’re sometimes forced to iterate based on progressive insight. I get the frustration, but I also hope you can understand that something like setting DevEUI on <1.0.4 ABP devices for use in cayenne/mydevices just happened to be edge-casy enough to slip through and be fixed iteratively.
Hi Kevin, do appreciate that, and am not being sniffy about it! You guys have a tough job maintaining and keeping on top of all this stuff! As you say regression gets harder with every passing day and each new feature and spec change… just suprised to see something as fundamental to device identity as the DEV EUI being called out as a corner case issue. Ensuring correct entry of Dev Eui, along with other identifiers and keys, has been a key item called out on the Forum posts since long before I even started using. Given there are featured/high profile integrations for the platform - of which cayenne is just one, and TBH one of the easiest for many and one that has been around a long time, I would have expected/hoped a check to see if a change breaks one of these key integration capabilities would be part of the regression suite?! Not sure if other integrations use the DEV EUI of the top of my head, (believe e.g. TTNMapper is device id, rather than dev eui, focussed) no doubt others will chime in if the Dev Eui needed for other than custom apps…