I encountered an obscure issue while re-configuring Hub Mesh token authentication between a C‑8 Pro and a C‑5 through my.hubitat.com. Initially, it appeared that the C‑5 was rejecting the C‑8 Pro’s token.
The problem seems to involve portal navigation when accessing more than one hub. After opening one hub through the portal and then accessing a second hub through the same portal, certain links on the Hub Mesh page unexpectedly open the other hub and terminate or replace the connection to the hub I was working on.
This makes it easy to lose track of which hub is actually receiving the configuration changes. In my case, it led to an apparent “invalid token” problem during token exchange.
Sequence that exposed the issue:
-
Access the first hub through my.hubitat.com.
-
Access a second hub through the same portal while the first is still open.
-
Follow links within the Hub Mesh page.
-
Observe that certain links take you to the other hub instead of keeping you on the intended hub.
Expected behavior: Navigation within a hub’s configuration pages should remain associated with that hub, even when another hub has been opened through the portal.
Workaround: Access only one hub at a time through the portal when copying and entering Hub Mesh tokens. This resolved the issue for me.
I have not isolated the specific links responsible or established whether this affects other hub models. I’m reporting it as a potential portal session/navigation defect rather than a confirmed Hub Mesh authentication defect.
Has anyone else encountered this behavior? I’d appreciate guidance on any diagnostic information that would help identify the cause.
Many thanks in advance for any insights related to this odd portal behavior!
U. Balis