Passive Roaming Activation hangs after "success"

Viewed 10

Hi,
has somebody expierence with "Passive Roaming Activation"?
After receiving "HomeNSAns","Result":{"ResultCode":"Success"} the fNS do nothing else. Complying to Aliance Spec. TS2-1.1.0 it should start with PRStartReq {Join-request}!

**fNS:**
2025-12-11T08:39:58.459783Z TRACE chirpstack::downlink::scheduler: Starting class_b_c_scheduler_loop run
2025-12-11T08:39:58.459853Z TRACE chirpstack::downlink::scheduler: Getting devices that have schedulable queue-items
2025-12-11T08:39:58.467311Z TRACE chirpstack::downlink::scheduler: Got this number of devices with schedulable queue-items device_count=0
2025-12-11T08:39:58.467377Z TRACE chirpstack::downlink::scheduler: class_b_c_scheduler_loop completed successfully
2025-12-11T08:39:58.635453Z TRACE chirpstack::uplink: Collecting received uplink events key="up:collect:{eu868_8:08a0cff89d03120a1a0808c8d007100c2801:0000000000000000002810006025641f8c33891ba7620d}"
2025-12-11T08:39:58.636737Z  INFO up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}: chirpstack::uplink: Uplink received f_type=JoinRequest
2025-12-11T08:39:58.636778Z DEBUG up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}: chirpstack::uplink: Updating gateway meta-data for uplink frame-set
2025-12-11T08:39:58.638645Z DEBUG up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}: chirpstack::uplink: Logging uplink frame to Redis Stream
2025-12-11T08:39:58.641792Z TRACE up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request: chirpstack::uplink::join: Getting JoinRequestPayload
2025-12-11T08:39:58.641873Z TRACE up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request{dev_eui="8c1f642560001028"}: chirpstack::uplink::join: Getting device
2025-12-11T08:39:58.644510Z  INFO up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request{dev_eui="8c1f642560001028"}: chirpstack::uplink::join: Unknown device, trying passive-roaming activation dev_eui=8c1f642560001028 join_eui=0000000000000000
2025-12-11T08:39:58.644611Z TRACE up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request{dev_eui="8c1f642560001028"}:start_pr: chirpstack::uplink::join_fns: Filtering rx_info by public gateways only
2025-12-11T08:39:58.644653Z TRACE up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request{dev_eui="8c1f642560001028"}:start_pr: chirpstack::uplink::join_fns: Getting home netid
2025-12-11T08:39:58.644680Z TRACE up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request{dev_eui="8c1f642560001028"}:start_pr: chirpstack::uplink::join_fns: Trying to get join-server client join_eui=0000000000000000
2025-12-11T08:39:58.644721Z TRACE up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request{dev_eui="8c1f642560001028"}:start_pr: chirpstack::uplink::join_fns: Requesting home netid
2025-12-11T08:39:58.644819Z  INFO up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}:join_request{dev_eui="8c1f642560001028"}:start_pr:request{message_type=HomeNSReq sender_id=000000 receiver_id=0000000000000000 transaction_id=2000143231}: backend: Making request server=http://10.2.0.7:9000/join/endpoint async_interface=false
2025-12-11T08:39:58.647467Z ERROR up{deduplication_id=1f94ddb9-fab6-469f-9a15-8d41f9ec9864}: chirpstack::uplink::join: Handle join-request error error=EOF while parsing a value at line 1 column 0
2025-12-11T08:39:58.648835Z  INFO request{sender_id=0000000000000000 receiver_id=000000 message_type=HomeNSAns transaction_id=**2000143231**}: chirpstack::api::backend: Request received
2025-12-11T08:39:58.664999Z TRACE chirpstack::applayer::fuota::scheduler: Starting fuota scheduler_loop run
2025-12-11T08:39:58.665048Z TRACE chirpstack::applayer::fuota::scheduler: Get schedulable fuota jobs
202

**hNS:**
2025-12-11T08:39:58.040394Z TRACE chirpstack::applayer::fuota::scheduler: schedule_batch completed without error
2025-12-11T08:39:58.646028Z  INFO request{sender_id=000000 receiver_id=0000000000000000 message_type=HomeNSReq transaction_id=2000143231}: chirpstack::api::backend: Request received
2025-12-11T08:39:58.648020Z  INFO backend: Making request receiver_id=000000 transaction_id=2000143231 message_type=HomeNSAns server=http://10.2.0.7:9001
2025-12-11T08:39:58.648077Z DEBUG backend: JSON: {"ProtocolVersion":"1.0","SenderID":"0000000000000000","ReceiverID":"000000","TransactionID":**2000143231**,"MessageType":"HomeNSAns","Result":**{"ResultCode":"Success"}**,"HNetID":"000001"}
2025-12-11T08:39:58.721173Z TRACE chirpstack::downlink::scheduler: Starting multicast-group queue scheduler loop run
0 Answers