Hello,I have been struggling with this issue, the issue being that my mdot device keeps trying to join the multitech conduit but it seems like its failing. I have set up so that the multitech conduit is the gateway and packet forwarder while the raspberry pi 3 has the lora app server and lora server installed which then forwards it to our own server. This is what i get from my lora server logs
Jun 20 15:38:20 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:20Z” level=info msg=“backend/gateway: rx packet received”
Jun 20 15:38:20 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:20Z” level=info msg=“packet(s) collected” dev_eui=008000000000b265 gw_count=1 gw_macs=00800000a0000781 mtype=JoinRequest
Jun 20 15:38:20 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:20Z” level=info msg=“finished unary call with code OK” grpc.code=OK grpc.method=GetDevice grpc.service=ns.NetworkServer grpc.start_time=“2018-06-20T22:38:20Z” grpc.time_ms=2.731 peer.address="[::1]:46434" span.kind=server system=grpc
Jun 20 15:38:21 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:21Z” level=info msg=“device-queue flushed” dev_eui=008000000000b265
Jun 20 15:38:21 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:21Z” level=info msg=“device-session saved” dev_addr=00c6007b dev_eui=008000000000b265
Jun 20 15:38:21 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:21Z” level=info msg=“device-activation created” dev_eui=008000000000b265 id=108
Jun 20 15:38:21 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:21Z” level=info msg=“backend/gateway: publishing tx packet” qos=0 topic=gateway/00800000a0000781/tx
Jun 20 15:38:21 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:21Z” level=info msg=“backend/gateway: rx packet received”
Jun 20 15:38:21 raspberrypi loraserver[21093]: time=“2018-06-20T22:38:21Z” level=error msg=“processing rx packet error: get device-session error: device-session does not exist or invalid fcnt or mic” data_base64=gFJbqwcAiQ0CtGDVOCl+QGip
Now from my lora app server log this is what i get
Jun 20 15:38:20 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:38:20-07:00” level=info msg=“finished client unary call” grpc.code=OK grpc.method=GetDevice grpc.service=ns.NetworkServer grpc.time_ms=5.298 span.kind=client system=grpc
Jun 20 15:38:20 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:38:20-07:00” level=info msg=“device-keys updated” dev_eui=008000000000b265
Jun 20 15:38:20 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:38:20-07:00” level=info msg=“device-activation created” dev_eui=008000000000b265 id=108
Jun 20 15:38:20 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:38:20-07:00” level=info msg=“handler/mqtt: publishing message” qos=0 topic=application/3/node/008000000000b265/join
Jun 20 15:38:20 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:38:20-07:00” level=info msg=“js: sending response” message_type=JoinAns receiver_id=000000 result_code=Success sender_id=f715f37ed16a7369 transaction_id=4061104893
Jun 20 15:40:12 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:40:12-07:00” level=info msg=“js: request received” message_type=JoinReq receiver_id=f715f37ed16a7369 sender_id=000000 transaction_id=3895565855
Jun 20 15:40:12 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:40:12-07:00” level=info msg=“finished client unary call” grpc.code=OK grpc.method=GetDevice grpc.service=ns.NetworkServer grpc.time_ms=5.175 span.kind=client system=grpc
Jun 20 15:40:12 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:40:12-07:00” level=info msg=“device-keys updated” dev_eui=008000000000b265
Jun 20 15:40:12 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:40:12-07:00” level=info msg=“device-activation created” dev_eui=008000000000b265 id=109
Jun 20 15:40:12 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:40:12-07:00” level=info msg=“handler/mqtt: publishing message” qos=0 topic=application/3/node/008000000000b265/join
Jun 20 15:40:12 raspberrypi lora-app-server[16439]: time=“2018-06-20T15:40:12-07:00” level=info msg=“js: sending response” message_type=JoinAns receiver_id=000000 result_code=Success sender_id=f715f37ed16a7369 transaction_id=3895565855
now just to let you guys know that there are several other devices in the building that have been sending out constant request to join the multitech conduit(gateway) which is why on the logs it says device session does not exist. Also i know there are multiple forums that have already answered the invalid fcnt and device session error and I tried those solutions but they did not work. I checked both fcnts from my end device and lora server and they both start fresh as well as new network session when it joins. So now the problem is that the end device cannot get back that join acceptance which is why it is failing and I am not sure how to fix it. Any hellp appreciated