Announcement

Collapse
No announcement yet.

Suddenly disconnected and doesn't work ever since

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Suddenly disconnected and doesn't work ever since

    Hello,

    I have a DualSense controller connected to my computer, with reWASD targetted to a Switch.
    Everything was working perfecty fine and smooth for a day until few hours ago, when the Switch is not responding to my controller.
    In reWASD it shows my DualSense is still running and connected to the targetted Switch, but the Switch is not receiving any signals.

    After that I tried reopening reWASD and reconnecting my DualSense to the Switch, but the status displaying in reWASD keeps flashing beween 'Waiting for the connection' and 'Connected to console'.
    I tried restarting the Switch, restarting the computer, reconnecting the DualSense to the computer, switching off and on computer's Bluetooth, unpair all saved controllers in Switch's settings, and none of them worked.

    I also tried removing the Switch from 'target devices' and removing the bluetooth adapter from 'adapters' in reWASD's 'External device' settings page, and 'Clear data' from the 'General' settings page.
    When I redo the whole initial connecting process, reWASD successfully got the Step 3 showing 'You are all set', while Window's bluetooth settings also shows my computer is connected to the Switch.
    However, the Switch's 'change grip order' page is still not showing any connected controllers, and the status goes back to flashing 'Waiting for the connection' and 'Connected to console' again.

    I have tested with another Switch controller that directly connects to the Switch without reWASD, and it is working fine so it shouldn't be the Switch's detection problem.
    Everything was connecting and working smoothly before the sudden disconnection, so it proves the connecion is possible,

    Please let me know what is the issue here and what else can I do to fix it.

    Thank you very much.

  • #2
    Switch consoles have a protection mechanism that prevents connection from non-official controllers, and it appears to be triggering in your case.
    We usually recommend using Broadcom-based Bluetooth adapters (which are likely to work) or an ESP32 Bluetooth adapter (which will definitely work), as most Bluetooth adapters are not fit for proper emulation.

    We'll need you to collect some logs to understand what is happening on your side. So please do the following:
    1. Use the [Clear data] button in [Preferences > General].
    2. Close reWASD and its Tray Agent.
    3. Delete the contents of the [c:\Users\Public\Documents\reWASD\Logs\] folder.
    4. Restart reWASD as Administrator.
    5. Open [Preferences > General].
    6. Make sure all options under [Standard logging] are enabled and click the [Start log] button.
    7. Set up an external virtual Nintendo Switch Pro and connect it to your Switch console.
    8. Wait until either the virtual controller is connected or the Switch console starts denying the controller.
    9. Click the [Stop log] button in [Preferences > General].
    10. ZIP up the contents of the [c:\Users\Public\Documents\reWASD\Logs\] folder and send it to us at [help@rewasd.com] with a link to this thread.

    Comment


    • #3
      Hello, the email with the zip folder attached has been sent. Please let me know any more files are needed.

      The DualSense with reWASD has been working fine with absolutely no problem at all before the sudden disconnection, or did something change at the disconnection moment causing the Switch to suddenly acknowledge the reWASD emulation as a non-official controller and start rejecting it?

      Comment


      • #4
        According to the logs, you are still using an unsupported version of reWASD (7.0.0). Please update to the latest version from our site.

        Comment


        • #5
          Hello,

          I have updated to version 9.2.0.10664 and the problem is still unsolved.

          New log files have been sent through email.

          Thank you

          Comment


          • #6
            We will check the logs with the team.

            However, we suggest purchasing an ESP32 Bluetooth Adapter, since we cannot guarantee that our external virtual controller will work with Switch consoles on any other Bluetooth adapter.

            Comment


            • #7
              Thank you very much for your help. Looking forward for the issue to be solved.

              I am planning to get an ESP32 adapter, but I still would like to try and fix the problem I am currently experiencing.
              As I mentioned in earlier replies, the current local Bluetooth adapter did successfully work and connected smoothly to the Switch for quite some time, which shows my current adapter is capable of functioning as intended.

              Comment

              Working...
              X