Greetings,
2 devices (temperature sensors) have stopped transmitting Up events for 7 days. I went to check and noticed that they are continuously “Join Request”. The key hasn’t changed, I tried to delete the device and I tried to reconfigure the device but it still stays like this, any advice?
Log screen
2024-02-09T06:41:02.279284Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}: chirpstack::storage::device_keys: Device-nonce validated, join-nonce incremented and stored dev_eui=70b3d58ff10261f4 dev_nonce=50290
2024-02-09T06:41:02.279815Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}: chirpstack::storage::device_session: Device-session saved dev_eui=70b3d58ff10261f4 dev_addr=008bbf60
2024-02-09T06:41:02.280270Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}: chirpstack::storage::device_queue: Device queue flushed dev_eui=70b3d58ff10261f4 count=0
2024-02-09T06:41:02.281760Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}: chirpstack::storage::device: Enabled class updated dev_eui=70b3d58ff10261f4 enabled_class=A
2024-02-09T06:41:02.283786Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}: chirpstack::storage::device: Updated DevAddr dev_eui=70b3d58ff10261f4 dev_addr=008bbf60
2024-02-09T06:41:02.285175Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}: chirpstack::storage::device: Updated JoinEUI dev_eui=70b3d58ff10261f4 join_eui=0000000000000000
2024-02-09T06:41:02.285408Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}:join_accept{downlink_id=730181463}: chirpstack::storage::downlink_frame: Downlink-frame saved downlink_id=730181463
2024-02-09T06:41:02.285482Z INFO up{deduplication_id=27b3f2fb-0433-46c6-822e-be7ce1615e19}:join_request{dev_eui=“70b3d58ff10261f4”}:join_accept{downlink_id=730181463}: chirpstack::gateway::backend::mqtt: Sending downlink frame region_id=eu868 gateway_id=7276ff002e0613ac topic=eu868/gateway/7276ff002e0613ac/command/down json=true
2024-02-09T06:41:02.286223Z INFO chirpstack::integration::mqtt: Publishing event topic=application/00000000-0000-0000-0000-000000000006/device/70b3d58ff10261f4/event/join
2024-02-09T06:41:02.286368Z INFO chirpstack::integration::amqp: Publishing event routing_key=application.00000000-0000-0000-0000-000000000006.device.70b3d58ff10261f4.event.join
Have you tried to reboot the device/node?
Yes, I tried also to change mode no OTAA and enable OTAA.
I think is problem of chirpstack because on log I saw accept but on GUI I saw only JoinAccept?
I have same problem with adenuis tester. In ABP mode works fine in OTAA continuily JoinRequest
@brocaar could you help me? I’m in production
Hi @fpalladino,
I’ve had this happen to me in the past and found it was a Firewall issue. Has anything changed on the network where the gateway is located?
Thanks, I think so. I’m checking the network configuration seems the downlink package don’t arrive.
1 Like
Is there anything other than 1700/UDP and 3001/BOTH important for this to work? That’s all there is to the networking bit for the LoRa comms, no?
I’ve encountered a similar problem where a node stopped transmitting, resulting in repetitive Join Requests.
I was able to resolve the issue by “Flushing OTAA device nonces” and then resubmitting the Application key. However, this took several attempts before succeeding.
The problem was firewall in my case