[chaoslans]

Seems it’s a bug of the parameter setting, I recover the addr range to 00000001-1fffffff, all nodes can join and send data normally.

[chaoslans]

Hi Jason,

Yes I modified the address range, but I’m sure it’s a big range, from 20000001 to 2FFFFFFF.

And today a new issue raised. In 1.4.17, the nodes have joined, but soon it shows the following error, what’s “not found in memory list”?

Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|FRAME-RX|TYPE: Join Request
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|JOINREQ-RX|00ae01010000ac5900ff67180000ac5900b6cd
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|DEV-EUI|00-59-ac-00-00-18-67-ff
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|JOIN-EUI|00-59-ac-00-00-01-01-ae
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|DEV-NONCE|cdb6
Feb 21 10:42:19 mtcdt user.info lora-network-server: ED:00-59-ac-00-00-18-67-ff|WL-SEARCH|Device found in whitelist
Feb 21 10:42:19 mtcdt user.debug lora-network-server: ED:00-59-ac-00-00-18-67-ff|CHECK-KEY|MIC Valid
Feb 21 10:42:19 mtcdt user.debug lora-network-server: ED:00-59-ac-00-00-18-67-ff|APP-NONCE|c7bcd1
Feb 21 10:42:19 mtcdt user.info lora-network-server: ED:00-59-ac-00-00-18-67-ff|DEV-ADDR|Found End Device in DB 670b756a
Feb 21 10:42:19 mtcdt user.err lora-network-server: ED:00-59-ac-00-00-18-67-ff|JOINREQ|Device not found in memory list
Feb 21 10:42:19 mtcdt user.err lora-network-server: SQL error: [no such column: class] on first call
Feb 21 10:42:19 mtcdt user.err lora-network-server: Failed to load device from database

[Author]

Posts