This is a known issue. I was having a problem with this on some of my V3’s until I loaded this new beta firmware that was just pushed to Beta last week:
It should hopefully be released to everyone soon if the beta testing goes well. If you don’t want to wait for it, you can enroll in beta and load the latest update and it should be resolved now. It is working for me again with this update.