Hi @benn
This has been fixed with a new release of the extension. Thanks for the heads up on this.
Mickaël