If you configure a PD (just one) for secure channel and the PD was not set up for secure channel it goes into a loop sending osdp_CHLNG on sequence 1 and getting a nak/encryption required. If you then reconfigure the PD for secure channel and restart the PD (the ACU is still running) then you get a loop where the ACU is sending osdp_CHLNG on sequence 1 and the PD sends nak/bad sequence number, sequence 0. The ACU never respects the sequence 0 aspect and does not reset the session and therefore never connects. Workaround is to reset everything. This feels like an osdp.net underlying bug and not an APBox-specific artifact.
If you configure a PD (just one) for secure channel and the PD was not set up for secure channel it goes into a loop sending osdp_CHLNG on sequence 1 and getting a nak/encryption required. If you then reconfigure the PD for secure channel and restart the PD (the ACU is still running) then you get a loop where the ACU is sending osdp_CHLNG on sequence 1 and the PD sends nak/bad sequence number, sequence 0. The ACU never respects the sequence 0 aspect and does not reset the session and therefore never connects. Workaround is to reset everything. This feels like an osdp.net underlying bug and not an APBox-specific artifact.