May be related to today’s hub firmware update, some other people have reported same problem. See the following: