I think the situation here might be the requirement to integrate with an existing IDRATEK system. In comparison to the Loxone etc. it might actually work out cheaper to run a second IDRATEK setup and use Cortex bridge between the two, which would achieve the proper automation integration aspect and of course consequently also provide the whole range of IDRATEK features such as snartphone and web browser control/interrogation/data logging etc. But I think this will be overkill for one light.
There is possibly a marginal reliability benefit to using enOceon by virtue of it using the more tightly regulated 868MHz band, but I think it is otherwise similar to the likes of HomeEasy, lightwavRF and so on in terms of using unacknowledged communication protocols relying on multiple message copies to try and counteract message loss. None of these is great for deeply automated systems like IDRATEK's which can also have high message volumes, hence our reluctance to introduce interfaces to such beyond our early foray into X10 and Rako. Zwave and Zigbee are better but still some issues for us. So for the time being a simple radio gateway to the former might be the most practical.