search

psmoveservice / PSMoveService

A background service that communicates with the psmove and stores pose and button data.
Apache License 2.0
593 stars 147 forks source link

Controllers appearing paired then unpairing #735

Closed darkessaiden closed 4 years ago

darkessaiden commented 4 years ago

I got 1 of my 2 controllers to pair but when it does decide to connect it just kinda blips out after a second and doesn't even light up. I'm using the newer model of controller with the micro port. The log keeps showing these messages:

PSMoveController::close - Closing PSMoveController(\?\hid#vid_054c&pid_0c5e&col01#7&16447b7a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) AsyncBluetoothPairDeviceRequest - Bluetooth device matching the given address is the expected controller type AsyncBluetoothPairDeviceRequest - Already authenticated. ServerRequestHandler - Async bluetooth request([Pair] ID: 0 Conn: 0) Canceled. ServerRequestHandler - Async bluetooth request([Pair] ID: 0 Conn: 0) failed! DeviceTypeManager::update_connected_devices - Closing device 0 (PSMove) since it's no longer in the device list. WorkerThread::stop - Stopping worker thread: PSMoveSensorProcessor WorkerThread::stop - Worker thread stopped: PSMoveSensorProcessor libusb: error [windows_get_device_list] program assertion failed - existing device should share parent

I'm using an atheros bluetooth+wi-fi card in a pcie-x1 slot, I read that the specific bluetooth adapter used matters so I hope that's not the issue. The libusb message is the most persistent and might be the root of the problem.

darkessaiden commented 4 years ago

Update: One of the controllers is now successfully paired and works perfectly, the other is still having the same issue. They are both reporting as id.0. I've tried un-pairing through windows and re-pairing but it still self reports as id.0 and disconnects after a second.

[2020-08-24 23:01:46.932]: PSMoveController::open - Opening PSMoveController(\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&0c5e&col01#9&e3c4ee7&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) [2020-08-24 23:01:46.938]: PSMoveController::open - with serial_number: dc0c2d3b504a Config file name: "C:\Users\aiden\AppData\Roaming\PSMoveService\dc_0c_2d_3b_50_4a.json" [2020-08-24 23:01:46.947]: WorkerThread::start - Starting worker thread: PSMoveSensorProcessor Config file name: "C:\Users\aiden\AppData\Roaming\PSMoveService\dc_0c_2d_3b_50_4a.json" [2020-08-24 23:01:46.954]: DeviceTypeManager::update_connected_devices - Device device_id 0 (PSMove) opened libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent [2020-08-24 23:01:49.426]: ServerDeviceView::poll - Device id 0 closing due to no data (100 failed poll attempts) [2020-08-24 23:01:49.429]: PSMoveController::close - Closing PSMoveController(\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&0c5e&col01#9&e3c4ee7&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) [2020-08-24 23:01:49.436]: WorkerThread::stop - Stopping worker thread: PSMoveSensorProcessor [2020-08-24 23:01:50.38]: WorkerThread::stop - Worker thread stopped: PSMoveSensorProcessor

darkessaiden commented 4 years ago

Update: I reinstalled the service and swapped to the updated admin.exe file and it fixed the issue. I'm unsure why this resolved the problem but everything is working now.