[SOLVED] Shibari not showing my BT adapter, cannot pair


  • UPDATE: After doing this once, running the Shibari Dom Server one more time, then pressing the on button on the PS3 controller paired properly!!!!!!!

    [21:53:19 INF] Found SIXAXIS device \?\BTHPS3BUS#{53F88889-1AAF-4353-A047-556B69EC6DA6}#9&1F715471&0&0498F3AB5500#{7B0EAE3D-4414-4024-BCBD-1C21523768CE} (BTHPS3BUS{53F88889-1AAF-4353-A047-556B69EC6DA6}\9&1F715471&0&0498F3AB5500)
    [21:53:19 INF] Device DualShock3 (04:98:F3:AB:55:00) got attached via Bluetooth
    [21:53:19 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller
    [21:53:19 INF] ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller connected successfully
    

    Now to test it.....

    END UPDATE

    So, after a very long absence I am back, and trying this whole thing again. Today I:

    Installed BthPS3 Bluetooth Drivers_v1.2.2
    Installed 64 version of FireShock (latest)
    Installed ViGEmBus_Setup_1.16.116
    Downloaded latest Shibari

    Upon starting Shibari Dom Server I recieve:

    [21:10:44 INF] Launching Shibari, version: 1.5.164.0
    Configuration Result:
    [Success] Name Shibari.Dom.Server
    [Success] DisplayName Shibari Dom Server
    [Success] Description Manages AirBender, FireShock & BthPS3 Devices.
    [Success] ServiceName Shibari.Dom.Server
    Topshelf v4.2.1.215, .NET Framework v4.0.30319.42000
    [21:10:45 INF] Loaded sink plugin ViGEm Xbox 360 Sink
    [21:10:45 INF] Loaded bus emulator BthPS3 Bus Emulator
    [21:10:45 INF] Starting bus emulator BthPS3 Bus Emulator
    [21:10:45 INF] BthPS3 Bus Emulator started
    [21:10:45 INF] Bus emulator BthPS3 Bus Emulator started successfully
    [21:10:45 INF] Loaded bus emulator FireShock Bus Emulator
    [21:10:45 INF] Starting bus emulator FireShock Bus Emulator
    [21:10:45 INF] FireShock Bus Emulator started
    [21:10:45 INF] Bus emulator FireShock Bus Emulator started successfully
    The Shibari.Dom.Server service is now running, press Control+C to exit.
    

    However, I know that I want to connect by BT, and if I read the Bluetooth Pairing with Shibari instructions I should be seeing an entry for the "Bluetoh Host Address" info, but as shown above, I don't have that entry when running Shibari Dom Server. I have tried running the PowerShell Import-Module command (and keeping it open), but that doesn't expose the Bluetooth Host Address. So I am stumped as what to do next,

    Just FYI, I confirm that my controller works on USB as when instered I get the below, and subsequently the Windows XBOX 360 Sucsess message in the notification tray.

    [21:42:09 INF] Found FireShock device \\?\USB#VID_054C&PID_0268#6&26030B37&0&7#{51AB481A-8D75-4BB6-9944-200A2F994E65} (USB\VID_054C&PID_0268\6&26030B37&0&7)
    [21:42:09 INF] Device is DualShock3 with address 04:98:F3:AB:55:00 currently paired to 00:02:72:D1:E9:92
    [21:42:09 INF] Device DualShock3 (04:98:F3:AB:55:00) got attached via USB
    [21:42:09 INF] Auto-pairing device DualShock3 (04:98:F3:AB:55:00) to 00:02:72:D1:E9:92
    [21:42:09 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller
    [21:42:09 INF] ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller connected successfully
    

    By the way, output above shows the "currently paired to" and "Auto-pairing" addresses as correctly finding by BT adapter, this is good, I think? However, when I disconnect the USB to see if I can connect to BT, the Shibari Dom Server vanishes. Subseuently, when I press the on button on the PS3 controller, I hear the Windows "connect" sound, but after a few seconds I hear the Windows "disconnect" sound.

    any ideas?

    thanks,
    RDP


  • Is there still an issue? I can't quite tell from the spaghetti-code-style of the writing 😛


  • you should hear 2 connect sounds(rising pitch) when pairing via blue tooth, the first is the DS3 being connected, the second is the xbox controller emulator being connected.


  • Yes, everything seems fine now.

    thanks!

    RDP


  • And what did you actually do to fix?