@les great! We'll, the debug flags should not help getting things to work, only provide additional information if it doesn't.
All configuration flags need to be placed prior to any header include directives. Else they will have no effect.
Anyway, glad it worked out in the end.
@les correct, no personalization needed. But with that flag, all nodes in your network need to share it. And memory requirements increase significantly so pay attention to the compiler log regarding warnings on memory use.
@les correct.
Have you checked the troubleshooting section in the docs regarding signibg issues? There is also a more verbose debug flag available.
@les right, but you also write that you were interested in encryption and not signing, so it is not the correct flag in that case. And also, note that you need the same flag on all nodes and gw if you use one that enable encryption.
@les here are all the security related flags documentation.
Hope will test the new version of this universal board soon. Now it has additional inexpensive accelerometer, magnetic sensor, led, reset button, multifootprint for lora/hw/cw radio without adapter and improoved 4layers design 
Hi. I use TPS61221DCKR for boards with such PIRs.
@sharath-b-krishna no, the simple options have all secrets stored in the sketch, so don't put your production code on github if you plan to use that
@alowhum @Sharath-B-Krishna yes, at least if we are talking a single gw setup. It is possible to use two gw:s to have two separate networks. One can be encrypted and the other plain.
