It's likely to be same issue, but caused by another switch access which I overlooked.