Revision 3 is out now, which should fix this reported issue
When able, please confirm it … Thanks
Cheers Richard