I have seen these problems before. What I'm guessing happens is that the Bluetooth connector uses a significant amount of Bluetooth resources (although this does not seem to affect CPU resources if viewed from Task Manager). In other words, having the Bluetooth connector running (i.e. by having HomeSeer running) seems to dramatically impede other Bluetooth operations, such as pairing. What's more, the longer the Connector has been running for, the more impact this appears to have on pairing/discovery.
I always pair first without HomeSeer running and then quickly jump into HomeSeer to do a Discover Service and ensure the PC gets a daily scheduled reboot.
I always pair first without HomeSeer running and then quickly jump into HomeSeer to do a Discover Service and ensure the PC gets a daily scheduled reboot.
Comment