One of the big obstacles for Enocean support was the licensing / IP issues with the enocean alliance.
An open source implementation of the protocol is ok, but the statement of the alliance is that any business user would be required to be part of the alliance (and pay them money). Which is really difficulty for an open source project like openhab. Don’t know if this is still that case, but I fear yes.
The inclusion of the enocean (opencean) library in openhab 1 / 2 might even be incompatible with the eclipse license.
AFAIK these IP and licensing issues are the reason why the aleoncean library was withdrawn.
Any direct usage of the protocol inside EPL code is probably prohibited, preventing anyone from developing a binding included into the official openhab distro where everything is EPL.
If there would be a clear commitment of the Enocean Alliance to open source, all of this would probably be solved, but there isn’t.
For me this is a reason to not increase enocean device use in my house and even think about replacing the existing ones.