I had what seems to be the same issue using the Advanced Zigbee CT driver and switched to the generic zigbee CT driver to correct the problem. Not sure if its the same type bug but would like to bring it to someones attention. I am asking because Im not sure. if some one coild look at this short thread.
