DevNonce changes in 1.0.4 about dragino

[pjb304]

It could be - I'm running my nodes in 1.0.2 MAC and PHY so it's still valid - however, if you're running on a more up to date version, then it might cause issues.

[BNNorman]

I take the view that [0,1] , [0,2]...[255,255] are all valid random devnonce values. I don't know if 1.0.2 MAC checks them other than I know TTN rejects join requests with repeated values when sent .

I have temporarily added a 'getDevNonce()' method which sets self.devnonce , increments the last value and stores it in a file imaginatively called , ahem, devnonce. This is called in the join() method. But I still haven't succeeded in joining on V3 so I'm about to see if I can create a single channel gateway for testing. Some joins have been accepted but I haven't received the downlink - could be RSSI with the gateway being 11km away.

My use case is investigating adding LoRa capability to roadside speed signs for my local council. Currently they send a bloke with a PDA to download the logs via bluetooth. Its quite complicated to stay within Fair Use policy and 1% airtime regulations. The signs would be in urban areas and likely have trouble with joining hence my test program tries all join freqs and SFs. No success yet.