When using two X2 remotes paired to the same hub (all on v6), activity and power-state synchronization is inconsistent depending on whether the second remote is awake.
-
Case A (problem): If an activity or power state is changed on Remote A while Remote B is asleep (display off), the state change is not reliably propagated to Remote B. Remote B may remain on the previous activity/power state.
-
Case B (works): If Remote B is awake during the interaction on Remote A, the state change is propagated reliably.
-
Case C (works): If the activity/power state is changed via the mobile app, both remotes update correctly, regardless of whether either remote is asleep or awake.
Impact: This prevents reliable operation of a two-remote setup on one hub and is a showstopper for this use case.
