All the Zigbee profiles are just pre-agreed upon standard messages (for example smart energy) going over "normal" zigbee (pro) protocol.
Pretty much. It is a bit more complicate that this in real life.
And any Zigbee (pro) device can receive and "see" those messages as long as it has the password/correct pan ID/ channel/ encryption key ?
And as long as stack does not kill them because they are not registered top be handled by the application.
A module I found was pre-approved platform for smart energy but the AT commands didn't seem "special". And just had unicast,broadcast and various rf parameters.
What mode is this? In order to handle standard profile messages, the stack must support ZigBee Cluster Library (ZCL).
So I assume when you write firmware to use such module you have the "construct" the packet yourself following the smart energy Vx.x specifications.
It is not easy to "construct" those frames. They are not simple messages, but rather complicated system of requests and responses. And core that handles all that stuff can be very complicated.
Anybody here that has experience with these profiles ?
I do, but I doubt you need SE profile. If you are not a utility company, then forget about it, SE requires Certicom library to do eliptic curve key negotiation and you are not getting that.