Kimmo Huoman

In general this looks like a good base, the only big issue for me is that there's no backwards compatibility. I'd like to have the `Packet` remain the same, maybe...

@toggm Yeah, the target should be that no changes are required for ESP3. Changes for ESP2 support on programs using this library would be fine. In practice this is shown...

@Stoney49th Sounds great! :+1: Once you're happy to make a pull request, open one and we can then continue on commenting and polishing it through that I've been also interested...

Well, not planned, but of course possible... At the moment, I have the trouble of not really using (or requiring) the use of EnOcean devices, which leads to very little...

I had quite a long discussion about the availability of XMLs when starting this project, at least then the response was a clear "no".

Well, it does and it doesn't. `Packet.data` includes the whole data, including stuff like `RORG`, `Sender ID` etc, which are not included in EEP. The idea of this issue is...

Please post the full code, with the device IDs.

You're not setting optional data, which should include the destination ID. Therefore the packet is handled as a broadcast message -> every switch in range reacts to it. I suggest...

I've now created the method discussed in #14. I've made also the corresponding changes to the example, so the `Packet` creation should be fairly easy now. However, one issue remains:...

Moving discussion back to this issue from #14. Hmm, actually according to [this document](http://www.g-media.fr/media/pdf/domotique/DO21-11B-E.pdf), if correctly translated by Google, you should be able to use other profiles as well. There's...