As always, let me start by saying that you should not use ABP unless you have a very good reason; OTAA is always preferred. If you do use ABP, you should not just randomly pick a DevAddr; instead you should request one from the Network Server, and use that.
Yes, I see that message everywhere in the V3 messages. But I have also seen “ABP is supported”.
And Yes, I had the NAM1 server generate the V3 DevAddr I mentioned earlier. I did not randomly make it up myself. In fact, I have had the NAM1 server make 3 different DevAddr values and all 3 have produced the same results.
The “router ttn-router-us-west drop … reason:no brokers” indeed doesn’t mean that traffic isn’t forwarded to Packet Broker. I’ll see if we can do something to somehow make this a bit more clear.
OK … I only emphasized the “no brokers” message because it seemed like the error. Ultimately, the real problem is no data from my V3 device ever shows up in the V3 application’s live data console.
All
ttn-router-*and*.cloud.thethings.networkare connected to Packet Broker. If any cluster receives traffic for DevAddr block260C0000/16(see also the list of blocks in this forum comment) , that traffic should end up innam1.cloud.thethings.network.
Again, this does does not appear to be happening. I don’t know how to diagnosis it any further, hence my request for help.