Default generated Device UUID uses wrong endianness and violates specification

Default generated Device UUID uses wrong endianness and violates specificationhttps://devzone.nordicsemi.com/f/nordic-q-a/58011/default-generated-device-uuid-uses-wrong-endianness-and-violates-specificationThe default generated Device UUID in SDK For Mesh v4.0.0 uses wrong endianess. From the Mesh Profile v1.0.1, section "3.10.3 Device UUID" "To decrease the complexity of deploying nodes, a unique Bluetooth BD_ADDR is not required for mesh operationsen-USTelligent Community 13Thu, 20 Feb 2020 08:45:54 GMTRE: Default generated Device UUID uses wrong endianness and violates specificationhttps://devzone.nordicsemi.com/thread/235356?ContentTypeID=1Thu, 20 Feb 2020 08:45:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2d6876ca-3fae-4691-a4b6-90801952b39fJoakim Jakobsen<p>Hi. </p> <p>Thank you for another detailed report. </p> <p>This will also be forwarded internally to our Mesh team.</p> <p>Regards,<br />Joakim </p><div style="clear:both;"></div>