A Tango device automatically exports State and Status commands which return predefined enumeration values (Ready, etc.).

However, I was surprised to notice in the JTango latest source code that if State and Status are defined as attributes, JTango will still execute write requests on those attributes as their command counterparts. Also, it seems that events on State and Status attributes cannot be pushed.

Which reasons justify enforcing in JTango library that State and Status attributes behave as their commands counterparts ? Is there any way to get around that 'limitation' ?

I am running a device with different protocols and generic (protocol-wise) scripts to remotely control the device. They all rely on the State attribute that happens to not behave as expected with the Tango protocol.