UPDATE: The “workaround” script is now available with ST support. The “fix” will be deployed in the upcoming 0.31.x hub firmware:
As I understand, this “issue” is acknowledged in the 0.30.x firmware, so keep an eye out for it. You could point support back to that link as well. It’s possible they may not be aware of it just yet.