Are there 2 versions of the state? Which one is considered as the source of truth?

I also couldn't find the case for this extra check. Is it possible to have a discrepancy between the two states?

Last week this.desktopState.desktopEnabled was returning false while establishing a new connection, but after rebasing today I removed this change and the fix still works.

Why do we need the alternate states here? Would no key and the wrong key not both result in the same "app not recognised" error?

There is another scenario where "Desktop has no pairing key" here

We really shouldn't be relying on implicit behaviour of enums where the values are assigned to numbers by default which in turn evaluate to truthy. We could change the order of the values, or assign them to strings and this would break.

I'd recommend assigning to a variable then doing a [PairingKeyStatus.NO_MATCH, PairingKeyStatus.MISSING].includes(pairingKeyStatus) to be explicit.

Good catch! It shouldn't be like that.
I was doing negatively compared with PairingKeyStatus.MATCH but the way you recommended it's more explicit.
Pushing the changes.

If we need this enum, then pairingKey is implied and we've been using capitals for enums so maybe MATCH, NO_MATCH and MISSING?