Passive Roaming Activation

Viewed 71

Does Chirpstack support Passive Roaming Activation?
Thanks for response
grafik.png

2 Answers

Yes, ChirpStack does support Passive Roaming and it should work for both OTAA and data up / down.

Hello Orne, I am still testing OTAA via PR. Comply to the Message Flow Diagram the device do a join request at fNS and it do the HomeNSReq:
JavaScript Object Notation: application/json
Object
Member: ProtocolVersion
[Path with value: /ProtocolVersion:1.0]
[Member with value: ProtocolVersion:1.0]
String value: 1.0
Key: ProtocolVersion
[Path: /ProtocolVersion]
Member: SenderID
[Path with value: /SenderID:000000]
[Member with value: SenderID:000000]
String value: 000000
Key: SenderID
[Path: /SenderID]
Member: ReceiverID
[Path with value: /ReceiverID:0000000000000000]
[Member with value: ReceiverID:0000000000000000]
String value: 0000000000000000
Key: ReceiverID
[Path: /ReceiverID]
Member: TransactionID
[Path with value: /TransactionID:1152754225]
[Member with value: TransactionID:1152754225]
Number value: 1152754225
Key: TransactionID
[Path: /TransactionID]
Member: MessageType
[Path with value: /MessageType:HomeNSReq]
[Member with value: MessageType:HomeNSReq]
String value: HomeNSReq
Key: MessageType
[Path: /MessageType]
Member: DevEUI
[Path with value: /DevEUI:8c1f642560001007]
[Member with value: DevEUI:8c1f642560001007]
String value: 8c1f642560001007
Key: DevEUI
[Path: /DevEUI]
The HomeNS is answering with "Success":
JavaScript Object Notation: application/json
Object
Member: ProtocolVersion
[Path with value: /ProtocolVersion:1.0]
[Member with value: ProtocolVersion:1.0]
String value: 1.0
Key: ProtocolVersion
[Path: /ProtocolVersion]
Member: SenderID
[Path with value: /SenderID:0000000000000000]
[Member with value: SenderID:0000000000000000]
String value: 0000000000000000
Key: SenderID
[Path: /SenderID]
Member: ReceiverID
[Path with value: /ReceiverID:000000]
[Member with value: ReceiverID:000000]
String value: 000000
Key: ReceiverID
[Path: /ReceiverID]
Member: TransactionID
[Path with value: /TransactionID:1152754225]
[Member with value: TransactionID:1152754225]
Number value: 1152754225
Key: TransactionID
[Path: /TransactionID]
Member: MessageType
[Path with value: /MessageType:HomeNSAns]
[Member with value: MessageType:HomeNSAns]
String value: HomeNSAns
Key: MessageType
[Path: /MessageType]
Member: Result
Object
Member: ResultCode
[Path with value: /Result/ResultCode:Success]
[Member with value: ResultCode:Success]
String value: Success
Key: ResultCode
[Path: /Result/ResultCode]
Key: Result
[Path: /Result]
Member: HNetID
[Path with value: /HNetID:c0003e]
[Member with value: HNetID:c0003e]
String value: c0003e
Key: HNetID
[Path: /HNetID]

Step 5 a. 6 aren't happened in the only PR case!
But the fNS is never doing the Step 7 "PRStartReq"??
Do have an idee?
Thanks a lot