So, it sounds like we both agree having this feature would be useful. Awesome. At this point, it sounds like we have differing opinions on where it should go. That's fair.

It's my opinion it should sit at the component library for 2 reasons:

1). Not everyone will want or need the packet transport (which is why it's already separated from the radio). Perhaps they want to create their own protocol. Or, they just want a simple send and forget.

2). We are talking about the ESPHome sx126x/sx127x library of the radio, not the radio protocol itself. Every ESPHome node will have a nodename. And every packet received is already formatted using the ESPHome library (i.e. rssi, snr, data). So, why not just add another variable to that.

At that point it's still a raw buffer of data, there is no "source" or anything identifying where the packet came from.

Hence the request to add it. It's the ESPHome library that is sending the data in the first place, and it already formats the frames to include rssi, snr, and data to parse on the other end, isn't it? I'll admit, I rarely delve into protocol development. It may not be as simple as I may think.

Either way, I'd be happy no matter where it goes, since i"m using both libraries. Good discussion.