> RAK_4631 especially is tied to a lot of things inside the source code that makes the module work as expected. You can add another define to act upon in macro guards but please never replace it. If you want to signal a'private hw' you can add your macro to the architecture.h for nrf52 platform.
Why would this have worked previously though? (changing from RAK_4631 to PRIVATE_HW in the platformio.ini)
Further, what you are suggestion actually is contrary to what is posted as part of the development documentaion.
https://meshtastic.org/docs/development/firmware/build/
Originally posted by @jbuck2005 in #5107 (comment)