Hi, we have found the issue causing this in the Hub Firmware and a fix will be included in the next firmware release.